Upgrade CodeQL v3.25.1 -> v3.27.5

This PR contains the following updates:

Package
Type
Update
Change

github/codeql-action
action
minor
v3.25.1 -> v3.27.5

Release Notes

github/codeql-action (github/codeql-action)
v3.27.5
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.
3.27.5 - 19 Nov 2024
No user facing changes.
See the full CHANGELOG.md for more information.
v3.27.4
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.
3.27.4 - 14 Nov 2024
No user facing changes.
See the full CHANGELOG.md for more information.
v3.27.3
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.
3.27.3 - 12 Nov 2024
No user facing changes.
See the full CHANGELOG.md for more information.
v3.27.2
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.
3.27.2 - 12 Nov 2024

Fixed an issue where setting up the CodeQL tools would sometimes fail with the message "Invalid value 'undefined' for header 'authorization'". #2590

See the full CHANGELOG.md for more information.
v3.27.1
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.
3.27.1 - 08 Nov 2024

The CodeQL Action now downloads bundles compressed using Zstandard on GitHub Enterprise Server when using Linux or macOS runners. This speeds up the installation of the CodeQL tools. This feature is already available to GitHub.com users. #2573
Update default CodeQL bundle version to 2.19.3. #2576

See the full CHANGELOG.md for more information.
v3.27.0
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.
3.27.0 - 22 Oct 2024

Bump the minimum CodeQL bundle version to 2.14.6. #2549
Fix an issue where the upload-sarif Action would fail with "upload-sarif post-action step failed: Input required and not supplied: token" when called in a composite Action that had a different set of inputs to the ones expected by the upload-sarif Action. #2557
Update default CodeQL bundle version to 2.19.2. #2552

See the full CHANGELOG.md for more information.
v3.26.13
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.
3.26.13 - 14 Oct 2024
No user facing changes.
See the full CHANGELOG.md for more information.
v3.26.12
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.
3.26.12 - 07 Oct 2024

Upcoming breaking change: Add a deprecation warning for customers using CodeQL version 2.14.5 and earlier. These versions of CodeQL were discontinued on 24 September 2024 alongside GitHub Enterprise Server 3.10, and will be unsupported by CodeQL Action versions 3.27.0 and later and versions 2.27.0 and later. #2520

If you are using one of these versions, please update to CodeQL CLI version 2.14.6 or later. For instance, if you have specified a custom version of the CLI using the 'tools' input to the 'init' Action, you can remove this input to use the default version.

Alternatively, if you want to continue using a version of the CodeQL CLI between 2.13.5 and 2.14.5, you can replace github/codeql-action/*@v3 by github/codeql-action/*@v3.26.11 and github/codeql-action/*@v2 by github/codeql-action/*@v2.26.11 in your code scanning workflow to ensure you continue using this version of the CodeQL Action.

See the full CHANGELOG.md for more information.
v3.26.11
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.
3.26.11 - 03 Oct 2024

Upcoming breaking change: Add support for using actions/download-artifact@v4 to programmatically consume CodeQL Action debug artifacts.
Starting November 30, 2024, GitHub.com customers will no longer be able to use actions/download-artifact@v3. Therefore, to avoid breakage, customers who programmatically download the CodeQL Action debug artifacts should set the CODEQL_ACTION_ARTIFACT_V4_UPGRADE environment variable to true and bump actions/download-artifact@v3 to actions/download-artifact@v4 in their workflows. The CodeQL Action will enable this behavior by default in early November and workflows that have not yet bumped to actions/download-artifact@v3 to actions/download-artifact@v4 will begin failing then.
This change is currently unavailable for GitHub Enterprise Server customers, as actions/upload-artifact@v4 and actions/download-artifact@v4 are not yet compatible with GHES.

See the full CHANGELOG.md for more information.
v3.26.10
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.
3.26.10 - 30 Sep 2024

We are rolling out a feature in September/October 2024 that sets up CodeQL using a bundle compressed with Zstandard. Our aim is to improve the performance of setting up CodeQL. #2502

See the full CHANGELOG.md for more information.
v3.26.9
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.
3.26.9 - 24 Sep 2024
No user facing changes.
See the full CHANGELOG.md for more information.
v3.26.8
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.
3.26.8 - 19 Sep 2024

Update default CodeQL bundle version to 2.19.0. #2483

See the full CHANGELOG.md for more information.
v3.26.7
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.
3.26.7 - 13 Sep 2024

Update default CodeQL bundle version to 2.18.4. #2471

See the full CHANGELOG.md for more information.
v3.26.6
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.
3.26.6 - 29 Aug 2024

Update default CodeQL bundle version to 2.18.3. #2449

See the full CHANGELOG.md for more information.
v3.26.5
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.
3.26.5 - 23 Aug 2024

Fix an issue where the csrutil system call used for telemetry would fail on MacOS ARM machines with System Integrity Protection disabled. #2441

See the full CHANGELOG.md for more information.
v3.26.4
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.
3.26.4 - 21 Aug 2024

Deprecation: The add-snippets input on the analyze Action is deprecated and will be removed in the first release in August 2025. #2436
Fix an issue where the disk usage system call used for telemetry would fail on MacOS ARM machines with System Integrity Protection disabled, and then surface a warning. The system call is now disabled for these machines. #2434

See the full CHANGELOG.md for more information.
v3.26.3
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.
3.26.3 - 19 Aug 2024

Fix an issue where the CodeQL Action could not write diagnostic messages on Windows. This issue did not impact analysis quality. #2430

See the full CHANGELOG.md for more information.
v3.26.2
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.
3.26.2 - 14 Aug 2024

Update default CodeQL bundle version to 2.18.2. #2417

See the full CHANGELOG.md for more information.
v3.26.1
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.
3.26.1 - 13 Aug 2024
No user facing changes.
See the full CHANGELOG.md for more information.
v3.26.0
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.
3.26.0 - 06 Aug 2024

Deprecation: Swift analysis on Ubuntu runner images is no longer supported. Please migrate to a macOS runner if this affects you. #2403
Bump the minimum CodeQL bundle version to 2.13.5. #2408

See the full CHANGELOG.md for more information.
v3.25.15
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.
3.25.15 - 26 Jul 2024

Update default CodeQL bundle version to 2.18.1. #2385

See the full CHANGELOG.md for more information.
v3.25.14
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.
3.25.14 - 25 Jul 2024

Experimental: add a new start-proxy action which starts the same HTTP proxy as used by github/dependabot-action. Do not use this in production as it is part of an internal experiment and subject to change at any time.

See the full CHANGELOG.md for more information.
v3.25.13
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.
3.25.13 - 19 Jul 2024

Add codeql-version to outputs. #2368
Add a deprecation warning for customers using CodeQL version 2.13.4 and earlier. These versions of CodeQL were discontinued on 9 July 2024 alongside GitHub Enterprise Server 3.9, and will be unsupported by CodeQL Action versions 3.26.0 and later and versions 2.26.0 and later. #2375

If you are using one of these versions, please update to CodeQL CLI version 2.13.5 or later. For instance, if you have specified a custom version of the CLI using the 'tools' input to the 'init' Action, you can remove this input to use the default version.
Alternatively, if you want to continue using a version of the CodeQL CLI between 2.12.6 and 2.13.4, you can replace github/codeql-action/*@v3 by github/codeql-action/*@v3.25.13 and github/codeql-action/*@v2 by github/codeql-action/*@v2.25.13 in your code scanning workflow to ensure you continue using this version of the CodeQL Action.

See the full CHANGELOG.md for more information.
v3.25.12
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.
3.25.12 - 12 Jul 2024

Improve the reliability and performance of analyzing code when analyzing a compiled language with the autobuild build mode on GitHub Enterprise Server. This feature is already available to GitHub.com users. #2353
Update default CodeQL bundle version to 2.18.0. #2364

See the full CHANGELOG.md for more information.
v3.25.11
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.
3.25.11 - 28 Jun 2024

Avoid failing the workflow run if there is an error while uploading debug artifacts. #2349
Update default CodeQL bundle version to 2.17.6. #2352

See the full CHANGELOG.md for more information.
v3.25.10
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.
3.25.10 - 13 Jun 2024

Update default CodeQL bundle version to 2.17.5. #2327

See the full CHANGELOG.md for more information.
v3.25.9
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.
3.25.9 - 12 Jun 2024

Avoid failing database creation if the database folder already exists and contains some unexpected files. Requires CodeQL 2.18.0 or higher. #2330
The init Action will attempt to clean up the database cluster directory before creating a new database and at the end of the job. This will help to avoid issues where the database cluster directory is left in an inconsistent state. #2332

See the full CHANGELOG.md for more information.
v3.25.8
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.
3.25.8 - 04 Jun 2024

Update default CodeQL bundle version to 2.17.4. #2321

See the full CHANGELOG.md for more information.
v3.25.7
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.
3.25.7 - 31 May 2024

We are rolling out a feature in May/June 2024 that will reduce the Actions cache usage of the Action by keeping only the newest TRAP cache for each language. #2306

See the full CHANGELOG.md for more information.
v3.25.6
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.
3.25.6 - 20 May 2024

Update default CodeQL bundle version to 2.17.3. #2295

See the full CHANGELOG.md for more information.
v3.25.5
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.
3.25.5 - 13 May 2024

Add a compatibility matrix of supported CodeQL Action, CodeQL CLI, and GitHub Enterprise Server versions to the README.md. #2273
Avoid printing out a warning for a missing on.push trigger when the CodeQL Action is triggered via a workflow_call event. #2274

See the full CHANGELOG.md for more information.
v3.25.4
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.
3.25.4 - 08 May 2024

Update default CodeQL bundle version to 2.17.2. #2270

See the full CHANGELOG.md for more information.
v3.25.3
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.
3.25.3 - 25 Apr 2024

Update default CodeQL bundle version to 2.17.1. #2247
Workflows running on macos-latest using CodeQL CLI versions before v2.15.1 will need to either upgrade their CLI version to v2.15.1 or newer, or change the platform to an Intel MacOS runner, such as macos-12. ARM machines with SIP disabled, including the newest macos-latest image, are unsupported for CLI versions before 2.15.1. #2261

See the full CHANGELOG.md for more information.
v3.25.2
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between v2 and v3 of the CodeQL Action is the node version they support, with v3 running on node 20 while we continue to release v2 to support running on node 16. For example 3.22.11 was the first v3 release and is functionally identical to 2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.
3.25.2 - 22 Apr 2024
No user facing changes.
See the full CHANGELOG.md for more information.

[ ] If you want to rebase/retry this PR, check this box

Suggested commit message:
Upgrade CodeQL v3.25.1 -> v3.27.5

See:
- https://github.com/github/codeql-action/blob/main/CHANGELOG.md
- https://github.com/github/codeql-action/releases/tag/v3.25.2
- https://github.com/github/codeql-action/releases/tag/v3.25.3
- https://github.com/github/codeql-action/releases/tag/v3.25.4
- https://github.com/github/codeql-action/releases/tag/v3.25.5
- https://github.com/github/codeql-action/releases/tag/v3.25.6
- https://github.com/github/codeql-action/releases/tag/v3.25.7
- https://github.com/github/codeql-action/releases/tag/v3.25.8
- https://github.com/github/codeql-action/releases/tag/v3.25.9
- https://github.com/github/codeql-action/releases/tag/v3.25.10
- https://github.com/github/codeql-action/releases/tag/v3.25.11
- https://github.com/github/codeql-action/releases/tag/v3.25.12
- https://github.com/github/codeql-action/releases/tag/v3.25.13
- https://github.com/github/codeql-action/releases/tag/v3.25.14
- https://github.com/github/codeql-action/releases/tag/v3.25.15
- https://github.com/github/codeql-action/releases/tag/v3.26.0
- https://github.com/github/codeql-action/releases/tag/v3.26.1
- https://github.com/github/codeql-action/releases/tag/v3.26.2
- https://github.com/github/codeql-action/releases/tag/v3.26.3
- https://github.com/github/codeql-action/releases/tag/v3.26.4
- https://github.com/github/codeql-action/releases/tag/v3.26.5
- https://github.com/github/codeql-action/releases/tag/v3.26.6
- https://github.com/github/codeql-action/releases/tag/v3.26.7
- https://github.com/github/codeql-action/releases/tag/v3.26.8
- https://github.com/github/codeql-action/releases/tag/v3.26.9
- https://github.com/github/codeql-action/releases/tag/v3.26.10
- https://github.com/github/codeql-action/releases/tag/v3.26.11
- https://github.com/github/codeql-action/releases/tag/v3.26.12
- https://github.com/github/codeql-action/releases/tag/v3.26.13
- https://github.com/github/codeql-action/releases/tag/v3.27.0
- https://github.com/github/codeql-action/releases/tag/v3.27.1
- https://github.com/github/codeql-action/releases/tag/v3.27.2
- https://github.com/github/codeql-action/releases/tag/v3.27.3
- https://github.com/github/codeql-action/releases/tag/v3.27.4
- https://github.com/github/codeql-action/releases/tag/v3.27.5
- https://github.com/github/codeql-action/compare/v3.25.1...v3.27.5


feat: 🎸 Add link variants: animated with arrow, icon on the left or right

This PR consist of these changes

[x] Link variant arrow animated
[x] Reduced motion option for the animated link
[x] Dark/Light mode variable for the arrow animated link
[x] A variant with optional icon on the left or right
[x]  Removed old link styled like ribbon with background colour

👋 Thanks for creating a pull request! 🚀 Checkout the storybook we've created for it: chlorophyll


Fix inputs

Thank you for your contribution to the repo. Before submitting this PR, please make sure:

[x] Your code builds clean without any errors or warnings
[ ] You are using approved terminology
[ ] You have added unit tests
[ ] You have updated documentation
[ ] You have tested your changes

Please provide a description of the changes proposed in the pull request and reference any related issues in the repository.
Please indicate if this PR contains:

[x] A bug fix
[ ] A feature request
[ ] Breaking changes
[ ] An enhancement

Build is not working & imports are incorrect. @fadiDL


Release/2.11.2

Coverage increased (+0.005%) to 95.144% when pulling fbe2a1f3479232bea407840b1df847b62db61a82 on release/2.11.2 into 52b5732c0704294ee162f11853612cb5100352b1 on master.

Coverage increased (+0.005%) to 95.144% when pulling fbe2a1f3479232bea407840b1df847b62db61a82 on release/2.11.2 into 52b5732c0704294ee162f11853612cb5100352b1 on master.

Coverage increased (+0.005%) to 95.144% when pulling fbe2a1f3479232bea407840b1df847b62db61a82 on release/2.11.2 into 52b5732c0704294ee162f11853612cb5100352b1 on master.

Coverage increased (+0.005%) to 95.144% when pulling fbe2a1f3479232bea407840b1df847b62db61a82 on release/2.11.2 into 52b5732c0704294ee162f11853612cb5100352b1 on master.


[Command] warden env command

Version of Warden
0.14.3
Operating System and Installation Method
Mac OS 15.1 via Brew
Describe the Bug
When running a warden env up command, it's printing a
To Reproduce

Install latest mutagen version (0.18.0 in my case)
Run warden env up

Actual result
You see a warnings in the output:
$ warden env  up
Connecting traefik to myproject_default network
Connecting tunnel to myproject_default network
Connecting mailhog to myproject_default network
[+] Running 7/0
 ✔ Container myproject-db-1             Running                               0.0s
 ✔ Container myproject-opensearch-1  Running                               0.0s
 ✔ Container myproject-redis-1          Running                               0.0s
 ✔ Container myproject-php-fpm-1        Runni...                              0.0s
 ✔ Container myproject-nginx-1          Running                               0.0s
 ✔ Container myproject-php-debug-1      Run...                                0.0s
 ✔ Container myproject-varnish-1        Runni...                              0.0s
/opt/homebrew/Cellar/warden/0.14.3/commands/env.cmd: line 220: [[:<PHONE_NUMBER>: value too great for base (error token is "0018000000")
/opt/homebrew/Cellar/warden/0.14.3/commands/env.cmd: line 220: [[:<PHONE_NUMBER>: value too great for base (error token is "0018000000")
/opt/homebrew/Cellar/warden/0.14.3/commands/env.cmd: line 220: [[:<PHONE_NUMBER>: value too great for base (error token is "0018000000")
/opt/homebrew/Cellar/warden/0.14.3/commands/env.cmd: line 220: [[:<PHONE_NUMBER>: value too great for base (error token is "0018000000")
Created session sync_gWgOnEsgekO8WZZBXYHcZzv0LnOdWDjWuTUFWJK5xeU
Waiting for initial synchronization to complete
.............

Expected Behavior
You should not see any warnings
Additional context
No response

Could you also please advise your mutagen and bash versions? I haven't been able to recreate this one yet (it was reported last week, too) which makes it hard to know if a fix will work.
If you're feeling enterprising, would you be able to test these stack overflow solutions? https://stackoverflow.com/a/24777667/43790 - if it fixes it for you, and doesn't break anything for me, we'll roll with it

I have a ZSH 5.9 + oh-my-zsh (just updated to latest version.
$ zsh --version
zsh 5.9 (arm64-apple-darwin24.0)

About bash version:
$ bash --version
GNU bash, version 3.2.57(1)-release (arm64-apple-darwin24)
Copyright (C) 2007 Free Software Foundation, Inc.

I can test it by the following commands:
function version {
  echo "$@" | awk -F. '{ printf("%d%03d%03d%03d\n", $1, $2, $3, $4); }'
}

if [[ $(version "0.18.0") -ge $(version '0.15.0') ]]; then
  echo 'success'
else
  echo 'fail'
fi

In bash, it fails:

while in zsh it's passing

@navarr I noticed that this option works fine for me:
function version {
  echo "$@" | awk -F. '{ printf("%d%03d%03d%03d\n", $1, $2, $3, $4); }'
}

if [[ $((10#$(version "0.18.0"))) -ge $((10#$(version "0.15.0"))) ]]; then
  echo 'success'
else
  echo 'fail'
fi

Based on this, I created pull request https://github.com/wardenenv/warden/pull/817


no keys found in different directory

I am having issues changing the directory of the keys location.
When I make the path /mnt/user/Video files/mnemonic.txt It will not detect the text file I have in there, It also will not create a new key.
I get this error when trying to create a new one.
"Unable to save mnemonic to /mnt/user/Video files/1/mnemonic.txt"
What am I doing wrong?

You seem to have the wrong path for "mnemonic". The path for this needs to be within the container e.g. /root/.chia/mnemonic.txt This /root/.chia-directory is then mapped to the host system using the "appdata"-variable.
So setting "appdata" to /mnt/user/appdata/machinaris and "mnemonic" to /root/.chia/mnemonic.txt will put your mnemonic.txt in /mnt/user/appdata/machinaris/mnemonic.txt

Closing as resolved with path fix.  Thanks!


fix precedence for where the projectId is acquired from

apologies for some of the formatting/indentation changes.


[PT]The "Show price model" is not displayed.

[Summary]
The "Show price model" is not displayed.
[Product name and version]
FUJITSU Software Enterprise Service Catalog Manager V16.1 GA1
BES_MASTER_DELIVERY-7442016/07/22
[Client IDE]
OS       : Windows7 Pro SP1
Browser  : Firefox(48.0)
[Reproduce frequency]
Always
[GBP Bug Classification]
Short Name:PB-InvFun
Fundamental Function:Yes
Workaround:Yes
Severity:Major
[How to reproduce]

The service of external billing is activate.
The customer is click "Show Details".
Click "Get it now"
Click "next"

[Expected result]
The "Show price model" is displayed.
[Observed result]
The "Show price model" is not displayed.
[Detail]
"Show price model" is not displayed at the service of an external billing.
Please display the link of "Show price model".
[Message and logs]
Nothing

[Date] 2016/08/08 verified,
link is displayed and works.

Code for external price model has been added in wrong place and was not executed. The fix modified the servicePriceLink.xhtml page and moved code with external price model to the first conditional.


How to Force login only use facebook app?

I want to force the user to login with facebook mobile app.
does the behavior "FacebookLoginBehavior.nativeOnly" force the user to login with facebook mobile app???

var facebookLogin = FacebookLogin();
facebookLogin.loginBehavior = FacebookLoginBehavior.nativeOnly;

Is it correct for my purpose??? Thanks

yes correct but it's not working in my app when i'm using this.
it's open one pop up with user profile photo and name but not log in.
var facebookLogin = FacebookLogin();
facebookLogin.loginBehavior = FacebookLoginBehavior.nativeOnly;


PasswordChangeSerializer throws an exception if Sessions aren't enabled in Django

With the popularity of SPA's increasing, sessions may not be present in a Django Project.
The save() function in the default PasswordChangeSerializer relies on sessions to be present when it calls the function update_session_auth_hash(self.request, self.user)
A check should be added to prevent this call if sessions aren't installed.
A hack workaround is to set LOGOUT_ON_PASSWORD_CHANGE = True to avoid this case.
Another workaround is to override the PasswordChangeSerializer and add a custom save() method that does not call update_sesion_auth_hash

One other case that looks like it requires sessions is the LogoutView when django_logout() is called unconditionally.

I'm having a similar issue when running with cache off


/mowgroups formatting cleanup

/mowgroups could use some formatting love, and maybe a count of total groups

Taken care of in /grouplist on np-telegram-bot.


Unsendable messages have frozen spinners

Unsendable messages appear in the message list with a frozen spinner, as shown below.

(This is a reprise, but apparently not a duplicate, of #1546.)

This is fine in a modern Webview; per MDN it should only fail on Chrome <43, where the animation property isn't supported.
On the other hand, the -webkit-animation property is supported as early as Chrome 18.

Huh, is this limited to unsendable messages?
I see also #3731 which is about "permanently unsendable" messages; is that the same set of messages?

Ah I see, but also this is only on Chrome <43. Copying what I just wrote on the PR #3735 (maybe I should have made the detailed comment here in the first place; oh well):

Hmm, this is quite a fair bit of duplication: 23 lines across 8 places in the file. [Which is a perfectly reasonable way of making the fix; it's just the nature of the fix.]
Here's what we say (in js.js) about old Chrome versions:
 * * For Android, core functionality needs to work on Chrome 44.
 *   Graceful degradation is acceptable below Chrome 58. [...]
 *
 *   * Below Chrome 44, it's possible (but rare) for a user to be on a
 *     version as old as Chrome 37, which shipped with Android 5 Lollipop.
 *     We sometimes fix issues affecting those versions, only when trivial.

I think the complexity of this fix falls well above the "trivial" threshold, in terms of its maintenance cost for ongoing changes to our CSS styles.
Happily the issue is also fairly minor: it doesn't affect the actual functionality, and most users will rarely to never see it at all. So I think it's the kind of "graceful degradation" I'd be OK with at any Chrome version below 58, when the fix isn't trivial.
Thanks for looking into this! I think based on the information collected, the best path is to close the PR and issue (as WONTFIX), and turn attention to other bugs and features.


fix(query): cover additional deprecated API versions in k8s rule

Proposed Changes

Add more CRD deprecations to the rule (previously mentioned here: https://github.com/Checkmarx/kics/pull/4830#pullrequestreview-881390156)
Extend description
Change category to "Best Practices": Using a Kubernetes resource with a deprecated API version is not a security risk, comparable to others in that category (e.g. seccomp profile missing). Newer versions are not "more secure", only less likely to cause problems during K8s upgrades.

I submit this contribution under the Apache-2.0 license.

Done, thanks for the hint, @rafaela-soares 👍

Done, thanks for cross-checking 😊


implement brushed selection

such that user can drag and select multiple items. could be restricted to the selection column only

I'm setting this to high because it's also important for Taggle.

@sgratzl does the brush only on string columns or all column types?

nice. @thinkh, I think it would be good to also turn off the text highlights as part of your style changes.

Thanks. Very nice. 👍

nice. @thinkh, I think it would be good to also turn off the text highlights as part of your style changes.

then you cannot copy a line anymore.

cannot we just change the style to not change but still select the text when copying? how is this handled in other visualizations?


Pick a Publish Target

Be aware that if you "Select Existing" instead of "Create New", it will overwrite anything in that existing function app. There is no backup or restore capability for overwriting data.

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

ID: 6e88ea08-81ef-2b5a-b9d6-539e85592672
Version Independent ID: f2d8b7b4-906a-d1f5-5201-fc22a7890955
Content: Create your first function in Azure using Visual Studio
Content Source: articles/azure-functions/functions-create-your-first-function-visual-studio.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

@ejacobsen-glofin Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

@AngelosP I can add a warning in the docs, but do you think we need a warning about this in the UI?

This is great feedback, thank you all. @ggailey777 we are going to take a look and see what we can do in the UI. There are also some advanced options that sometimes let you control the behavior in some scenarios. We just need to review them and find a nice, friendly, consistent way of stating what will happen after you click Publish in all scenarios. Thanks again!

Thanks guys. I think a warning or note in the docs would be sufficient.


650-update-github-actions

replace helm-release-differ.yaml with @onedr0p

You do not need to keep mentioning me, I get notifications each time you do :)


ostree: Always include from-scratch deltas in wanted deltas

If from-scratch delta is not generated and uploaded by the client,
flat-manager never generates it on its own. As it's potentially
common oversight, from-scratch deltas should always be generated
on flat-manager end.
This means the only way to disable deltas completely is to set depth
to -1.

Converted to draft as I need to test it.

Should there be some warning somewhere when this happens?

Going to close it – I guess it should be better documented that flat-manager only handles between-commits deltas as it's trivial to generate from-scratch deltas locally.

Going to close it – I guess it should be better documented that flat-manager only handles between-commits deltas as it's trivial to generate from-scratch deltas locally.


[SR-2671] Date Components return value instead of nil

Previous ID
SR-2671

Radar
None

Original Reporter
erica (JIRA User)

Type
Bug

Attachment: Download

Environment
Xcode 8

Additional Detail from JIRA

Votes
1

Component/s
Foundation

Labels
Bug

Assignee
None

Priority
Medium

md5: 0cfc50f542146fceb8eeb2f9d4156906

Issue Description:
let dc = DateComponents(hour: 5, minute: 2)
print(dc.value(for: .second))
/// The calendar and timeZone and isLeapMonth property values cannot be retrieved by this method.
public func value(for component: Calendar.Component) -> Int?
Returns: Optional(9223372036854775807) instead of nil
p.s. the whole "isLeapMonth" thing for EVERY DATE COMPONENTS is really annoying

This is now fixed.


Kuberhealthy daemonset pods fail to get cleared up

Describe the bug
We've noticed that kuberhealthy pods are failing to be cleared up after their use. The logs show:
time="2020-03-11T03:02:40Z" level=error msg="Get https://<IP>443/api/v1/namespaces/jx/pods?fieldSelector=status.phase%3DRunning&labelSelector=app%3Dkuberhealthy: dial tcp <IP>:443: connect: connection refused"
time="2020-03-11T03:03:20Z" level=error msg="Get https://<IP>:443/api/v1/namespaces/jx/pods?fieldSelector=status.phase%3DRunning&labelSelector=app%3Dkuberhealthy: dial tcp <IP>:443: i/o timeout"

Steps To Reproduce

Long running kuberhealthy instance it seems (some of ours have been running more that 30d

Expected behavior
Pods created by kuberhealthy are removed once they have completed their task
Versions

Kubernetes Version: v1.15.8-gke.3, v1.13.12-gke.25 (happening on multiple cluster versions)
Kuberhealthy Chart version: 1.2.6

Additional context
When deleting the kuberhealthy app pods then it seems to resolve the issue and the daemonset pods are cleared up as expected.
daemonset pods output
daemonset-test-kuberhealthy-849f8ccd74-4vtck-1579889629-4fpfw     1/1     Running     0          52d
daemonset-test-kuberhealthy-849f8ccd74-4vtck-1579889629-nqmks     1/1     Running     0          52d
daemonset-test-kuberhealthy-849f8ccd74-4vtck-1579889629-vnzxt     1/1     Running     0          52d
daemonset-test-kuberhealthy-849f8ccd74-4vtck-1581142553-5dxqh     1/1     Running     0          37d
daemonset-test-kuberhealthy-849f8ccd74-4vtck-1581142553-99bls     1/1     Running     0          37d
daemonset-test-kuberhealthy-849f8ccd74-4vtck-1581142553-btpxn     1/1     Running     0          37d
daemonset-test-kuberhealthy-849f8ccd74-4vtck-1581451506-2b4zn     1/1     Running     0          34d
daemonset-test-kuberhealthy-849f8ccd74-4vtck-1581451506-4kqq4     1/1     Running     0          34d
daemonset-test-kuberhealthy-849f8ccd74-4vtck-1581451506-q9bbn     1/1     Running     0          34d
daemonset-test-kuberhealthy-849f8ccd74-4vtck-1582613991-gkb2g     1/1     Running     0          20d
daemonset-test-kuberhealthy-849f8ccd74-4vtck-1582613991-td84c     1/1     Running     0          20d
daemonset-test-kuberhealthy-849f8ccd74-4vtck-1582613991-xkvrr     1/1     Running     0          20d
daemonset-test-kuberhealthy-849f8ccd74-4vtck-1583102472-8xhm8     1/1     Running     0          15d
daemonset-test-kuberhealthy-849f8ccd74-4vtck-1583102472-9r6rw     1/1     Running     0          15d
daemonset-test-kuberhealthy-849f8ccd74-4vtck-1583102472-mnzs4     1/1     Running     0          15d
daemonset-test-kuberhealthy-849f8ccd74-4vtck-1583112675-9jr4s     1/1     Running     0          14d
daemonset-test-kuberhealthy-849f8ccd74-4vtck-1583112675-l75vf     1/1     Running     0          14d
daemonset-test-kuberhealthy-849f8ccd74-4vtck-1583112675-vndx4     1/1     Running     0          14d
daemonset-test-kuberhealthy-849f8ccd74-4vtck-1583257883-bbk2g     1/1     Running     0          13d
daemonset-test-kuberhealthy-849f8ccd74-4vtck-1583257883-l8jcr     1/1     Running     0          13d
daemonset-test-kuberhealthy-849f8ccd74-4vtck-1583257883-qgc6b     1/1     Running     0          13d
daemonset-test-kuberhealthy-849f8ccd74-4vtck-1584159662-bwcdf     1/1     Running     0          3d5h
daemonset-test-kuberhealthy-849f8ccd74-4vtck-1584159662-lh2pp     1/1     Running     0          3d5h
daemonset-test-kuberhealthy-849f8ccd74-4vtck-1584159662-vcg7m     1/1     Running     0          3d5h
daemonset-test-kuberhealthy-849f8ccd74-4vtck-1584344296-v7cmp     1/1     Running     0          18h
daemonset-test-kuberhealthy-849f8ccd74-4vtck-1584344296-vxhjp     1/1     Running     0          18h
daemonset-test-kuberhealthy-849f8ccd74-4vtck-1584344296-zh54n     1/1     Running     0          18h

Hmm, seems like you are using an older version of Kuberhealthy. We've recently made a lot of changes with out 2.0.0 release -- making Kuberhealthy an operator for synthetic monitoring, giving devs the ability to add more synthetic checks easily -- and we also made more changes with our latest 2.1 release as well (this actually keeps checker pods around a bit longer so folks have more time to diagnose issues/failures, along with a check reaper that does the cleanup of older checker pods).

@cagiti could you try installing one of the flat file specs here to update to Kuberhealthy 2.1?  You can also use the helm chart provided there if you prefer.

@cagiti could you try installing one of the flat file specs here to update to Kuberhealthy 2.1? You can also use the helm chart provided there if you prefer.

I’ll try upgrading using the chart, thanks for getting back to me 👍

Where can I find the latest chart version please? I'm using the latest hosted here https://hub.helm.sh/charts/stable/kuberhealthy/1.2.6

We're just about to finish #288 and you'll be able to use helm 3 to install the chart soon....
If you want to deploy before that, the most current specs would be here: https://github.com/Comcast/kuberhealthy/tree/master/deploy
You should probably use this file if you have a standard Kubernetes deployment.

@cagiti wondering if this is still an issue for you? hoping to close this out if possible!

@cagiti wondering if this is still an issue for you? hoping to close this out if possible!

We've not migrated over to Helm3 at the moment, so we'll need to look at moving to using the specs from https://github.com/Comcast/kuberhealthy/tree/master/deploy .

@cagiti wondering if this is still an issue for you? hoping to close this out if possible!

We've not migrated over to Helm3 at the moment, so we'll need to look at moving to using the specs from https://github.com/Comcast/kuberhealthy/tree/master/deploy .

@cagiti closing this issue for now -- feel free to open another issue if you're still running into problems!


[Feature] Is there a process for visually adjusting the thresholds?

For example, I get the outputs (logits) of last layer of a segmentation neural network (eg: binary segmentation), and I get the probabilities with the sigmoid function.
I pass it on the wandb webiste with wandb.Image().
Is there a way to adjust the threshold on the webpage to see different segmentation results?

Hi @qsunyuan,
Currently there is no such feature, but we do have an existing request for something like this. I'll increase the priority on the feature request for you!
Thanks,
Ramit

Thx.


TextAnalyticsApiKeyCredential not working with python 3.6.9

from azure.ai.textanalytics import TextAnalyticsClient, TextAnalyticsApiKeyCredential
is throwing an error.
Traceback (most recent call last):
File "", line 1, in
ImportError: cannot import name 'TextAnalyticsApiKeyCredential'
I'm using python 3.6.9.
I have used this to install library
 pip install azure-ai-textanalytics
It installs the following version.
Name: azure-ai-textanalytics
Version: 1.0.0b4

@denyshubh Thanks for the question. We are investigating the issue and will update you shortly.

Thank You @ram-msft .

@denyshubh The following  sample demonstrates how to authenticate to the Text Analytics service.
There are two supported methods of authentication:
1) Use a Cognitive Services/Text Analytics API key with AzureKeyCredential from azure.core.credentials
2) Use a token credential from azure-identity to authenticate with Azure Active Directory
See more details about authentication here:
https://github.com/Azure/azure-sdk-for-python/blob/master/sdk/textanalytics/azure-ai-textanalytics/samples/sample_authentication.py
https://docs.microsoft.com/azure/cognitive-services/authentication
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

On April 7, 2020, a new version of azure.ai.textanalytics (1.0.0b4) was released, in which they removed TextAnalyticsApiKeyCredential and are now using AzureKeyCredential from azure.core.credentials as key credential
(details can be found here - https://pypi.org/project/azure-ai-textanalytics/)
You basically have two options -

Start using AzureKeyCredential instead of TextAnalyticsApiKeyCredential (implementation details can be found on the same link)
Downgrade to a previous version of azure.ai.textanalytics (preferably 1.0.0b3 )
Steps -
First uninstall the current version with -
 pip uninstall azure.ai.textanalytics
Then downgrade to lower version using -
 pip install -Iv azure.ai.textanalytics==1.0.0b3

Hey thanks at @abhimanyusood for the update here. Could you talk someone into updating this doc to reflect that? https://docs.microsoft.com/en-us/azure/cognitive-services/text-analytics/quickstarts/text-analytics-sdk?tabs=version-3&pivots=programming-language-python


Bugbash: Two references to dev.botframework.com on Troubleshooting pagethat are no longer valid

Describe the bug
On the troubleshooting page: https://review.docs.microsoft.com/en-us/azure/bot-service/bot-service-troubleshoot-general-problems?view=azure-bot-service-4.0&branch=pr-en-us-1325
We have multiple references to dev.botframework.com that should be the Azure portal.  Note, this is limited to the first two cases; the migration case is still valid.

Fixed 3 instances.


error with last chrome and openssl

I using last nginx-ct with nginx 1.13.9 and openssl 1.1.1(alpha2)
when using ct we have a bug in chrome 64.0.3282.186
when you open site the all is good, but don’t close the tab and wait 5-10min and than refresh site with f5 and you will get ssl error(ERR_SSL_VERSION_INTERFERENCE on windows) and can’t open site while not close browser or restart nginx.
Also ct works with that openssl only if you write ct vars in block with default_server.

I can confirm this issue.

}


Fix for: Reopened task message does not translate to Spanish in LHN

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/21563
PROPOSAL: https://github.com/Expensify/App/issues/21563#issuecomment-1607531905
Tests

Click FAB button > Assign Task
Proceed to create a task
Go to task thread
Click mark as done
Go to Settings > Preferences > Language
Change the language to Spanish
In the LHN verify that the 'completed task' text is translated to Spanish ('tarea completada').
Go to Settings > Preferences > Language
Change the language back to English
Go to task thread
Click on three dots and reopen the task
Go to Settings > Preferences > Language
Change the language to Spanish
In the LHN verify that the 'reopened task' text is translated to Spanish ('tarea reabrir').

[ ] Verify that no errors appear in the JS console

Offline tests

Click FAB button > Assign Task
Proceed to create a task
Go to task thread
Click mark as done
Go to Settings > Preferences > Language
Change the language to Spanish
In the LHN verify that the 'completed task' text is translated to Spanish ('tarea completada').
Go to Settings > Preferences > Language
Change the language back to English
Go to task thread
Click on three dots and reopen the task
Go to Settings > Preferences > Language
Change the language to Spanish
In the LHN verify that the 'reopened task' text is translated to Spanish ('tarea reabrir').

QA Steps

Click FAB button > Assign Task
Proceed to create a task
Go to task thread
Click mark as done
Go to Settings > Preferences > Language
Change the language to Spanish
In the LHN verify that the 'completed task' text is translated to Spanish ('tarea completada').
Go to Settings > Preferences > Language
Change the language back to English
Go to task thread
Click on three dots and reopen the task
Go to Settings > Preferences > Language
Change the language to Spanish
In the LHN verify that the 'reopened task' text is translated to Spanish ('tarea reabrir').

[ ] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web
https://github.com/Expensify/App/assets/11609254/b2bbf613-6ccd-45a5-9c3d-1e5e2fa1e111

Mobile Web - Chrome

Mobile Web - Safari
https://github.com/Expensify/App/assets/11609254/a7f4d76c-3095-476f-b400-616b33c3bc2d

Desktop
https://github.com/Expensify/App/assets/11609254/cff6c6a6-bb82-42d8-b4b1-4a9a84cf150c

iOS
https://github.com/Expensify/App/assets/11609254/235a8c70-6eee-48c2-b2e7-5f400d8b5126

Android
https://github.com/Expensify/App/assets/11609254/6ee78d65-d1a3-4c4f-b384-6cd4d1360487

It should be noted that as mentioned in #20479 (comment) on a fresh login the last message is set by the back end (in this case 'reopened task: taskname') which don't translate as the data with the action type has not yet been received. I think this is something that is being worked on on the back end.

I think it's okay for now as it is displayed only for few seconds.

@Ollyws Task Name should also be included in the altenateText. The following screenshot from staging depicts the expected output.

@Ollyws The issue that you mentioned here is quite noticeable in smallwidth screens. Do we have any open issue for this?

Thanks for the update @Ollyws. As per this thread, we are okay to proceed with our current solution.

@srikarparsi Changes look good and test well.

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/srikarparsi in version: 1.3.39-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/francoisl in version: 1.3.39-11 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


feat: Add rollback mechanism when training fails

Description
Added a rollback mechanism to handle training failures gracefully. When the training process fails, the system will now:

Log the error and stop the workflow
Automatically fall back to using the base model
Continue with email bot operation using the base model

Changes Made

Modified run_workflow() function in lambda.py
Added error handling and logging for training failures
Implemented automatic fallback to base model
Updated comments to follow English documentation standards

Testing

Tested the fallback mechanism with failed training scenarios
Verified that the email bot continues to function with base model
Confirmed proper error logging

Impact
This change improves system reliability by ensuring the email bot can continue operating even when model training fails, rather than stopping the entire workflow.

@cafferychen777 thanks this is quite useful. may i confirm that the purpose is to NOT run the bot when training fails, and only runs it if training.py runs successfully without error? my intention was to make it such that even if something failed in training the bot would still run without the adapter, maybe it'd be better to fallback to running the chatbot directly (i.e., take out sys.exit(1) in train_model()?

@zycyc Thanks for the feedback! I've updated the code to align with your intention:
Changes in this update:

Removed sys.exit(1) from train_model()
Modified the function to return boolean status instead of exiting
Updated run_workflow() to continue execution even when training fails
Added clearer logging messages for failure scenarios

The new implementation now:

Returns True/False to indicate training success/failure
Continues running the bot even if training fails
Falls back to base model automatically when training fails
Provides better visibility through warning logs

Example workflow:
def train_model():
    try:
        # Training logic
        if success:
            return True
        else:
            logger.warning("Training failed, will continue without adapter")
            return False
    except Exception:
        logger.warning("Failed to train model, will continue without adapter")
        return False

def run_workflow():
    create_dataset()
    training_success = train_model()
    if not training_success:
        logger.warning("Training failed, continuing with base model only")
    run_email_bot()
    return True

This ensures the bot remains operational even when training encounters issues, providing better reliability and user experience. Please let me know if this better matches your requirements!


flutter pub upgrade randomly results in: Rename failed, path = '~/.pub-cache/_temp/dirBVDEOH' (OS Error: File exists, errno = 17)

Steps to reproduce
The error does not happen frequently maybe once a day.  But I have script that goes through all my flutter projects and does a flutter pub upgrade.  After installing flutter 3.22 it randomly fails every so often with
Rename failed, path = '/home/csh/.pub-cache/_temp/dirBVDEOH' (OS Error: File exists, errno = 17)
The random filename is different each time of course.  It may happen more frequently if there are actually a lot of packages updated.  If I can notice any clear patterns I will update.
I have only seen this on Linux, but I do most of my development on Linux.
Expected results
flutter pub upgrade completes without error
Actual results
.
.
.
> flutter_secure_storage 9.2.1 (was 9.1.1)
> flutter_secure_storage_macos 3.1.1 (was 3.1.0)
> image_picker_ios 0.8.11+2 (was 0.8.11+1)
Rename failed, path = '/home/csh/.pub-cache/_temp/dirBVDEOH' (OS Error: File exists, errno = 17)
make[1]: *** [Makefile:44: upgrade] Error 66

Code sample
n/a
Screenshots or Video
n/a
Logs
n/a
Flutter Doctor output
Doctor output
[✓] Flutter (Channel stable, 3.22.0, on Fedora Linux 39 (Thirty Nine) 6.8.7-200.fc39.x86_64, locale
    en_US.UTF-8)
    • Flutter version 3.22.0 on channel stable at /server/home/csh/lib/flutter3
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 5dcb86f68f (10 days ago), 2024-05-09 07:39:20 -0500
    • Engine revision f6344b75dc
    • Dart version 3.4.0
    • DevTools version 2.34.3

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /home/csh/Android/Sdk
    • Platform android-34, build-tools 34.0.0
    • Java binary at: /server/home/csh/lib/android-studio/jbr/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.9+0-17.0.9b1087.7-11185874)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • Chrome at google-chrome

[✓] Linux toolchain - develop for Linux desktop
    • clang version 17.0.6 (Fedora 17.0.6-2.fc39)
    • cmake version 3.27.7
    • ninja version 1.11.1
    • pkg-config version 1.9.5

[✓] Android Studio (version 2023.2)
    • Android Studio at /server/home/csh/lib/android-studio
    • Flutter plugin version 78.4.1
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.9+0-17.0.9b1087.7-11185874)

[✓] VS Code (version 1.89.1)
    • VS Code at /usr/share/code
    • Flutter extension version 3.88.0

[✓] Connected device (5 available)
    • sdk gphone64 x86 64 (mobile) • emulator-5554 • android-x64    • Android 14 (API 34) (emulator)
    • sdk gphone x86 64 (mobile)   • emulator-5556 • android-x64    • Android 13 (API 33) (emulator)
    • sdk gphone64 x86 64 (mobile) • emulator-5558 • android-x64    • Android 14 (API 34) (emulator)
    • Linux (desktop)              • linux         • linux-x64      • Fedora Linux 39 (Thirty Nine)
      6.8.7-200.fc39.x86_64
    • Chrome (web)                 • chrome        • web-javascript • Google Chrome 125.0.6422.60

[✓] Network resources
    • All expected network resources are available.

• No issues found!

Thanks for the report @mrcsh

I have script that goes through all my flutter projects and does a flutter pub upgrade. After installing flutter 3.22 it randomly fails every so often with

Does it occur without using the script or occurs only while using the script ?

If I can notice any clear patterns I will update.

This will be helpful to address it further.

Keeping the issue open and labeling for team's attention.

Howdy. Thanks for contributing this issue!
This one is certainly interesting. flutter pub is, for the most part, a lightweight wrapper around the pub CLI tool[^1]. From the error message, I'm guessing pub is trying to create a new temp directory[^2], but one with the chosen name already exists. Still, this would be surprising for me because the Linux implementation for choosing a temp directory name includes logic to avoid this[^3].
[^1]: Source: https://github.com/flutter/flutter/blob/66367dd888458d94a3bd1ffd712c4cb473dc5f69/packages/flutter_tools/lib/src/dart/pub.dart#L307
[^2]: Source: https://github.com/dart-lang/pub/blob/e1fbda73d1ac597474b82882ee0bf6ecea5df108/lib/src/system_cache.dart#L121-L130
[^3]: Source: https://github.com/dart-lang/sdk/blob/14f7622ef4404eb22b7396458b6382b96f8af128/runtime/bin/directory_linux.cc#L451

Since this is most likely an issue in pub, I'll be closing this issue. Feel free to re-file this issue on the pub repository.


Issue in Install & Start HBase Process

Hi,
As per the guide line given in the below link, i have build Pinpoint using "mvn install -Dmaven.test.skip=true" command. It is got success all the projects.
https://github.com/naver/pinpoint/blob/master/quickstart/README.md
After that i have downloaded Hbase for windows. and Rename the directory to hbase so that the final HBase directory looks like quickstart\hbase\hbase.
When i am trying to run below commond, its not working. Could you please help me, how to run these in commond prompt in window 2008 server.
Download & Start - Run quickstart/bin/start-hbase.sh
Initialize Tables - Run quickstart/bin/init-hbase.sh

Please help on my issue. I am not able to progress on Pinpoint. Could you pls guide me how to run HBase on window2008 server

Please refer to this guide on window environment.
However, this guide document has been tested only on windows 7 and 10, so it may not work on Windows server.
Quickstart does not guarantee support on Windows servers.
Sadly if it does not work, there is no way we can help.


how can I get intent ？

I want intent to do something, how can I get it?

for examle do what

Postcard ≈ Intent

Notification  PendingIntent


Issue with Akask Provider: Misconfigured Worker Node

Problem
User quantomworks experienced an issue where cloudmos was not recognizing their node despite being active and running a test deployment. Further discussions with SGC | DCNorse identified a problematic configuration where the output indicated the intriguing number for the GPU count:
"gpu":18446744073709551615

This number,<PHONE_NUMBER>3709551615, was determined to be a representation of -1 when interpreted as a unsigned 64-bit integer ^1^. The user queried this unexpected interpretation and what might cause such an issue.
Diagnosis
SGC | DCNorse suggested that when a GPU goes offline while the provider/worker node is running, the reported number of GPUs might be incorrect. They proposed resolution methods such as shutting down some operations or rebooting the node.
Subsequent Findings

There seemed to be inconsistency between the available GPUs reported by Akash and the actual resources in Kubernetes.

The issue persisted even after updating the driver.

Misconfiguration was identified when moving GPU's between worker nodes. The labels for quantomworks Kubernetes/Akash worker node could be erroneous.

quantomworks detected that the node misunderstanding the number of GPUs available could be because of the node being in use but presenting -1. The nodes in question weren't labeled for GPU use.

Solution
The issue was resolved when correctly labeling the nodes. It seemed that since they weren't initally labeled, it assumed 0 GPU availability for consumption but also presented a -1 due to a workload using them.
{"name":"game-1","allocatable":{"cpu":11000,"gpu":1,"memory":67242971136,"storage_ephemeral":390585090631},"available":{"cpu":3000,"gpu":0,"memory":47008821248,"storage_ephemeral":390585090631}},{"name":"game-2","allocatable":{"cpu":11000,"gpu":1,"memory":67242594304,"storage_ephemeral":390586034349},"available":{"cpu":2285,"gpu":0,"memory":47172022272,"storage_ephemeral":390586034349}}

This correct labeling should allow cloudmos to correctly identify the node and compute resources.
Suggestions
Going forward, these insights would be useful to the community:

A provider troubleshooting page on cloudmos would be handy for issue identification and solutions.
Potential issues when mixing usage of GPUs locally and with Akash given the nature of passthrough in Akash.

Thanks for the suggestion @sfxworks - I'm moving this to the cloudmos repo for consideration towards enhancements there

Actually - looks like this could use improvements in both cloudmos and provider so I'll leave this here and create a separate one in cloudmos, referencing this

Not sure if related, but I am working on one provider now (the other issue where provider isn't releasing all of the GPU's it has),
So the gpu number briefly spiked up to<PHONE_NUMBER>3709552000 after I've bounced all the four nvdp-nvidia-device-plugin pods (using kubectl -n nvidia-device-plugin delete pods --all command)  (4 worker nodes, each has 8x A100 GPUs)

cc @chainzero @troian


Wrapped ipfs/ipns regex in RegExp constructor

Merging into staging and will push new fixes directly to staging from now on


chmod +X equivalent flag  when mounting artifacts

Summary
Currently, the only way to set the file mode on a mounted artifact is to provide the octal mask as mode, with the option to make it recursive akin to chmod -R.  This covers a lot of use-cases, however I'm finding myself missing a way to express chmod +X style permissions when working with artifacts:
From man chmod:

execute/search only if the file is a directory or already has execute permission for some user (X)

Finding a name for this flag may be a challenge. modeExecuteDirOnly: true?
Use Cases
I want to allow any user to read the full file tree in the artifact, so that artifact consumers can work with the data. But for security reasons, I do not want the artifact consumer to be able to execute anything (except traversing into directories).

Message from the maintainers:
Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.

Im afraid not. It's been a good while since I opened this and I don't currently work with Argo, so it's not very relevant to me anymore. Feel fre to close. Looks like it might have been pretty niche anyway.


orjail leaks non-TCP/Tor packets if forwarding is enabled in the main OS.

IP forwarding is needed to be activated sometimes.
When net.ipv4.conf.all.forwarding and net.ipv4.conf.default.forwarding are enabled (with sysctl), all non-Tor packets are visible in the main network stack coming from orjail, that is, the internal packets inside sandbox.
I really don't know if the packets leaks through router and reaches the Internet IP which is destined, but if there is an adversary controlling the router, yes, he can capture all of them!
$ orjail -v -u root ping <IP_ADDRESS>
$ orjail -v deluge magnet:?xt=urn:btih:f4e3cc2db4163e3b1ff77b3e23b76b85a1d4ee1f&tr=https://ipleak.net/announce.php%3Fh%3Df4e3cc2db4163e3b1ff77b3e23b76b85a1d4ee1f&dn=ipleak.net+torrent+detection # Torrent leak test from ipleak.net
Running tcpdump show this:
$ tcpdump -vv -i in-torjail | grep <IP_ADDRESS>
Running inside a separate namespace prove that the main router can see the leaked packets:
$ ip netns add nsx
$ ip link add vethx type veth peer name peerx
$ ip link set peerx netns nsx
$ ip addr add <IP_ADDRESS>/24 dev vethx
$ ip link set vethx up
$ ip netns exec nsx ip addr add <IP_ADDRESS>/24 dev peerx
$ ip netns exec nsx ip li set peerx up
$ ip netns exec nsx ip route add <IP_ADDRESS> dev peerx
$ iptables -t nat POSTROUTING -s <IP_ADDRESS>/24 -o eth0 -j MASQUERADE
$ ip netns exec nsx orjail -s -u root ping <IP_ADDRESS>
$ tcpdump -vv -i in-torjail | grep <IP_ADDRESS>
$ tcpdump -vv -i eth0 | grep <IP_ADDRESS>
Yes, leaked packets pass through virtual interface vethx from the network namespace nsx and reaches the upside router.
There is a simple fix for this:
$ iptables -I FORWARD 1 -i in-torjail -j DROP
$ iptables -I FORWARD 1 -o in-torjail -j DROP
$ sysctl -w -q net.ipv4.conf.in-torjail.forwarding=0
$ sysctl -w -q net.ipv4.conf.in-torjail.forwarding=0
Now none of the packets leaks.
Some additional iptables rules for protection:
$ iptables -t nat -I POSTROUTING 1 ! -o in-torjail -s <IP_ADDRESS>/24 -j RETURN
$ iptables -t nat -I PREROUTING 1 ! -i in-torjail -d <IP_ADDRESS>/24 -j RETURN
$ iptables -t nat -A PREROUTING -i in-torjail -j RETURN
$ iptables -A INPUT ! -i in-torljail -s <IP_ADDRESS>/24 -j DROP
$ iptables -A INPUT ! -i in-torljail -d <IP_ADDRESS>/24 -j DROP

This issue needs urgent attention, I used orjail for almost 1 year since it was torjail, although I never made anything illegal with it.

thanks, I'm looking on it

Very nice catch!
Fixed as suggested, thanks.
Before adding the additional rules I want to investigate a bit more, so I leave this issue open for now.

@lesion
There is some programs that adds netfilter rules without user knows that (as Guidedog does), and also, the user may want to have some iptables rules saved for loading in system initialization. Is possible to these rules conflict with those of orjail and lead to a potential leak.
Everything coming from orjail (-s <IP_ADDRESS>/24) will not reach any other interface but orjail (! -o orjail), being the first in the chain will block everything down:
$ iptables -t nat -I POSTROUTING 1 ! -o in-orjail -s <IP_ADDRESS>/24 -j RETURN
Redirections from orjail (<IP_ADDRESS>/24) will not reach anything but orjail (! -i in-orjail) being the fist in the chain:
$ iptables -t nat -I PREROUTING 1 ! -i in-orjail -d <IP_ADDRESS>/24 -j RETURN
This will prevent any other port redirection to me made in the orjail virtual interface, must be appended (-A) after all other DNAT rules (remember, some programs listen on <IP_ADDRESS> and [::], and so, will listen on the orjail veth too!):
$ iptables -t nat -A PREROUTING -i in-orjail -j RETURN
This will prevent pings on the orjail veth (if there is an adversary controlling the internet router (gateway),  he can ping orjail)
$ iptables -A INPUT ! -i in-orjail -s <IP_ADDRESS>/24 -j DROP
$ iptables -A INPUT ! -i in-orjail -d <IP_ADDRESS>/24 -j DROP
The main purpose of this rules is lock orjail completely from the main network stack and prevent even the minor leaks.
Is very important that forwarding rules for orjail be the first in the chain, because they will neutralize all the other rules down in the chain. I suggest to put 1 (one) after FORWARD in the script as that:
iptables -I FORWARD 1 -i in-orjail -j DROP
iptables -I FORWARD 1 -o in-orjail -j DROP

I think I leaked my real IP some months ago due to a very strange bug in the system which zeroed all my iptables rules. I decided to make a script for personal to achieve a paranoid level of isolation, I will share with you: https://gist.github.com/phantomcraft/2e7c3dfab8cf62702e784a8c54686fc8
Perhaps you can help to improve orjail.

Thank you for taking the time to explain.

Is very important that forwarding rules for orjail be the first in the chain, because they will neutralize all the other rules down in the chain. I suggest to put 1 (one) after FORWARD in the script as that:

with -I if not specified 1 is the default value.

I think I leaked my real IP some months ago due to a very strange bug in the system which zeroed all my iptables rules.

I'm really sorry to hear that. if you can, could you explain some details?
<  I decided to make a script for personal to achieve a paranoid level of isolation, I will share with you: https://gist.github.com/phantomcraft/2e7c3dfab8cf62702e784a8c54686fc8
It looks amazing, I think I'm going to study it a bit :smile:
thanks

@lesion
I use Debian testing, I was using torjail when some strange bug zeroed all the iptables rules, I'm sure this was not a bug in orjail, but in the system. That's why I wrote that script.


Hi

Hi
How can I pass lamda as a callback function to the destination?
`
@RootNavGraph(start = true)
@Destination
@Composable
fun NavigationScreen(
navigator: DestinationsNavigator
) {
navigator.navigate(AuthScreenDestination(
    //############################
    //here I want to pass the lamda as a callback function
    nav = {screen ->

        when{
            screen is ScreenRout.HOMESCREEN ->
                val userName = (screen as ScreenRout.HOMESCREEN).userName
                navigator.navigate(HomeScreenDestination(userName)))
        }

    }

}
@Destination
@Composable
fun AuthScreen(
viewModel: LoginViewModel = hiltViewModel(),
nav:(ScreenRout)->Unit
) {
Button(onClick = {
nav(ScreenRout.HOMESCREEN(username))
})
{
Text(text = "Test Login")
}
}
@Destination
@Composable
fun HomeScreen(
currentUser : String
) {
Text(text = currentUser)
}
`

It seems this is what I need !!!
I just want to keep all navigation-related stuff in one place instead of passing the 'navigator' all around.

For that you need to manually call your destination composables, here:
https://composedestinations.rafaelcosta.xyz/destination-arguments/navhost-level-parameters#manually-call-your-screen-composable

Have you tried running the app? Those results are only received when the second screen goes away and this first is shown 😛 not sure if this is what you want to achieve

yes, it's working.
in my case that's what I need
when the user authenticates successfully the authScreeen sends back the username which I use for going to the HomeScreen,
and from there if the user clicks on the specific device it returns back the device_id which I use to create the DeviceView

Ok great. Not sure if you’ve worked with it, but this feature is sort of anologous to startActivityForResult.

All the credits to "Ben Kadel" :)
I saw this pattern (let's say) in his live stream and really liked it because all my navigation-related stuff stays in one place, and when I come back to code later on I don't have to guess which screen comes before or after what.

Do you have any idea why I get a new instance of viewModel when I come back to a Composable?
I use Hilt dependency injection and only one activity, so every time I come to screen I have to get the same instance of viewModel, or am I missing something?

Are you passing the activity to the hiltViewModel method?

In order for a viewModel to be scoped to the activity, you need to pass activity as a parameter to hiltViewModel (which you’re not).
Check here:
https://composedestinations.rafaelcosta.xyz/common-use-cases/providing-viewmodels#share-viewmodels-between-multiple-destinations
In the example, we provide same VM for all destinations of given nav graph or to all by passing the activity.

this is what I added to MaynActivity onCreate function.
But the homeScreen still gets a new instance of viewModel, as you can see in logs

So how I can get the VM instance in Composable?

You can just remove  = hiltViewModel() and run the app 🙂
Compose Destinations is the one calling your Destination Compsoable functions, so it can pass whatever you add as dependency in the NavHost parameter.

Yes yes I see !!!!!!

Thank you very much


transformers series part 4

With all the preparations we can now train, evaluate and save a model.

train, save, evaluate model
notebook for training also on colab
Because of duplication with spacy_model_manager, I did not include methods for:
checking if model_dir exists and is a valid name
set metadata and publish to huggingface

We need to decide on how to rework the modules to avoid duplication but still expose functionality to both model managers.
We also need to include the different tasks and running on more than one input file.

Also if the get_data_lists and generate_labels functions are intended to be used by the user it might be better to pass the DataManger object instead of the doc_dict.


Tools folder refered to by  test/runner.html is not included

 Issue by QuantumInformation
Thursday Aug 14, 2014 at 11:07 GMT
Originally opened as https://github.com/Polymer/polymer-dev/issues/73

In test/runner.html references to ../../tools is made but it is not included in the repo.
    <title>Polymer Test Runner (Mocha)</title>
    <meta charset="UTF-8">
    <!-- -->
    <link rel="stylesheet" href="../../tools/test/mocha/mocha.css">
    <script src="../../tools/test/mocha/mocha.js"></script>

Can we close?

Closing this issue due to age and the release of version 1 of Polymer - please feel free to re-open if this is incorrect.


doc: align spelling with oauth2 spec

I suggest to align the spelling of fields like refreshToken to the oauth2 spec and make it refresh_token. To be consistent, additional fields not specified by the oauth2 spec, should follow the same pattern, e.g.: refreshEndpoint -> refresh_endpoint

@jimmarino , do you think that is reasonable? I see it beneficial to take the oauth2 wording as base.

@lholthof we discussed this and don't think we should change from camel case to snake case because the DSP specifications, IATP, and Tractus-X profile all use the former. Originally DSP aligned with the W3C Verifiable Credentials on using camel case.


Standard.Buffer:map and Standard.Buffer:map inPlaceMap fail with empty buffer

Expected behavior:
map and inPlaceMap should return an empty buffer or do nothing to an empty buffer, respectively.
Observed behavior
An Overflow in trappingSubtract (Index) error is thrown.  Similar to #469
Triggering test cases
    function inPlaceMapEmptyTest(): Unit is
        testHeading("inPlaceMapEmpty");

        let b: Buffer[Int32] := allocateEmpty();
        inPlaceMap(&!b, double);
        assertLength(&b, 0);

        destroyFree(b);
        assertSuccess("destroyFree complete");
        return nil;

    function mapEmptyTest(): Unit is
        testHeading("mapEmpty");

        let b1: Buffer[CardinalDirection] := allocateEmpty();
        let b2: Buffer[Nat8] := map(b1, directionToChar);

        assertLength(&b2, 0);

        destroyFree(b2);
        assertSuccess("destroyFree complete");
        return nil;
    end;

Fixed by #476


it works for 3-D Multilateration?

I only want to know if it's works for 3D(x,y,z) or only for 2D (X,Y) solutions.

@maxicastle Works for 2D, 3D, 4D ... ND.


upd(rustdesk-deb): 1.2.3 -> 1.2.6

Update of rustdesk-deb which is now hits 404 on source, to 1.2.6 with included updates to dependencies, addition of arm64 and armhf, and corrects issue with using breaks instead of replaces/conflicts.

This is fully tested and ready for review.

Upstream bug issue determined: package does not include binary as expected:
https://github.com/rustdesk/rustdesk/issues/8515


Checkout zone

QA Test
https://highfidelity.testrail.net/index.php?/tests/view/7031&group_by=cases:section_id&group_order=asc&group_id=323
Use hifi://dev-content/testing for the test and use the most left check-out zone, that one contains the scripts of this PR.

@thoys or @RebeccaStankus -- can we please have the recycle loop only start when the user is in the checkout zone? Right now, it's spamming error messages every second

This is ready to retest

Testing

Time for cartwheels across the office floor it's a PASS
See testrail


OpenVPN: don't generate dummy certificates

Fixes #492.

SoftEther VPN Patch Acceptance Policy:
http://www.softether.org/5-download/src/9.patch
I choose option 1.

Thank you very much for this great PR. I'd have preferred that the code checks whether there is a server certificate already available and paste it in the sample configuration, else leave the block empty as you did it. But this could be done in a separate PR and this one actually solves Issue #492 .
Thanks and regards

The code already pastes the server certificate (<ca>) to the sample configuration.

Ah now I see what you mean. Cool. Thanks

You're welcome.

Thank you for this good improvement that is good for users who use the certificate authentication function with OpenVPN.
However, I think that this is not goot for users who use the password-based authentication function with OpenVPN. Some OpenVPN Client implementations (e.g. OpenVPN Connect for iOS) requires the dummy certificate in the client configuration file even if the password-based method is specified. Therefore, the dummy certificate must not be removed as the default behavior for existing users.
This does not meet with the following principle.
https://github.com/SoftEtherVPN/SoftEtherVPN/wiki/SoftEther-VPN-Developers-Guideline- (DRAFT)

MUST NOT remove any features from the current SoftEther VPN in the default configuration setting. It is OK to add an opt-out configuration to turn off a specific feature in the configuration file.

The good way is to add new OpenVPN configuration samples for users of the certificate authentication function. In the current code, we have just two existing .ovpn files in the ZIP file generated by the sample configuration generating function.
"XXXXX_openvpn_remote_access_l3.ovpn"
"XXXXX_openvpn_site_to_site_bridge_l2.ovpn"
(XXXXX is the server hostname.)
I recommend NOT to change the behavior on the above two .ovpn files, according to the guideline.
I suppose that adding two additional .ovpn files is a good idea.
"XXXXX_openvpn_remote_access_l3_with_certificate_auth.ovpn"
"XXXXX_openvpn_site_to_site_bridge_l2_with_certificate_auth.ovpn"

Making a copy of "hamcore/openvpn_sample.ovpn" to "hamcore/openvpn_sample_cert_auth.ovpn", and to edit the latter one as you wish is good to realize both keeping existing behavior and adding new behavior. This method does not affect any existing users who are still using password-based authentication with some OpenVPN Clients (e.g. for iOS).

From https://github.com/SoftEtherVPN/SoftEtherVPN/pull/327#issuecomment-380305697:

I think that we should remove them and add setenv CLIENT_CERT 0, as suggested in OpenVPN's documentation.
Setting the environment variable is not required anymore though, as the problem has been fixed in OpenVPN Connect 1.0.1, back in 2013: https://forums.openvpn.net/viewtopic.php?t=11991#p26976

Also, regarding dummy certificates:

They wouldn't be ideal for applications like OpenVPN for Android, as it supports authentication with certificates + credentials.
They can't be used anymore, unless we edit the code so that they are ignored and not used to authenticate the user.

I see. Thank you for your comment.
If there is confidence about this, this is not a practical problem.

we use "setenv CLIENT_CERT 0" for user/password auth with openvpn connect.
no need to have dummy cert


Deploy Agent: API resource location is not registered

Agent version and platform
2.124.0 onwards ...
OS of the machine running the agent? OSX/Windows/Linux...
Windows Server 2008 R2
VSTS type and version
On-Prem TFS
If On-Prem TFS, which release, 2015 RTM/QU1/QU2?
2018 (Version 16.122.27102.1)
What's not working?
When I try to register an agent as part of a deployment group with any version of the agent from 2.124.0 onwards I get the error API resource location [GUID] is not registered on [URL].

This screenshot was taken after trying 2.126.0 and I have tried 2.124.0, 2.125.0, and 2.125.1 which all show the same behaviour. Version 2.123.0 works fine.

Hi Iam having the same issue with version 2.181.0. Ist there a place where i can download 2.123.0 ? or is there a bugfix planned at some point?
We are running TFS 2018 on site.

Hi Iam having the same issue with version 2.181.0. Ist there a place where i can download 2.123.0 ? or is there a bugfix planned at some point?
We are running TFS 2018 on site.


Add 'generate and quit' mode

When serving the generated and plugin files using a different web server, and only updating the metadata every few hours or so, it would be useful if there were a 'generate and quit' way to run this tool.

now you can use juseppe generate cmd