Strange sporadic "Could not get yarn cache folder path" with v3

Description:
We currently encounter sporadic issues in our CI pipelines that make use of setup-node@v3 with Yarn 1 Caching. During setup-node the command yarn cache dir fails for only one (apparently) random project folder with exit code 1, at least the error message Could not get yarn cache folder path for ... is printed, and the build fails. This started around the time we migrated the CI to Node 20 in mid-October.
These issues are not easily reproducible since it works fine most of the time, but then fails in only one very specific place only. The GHA workflow contains multiple very similar jobs that perform the same setup, and of these only one job fails the command in only one particular folder. After one to a few rebuilds the issue has usually resolved itself. Unfortunately, with enough repositories, CI jobs and project folders, it's only a question of time until it pops up again.
Sometimes, the error message is accompanied by what appears to be a V8/nodejs Stacktrace crashing somewhere about v8::internal::Deserializer called by node::contextify::ContextifyScript::New(v8::FunctionCallbackInfo<v8::Value> const&) [node]  with either
# Fatal error in , line 0
# Check failed: current == end_slot_index.

or
# Fatal error in , line 0
# unreachable code

Clearing the caches from Management > Caches in the Actions UI did not help, and after looking through all the code that gets executed until this point and could (or could not) cause such issues, and being unable to find anyone else with the same issue, I'm having a really hard time understanding how this can happen.
In one build I noticed something else rather odd: the debug output of /usr/local/bin/yarn --version was inconsistent and printed 1.18.0 instead of 1.22.19. In all other builds however, they all report the same version (1.22.19).
So my best guess is we're experiencing some sort of very specific setup race condition or so, although I can't say what is causing this. I'm open for any suggestions how to further debug/resolve this.
Action version:
v3, last occurred with 'actions/setup-node@v3' (SHA:1a4442cacd436585916779262731d5b162bc6ec7)
Platform:

[x] Ubuntu
[ ] macOS
[ ] Windows

Runner type:

[x] Hosted
[ ] Self-hosted

Tools version:
ubuntu-latest Runners (Ubuntu 22.04.3)
node: v20.9.0
npm: 10.1.0
yarn: 1.22.19
Repro steps:
Unfortunately the repos where this happens are private, but I have caught one instance with ACTIONS_RUNNER_DEBUG: true and ACTIONS_STEP_DEBUG: true set in this workflow:
ci-build.yaml

name: CI Build
on:
  pull_request:
  push:
    branches: [ master, hotfix/* ]
permissions:
  id-token: write
  checks: write
  packages: write
  actions: read
  contents: write
  issues: read
  pull-requests: write
jobs:
  build-webfrontend:
    runs-on: ubuntu-latest
    env:
      NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
    steps:
      - uses: actions/checkout@v3
      - uses: actions/setup-node@v3
        with:
          node-version: "20"
          cache: 'yarn'
          cache-dependency-path: '**/yarn.lock'
      - run: 'echo "//registry.npmjs.org/:_authToken=${NPM_TOKEN}" >> ~/.npmrc'
      - run: make webfrontend-build
      - uses: actions/upload-artifact@v3
        with:
          name: webfrontend
          path: service/webfrontend/build/

  test-webfrontend:
    runs-on: ubuntu-latest
    env:
      NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
    steps:
      - uses: actions/checkout@v3
      - uses: actions/setup-node@v3
        with:
          node-version: "20"
          cache: 'yarn'
          cache-dependency-path: '**/yarn.lock'
      - run: 'echo "//registry.npmjs.org/:_authToken=${NPM_TOKEN}" >> ~/.npmrc'
      - run: make webfrontend-test
      - name: Upload Test Results (webfrontend)
        if: always()
        uses: actions/upload-artifact@v3
        with:
          name: webfrontend-test-results
          path: "**/webfrontend/junit.xml"

# ... more similar jobs ...

Now here are the logs of test-webfrontend/1_Set up job:
Set up job

2023-11-07T11:43:40.6576920Z ##[debug]Starting: Set up job
2023-11-07T11:43:40.6577618Z Current runner version: '2.311.0'
2023-11-07T11:43:40.6604334Z ##[group]Operating System
2023-11-07T11:43:40.6605198Z Ubuntu
2023-11-07T11:43:40.6605625Z 22.04.3
2023-11-07T11:43:40.6605972Z LTS
2023-11-07T11:43:40.6606452Z ##[endgroup]
2023-11-07T11:43:40.6606940Z ##[group]Runner Image
2023-11-07T11:43:40.6607522Z Image: ubuntu-22.04
2023-11-07T11:43:40.6607968Z Version: 20231030.2.0
2023-11-07T11:43:40.6609082Z Included Software: https://github.com/actions/runner-images/blob/ubuntu22/20231030.2/images/linux/Ubuntu2204-Readme.md
2023-11-07T11:43:40.6610724Z Image Release: https://github.com/actions/runner-images/releases/tag/ubuntu22%2F20231030.2
2023-11-07T11:43:40.6611700Z ##[endgroup]
2023-11-07T11:43:40.6612134Z ##[group]Runner Image Provisioner
2023-11-07T11:43:40.6612770Z 2.0.312.1
2023-11-07T11:43:40.6613356Z ##[endgroup]
2023-11-07T11:43:40.6615214Z ##[group]GITHUB_TOKEN Permissions
2023-11-07T11:43:40.6617302Z Actions: read
2023-11-07T11:43:40.6618244Z Checks: write
2023-11-07T11:43:40.6618711Z Contents: write
2023-11-07T11:43:40.6619162Z Issues: read
2023-11-07T11:43:40.6619619Z Metadata: read
2023-11-07T11:43:40.6620080Z Packages: write
2023-11-07T11:43:40.6620542Z PullRequests: write
2023-11-07T11:43:40.6621114Z ##[endgroup]
2023-11-07T11:43:40.6624984Z Secret source: Actions
2023-11-07T11:43:40.6625846Z ##[debug]Primary repository: private-organization/private-repository
2023-11-07T11:43:40.6626776Z Prepare workflow directory
2023-11-07T11:43:40.6708257Z ##[debug]Creating pipeline directory: '/home/runner/work/private-repository'
2023-11-07T11:43:40.6711979Z ##[debug]Creating workspace directory: '/home/runner/work/private-repository/private-repository'
2023-11-07T11:43:40.6713709Z ##[debug]Update context data
2023-11-07T11:43:40.6718099Z ##[debug]Evaluating job-level environment variables
2023-11-07T11:43:40.7566438Z ##[debug]Evaluating: secrets.NPM_TOKEN
2023-11-07T11:43:40.7573351Z ##[debug]Evaluating Index:
2023-11-07T11:43:40.7576250Z ##[debug]..Evaluating secrets:
2023-11-07T11:43:40.7594028Z ##[debug]..=> Object
2023-11-07T11:43:40.7611594Z ##[debug]..Evaluating String:
2023-11-07T11:43:40.7612720Z ##[debug]..=> 'NPM_TOKEN'
2023-11-07T11:43:40.7618196Z ##[debug]=> '***'
2023-11-07T11:43:40.7621875Z ##[debug]Result: '***'
2023-11-07T11:43:40.7661192Z ##[debug]Evaluating job container
2023-11-07T11:43:40.7664907Z ##[debug]Evaluating job service containers
2023-11-07T11:43:40.7667700Z ##[debug]Evaluating job defaults
2023-11-07T11:43:40.7752512Z Prepare all required actions
2023-11-07T11:43:40.7948837Z Getting action download info
2023-11-07T11:43:41.0202459Z Download action repository 'actions/checkout@v3' (SHA:f43a0e5ff2bd294095638e18286ca9a3d1956744)
2023-11-07T11:43:41.0243083Z ##[debug]Copied action archive '/opt/actionarchivecache/actions_checkout/f43a0e5ff2bd294095638e18286ca9a3d1956744.tar.gz' to '/home/runner/work/_actions/_temp_0e99b505-3a68-41aa-8544-79b62067eff2/3bf1eaf3-b702-48da-8d52-275824b40cff.tar.gz'
2023-11-07T11:43:41.1304104Z ##[debug]Unwrap 'actions-checkout-f43a0e5' to '/home/runner/work/_actions/actions/checkout/v3'
2023-11-07T11:43:41.1435608Z ##[debug]Archive '/home/runner/work/_actions/_temp_0e99b505-3a68-41aa-8544-79b62067eff2/3bf1eaf3-b702-48da-8d52-275824b40cff.tar.gz' has been unzipped into '/home/runner/work/_actions/actions/checkout/v3'.
2023-11-07T11:43:41.1573944Z Download action repository 'actions/setup-node@v3' (SHA:1a4442cacd436585916779262731d5b162bc6ec7)
2023-11-07T11:43:41.1630975Z ##[debug]Copied action archive '/opt/actionarchivecache/actions_setup-node/1a4442cacd436585916779262731d5b162bc6ec7.tar.gz' to '/home/runner/work/_actions/_temp_c2d9dfeb-a5e9-4924-a65a-e361b3a4eb5c/f35200d1-4ba3-4ed4-ad00-39a880065f65.tar.gz'
2023-11-07T11:43:41.2341599Z ##[debug]Unwrap 'actions-setup-node-1a4442c' to '/home/runner/work/_actions/actions/setup-node/v3'
2023-11-07T11:43:41.2612360Z ##[debug]Archive '/home/runner/work/_actions/_temp_c2d9dfeb-a5e9-4924-a65a-e361b3a4eb5c/f35200d1-4ba3-4ed4-ad00-39a880065f65.tar.gz' has been unzipped into '/home/runner/work/_actions/actions/setup-node/v3'.
2023-11-07T11:43:41.2671419Z Download action repository 'actions/upload-artifact@v3' (SHA:a8a3f3ad30e3422c9c7b888a15615d19a852ae32)
2023-11-07T11:43:41.2694520Z ##[debug]Copied action archive '/opt/actionarchivecache/actions_upload-artifact/a8a3f3ad30e3422c9c7b888a15615d19a852ae32.tar.gz' to '/home/runner/work/_actions/_temp_5214a219-533e-4554-86dd-aec804f36c73/9148a6d1-c4a3-4e79-97b9-53a6ce55d3e9.tar.gz'
2023-11-07T11:43:41.2994867Z ##[debug]Unwrap 'actions-upload-artifact-a8a3f3a' to '/home/runner/work/_actions/actions/upload-artifact/v3'
2023-11-07T11:43:41.3051804Z ##[debug]Archive '/home/runner/work/_actions/_temp_5214a219-533e-4554-86dd-aec804f36c73/9148a6d1-c4a3-4e79-97b9-53a6ce55d3e9.tar.gz' has been unzipped into '/home/runner/work/_actions/actions/upload-artifact/v3'.
2023-11-07T11:43:41.3123417Z ##[debug]action.yml for action: '/home/runner/work/_actions/actions/checkout/v3/action.yml'.
2023-11-07T11:43:41.3958299Z ##[debug]action.yml for action: '/home/runner/work/_actions/actions/setup-node/v3/action.yml'.
2023-11-07T11:43:41.4026327Z ##[debug]action.yml for action: '/home/runner/work/_actions/actions/upload-artifact/v3/action.yml'.
2023-11-07T11:43:41.4126261Z ##[debug]Set step '__actions_checkout' display name to: 'Run actions/checkout@v3'
2023-11-07T11:43:41.4128906Z ##[debug]Set step '__actions_setup-node' display name to: 'Run actions/setup-node@v3'
2023-11-07T11:43:41.4132867Z ##[debug]Set step '__run' display name to: 'Run echo "//registry.npmjs.org/:_authToken=${NPM_TOKEN}" >> ~/.npmrc'
2023-11-07T11:43:41.4134920Z ##[debug]Set step '__run_2' display name to: 'Run make webfrontend-test'
2023-11-07T11:43:41.4136977Z ##[debug]Set step '__actions_upload-artifact' display name to: 'Upload Test Results (webfrontend)'
2023-11-07T11:43:41.4138479Z Complete job name: test-webfrontend
2023-11-07T11:43:41.4161142Z ##[debug]Collect running processes for tracking orphan processes.
2023-11-07T11:43:41.4384275Z ##[debug]Finishing: Set up job

And then it fails in test-webfrontend/3_Run actionssetup-node@v3:
Run actionssetup-node@v3 with error

2023-11-07T11:43:42.9003997Z ##[debug]Evaluating condition for step: 'Run actions/setup-node@v3'
2023-11-07T11:43:42.9007657Z ##[debug]Evaluating: success()
2023-11-07T11:43:42.9008259Z ##[debug]Evaluating success:
2023-11-07T11:43:42.9008972Z ##[debug]=> true
2023-11-07T11:43:42.9009656Z ##[debug]Result: true
2023-11-07T11:43:42.9010574Z ##[debug]Starting: Run actions/setup-node@v3
2023-11-07T11:43:42.9038655Z ##[debug]Register post job cleanup for action: actions/setup-node@v3
2023-11-07T11:43:42.9056589Z ##[debug]Loading inputs
2023-11-07T11:43:42.9076162Z ##[debug]Evaluating: (((github.server_url == 'https://github.com') && github.token) || '')
2023-11-07T11:43:42.9077055Z ##[debug]Evaluating Or:
2023-11-07T11:43:42.9081498Z ##[debug]..Evaluating And:
2023-11-07T11:43:42.9086163Z ##[debug]....Evaluating Equal:
2023-11-07T11:43:42.9087682Z ##[debug]......Evaluating Index:
2023-11-07T11:43:42.9088171Z ##[debug]........Evaluating github:
2023-11-07T11:43:42.9088699Z ##[debug]........=> Object
2023-11-07T11:43:42.9089123Z ##[debug]........Evaluating String:
2023-11-07T11:43:42.9089663Z ##[debug]........=> 'server_url'
2023-11-07T11:43:42.9090492Z ##[debug]......=> 'https://github.com'
2023-11-07T11:43:42.9091013Z ##[debug]......Evaluating String:
2023-11-07T11:43:42.9091487Z ##[debug]......=> 'https://github.com'
2023-11-07T11:43:42.9096001Z ##[debug]....=> true
2023-11-07T11:43:42.9096655Z ##[debug]....Evaluating Index:
2023-11-07T11:43:42.9097109Z ##[debug]......Evaluating github:
2023-11-07T11:43:42.9097593Z ##[debug]......=> Object
2023-11-07T11:43:42.9098015Z ##[debug]......Evaluating String:
2023-11-07T11:43:42.9098465Z ##[debug]......=> 'token'
2023-11-07T11:43:42.9099241Z ##[debug]....=> '***'
2023-11-07T11:43:42.9099841Z ##[debug]..=> '***'
2023-11-07T11:43:42.9100576Z ##[debug]=> '***'
2023-11-07T11:43:42.9106924Z ##[debug]Expanded: ((('https://github.com' == 'https://github.com') && '***') || '')
2023-11-07T11:43:42.9107920Z ##[debug]Result: '***'
2023-11-07T11:43:42.9109579Z ##[debug]Loading env
2023-11-07T11:43:42.9117043Z ##[group]Run actions/setup-node@v3
2023-11-07T11:43:42.9117502Z with:
2023-11-07T11:43:42.9117814Z   node-version: 20
2023-11-07T11:43:42.9118138Z   cache: yarn
2023-11-07T11:43:42.9118500Z   cache-dependency-path: **/yarn.lock
2023-11-07T11:43:42.9118975Z   always-auth: false
2023-11-07T11:43:42.9119340Z   check-latest: false
2023-11-07T11:43:42.9119882Z   token: ***
2023-11-07T11:43:42.9120189Z env:
2023-11-07T11:43:42.9120593Z   NPM_TOKEN: ***
2023-11-07T11:43:42.9120922Z ##[endgroup]
2023-11-07T11:43:43.1658305Z ##[debug]isExplicit:
2023-11-07T11:43:43.1665777Z ##[debug]explicit? false
2023-11-07T11:43:43.1674294Z ##[debug]isExplicit: 14.21.3
2023-11-07T11:43:43.1676393Z ##[debug]explicit? true
2023-11-07T11:43:43.1679713Z ##[debug]isExplicit: 16.20.2
2023-11-07T11:43:43.1681858Z ##[debug]explicit? true
2023-11-07T11:43:43.1684360Z ##[debug]isExplicit: 18.18.2
2023-11-07T11:43:43.1686446Z ##[debug]explicit? true
2023-11-07T11:43:43.1688911Z ##[debug]isExplicit: 20.9.0
2023-11-07T11:43:43.1692079Z ##[debug]explicit? true
2023-11-07T11:43:43.1695703Z ##[debug]evaluating 4 versions
2023-11-07T11:43:43.1723570Z ##[debug]matched: 20.9.0
2023-11-07T11:43:43.1732932Z ##[debug]checking cache: /opt/hostedtoolcache/node/20.9.0/x64
2023-11-07T11:43:43.1734359Z ##[debug]Found tool in cache node 20.9.0 x64
2023-11-07T11:43:43.1737408Z Found in cache @ /opt/hostedtoolcache/node/20.9.0/x64
2023-11-07T11:43:43.1739590Z ::group::Environment details
2023-11-07T11:43:43.1740033Z ##[group]Environment details
2023-11-07T11:43:43.8937028Z node: v20.9.0
2023-11-07T11:43:43.8938129Z npm: 10.1.0
2023-11-07T11:43:43.8938517Z yarn: 1.22.19
2023-11-07T11:43:43.8939300Z ::endgroup::
2023-11-07T11:43:43.8939631Z ##[endgroup]
2023-11-07T11:43:43.8951679Z ##[debug]followSymbolicLinks 'true'
2023-11-07T11:43:43.8952673Z ##[debug]implicitDescendants 'true'
2023-11-07T11:43:43.8955271Z ##[debug]matchDirectories 'true'
2023-11-07T11:43:43.8956047Z ##[debug]omitBrokenSymbolicLinks 'true'
2023-11-07T11:43:43.8965082Z ##[debug]Search path '/home/runner/work/private-repository/private-repository'
2023-11-07T11:43:44.0603605Z [command]/usr/local/bin/yarn --version
2023-11-07T11:43:44.0604864Z [command]/usr/local/bin/yarn --version
2023-11-07T11:43:44.0606342Z [command]/usr/local/bin/yarn --version
2023-11-07T11:43:44.0607731Z [command]/usr/local/bin/yarn --version
2023-11-07T11:43:44.0608579Z [command]/usr/local/bin/yarn --version
2023-11-07T11:43:44.0609449Z [command]/usr/local/bin/yarn --version
2023-11-07T11:43:44.4698330Z 1.22.19
2023-11-07T11:43:44.5425956Z ##[debug]Consumed yarn version is 1.22.19 (working dir: "/home/runner/work/private-repository/private-repository/service/microfrontend")
2023-11-07T11:43:44.5436488Z [command]/usr/local/bin/yarn cache dir
2023-11-07T11:43:44.6228683Z 1.22.19
2023-11-07T11:43:44.6647428Z ##[debug]Consumed yarn version is 1.22.19 (working dir: "/home/runner/work/private-repository/private-repository/service")
2023-11-07T11:43:44.6658255Z [command]/usr/local/bin/yarn cache dir
2023-11-07T11:43:44.6822781Z 1.22.19
2023-11-07T11:43:44.6823634Z 1.22.19
2023-11-07T11:43:44.6937502Z ##[debug]Consumed yarn version is 1.22.19 (working dir: "/home/runner/work/private-repository/private-repository/service/library-utils")
2023-11-07T11:43:44.6973852Z [command]/usr/local/bin/yarn cache dir
2023-11-07T11:43:44.7065675Z 1.22.19
2023-11-07T11:43:44.7066390Z 1.22.19
2023-11-07T11:43:44.7201400Z ##[debug]Consumed yarn version is 1.22.19 (working dir: "/home/runner/work/private-repository/private-repository/service/library")
2023-11-07T11:43:44.7218325Z [command]/usr/local/bin/yarn cache dir
2023-11-07T11:43:44.7427305Z ##[debug]Consumed yarn version is 1.22.19 (working dir: "/home/runner/work/private-repository/private-repository/service/webfrontend")
2023-11-07T11:43:44.7442250Z [command]/usr/local/bin/yarn cache dir
2023-11-07T11:43:44.7518826Z ##[debug]Consumed yarn version is 1.22.19 (working dir: "/home/runner/work/private-repository/private-repository/service/microfrontend-wrapper")
2023-11-07T11:43:44.7526882Z [command]/usr/local/bin/yarn cache dir
2023-11-07T11:43:45.5178973Z /home/runner/.cache/yarn/v6
2023-11-07T11:43:45.5701292Z ##[debug]yarn's cache folder "/home/runner/.cache/yarn/v6" configured for the directory "/home/runner/work/private-repository/private-repository/service/library-utils"
2023-11-07T11:43:45.6308358Z /home/runner/.cache/yarn/v6
2023-11-07T11:43:45.6917922Z ##[debug]yarn's cache folder "/home/runner/.cache/yarn/v6" configured for the directory "/home/runner/work/private-repository/private-repository/service/webfrontend"
2023-11-07T11:43:45.7178811Z /home/runner/.cache/yarn/v6
2023-11-07T11:43:45.7500285Z ##[debug]yarn's cache folder "/home/runner/.cache/yarn/v6" configured for the directory "/home/runner/work/private-repository/private-repository/service"
2023-11-07T11:43:45.7822267Z /home/runner/.cache/yarn/v6
2023-11-07T11:43:45.8324690Z ##[debug]yarn's cache folder "/home/runner/.cache/yarn/v6" configured for the directory "/home/runner/work/private-repository/private-repository/service/library"
2023-11-07T11:43:45.8961896Z /home/runner/.cache/yarn/v6
2023-11-07T11:43:45.9307755Z ##[debug]yarn's cache folder "/home/runner/.cache/yarn/v6" configured for the directory "/home/runner/work/private-repository/private-repository/service/microfrontend-wrapper"
2023-11-07T11:43:47.0912218Z ##[error]Could not get yarn cache folder path for /home/runner/work/private-repository/private-repository/service/microfrontend
2023-11-07T11:43:47.0985552Z ##[debug]Node Action run completed with exit code 1
2023-11-07T11:43:47.0990738Z ##[debug]Save intra-action state SETUP_NODE_CACHE_PACKAGE_MANAGER = yarn
2023-11-07T11:43:47.0993089Z ##[debug]Set output node-version = v20.9.0
2023-11-07T11:43:47.0996878Z ##[debug]Finishing: Run actions/setup-node@v3

Compare this to the start of build-webfrontend/3_Run actionssetup-node@v3 where the very same command works just fine:
Run actionssetup-node@v3 without error

2023-11-07T11:43:42.5045134Z ##[debug]Evaluating condition for step: 'Run actions/setup-node@v3'
2023-11-07T11:43:42.5048077Z ##[debug]Evaluating: success()
2023-11-07T11:43:42.5048672Z ##[debug]Evaluating success:
2023-11-07T11:43:42.5049377Z ##[debug]=> true
2023-11-07T11:43:42.5050034Z ##[debug]Result: true
2023-11-07T11:43:42.5050928Z ##[debug]Starting: Run actions/setup-node@v3
2023-11-07T11:43:42.5081732Z ##[debug]Register post job cleanup for action: actions/setup-node@v3
2023-11-07T11:43:42.5101416Z ##[debug]Loading inputs
2023-11-07T11:43:42.5122474Z ##[debug]Evaluating: (((github.server_url == 'https://github.com') && github.token) || '')
2023-11-07T11:43:42.5123431Z ##[debug]Evaluating Or:
2023-11-07T11:43:42.5127668Z ##[debug]..Evaluating And:
2023-11-07T11:43:42.5133686Z ##[debug]....Evaluating Equal:
2023-11-07T11:43:42.5135490Z ##[debug]......Evaluating Index:
2023-11-07T11:43:42.5136070Z ##[debug]........Evaluating github:
2023-11-07T11:43:42.5136687Z ##[debug]........=> Object
2023-11-07T11:43:42.5137202Z ##[debug]........Evaluating String:
2023-11-07T11:43:42.5137841Z ##[debug]........=> 'server_url'
2023-11-07T11:43:42.5138743Z ##[debug]......=> 'https://github.com'
2023-11-07T11:43:42.5139381Z ##[debug]......Evaluating String:
2023-11-07T11:43:42.5139947Z ##[debug]......=> 'https://github.com'
2023-11-07T11:43:42.5144728Z ##[debug]....=> true
2023-11-07T11:43:42.5145412Z ##[debug]....Evaluating Index:
2023-11-07T11:43:42.5145932Z ##[debug]......Evaluating github:
2023-11-07T11:43:42.5146457Z ##[debug]......=> Object
2023-11-07T11:43:42.5146925Z ##[debug]......Evaluating String:
2023-11-07T11:43:42.5147428Z ##[debug]......=> 'token'
2023-11-07T11:43:42.5148875Z ##[debug]....=> '***'
2023-11-07T11:43:42.5149579Z ##[debug]..=> '***'
2023-11-07T11:43:42.5150571Z ##[debug]=> '***'
2023-11-07T11:43:42.5158222Z ##[debug]Expanded: ((('https://github.com' == 'https://github.com') && '***') || '')
2023-11-07T11:43:42.5159447Z ##[debug]Result: '***'
2023-11-07T11:43:42.5161213Z ##[debug]Loading env
2023-11-07T11:43:42.5169326Z ##[group]Run actions/setup-node@v3
2023-11-07T11:43:42.5169758Z with:
2023-11-07T11:43:42.5170057Z   node-version: 20
2023-11-07T11:43:42.5170392Z   cache: yarn
2023-11-07T11:43:42.5170899Z   cache-dependency-path: **/yarn.lock
2023-11-07T11:43:42.5171427Z   always-auth: false
2023-11-07T11:43:42.5171834Z   check-latest: false
2023-11-07T11:43:42.5172389Z   token: ***
2023-11-07T11:43:42.5172700Z env:
2023-11-07T11:43:42.5173132Z   NPM_TOKEN: ***
2023-11-07T11:43:42.5173496Z ##[endgroup]
2023-11-07T11:43:42.8325370Z ##[debug]isExplicit:
2023-11-07T11:43:42.8397876Z ##[debug]explicit? false
2023-11-07T11:43:42.8400290Z ##[debug]isExplicit: 14.21.3
2023-11-07T11:43:42.8402350Z ##[debug]explicit? true
2023-11-07T11:43:42.8404354Z ##[debug]isExplicit: 16.20.2
2023-11-07T11:43:42.8436608Z ##[debug]explicit? true
2023-11-07T11:43:42.8437562Z ##[debug]isExplicit: 18.18.2
2023-11-07T11:43:42.8438358Z ##[debug]explicit? true
2023-11-07T11:43:42.8439105Z ##[debug]isExplicit: 20.9.0
2023-11-07T11:43:42.8439878Z ##[debug]explicit? true
2023-11-07T11:43:42.8440653Z ##[debug]evaluating 4 versions
2023-11-07T11:43:42.8441572Z ##[debug]matched: 20.9.0
2023-11-07T11:43:42.8442433Z ##[debug]checking cache: /opt/hostedtoolcache/node/20.9.0/x64
2023-11-07T11:43:42.8443450Z ##[debug]Found tool in cache node 20.9.0 x64
2023-11-07T11:43:42.8444153Z Found in cache @ /opt/hostedtoolcache/node/20.9.0/x64
2023-11-07T11:43:42.8445105Z ::group::Environment details
2023-11-07T11:43:42.8445572Z ##[group]Environment details
2023-11-07T11:43:46.3695280Z node: v20.9.0
2023-11-07T11:43:46.3696376Z npm: 10.1.0
2023-11-07T11:43:46.3697531Z yarn: 1.22.19
2023-11-07T11:43:46.3698630Z ::endgroup::
2023-11-07T11:43:46.3699043Z ##[endgroup]
2023-11-07T11:43:46.3741355Z ##[debug]followSymbolicLinks 'true'
2023-11-07T11:43:46.3743128Z ##[debug]implicitDescendants 'true'
2023-11-07T11:43:46.3744458Z ##[debug]matchDirectories 'true'
2023-11-07T11:43:46.3746228Z ##[debug]omitBrokenSymbolicLinks 'true'
2023-11-07T11:43:46.3757885Z ##[debug]Search path '/home/runner/work/private-repository/private-repository'
2023-11-07T11:43:46.5754300Z [command]/usr/local/bin/yarn --version
2023-11-07T11:43:46.5760862Z [command]/usr/local/bin/yarn --version
2023-11-07T11:43:46.5764553Z [command]/usr/local/bin/yarn --version
2023-11-07T11:43:46.5767907Z [command]/usr/local/bin/yarn --version
2023-11-07T11:43:46.5771188Z [command]/usr/local/bin/yarn --version
2023-11-07T11:43:46.5774583Z [command]/usr/local/bin/yarn --version
2023-11-07T11:43:47.1231648Z 1.22.19
2023-11-07T11:43:47.1746162Z 1.22.19
2023-11-07T11:43:47.1799246Z ##[debug]Consumed yarn version is 1.22.19 (working dir: "/home/runner/work/private-repository/private-repository/service/microfrontend")
2023-11-07T11:43:47.1814683Z [command]/usr/local/bin/yarn cache dir
2023-11-07T11:43:47.1952668Z 1.22.19
2023-11-07T11:43:47.1953522Z 1.22.19
2023-11-07T11:43:47.1954149Z 1.22.19
2023-11-07T11:43:47.2243607Z ##[debug]Consumed yarn version is 1.22.19 (working dir: "/home/runner/work/private-repository/private-repository/service/microfrontend-wrapper")
2023-11-07T11:43:47.2267594Z [command]/usr/local/bin/yarn cache dir
2023-11-07T11:43:47.2577740Z ##[debug]Consumed yarn version is 1.22.19 (working dir: "/home/runner/work/private-repository/private-repository/service/webfrontend")
2023-11-07T11:43:47.2580755Z ##[debug]Consumed yarn version is 1.22.19 (working dir: "/home/runner/work/private-repository/private-repository/service/library")
2023-11-07T11:43:47.2583460Z ##[debug]Consumed yarn version is 1.22.19 (working dir: "/home/runner/work/private-repository/private-repository/service/library-utils")
2023-11-07T11:43:47.2614624Z [command]/usr/local/bin/yarn cache dir
2023-11-07T11:43:47.2619847Z [command]/usr/local/bin/yarn cache dir
2023-11-07T11:43:47.2624789Z [command]/usr/local/bin/yarn cache dir
2023-11-07T11:43:47.2910735Z 1.22.19
2023-11-07T11:43:47.3200340Z ##[debug]Consumed yarn version is 1.22.19 (working dir: "/home/runner/work/private-repository/private-repository/service")
2023-11-07T11:43:47.3215325Z [command]/usr/local/bin/yarn cache dir
2023-11-07T11:43:47.9026477Z /home/runner/.cache/yarn/v6
2023-11-07T11:43:47.9790941Z ##[debug]yarn's cache folder "/home/runner/.cache/yarn/v6" configured for the directory "/home/runner/work/private-repository/private-repository/service/microfrontend"
2023-11-07T11:43:48.0026024Z /home/runner/.cache/yarn/v6
2023-11-07T11:43:48.0425940Z ##[debug]yarn's cache folder "/home/runner/.cache/yarn/v6" configured for the directory "/home/runner/work/private-repository/private-repository/service"
2023-11-07T11:43:48.0831076Z /home/runner/.cache/yarn/v6
2023-11-07T11:43:48.1041621Z /home/runner/.cache/yarn/v6
2023-11-07T11:43:48.1261033Z ##[debug]yarn's cache folder "/home/runner/.cache/yarn/v6" configured for the directory "/home/runner/work/private-repository/private-repository/service/webfrontend"
2023-11-07T11:43:48.1311110Z /home/runner/.cache/yarn/v6
2023-11-07T11:43:48.1415387Z /home/runner/.cache/yarn/v6
2023-11-07T11:43:48.1550742Z ##[debug]yarn's cache folder "/home/runner/.cache/yarn/v6" configured for the directory "/home/runner/work/private-repository/private-repository/service/library"
2023-11-07T11:43:48.1699081Z ##[debug]yarn's cache folder "/home/runner/.cache/yarn/v6" configured for the directory "/home/runner/work/private-repository/private-repository/service/microfrontend-wrapper"
2023-11-07T11:43:48.1824172Z ##[debug]yarn's cache folder "/home/runner/.cache/yarn/v6" configured for the directory "/home/runner/work/private-repository/private-repository/service/library-utils"
2023-11-07T11:43:48.1827292Z ##[debug]followSymbolicLinks 'true'
2023-11-07T11:43:48.1839324Z ##[debug]followSymbolicLinks 'true'
2023-11-07T11:43:48.1840591Z ##[debug]implicitDescendants 'true'
2023-11-07T11:43:48.1841831Z ##[debug]matchDirectories 'true'
2023-11-07T11:43:48.1843937Z ##[debug]omitBrokenSymbolicLinks 'true'
2023-11-07T11:43:48.1864822Z ##[debug]Search path '/home/runner/work/private-repository/private-repository'
2023-11-07T11:43:48.2190989Z ##[debug]/home/runner/work/private-repository/private-repository/service/library/yarn.lock
2023-11-07T11:43:48.2356218Z ##[debug]/home/runner/work/private-repository/private-repository/service/library-utils/yarn.lock
2023-11-07T11:43:48.2700733Z ##[debug]/home/runner/work/private-repository/private-repository/service/microfrontend/yarn.lock
2023-11-07T11:43:48.2753487Z ##[debug]/home/runner/work/private-repository/private-repository/service/microfrontend-wrapper/yarn.lock
2023-11-07T11:43:48.3601324Z ##[debug]/home/runner/work/private-repository/private-repository/service/webfrontend/yarn.lock
2023-11-07T11:43:48.3638358Z ##[debug]/home/runner/work/private-repository/private-repository/service/yarn.lock
2023-11-07T11:43:48.3645588Z ##[debug]Found 6 files to hash.
--- snip ---

Expected behavior:
Action completes setting up the cache and not failing the build.
Actual behavior:
Action nondeterministically fails the build due to the issue described.

Thank you for the detailed issue description! We will investigate the problem and come back to you with the details.

yarn cache apparently not working for the same Ubuntu / hosted setup with node 20 and actions v4
Configuration:
- uses: actions/setup-node@v4
  with:
    node-version: ${{ matrix.node-version }}
    cache: 'yarn'

Log:
actions/setup-node@v4

node: v20.10.0
npm: 10.2.3
yarn: 4.0.2

/usr/local/bin/yarn --version
4.0.2
/usr/local/bin/yarn config get cacheFolder
/home/runner/.yarn/berry/cache
/usr/local/bin/yarn config get enableGlobalCache
true
yarn cache is not found

@frederic-saunier Unfortunately not. As far as I know upgrading to v4 did reduce the frequency, but the problem is definitely still there.

Hello!
I'm facing a similar issue, however not with setup-node. I'm facing this with Nx/pnpm/Atlassian Bamboo. There is an issue filed with nodejs for similar crashes (nodejs/node#51555). So I'm presuming this may be occuring outside of setup-node.

I think I am running into this as well, but it doesn't seem to be intermittent though

I'm still running into this issue, I've tried the above steps but no dice.

We're seeing these sporadic failures too

I'm guessing there are probably multiple causes of this issue, but I managed to fix it on my own repositories by specifying the yarn.lock file
In other words, I changed
cache-dependency-path: nested-directory/
to
cache-dependency-path: nested-directory/yarn.lock
I see someone above already specified yarn.lock so this probably isn't the only reason for failure, but it worked for me.

Hello @xcq1, Thank you for bringing this issue to our attention. We have thoroughly investigated the situation and were unable to reproduce the problem you're experiencing with the actions/setup-node workflow.
We have successfully run the setup with caching for Yarn dependencies without encountering the error. It seems that the issue might be environment-specific or related to a particular configuration.
Based on the logs and the setup-node current logic, the process for retrieving the Yarn cache directory is working correctly in most cases, but it encounters an error for the specific project directory /home/runner/work/private-repository/private-repository/service/microfrontend. As per the investigation the setup-node logic successfully retrieves the Yarn version (1.22.19) and correctly decides to use the yarn cache dir command. For the directory /home/runner/work/private-repository/private-repository/service/microfrontend, the process fails with the error message: Could not get yarn cache folder path for /home/runner/work/private-repository/private-repository/service/microfrontend. This indicates that the command to fetch the cache directory is likely not returning the expected output for this specific project directory.
Please find the below screenshot for reference.
Potential Causes:

the microfrontend directory should properly set up and contains a valid yarn.lock file. If it's missing or incorrectly configured, it might affect how Yarn resolves its cache directory.
If there are any permission-related issues that might be preventing Yarn from accessing or creating the cache in that directory. Certain environment variables or configurations might affect how Yarn behaves.
We should make sure that any relevant configurations are consistent across the projects.

If you could provide more details with public repro link about your setup or any specific error messages you're receiving, it would be helpful for further investigation.

Hello @xcq1, Please provide more details with public repro link about your setup or any specific error messages you're receiving, it would be helpful for further investigation as we are unable to reproduce the issue from our end.

Hello @xcq1, gentle remider.. to get more details with public repro link about your setup or any specific error messages you're receiving, it would be helpful for further investigation as we are unable to reproduce the issue from our end.

Hello @xcq1, We are proceeding to close this issue after two reminders as we didn't hear anything from a long time.
Please feel free to reach us in case of any concerns or assistance needed to reopen this issue.


Provide example for Wiznet W5500-EVB-Pico

Disclaimer: I'm a complete newcomer to embedded Rust, so I'm in way over my head here - feel free to ignore..
I would like to run picoserve on a Wiznet W5500-EVB-Pico which provides a hardware ethernet connection for an RP2040 device. There is a simple echo server example for this in the embassy repo.
I tried simply mashing together that example with the set_pico_w_led example in picoserve, but rapidly reached the limit of my abilities. I think part of the problem is that the W5500 driver only operates at a very low level, but I could be talking nonsense.

I unfortunately don't have a Wiznet W5500-EVB-Pico, but looking at the echo server example, if you replace the loop from lines 108 to 126 with a call to picoserve::serve, it should Just Work™

Cool .. I'll have a go. At the moment, I don't have anything; I was attempting to replace the WiFi code from your pico w example, but as you point out, it will probably be easier to modify the original example.

errors concerning the use of the make_static!(make_app()) call

Due to a change in the compiler, make_static no longer works. Look at the new versions of the picoserve examples for the new way.

the use of #![feature(type_alias_impl_trait)] caused errors. I think this means I should be using nightly? Haven't figured out how to use nightly yet.

Yes, you do need to use the nightly compiler. Copy the "rust-toolchain" file from the embassy examples of picoserve, and have a look at https://rust-lang.github.io/rustup/overrides.html#the-toolchain-file

Compiler complained the the type of TcpSocket expected by picoserve is different to that created by the embassy_net_wiznet implementation. Looking at the Cargo.toml files, picoserve uses 0.4.0 as the base embassy_net version, whereas the current embassy implementation uses 0.5.0

I've recently updated picoserve to use embassy_net 0.5, you'll need to update your Cargo.toml file

so I think I'll leave it until my understanding of rust has improved ...

No worries, Rust definitely has a learning curve, and bare metal programming has its own challenges. If you've not done so already, I'd recommend reading The Book and doing Rustlings

OK,   I managed to get the hello_world sample running on a W5500-Evb-pico board. To do this ..

I had to make it a new example in my picoserve repo fork.
update to 0.13.1 version - I set the version in the embassy examples branch to be sure I was relying on published crates
update to latest embassy-net versions
use dhcp4 to get an IP address
the usual zillions of variations of code .. until it compiled
add defmt support
replace the hello_world approach of using the web_task to spawn instances in a loop in favour of explicitly creating a socket and passing to a picoserve::serve call, as in the embassy example.

If I didn't do (6),  logging showed DHCP succeeding, then server threads spawning .. but all went dead  .. could't ping the interface. Haven't found out why yet ..

Then I eventually managed to build a version of the set_pico_w_led example, but with a few changes.

Added a channel that is used to communicate from the web app to a control task.
Created a Command type that is used to communicate intent to the control task
created a control task that receives commands from the Channel

There were two main difficulties with developing this code:

How to add in the state to hold the communication channel
Getting the tasks correct - I went round several houses getting the control channel / task working

(1) - I tried to re-use the pattern in set_pico_w_led, by creating a state to hold a Pin to represent the LED, but I could not get it to compile. There seemed to be some clash between an existing definition of State somewhere in the embassy W5500 code, and the State required by picoserve; it was beyond my ability to debug.
Then I had a trial of GitHub CoPilot, and in frustration asked it to help me add in state. To my jaw-dropping surprise, it suggested adding a field into the AppProps struct, and this approach seems to have worked! However, I feel I'm missing some sort of point here, so I do need to understand how AppStates work. AppProps now looks like this:
struct AppProps {
    source: Sender<'static, CriticalSectionRawMutex, InstrCmd, 10>,
}

impl AppBuilder for AppProps {
    type PathRouter = impl picoserve::routing::PathRouter;

    fn build_app(self) -> Router<<AppProps as AppBuilder>::PathRouter> {
            picoserve::Router::new()
            .route(
                "/",
                get_service(picoserve::response::File::html(include_str!("index.html"))),
            )
            .route(
                "/index.css",
                get_service(picoserve::response::File::css(include_str!("index.css"))),
            )
            .route(
                "/index.js",
                get_service(picoserve::response::File::javascript(include_str!(
                    "index.js"
                ))),
            )
            .route(
                ("/set_led", parse_path_segment()),
                get(
                    move |led_is_on | async move {
                        self.source.send(InstrCmd::SetLed(led_is_on)).await;
                        DebugValue(led_is_on)
                    },
                ),
            )
    }
}

and gets used like this:
    // create a channel for sending instructions to the main loop

    static CHANNEL : Channel::<CriticalSectionRawMutex, InstrCmd, 10> = Channel::new();
    let sender                          = CHANNEL.sender();
    let receiver                        = CHANNEL.receiver();
    let app_props                       = AppProps { source  : sender.clone() };

    let app = make_static!(AppRouter<AppProps>, picoserve::AppBuilder::build_app(app_props));

I also had a lot of inconsistent problems where the web app was not responding to the ON/OFF commands, although the web page serving part seemed OK. In fact I think that Chrome was not sending the requests properly! curl from a console works fine. No idea what's going on, but in the end it wasn't the code, I think.


About train detail

You've done a great job! When I trained the MAR model, I noticed that if the training steps are insufficient, the output images can be quite similar to your results.So I suspect that the issue might be due to insufficient training epochs. The authors of MAR have pointed out that at least 1,000 epochs of training are needed to start seeing textural images.

i

sry my wrong


Reference for Vitis AI Quantization

Could I ask for the reference publication for quantization algorithm in Vitis AI? This is not mentioned in Vitis AI User Guide. I want to know which paper should I refer to when I use Vitis AI quantization.
If possible, the reference for pruning as well.
Many thanks.

Hi @FrankXinqi
I'm afraid there is no reference for quantization algorithm. It's recommended that you can refer to the following 2 documents to use the quantization tools.
UG1414: https://www.xilinx.com/html_docs/vitis_ai/1_2/uim1570695919827.html
UG1333: https://www.xilinx.com/support/documentation/sw_manuals/vitis_ai/1_2/ug1333-ai-optimizer.pdf

Many thanks @qianglin-xlnx
I was aware of the two documents. The reason I am asking for that is that VitisAI quantization does not perform desired result to reduce model size in a lot.
If no refernce can be provided, please refer to #150. I am wondering if the algorithm only quantize FC layers, rather than CNN and FC layers.

Thanks for the information. If there are updates about quantization algorithms used in Vitis AI, please let me know.
I close this issue now.


Add status filter switch

This adds a --status switch to filter the output of 'runs list' by the run status.

+1 looks good!


Brush chart does not have .locale() method

I'm using a Line chart combined with Brush, and want to display data in custom locale. Line chart, as some of others, has a .locale() method, and is fine, but Brush does not.
So, when you render your Line data in, let's say, .locale('da-DK'), the Brush labels are still in English, which is confusing.

Hi @creage , thanks for filling the issue!
That's legit, the brush should have a locale as the line chart.

Hi! I could tackle this the next week and add the locale() method to every chart that is missing it.
Mind making a list of which charts are missing it?

According to API docs, these charts don't have a .locale() method
Bar
Brush
Donut
Grouped-bar
Legend
Mini-tooltip
Sparkline
Stacked-bar
Step

Ah, it should not be that many.
Locale only make sense when the timeAxis is being used, so we will need it on the Brush and the Stacked Area charts.
Thanks a lot @martinmanzo !!

Thanks to both!
I'll tackle this issue this week.

Thanks a lot @martinmanzo !

Made a pull request!
While making the change I saw that Stacked Area already had a locale method so assumed that you meant Stacked Bar and added locale to it.
Let me know if that wrong to change it back.
Regards!

I actually wasn't, but it makes sense!
Thankss


Use ui.Proceed instead of log.AskF

What is the purpose of this change? What does it change?
Adding interactive mode to commands has brought along a library that provides UI elements to ask questions to users. It makes sense to use these elements where we ask the user for confirmation. This simplifies client code and makes sure the experience is consistent across commands.
Was the change discussed in an issue?
No.
How to test changes?
Any of the delete (app, component, etc.) commands that ask for confirmation should still work as before, though the UI might be a little different.

Has the handling of the service properties also changed?

:white_check_mark: odo build 1613 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/7932514b73 by @metacosm)

Has the handling of the service properties also changed?

Not sure I understand the question…

Has the handling of the service properties also changed?

Not sure I understand the question…

Never mind, I got mixed up when looking at the changes to the service parameter UI handling - they make sense now

:white_check_mark: odo build 1616 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/b9ec915881 by @metacosm)

:white_check_mark: odo build 1638 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/2f907dd5f6 by @metacosm)

@metacosm works fine locally, merging


[Windows] Tray icon pixelated and menu always visible

Hi,
I used Sleek on Windows 10 before the update and am still using it after the update.
Very superficial feedback here:

The favicon type logo is pixelated
I think it was possible to hide the menu bar previously, but now it isn't.

I hope some of that is useful. Sleek is great, thanks so much for developing this!
Fred
Originally posted by @fredofredofred in https://github.com/ransome1/sleek/discussions/562#discussioncomment-7481273

@fredofredofred the pixelation issue should be resolved in this pre-release, please feel free to give it a quick test: https://github.com/ransome1/sleek/releases/tag/v2.0.3-rc.2

I just downloaded and ran sleek-2.0.3-rc.2-win.exe
The icon on the .exe file looks smooth.
However the icon which appears on the taskbar and top left of the window still looks pixellated.
The screenshot of the taskbar has the current version from the Microsoft Store running next to sleek-2.0.3-rc.2-win.exe. On my other computer I re-installed the previous version 1.3.1 which doesn't have this issue (as a temporary measure).
I hope that's helpful.
Fred

Top screenshot is the .exe file, the next one is showing the icon on corner of the window, the bottom is the task bar.

@fredofredofred can you check, if this still happens in this pre-release? https://github.com/ransome1/sleek/releases/tag/v2.0.3-rc.3

@ransome1 thanks for hiding the menu bar on Linux, I was about to report this

@ransome1
Logos look good everywhere and the menu is gone, but it appears when I press 'Alt'.

So it all looks good to me.

Logos look good everywhere and the menu is gone, but it appears when I press 'Alt'.

That's actually the old behavior of sleek v1.3.1 and had been explicitly requested in another issue. I kind of support this behavior, since it makes the app looks significantly more tidy.
But as for the issue at hand, I'm closing here. Feel free to re-open, if you think there is still stuff to do.


CSV is not escaped.

CSV data is not escaped correctly, a quote character (") should be escaped as a double quote("").
Example:
"The "elephant" in the room. "
Should be:
"The ""elephant"" in the room. "
It should also be un-escaped before import.

If you mean from Json to CSV, yes we have an issue there
But {"The ""elephant"" in the room. "} is not a valid Json I think it should be {"The "elephant" in the room. "} when exporting to CSV will be {The "elephant" in the room. }
Please correct me if I am wrong


add internal interface to Shopify's GraphQL API

This is a simple GraphQL implementation to handle GraphQL Queries against Shopify API using HTTPoison library as client, this initial implementation consists of hitting Shopify GraphQL and returning the response in a tuple {:ok, %Response{}} | {:error, %Response{}} containing the response and metadata(actualQueryCost, throttleStatus).
Transforms HTTPoison.Response into a %GraphQL.Response struct:
 %GraphQL.Response{
          response: Map.t(),
          metadata: Map.t(),
          status_code: Integer.t()
        }.

Testing from console:

iex> auth = %ShopifyAPI.AuthToken{}
iex> query = "mutation {
    metafieldDelete (
            input: {
              id: \"gid://shopify/Metafield/1234567891234\"
            }
    )
    {
      deletedId
      userErrors {
        field
        message
      }
      }
  }"
iex> ShopifyAPI.GraphQL.query(auth, query)

[ch53711]

Nice! Very exciting to start incorporating this functionality.
Have you had a look at Neuron? It might help to clean up some of the boilerplate code. Sending actual GraphQL requests is pretty simple, but it also neatly handles JSON parsing, and supports some extra GraphQL features like fragments and variables.

Nice! Very exciting to start incorporating this functionality.
Have you had a look at Neuron? It might help to clean up some of the boilerplate code. Sending actual GraphQL requests is pretty simple, but it also neatly handles JSON parsing, and supports some extra GraphQL features like fragments and variables.

thanks @quinlanjager !!!
Yes, we did look at neuron and although we are following some of the patterns in this repo we soon discovered this library didn't fit our needs(for Shopify API at least at this moment), for example, JSON parsing in neuron doesn't seem to be working as intended as it always returns {:ok, %Neuron.Response{}} regardless if request succeeded | failed and we would still need to parse response to retrieve the response itself and throttleStatus like we do here GraphQL.Response(our Response module follows a similar implementation as Neuron Response returning {:ok, %Response{}} | {:error, %Response{}} and including throttleStatus when request is successful)
Neuron Response for a failed request {:ok, %Response{}}:
{:ok,
 %Neuron.Response{
   body: %{
     "errors" => [
       %{
         "locations" => [%{"column" => 2, "line" => 1}],
         "message" => "Parse error on \"query\" (STRING) at [1, 2]"
       }
     ]
   },
   headers: [...].
   status_code: 200
}

but poisons says there was an error in the response:
{:error,
 %HTTPoison.Response{
   body: %{
     "errors" => [
       %{
         "locations" => [%{"column" => 2, "line" => 1}],
         "message" => "Parse error on \"query\" (STRING) at [1, 2]"
       }
   }
   headers: [...]
}


cuckoo -d inform of outdated version

pyhon cuckoo -d produce the following warning:
""Outdated! Cuckoo Sandbox version 1.2 is available now." "

@botherder @jekil Please fix the server to handle 2.0-dev.

Updated Cuckoo to show one is running a development version instead of the supposedly latest version.


deis CLI can't determine app context

When I build the deis CLI from workflow master on Mac OS X, it can't figure out what the app context is:
$ deis create
Creating Application... done, created vacuum-asteroid
Git remote deis added
remote available at ssh://git@deis.<IP_ADDRESS>.xip.io:2222/vacuum-asteroid.git
$ deis info
Error:
404 Not Found
detail: Not found.
$ git remote -v
deis	ssh://git@deis.<IP_ADDRESS>.xip.io:2222/vacuum-asteroid.git (fetch)
deis	ssh://git@deis.<IP_ADDRESS>.xip.io:2222/vacuum-asteroid.git (push)
origin	https://github.com/deis/example-go (fetch)
origin	https://github.com/mboersma/example-go (push)
$ deis info -a vacuum-asteroid
=== vacuum-asteroid Application
updated:  2016-02-25T17:39:22UTC
uuid:     c4275640-c84b-4073-b148-fd1614634599
created:  2016-02-25T17:39:22UTC
url:      vacuum-asteroid.<IP_ADDRESS>.xip.io:31854
owner:    matt
id:       vacuum-asteroid

=== vacuum-asteroid Processes

=== vacuum-asteroid Domains

The same is true for other commands such as ps:scale or apps:destroy--the local git remote does not seem to be used.
    WARNING: Potentially Destructive Action
 !        To proceed, type "kabuki-mackinaw" or re-run this command with --confirm=kabuki-mackinaw

> kabuki-mackinaw
Destroying kabuki-mackinaw...
done in 0s
Git remote deis removed
><> deis info
Error:
404 Not Found
detail: Not found.

><> deis create
Creating Application... done, created knotty-ironwood
Git remote deis added
remote available at ssh://git@deis.<IP_ADDRESS>.xip.io:2222/knotty-ironwood.git
><> deis info
=== knotty-ironwood Application
updated:  2016-02-25T18:48:40UTC
uuid:     49b779bd-fb4b-4be6-9191-c4822d62436d
created:  2016-02-25T18:48:40UTC
url:      knotty-ironwood.<IP_ADDRESS>.xip.io
owner:    bacongobbler
id:       knotty-ironwood

=== knotty-ironwood Processes

=== knotty-ironwood Domains

@mboersma here's my git version 2.5.4 (Apple Git-61)

@vdice same here.

Once I'm finished with what I got I'll see if I can reproduce as well and see what we can come up with

I cant seem to reproduce this.

ok so im seeing something weird. Latest build from master doesnt seem to pickup any information from the controller. So even though I have apps deployed on this cluster it doesn't pick them up.

Name:			ip-10-0-0-27.us-west-2.compute.internal
Labels:			kubernetes.io/hostname=ip-10-0-0-27.us-west-2.compute.internal
CreationTimestamp:	Mon, 22 Feb 2016 12:53:09 -0700
Phase:
Conditions:
  Type		Status	LastHeartbeatTime			LastTransitionTime			Reason				Message
  ────		──────	─────────────────			──────────────────			──────				───────
  OutOfDisk 	False 	Fri, 26 Feb 2016 11:40:31 -0700 	Mon, 22 Feb 2016 12:53:09 -0700 	KubeletHasSufficientDisk 	kubelet has sufficient disk space available
  Ready 	True 	Fri, 26 Feb 2016 11:40:31 -0700 	Mon, 22 Feb 2016 12:53:09 -0700 	KubeletReady 			kubelet is posting ready status
Addresses:	<IP_ADDRESS>,<IP_ADDRESS>,<IP_ADDRESS>
Capacity:
 memory:	8178876Ki
 pods:		40
 cpu:		2
System Info:
 Machine ID:			2a4fa21ad7044b5b91c10c9b2f34c7d5
 System UUID:			EC2B15E4-E153-F848-511B-BB7AAA45783F
 Boot ID:			57bbfca0-fbeb-42d6-96f4-ad37c093dff6
 Kernel Version:		4.3.3-coreos-r2
 OS Image:			CoreOS 899.7.0
 Container Runtime Version:	docker://1.9.1
 Kubelet Version:		v1.1.2+3085895
 Kube-Proxy Version:		v1.1.2+3085895
ExternalID:			i-6725b9a0
Non-terminated Pods:		(21 in total)
  Namespace			Name								CPU Requests	CPU Limits	Memory Requests	Memory Limits
  ─────────			────								────────────	──────────	───────────────	─────────────
  deis				deis-builder-knypb						0 (0%)		0 (0%)		0 (0%)		0 (0%)
  deis				deis-workflow-2v84b						0 (0%)		0 (0%)		0 (0%)		0 (0%)
  foo				foo-v3-web-1a7bu						0 (0%)		0 (0%)		0 (0%)		0 (0%)
  foo				foo-v3-web-6cjzv						0 (0%)		0 (0%)		0 (0%)		0 (0%)
  foo				foo-v3-web-8yb3q						0 (0%)		0 (0%)		0 (0%)		0 (0%)
  foo				foo-v3-web-b11nh						0 (0%)		0 (0%)		0 (0%)		0 (0%)
  foo				foo-v3-web-yexbb						0 (0%)		0 (0%)		0 (0%)		0 (0%)
  foobar			foobar-v3-web-0dlf2						0 (0%)		0 (0%)		0 (0%)		0 (0%)
  foobar			foobar-v3-web-1sxd1						0 (0%)		0 (0%)		0 (0%)		0 (0%)
  foobar			foobar-v3-web-28gyg						0 (0%)		0 (0%)		0 (0%)		0 (0%)
  foobar			foobar-v3-web-bkqcc						0 (0%)		0 (0%)		0 (0%)		0 (0%)
  foobar			foobar-v3-web-cgib2						0 (0%)		0 (0%)		0 (0%)		0 (0%)
  foobar			foobar-v3-web-e5p7r						0 (0%)		0 (0%)		0 (0%)		0 (0%)
  foobar			foobar-v3-web-evvnf						0 (0%)		0 (0%)		0 (0%)		0 (0%)
  foobar			foobar-v3-web-lot9p						0 (0%)		0 (0%)		0 (0%)		0 (0%)
  foobar			foobar-v3-web-skb0y						0 (0%)		0 (0%)		0 (0%)		0 (0%)
  foobar			foobar-v3-web-u3bw2						0 (0%)		0 (0%)		0 (0%)		0 (0%)
  kube-system			kube-dns-v9-h5r1l						310m (15%)	310m (15%)	170Mi (2%)	170Mi (2%)
  kube-system			kube-proxy-ip-10-0-0-27.us-west-2.compute.internal		0 (0%)		0 (0%)		0 (0%)		0 (0%)
  kube-system			monitoring-influxdb-v2-lksqd					100m (5%)	100m (5%)	200Mi (2%)	200Mi (2%)
  skiing-keypunch		skiing-keypunch-v2-web-02zb9					0 (0%)		0 (0%)		0 (0%)		0 (0%)
Allocated resources:
  (Total limits may be over 100%, i.e., overcommitted. More info: http://releases.k8s.io/HEAD/docs/user-guide/compute-resources.md)
  CPU Requests	CPU Limits	Memory Requests	Memory Limits
  ────────────	──────────	───────────────	─────────────
  410m (20%)	410m (20%)	370Mi (4%)	370Mi (4%)
No events.

╭─jonathanchauncey at ENG000637 in ~/projects/deis/postgres on rewrite✘✘✘ using ‹2.0.0-p645›
╰─± deis apps
=== Apps
foo```

That's due to rolling the DB, app info comes from there.

Oh yeah sorry should have replied here


[WFCORE-4064] Upgrade log4j-jboss-logmanager from 1.1.5.Final to 1.1.…

…6.Final
https://issues.jboss.org/browse/WFCORE-4064
This change only includes a fix for generating JavaDocs with Java 8. There are no functional changes.

These Windows failures are not related. The only change is for the JavaDoc build process.


MINOR: Some spelling corrections in comments that I happened to notice

Minor doesn't even do it justice, really minor change, mostly to fix node->note in a comment.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

I'll save jenkins the trouble of retesting this, since no code changes were made I'll assume the failure is down to flaky tests.


Print a warning in a case of unknown/ignored stuff

Is your feature request related to a problem? Please describe.
An unknown content (attributes,elements) is silently ignored by a parser.
Describe the solution you'd like
A warning should be printed to a console.

i assume this is a behavior for the validate action, right? that's fine.
transform behavior on handling unknown content might need to be handled differently.

That's interesting, I was thinking about having a switch (-vv  or  -w) to enable printing of  warnings to a console no matter on the action (validate | transform).
Can you please help me understand your thoughts on transform in this context?

warnings for ignore and passed through vs. warnings for ignored and removed.

by default i'd like to "pass through" the unknown elements.
i also would prefer warnings for these cases and might even accept that as default (IOW, use --silent to supress warnings?)
would be happy to have a --strict and strips out all unknown elements as an option (a way to create a "clean" doc).
the --strict could bark errors for added properties for validate and drop the added properties for transform mode.

does this make sense?

yes, thanks for the input. I like the --strict and --silent switch idea.


Updating typings

Hi there,
Great library. Very easy to use. Quick question: should the typings be expanded to cover the full API? For example, interceptors? I added this to augment locally, but I think it should be built into the typings.
declare module axios {
    interface AxiosRequestMethods {
        interceptors: {
            request: {
                use: (interceptRequest: (config: RequestOptions) => RequestOptions, handleRequestError?: (error: any) => Promise) => number;
            }
            response: {
                use: (interceptResponse: (config: Response) => Response, handleResponseError?: (error: any) => Promise) => number;
            }
        };
    }
}

Thanks,
Silvio

Yes, this needs to be fixed. I'm planning to rewrite axios type script definitions soon. I will make sure that interceptors are covered. Thank you!

Closing in favor of a single issue for all typescript requests (#379).


MediaStorePlugin.saveFile error with API 28

Hello again 😃
Wtih API 28 I got this error if  MediaStore.appFolder does not exist when calling mediaStorePlugin.saveFile.
In my case MediaStore.appFolder is 'Beep & Speech'
E/flutter (11402): [ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: FileSystemException: Cannot copy file to '/storage/emulated/0/Notifications/Beep & Speech/Toto.wav', path = '/data/user/0/fr.hyperburst.beepandspeech.beep_and_speech/app_flutter/beep_and_speech_data/Toto.wav' (OS Error: No such file or directory, errno = 2)
E/flutter (11402): #0      _File.copy.<anonymous closure> (dart:io/file_impl.dart:328:9)
E/flutter (11402): <asynchronous suspension>
E/flutter (11402): #1      MediaStore.saveFile (package:media_store_plus/media_store_plus.dart:82:19)
E/flutter (11402): <asynchronous suspension>

await mediaStorePlugin.saveFile(
        tempFilePath: notificationFile.path,
        dirType: DirType.audio,
        dirName: DirName.notifications)

Temporarily fixed by creating the directory before copying.
...
      Directory directory = Directory(dirType.fullPath(
          relativePath: relativePath.orAppFolder, dirName: dirName));
      String fileName = Uri.parse(tempFilePath).pathSegments.last.trim();
      File tempFile = File(tempFilePath);

      await Directory(directory.path).create();

      File file = await tempFile.copy(directory.path + "/" + fileName);
      return await file.exists();
...

Nice catch. So, basically, we just need to create the directory in lower APIs as we are using direct File API to do the things.

Tested in API levels 27 & 28. Thanks for this find out.


Add ability to delete tokens (undo feed)

The goal of this PR is to enable token feed undo. This is mostly useful for autocomplete functionality (e.g. keyboards or coding assistants), where the text changes often around the cursor's position.
Fixes issue https://github.com/rustformers/llm/issues/332
Tested on GptNeoX by writing a demo program that uses the delete_token method to minimize model refreshes. I tested these use cases:

Add 200 tokens, then delete one of them. Ensure topk predictions look the same as before the latest token.
Add 200 tokens, then delete all of them. Ensure topk predictions return to start of sentence.
Delete then add, add then delete, etc.
Used println!() extensively to verify it was deleting the expected tokens.

The performance is pretty solid. Deleting 10 tokens takes less than a millisecond on my box.
A potential issue with this PR is that you can't delete the start of content token because decoded_tokens.truncate would fail. It also might fail on other special tokens, but I'm not sure how to encounter these as part of my testing.

Good job, i read through it and it looks good. Could you provide a link to your demo program? I would like to play around a bit with it.

Sure! Here's the demo code:
https://gist.github.com/steventrouble/47cca1306bf3a41c4f62dc698d71f5af
And you can run it with cargo run -- --model=my_model_path
I extracted it rather hastily from my project crate, but I think it should compile fine. Hopefully I didn't remove too much functionality when I yanked it out, and hopefully it's somewhat comprehensible. It's a little late over here 😅

Hi there! Great work on this; this is a very useful feature to have.
The only thing I'm not sure about is the interaction with the memory_k/memory_v tensors. If you do the following sequence of operations:
logits_0 = feed_prompt("blah")
logits_200 = infer_200(deterministic_sampler)

logits_0_new = rewind_200()
logits_200_new = infer_200(deterministic_sampler)

assert(logits_0 == logits_0_new)
assert(logits_200 == logits_new)

Do the logits match with no further user intervention? My understanding is that the process of feeding prompts/running inference will mutate the memory tensors, so the logits will not match. (Feel free to correct me if I'm wrong - it's very hard to get visibility into exactly what's happening with the tensors, so I have to resort to conjecture)

You bring up a great point. There's not a lot of visibility into the buffersl. I verified with a hex editor that GptNeoX only modifies the memory corresponding to the latest token, but I'd be happy to do more tests.
Do you have ggml copies of tiny models for each of the model types? That would save me a lot of time when testing.
Also, I'm not sure what the policy is on integration tests, but I'd love to be able to submit some kind of repeatable test so others can verify it works on other hardware.

@steventrouble  Currently we don't have integration tests but we sure would like to have some :D (see https://github.com/rustformers/llm/issues/319)
The problem is that we don't have miniature versions of our models which makes testing with the original models kinda difficult.
Maybe we could create some sort of python script to only covert a single layer of a pytorch model but that's incredibly hacky.

Not sure how much progress you've made on this already, but I can give you mock models that compress to about 2MB each. Does that work for your needs?
I set most of the model weights and biases to 0, then compressed it with gzip. I should be able to do this with any model. Here's an example with GptNeoX:
https://github.com/steventrouble/llm/tree/smoke/crates/llm/tests

Awesome! I saw your integration tests PR 😄
I wrote a basic integration test, but I'll hold off on uploading until your PR is stable. Then I'll upate my PR to add the test in. Ping me when I can pick this up again!

Uhm i dont know how i these zeroed out models will behave but wont they always  output the same results as they will zero out the input after the first matmul?

A few of the neurons will still have values, so it'll output random jibberish. It's mostly useful as a lightweight smoke test, to make sure the tensor loader still works and that the compute graph doesn't crash at inference time.

Maybe we could use these tiny models, currently we're just using the smallest available models for each architecture 🤷
I also thought about creating some "tiny_shakespeare" models where is use 1-2 layers and maybe 8 heads to train a small variant of each model on this dataset.
But honestly, we can just use the original models as the github action runners can download them in about 30 sec 😅
If you want you could pull the newest main into this branch and try to create an integration test for the token deletion 👍

Sweet! I'm on it 😃

Alright, all tested. Deleting tokens works on all the models! (except llama 😢)

Hm thats strange, are you recalculating the K/V memory or are you removing the last n entries from it?

@LLukas22 Nope, I leave the memory unchanged. The old values are still in the memory, but it's fine because the memory is treated as uninitialized by many (not all) models.
E.g.

TBH, I'm not sure why it doesn't work for llama. I've looked over the code, and all access to memory_k and memory_v seem to be using session_len.
Is it possible it's storing state in the scratch buffers or statically? Or that there's some subtle bug in one of the memory_k/v accesses?

Maybe it has something to do with the scratch buffers. If i find some time i'll give it a look and check why the results diverge.

Aha! Found the issue. The test was wrong, and the model works fine with delete. I used a debugger to verify that it only touches the section of memory corresponding to the current token, and that the scratch buffers don't (seem to) carry state between calls.
The issue was that the token " crab" is actually tokenized as two separate tokens, but I only remove one token in the test. I updated the test to use " ", which is a single token and it passes for llama.
😄

(Fixed a temp change I made while debugging. I'm still getting back into the hang of git after 8 years of perforce, thanks for your patience!)

Is this ready for a review?

Yup, it looks good for review.
Thanks for your patience! Next time I contribute there will be a lot less back and forth.

Fantastic work - thank you very much 🚀


Support for building on java11

In submitting this contribution, I agree to the current Software AG contributor agreement as referred to here:
https://github.com/quartz-scheduler/contributing/blob/main/CONTRIBUTING.md
This PR...
Changes

enables to build this project using jdk11 and jdk17

Checklist

[x] tested locally
[x] signed-off on the above mentioned SoftwareAG contributor agreement via git commit -s on my commits.
(If you're not using command-line, you can use a browser extension )

Fixes #

Thank you @konopka .

@jhouserizer can you somehow stop this stale bot madness? We are now forced to comment on issues/PRs to keep them alive and all valid issues/PRs are getting closed due to no-one looking at them.


Noisy admin log -Exception while resolving variable 'non_field_errors' in template 'admin/import_export/change_list_import_export.html'.

I might've set my admin/models up incorrectly, but my logs are unbearably noisy after adding this package to my project.
Traceback (most recent call last):
  File "/opt/spoton_venvs/salons/lib/python3.6/site-packages/django/template/base.py", line 856, in _resolve_lookup
    (bit, current))  # missing attribute
django.template.base.VariableDoesNotExist: Failed lookup for key [non_field_errors] in None
[Tue 2019-04-02 20:03:52+0000] DEBUG [django.template._resolve_lookup:878] Exception while resolving variable 'non_field_errors' in template 'admin/import_export/change_list_import_export.html'.
Traceback (most recent call last):
  File "/opt/spoton_venvs/salons/lib/python3.6/site-packages/django/template/base.py", line 835, in _resolve_lookup
    current = current[bit]
TypeError: 'NoneType' object is not subscriptable

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/spoton_venvs/salons/lib/python3.6/site-packages/django/template/base.py", line 843, in _resolve_lookup
    current = getattr(current, bit)
AttributeError: 'NoneType' object has no attribute 'non_field_errors'

How do I quiet these down?

currently have the same problem

Hi Reed
What version are you using?  I suggest use the v4 beta version (if not already) as this has the most recent fixes.
This is an old issue, can you be more specific about the exact issue you are seeing?
Any help to resolve is much appreciated.


[Linaro:ARM_CI] Quiet warnings from build_pip_package

Quiet those warnings about 'Installing as data is deprecated' as they just spam the log

Sorry, doing this a different way.


Unable to select items on Sandance after publishing as an App

I have created a SandDance visual on Power BI Desktop and published it as an App. When testing on Desktop, I was able to select items of the scatter plot thus reflecting those selection filters on other plots.
But after publishing as an Power BI App, I am not being able to make this selection. When I try to select an item on the SandDance, it gets unselected automatically. I am not sure why.

Hi I also see a similar issue after the recent update if Sanddance, when I am in a edit mode, the mouse click selections stays. But in other modes like in Reading more / Dashboard / App, the selection does not work on clicking or immediately unselects.


:lady_beetle: Uneven spacing in mappings tab

Issue:
Uneven spacing in mapping tab
Screenshot:

Addressed by #979


Update communicate-with-users-from-other-organizations.md

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@MikePlumleyMSFT PR has been copyedited and is ready for final review, could you please check and merge? Thanks!

@scanum this PR has unresolved edits.
@RuiPereiraTabares what's the scope of "external communications"? I'm not clear on what feature you're referring to.

@MikePlumleyMSFT  TeamsFree is not going to provision a cloudsipproxxyadress or either the domain will be online sip enabled, therefore the externalcomunications will not work for it.
Teamsfree is different than the exploratory licenses is the completly freemiun subscription
https://support.microsoft.com/en-us/office/differences-between-microsoft-teams-and-microsoft-teams-free-0b69cf39-eb52-49af-b255-60d46fdf8a9c
we do not mention this, However over my tests in deepsite i could see that is not provisioned, what will make imposible to comunicate externally or make a external search to a TeamsFree license


[WIP] Otoken init

Description
This PR is for the init function for Otoken contract. In this function we will

set global parameters.
generate deterministic name and symbol

Todos:

[ ] Add doc for each function
[x] Make test caes 100% coverage

The on-chain name and symbol generation is making the init function very expensive, now this function is costing 230000 gas (around $3.3 with current 60 gwei gas price.)

Great job on this! Again a lot of complexity going on with the date time library :) You did a good job of distilling that down!
Also question on will the integration tests with Factory + Whitlist Module be in this or elsewhere?

We need the AddressBook module to do real integration test.


Review of the current "SAP Samples" content

Hello,
I submit the review of the SAP samples related to the Kyma runtime so that all the external-facing content is created with one voice. I have corrected the naming according to the SAP Brand Tools, provided some fixes, and also adjusted the content to the general guidelines for technical documentation. Feel free to contact me if you have any questions and please let me know when you accept this PR.
Related issue:
https://github.tools.sap/kyma/backlog/issues/600

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


npm test run mostly fails on node 20.11.0

[x] fixed

Most of the test cases are fixed

node version 22.11.0


[Incremental] Interleave waves by adding llbuild rules dynamically

Redo the interaction between llbuild and IncrementalBuildState in order to allow 2nd wave compilations to interleave with first wave compilations. As each first wave job finishes, add rules for discovered 2nd wave jobs.

@swift-ci please test

@swift-ci please test

@swift-ci please test

@swift-ci please test

@swift-ci please test

This looks like a really great improvement! I don't know enough about llbuild best practices to meaningfully review the changes to MultiJobExecutor, but I didn't see any issues there. This PR will need a simultaneous update to SPM, but it'll be a really small change

Thank you. As always your help is much appreciated.

@swift-ci please test

Will need to be synchronized with https://github.com/apple/swift-package-manager/pull/3033

Just for my edification, let's clarify some terminology:

Primary Jobs
Secondary Jobs
Tertiary Jobs

It looks like primary jobs are the initial jobs gathered by files with mod time changes, external deps modified, etc. Secondary jobs are gathered during the swiftdeps reload step after a job finishes. Tertiary jobs are sort of a mystery to me.

Just for my edification, let's clarify some terminology:

Primary Jobs
Secondary Jobs
Tertiary Jobs

It looks like primary jobs are the initial jobs gathered by files with mod time changes, external deps modified, etc. Secondary jobs are gathered during the swiftdeps reload step after a job finishes. Tertiary jobs are sort of a mystery to me.

Thanks much for looking at this! I will add some comments. You are absolutely right. Tertiary jobs include linking, etc. These are the jobs that must wait until all primary and secondary jobs finish. I'd be happy to brainstorm better names, if these seem to be obscure.

@swift-ci please test

The cleanup here is quite nice. I agree with Artem's assessment though considering even reading the comments that were there were not sufficient for me to grasp the naming change for the abstractions here.

Thank you--I really appreciate the time and thought of you and all the other reviewers. I'll go for the other names.

@swift-ci please test

@swift-ci please test


feat(t_templates): use syslog-ng default substitution instead of $(if)

This is a tiny improvement I use mainly to see how the contribution process works and also to get to know Github actions which don't run on my fork. I don't insist on merging this, I am just trying to get more familiar with sc4s.

Oh nice syntax I learned something which I usually do when I look at your work. I approved the CI run but I need you to accept the cla/coc agrements to merge

I have read the CLA Document and I hereby sign the CLA

I could only find the CoC in the GitHub actions config, but there's no link posted by the bot and the CoC is not part of the project's GitHub settings.

https://github.com/splunk/cla-agreement/blob/main/CODE_OF_CONDUCT.md
I have read the Code of Conduct and I hereby accept the Terms

I have read the Code of Conduct and I hereby accept the Terms

It seems I have no permission to push the docker image generated from this PR into the github docker registry. It is understandable, but it seems the CI is not able to run this way.

:tada: This PR is included in version 2.0.0-next-major.4 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Option to split chain based on number of method calls

I typically split my chains into multiple lines after the first method call, not dependent on the length of some chain. So something like:
- some_item.method_a().method_b().then_c().also_d();

+ some_item.method_a()
+     .method_b()
+     .then_c()
+     .also_d();

But I don't split them up if there are, for instance, just three methods being chained:
some_item.method_a().method_b();

I'd like to be able to control:

How many methods need to be called for a split to happen (in my case, > 2).
When a split happens, how many calls should stay on the first line (in my case, 1).

Of course, if the setting for 2) exceeds max-width (or perhaps another setting), then the first method call should be moved to the next line regardless:
- some_item.this_is_some_really_long_method_name_that_definitely_exceeds_max_width();
+ some_item
+     .this_is_some_really_long_method_name_that_definitely_exceeds_max_width();

- some_item_name_here_that_definitely_results_in_exceeding_max_width().in_first_method();
+ some_item_name_here_that_definitely_results_in_exceeding_max_width()
+     .in_first_method();

We experimented with this in the past, but it worked really badly in practice - long method calls, etc. caused problems and we found the character based version (chain_one_line_max) much better. Given that experience, we're unlikely to re-add the old count-based prefs (we might decide something else in the fmt-rfcs process too).


docs(Introduction): fix declarative example

There is a missing href to "/home" in the HTML version for the . This is the link

This PR changes  to

Codecov Report

Merging #1771 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1771   +/-   ##
=======================================
  Coverage   99.75%   99.75%
=======================================
  Files         142      142
  Lines        2459     2459
=======================================
  Hits         2453     2453
  Misses          6        6

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 04ea612...9b53438. Read the comment docs.

Sorry for the delay, thanks much!

Released in<EMAIL_ADDRESS>


Update integration tests when container and image have same name

Signed-off-by: Wen Cheng Ma<EMAIL_ADDRESS>

LGTM

LGTM 🐶

LGTM 🐶


Displaying Error when run this command "ng test --code-coverage"

Hi, I want to generate a test report by using above command but i got this error.
ERROR in ./src/node_modules/ng2-sharebuttons/index.js
Module build failed: SyntaxError: 'import' and 'export' may appear only with 'sourceType: module' (1:0)

Hi @vasu592 I have no knowledge about that I'm sorry


Fix call to prepare and prepareAsync

When calling prepare() and prepareAsync() without a 2nd argument, we had the following fatal :
PHP Catchable fatal error:  Argument 2 passed to Cassandra\DefaultSession::prepare() must be an instance of Cassandra\ExecutionOptions, null given

This PR fixes this error.

:+1:


Update Istio version to latest

Current version is 0.6.0; this script fails due to the mismatch.
Signed-off-by: Phil Estes<EMAIL_ADDRESS>

I had updated this earlier this week. Maybe you had a slightly older version checked out.
https://github.com/todkap/istio-index-conf2018/commit/72c78ce9a095bd1bbbebbbf995abbb98ea231fd8

Oops! Fixed this locally at the start of the week and totally forgot to check if upstream had changed. No problem, thx

Welcome future contributions.  Would like to test this on other kube envs as well.  Hope you find this useful ;)


Correct flow for complex operations

Hi everybody,
This isn't a technical issue with the code base per se but I thought this might be a good place to ask the question if others are wondering the same.
I'm fairly new to the CQRS / Mediatr setup so please bear with me if I've missed something basic :)
I have a flow where I need to create a customer and afterward a subscription for the customer (which requires a call to an external API). I've set up an IPaymentProvider interface to handle the external API call.
But my question is - what is the correct way of handling this process?
There are a few options
Option A - The classic MVC approach

CustomerController (MVC) calls Mediatr.Send(new CreateCustomerCommand(...);
Upon response, CustomerController (MVC) calls Mediatr.Send(new CreateSubscriptionCommand(...);
The CreateSubscriptionCommandHandler creates the subscription, calls the IPaymentProvider and saves changes to my system

Option B - The Publish event approach

CustomerController (MVC) calls Mediatr.Send(new CreateCustomerCommand(...);
CreateCustomerCommandHandler publishes a notification through Mediatr (CustomerCreated)
The CreateSubscriptionNotificationHandler picks up the notification, creates the subscription, calls the IPaymentProvider and saves changes to my system

Option C - Something else entirely
I hope my question makes sense :)
I'm really REALLY happy with the CQRS/Mediatr set up.... I just need to get it right :)
Thank you guys.

The second option is looks good from my point of view. Rather than calling two handlers from controller, you can publish the notification after creating customer and then create the subscription for that customer on other side!
And also let's say in future if you wanna create subscription for specific user then rather than adding if condition in controller (if we followed first approach) we can include the same in Create Customer handler to do same. And having business logic in handler makes more sense than having it in controller level.

Good point @MCCshreyas - thanks :)
I think I'll explore this path a bit - unless someone feels very strongly about why this should not be the path to take.

Thank you for your interest in this project. This repository has been archived and is no longer actively maintained or supported. We appreciate your understanding. Feel free to explore the codebase and adapt it to your own needs if it serves as a useful reference. If you have any further questions or concerns, please refer to the README for more information.


Update discord.go

Added bolding around the name, and split the name vs message with ": " on line 338

You should use RemoteNickFormat config for changing the nick appearance.

I mean I'll look at that, but the current code is purposely stringing the name and message together without any kind of separation. Surely that cannot be intended design?

Ok the RemoteNickFormat changes the display for ALL messages. I'm specifically fixing an issue in threads (with PreserveThreading set to true) that the name of the person sending the message (Since the sender is the bot name) and the message itself is concatenated together and looks dumb. My changes will fix this and make the threads easier to read.

You can see the Bot messages look fine, but the thread reply looks ridiculous.

Okay, I compiled the changes I suggested and tested and found that they didn't actually do anything lol. Definitely not what I was trying to achieve. I spent some more time actually reading through the code and I think i'm in the wrong place to influence the messages being sent when a thread is occurring. You can ignore this for now if I find out where to do the change I'll make a new pull request.

Did you ever solve this @greenlighttec because I think this was a clean solution

https://github.com/mspgeek-community/matterbridge


Fix DelayedDelivery at the broker level has a default value

Motivation
delayedDeliveryEnabled at the broker level is enabled by default, but at the namespace level is not set.
But now the value can be obtained directly through admin.namespaces().getDelayedDelivery(namespace).
This makes users very confused, we did not set the policy, but it has value.
Therefore, null should be returned by default

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks


I forgot to add show-today-shortcut to the directive also (was only in the component)

I've added the today-shortcut to the directive also now.
Markus

I fixed a layout bug that happens if using a global css directive to set all box-sizing to border-box.
There is a check for a global moment object in several places of datetime.ts, but one of them fails if the moment object is not there. I fixed this null-check but noted that the datetime picker does not work at all if there is no moment-object in the global scope. However, I didn't investigate it further.

The safest way to work this for the time being was to declare content-box in all places where it's implicitly assumed.
I removed the -moz- prefix, as we have never used any of the other vendor prefixes.
Seem ok now?

I will merge it for now, but it might be changed to 'border-box' later when if necessary.

Sounds great!

Hi again, any projection regarding when this'll be in a release? I'm deciding whether or not I should use a direct github reference in our project.


Add support for air filter and error code

The draft of the corresponding Home Assistant PR can be found here, including a short demo clip.
(Waiting for this PR to be accepted and new version of the library to be published before HA's PR can be submitted.)

Thanks @amitfin, new version released here: https://pypi.org/project/pycoolmasternet-async/0.1.5/
Please note the the HA PR is unlikely to pass review in its current implementation - you'll most likely be asked to use separate entities (probably a switch for the filter state and sensor for the error code) rather than attributes and custom services.

Thanks @OnFreund.
I was also debating between the 2 different approaches. Since Climate has many attributes, it seemed more aligned to add attributes than creating separate entities. In addition, the default naming for the units is not descriptive, so it's most likely that "friendly_name" (or even the entity_id) gets changed. By having multiple entities, the renaming process becomes tedious (number of units times number of entities).
As for the custom service, I don't see many options here, regardless of the entity which is used for the service call. (But I might be missing something here, so please let me know if you have something concrete in mind.)

The core team has shifted to preferring separate entities over the last few years, and I think they even mentioned somewhere that climate, if designed today, would have been several entities by itself.
As for naming - don't worry about it. With the new naming schema, all you have to do is give your entity a "relative" name, and the prefix will be taken from the device (so if you use the name "Filter" and the user renames l1_111 to "Bedroom A/C", the resulting entity name will be "Bedroom A/C Filter"). You only rename once per device.
If clean filter is a switch - you don't need a custom service. You can simply use the regular turn off service (you just have to prevent the user from turning it on, because that doesn't make sense - it can only be marked as on by coolmaster itself).


feat: export as parquet

What type of PR is this?

[ ] Refactor
[x] Feature
[ ] Bug Fix
[ ] New Query Runner (Data Source)
[ ] New Alert Destination
[ ] Other

Description

How is this tested?

[ ] Unit tests (pytest, jest)
[ ] E2E Tests (Cypress)
[ ] Manually
[ ] N/A

Related Tickets & Documents

Mobile & Desktop Screenshots/Recordings (if there are UI changes)

@gabriel-suela


Environment
Docker
Version
0.15.1
Describe the problem
trying to setup OIDC provider with Authentik and getting error described in Logs below.

setting the necessary variables in the .env file

AUTH_PROVIDER=credentials,oidc
BASE_URL=homera.mydomain.com
AUTH_OIDC_URI=https://login.mydomain.com/application/o/homarr
AUTH_OIDC_CLIENT_ID=ID
AUTH_OIDC_CLIENT_SECRET=SECRET
AUTH_OIDC_CLIENT_NAME=Authentik
NEXTAUTH_URL=https://homera.mydomain.com

Logs
15.03.2024 13:41:24 Exporting hostname...
15.03.2024 13:41:24 Migrating database...
15.03.2024 13:41:25 yarn run v1.22.19
15.03.2024 13:41:25 $ ts-node ./migrate.ts
15.03.2024 13:41:27 Done in 2.40s.
15.03.2024 13:41:27 Starting production server...
15.03.2024 13:41:28 Listening on port 7575 url: http://f470414efdfb:7575
15.03.2024 13:41:37 ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable...
15.03.2024 13:41:37 ℹ Database is writeable
15.03.2024 13:41:39 ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable...
15.03.2024 13:41:39 ℹ Database is writeable
15.03.2024 13:41:44 ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable...
15.03.2024 13:41:44 ℹ Database is writeable
15.03.2024 13:41:45 ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable...
15.03.2024 13:41:45 ℹ Database is writeable
15.03.2024 13:41:47 ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable...
15.03.2024 13:41:47 ℹ Database is writeable
15.03.2024 13:41:58 user admin is trying to log in. checking password...
15.03.2024 13:41:58 user admin successfully authorized
15.03.2024 13:42:10 user admin is trying to log in. checking password...
15.03.2024 13:42:10 user admin successfully authorized
15.03.2024 13:42:11 ℹ Local icons repository directory exists and contains 0 icons
15.03.2024 13:42:22 [next-auth][error][SIGNIN_OAUTH_ERROR]
15.03.2024 13:42:22 https://next-auth.js.org/errors#signin_oauth_error Socket connection timeout {
15.03.2024 13:42:22  error: {
15.03.2024 13:42:22    message: 'Socket connection timeout',
15.03.2024 13:42:22    stack: 'Error [ERR_SOCKET_CONNECTION_TIMEOUT]: Socket connection timeout\n' +
15.03.2024 13:42:22      '    at new NodeError (node:internal/errors:399:5)\n' +
15.03.2024 13:42:22      '    at internalConnectMultiple (node:net:1099:20)\n' +
15.03.2024 13:42:22      '    at Timeout.internalConnectMultipleTimeout (node:net:1638:3)\n' +
15.03.2024 13:42:22      '    at listOnTimeout (node:internal/timers:575:11)\n' +
15.03.2024 13:42:22      '    at process.processTimers (node:internal/timers:514:7)',
15.03.2024 13:42:22     name: 'Error'
15.03.2024 13:42:22   },
15.03.2024 13:42:22   providerId: 'oidc',
15.03.2024 13:42:22   message: 'Socket connection timeout'
15.03.2024 13:42:22 }

Context
No response
Please tick the boxes

[X] I confirm that I attached the proper logs
[X] I've read the docs
[X] I've checked for duplicate issues
[X] I've tried to debug myself

AUTH_OIDC_URI=https://login.mydomain.com/application/o/homarr
Try without the path, just https://login.mydomain.com
NEXTAUTH_URL=https://homera.mydomain.com
homera? Is that on purpose?

AUTH_OIDC_URI=https://login.mydomain.com/application/o/homarr Try without the path, just https://login.mydomain.com
NEXTAUTH_URL=https://homera.mydomain.com homera? Is that on purpose?

AUTH_OIDC_URI=https://login.mydomain.com doesn't help 😞
homera is just my subdomain for homarr 😄

Are you certain that you've setup Authentik correctly for OIDC?
There is also another known issue, if you try to login with OIDC using a user whose email is already used by one setup in homarr, then it's not going to work. We would recommend using only one auth provider at a time.
I assume that you only have "credentials" to be able to access your board, but if you have any user registered onto homarr's native database, you might not be able to connect to it using OIDC.
I haven't tried Authentik but other users have set it up successfully, this may help:
https://github.com/ajnart/homarr/issues/1909#issuecomment-1951780147

Are you certain that you've setup Authentik correctly for OIDC? There is also another known issue, if you try to login with OIDC using a user whose email is already used by one setup in homarr, then it's not going to work. We would recommend using only one auth provider at a time. I assume that you only have "credentials" to be able to access your board, but if you have any user registered onto homarr's native database, you might not be able to connect to it using OIDC. I haven't tried Authentik but other users have set it up successfully, this may help: #1909 (comment)

readed this post again and reinstalled homarr from scratch.
Now all working perfectly


Setting a cache-control for external static files?

I'd like to set the cache control on external static files(which contains some .css and .html files), so that my web client's browsers don't have to fully reload the page every time.
How do I do this?
edit: Or any response header for the external static files for that matter.
Currently, when looking at the headers with my browser, it looks like the current cache-control header is: "max-age=0"

I'd like to keep this issue open, because client-caching static files with a last-modified when spark was started seems like a no-brainer, but I've developed a workaround for serving up folders:
Make sure this is the last endpoint referenced
		get("/*", (req, res) -> {
			Tools.allowAllHeaders(req, res);
			Tools.set15MinuteCache(req, res);

			String pageName = req.splat()[0];

			String webHomePath = DataSources.WEB_HOME() + "/" + pageName;

			Tools.setContentTypeFromFileName(pageName, res);

			return Tools.writeFileToResponse(webHomePath, res);

		});

Can't you just use an after-filter?
after((request, response) -> {
    response.header("Cache-Control", "max-age=2592000");
});

I don't think after/before works for static files, but someone could correct me.

@tchoulihan Sorry, you are correct. You really shouldn't have to do this manually though.

The introduction of cache-control for static files would be great. Has this been prioritised?

Hi,
I'd like to know if any progress has been made on this subject ?
To me, it also seems like a no brainer thing "a priori" but given the amount of effort needed this is not :)
@tchoulihan could please post your Tools class somewhere so that I can reuse your workaround ?

This was introduced in 2.5 :)
staticFiles.expireTime(600);
//or
staticFiles.header("Some header key", "Some header value");

Thanks!

I want to add a "Last-Modified" header to static resources (which, if I understand correctly, offers a different type of caching than "Expires" or "Cache-Control": https://stackoverflow.com/a/22188521)
However, staticFiles.header(key, value) still seems inadequate to me, as I have to somehow get a reference to the File being served to determine the last modified date.
I see that the AbstractFileResolvingResource class, used by the static file loader, already has a lastModified() function implemented, but the function is not used for much right now. In particular, it would be good if I can make StaticFilesConfiguration.consumeWithFileResourceHandlers() inject the "Last-Modified" header while it has a reference to the AbstractFileResolvingResource.
Am I missing something?


collect all errors before raising

fixes #20
What does this do on a high level?
Rather than asserting on the first error found, wait until all fields have been processed and then build a message that includes all missing or mismatched fields.
How will this be verified?

[X] The PR includes new tests
[ ] Current test suite covers functionality
[ ] This has been tested locally
[ ] This has been tested in dev

motivational imagery

Pull Request Test Coverage Report for Build 7b8cd534e776de8fcbd62b8c7fa75d32a909347d-PR-21

24 of 24 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build d74aff3f708cf6ca5c2e678c51ad84dabd6903a3:
0.0%

Covered Lines:
44

Relevant Lines:
44

💛  - Coveralls


Benchmark results

I wonder is any benchmark results could be published so that when testing the libray we can get a comparison is ebverything is running ok?
When ikind of result would you expect for runing the command:
./build/rtneural_model_bench

Measuring non-templated model...
Processed 100 seconds of signal in 117.635 seconds
0.850086x real-time

Thats what I get for release mode with the default backend.   Is that expected or would you be expecting faster than real-time?

Hello!
The benchmarks included in the repository here are run regularly as part of the repository CI pipeline. Here is the latest result from the CI benchmarks using the Eigen backend.
Run ./build/rtneural_model_bench
Measuring non-templated model...
Processed 100 seconds of signal in 2.5133 seconds
39.1952x real-time

I don't know exactly what CPU was used for running the benchmarks either in the CI pipeline, or in your local tests, but I would expect most consumer CPUs to perform as good or better than the CI pipeline.
I would be curious to see the commands your using to compile the benchmarks as well as to configure the benchmarks via CMake?
If you are trying to run the benchmarks on a very low-power CPU (maybe some embedded device), then the benchmark model may indeed be too much computation to run in real time on that device. In that case, you may want to run the individual "layer" benchmarks to get a sense of where the computational limits are for that device.


Possible issue due to allow detect mimeType from non-gap segments change

Have you read the Tutorials?
Yes
Have you read the FAQ and checked for duplicate open issues?
Yes
If the question is related to FairPlay, have you read the tutorial?

No
What version of Shaka Player are you using?
4.10.9
What browser and OS are you using?
Chrome on iOS
Please ask your question
I am trying to play a HLS manifest where the segment URIs on it does not have a extension, which makes shaka to try to retrieve the segment basic info from the segment request content-type header. In my case, this will return application/octet-stream.  When that happens, none of the conditions regarding mimeType and extension will be satisfied and shaka will return a basic info where the type will be application/octet-stream back to convertParsedPlaylistIntoStreamInfo_ method. Shaka will then call makeStreamObject_ passing application/octet-stream as the type and, within makeStreamObject_ method, shaka will call guessMimeTypeFallback_ which will throw an error because shaka.hls.HlsParser.EXTENSION_MAP_BY_CONTENT_TYPE_[contentType] map does not have an entry to application/octet-stream.
This issue does not happen on 4.9.x versions. That said, are you going to consider this a bug or do you suggest any workaround?

@celsosantarosa can you provide a sample stream to work on it? Thanks!