Update readme with TS typings

Those might be needed for users that compile TS with noImplicitAny compiler option.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Coverage decreased (-0.2%) to 95.0% when pulling d745a30859aced5cd28307735b9ada6c868928ad on ondrowan:patch-1 into 67ace6fb857ecb38be6e5dbb8a8eabd7eebe070c on dgraph-io:master.

Coverage decreased (-0.2%) to 95.0% when pulling d745a30859aced5cd28307735b9ada6c868928ad on ondrowan:patch-1 into 67ace6fb857ecb38be6e5dbb8a8eabd7eebe070c on dgraph-io:master.

Coverage decreased (-0.2%) to 95.0% when pulling d745a30859aced5cd28307735b9ada6c868928ad on ondrowan:patch-1 into 67ace6fb857ecb38be6e5dbb8a8eabd7eebe070c on dgraph-io:master.

Did you need these typings anywhere?

I use TypeScript with strict compiler option (which includes noImplicitAny). In that case, if typing isn't present, you get following error:
Could not find a declaration file for module 'protobufjs'. '.../node_modules/protobufjs/dist/protobuf.js' implicitly has an 'any' type.
 Try `npm install @types/protobufjs` if it exists or add a new declaration (.d.ts) file containing `declare module 'protobufjs';`

Oh! I see. BTW thanks for the contribution.

Could you add a command for yarn also and the save-dev option for both of them.

Done.

Thanks


VeeValidate validating a non-existent field error even with key

Versions

vee-validate: 2.2.9
vue: 2.6.10

Describe the bug
I have a "select" and "text" to switch from. When I close the my modal, I run this : this.$validator.reset();
The problem is that I get the error : "Uncaught (in promise) Error: [vee-validate] Validating a non-existent field: "#29". Use "attach()" first." if I open the modal by editing a row with dynamic field of type "a" and then editing a row of type "b"
To reproduce
`

Catégorie du soin*

                            <template v-if="vCatState === 'list'">

                                        <option></option>
                                        <option v-for="categoriesoin in categoriesoins" :key="categoriesoin.id" v-bind:value="categoriesoin.id">
                                            {{categoriesoin.name}}
                                        </option>

                                    {{ errors.first('catégorie liste') }}

                            </template>
                            <template v-else-if="vCatState === 'typing'">

                                    {{ errors.first('catégorie texte') }}

                            </template>

                        `

Expected behavior
I hoped that : "this.$validator.reset();" would handle switching between dynamic fields if they had a key.
Desktop (please complete the following information):

W10
Chrome
Version 74.0.3729.169

Additional context
I've been trying to get this to work for a moment now but I haven't figured out a solution. I've read about the VeeValidate dynamical fields but it didn't help either.

The same issue here, it was working fine a few days ago, not too sure what has happened.

The directive timing issues is hard to pinpoint and fix completely. I suggest moving to ValidationProvider component as it is more robust and doesn't have the common issues of a directive.
The directive will be deprecated in v3

This bug is still present as far as I can tell — we're seeing this issue when used in a modal and a collapsible accordion


New package: IntegrateSphericalPoly v1.0.0

Registering package: IntegrateSphericalPoly
Repository: https://github.com/harris-mit/IntegrateSphericalPoly.jl
Created by: @harris-mit
Version: v1.0.0
Commit: cf824fed8b2c0fabc561e0c2079a7ed2f7f901c2
Reviewed by: @harris-mit
Reference: https://github.com/harris-mit/IntegrateSphericalPoly.jl/issues/3#issuecomment-2140938642
Description: Integrate polynomials over the sphere in arbitrary dimensions.

Congratulations on the new package! Could you extend the README a little bit with a usage example?


Adding lale.lib.rasl.SimpleImputer.

Added a new operator that uses Aggregate and Map for missing value imputation.
Added support for mode and median as aggregates.
Added exclude_value hyperparameter to Aggregate so that it can exclude the missing value while computing the aggregate.

Here are few caveats with this implementation:

In the case of multiple modes in the data, sklearn chooses the one with the smallest value. This works for rasl.SimpleImputer for numeric columns, but does not for strings.
The aggregate mode for spark does not work when it is used after a groupby. When SimpleImputer is used, we do not expect a GroupedData, so keeping it that way for now.

Hi, thanks so much for this PR! It looks great overall. I am impressed that you went the extra mile to implement all of the strategies of SimpleImputer. I added a few inline comments in the code. The biggest comment is probably that instead of adding a hyperparameter to Aggregate, I would prefer to use a Filter operator. I hope that is possible and that I didn't miss anything fundamental there.

Thank you for all the comments Martin! I will look into the Filter >> Aggregate and partial_fit next.

Thank you for all the comments Martin! I will look into the Filter >> Aggregate and partial_fit next.

Regarding Filter >> Aggregate, I would give this lower priority, because you already have a working solution, and because of the need to do different filtering for each column.
Regarding partial_fit, I wonder if you can do this via static lift and combine methods like in OneHotEncoder, OrdinalEncoder, and StandardScaler. My hope is that we can use the combine method for cross-validation. At the same time, if that API is somehow problematic for SimpleImputer, that would be good to know so we can revise the API accordingly.


libs/utils/energy: Add 'power' kind for default VExpress hwmon config

It seems like some hwmon instances use 'power' instead of 'energy'. It looks like we can just enable both.
I'm not merging this unilaterally because there's a lot of hwmon-related code between LISA and devlib that I don't understand. It would also be fantastic if at least one other person could test this as it seems likely I'm breaking something for somebody.
BTW, at some point we really need to improve the way the hwmon stuff reports errors. This error was reported as a KeyError in HwMon.report. I spent a little time to try and make it a bit more helpful but there's really a lot of complexity and it seems like this complexity is necessary.

I would not be surprised if that depends on the kernel version in use... I'm pretty sure it used to work in the past using "energy".
Regarding kinds, AFAIR you can specify multiple channels and devlib does its best (sloooowly) to figure out which one are available. But, if there should be only one of the two, the code we have should sill work since we index just on sites... but I'm not completely sure and yes, that should be tested by more people... perhaps also using an older kernel.

[-1] don't merge

This is not the correct solution. Will separately submit the error message improvement.


Homework Week 2

Hey John,
Great job on the h/w! Love the images you used for the bootstrap site. Were you also able to upload your files for Assignment 1 to github?
Peter

I was, however, they may be in a different repo because of what i was dealing with with heroku. i submitted the original repo with my first submission today. let me know if you need me to send you that repo again.

On Feb 10, 2016, at 8:47 PM, Peter Tumulty<EMAIL_ADDRESS>wrote:
Hey John,
Great job on the h/w! Love the images you used for the bootstrap site. Were you also able to upload your files for Assignment 1 to github?
Peter
—
Reply to this email directly or view it on GitHub https://github.com/johnreda/herokutest/issues/1.


Bug fix in uniform cost search implementation

Hello,
There is a bug in the implementation of the uniform cost search in the file search-4e.ipynb.
In this commit you can see the fix. There are also some typo fixes in previous commits in my fork...
Cheers
PS. Thanks a lot for sharing the code of AIMA book. Very helpful !

i would like to take this up

I am a newcomer in this organisation, can anyone help me out.


Add dynamic schemas on a per-query basis

Resolves https://github.com/supabase/postgrest-js/issues/280
What kind of change does this PR introduce?
Feature
What is the current behavior?
Currently, the supabase client is created and defaults to the public schema when no option is supplied:
createClient(supabaseUrl, supabaseKey)

Or, you can supply an alternative schema:
createClient(supabaseUrl, supabaseKey, {
  db: {
    schema: 'alternative'
  }
})

However, this means that all methods/queries for the client are associated to the single schema. Using multiple schemas requires multiple clients, which presents a challenge for auth where all clients need to be authenticated.
See pre-existing issue:
https://github.com/supabase/postgrest-js/issues/280
What is the new behavior?
The method added to the supabase client allows for dynamic schema selection on a per-query basis.
const supabase = createClient(supabaseUrl, supabaseKey);

supabase.from('some_table_in_public').select();

supabase.schema('alt').from('table_in_alt').select()

Additional context
Add any other context or screenshots.

Thanks for the feedback! We do have an issue discussing a solution for this here https://github.com/supabase/postgrest-js/issues/280 . We will pick this one post launch week. Thanks for your patience!

Thanks @sjones6! We'll need the change both here and in postgrest-js, so keeping this open.

@soedirgo , updated this PR now that https://github.com/supabase/postgrest-js/pull/455 is published.


dvc: fix build

Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 185127 run on x86_64-linux 1

2 packages built:

dvc
dvc-with-remotes

@SuperSandro2000 Hello!
FYI, I just saw that when I run dvc init on my x86_64-linux laptop, I have the following output:
Traceback (most recent call last):
  File "/nix/store/bhkgqn7flwd1y5zyssny0lsyixmpgwfm-dvc-2.12.0/lib/python3.10/site-packages/dvc/cli/__init__.py", line 185, in main
    ret = cmd.do_run()
  File "/nix/store/bhkgqn7flwd1y5zyssny0lsyixmpgwfm-dvc-2.12.0/lib/python3.10/site-packages/dvc/cli/command.py", line 36, in do_run
    return self.run()
  File "/nix/store/bhkgqn7flwd1y5zyssny0lsyixmpgwfm-dvc-2.12.0/lib/python3.10/site-packages/dvc/commands/init.py", line 42, in run
    from dvc.repo import Repo
  File "/nix/store/bhkgqn7flwd1y5zyssny0lsyixmpgwfm-dvc-2.12.0/lib/python3.10/site-packages/dvc/repo/__init__.py", line 13, in <module>
    from dvc.ignore import DvcIgnoreFilter
  File "/nix/store/bhkgqn7flwd1y5zyssny0lsyixmpgwfm-dvc-2.12.0/lib/python3.10/site-packages/dvc/ignore.py", line 11, in <module>
    from dvc.fs import AnyFSPath, FileSystem, Schemes, localfs
  File "/nix/store/bhkgqn7flwd1y5zyssny0lsyixmpgwfm-dvc-2.12.0/lib/python3.10/site-packages/dvc/fs/__init__.py", line 33, in <module>
    from dvc_objects.fs.implementations.gdrive import GDriveAuthError  # noqa: F401
ImportError: cannot import name 'GDriveAuthError' from 'dvc_objects.fs.implementations.gdrive' (/nix/store/kzspjpsfk7cxbbaadzbnfc2rfd3il9cx-python3.10-dvc-objects-0.1.5/lib/python3.10/site-packages/dvc_objects/fs/implementations/gdrive.py)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/nix/store/bhkgqn7flwd1y5zyssny0lsyixmpgwfm-dvc-2.12.0/bin/.dvc-wrapped", line 9, in <module>
    sys.exit(main())
  File "/nix/store/bhkgqn7flwd1y5zyssny0lsyixmpgwfm-dvc-2.12.0/lib/python3.10/site-packages/dvc/cli/__init__.py", line 202, in main
    ret = _log_exceptions(exc) or 255
  File "/nix/store/bhkgqn7flwd1y5zyssny0lsyixmpgwfm-dvc-2.12.0/lib/python3.10/site-packages/dvc/cli/__init__.py", line 69, in _log_exceptions
    from dvc.fs import AuthError, ConfigError, RemoteMissingDepsError
  File "/nix/store/bhkgqn7flwd1y5zyssny0lsyixmpgwfm-dvc-2.12.0/lib/python3.10/site-packages/dvc/fs/__init__.py", line 33, in <module>
    from dvc_objects.fs.implementations.gdrive import GDriveAuthError  # noqa: F401
ImportError: cannot import name 'GDriveAuthError' from 'dvc_objects.fs.implementations.gdrive' (/nix/store/kzspjpsfk7cxbbaadzbnfc2rfd3il9cx-python3.10-dvc-objects-0.1.5/lib/python3.10/site-packages/dvc_objects/fs/implementations/gdrive.py)

I am going to mark it broken since it is obviously not working right now. The update requires a new package which I don't want to package right now since I am not even using the package.

I am going to mark it broken since it is obviously not working right now. The update requires a new package which I don't want to package right now since I am not even using the package. If someone wants to fix it feel tree to do that.

@SuperSandro2000 Hello!
No problem, I use dvc regularly so I will try to fix that issue and upgrade dvc in the next few days :)

PR to upgrade dvc to v2.17.0: https://github.com/NixOS/nixpkgs/pull/185703


Observation in data doesn't match the retention period END date time for Delete policy.

In this example, it says "typically 1-7 days after the start of the retention period on day 2"
https://learn.microsoft.com/en-us/microsoft-365/compliance/retention-policies-teams?view=o365-worldwide#example-3-delete-only-after-1-day
from above document, my understanding in "1-day delete policy" is like this:
Message sent: 2022-11-01T02:30:00 (UTC)
Retention period start: 2022-11-02T00:00:00(UTC)
Retention period end: 2022-11-03T00:00:00(UTC)
However, my observation in data doesn't match above understanding.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 147f081a-c235-3400-23c9-8b4de7c9bbbc
Version Independent ID: 0d8958fb-247e-c05b-999e-3cbd93e943c9
Content: Learn about retention for Teams - Microsoft Purview (compliance)
Content Source: microsoft-365/compliance/retention-policies-teams.md
Service: o365-seccomp
GitHub Login: @cabailey
Microsoft Alias: cabailey

@VincentXu2021 I don't see how this is actionable for the documentation as a GitHub Issue, but I can share that the explanation and example went through careful review and signoff by the engineering team that owns the code. If your observations don't match the documentation, you can open a support ticket for investigation.  They can contact us if they think any changes are needed.


Looking for sources for corpora

Would like to add more corpora but don't have stable links for them yet.
The first one is MiPACQ:
paper - the Multi-source Integrated Platform for Answering Clinical Questions corpus, containing 13,091 sentences from clinical narratives, all annotated for syntactic structure and named entities.
Looks like it should be at http://clear.colorado.edu/compsem/index.php?page=endendsystems&sub=mipacq but that link doesn't appear live at the moment.

SHARPn NLP Seed Corpus - paper - clinical notes from pulmonary arterial disease and breast cancer patients.
That paper may not be quite right.

SHARPn Stratified Corpus - this and the previous set seem like they should be at http://informatics.mayo.edu/sharp/index.php/Tools but I haven't found download links for the corpora.

Would like to add more corpora but don't have stable links for them yet.
The first one is MiPACQ:
paper - the Multi-source Integrated Platform for Answering Clinical Questions corpus, containing 13,091 sentences from clinical narratives, all annotated for syntactic structure and named entities.
Looks like it should be at http://clear.colorado.edu/compsem/index.php?page=endendsystems&sub=mipacq but that link doesn't appear live at the moment.

The Colorado CLEAR page is accessible but doesn't have an obvious link to the MiPACQ corpus.
Looks like usage may still require coordination through Mayo Clinic?

Gave up looking for these - inaccessible data sets are Not Awesome.

Hi, @caufieldjh. It's a shame that it's not easier to access these. Did you ever get access? I'm also trying to get access to MiPACQ and SHARP (and THYME, too).

Hi @drussellmrichie - not sure about the others, but THYME colon cancer splits are here: https://github.com/stylerw/thymedata

Not sure if you're still interested in this, but for you or anyone else who comes across this, according to an email from Guergana Savova that my PI just received:
"the MiPACQ and SHARP corpora are not available for distribution at this point."
😦😦😦😦😦😦😦😦
I'll post here if I here anything else....

Oh well! Thanks for forwarding the official word, even if it's disappointing.


[SPARK-20311][SQL] Support aliases for table value functions

https://issues.apache.org/jira/browse/SPARK-20311

Fixed in https://github.com/apache/spark/commit/8c67aa7f00e0186abe05a1628faf2232b364a61f


Disabled test_bayesopt_searcher

Issue #, if available:
#734
Description of changes:
Attempt to fix the CI
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Job PR-736-1 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-736/1/index.html


Security: cookies missing secure flag

Stratos UI recently underwent a 3rd party pen testing as part of our system's security inspection. This was the response related to stratos:

Stratos UI
This user interface was what we refer to as a rather "boring" web application test in that there wasvery little of interest discovered during mapping and therefore not very many options to attemptexploitation.  We attempted the usual injection and cross-site scripting (XSS) attacks and lookedinto some potential cross site request forgery (CSRF) vectors.  We verified authentication andlooked at web browser policies such as the CORS policy.The one point of interest in this UI was the fact that a JSESSIONID cookie was being set withoutthe HTTPOnly or Secure flags.  Missing these flags would make the session cookie moresusceptible to hijacking. Given how well understood this mechanism is and the simplicity of theresolution here we did not pursue a PoC for this attack vector.

The JSESSIONID cookie is missing the HTTPOnly and the Secure flag.  This is a session cookie.The VCAP_ID cookie is missing the Secure flag.  Secure Ideas was unable to determine the purpose of this cookie.

@andrewghobrial Thank you.
When was the test done? There was an issue with the consolesession cookie which was resolved - which would have a knock on to JSESSIONID. This was resolved 16 days ago - see https://github.com/cloudfoundry-incubator/stratos/issues?utf8=✓&q=is%3Aissue+is%3Aclosed+cookie.
I have tested locally and can't reproduce - all three cookies are marked as secure and http only.
The VCAP_ID cookie is set by the CF router and should inherit the same secure and http flags as JSESSIONID.


python311Packages.google-cloud-tasks: 2.17.1 -> 2.18.0

Changelog: https://github.com/googleapis/google-cloud-python/blob/google-cloud-tasks-v2.18.0/packages/google-cloud-tasks/CHANGELOG.md

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 365844

x86_64-linux

:white_check_mark: 4 packages built:

python311Packages.google-cloud-tasks
python311Packages.google-cloud-tasks.dist
python312Packages.google-cloud-tasks
python312Packages.google-cloud-tasks.dist


Ajouter filtre booléen de service public : est_service_public

closes #172
This PR adds est_service_public filter to the API.
This is determined by a list of nature juridiques  values which were selected based on their label. It is not an exhaustive list.
I tried using a prefix query to filter on these values, but this query does not accept an or condition on a list of values, it is rather an and by default.
I finally settled on using the same terms query that I use for lists of values of other filters ( like  code_postal and  commune) and used the list of predetermined  natures juridiques values to filter the results when est_service_public=True.
When est_service_public=False I use the remaining list of natures juridiques.

I ended up using @XavierJp's suggestion and adding est_service_public as a field to elastic search's index.


add NativeScript plugin link

Not going to merge this for now since it's an outdated PR. Feel free to create a new PR if you still want to do it.


Set up Transifex.

In the Future we have to allow the user to choose which idiom he want. Then we will use Transifex for the management of translations.

I already done this, we have a English resource, including the js content and Portuguese versions.


Target type detection (file/directory) for relative symlinks is still broken, even on Windows

https://github.com/PowerShell/PowerShell/pull/12797#issuecomment-819889789
Intro & context
Symlink target may be a relative path, which is then resolved by the filesystem as a relative path from parent directory of the symlink. Example:
We have the following 2 files:
    Directory: D:\test

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
la---          2021-04-15    00:41              0 file_link.txt -> .\file.txt
-a---          2021-04-15    00:41              0 file.txt

file_link.txt is a file symlink, which resolves to D:\test\file.txt. It might be created with New-Item -Type SymbolicLink .\file_link.txt -Target .\file.txt.
There's a difference between a symlink to a file and to a directory, and attempting to traverse a directory symlink pointing to a file does not work (and same for trying to read from a file symlink pointing to a directory).
To correctly create the symlink, PowerShell checks whether the target is a file or a directory. Originally, this check was broken for relative target paths, because the process-wide .NET working directory was used to resolve the target (so the above command would check for a target path like C:\Windows\System32\file.txt - that path doesn't exist, so pwsh defaults to creating a file symlink). This was supposedly fixed in #12797.
With this "fix", working directory of PowerShell is now used instead of the .NET working directory. This is however still incorrect, because we don't want to resolve the target relative to CWD, but relative to the symlink itself.
Reproduction
(I'll use D:/test as our testing directory to make it clear when I'm talking about absolute paths)
1)
mkdir D:/test
mkdir D:/test/dir
cd D:/
ni -Type SymbolicLink D:/test/dir_link -Target ./dir

Expected: directory symlink to D:/test/dir, with target ./dir
Got: file symlink to D:/test/dir, with target ./dir
The target type detection code checks the relative path ./dir (D:/dir), which doesn't exist, so the symlink incorrectly defaults to file symlink.
2)
mkdir D:/test
mkdir D:/test/dir
cd D:/test
ni -Type SymbolicLink D:/test/dir_link -Target ./dir

Expected: directory symlink to D:/test/dir, with target ./dir
Got: what I expected
Only difference from previous example is the cd D:/test on line 3. This correctly creates a directory symlink, because the code checks type of target for ./dir (D:/test/dir), which now matches the real target.
3)
mkdir D:/test/subdir
mkdir D:/test/item # <-- directory
ni D:/test/subdir/item # <-- file
cd D:/test
ni -Type SymbolicLink D:/test/subdir/item_link -Target ./item

Expected: file symlink to D:/test/subdir/item, with target ./item
Got: directory symlink D:/test/subdir/item, with target ./item
The the file D:/test/item is used for target check, it's a directory, so a directory symlink is created (but the actual target is D:/test/subdir/item, which is a file).
Proposed fixes
There are 2 possible correct behaviors I see here:

Always resolve symlink target to an absolute path in New-Item. This effectively prevents PowerShell from creating symlinks with relative paths to target.
Allow relative paths, but when checking for target type (file/directory), use the path Join-Path $Path $Target internally, but still write $Target as provided by user (relative) into the symlink itself. This is imo the better solution, allows the user to create symlinks with relative paths, but still correctly detects the type.

Environment data

Name                           Value
----                           -----
PSVersion                      7.2.0-preview.4
PSEdition                      Core
GitCommitId                    7.2.0-preview.4
OS                             Microsoft Windows 10.0.19042
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0ΓÇª}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Thanks for writing this up.
Re behavior 1. (resolving to full paths before creating the symlink):
We do not want this, because defining symlinks that reference their targets via relative paths is an important feature, which enables moving such symlinks - along with their targets - to a different location without breaking things.
Therefore - I agree with your preference - we want behavior 2.
With that in mind, we want:

preserving relative targets as specified in the symlink's actual _definition (potentially after normalizing path separators to the platform-native form).

for the sake of validating the target on creation, an existence check relative to the symlink's directory.

Currently, such checks are not performed, except if the target is specified as a full path AND that path starts with a nonexistent drive specification or a nonexistent UNC share.

Conversely, you may  want to - by way of opt-in - create a symlink to a target that you know not to exist yet.

For technical reasons, on Windows this additionally requires explicitly indicating the target's file-system type (file vs. directory).

See https://github.com/PowerShell/PowerShell/issues/9067#issuecomment-470140963 for a discussion of these issues.

If this gets fixed as suggested, the following is a moot point, but just to prevent additional confusion:
#12797, which, as you state, was conceptually the wrong fix, only partially achieved what it tried to do: a target path such as .\foo is recognized as a relative path and resolved against $PWD, but the equivalent foo (no .\ prefix) is not, and is currently still resolved against the process' current directory ([Environment]::CurrentDirectory); see #15161 for a repro (since closed, because it will implicitly also be resolved by resolving this issue).

The Engine WG spent about 25 minutes discussing about this issue. We agreed that the proposed fix no.2 is reasonable (quoted below), namely a relative path specified for -Target should be resolved using the path to the symbolic link, instead of powershell's current working directory.

Allow relative paths, but when checking for target type (file/directory), use the path Join-Path $Path $Target internally, but still write $Target as provided by user (relative) into the symlink itself. This is imo the better solution, allows the user to create symlinks with relative paths, but still correctly detects the type.

This makes sense because when accessing a file/directory symbolic that is associated with a relative path, such as Get-Content <symlink>, the relative path is resolved using the symlink path. So, we should be consistent in resolving the target relative path when creating a symbolic link with New-Item.
This proposed fix would be a breaking change to PowerShell 7.1. It feels like the right thing to do, but we need to evaluate the impact before proceeding.

Interestingly, our discussion led to another idea when comparing New-Item with mklink, which we want to throw out here for more discussion.
When creating a symbolic using mklink, mklink doesn't check the existence of the specified <target> path. It creates a file symbolic by default, and creates a directory symbolic when /d is specified.
As is shown in the screenshot below, myfolder is an existing directory, but mklink my-link c:\arena\tmp\test-2\myfolder creates a file symbolic, even though the target path is an existing directory.

So, maybe New-Item should work similarly as mklink in creating a symbolic link?
- does not check on the existence of target path
- create file symbolic by default, and add a new switch parameter for creating directory symbolic
This would be a breaking change too, in that if target points to an existing directory, a directory symbolic will be create with the current behavior, but a file symbolic will be created if we change to the mklink behavior.

If it is a bug why we would say "breaking change"? :-)

Junction example:
Pwsh version: 7.1.4
New-Item '.\node_modules\example-project-base\' -ItemType Junction -Value '.\example-project-base\'
# New-Item: Could not find item .\example-project-base\.

PowerShell version: 5.1.19041.1023:
New-Item '.\node_modules\example-project-base\' -ItemType Junction -Value '.\example-project-base\'
#    Directory: C:\example-project\node_modules
# Mode                 LastWriteTime         Length Name
# ----                 -------------         ------ ----
# d----l        2021.08.23     23:27                example-project-base

My god this is a distasterous mess... You'd think doing something as simple as creating a relative symlink to a parent directory/file (....\etc) would be a simple matter but you would be very, very wrong.

My god this is a distasterous mess... You'd think doing something as simple as creating a relative symlink to a parent directory/file (....\etc) in Powershell would be a simple matter but you would be very, very wrong.

This comment is not helpful to the discussion, please refrain from commenting just to vent your (understandable) frustration. Instead, if the issue bothers you, why not either a) contribute something meaningful to the discussion, b) write the code that fixes it?

So, maybe New-Item should work similarly as mklink in creating a symbolic link?

Since no other user seems to have replied yet: I don't think this is an either-or question. Both behaviors might be desirable: When using PowerShell interactively, or if you are expecting POSIX-like semantics, you probably want it to choose the type of symlink automatically based on the target. But in a script or in exceptional cases, you may want to explicitly create a file or directory symlink, e.g. because the target is not guaranteed to exist or may not currently be reachable (network drive).
So, I would propose the following:

New-Item -Type SymbolicLink should be fixed as outlined above.
Two new item types FileSymbolicLink and DirectorySymbolicLink should be introduced to make the equivalent of mklink and mklink /D available in PowerShell. On non-Windows systems, they would be treated as synonyms of SymbolicLink, and on Windows PowerShell would skip the target check and create the specified type of symbolic link.

(In an ideal world, mklink would have a similar interface with an explicit /F switch and target detection when no switch is specified.)

Commenting to prevent the bot from closing an issue that is still relevant.

Dear bot, this is still relevant.

Is there any solution to this? What's the true Powershell equivalent of mklink /D now?

Two new item types FileSymbolicLink and DirectorySymbolicLink should be introduced to make the equivalent of mklink and mklink /D available in PowerShell. On non-Windows systems, they would be treated as synonyms of SymbolicLink, and on Windows, PowerShell would skip the target check and create the specified type of symbolic link.

Ideally, PowerShell should still check the link type, and report errors if it finds the target but the type is wrong.
Also, there seems to be more wrong with the original fix than I found discussed here.  Interactively, the previous fix seems to work as described using the CWD, but in a script, it does not appear to use the CWD to resolve the relative link.  CD/Set-Location/Push-Location do not help the New-Item command correctly interpret the relative path and resolve the target.   As long as the target is relative to the path PowerShell (pwsh.exe) was originally started in at the point the script was executed, then it works fine.


"Make Public" also need second confirmation

Below is not issue or bug. it is just a small suggestion.
When I "Delete" project,

the UI pops the page for second confirmation.

We hope "Make Public" also have the same  second confirmation to avoid incorrect clicking
Thanks.

i think that making a project public and deleting one are a bit different use cases. you can't undo a delete. but you can easily set the project to private again. so when the user clicks properly we don't add another step with a confirmation dialog simplifying that interaction. but when the user clicks the wrong item, we make them click an additional time to change it back to private.

want to close this issue but put on labels so someone could verify. it seems that this is no longer an issue since making a project public is done in the configuration page.

@lweitzman I'll close this.


⚠ Samsung has degraded performance

In 7f18470, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2804 ms

Resolved: Samsung performance has improved in 9734b86.


Convert RDF data into usable JSON-LD

For source data see:
https://github.com/hbz/lobid-resources/issues/851
https://github.com/hbz/lobid-resources/pull/919
https://github.com/hbz/lobid-resources/blob/master/src/test/resources/loc_bib_works_test.nt
For implementation see:
https://github.com/hbz/lobid-gnd/blob/master/app/apps/Convert.java#L111
Thoughts:

Start with playground
Start without context, without frame, most simple conversion to JSON-LD
Attempt usage (maybe with jq?), experience problem
Improve with context, frame

I generated the first version of a JSON-LD context. The result was added with 9ed7808dd5221b414c7db5ef91342a9a8f0d34c5.

Get the Bibframe vocabulary as Turtle: $ rapper -i rdfxml -o turtle http://id.loc.gov/ontologies/bibframe.rdf > bibframe20_20180926.ttl
Convert to JSON-LD context with @niklasl's python script from 2012 (I could not find a better option by now)
Some manual clean ups (using absolute URIs instead of bf prefix etc.)

Pushed using the context and a simple frame. Open data/index.html in a browser for a quick look. See also the README for running the node code (which uses the local context file if you want test local changes). Some things are missing in the context, so far I noticed http://id.loc.gov/ontologies/bflc, http://id.loc.gov/vocabulary/relators, and http://www.w3.org/2000/01/rdf-schema.


Cannot set custom jest.config.{js,ts} even with --config flag in test CLI command

Current Behavior
The test command's --config, -c flags throw a nondescript error when passed any value.
$ yarn run tsdx test --config=./jest.config.js --env=jsdom
...Usage...
argv.config.match is not a function

This also doesn't load the test command in watch mode as the documentation specified.
Expected behavior
Either having a jest.config.{js,ts} in the project root or specifying one via the config flag in your tsdx test should actually be loaded on setup.
Suggested solution(s)
Quickfix:
Just move all your configuration into package.json under the "jest" key.
Long term fix:
I can't seem to find the bug first thing in index.ts, but this is definitely where things are going wrong.
I will update this issue as I study it more!
Additional context
The example bug repo is available here.
Your environment

Software
Version(s)

TSDX
0.7.1

TypeScript
3.5.2

Browser
NA

yarn
1.15.2

Operating System
Ubuntu 16.04

@SeedyROM @jaredpalmer I'm taking a quick look at this and I'm unsure what would be the correct fix.
The easiest is to check if the args already contain a config (here), if it does then don't push the tsdx config.
Or do we merge in the contents of the supplied config with the tsdx config? It would probably need to be a deep merge if you need to add in custom transforms into your jest config such as CSS transforms.

I think a deep merge would be appropriate, but I'm not an expert on this library. So take my opinion with a grain of salt.

Ran into this myself during some testing (and, notably, TSDX itself uses jest --config) and did some further investigation.
This same error, argv.config.match is not a function also occurs with CRA (e.g. https://github.com/wmonk/create-react-app-typescript/issues/396) as it uses the same code for config:
https://github.com/facebook/create-react-app/blob/687c4ebf211ad30238f2d59e063b8171e015bfc7/packages/react-scripts/scripts/test.js#L73-L82
Root cause is actually Jest's very bare programmatic API: https://github.com/facebook/jest/issues/5048
Until Jest's programmatic API becomes better, I do think checking if argv already has a config and merging that in would be optimal. Currently package.json.jest and jest.config.js aren't deep merged right now, just shallow merged.

The same error here. How to fix?

@wzup you can use a jest.config.js in your project root already (was added in #229 above). I wrote up a PR for --config a few days ago in #526 above.


Can you update this to work with Android Studio?

The usage section details how to use the app with Eclipse, more users are migrating to Android studio therefore it will be great if you could update the app so that it can also be used with Android Studio.

You can just import it into Android Studio.  There's a build.gradle.


Perl version with proxy capabilities

An alternative version of the same software written in perl, improved with proxy capabilities.

Looks great, thanks!


Screen Doesn't Scroll Automatically while Selecting Multiple Files

Explain the bug
While trying to select multiple files in details view which has y-overflow, the app doesn't seem to automatically scroll up and or down.
To reproduce

Open Folder which consist of more than 8 items
Select multiple files until top/bottom
See error

Expected behavior
Screen should scroll automatically while users select multiple files.
Screenshots
Expected:
https://user-images.githubusercontent.com/69080584/126172425-2b092ef0-9b64-4460-8bec-38e8e20b1fb2.mp4
Saw:
https://user-images.githubusercontent.com/69080584/126172176-1f2488f6-3fc4-46f4-b8b2-f0d1ae65ce28.mp4
System Information

OS Version: Windows 10 21H1 19043.1110
App version: v<IP_ADDRESS>

Additional comment
Does this problem happen again after restarting the app? Yes

This issue should be resolved with #5463.


pathFollowers need to reference multiple jsons

If your follower list is huge, you'll receive followers_1.json, followers_2.json, etc. I'm a Go noob so my current workaround is manually combining _2.json, _3.json, etc. into _1.json.

Hi @thejasonhsu,
Thank you for reporting that issue!
Can you confirm what is the maximum number of objects in the first json file? In other words - at what point subsequent files are being generated for your followers data?
I can update the code to account for that in the coming week, but feel free to open a pull request if you’re interested.

Np. Won't be submitting PR since I can't fix it via Go haha.

followers_1.json ends on line 130002. Take away [], we have 130k. Each account entry makes up 13 lines. So exactly after 10k entries, followers_1.json ends. The 10001st follower will show up as the 1st entry in followers_2.json.
Don't need to account for this for following.json because it caps at 7.5k.

Hi @thejasonhsu,
I've addressed the issue in the latest commit.
I tested this locally with some dummy data - it should work fine for you too.
Could you please sync the latest changes to your fork and confirm whether it works as expected?

It still only reads the first json.

The application extracts the zip file your feed into it into a folder called instagram_data.
Afterward, it assumes the following structure:
$ tree instagram_data
instagram_data
└── followers_and_following
    ├── followers_1.json
    ├── followers_2.json
    ├── following.json

There can be an infinite number of followers_n.json files in your followers_and_following folder.
Here are the contents of my dummy files:
$ cat instagram_data/followers_and_following/followers_1.json
[
  {
    "title": "",
    "media_list_data": [

    ],
    "string_list_data": [
      {
        "href": "https://www.instagram.com/test1",
        "value": "test1",
        "timestamp":<PHONE_NUMBER>
      }
    ]
  }
]

$ cat instagram_data/followers_and_following/followers_2.json
[
  {
    "title": "",
    "media_list_data": [

    ],
    "string_list_data": [
      {
        "href": "https://www.instagram.com/test2",
        "value": "test2",
        "timestamp":<PHONE_NUMBER>
      }
    ]
  }
]

The application adds all unique elements from the followers_n.json files to a list and the final result is the following:

test1
test2

The number of elements in the JSON arrays shouldn't matter because the application will work in the same way regardless of the array sizes.
Let me know if you think the outcome should be different.
It would be helpful if you can confirm the folder structure is the same for you.

Your assumption and design are correct. I can confirm that my folder structure follows the design.
$ tree instagram_data instagram_data └── followers_and_following     ├── followers_1.json     ├── followers_2.json     ├── following.json
Right now it only reads followers_1.json.

First run before e3e301c - failed. Only followers_1.json was used to compare with following.json. This was expected based on code.
The workaround was manually combining followers_1.json with followers_2.json into just followers_1.json. Second run before e3e301c - success. Expected.
Now that the code should combine infinite followers_#.json into followers_n.json, I restored followers_1.json into followers_1.json and followers_2.json. Latest run after e3e301c - failed. Unexpected.

My assumption is followers_n.json contains only followers_1.json at the moment. Is there a way to read/debug this file during/after workflow?


feat: add accessing kubelet with http option for koordlet

Signed-off-by: Jason Liu<EMAIL_ADDRESS>Ⅰ. Describe what this PR does

Ⅱ. Does this pull request fix one issue?

Ⅲ. Describe how to verify it
Ⅳ. Special notes for reviews
V. Checklist

[x] I have written necessary docs and comments
[x] I have added necessary unit tests and integration tests
[x] All checks passed in make test

/cc @eahydra

/cc @eahydra Please be aware this PR will add/modify command line flag of koordlet.

looking forward

/lgtm
/approve


missing mapping of proposal indexes to proposal ids in Zodiac module contract

Currently there is no way to know which proposal id correspond to the proposal index on Zodiac module contract. This make it complicated to request execution in the UI. We should address this, one idea would be to send the proposal id and space address along with the execution hash from L2 to L1.

Not sure I understand the description there, but proposalIndex can be read from the contract:
https://goerli.etherscan.io/address/0x196f0548e3140d2c7f6532a206dd54fbc12232a4#readContract (proposalIndex).
The issue is that it's impossible to translate starknet's contracts space/proposalId into that index so if we want to execute specific proposal from UI we can't do that because we have no way to finding correct proposalIndex.

Sorry got confused, just updated the issue

Closing this issue, this is not relevant anymore.


copy from CudaView

Sometimes you only need a specific part of a CudaSlice and copying from a CudaView would be very useful (and why can you only slice with a RangeFrom?)

Can you give example of copying in that manner?
I initially did RangeFrom to make it clear that there is no concept of length for CudaViews. Perhaps with what you are thinking about (copying from CudaView) we could add length and then make the range more generic.

if i have a large CudaSlice but only want to copy let's say 100 elements out of it (first 100), then you would have to copy the whole slice and slice the slice you just copied out ...

This is needed for the stack operation in dfdx - notably you allocate enough space for all the tensors you are stacking, then copy values into sub views


feat(modal): prevent focusing on elements out of the modal

Merged with current version of development branch
Squashed original commits

Current coverage is 83.81% (diff: 100%)

Merging #1292 into development will not change coverage

@@           development      #1292   diff @@
=============================================
  Files               53         53
  Lines             1656       1656
  Methods              7          7
  Messages             0          0
  Branches           227        227
=============================================
  Hits              1388       1388
  Misses             189        189
  Partials            79         79

Powered by Codecov. Last update 92e3ba5...48c6501

Does this resolve the issue?  And will this make it into a release in the near future?  Thanks!

merged as a part of another PR


[TRIVIAL] [PDF] Minor adjustments

Code macros straddling the end of a line are problematic.

There's more continuation on the next line happening: https://issues.dlang.org/show_bug.cgi?id=17532


feat(localizations): Add id localization

feat: add locale id (Indonesian language) to locales

[x] add id zod.json to packages/core/locales/id
[x] add id test to tests/integrations
[x] add id zod.json and zod.json to examples/with-next-i18next/public/locales/id
[x] update next-i18next.config.js add "id" to locales (in examples/with-next-i18next)
[x] update examples/with-next-i18next/pages/index.tsx, add option Bahasa Indonesia

@undeadevs Thank you for your contribution! I will merge this PR and release it.
@all-contributors please add @undeadevs for translation and test.


Multiple S40 Thermostats - No Entities on 2nd

Hello,
I'm able to add my S40 thermostats locally by IP Address.  The first one works as expected, showing 4 devices and 15 entities associated with it.
When I add the 2nd S40 thermostat, it shows 4 devices but no entities.  If I delete the first thermostat and reload the integration, the 15 entities for the 2nd thermostat will show up.
I've made sure I'm using unique application id for each thermostat but still cannot get them to both function at the same time.
Any ideas?

Sounds like something is going wrong.  Do the systems have different names? Any warning messages in the home assistant log file when both are enabled?
if not the best thing to do is to get messages logs for both.  Going into the integration config for each system and configure message logging as described below; but give each systems a different log file name - this way the messages from each system will be in their own log file.
https://github.com/PeteRager/lennoxs30#reporting-bugs

I suspect the issue is related to the serial number the S40 is reporting.  On S30 each S30 reports a unique serial number.  The unique number is then used as the unique id in HASS.  From looking at an S40 message log I see it is reporting "123" as its serial number.  My guess right now is that both of your S40s are also reporting "123" as the serial number, so the second set of entities is failing to be added.  I'd expect we'd see HASS complaining about this in the log files.
Either way the message log files will verify this.

The "systems" have different names (upstairs and downstairs).  I went into each individual component and added "down" to furnace, air conditioner, and thermostat.  I am running the 2023.4.0 version.
Below is what the logs show:
Platform lennoxs30 does not generate unique IDs. ID 123_OT already exists - ignoring sensor.downstairs_system_outdoor_temperature
6:20:50 PM – (ERROR) Sensor - message first occurred at 6:20:50 PM and shows up 5 times
Platform lennoxs30 does not generate unique IDs. ID 123_HS already exists - ignoring binary_sensor.downstairs_system_home_state
6:20:50 PM – (ERROR) Binary sensor - message first occurred at 6:20:50 PM and shows up 3 times
Platform lennoxs30 does not generate unique IDs. ID 123_DHMS already exists - ignoring select.downstairs_system_dehumidification_mode
6:20:50 PM – (ERROR) Select - message first occurred at 6:20:50 PM and shows up 2 times
Platform lennoxs30 does not generate unique IDs. ID 123_DOC already exists - ignoring number.downstairs_system_dehumidification_overcooling
6:20:50 PM – (ERROR) Number - message first occurred at 6:20:50 PM and shows up 2 times
Platform lennoxs30 does not generate unique IDs. ID 123_SW_MA already exists - ignoring switch.downstairs_system_manual_away_mode
6:20:50 PM – (ERROR) Switch - message first occurred at 6:20:50 PM and shows up 2 times
Platform lennoxs30 does not generate unique IDs. ID 123_0_T already exists - ignoring climate.downstairs_system_zone_1
6:20:50 PM – (ERROR) Climate

I suspect the issue is related to the serial number the S40 is reporting. On S30 each S30 reports a unique serial number. The unique number is then used as the unique id in HASS. From looking at an S40 message log I see it is reporting "123" as its serial number. My guess right now is that both of your S40s are also reporting "123" as the serial number, so the second set of entities is failing to be added. I'd expect we'd see HASS complaining about this in the log files.
Either way the message log files will verify this.

Looks to be exactly what you thought.  Strangely, 123 isn't in actual serial numbers of the devices at all.

Sounds like we need to find a new unique Id to use for S40s, which should be relatively easy.
The challenge will be finding a way to do it without breaking existing configuration.
I'll get this in the next release.  Take a week or two.

I'm going to be getting a S40 installed next week to replace my
S30+iHarmony zone controller. I complained enough to the installer about
how my $30k three zone system can no longer do dehumidification since
with the zone controller installed, the fully communicating furnace/AC
combo becomes a 'dumb' bang-bang system. I hope the remote sensor averaging
of the S40 will do a better job then the S30+zones.
So i will be curious to see if mine also reports a serial number of 123.
But it won't be a problem because I will only have one.
Nathan Ellsworth
@.***
512-450-8404 cell/text
On Sun, Apr 30, 2023 at 8:37 PM PeteRager @.***> wrote:

Sounds like we need to find a new unique Id to use for S40s, which should
be relatively easy.
The challenge will be finding a way to do it without breaking existing
configuration.
I'll get this in the next release. Take a week or two.
—
Reply to this email directly, view it on GitHub
https://github.com/PeteRager/lennoxs30/issues/235#issuecomment-1529235897,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AILLRKGCR4WFWCNMVA4GOXLXD4HUPANCNFSM6AAAAAAXRGHFLU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

It should just work with 1 system, what I don't know is if I'll be able to have a seamless upgrade in the next release to fix the issue or if I'll need you to first remove the integration, delete the entities and then re-add it.

c

I should also have a new release available next week with the fix, as well as an automatic upgrade to the entities, which could be a simpler path.


Bumped Web Chat to 4.13.0

<EMAIL_ADDRESS>-> @4.13.0
<EMAIL_ADDRESS>-> @4.13.0

Coverage remained the same at 67.819% when pulling a8904ef836f7d3816c7405ee61ca5cef067f5ced on toanzian/wc-bump into c520cc6ed0fd936a9fda7d34d9a74aa395214164 on main.

@tonyanziano  do we want to make the PR into a release branch instead of main?

@srinaath I'll cut the release branch after I merge this and we'll do the version bump there


Performance tests data to the shadow table

Now，Performance testing in distributed systems is a regular process.
Performance tests will generate dirty data.Sharding-jdbc shuld write performance test data to the shadow table.
personally recommend considering providing plugins to support shadow tables in the sql execution layer.

It is a good idea, if somebody interesting and want to do this feature, we can talk about further.

We want to do this through SQL parse and add router, add a tag field in sql, and according to this field, route to shadow database.
Here is a simple design，and we chose the second way.  because ThreadLocal might introduce other problems.

Comments or Suggestions on this design are welcome!

I like the SQL parser way, it can do with sharding-jdbc and sharding-proxy together. How do you think? @yanyzy

Yes, in this way, we only use SQL to judge whether route to the shadow database, and user just needs to write the SQL according to the rules. so both sharding-jdbc and sharding-proxy can implement it. @terrymanu


Microsoft.Maui.Storage updates

Fixes #29048
Thanks @blanthor! 🚀 ... I know this isn't exactly addressing your problem. You should have access to that namespace throughout your app. Check with the product unit if you don't, and please CC: me on that issue so that I can follow along. For now, I'm removing that namespace from the first example, and I'm adding a NOTE on that API to the MAUI part of the tutorial to surface it.

Internal previews

📄 File
🔗 Preview link

aspnetcore/blazor/hybrid/static-files.md
ASP.NET Core Blazor Hybrid static files

Mackinnon ... I've got like a gazillion PRs open right now. I'm going to go ahead and merge this one to try to get the number down ... 😈 merge conflicts 😈 are breathing down my neck right now. Hit me up for changes if you see a problem here, and I'll put in a patch PR for them.

@Rick-Anderson ... FYI ... there seems to be a new build problem these days that I've seen now three times just in the last couple of days. The PR builds but the license check fails. Each time, I need to close and re-open the PR to get the build to succeed. Idk if this has risen to the level of an internal bug report. I can monitor further ... if I see it several more times, I can ping u back that it's a real problem.


Bump byteorder and remove no-op feature

It's automatically detected: https://github.com/BurntSushi/byteorder/commit/5b3ffeeed2d04ec5051336ea2c6e6d36abc94581
With this PR byteorder can be from rustc-workspace-hack.

Oh I see, the feature became a NOP with byteorder 1.3. That makes sense.

@bors r+

:pushpin: Commit 247ac227ef3ce3fe5c1886b6b5c96eee17e4779a has been approved by RalfJung

:hourglass: Testing commit 247ac227ef3ce3fe5c1886b6b5c96eee17e4779a with merge b1d35d5ba2a60f7e877ecc8442fadb618e0d35e3...

:sunny: Test successful - checks-travis, status-appveyor
Approved by: RalfJung
Pushing b1d35d5ba2a60f7e877ecc8442fadb618e0d35e3 to master...


[samples/Calling] Simplified Call Id ref by relocating console log in CallScreen.tsx

What
Simplified use of ref in CallScreen.tsx by relocating Call Id console log in samples/Calling
Why
Simplified code as callid is a ref and won't retrigger a re-render.
https://skype.visualstudio.com/SPOOL/_workitems/edit/2693381/
How Tested
Tested on local chrome browser.
Entered, exited, rejoined, and started a new call session to confirm if id gets logged upon joining a call.
Process & policy checklist

[x] I have updated the project documentation to reflect my changes if necessary.
[x] I have read the CONTRIBUTING documentation.

Out of scope note: it would be useful to have this in the meeting sample also!

I am open to this being out of scope. I think this is helpful when people want to debug why their call quality wasnt great. Having the CallId is always one of the first questions we need in order to determine what happened in the call from the service infrastructure side.

Created a new PR for sample/Meeting
https://github.com/Azure/communication-ui-library/pull/1383


Y24-051 [BUG] Limber can display an incorrect nonexistent pool and incorrect warnings for some stock plates.

Describe the bug
Limber can display an incorrect nonexistent pool and incorrect warnings for some stock plates.
RT Ticket Number
800530
To Reproduce
It is not clear exactly why or when this happens but it seems to be related to stock plates that are not part of Limber pipelines.
The RT contains a number of example plates that have this problem.
Expected behaviour
Limber should be clear that displayed pools will happen in the future.
Limber should be clear that displayed pools have already happened.
Limber should not display pool information on plates that do not have pools or do not have pools scheduled.
Limber should not display incorrect "Libraries are completed" warnings because a plate has completed creation requests.
Limber should fail gracefully and display useful error messages if unexpected conditions or data arise.
Logic for showing next steps button should be consistent with logic showing warnings.
Screenshots
Screenshots are contained in the related RT ticket
Desktop (please complete the following information):
Additional context

Only fixed in 1 view so we need to fix it for other views.

I have updated the acceptance criteria on this story to reflect the fact that the probable intention is to show pools in the future.
Of course, that then raises the question of how to display pooling that has already happened or if we want to.

Update from chat with @StephenHulme .
Existing functionality:

When you load up a labware page in Limber, it runs some logic to figure out what pipeline it's part of, so that it can display the next step in the 'suggested actions' section. (This looks at the purpose, request type and library type and matches that up to the piepline config files)

Potential solution for this story:

Re-using that existing logic, if it cannot figure out what pipeline it's part of, then DON'T display the pooling tab.
That would hopefully solve the problem with 'stock' plates, because stock plates are not normally part of Limber pipelines.

Potential extension - could be a second story:

Extending the above logic, having figured out what pipeline it's part of, it could look down that pipeline to see if any of the descendent labware use the 'PooledTubesBySubmission' labware creator.
If they do, the pooling tab is relevant and should be displayed.
If they don't the pooling tab is irrelevant and should be hidden.
This works on the assumption that the pooling tab uses submissions to show which pools the wells will be part of - and that the 'PooledTubesBySubmission' is the only labware creator that creates pools this way. I think this is correct, but haven't looked at the code to make sure.

Just a note this issue #2110, seems like a similar problem where an incorrect warning is displayed but the button logic allows the plate to continue and is in fact fine.


fix: don't post GitHub comments concurrently from each runner

[ ] Updated Unreleased section in CHANGELOG or it's not notable changes.

Resolves #1911.
Call the reviewdog.RunFromResult() function only once after the results of all the runners are collected.
This prevents the scenario where multiple reviewdog runners list the comments, post their own review comments, and delete each other's comments, that is described in #1911.
I tested this locally on a PR. From what I see the linters still run in parallel, but the comments are posted in one go. I placed log.Println() lines in the GitHub helpers to verify it.
⚠ I don't know Go and did this at the best of my capabilities with the help of ChatGPT. I may have not understood all the implications of this change.

Logs of a run before the fix:

```
chore/reviewdog-experiment* $ ~/git/reviewdog/cmd/reviewdog/reviewdog -guess -reporter=github-pr-review
time=2024-08-30T22:12:34.929+02:00 level=INFO msg="reviewdog: [start]\trunner=ruff check (api)"
time=2024-08-30T22:12:34.932+02:00 level=INFO msg="reviewdog: [start]\trunner=ESLint (backoffice-v2)"
time=2024-08-30T22:12:34.934+02:00 level=INFO msg="reviewdog: [start]\trunner=ESLint (frontend-public)"
time=2024-08-30T22:12:35.841+02:00 level=INFO msg="reviewdog: [finish]\trunner=ruff check (api)\terror=exit status 1"
time=2024-08-30T22:12:40.701+02:00 level=INFO msg="reviewdog: [finish]\trunner=ESLint (frontend-public)\terror=exit status 1"
time=2024-08-30T22:12:41.434+02:00 level=INFO msg="reviewdog: [finish]\trunner=ESLint (backoffice-v2)\terror=exit status 1"
backoffice-v2/src/Logic/network/apiClient.ts:16:5: [ESLint (backoffice-v2)] 'call' is never reassigned. Use 'const' instead  prefer-const
time=2024-08-30T22:12:41.715+02:00 level=INFO msg="reviewdog: listing review comments"
time=2024-08-30T22:12:43.569+02:00 level=INFO msg="reviewdog: created a review comment"
frontend-public/src/Logic/network/common/apiClient.ts:12:7: [ESLint (frontend-public)] 'backend_url' is assigned a value but never used  @typescript-eslint/no-unused-vars
time=2024-08-30T22:12:43.569+02:00 level=INFO msg="reviewdog: listing review comments"
time=2024-08-30T22:12:45.202+02:00 level=INFO msg="reviewdog: created a review comment"
time=2024-08-30T22:12:46.189+02:00 level=INFO msg="reviewdog: outdated comment (id=1739374075) is removed"
api/duster/common/settings.py:3:8: [ruff check (api)] `time` imported but unused
time=2024-08-30T22:12:46.190+02:00 level=INFO msg="reviewdog: listing review comments"
time=2024-08-30T22:12:47.797+02:00 level=INFO msg="reviewdog: created a review comment"
time=2024-08-30T22:12:48.676+02:00 level=INFO msg="reviewdog: outdated comment (id=1739374097) is removed"
```

After the fix:

```
chore/reviewdog-experiment* $ ~/git/reviewdog/cmd/reviewdog/reviewdog -guess -reporter=github-pr-review
time=2024-08-30T22:43:27.210+02:00 level=INFO msg="reviewdog: [start]\trunner=ruff check (api)"
time=2024-08-30T22:43:27.213+02:00 level=INFO msg="reviewdog: [start]\trunner=ESLint (backoffice-v2)"
time=2024-08-30T22:43:27.214+02:00 level=INFO msg="reviewdog: [start]\trunner=ESLint (frontend-public)"
time=2024-08-30T22:43:28.136+02:00 level=INFO msg="reviewdog: [finish]\trunner=ruff check (api)\terror=exit status 1"
time=2024-08-30T22:43:32.233+02:00 level=INFO msg="reviewdog: [finish]\trunner=ESLint (frontend-public)\terror=exit status 1"
time=2024-08-30T22:43:34.520+02:00 level=INFO msg="reviewdog: [finish]\trunner=ESLint (backoffice-v2)\terror=exit status 1"
api/duster/common/settings.py:3:8: [reviewdog] `time` imported but unused
frontend-public/src/Logic/network/common/apiClient.ts:12:7: [reviewdog] 'backend_url' is assigned a value but never used  @typescript-eslint/no-unused-vars
backoffice-v2/src/Logic/network/apiClient.ts:16:5: [reviewdog] 'call' is never reassigned. Use 'const' instead  prefer-const
time=2024-08-30T22:43:34.910+02:00 level=INFO msg="Entering comment.Flush()"
time=2024-08-30T22:43:34.911+02:00 level=INFO msg="Flushing comments:  0"
time=2024-08-30T22:43:34.911+02:00 level=INFO msg="reviewdog: listing review comments"
time=2024-08-30T22:43:35.611+02:00 level=INFO msg="reviewdog: postAsReviewComment entered with comments: 3"
time=2024-08-30T22:43:35.611+02:00 level=INFO msg="Flushing comments:  1"
```

It should be fixed by #1867

Indeed now it works, thanks! All the comments are showing.
However, now every tool shows as a separate review. Wouldn't it be better to have all the comments under the same review thread? Screenshot below.


UpdateCLI generated PR comment is not correct

When UpdateCLI generates a PR, the additional commit details reference to a demo program
 ... he 'Hello World!' tutorial

Oopsie...
My bad, I will correct that. 😳


./config/config > ./config/config.js

Its Just Because Mostly It Causes Error While starting the server but if u dont want to merge this u can! I Just made the PR so that no more errors will be shown for ppl who dont install dependencies properly

did u test this @KewlStatics ?

Ofcourse I Did

Just adding the file extension doesn't fix anything


Add --fail-level option for the CLI and Rake task

This builds on the work started by @mauu-alpha in June of last year by fleshing out the functionality, extending the domain model of a severity a bit, and adding tests.
By enabling users to only fail on violations that are of the "error" severity, we can make it so you can use Haml-Lint in CI to print out style violations that are of lesser importance, but still let the build pass.
Closes #137
Closes #142

Thanks for catching that copy/paste. I cleaned it up (with an example as well!)


Can not use Chrome to debug React Native App?

Error was occurred while I was trying to open the Debug JS Remotely option in my Android emulator.
The follow information was shown in react-native debug app:

I found these error information in my terminal running React packager：

But if i stop Remote JS Debugging, React Native App can run successfully.

@facebook-github-bot no-template


Set Node Version Explicitly

As of a few days ago, Node LTS is version 18.
Since trion/ng-cli:14.2.7 is based on node:lts-slim now Node 18, which is not compatible with ng cli 💣
I'm not sure if you can remove / republish 14.2.7 onto docker hub

@triondevelopment, I see you've updated to 14.2.8 but I think the issue still exists, could you please confirm

Please excuse the late reply.
Anguar 15 now supports Node 18 LTS, so the immediate issue should be solved. In the past we experienced the exactly opposite problem when it was expected to have a newer Node version provided. That is why we switched to using the LTS upstream base image. I don't think that there is a silver bullet to solve this.


Guidance or Support for Microsoft.IdentityModel

Summary
Some of us need to work with multiple claims and/or identities provided by the SessionAuthenticationModule with Forms authentication rather than the vanilla FormsAuthenticationModule.
I've confirmed that the RemoteAppAuthenticationHttpHandler doesn't handle the former as it will appear unauthenticated to it, and it has no visibility into the claims collection.   Having the claims collection is a useful feature.
Motivation and goals
This dovetails into the differences between the Microsoft.IdentityModel and the System.Security.Claims implementations. It would appear that to get multiple claims in ASP.NET web forms with ASP.NET Membership, one has to thread the needle with via SessionAuthenticationModule using Microsoft.IdentityModel.
Perhaps getting the webforms app to use OWIN is the prescribed answer, but this does not appear to be a small matter for systems still using ASP.NET Membership backend.
Given that Blazor Server apps are not well-supported (yet) with the adapters - at least for session interop due to limitations in bridging the gap between HTTPContexts and circuits - I was hoping to add the aspnet session id or other identifier as a claim (userdata) so that I could pull this out of the ClaimsIdentity on the Blazor side to enable a pubsub scenario to share session data by way of Redis and a modified Redis session provider that was cooperative with the scheme.
In scope
I believe that someone could easily write their own RemoteAppAuthenticationHttpHandler, maybe the below code in fact, if the IHttpHandler was DI'ed for the RemoteAppAuthenticationModule.
// Licensed to the .NET Foundation under one or more agreements.
// The .NET Foundation licenses this file to you under the MIT license.

using System.IO;
using System.Linq;
using System.Security.Claims;
using System.Web;

/// <summary>
/// HTTP handler for serving requests to remote authenticaiton endpoint.
/// </summary>
public class CanopyRemoteAppAuthenticationHttpHandler : IHttpHandler
{
    public bool IsReusable => true;

    public void ProcessRequest(HttpContext context)
    {
        if (context is null)
        {
            return;
        }

        // Setting 401 signals to other components (such as OWIN auth handlers) that authentication is required.
        // Those components can make updates, as needed, based on the specific auth process being used (such as
        // changing to a 302 status code or adding WWW-Authenticate or Location headers.
        context.Response.StatusCode = 401;

        if (context.User.Identity != null)
        {
            if ((context.User is Microsoft.IdentityModel.Claims.ClaimsPrincipal) &&
                ((Microsoft.IdentityModel.Claims.ClaimsIdentity)HttpContext.Current.User.Identity).IsAuthenticated)
            {
                var identity = (Microsoft.IdentityModel.Claims.ClaimsIdentity)HttpContext.Current.User.Identity;

                context.Response.StatusCode = 200;
                context.Response.ContentType = "application/octet-stream";

                var claims = identity.Claims.Select(x => new System.Security.Claims.Claim(x.ClaimType, x.Value)).ToList();
                var claimsPrincipal = new ClaimsPrincipal(new System.Security.Claims.ClaimsIdentity(HttpContext.Current.User.Identity, claims));

                using (var writer = new BinaryWriter(context.Response.OutputStream))
                {
                    claimsPrincipal.WriteTo(writer);
                }
            }
            // If a user is logged in (using ASP.NET's usual authentication mechanisms), return that claims principal.
            else if (context.User.Identity is System.Security.Principal.IIdentity
                && context.User.Identity.IsAuthenticated)
            {
                context.Response.StatusCode = 200;
                context.Response.ContentType = "application/octet-stream";
                var claimsPrincipal = context.User as ClaimsPrincipal ?? new ClaimsPrincipal(context.User.Identity);
                using( var writer = new BinaryWriter(context.Response.OutputStream))
                {
                    claimsPrincipal.WriteTo(writer);
                }
            }
        }

        context.ApplicationInstance.CompleteRequest();
    }
}

Out of scope
Multiple identities?
unknowns
I'm hoping that I'm missing something easy and obvious to get claims in the web adapters or to get the web forms app to work with claims in the System.Security.Claims namepace, neither of which seem to work out so far, which seems odd!

I may just revert to passing the session id in a response header and get it to work with standard forms auth.


sql: break docs navigation into DML, DDL, etc.

Our current docs navigation lumps together many different sql statements:

We should consider grouping them in layers based on their types. For example, like this chart:
https://www.geeksforgeeks.org/sql-ddl-dql-dml-dcl-tcl-commands/

@awoods187, this would add too much hierarchy to the sidenav, in my opinion. The overview page already does what you're asking for, however: https://www.cockroachlabs.com/docs/stable/sql-statements.html

Should we close this? cc @ericharmeling

Should we close this? cc @ericharmeling


feat: add tab_scoped prop to get_current_session_info dict

Callers of get_current_session_info may want to check whether the session is tab-scoped or globally scoped.

LGTM thanks!


runtime exception in Regex.regex

The function regex : String -> Regex creates a Elm Regex from a String. If given an invalidly formatted regex string, for example, "0)", it throws a runtime exception.
Perhaps this is expected behavior, since regex returns a Regex instead of a Result _ Regex? So perhaps this is a feature request to alter the return type to return Err _ if the input has bad syntax, or at least give some way to test whether a String is a valid Javascript regular expression before calling the regex function.

Sorry, I just noticed that this will be fixed in Elm 0.19:
https://github.com/elm-lang/core/issues/722

Yep, looking forward to that :)


feat(test) - add status page test for 942170

This PR adds a testcase 942170-4 that only triggers this rule.

Tested: works for me, too.
Merging.


Add emreozcan3320 to Contributors list

Hi  @emreozcan3320, I'm quite elated about your pull request. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a pull request and learned that I merged it?
We’ve recently added social share  to our web app. Could you please go to https://roshanjossey.github.io/first-contributions/#social-share and share your first contribution to open source?
Also, check out projects with easy issues while you’re there.

Hi Roshajossey I'm new to depositoys how can I access my funds. Thank you
On Tue, Mar 6, 2018, 3:26 PM Roshan Jossey<EMAIL_ADDRESS>wrote:

Merged #3232
https://github.com/Roshanjossey/first-contributions/pull/3232.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Roshanjossey/first-contributions/pull/3232#event-1507743804,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AhrVl0DO8eMYkXgDzEWvCooL4NfsAK_7ks5tbxtBgaJpZM4SfnGA
.


Create integration/smoke test for Android & TalkBack

For example, run through some non-trivial interactions in the gallery with semantics enabled and scan the system logs for exceptions specifically emitted through TalkBack. This will require a new addition to the device lab of a current generation Android device running the latest TalkBack. Ideally we could always run on the latest TalkBack version.

This might also be something we can run in Google's internal infrastructure if necessary.

We should definitely do this for the long term, but I am not actually working on this currently


fix: cannot set baseurl to an empty string

Flips the checking of baseUrl definedness to check for explicit undefinedness

Solves both

Not being able to set baseUrl to an empty string (resulting in paths served from the same host - this requires some advanced external routing!)
Not being able to set ACLs on the uploaded files. Now, if params.acl isn't set, the object inherits the bucket's policy, which you can set by adding

{
  "Sid": "AllowPublicRead",
  "Effect": "Allow",
  "Principal": {
    "AWS": "*"
  },
  "Action": "s3:GetObject",
  "Resource": "arn:aws:s3::<bucket>/<prefix>/*"
}

in your AWS console in bucket permissions. For other cloud providers, you'll have to check on your own, but this update allows you to set ACLs on the object directly as long as the uploading user has "s3:PutObjectACL" permissions.
Tested this on strapi v4 with an AWS S3 bucket.


Creating a Custom Model is Broken

Describe the bug
Currently attempting to follow the example google collab document results in an error at step 7, this is due to changes in FlatBuffers that is resulting in a critical error:
 “TensorFlow Lite: export failure: EndVector() missing 1 required positional argument: ‘vectorNumElems’”
Since step 7 does not complete successfully, all subsequent steps fail.
To Reproduce
Steps to reproduce the behavior:

Go to the example doc above
Click on fill in the information for the custom training set from robotflow
Run All
See error

Expected behavior
Run all should run the whole document through, and result in a usable model file, however the execution stops at step 7.
Screenshots

Desktop (please complete the following information):

OS: Windows 11
Browser Firefox, Chrome
Version 109.0.1

turned out to be an issue of flatbuffers v1.12 being forced in export.py of the transfer

Hi, It is recommended to use the latest mod assistant for training
https://github.com/Seeed-Studio/ModelAssistant
https://github.com/Seeed-Studio/sscma-model-zoo

Hello,
I'm going to close this issue, feel free to re-open it if you have any other questions.
[Autocommentary]


Action buttons not getting the correct default accent color

Found on API 10, probably applies elsewhere.
It might be due to attempting to get R.attr.colorAccent out of the wrong context.

Nevermind


What does this mean Thread Starvation or clock leap detected

Hi,
I am trying out HikariCP pooling.  I am using Tomcat localhost and my config is direct copy from the docs
pom.xml
<dependency>
        <groupId>mysql</groupId>
        <artifactId>mysql-connector-java</artifactId>
        <version>5.1.39</version>
    </dependency>
    <dependency>
        <groupId>com.zaxxer</groupId>
        <artifactId>HikariCP</artifactId>
        <version>2.4.7</version>
    </dependency>
    <dependency>
        <groupId>org.hibernate</groupId>
        <artifactId>hibernate-core</artifactId>
        <version>4.3.11.Final</version>
    </dependency>

applicationContext.xml
<bean id="hikariConfig" class="com.zaxxer.hikari.HikariConfig">
   <property name="poolName" value="springHikariCP" />
            <property name="connectionTestQuery" value="SELECT 1" />
            <property name="dataSourceClassName"
                value="com.mysql.jdbc.jdbc2.optional.MysqlDataSource" />
            <property name="dataSourceProperties">
                <props>
                    <prop key="url">jdbc:mysql://localhost:3306/unicare_test</prop>
                    <prop key="user">xxxxx</prop>
                    <prop key="password">xxxxx</prop>
                </props>
            </property>
        </bean>
        <bean id="dataSource" class="com.zaxxer.hikari.HikariDataSource"
            destroy-method="close">
            <constructor-arg ref="hikariConfig" />
        </bean>
<bean id="sessionFactory"
            class="org.springframework.orm.hibernate4.LocalSessionFactoryBean">
            <property name="dataSource" ref="dataSource"></property>
            <property name="hibernateProperties">
                <props>
                    <prop key="hibernate.dialect">org.hibernate.dialect.MySQLDialect</prop>
                    <prop key="hibernate.connection.useUnicode">true</prop>
                    <prop key="hibernate.connection.characterEncoding">UTF-8</prop>
                    <prop key="hibernate.connection.charSet">UTF-8</prop>
                    <prop key="hibernate.show_sql">true</prop>
                    <prop key="org.hibernate.jdbc">TRACE</prop>
                </props>
            </property>
            <property name="packagesToScan">
                <list>
                    <value>com.app.books</value>
                </list>
            </property>
        </bean>

WARN - 1h35m13s114ms - Thread starvation or clock leap detected (housekeeper delta=springHikariCP).
What does this mean and how to fix?

Nothing to worry about.  Looks like you are running on a laptop, and it went to sleep.  Nothing to fix configuration-wise.

I also noticed this error several times on server systems which definitely didn't went to sleep:
2m36s172ms20?s75ns - Thread starvation or clock leap detected (housekeeper delta=HikariPool - default).

2m36s starvation is significant.  If the system did not enter sleep, and you are sure of that, there are only two possibilities that I can see.
One, this is a virtual machine that is configured to synchronize its clock from the host.  In which case, the solution is to run ntpd (Linux) or w32time (windows) in the VM.
Two, there was actually a 2+ minute starvation event.  In which case, you need to monitor the CPU and figure out what is creating the load.

Today I saw this on a developer windows machine (no VM).
Not sure if this is related at all, but it happened during the execution of a very long running Statement.
After 50 minutes of executing a statement, the above warning appeared.
The application itself does not cause any load, it had been waiting for the Statement to return.
Although I cannot rule it out completely, it's very unlikely that the machine was "CPU-stalled" for more than 2 minutes.

I also have the same problem. After running process for a while I am getting this
2017-06-06 17:39:34.170  WARN 2152 --- [l-1 housekeeper] com.zaxxer.hikari.pool.HikariPool        : HikariPool-1 - Thread starvation or clock leap detected (housekeeper delta=54s566ms151µs86ns).

Virtual machine?  Laptop?

It's in the laptop. Reason I put in here is as patric-r said. I am trying to index my relational database with elasticsearch, since it takes sometime around 50min mark I start getting this warning. Application services stops responding! You think it's problem due to my configuration Brett! Till 40 -4 5 min Application runs perfectly fine.

The CPU is going into deep sleep mode.  Turn off power saving/sleep during the operation.

I also have the same problem. After running process for a while I am getting this payprod-core-hikari-pool - Thread starvation or clock leap detected (housekeeper delta=3h36m56s61ms486µs9ns). So I can't get a Connection, it throws  * org.springframework.jdbc.CannotGetJdbcConnectionException: Could not get JDBC Connection; nested exception is java.sql.SQLTransientConnectionException: payprod-core-hikari-pool - Connection is not available, request timed out after 935119ms*.   How should I solve it?

Hi.. You must be doing a

3h36m56s61ms?!  Your computer must be going into sleep mode.  There is no way a thread in a normally running system could be starved for so long.  Either that or something is messing with the system clock (unlikely).

I found this issue running Tomcat servers on a virtual Kubernetes cluster. I was getting status 80 connection refused from all the endpoints, and intermittently the services would briefly work. This was the only thing out of the ordinary I could find in the logs.
My theory is that the machine did not have enough resources for the thread because when I did not start all of the services in the cluster I had no issue. Therefore, it may be a lack of resource issue.

I concur with @Coroecram.  We just encountered these messages with java.lang.OutOfMemoryError.

@Coroecram what is the magnitude of your reported delta, and did you find any cause or solution? We're seeing the same issue in a similar setup (45s delta).

I also encountered the same warning, but it has no effect on my scheduled task. The only problem is that I found that my scheduled task was retriggered during this time period.
2020-04-23 12:58:55.903  WARN 3228 --- [HikariPool-1 housekeeper] com.zaxxer.hikari.pool.HikariPool        : HikariPool-1 - Thread starvation or clock leap detected (housekeeper delta=8m44s242ms).

In my case I got this error Initially and then heap overflow.  I increase the Heap and Stack size and it got away. But in my case, I run a class that overflow the stock heap size.

@milosonator  Sorry, this has been so long ago I really don't know the exact conditions.

2020-06-23 19:12:00,690 DEBUG (PoolBase.java:147)[HikariPool-1 housekeeper]- HikariPool-1 - Closing connection com.cloudera.impala.impala.jdbc41.ImpalaJDBC41Connection@3a3f4750 failed java.sql.SQLNonTransientConnectionException: [Cloudera][JDBC](10060) Connection has been closed. 	at com.cloudera.impala.exceptions.ExceptionConverter.toSQLException(Unknown Source) 	at com.cloudera.impala.jdbc.common.SConnection.closeConnection(Unknown Source) 	at com.cloudera.impala.jdbc.common.SConnection.abortInternal(Unknown Source) 	at com.cloudera.impala.jdbc.common.SConnection.close(Unknown Source) 	at com.zaxxer.hikari.pool.PoolBase.quietlyCloseConnection(PoolBase.java:143) 	at com.zaxxer.hikari.pool.HikariPool.lambda$closeConnection$1(HikariPool.java:451) 	at java.util.concurrent.ThreadPoolExecutor$CallerRunsPolicy.rejectedExecution(ThreadPoolExecutor.java:2038) 	at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:830) 	at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1379) 	at com.zaxxer.hikari.pool.HikariPool.closeConnection(HikariPool.java:450) 	at com.zaxxer.hikari.pool.HikariPool.softEvictConnection(HikariPool.java:615) 	at com.zaxxer.hikari.pool.HikariPool.lambda$createPoolEntry$2(HikariPool.java:486) 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 	at java.util.concurrent.FutureTask.run(FutureTask.java:266) 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 	at java.lang.Thread.run(Thread.java:748) 2020-06-23 19:12:00,691 DEBUG (HikariPool.java:517)[HikariPool-1 housekeeper]- HikariPool-1 - Fill pool skipped, pool is at sufficient level. 2020-06-23 19:12:00,691 WARN (HikariPool.java:787)[HikariPool-1 housekeeper]- HikariPool-1 - Thread starvation or clock leap detected (housekeeper delta=17m1s952ms571µs377ns). 2020-06-23 19:12:00,692 DEBUG (HikariPool.java:421)[HikariPool-1 housekeeper]- HikariPool-1 - Pool stats (total=4, active=0, idle=4, waiting=0) 2020-06-23 19:12:00,692 DEBUG (HikariPool.java:517)[HikariPool-1 housekeeper]- HikariPool-1 - Fill pool skipped, pool is at sufficient level. 2020-06-23 19:12:00,692 DEBUG (PoolBase.java:134)[HikariPool-1 housekeeper]- HikariPool-1 - Closing connection com.cloudera.impala.impala.jdbc41.ImpalaJDBC41Connection@4309df21: (connection has passed maxLifetime) 2020-06-23 19:12:01,025 DEBUG (HikariPool.java:728)[HikariPool-1 connection adder]- HikariPool-1 - Added connection com.cloudera.impala.impala.jdbc41.ImpalaJDBC41Connection@34b395a2 2020-06-23 19:12:01,459 DEBUG (HikariPool.java:728)[HikariPool-1 connection adder]- HikariPool-1 - Added connection com.cloudera.impala.impala.jdbc41.ImpalaJDBC41Connection@758e9f99 2020-06-23 19:16:11,058 DEBUG (PoolBase.java:147)[HikariPool-1 connection closer]- HikariPool-1 - Closing connection com.cloudera.impala.impala.jdbc41.ImpalaJDBC41Connection@3f685b9f failed java.sql.SQLNonTransientConnectionException: [Cloudera][JDBC](10060) Connection has been closed. 	at com.cloudera.impala.exceptions.ExceptionConverter.toSQLException(Unknown Source) 	at com.cloudera.impala.jdbc.common.SConnection.closeConnection(Unknown Source) 	at com.cloudera.impala.jdbc.common.SConnection.abortInternal(Unknown Source) 	at com.cloudera.impala.jdbc.common.SConnection.close(Unknown Source) 	at com.zaxxer.hikari.pool.PoolBase.quietlyCloseConnection(PoolBase.java:143) 	at com.zaxxer.hikari.pool.HikariPool.lambda$closeConnection$1(HikariPool.java:451) 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 	at java.lang.Thread.run(Thread.java:748) 2020-06-23 19:16:11,058 DEBUG (HikariPool.java:517)[HikariPool-1 connection closer]- HikariPool-1 - Fill pool skipped, pool is at sufficient level. 2020-06-23 19:16:11,058 DEBUG (PoolBase.java:134)[HikariPool-1 connection closer]- HikariPool-1 - Closing connection com.cloudera.impala.impala.jdbc41.ImpalaJDBC41Connection@57502b63: (connection has passed maxLifetime) 2020-06-23 19:28:00,690 DEBUG (PoolBase.java:147)[HikariPool-1 housekeeper]- HikariPool-1 - Closing connection com.cloudera.impala.impala.jdbc41.ImpalaJDBC41Connection@4309df21 failed java.sql.SQLNonTransientConnectionException: [Cloudera][JDBC](10060) Connection has been closed. 	at com.cloudera.impala.exceptions.ExceptionConverter.toSQLException(Unknown Source) 	at com.cloudera.impala.jdbc.common.SConnection.closeConnection(Unknown Source) 	at com.cloudera.impala.jdbc.common.SConnection.abortInternal(Unknown Source) 	at com.cloudera.impala.jdbc.common.SConnection.close(Unknown Source) 	at com.zaxxer.hikari.pool.PoolBase.quietlyCloseConnection(PoolBase.java:143) 	at com.zaxxer.hikari.pool.HikariPool.lambda$closeConnection$1(HikariPool.java:451) 	at java.util.concurrent.ThreadPoolExecutor$CallerRunsPolicy.rejectedExecution(ThreadPoolExecutor.java:2038) 	at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:830) 	at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1379) 	at com.zaxxer.hikari.pool.HikariPool.closeConnection(HikariPool.java:450) 	at com.zaxxer.hikari.pool.HikariPool.softEvictConnection(HikariPool.java:615) 	at com.zaxxer.hikari.pool.HikariPool.lambda$createPoolEntry$2(HikariPool.java:486) 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 	at java.util.concurrent.FutureTask.run(FutureTask.java:266) 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 	at java.lang.Thread.run(Thread.java:748) 2020-06-23 19:28:00,691 DEBUG (HikariPool.java:517)[HikariPool-1 housekeeper]- HikariPool-1 - Fill pool skipped, pool is at sufficient level. 2020-06-23 19:28:00,693 WARN (HikariPool.java:787)[HikariPool-1 housekeeper]- HikariPool-1 - Thread starvation or clock leap detected (housekeeper delta=16m1ms667µs120ns). 2020-06-23 19:28:00,693 DEBUG (HikariPool.java:421)[HikariPool-1 housekeeper]- HikariPool-1 - Pool stats (total=5, active=0, idle=5, waiting=0) 2020-06-23 19:28:00,694 DEBUG (HikariPool.java:517)[HikariPool-1 housekeeper]- HikariPool-1 - Fill pool skipped, pool is at sufficient level. 2020-06-23 19:28:00,694 DEBUG (PoolBase.java:134)[HikariPool-1 housekeeper]- HikariPool-1 - Closing connection com.cloudera.impala.impala.jdbc41.ImpalaJDBC41Connection@2625637d: (connection has passed maxLifetime) 2020-06-23 19:28:01,108 DEBUG (HikariPool.java:728)[HikariPool-1 connection adder]- HikariPool-1 - Added connection com.cloudera.impala.impala.jdbc41.ImpalaJDBC41Connection@1db905ff 2020-06-23 19:31:58,770 DEBUG (PoolBase.java:147)[HikariPool-1 connection closer]- HikariPool-1 - Closing connection com.cloudera.impala.impala.jdbc41.ImpalaJDBC41Connection@57502b63 failed java.sql.SQLNonTransientConnectionException: [Cloudera][JDBC](10060) Connection has been closed. 	at com.cloudera.impala.exceptions.ExceptionConverter.toSQLException(Unknown Source) 	at com.cloudera.impala.jdbc.common.SConnection.closeConnection(Unknown Source) 	at com.cloudera.impala.jdbc.common.SConnection.abortInternal(Unknown Source) 	at com.cloudera.impala.jdbc.common.SConnection.close(Unknown Source) 	at com.zaxxer.hikari.pool.PoolBase.quietlyCloseConnection(PoolBase.java:143) 	at com.zaxxer.hikari.pool.HikariPool.lambda$closeConnection$1(HikariPool.java:451) 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 	at java.lang.Thread.run(Thread.java:748) 2020-06-23 19:31:58,772 DEBUG (PoolBase.java:134)[HikariPool-1 connection closer]- HikariPool-1 - Closing connection com.cloudera.impala.impala.jdbc41.ImpalaJDBC41Connection@166d2158: (connection has passed maxLifetime) 2020-06-23 19:31:59,210 DEBUG (HikariPool.java:728)[HikariPool-1 connection adder]- HikariPool-1 - Added connection com.cloudera.impala.impala.jdbc41.ImpalaJDBC41Connection@1387dfb7 2020-06-23 19:31:59,210 DEBUG (HikariPool.java:421)[HikariPool-1 connection adder]- HikariPool-1 - After adding stats (total=5, active=0, idle=5, waiting=0) 2020-06-23 19:43:48,402 DEBUG (PoolBase.java:147)[HikariPool-1 housekeeper]- HikariPool-1 - Closing connection com.cloudera.impala.impala.jdbc41.ImpalaJDBC41Connection@2625637d failed java.sql.SQLNonTransientConnectionException: [Cloudera][JDBC](10060) Connection has been closed. 	at com.cloudera.impala.exceptions.ExceptionConverter.toSQLException(Unknown Source) 	at com.cloudera.impala.jdbc.common.SConnection.closeConnection(Unknown Source) 	at com.cloudera.impala.jdbc.common.SConnection.abortInternal(Unknown Source) 	at com.cloudera.impala.jdbc.common.SConnection.close(Unknown Source) 	at com.zaxxer.hikari.pool.PoolBase.quietlyCloseConnection(PoolBase.java:143) 	at com.zaxxer.hikari.pool.HikariPool.lambda$closeConnection$1(HikariPool.java:451) 	at java.util.concurrent.ThreadPoolExecutor$CallerRunsPolicy.rejectedExecution(ThreadPoolExecutor.java:2038) 	at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:830) 	at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1379) 	at com.zaxxer.hikari.pool.HikariPool.closeConnection(HikariPool.java:450) 	at com.zaxxer.hikari.pool.HikariPool.softEvictConnection(HikariPool.java:615) 	at com.zaxxer.hikari.pool.HikariPool.lambda$createPoolEntry$2(HikariPool.java:486) 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 	at java.util.concurrent.FutureTask.run(FutureTask.java:266) 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 	at java.lang.Thread.run(Thread.java:748) 2020-06-23 19:43:48,403 DEBUG (HikariPool.java:517)[HikariPool-1 housekeeper]- HikariPool-1 - Fill pool skipped, pool is at sufficient level. 2020-06-23 19:43:48,403 WARN (HikariPool.java:787)[HikariPool-1 housekeeper]- HikariPool-1 - Thread starvation or clock leap detected (housekeeper delta=15m47s710ms139µs13ns). 2020-06-23 19:43:48,404 DEBUG (HikariPool.java:421)[HikariPool-1 housekeeper]- HikariPool-1 - Pool stats (total=4, active=0, idle=4, waiting=0) 2020-06-23 19:43:48,404 DEBUG (HikariPool.java:517)[HikariPool-1 housekeeper]- HikariPool-1 - Fill pool skipped, pool is at sufficient level. 2020-06-23 19:43:48,404 DEBUG (PoolBase.java:134)[HikariPool-1 housekeeper]- HikariPool-1 - Closing connection com.cloudera.impala.impala.jdbc41.ImpalaJDBC41Connection@34b395a2: (connection has passed maxLifetime) 2020-06-23 19:43:49,069 DEBUG (HikariPool.java:728)[HikariPool-1 connection adder]- HikariPool-1 - Added connection com.cloudera.impala.impala.jdbc41.ImpalaJDBC41Connection@273fe02c 2020-06-23 19:43:49,569 DEBUG (HikariPool.java:728)[HikariPool-1 connection adder]- HikariPool-1 - Added connection com.cloudera.impala.impala.jdbc41.ImpalaJDBC41Connection@6602ea17 2020-06-23 19:47:50,578 DEBUG (PoolBase.java:147)[HikariPool-1 connection closer]- HikariPool-1 - Closing connection com.cloudera.impala.impala.jdbc41.ImpalaJDBC41Connection@166d2158 failed java.sql.SQLNonTransientConnectionException: [Cloudera][JDBC](10060) Connection has been closed. 	at com.cloudera.impala.exceptions.ExceptionConverter.toSQLException(Unknown Source) 	at com.cloudera.impala.jdbc.common.SConnection.closeConnection(Unknown Source) 	at com.cloudera.impala.jdbc.common.SConnection.abortInternal(Unknown Source) 	at com.cloudera.impala.jdbc.common.SConnection.close(Unknown Source) 	at com.zaxxer.hikari.pool.PoolBase.quietlyCloseConnection(PoolBase.java:143) 	at com.zaxxer.hikari.pool.HikariPool.lambda$closeConnection$1(HikariPool.java:451) 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 	at java.lang.Thread.run(Thread.java:748) 2020-06-23 19:47:50,579 DEBUG (HikariPool.java:517)[HikariPool-1 connection closer]- HikariPool-1 - Fill pool skipped, pool is at sufficient level. 2020-06-23 19:47:50,579 DEBUG (PoolBase.java:134)[HikariPool-1 connection closer]- HikariPool-1 - Closing connection com.cloudera.impala.impala.jdbc41.ImpalaJDBC41Connection@7af13fae: (connection has passed maxLifetime)
closeConnect time too long can also cause "Thread starvation"

Having the same issue in an AWS ECS container. Couldn't be due to sleep. Previously the CPU resources were highly utilized(90-100%). Even after providing enough resources, it gives the same error.
It would be really great if someone can shed some light on this.

The number one cause of this issue is excessive garbage collection.  If you are seeing starvation logs indicating delays of more than a few tens of seconds it is unlikely to be caused by excessive CPU -- though that is still a possibility.
I highly recommend that you enable GC (garbage collection) logging.  GC logging will show garbage collection times as well has memory statistics such has how much memory was available before and after the GC.  When the memory gets extremely low in the JVM, the JVM will spend all of its time in GC; pausing application threads as it does so.
See this page: https://www.baeldung.com/java-verbose-gc
(Note: the example JVM arguments on that page use the -XX:+UseSerialGC flag, do not use this flag, it is merely in the blog for demonstration purposes)
If you are running on Java 11 or greater on Linux then I strongly recommend looking into the new ZGC collector:
https://www.baeldung.com/jvm-zgc-garbage-collector
(enabled by the -XX:+UnlockExperimentalVMOptions -XX:+UseZGC flags)
But, I recommend doing so after fulling investing your current GC configuration with the logging referenced above.


The video showcase doesn't have any sound turned on

It does, its just real quiet
I don't care enough to fix it