[bug] Build timing out in GitHub Actions

Describe the bug
After updating from 0.22.0 to 0.23.4 builds in GitHub Actions are timing out. However while running the build locally it succeeds. I suspect, though I can not be sure, that the action runner is encountering memory constraints and then stalling.
Steps to reproduce
Unfortunately, I don't have reproduction steps here. At least not steps I can give because I think it has to do with the setup of my specific project which is not open source.
Expected behavior
The build runs to completion.
Environment
I capturee this information with npx envinfo. It is a GitHub Actions runner based on ubuntu-20.04.
System:
    OS: Linux 5.15 Ubuntu 20.04.5 LTS (Focal Fossa)
    CPU: (2) x64 Intel(R) Xeon(R) Platinum 8272CL CPU @ 2.60GHz
    Memory: 5.72 GB / 6.78 GB
    Container: Yes
    Shell: 5.0.17 - /bin/bash
  Binaries:
    Node: 16.19.0 - /opt/hostedtoolcache/node/16.19.0/x64/bin/node
    Yarn: 3.3.0 - /usr/local/bin/yarn
    npm: 8.19.3 - /opt/hostedtoolcache/node/16.19.0/x64/bin/npm
  Managers:
    Apt: 2.0.9 - /usr/bin/apt
    Cargo: 1.67.0 - ~/.cargo/bin/cargo
    Composer: 2.5.1 - /usr/bin/composer
    Gradle: 7.6 - /usr/bin/gradle
    Maven: 3.8.7 - /usr/bin/mvn
    pip3: 20.0.2 - /usr/bin/pip3
    RubyGems: 3.1.2 - /usr/bin/gem
  Utilities:
    Bazel: 6.0.0 - /usr/local/bin/bazel
    CMake: 3.[25](https://github.com/littlecinemadigital/backstage/actions/runs/4115321414/jobs/7103877260#step:4:26).2 - /usr/local/bin/cmake
    Make: 4.2.1 - /usr/bin/make
    GCC: 9.4.0 - /usr/bin/gcc
    Git: 2.39.1 - /usr/bin/git
    Clang: 11.0.0 - /usr/bin/clang
    Mercurial: 5.3.1 - /usr/bin/hg
    Subversion: 1.13.0 - /usr/bin/svn
  Servers:
    Nginx: 1.18.0 - /usr/sbin/nginx
  Virtualization:
    Docker: 20.10.22+ - /usr/bin/docker
  SDKs:
    Android SDK:
      API Levels: [27](https://github.com/littlecinemadigital/backstage/actions/runs/4115321414/jobs/7103877260#step:4:28), [28](https://github.com/littlecinemadigital/backstage/actions/runs/4115321414/jobs/7103877260#step:4:29), [29](https://github.com/littlecinemadigital/backstage/actions/runs/4115321414/jobs/7103877260#step:4:30), [30](https://github.com/littlecinemadigital/backstage/actions/runs/4115321414/jobs/7103877260#step:4:31), [31](https://github.com/littlecinemadigital/backstage/actions/runs/4115321414/jobs/7103877260#step:4:32), [32](https://github.com/littlecinemadigital/backstage/actions/runs/4115321414/jobs/7103877260#step:4:33), [33](https://github.com/littlecinemadigital/backstage/actions/runs/4115321414/jobs/7103877260#step:4:34), 33
      Build Tools: 27.0.0, 27.0.1, 27.0.2, 27.0.3, 28.0.0, 28.0.1, 28.0.2, 28.0.3, 29.0.0, 29.0.1, 29.0.2, 29.0.3, 30.0.0, 30.0.1, 30.0.2, 30.0.3, 31.0.0, 32.0.0, 33.0.0, 33.0.1
      Android NDK: 25.1.89[37](https://github.com/littlecinemadigital/backstage/actions/runs/4115321414/jobs/7103877260#step:4:38)[39](https://github.com/littlecinemadigital/backstage/actions/runs/4115321414/jobs/7103877260#step:4:40)3
  IDEs:
    Nano: 4.8 - /usr/bin/nano
    Vim: 8.1 - /usr/bin/vim
  Languages:
    Bash: 5.0.17 - /usr/bin/bash
    Go: 1.17.13 - /usr/bin/go
    Erlang: 25.0.4 - /usr/bin/erl
    Java: 11.0.11 - /opt/hostedtoolcache/Java_Adopt_jdk/11.0.11-9/x64/bin/javac
    Perl: 5.30.0 - /usr/bin/perl
    PHP: 8.2.1 - /usr/bin/php
    Python: 3.8.10 - /usr/bin/python
    Python3: 3.8.10 - /usr/bin/python3
    R: 4.2.2 - /usr/bin/R
    Ruby: 2.7.0 - /usr/bin/ruby
    Rust: 1.67.0 - /home/runner/.cargo/bin/rustc
  Databases:
    MongoDB: 5.0.14 - /usr/bin/mongo
    MySQL: <IP_ADDRESS> - /usr/bin/mysql
    SQLite: 3.31.1 - /usr/bin/sqlite3
  Browsers:
    Chrome: 109.0.5[41](https://github.com/littlecinemadigital/backstage/actions/runs/4115321414/jobs/7103877260#step:4:42)4.119
    Chromium: 109.0.[54](https://github.com/littlecinemadigital/backstage/actions/runs/4115321414/jobs/7103877260#step:4:55)14.0
    Firefox: 109.0.1
  Monorepos:
    Yarn Workspaces: 3.3.0

Additional context
I have attached as a .zip archive the text file output of the run execution with MOON_LOG set to trace. I did abort the run once it appeared to be stalled (stopped printing anything for a couple seconds). I'll include the last 100 or so lines inline here as well.
4_Run make project.txt.zip
2023-02-07T14:02:08.2972425Z ▪▪▪▪ messaging-api:gen-prisma-client (17s 398ms, f1d31d84)
2023-02-07T14:02:08.3003445Z [trace 14:02:08] moon:cache:item Writing cache ~/work/backstage/backstage/.moon/cache/states/messaging-api/gen-prisma-client/lastRun.json
2023-02-07T14:02:08.3005076Z [debug 14:02:08] moon:archive:tar Packing tar archive from ~/work/backstage/backstage/packages/messaging-api to ~/work/backstage/backstage/.moon/cache/outputs/f1d31d84e50812c2f75599f8a3bf7ab5e279e79d56e32381526a98f28c1e2f31.tar.gz
2023-02-07T14:02:08.3006545Z [trace 14:02:08] moon:archive:tar Packing file ~/work/backstage/backstage/.moon/cache/states/messaging-api/gen-prisma-client/stderr.log
2023-02-07T14:02:08.3007689Z [trace 14:02:08] moon:archive:tar Packing directory ~/work/backstage/backstage/packages/messaging-api/src/generated/prisma-client
2023-02-07T14:02:11.8393078Z [trace 14:02:11] moon:archive:tar Packing file ~/work/backstage/backstage/.moon/cache/states/messaging-api/gen-prisma-client/stdout.log
2023-02-07T14:02:11.8400476Z [trace 14:02:11] moon:action-pipeline:batch:5:3 Processed action RunTarget(messaging-api:gen-prisma-client) in 21.027832638s
2023-02-07T14:02:16.4723674Z [trace 14:02:16] moon:cache:item Writing cache ~/work/backstage/backstage/.moon/cache/states/lambda-helpers/build/lastRun.json
2023-02-07T14:02:16.4724448Z ▪▪▪▪ lambda-helpers:build (25s 575ms, c821d0c9)
2023-02-07T14:02:16.4725916Z [debug 14:02:16] moon:archive:tar Packing tar archive from ~/work/backstage/backstage/packages/lambda-helpers to ~/work/backstage/backstage/.moon/cache/outputs/c821d0c9096306f990d1f3ceb884c278d4dc5f7a32953bd80517670fa55c452b.tar.gz
2023-02-07T14:02:16.4727079Z [trace 14:02:16] moon:archive:tar Packing file ~/work/backstage/backstage/.moon/cache/states/lambda-helpers/build/stderr.log
2023-02-07T14:02:16.4748597Z [trace 14:02:16] moon:archive:tar Packing file ~/work/backstage/backstage/.moon/cache/states/lambda-helpers/build/stdout.log
2023-02-07T14:02:16.4749623Z [trace 14:02:16] moon:archive:tar Packing directory ~/work/backstage/backstage/packages/lambda-helpers/dist
2023-02-07T14:02:16.4780746Z [trace 14:02:16] moon:action-pipeline:batch:5:1 Processed action RunTarget(lambda-helpers:build) in 25.667651435s
2023-02-07T14:02:17.2004196Z [trace 14:02:17] moon:cache:item Writing cache ~/work/backstage/backstage/.moon/cache/states/analytics-api/build/lastRun.json
2023-02-07T14:02:17.2004995Z ▪▪▪▪ analytics-api:build (26s 312ms, ab59bfc4)
2023-02-07T14:02:17.2006402Z [debug 14:02:17] moon:archive:tar Packing tar archive from ~/work/backstage/backstage/packages/analytics-api to ~/work/backstage/backstage/.moon/cache/outputs/ab59bfc4cdb544cf6c605debe83dacfb9b21589eed88833090a2ab62a2ef2dd5.tar.gz
2023-02-07T14:02:17.2007637Z [trace 14:02:17] moon:archive:tar Packing file ~/work/backstage/backstage/.moon/cache/states/analytics-api/build/stderr.log
2023-02-07T14:02:17.2008579Z [trace 14:02:17] moon:archive:tar Packing file ~/work/backstage/backstage/.moon/cache/states/analytics-api/build/stdout.log
2023-02-07T14:02:17.2009485Z [trace 14:02:17] moon:archive:tar Packing directory ~/work/backstage/backstage/packages/analytics-api/dist
2023-02-07T14:02:17.2043516Z [trace 14:02:17] moon:action-pipeline:batch:5:2 Processed action RunTarget(analytics-api:build) in 26.393082622s
2023-02-07T14:02:18.6283300Z ▪▪▪▪ asset-management-api:build (27s 737ms, 9e2cd33f)
2023-02-07T14:02:18.6284675Z [trace 14:02:18] moon:cache:item Writing cache ~/work/backstage/backstage/.moon/cache/states/asset-management-api/build/lastRun.json
2023-02-07T14:02:18.6286179Z [debug 14:02:18] moon:archive:tar Packing tar archive from ~/work/backstage/backstage/packages/asset-management-api to ~/work/backstage/backstage/.moon/cache/outputs/9e2cd33f484bdcd2786a47f06c6a6f1c551b6c70bcdc00a8c0e8571c79eafc77.tar.gz
2023-02-07T14:02:18.6287465Z [trace 14:02:18] moon:archive:tar Packing file ~/work/backstage/backstage/.moon/cache/states/asset-management-api/build/stderr.log
2023-02-07T14:02:18.6288515Z [trace 14:02:18] moon:archive:tar Packing file ~/work/backstage/backstage/.moon/cache/states/asset-management-api/build/stdout.log
2023-02-07T14:02:18.6289502Z [trace 14:02:18] moon:archive:tar Packing directory ~/work/backstage/backstage/packages/asset-management-api/dist
2023-02-07T14:02:18.6320371Z [trace 14:02:18] moon:action-pipeline:batch:5:5 Processed action RunTarget(asset-management-api:build) in 27.81867154s
2023-02-07T14:02:18.6321553Z [trace 14:02:18] moon:action-pipeline:batch:6 Running 3 actions in batch 6
2023-02-07T14:02:18.6322972Z [trace 14:02:18] moon:action-pipeline:batch:6:1 Processing action RunTarget(messaging-api:gen-admin-schema)
2023-02-07T14:02:18.6324058Z [trace 14:02:18] moon:cache:item Cache miss for ~/work/backstage/backstage/.moon/cache/states/messaging-api/gen-admin-schema/lastRun.json, does not exist
2023-02-07T14:02:18.6325066Z [debug 14:02:18] moon:action:run-target Running target messaging-api:gen-admin-schema
2023-02-07T14:02:18.6329264Z [trace 14:02:18] moon:action-pipeline:batch:6:2 Processing action SyncNodeProject(root)
2023-02-07T14:02:18.6330157Z [trace 14:02:18] moon:action-pipeline:batch:6:3 Processing action RunTarget(messaging-api:gen-attendee-schema)
2023-02-07T14:02:18.6331226Z [trace 14:02:18] moon:utils:process Running command git ls-files --cached --modified --others --full-name --exclude-standard packages/messaging-api (in ~/work/backstage/backstage)
2023-02-07T14:02:18.6332310Z [trace 14:02:18] moon:cache:item Cache miss for ~/work/backstage/backstage/.moon/cache/states/messaging-api/gen-attendee-schema/lastRun.json, does not exist
2023-02-07T14:02:18.6333121Z [debug 14:02:18] moon:action:run-target Running target messaging-api:gen-attendee-schema
2023-02-07T14:02:18.6425993Z [trace 14:02:18] moon:utils:process Running command git hash-object --stdin-paths - (truncated files list) (in ~/work/backstage/backstage)
2023-02-07T14:02:18.6501498Z [trace 14:02:18] moon:utils:process Running command git status --porcelain --untracked-files -z (in ~/work/backstage/backstage)
2023-02-07T14:02:18.6700535Z [debug 14:02:18] moon:runner Generated hash 83a2046b03241112e100a519ab6c2457f843d11b5c70fb728c3c7c8b29005322 for target messaging-api:gen-admin-schema
2023-02-07T14:02:18.6701689Z [trace 14:02:18] moon:cache Writing hash manifest ~/work/backstage/backstage/.moon/cache/hashes/83a2046b03241112e100a519ab6c2457f843d11b5c70fb728c3c7c8b29005322.json
2023-02-07T14:02:18.6702801Z [debug 14:02:18] moon:runner Cache miss for hash 83a2046b03241112e100a519ab6c2457f843d11b5c70fb728c3c7c8b29005322, continuing run
2023-02-07T14:02:18.6729505Z [debug 14:02:18] moon:action:sync-project Syncing project root
2023-02-07T14:02:18.6730068Z ▪▪▪▪ messaging-api:gen-attendee-schema
2023-02-07T14:02:18.6730694Z [trace 14:02:18] moon:lang:config Syncing ~/work/backstage/backstage/tsconfig.json with changes
2023-02-07T14:02:18.6731488Z [trace 14:02:18] moon:action-pipeline:batch:6:2 Processed action SyncNodeProject(root) in 37.708484ms
2023-02-07T14:02:18.6732429Z [debug 14:02:18] moon:runner Generated hash c047a55b47e9c04c43472d93e5b33ad1a5713b0bba90bc3b02c4c0770cb13bf9 for target messaging-api:gen-attendee-schema
2023-02-07T14:02:18.6733311Z [trace 14:02:18] moon:cache Writing hash manifest ~/work/backstage/backstage/.moon/cache/hashes/c047a55b47e9c04c43472d93e5b33ad1a5713b0bba90bc3b02c4c0770cb13bf9.json
2023-02-07T14:02:18.6734526Z [debug 14:02:18] moon:runner Cache miss for hash c047a55b47e9c04c43472d93e5b33ad1a5713b0bba90bc3b02c4c0770cb13bf9, continuing run
2023-02-07T14:02:18.6735599Z [debug 14:02:18] moon:runner Creating messaging-api:gen-attendee-schema command (in working directory ~/work/backstage/backstage/packages/messaging-api)
2023-02-07T14:02:18.6736601Z [trace 14:02:18] moon:cache:runfile Writing runfile ~/work/backstage/backstage/.moon/cache/states/messaging-api/runfile.json
2023-02-07T14:02:18.6742063Z [trace 14:02:18] moon:utils:process Running command ~/.moon/tools/node/16.19.0/node --title messaging-api:gen-attendee-schema ../../node_modules/ts-node/dist/bin.js --transpile-only src/index.ts --attendee-schema (in ~/work/backstage/backstage/packages/messaging-api)
2023-02-07T14:02:18.6751551Z   MOON_PROJECT_SOURCE=packages/messaging-api
2023-02-07T14:02:18.6752079Z   MOON_TARGET=messaging-api:gen-attendee-schema
2023-02-07T14:02:18.6752421Z   NODE_ENV=development
2023-02-07T14:02:18.6752812Z   MOON_WORKSPACE_ROOT=/home/runner/work/backstage/backstage
2023-02-07T14:02:18.6753729Z   MOON_PROJECT_ROOT=/home/runner/work/backstage/backstage/packages/messaging-api
2023-02-07T14:02:18.6754373Z   MOON_WORKING_DIR=/home/runner/work/backstage/backstage
2023-02-07T14:02:18.6754756Z   MOON_TOOLCHAIN_DIR=/home/runner/.moon
2023-02-07T14:02:18.6755187Z   MOON_CACHE_DIR=/home/runner/work/backstage/backstage/.moon/cache
2023-02-07T14:02:18.6756248Z   MOON_PROJECT_RUNFILE=/home/runner/work/backstage/backstage/.moon/cache/states/messaging-api/runfile.json
2023-02-07T14:02:18.6756632Z   MOON_PROJECT_ID=messaging-api
2023-02-07T14:02:18.6761367Z [debug 14:02:18] moon:runner Creating messaging-api:gen-admin-schema command (in working directory ~/work/backstage/backstage/packages/messaging-api)
2023-02-07T14:02:18.6761982Z ▪▪▪▪ messaging-api:gen-admin-schema
2023-02-07T14:02:18.6762999Z [trace 14:02:18] moon:cache:runfile Writing runfile ~/work/backstage/backstage/.moon/cache/states/messaging-api/runfile.json
2023-02-07T14:02:18.6764440Z [trace 14:02:18] moon:utils:process Running command ~/.moon/tools/node/16.19.0/node --title messaging-api:gen-admin-schema ../../node_modules/ts-node/dist/bin.js --transpile-only src/index.ts --admin-schema (in ~/work/backstage/backstage/packages/messaging-api)
2023-02-07T14:02:18.6765644Z   MOON_PROJECT_SOURCE=packages/messaging-api
2023-02-07T14:02:18.6766152Z   MOON_TARGET=messaging-api:gen-admin-schema
2023-02-07T14:02:18.6766501Z   NODE_ENV=development
2023-02-07T14:02:18.6766905Z   MOON_WORKSPACE_ROOT=/home/runner/work/backstage/backstage
2023-02-07T14:02:18.6767490Z   MOON_PROJECT_ROOT=/home/runner/work/backstage/backstage/packages/messaging-api
2023-02-07T14:02:18.6767970Z   MOON_WORKING_DIR=/home/runner/work/backstage/backstage
2023-02-07T14:02:18.6768364Z   MOON_TOOLCHAIN_DIR=/home/runner/.moon
2023-02-07T14:02:18.6768786Z   MOON_CACHE_DIR=/home/runner/work/backstage/backstage/.moon/cache
2023-02-07T14:02:18.6769439Z   MOON_PROJECT_RUNFILE=/home/runner/work/backstage/backstage/.moon/cache/states/messaging-api/runfile.json
2023-02-07T14:02:18.6769943Z   MOON_PROJECT_ID=messaging-api
2023-02-07T14:02:27.2586487Z [messaging-api:gen-attendee-schema] Generated Artifacts:
2023-02-07T14:02:27.2587874Z [messaging-api:gen-attendee-schema]           TypeScript Types  ==> /home/runner/work/backstage/backstage/packages/messaging-api/src/schema/../generated/attendee-nexus.ts
2023-02-07T14:02:27.2589263Z [messaging-api:gen-attendee-schema]           GraphQL Schema    ==> /home/runner/work/backstage/backstage/packages/messaging-api/src/schema/../../attendee-schema.graphql
2023-02-07T14:02:27.2787643Z [trace 14:02:27] moon:cache:item Writing cache ~/work/backstage/backstage/.moon/cache/states/messaging-api/gen-attendee-schema/lastRun.json
2023-02-07T14:02:27.2788484Z ▪▪▪▪ messaging-api:gen-attendee-schema (8s 605ms, c047a55b)
2023-02-07T14:02:27.2790119Z [debug 14:02:27] moon:archive:tar Packing tar archive from ~/work/backstage/backstage/packages/messaging-api to ~/work/backstage/backstage/.moon/cache/outputs/c047a55b47e9c04c43472d93e5b33ad1a5713b0bba90bc3b02c4c0770cb13bf9.tar.gz
2023-02-07T14:02:27.2791471Z [trace 14:02:27] moon:archive:tar Packing file ~/work/backstage/backstage/packages/messaging-api/src/generated/attendee-nexus.ts
2023-02-07T14:02:27.2792649Z [trace 14:02:27] moon:archive:tar Packing file ~/work/backstage/backstage/.moon/cache/states/messaging-api/gen-attendee-schema/stderr.log
2023-02-07T14:02:27.2793775Z [trace 14:02:27] moon:archive:tar Packing file ~/work/backstage/backstage/.moon/cache/states/messaging-api/gen-attendee-schema/stdout.log
2023-02-07T14:02:27.2794773Z [trace 14:02:27] moon:archive:tar Packing file ~/work/backstage/backstage/packages/messaging-api/attendee-schema.graphql
2023-02-07T14:02:27.2795864Z [trace 14:02:27] moon:action-pipeline:batch:6:3 Processed action RunTarget(messaging-api:gen-attendee-schema) in 8.645823868s
2023-02-07T14:02:27.5227881Z [messaging-api:gen-admin-schema] Generated Artifacts:
2023-02-07T14:02:27.5229221Z [messaging-api:gen-admin-schema]           TypeScript Types  ==> /home/runner/work/backstage/backstage/packages/messaging-api/src/schema/../generated/admin-nexus.ts
2023-02-07T14:02:27.5230823Z [messaging-api:gen-admin-schema]           GraphQL Schema    ==> /home/runner/work/backstage/backstage/packages/messaging-api/src/schema/../../admin-schema.graphql
2023-02-07T14:02:27.5409903Z ▪▪▪▪ messaging-api:gen-admin-schema (8s 864ms, 83a2046b)
2023-02-07T14:02:27.5422623Z [trace 14:02:27] moon:cache:item Writing cache ~/work/backstage/backstage/.moon/cache/states/messaging-api/gen-admin-schema/lastRun.json
2023-02-07T14:02:27.5423969Z [debug 14:02:27] moon:archive:tar Packing tar archive from ~/work/backstage/backstage/packages/messaging-api to ~/work/backstage/backstage/.moon/cache/outputs/83a2046b03241112e100a519ab6c2457f843d11b5c70fb728c3c7c8b29005322.tar.gz
2023-02-07T14:02:27.5425025Z [trace 14:02:27] moon:archive:tar Packing file ~/work/backstage/backstage/packages/messaging-api/admin-schema.graphql
2023-02-07T14:02:27.5425927Z [trace 14:02:27] moon:archive:tar Packing file ~/work/backstage/backstage/.moon/cache/states/messaging-api/gen-admin-schema/stdout.log
2023-02-07T14:02:27.5426828Z [trace 14:02:27] moon:archive:tar Packing file ~/work/backstage/backstage/packages/messaging-api/src/generated/admin-nexus.ts
2023-02-07T14:02:27.5427715Z [trace 14:02:27] moon:archive:tar Packing file ~/work/backstage/backstage/.moon/cache/states/messaging-api/gen-admin-schema/stderr.log
2023-02-07T14:02:27.5428591Z [trace 14:02:27] moon:action-pipeline:batch:6:1 Processed action RunTarget(messaging-api:gen-admin-schema) in 8.909929172s
2023-02-07T14:02:27.5429299Z [trace 14:02:27] moon:action-pipeline:batch:7 Running 1 actions in batch 7
2023-02-07T14:02:27.5442941Z [trace 14:02:27] moon:action-pipeline:batch:7:1 Processing action RunTarget(root:gen-gql-types)
2023-02-07T14:02:27.5443837Z [trace 14:02:27] moon:cache:item Cache miss for ~/work/backstage/backstage/.moon/cache/states/root/gen-gql-types/lastRun.json, does not exist
2023-02-07T14:02:27.5444564Z [debug 14:02:27] moon:action:run-target Running target root:gen-gql-types
2023-02-07T14:02:27.5447488Z [trace 14:02:27] moon:utils:process Running command git hash-object --stdin-paths - codegen.yml packages/messaging-api/admin-schema.graphql packages/messaging-api/attendee-schema.graphql (in ~/work/backstage/backstage)
2023-02-07T14:02:27.5468928Z [trace 14:02:27] moon:utils:process Running command git ls-files --cached --modified --others --full-name --exclude-standard . (in ~/work/backstage/backstage)
2023-02-07T14:02:27.5738133Z [trace 14:02:27] moon:utils:process Running command git hash-object --stdin-paths - (truncated files list) (in ~/work/backstage/backstage)
2023-02-07T14:04:27.5328732Z ##[error]The operation was canceled.

Happy to provide any other information I can. It looks to me like the last command is to run git hash-object on too many files but I don't know enough about the internals that changed or how I could define my tasks differently to avoid it.

@bryanjswift Great debugging so far.
In your CI pipeline, if you run with --concurrency 1, does it pass? Or does it fail?
If it fails, does it fail at the same spot? If so, then it's most likely that git hash-object. I'm going to dig into this a little bit and see if there's a limit to how much we can call it with.

I ended up reverting to the older version so I could get the PR that converts our build system to use moon to land, I've been working on the conversion for a while (off and on) and didn't want this issue to hold things up.
I was setting concurrency explicitly to 6 when i ran into this issue. I have since removed the explicit concurrency setting since it seems like moon limits the number of tasks it runs at once now by default (thanks again for that!).
I will try with the version update again and let you know if the inferred or an explicit lower concurrency setting makes a difference.

Sounds good. At least we know the regression is somewhere in 0.23.

I've been going through the 0.23 commits, and nothing looks suspect, except for the changes to git hash-object. https://github.com/moonrepo/moon/pull/567/files#diff-11a1713bb46569b0b4f3b6262075e5b25bf708c15b680ffd65df9c694517959cR204
However, after googling around, other developers have mentioned passing 10,000 files just fine to that command, so I'm not entirely sure that's the problem.
Is your repo private? I think a next step may be compiling moon in debug mode and trying to debug what's going on.

Is your repo private? I think a next step may be compiling moon in debug mode and trying to debug what's going on.

The repo is private.
On my todo list for today is trying the moon update to 0.23 again and seeing if I can narrow the issue down. I have a suspicion it has to do with my unwittingly forcing concurrency over the number of cores available in a GitHub Actions runner.

@bryanjswift Let me know how it goes. Feel free to join the Discord and we can pair on this together.

Regrettably removing the explicit concurrency did not resolve the issue. I'm on the discord server now with the same username as GitHub. I'm not sure how I would go about getting a debug build of moon into GitHub actions but I'm willing to give it a try.

I wonder if it might be easier to get a docker image of the GitHub Action runner and test the build locall

Not a bad idea. I'll look into this as well this weekend.

The act project defines some, very large, docker images that emulate the GitHub Actions runtime. I'm doing a bit of poking around with this to see if I can reproduce the behavior I was seeing locally.

I created a docker image based on the catthehacker/ubuntu:full-20.04 image. I didn't use act to perform the tests but instead copied my project files into the image and then ran ./node_modules/.bin/moon run --concurrency 1 :build from an interactive docker prompt. I've included the Dockerfile I used for testing below, though I recognize it isn't much help without the rest of the project source which I can not share. This local build in the Docker image hasn't completed yet but it is well past the step where the GitHub Actions runner timed out.
I also changed my GitHub action definition to explicitly use ./node_modules/.bin/moon run --concurrency 1 :build rather than the implicit concurrency limit. The resulting GitHub Actions execution stalled on the same task as the original report, stalling as it starts prepping to execute the root:gen-gql-types task. Please do let me know if there is more information I can provide. I'll be sure to follow up if I think of anything else. If you'd like to arrange a time to do some additional debugging I'd be happy to do that as well, I don't keep Discord open day to day (too distracting for me) but I can definitely hop online for some pairing.
[debug 15:18:41] moon:action:sync-project Syncing project root
[3030](https://github.com/littlecinemadigital/backstage/actions/runs/4151952953/jobs/7182582464#step:4:3031)
[trace 15:18:41] moon:lang:config Syncing ~/work/backstage/backstage/tsconfig.json with changes
[3031](https://github.com/littlecinemadigital/backstage/actions/runs/4151952953/jobs/7182582464#step:4:3032)
[trace 15:18:41] moon:action-pipeline:batch:6:3 Processed action SyncNodeProject(root) in 387.104µs
[3032](https://github.com/littlecinemadigital/backstage/actions/runs/4151952953/jobs/7182582464#step:4:3033)
[trace 15:18:41] moon:action-pipeline:batch:7 Running 1 actions in batch 7
[3033](https://github.com/littlecinemadigital/backstage/actions/runs/4151952953/jobs/7182582464#step:4:3034)
[trace 15:18:41] moon:action-pipeline:batch:7:1 Processing action RunTarget(root:gen-gql-types)
[3034](https://github.com/littlecinemadigital/backstage/actions/runs/4151952953/jobs/7182582464#step:4:3035)
[trace 15:18:41] moon:cache:item Cache hit for ~/work/backstage/backstage/.moon/cache/states/root/gen-gql-types/lastRun.json, reading
[3035](https://github.com/littlecinemadigital/backstage/actions/runs/4151952953/jobs/7182582464#step:4:3036)
[debug 15:18:41] moon:action:run-target Running target root:gen-gql-types
[3036](https://github.com/littlecinemadigital/backstage/actions/runs/4151952953/jobs/7182582464#step:4:3037)
[trace 15:18:41] moon:utils:process Running command git hash-object --stdin-paths - codegen.yml packages/messaging-api/admin-schema.graphql packages/messaging-api/attendee-schema.graphql (in ~/work/backstage/backstage)
[3037](https://github.com/littlecinemadigital/backstage/actions/runs/4151952953/jobs/7182582464#step:4:3038)
[trace 15:18:41] moon:utils:process Running command git ls-files --cached --modified --others --full-name --exclude-standard . (in ~/work/backstage/backstage)
[3038](https://github.com/littlecinemadigital/backstage/actions/runs/4151952953/jobs/7182582464#step:4:3039)
[trace 15:18:42] moon:utils:process Running command git hash-object --stdin-paths - (truncated files list) (in ~/work/backstage/backstage)

Dockerfile definition I mentioned earlier.
# syntax=docker/dockerfile:1.2
FROM catthehacker/ubuntu:full-20.04

# Define args used in the `builder` stage
ARG NPM_CONFIG_GH_TOKEN
ARG NPM_CONFIG_GSAP_TOKEN
ARG NPM_CONFIG_NPM_TOKEN
# Set the environment variables expected by yarn
ENV NPM_CONFIG_GH_TOKEN=$NPM_CONFIG_GH_TOKEN \
    NPM_CONFIG_GSAP_TOKEN=$NPM_CONFIG_GSAP_TOKEN \
    NPM_CONFIG_NPM_TOKEN=$NPM_CONFIG_NPM_TOKEN \
    CI=true

# Create env files so they exist
RUN touch .env .env.sample
# Copy yarn and build configuration
COPY .yarnrc.yml .
COPY .yarn/ ./.yarn/
COPY .moon/ ./.moon/
COPY scripts/ ./scripts/
# The `assemble-package-definitions.sh` script puts the hierarchy of
# `package.json` files in the `node_modules/.packages folder, this copies the
# hierarchy of `package.json` first to enable build caching of the `yarn
# install` step
COPY yarn.lock .
COPY node_modules/.packages .
# Filter out useless log messages
RUN yarn config set logFilters --json \
    '[{"code": "YN0002", "level": "discard"}, {"code": "YN0076", "level": "discard"}, {"code": "YN0013", "level": "discard"}]'
# Install dependencies
RUN yarn install --immutable
# Copy everything
COPY . .

@bryanjswift Does the root:gen-gql-types task talk to an upstream endpoint? Is that endpoint accessible from CI?
Can you also paste the task config for root:gen-gql-types so I can try and recreate it.

I spent a little time reorganizing task dependencies to take better advantage of caching. This is relevant mostly because it changed the execution order of tasks. However, the GitHub Actions runner still stalls in the steps leading up to executing my root:gen-gql-types task. Since it is stalling consistently on this task despite exception order of other dependent tasks I started to get curious if it had something to do with how the task was defined so I removed all of the input globs to see if that mattered, it didn't.
Looking at the trace logs again I noticed that the line immediately preceding the line where it stalls moon is executing
git ls-files --cached --modified --others --full-name --exclude-standard .

Which indicates it is listing all the files in the project. I also noticed that this is the first of the tasks in the root: project that is being executed. I think my next step is to try and explicitly run a different task from the root: project and see if that stalls.

@bryanjswift Does the root:gen-gql-types task talk to an upstream endpoint? Is that endpoint accessible from CI?

It does not talk to an upstream endpoint, it is generating the types based on .graphql schema files that are available in the filesystem.

Can you also paste the task config for root:gen-gql-types so I can try and recreate it.

The task definition is in https://github.com/moonrepo/moon/issues/601#issuecomment-1420967061 and has not changed. Copied below for reference.
  gen-gql-types:
    command: 'graphql-codegen --silent'
    deps:
      - 'messaging-api:gen-admin-schema'
      - 'messaging-api:gen-attendee-schema'
    inputs:
      - '/codegen.yml'
      - '/component-packages/access-code/src/gql/**/*.ts'
      - '/component-packages/attendee-container/src/gql/**/*.ts'
      - '/component-packages/rtc-room-container/src/gql/**/*.ts'
      - '/component-packages/video/src/gql/**/*.ts'
      - '/packages/admin-gql-types/src/**/*.ts'
      - '/packages/attendee-ui-types/src/**/*.ts'
      - '/packages/site-builder/src/controllers/**/*.ts'
      - '/packages/messaging-api/admin-schema.graphql'
      - '/packages/messaging-api/attendee-schema.graphql'
    outputs:
      - 'component-packages/access-code/src/generated/attendee-types.ts'
      - 'component-packages/attendee-container/src/generated/attendee-types.ts'
      - 'component-packages/rtc-room-container/src/generated/attendee-types.ts'
      - 'component-packages/video/src/generated/attendee-types.ts'
      - 'packages/admin-gql-types/src/generated/admin-types.ts'
      - 'packages/attendee-ui-types/src/generated/attendee-types.ts'
      - 'packages/site-builder/src/generated/admin-types.ts'

Good news, I think. I've recreated the stalling behavior with a much simpler task definition that is also in the root project by running it independently.
  env-compare:
    command: 'node scripts/env-compare.js .env.sample .env'
    inputs:
      - '.env'
      - '.env.sample'
      - 'scripts/env-compare.js'

Where scripts/env-compare.js is defined as below (though I don't think the command matters any longer.
#!/usr/bin/env node

const fs = require('fs');
const fsp = require('fs/promises');
const path = require('path');
const readline = require('readline');

const cwd = process.cwd();

async function compareEnvFiles(filenames) {
  const sample = path.join(cwd, filenames[0]);
  const environment = path.join(cwd, filenames[1]);
  try {
    await fsp.access(sample, fs.constants.R_OK);
  } catch (e) {
    throw new Error(`${sample} is not a readable file`);
  }
  try {
    await fsp
      .access(environment, fs.constants.R_OK)
      .catch(() => fsp.copyFile(sample, environment));
  } catch (e) {
    // copy sample file
    throw new Error(
      `${environment} is not a readable file and could not be created`
    );
  }
  const {variables: sampleVariables, optionals} = await readVariables(sample);
  const {variables: environmentVariables} = await readVariables(environment);
  const missingEnvironmentKeys = findAbsent({
    haystack: sampleVariables,
    needles: environmentVariables,
  });
  const extraEnvironmentKeys = findAbsent({
    haystack: environmentVariables,
    needles: sampleVariables.concat(optionals),
  });
  return {
    environmentFilename: environment,
    extraEnvironmentKeys,
    missingEnvironmentKeys,
    sampleFilename: sample,
  };
}

async function readVariables(filename) {
  const variables = [];
  const optionals = [];
  const rl = readline.createInterface({
    input: fs.createReadStream(filename),
  });
  rl.on('line', (line) => {
    const result = line.match(/^#?([A-Z_]+)=["']?(.*)["']?$/);
    if (result !== null && line.startsWith('#')) {
      optionals.push({key: result[1], value: result[2]});
    } else if (result !== null) {
      variables.push({key: result[1], value: result[2]});
    }
  });
  return new Promise((resolve) => {
    rl.on('close', () => {
      resolve({optionals, variables});
    });
  });
}

function findAbsent({haystack, needles}) {
  const haystackKeys = haystack.map((straw) => straw.key);
  const needleKeys = needles.map((straw) => straw.key);
  return haystackKeys.filter((key) => !needleKeys.includes(key));
}

async function reportEnvironmentKeys(props) {
  const {extraEnvironmentKeys, missingEnvironmentKeys} = props;
  missingEnvironmentKeys.forEach((variable) => {
    console.error(`🚩 ${variable} is not defined in environment file.`);
  });
  extraEnvironmentKeys.forEach((variable) => {
    // Variables prefixed with "MY_" are local to the developer's machine
    // and are deliberate, so should not cause a warning.
    if (!variable.startsWith('MY_')) {
      console.error(`${variable} does not exist in sample file.`);
    }
  });
  return props;
}

async function handleExitCode(props) {
  const {missingEnvironmentKeys} = props;
  if (missingEnvironmentKeys.length > 0) {
    process.exit(1);
  }
  return props;
}

async function handleCi(filenames) {
  const envFile = path.join(
    cwd,
    filenames.length === 0 ? '.env' : filenames[1]
  );
  return fsp
    .access(envFile, fs.constants.R_OK)
    .catch(() => fsp.writeFile(envFile, Buffer.from('')));
}

function printUsage() {
  const PROGNAME = path.basename(__filename);
  const usage = [
    `usage: ${PROGNAME} [sample] [environment]`,
    '',
    'Compares the variables declared in sample to those in environment and',
    'prints the difference. Variables defined in sample but missing in',
    'environment or defined in environment butnot present in sample are',
    'printed to stderr.',
    '',
    'Exits with a non-zero status if environment file is missing keys that',
    'exist in sample.',
    '',
    'Arguments:',
    '  [sample]        defaults to .env.sample in the current directory',
    '  [environment]   defaults to .env in the current directory',
    '',
    'Examples:',
    '  Show help:',
    `  ${PROGNAME} --help`,
    '',
    '  Compare .env.sample to .env',
    `  ${PROGNAME} .env.sample .env`,
  ];
  console.log(usage.join('\n'));
}

async function main(args) {
  let filenames = [];
  if (typeof process.env.CI !== 'undefined') {
    return handleCi(args);
  } else if (args.includes('--help')) {
    return printUsage();
  } else if (args.length === 0) {
    filenames = ['.env.sample', '.env'];
  } else if (args.length !== 2) {
    throw new Error('Pass the paths to sample and environment files');
  } else {
    filenames = args;
  }
  return compareEnvFiles(filenames)
    .then(reportEnvironmentKeys)
    .then(handleExitCode);
}

if (require.main === module) {
  main(process.argv.slice(2)).catch((reason) => {
    if (reason instanceof Error) {
      console.error(reason.message);
    } else if (typeof reason === 'string') {
      console.error(reason);
    } else {
      throw reason;
    }
  });
}

I see this warning in the caveats of the "root-level project" documentation: https://moonrepo.dev/docs/guides/root-project#greedy-inputs

Task inputs default to **/*, which would result in root-level tasks scanning all files in the repository. This will be a very expensive operation! We suggest restricting inputs to a very succinct whitelist, or disabling inputs entirely.

Is it possible there is another implicit definition like this for root projects that was introduced in the 0.23 line?

git ls-files --cached --modified --others --full-name --exclude-standard . | wc -l

Returns the same number of files remotely in Actions and locally for me, 2961

Awesome debugging.
So there was a change with how **/* is determined: https://github.com/moonrepo/moon/pull/581 I wonder if this is it.
If you expect the runfile at /.moon/cache/states/<project>/runfile.json, you can view the raw data that moon uses for everything. Can you verify what the inputs are for these root tasks? There's also the inheritedConfig that may be useful too.

Here are snippets from the runfile.json

root/runfile.json for root/runfile.json
      "env-compare": {
        "command": "node scripts/env-compare.js .env.sample .env",
        "inputs": [
          ".env",
          ".env.sample",
          "scripts/env-compare.js"
        ]
      },

root/runfile.json for root:gen-gql-types
      "gen-gql-types": {
        "command": "graphql-codegen --silent",
        "deps": [
          "messaging-api:gen-admin-schema",
          "messaging-api:gen-attendee-schema"
        ],
        "inputs": [
          "/codegen.yml",
          "/component-packages/access-code/src/gql/**/*.ts",
          "/component-packages/attendee-container/src/gql/**/*.ts",
          "/component-packages/rtc-room-container/src/gql/**/*.ts",
          "/component-packages/video/src/gql/**/*.ts",
          "/packages/admin-gql-types/src/**/*.ts",
          "!/packages/admin-gql-types/src/generated/*",
          "/packages/attendee-ui-types/src/**/*.ts",
          "!/packages/attendee-ui-types/src/generated/*",
          "/packages/site-builder/src/controllers/**/*.ts",
          "/packages/messaging-api/admin-schema.graphql",
          "/packages/messaging-api/attendee-schema.graphql"
        ],
        "outputs": [
          "component-packages/access-code/src/generated/attendee-types.ts",
          "component-packages/attendee-container/src/generated/attendee-types.ts",
          "component-packages/rtc-room-container/src/generated/attendee-types.ts",
          "component-packages/video/src/generated/attendee-types.ts",
          "packages/admin-gql-types/src/generated/admin-types.ts",
          "packages/attendee-ui-types/src/generated/attendee-types.ts",
          "packages/site-builder/src/generated/admin-types.ts"
        ]
      },

inheritedConfig from root/runfile.json
  "inheritedConfig": {
    "fileGroups": {
      "configs": [
        "*.{js,json}"
      ],
      "sources": [
        "src/**/*",
        "types/**/*"
      ],
      "prettier": [
        "/.prettierignore",
        "/.prettierrc"
      ],
      "projectConfigs": [
        "package.json",
        "tsconfig.json"
      ],
      "tests": [
        "test/**/*.test.*",
        "**/__tests__/**/*"
      ]
    },
    "implicitInputs": [
      "/.moon/*.yml"
    ],
    "tasks": {
      "build": {
        "command": "tsc --build",
        "deps": [
          "^:build"
        ],
        "inputs": [
          "@files(sources)",
          "@group(projectConfigs)"
        ],
        "outputs": [
          "dist"
        ]
      },
      "buildComponent": {
        "command": "node ../../scripts/build-component.js .",
        "deps": [
          "^:build",
          "~:buildComponentTypes"
        ],
        "inputs": [
          "@files(sources)",
          "@group(projectConfigs)"
        ],
        "outputs": [
          "dist/index.js",
          "dist/index.js.map",
          "dist/index.mjs",
          "dist/index.mjs.map"
        ]
      },
      "buildComponentTypes": {
        "command": "tsc --build",
        "deps": [
          "^:build"
        ],
        "inputs": [
          "@files(sources)",
          "@group(projectConfigs)"
        ],
        "outputs": [
          "dist/src",
          "dist/tsconfig.tsbuildinfo"
        ]
      },
      "format": {
        "command": "prettier --ignore-path ../../.prettierignore --config ../../.prettierrc --write .",
        "inputs": [
          "@globs(configs)",
          "@files(prettier)",
          "@globs(sources)",
          "@globs(tests)"
        ],
        "options": {
          "runInCI": false
        }
      },
      "gen-tsconfig-ref": {
        "command": "yarn ts-node scripts/development/update-tsconfig-refs.ts",
        "args": [
          "$projectSource"
        ],
        "inputs": [
          "package.json",
          "/scripts/development/update-tsconfig-refs.ts"
        ],
        "options": {
          "runInCI": false,
          "runFromWorkspaceRoot": true
        }
      },
      "test": {
        "command": "jest --passWithNoTests --reporters=default --reporters=jest-junit",
        "deps": [
          "^:build"
        ],
        "inputs": [
          "@files(sources)",
          "@files(tests)"
        ],
        "outputs": [
          "junit.xml"
        ]
      },
      "watch": {
        "command": "tsc --build --watch",
        "deps": [
          "^:build"
        ],
        "local": true
      },
      "watchComponent": {
        "command": "node ../../scripts/build-component.js . --watch",
        "deps": [
          "^:build"
        ],
        "local": true
      },
      "watchTest": {
        "command": "jest --passWithNoTests --reporters=default --watch",
        "deps": [
          "^:build"
        ],
        "local": true
      }
    }
  },

I'm not sure what to infer from these though.

Haven't found a root cause yet, but going to add more utils to help debug this: https://github.com/moonrepo/moon/pull/615

Sounds good, I’ll get more information for debugging once the build is available.

Ok 0.24, try it and let me know what happens. Pass MOON_DEBUG_PROCESS_INPUT=1 to see all the hashed files also.

I'm not sure which of these resolved the problem for me but I suspect it was one of these two changes.

Checking that the given path is a file (my project has symlinks in source control that I totally forgot about until I read this line): https://github.com/moonrepo/moon/pull/615/files#diff-321e2ef7dfdb1f8fe2e7fe28b01bda6c15134bca44bdc697e17b5c2cf7162d13R38
Using the "glob" file walker for root projects: https://github.com/moonrepo/moon/pull/615/files#diff-76dabf462aba06eb4f027d664d2a1847c75af054c4f6085024c93f45a69ce5dfR215-R219

Whichever it was, I'm no longer experiencing the bug I reported with v0.24. Thank you! 🙌

This is exciting! I had a hunch that git ls-files was grabbing everything because it was a root project, so moving root to the glob pattern seemed like the best approach.


game not responding problem

Describe your bug here. Mind you, if you are modding, please try testing your bug in a clean version of the engine instead, this ensures the bug is actually caused by the engine itself. Also, if you're using an older version of JSE, please try the latest action build in the Actions tab or the latest release build. The issue has probably been fixed since that version. Oh yeah, and also be sure to check the pinned 'JS Engine: Known Issues' issue, to double check if your issue hasn't already been found!
this bug is so annoying and has been in this engine for 23 versions
when the game has been left out for 2 days the game starts to not respond and then crashes slowly
Command Prompt/Terminal/Crash logs (if existing)
No response
Have you identified any steps to reproduce the bug? If so, please describe them below in as much detail as possible. Use images if possible.
gfdhjgdfggjhs

Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
I only added scripts
If you use 1.12.0 or earlier, did you have Optimized Chart Loading turned on?
None
Did you check for any similar issues to what you're reporting? Check, then come back here. If there is a similar issue, then do not report the issue, otherwise it will be marked as a duplicate.
Yes

dawg why do you even leave jse running for 2 days straight in the first place 💀

dawg why do you even leave jse running for 2 days straight in the first place 💀

ikr


Cilium: hubble-relay pod restarts, when hubble.tls.auto.method is certmanager

The documentation does not cover the use of self-signed certificates, see https://github.com/cilium/cilium/issues/30941.

Fixed in https://github.com/axivo/k3s-cluster/pull/8.


Rebalancer is getting stuck with 'RPC services not available' error

Error: Error: 2 UNKNOWN: waiting to start, RPC services not available from /tmp/autorebalance.log.
The service is running based on jet status, but rebalances arent being kicked off.
Noticed during alpha testing (at least two instances).
workaround: jet restart rebalancer

workaround: jet restart rebalancer

fixed by adding try & catch around classify.

The issue keeps on re-occurring. The rebalancer is getting stuck with 'Error: Error: 2 UNKNOWN: waiting to start, RPC services not available'.  Debugging the issue. Added extra notifications in the jet monitor and the telegram bot.

The same issue occurred in the telegram bot service. It looks like lnd grpc connect is getting dropped (intermittently), which causes jet services to stall.
/home/umbrel/mytools/lnd-api/utils.js:457
if (err) throw new Error(err);
^
Error: Error: 14 UNAVAILABLE: Connection dropped
at Object.callback (/home/umbrel/mytools/lnd-api/utils.js:457:22)
at Object.onReceiveStatus (/home/umbrel/mytools/node_modules/@grpc/grpc-js/build/src/client.js:179:36)
at Object.onReceiveStatus (/home/umbrel/mytools/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:336:141)
at Object.onReceiveStatus (/home/umbrel/mytools/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:299:181)
at /home/umbrel/mytools/node_modules/@grpc/grpc-js/build/src/call-stream.js:145:78
at processTicksAndRejections (internal/process/task_queues.js:79:11)
at runNextTicks (internal/process/task_queues.js:66:3)
at processTimers (internal/timers.js:494:9)
at Function.module.exports.runLoopOnce (/home/umbrel/mytools/node_modules/deasync/index.js:65:10)
at fetchTelegramMessageSync (/home/umbrel/mytools/db/utils.js:61:28)
at Timeout.pollMessages [as _onTimeout] (/home/umbrel/mytools/service/telegram.js:78:14)
at listOnTimeout (internal/timers.js:554:17)
at processTimers (internal/timers.js:497:7)
at Function.module.exports.runLoopOnce (/home/umbrel/mytools/node_modules/deasync/index.js:65:10)
at Object.getInfoSync (/home/umbrel/mytools/lnd-api/utils.js:461:26)
at Object.listFees (/home/umbrel/mytools/lnd-api/utils.js:284:31)
at listFeesSync (/home/umbrel/mytools/lnd-api/utils.js:272:20)
at Timeout.monitorFees [as _onTimeout] (/home/umbrel/mytools/service/telegram.js:28:16)
at listOnTimeout (internal/timers.js:554:17)
at processTimers (internal/timers.js:497:7)

Identified an issue within the layer that communicates with lnd.  One grpc handle is being reused for multiple grpc calls.  A new handle needs to be generated upon connection reset.


ActionBar RTL not working

I've added android:supportsRtl="true" to the application tag in tiapp.xml but it has no effect on ActionBar and DrawerLayout and they still appear on left side. Any suggestions?

Ah, got it. Have to set the correct language using Ti.Locale (e.g. Ti.Locale.setLanguage('ar')) for android:supportsRtl="true" to work, otherwise it has no effect.


Multi-step input jumps back to first step on pressing enter in a text input

Reproduction
https://formkit.link/b0a0f8d2760a4482d1e6930fb8eb86b3
Describe the bug
Pressing the enter key within a text input in any step after the first leads to a jump to the first step, regardless of any validation settings. I expect the multi-step to jump to the next step if all inputs on the current step are valid.
This only happens if the multi-step component is within a FormKit form.
Environment
• OS: MacOS
• Browser Brave
• Version Version 1.48.171 Chromium: 110.0.5481.177 (Official Build) (arm64)

🤔 super weird. We’ll definitely look into this 👍

It was fixed at beta.16 #602

Actually that was a issue I posted simultaneously with this one — it has not been addressed yet. Re-opening.

This actually is already fixed in beta.16. Fix not related to any direct changes I made.
https://formkit.link/d8d9011453b84ecfb0dd4b1ab8043a96


Wrong Answer? Front-End: Target the same element with multiple jQuery Selectors

Is this wrong?
<script>   $(document).ready(function() {               $("button").addClass("animated bounce");                $(".btn").addClass("animated shake");               $("#target1").addClass("btn-primary");   }); </script>

Solved

<script>   $(document).ready(function() {               $("button").addClass("animated");                $(".btn").addClass("shake");               $("#target1").addClass("btn-primary");   }); </script>

The issue outline is correct, the documentation for the question appears to be incorrect.
"Only add one class with each of your three selectors."
"Your #target1 element should have the classes animated‚ shake and btn-primary."

@MaXwellFalstein It's asking you to apply one class for each selector, but since every one of those selectors will grab the #target1 element you'll end up with every class being applied to the #target1 element.

That is true. That is they correct way round. Thanks @ltegman!


Creating wonder-stuff-ci package!

Summary:

Created a new package wonder-stuff-ci. This package will contain typescript functions that are used throughout our scripts and automations ( OLC, Bitrise, Github Actions, etc.). I found a need for this when needing common functions for interacting with mobile releases.
Ported over three functions that I need and will continue adding functions into this package as they arise.

Issue: FEI-5058
Test plan:

Wrote Jest test for the functions.

@somewhatabstract @kevinbarabash , uh did i do this right lol

@somewhatabstract Thanks for the feedback jeff, updated the pr based on your comments. Let me know if I missed anything!


Use ": " as end of tag instead of ":" in android/mindroid parsers

This allows correct parsing of most tags which contain ":" since
it is unusual for such tags to contain ": ".

@MortronMeymo Can you please check clippy and the red tests?

@flxo the clippy lint's are in a file I haven't touched (terminal.rs). So seams to be a preexisting issue exposed by a newer clippy version?


[APIM] az apim: Add group deletedservice to support managing soft-deleted azure API Management services

Related command

az deletedservice list
az deletedservice show
az deletedservice purge
Description

Add az deletedservice  module to CLI to allow customer to manage soft-deleted service via CLI
Testing Guide

Tests are included in test_apim_deletedservice method
History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

APIM

@wangzelin007 All CLI linter error are fixed

@zhoxing-ms I've addressed the comments

/azp run


upgrade to node20

Node 16 is deprecated. So I changed it to run on node 20

@tokorom Hi, could you review this?

+1 thanks for creating this PR.  After updating it should remove this warning that users currently see:


MB-12322: Create ShipmentCustomerSIT sub-component (for Office add/edit PPM)

Jira ticket for this change: MB-12322, sub-task of MB-11865
Summary
This pull request adds the ShipmentCustomerSIT component, which will be used a part of the Office flow to add or edit details of a PPM shipment. On first view, the component displays a label and a radio buttons; if the value of the radio button group is "Yes," additional fields and a button are displayed to the user.
The "Calculate SIT" button is disabled until the remaining fields are filled out with valid values.
The functionality of what the "Calculate SIT" button is going to do/what it's going to display on-screen is presently undetermined; as of right now, the optional onCalculateClick prop accepts a function that will called with an object of the shape { start, end, weight, location }.
Tests and stories are added for this new component. As this component is only implemented and visible in Storybook, no change to any existing functionality in the application should be present.
Setup to Run Your Code
Start the Storybook locally.
make storybook

Additional steps
Open Storybook and view the Office Components -> Forms -> ShipmentForm -> StorageInTransit sub-component. Verify that the component looks and behaves correctly. (There are no changes to the application outside of Storybook at this time.)
Verification Steps for Author
These are to be checked by the author.

[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

Verification Steps for Reviewers
These are to be checked by a reviewer.

Frontend

[ ] User facing changes have been reviewed by design.
[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] There are no new console errors in the browser devtools
[ ] There are no new console errors in the test output
[ ] If this PR adds a new component to Storybook, it ensures the component is fully responsive, OR if it is intentionally not, a wrapping div using the officeApp class or custom min-width styling is used to hide any states the would not be visible to the user.

Screenshots

Messages

:book:
:link: MB-12322

  Generated by :no_entry_sign: dangerJS against 757c3ba3fcf848c7e43ed4e493e81ed77d909d35


ADR lint failing to comment

Describe the bug
When an ADR lint is failing, the comment action is not working
See: https://github.com/asyncapi/studio/actions/runs/5505258920/jobs/10032388819?pr=730
How to Reproduce
Steps to reproduce the issue. Attach all resources that can help us understand the issue:

Create an ADR PR (ex: https://github.com/asyncapi/studio/pull/730)
The PR fail as the label kind/adr is missing
No comment is shown in the PR

Expected behavior

The PR should have a comment with this message This PR must be labled as kind/adr

Hey, I'd like to work on this. But first, I need to understand the issue a little better. Can you elaborate as to exactly when this error needs to be thrown? And also when and where this error is generated?

Hi @depleur ,
Sure, this is handled by .github/workflows/check-adr.yml action.
We are also discussing the issue here: https://github.com/asyncapi/studio/pull/730, probably there is something wrong with the Github Token I'm using.

@depleur for now it should be a quick fix that we try to figure out https://github.com/asyncapi/studio/pull/732

@KhudaDad414 not sure what's wrong https://github.com/asyncapi/studio/actions/runs/5508530383/jobs/10039939243?pr=732

@Amzani pull_request_target should be used instead of pull_request to access the secrets.

@KhudaDad414 works https://github.com/asyncapi/studio/pull/732 thanks mate!


Fix: Enable Socket.send() to write more than 16Kb

tls_write() returns after writing a single message block if
SSL_MODE_ENABLE_PARTIAL_WRITE is enabled, which it is by default when
using tls_configure(). A message block is limited to 16384 bytes
(SSL3_RT_MAX_PLAIN_LENGTH). This patch changes send() to iterate over
the buffer until all data is sent.

Current coverage is 73.22% (diff: 100%)

Merging #28 into master will increase coverage by 11.44%

@@             master        #28   diff @@
==========================================
  Files             5          6     +1
  Lines           191        295   +104
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            118        216    +98
- Misses           73         79     +6
  Partials          0          0

Powered by Codecov. Last update b89595b...66463ef

Thanks!

@andreasley I'll merge this now and tag to fix the bug. But if you want to add a test case to ensure there is no regression, that would be awesome.

@tannernelson Thanks. I'm just getting started with this whole GitHub and Open Source thing, but looking forward to contribute.
I'm not quite sure how to write a proper regression test for this case. It was definitely broken before and is definitely working now – I'm actually crazy enough to be running this in production (no proxy). :)

No worries. :) And welcome to open source!


format new lines in C# types with a  tag

Thanks for the PR.
Makes sense to add...
the optimal solution would be to use a full fledged markdown to HTML converter :)


confused about how to make this work on android when the app is killed

I've been using the firebase modules because this module didnt support firebase until recently. I now want to come back to just using this module for both pushkit and FCM data messages
But I'm very confused about how to make this work for apps killed and not running in the background for android/fcm
in the firebase module I have to set up a background task for dealing with notifications - how am I meant to make this work in this module?

For context this is the payload I'm sending
var message = {
  data: {
    register: 'true'
  },
  android:{
    priority:"high"
  },
  token: registrationToken
};

The more I read this module won't do what I need and won't startup the app on a remote notification without any content (Data message - https://firebase.google.com/docs/cloud-messaging/concept-options)
I'd love someone to either confirm my thoughts or point me in the right direction? RN-Firebase has a background task service allowing me to get messages piped through to a headlessjs task


Crash Report

When editing an attribute of an item in the editor and pressing save, the game crashes.
This is for the new 1.16.2 Beta version BTW.

Fixed by ce34c2bc2649675d25fc3904399b8944c61cc1ad. Expect a fix to be released in a few minutes

@jqck3d Thanks for reporting the issue. A hotfix can be downloaded here: https://www.curseforge.com/minecraft/mc-mods/ibe-editor/files/3051835


Use provider application patterns on support application page

Context
Use provider application review components to display work history and volunteering items in support and generally tidy up the relationship between these two similar pages and their respective components.
Changes proposed in this pull request

Moves headings for application review components into these components (DRYer)
Adjusts size of headings in these components from large to 27px (partly addressing this change)
Remove application related rows from personal details review component
Add a provider-facing application summary component
Include recruitment cycle information in this new application summary (matching prototype)
Update name spacing for work history and volunteering components:

ProviderInterface::WorkHistoryComponent → WorkHistoryComponent
ProviderInterface::VolunteeringHistoryComponent → VolunteeringHistoryComponent
ProviderInterface::WorkHistoryItemComponent → WorkHistoryItemComponent
WorkHistoryReviewComponent → CandidateInterface::WorkHistoryReviewComponent
VolunteeringReviewComponent → CandidateInterface::VolunteeringReviewComponent

Before
After

Guidance to review

Link to Trello card
https://trello.com/c/qfGonFDe
Things to check

[ ] This code does not rely on migrations in the same Pull Request
[ ] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[ ] API release notes have been updated if necessary
[ ] New environment variables have been added to the Azure config

Shall we close this?

@tvararu @tijmenb I have started splitting the components up, but is starting to feel a bit icky as lots of duplicated code, and some components (such as qualifications) are nested, which adds further duplication.
Happy to continue that effort in a separate PR, but feels out of scope for what I was trying to achieve here.

🎉


Do not use the same matcher instance on each wait iteration

Fixes: #20
Some notes on the rootcause and solution:
contain_exactly is one of those matchers that stores some intermediate computations internally. And hence we reuse this matcher object throughout the whole handle_matcher loop, it ignores the actual results and uses it's internal state computed on the first iteration.
The solution proposed is simply to clone initial matcher every iteration.
Please note that I have no idea is the solution is optimal, so any opinions welcome.

I have a feeling this is awesome and needed, but:

I don't really understand what's happening in the tests. Can they be simplified or at least commented?
I'm also confused as to why cloning the matcher doesn't copy the matcher's internal state as well? Is it because we only ever use cloned matchers, so they're cloned from an empty state?
How did you decide between clone and dup?

Thank you for this contribution! 👏

Thank you very much for the immediate response.

Yes they can! I completely forgot there is Enumerator – a better way to have a simple object returning some predefined values on each call. I've updated the tests code.
Yes, exactly like this, we keep initial matcher as a sacred template and only use clones to do actual assertion.
To be honest, it just felt like a safer choice, because clone seems a little more powerful and rspec-expectation class system looks somewhat complicated. Anyways dup works just as well. I can change it if you feel like this is a better choice.

@laserlemon a kind reminder 😃

Sorry for the slight delay in responding to this well-crafted pull request! I'm currently prepping a v1.0 release and will be working to incorporate this behavior. I'll take a slightly deeper dive into the clone vs. dup decision. I might rework the tests a little for my own personal readability but I'll cherry-pick or at least co-author-attribute your contributions. Thank you again and sorry for the tardy reply!

Haha, thank you for looking into this! Yeah it's a good call to give this PR. My knowledge of Ruby completely declined over the past years, so I wouldn't be able to offer any help and it's good to have a person with fresh understanding while merging.

I haven't been able to reproduce the issue with RSpec's latest suite of matchers. But I am able to reproduce the issue in RSpec::Wait's test suite if I define a custom matcher with bad memoization, which is exactly what I did in the v1 branch. But because this issue doesn't seem super prevalent, I decided to build in the clone functionality as an optional configuration. By default, matchers will not be cloned. That decision may change in a future version release. But there are a few ways to get the matcher cloning behavior you built out here:
# You can always globally configure the behavior.
RSpec.configuration.clone_wait_matcher = true

it "clones the matcher using with_wait" do
  with_wait(clone_matcher: true) do
    wait_for { this }.to eq(that)
  end
end

it "clones the matcher using example metadata", wait: { clone_matcher: true } do
  wait_for { this }.to eq(that)
end

it "clones the matcher using wait.for" do
  wait(clone_matcher: true).for { this }.to eq(that)
end

I'm going to close this pull request in favor of the work happening in v1. I've added you as a co-author on the commit introducing this new configuration. Thanks again! 💛


[ZF3] Behat tests fix ref #431

I make behat tests to be green again, and skip failed tests. I will fix that failed tests, and will commit when that tests is ready.

Coverage decreased (-0.02%) to 38.051% when pulling 9abfc36fb919996177b4f0a76aa1049a5cabeaa8 on kilip:develop into 52eca782bf2e69ba4a9fef5c5e64c71b6e2dfcd5 on cross-solution:develop.


"succinct and expressive"

I'd add "composable" to that list. Conversely, "composable, succinct and expressive" can be at odds with "interoperable". Interoperability is not by itself a virtue, it's just one of the quality attributes that one may or may not care about.

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

ID: b63d2086-c15d-2434-8189-c2acaab237ca
Version Independent ID: 08a7d210-bab0-fdd3-5629-34dcc79172e1
Content: F# style guide
Content Source: docs/fsharp/style-guide/index.md
Product: dotnet-fsharp
GitHub Login: @cartermp
Microsoft Alias: phcart

@eiriktsarpalis it would be good to get your perspective on this as well.
The current document states that interoperability is a virtue. My purpose in writing this document is less about interoperability and more about making it clear that the boundaries of pieces of a system matter, and should be considered whenever writing F# code. I think that this is not at odds with "composable, succinct, and expressive".
As it stands, this paragraph could be interpreted in a way that discourages the use composability. @et1975 what do you think?

I'd love to see @swlaschin take as well.


Open playing tab on clicking notification

Current behavior

Nothing happens

This is a duplicate of #1519, isn't it?

Lol
sorry


How to use TBB in opencv Python?

Opencv Python write function, cycle to call this function, parallel computing how to call TBB

Hi @honghande,
Can you explain more your usage model, please?
Are you asking about how to use tbb4py over the OpenCV Python API or about using the TBB underneath OpenCV?
It would be great, if you could share some code snippets.
Thanks!


google maps markers areaselect not working propperly

Hi,
you lib is awesome!! already stared. :-)
I have a problem.
In you deom Markers with no clustering and selection by area and also in my own tests test filtering works if i move the map. But if i change the pie filter or other connected crossfilter the map flickers and stays the same.
Is it working propperly?

It is definitely an issue. The choropleth on that page doesn't work properly either.

Fixed in commit d2087781e20aef1ffe6825a1c77252c667f80dd9 and released in v0.11.5. Please reopen if the problem persists.

Awesome! Thanks for the quick response


Use non-permalink for HIGHEST_SUPPORTED_K8S_VERSION

Reference Issues or PRs
Relates to https://github.com/nebari-dev/nebari/issues/2301, https://github.com/nebari-dev/nebari/pull/2276

What does this implement/fix?
The permalink to an old commit led me down a bit of a rabbit hole through the issues/PRs above to find out Nebari's plans for 1.26's planned EOL (e.g., references above). I think it would make more sense to use a non-permalink so readers are taken to the lastest commit and can see the current maximum supported k8s version. That said, I'm not sure whether the branch should be develop or main (this PR currently uses the default branch of develop).
Put a x in the boxes that apply

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds a feature)
[ ] Breaking change (fix or feature that would cause existing features not to work as expected)
[X] Documentation Update
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build related changes
[ ] Other (please describe):

Testing

[ ] Did you test the pull request locally?
[ ] Did you add new tests?

Documentation

Access-centered content checklist
Text styling

[X] The content is written with plain language (where relevant).
[X] If there are headers, they use the proper header tags (with only one level-one header: H1 or # in markdown).
[X] All links describe where they link to (for example, check the Nebari website).
[X] This content adheres to the Nebari style guides.

Non-text content

[X] All content is represented as text (for example, images need alt text, and videos need captions or descriptive transcripts).
[X] If there are emojis, there are not more than three in a row.
[X] Don't use flashing GIFs or videos.
[X] If the content were to be read as plain text, it still makes sense, and no information is missing.

Any other comments?

Nice catch @maxrjones! Thank you for that. I think it would make more sense to point to the main branch as it is consistent with the latest release (develop might have changes that have not been released yet).

Although I believe the permalink was originally added to make sure we were always linking to that particular line, I think the line numbers in constants.py file do not change that often and readers will benefit to having it linking to the up-to-date version.


Show infinite loop errors through the runner

Currently, these show a pretty useless backtrace at the end and stop further analysing.
Now it shows these errors at the end, like normal cop errors
Before

Inspecting 1 file
C

Offenses:

test.rb:8:3: C: [Corrected] Layout/HashAlignment: Align the keys and values of a hash literal if they span more than one line.
  "deep" => { ...
  ^^^^^^^^^^^
test.rb:8:11: C: [Corrected] Layout/SpaceAroundOperators: Operator => should be surrounded by a single space.
  "deep"  => {
          ^^

0 files inspected, 2 offenses detected, 2 offenses corrected
Infinite loop detected in /home/earlopain/Documents/test/test.rb and caused by Layout/HashAlignment -> Layout/SpaceAroundOperators
Hint: Please update to the latest RuboCop version if not already in use, and report a bug if the issue still occurs on this version.
Please check the latest version at https://rubygems.org/gems/rubocop.
/home/earlopain/Documents/rubocop/lib/rubocop/runner.rb:336:in `check_for_infinite_loop'
/home/earlopain/Documents/rubocop/lib/rubocop/runner.rb:319:in `block in iterate_until_no_changes'
<internal:kernel>:187:in `loop'
/home/earlopain/Documents/rubocop/lib/rubocop/runner.rb:318:in `iterate_until_no_changes'
/home/earlopain/Documents/rubocop/lib/rubocop/runner.rb:287:in `do_inspection_loop'
/home/earlopain/Documents/rubocop/lib/rubocop/runner.rb:168:in `block in file_offenses'
/home/earlopain/Documents/rubocop/lib/rubocop/runner.rb:193:in `file_offense_cache'
/home/earlopain/Documents/rubocop/lib/rubocop/runner.rb:167:in `file_offenses'
/home/earlopain/Documents/rubocop/lib/rubocop/runner.rb:158:in `process_file'
/home/earlopain/Documents/rubocop/lib/rubocop/runner.rb:139:in `block in each_inspected_file'
/home/earlopain/Documents/rubocop/lib/rubocop/runner.rb:138:in `each'
/home/earlopain/Documents/rubocop/lib/rubocop/runner.rb:138:in `reduce'
/home/earlopain/Documents/rubocop/lib/rubocop/runner.rb:138:in `each_inspected_file'
/home/earlopain/Documents/rubocop/lib/rubocop/runner.rb:124:in `inspect_files'
/home/earlopain/Documents/rubocop/lib/rubocop/runner.rb:77:in `run'
/home/earlopain/Documents/rubocop/lib/rubocop/cli/command/execute_runner.rb:26:in `block in execute_runner'
/home/earlopain/Documents/rubocop/lib/rubocop/cli/command/execute_runner.rb:52:in `with_redirect'
/home/earlopain/Documents/rubocop/lib/rubocop/cli/command/execute_runner.rb:25:in `execute_runner'
/home/earlopain/Documents/rubocop/lib/rubocop/cli/command/execute_runner.rb:17:in `run'
/home/earlopain/Documents/rubocop/lib/rubocop/cli/command.rb:11:in `run'
/home/earlopain/Documents/rubocop/lib/rubocop/cli/environment.rb:18:in `run'
/home/earlopain/Documents/rubocop/lib/rubocop/cli.rb:122:in `run_command'
/home/earlopain/Documents/rubocop/lib/rubocop/cli.rb:129:in `execute_runners'
/home/earlopain/Documents/rubocop/lib/rubocop/cli.rb:51:in `block in run'
/home/earlopain/Documents/rubocop/lib/rubocop/cli.rb:81:in `profile_if_needed'
/home/earlopain/Documents/rubocop/lib/rubocop/cli.rb:43:in `run'
/home/earlopain/Documents/rubocop/exe/rubocop:19:in `<top (required)>'
/home/earlopain/.rbenv/versions/3.3.6/lib/ruby/gems/3.3.0/bin/rubocop:25:in `load'
/home/earlopain/.rbenv/versions/3.3.6/lib/ruby/gems/3.3.0/bin/rubocop:25:in `<top (required)>'
/home/earlopain/.rbenv/versions/3.3.6/lib/ruby/gems/3.3.0/gems/bundler-2.6.1/lib/bundler/cli/exec.rb:59:in `load'
/home/earlopain/.rbenv/versions/3.3.6/lib/ruby/gems/3.3.0/gems/bundler-2.6.1/lib/bundler/cli/exec.rb:59:in `kernel_load'
/home/earlopain/.rbenv/versions/3.3.6/lib/ruby/gems/3.3.0/gems/bundler-2.6.1/lib/bundler/cli/exec.rb:23:in `run'
/home/earlopain/.rbenv/versions/3.3.6/lib/ruby/gems/3.3.0/gems/bundler-2.6.1/lib/bundler/cli.rb:452:in `exec'
/home/earlopain/.rbenv/versions/3.3.6/lib/ruby/gems/3.3.0/gems/bundler-2.6.1/lib/bundler/vendor/thor/lib/thor/command.rb:28:in `run'
/home/earlopain/.rbenv/versions/3.3.6/lib/ruby/gems/3.3.0/gems/bundler-2.6.1/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
/home/earlopain/.rbenv/versions/3.3.6/lib/ruby/gems/3.3.0/gems/bundler-2.6.1/lib/bundler/vendor/thor/lib/thor.rb:538:in `dispatch'
/home/earlopain/.rbenv/versions/3.3.6/lib/ruby/gems/3.3.0/gems/bundler-2.6.1/lib/bundler/cli.rb:35:in `dispatch'
/home/earlopain/.rbenv/versions/3.3.6/lib/ruby/gems/3.3.0/gems/bundler-2.6.1/lib/bundler/vendor/thor/lib/thor/base.rb:584:in `start'
/home/earlopain/.rbenv/versions/3.3.6/lib/ruby/gems/3.3.0/gems/bundler-2.6.1/lib/bundler/cli.rb:29:in `start'
/home/earlopain/.rbenv/versions/3.3.6/lib/ruby/gems/3.3.0/gems/bundler-2.6.1/exe/bundle:28:in `block in <top (required)>'
/home/earlopain/.rbenv/versions/3.3.6/lib/ruby/gems/3.3.0/gems/bundler-2.6.1/lib/bundler/friendly_errors.rb:117:in `with_friendly_errors'
/home/earlopain/.rbenv/versions/3.3.6/lib/ruby/gems/3.3.0/gems/bundler-2.6.1/exe/bundle:20:in `<top (required)>'
/home/earlopain/.rbenv/versions/3.3.6/bin/bundle:25:in `load'
/home/earlopain/.rbenv/versions/3.3.6/bin/bundle:25:in `<main>'

After

Inspecting 1 file
Infinite loop detected in /home/earlopain/Documents/test/test.rb and caused by Layout/HashAlignment -> Layout/SpaceAroundOperators
C

Offenses:

test.rb:8:3: C: [Corrected] Layout/HashAlignment: Align the keys and values of a hash literal if they span more than one line.
  "deep" => { ...
  ^^^^^^^^^^^
test.rb:8:11: C: [Corrected] Layout/SpaceAroundOperators: Operator => should be surrounded by a single space.
  "deep"  => {
          ^^

1 file inspected, 2 offenses detected, 2 offenses corrected

1 error occurred:
Infinite loop detected in /home/earlopain/Documents/test/test.rb and caused by Layout/HashAlignment -> Layout/SpaceAroundOperators
Errors are usually caused by RuboCop bugs.
Please, update to the latest RuboCop version if not already in use, and report a bug if the issue still occurs on this version.
https://github.com/rubocop/rubocop/issues

Mention the following information in the issue report:
1.69.2 (using Parser <IP_ADDRESS>, rubocop-ast 1.37.0, analyzing as Ruby 3.3, running on ruby 3.3.6) [x86_64-linux]

I also colored the final error summary at the end in yellow. The infinite loop error did this, and it just looks better that way:

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[ ] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[ ] Squashed related commits together.
[x] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[ ] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

Looks like a good improvement to me. Thanks!


Reoganize the project to split typescript packages and extensions

Fixes https://github.com/jupyterlab/jupyter-chat/issues/72
Reorganizes the project with:

a packages directory containing typescript library (@jupyter/chat and jupyterlab-collaborative-chat)
a python directory containing jupyterlab extension (jupyterlab_collaborative_chat and jupyterlab_ws_chat)

Thanks @jtpio for the review


Add bpaf 0.3.0

As expected - it's the slowest parser but seems to be fast enough for practical purposes.

FYI this is being discussed in #23

I see. If you going to include any benchmark figures - please switch to recently released 0.3.0, I added some more optimizations.

Just updated it to 0.3 before running the benchmarks


Verify users om comment ?

Is There a way to have users auth before posting ? Ie. Use github, Twitter, Facebook profil any other oauth to at least verify their identity to avoid imposters ?

@staticmanlab, the public Staticman instance for GitLab, has implemented eduardoboucas/staticman#231, so that the authentication process of commentators is independent from the Git service provider on which the Git repo of the static site is hosted.  For instance, GitLab Pages served by @staticmanlab can allow commentators authenticated by either GitLab or GitHub.
This PR currently support GitHub and GitLab.  You may add a PR for supporting more OAuth providers if you like.


fix: Update CMA client type []

Updating types for plain client. Changes:
https://github.com/contentful/ui-extensions-sdk/pull/1430
CMAClient is only available from App SDK v4.14.0, but we want to keep compatible with old versions
If CMAClient is available, useCMA should return CMAClient
If CMAClient is not available, useCMA should return PlainClientAPI
Source: https://stackoverflow.com/a/61625831/17270873

LGTM 👍 (can't approve)


[release-v1.11] :bug: Backport proper Istio' quit

Fixes https://issues.redhat.com/browse/SRVKE-1522
Related to https://github.com/knative-extensions/reconciler-test/pull/591
Proposed Changes

:bug: Backport proper Istio' quit

/test 411-test-e2e-aws-ocp-411
Looks like an infra failure

/test 411-test-conformance-aws-ocp-411
Also, looks like a infra failure

/test 413-test-conformance-aws-ocp-413
Same error as the others - looks like an infra

/cc @pierDipi

/hold
Patched files are overriten

I reapplied the patches. Now it matches the changes from: https://github.com/knative-extensions/reconciler-test/compare/9e58415bcb84...f561fc2e2d66

/test 413-test-reconciler-aws-ocp-413
I think this might be an infra failure

/retest

Do we still need to hold this?

/unhold

Thanks @cardil


Release notes for 1.16.0

Release time
2022-05-13
Components involved

ClickHouse

Check list
Enhancement

[x] SSH login is supported #40
[x] Support query ClickHouse to dynamically add configuration
[x] Support metadata management to filter the database

Optimize

[x] Optimize error reporting pop-up window #148

UI

[x] Optimize query history display list
[x] Migrate the software update function to the system menu
[x] Support editor bracket matching

Released


Internal setting to override UA

Task/Issue URL: https://app.asana.com/0/42792087274227/1201464130371298/f
Description
This PR adds the capability to override app UA on internal builds for testing purposes.
Steps to test this PR
Play debug

Install play build
ensure no dev settings are visible
go to serp
search for "what's my user agent"
Ensure UA detected is the expected one (more info inside Asana task)

internal debug

Install internal build
Go to dev settings
toggle on override UA
select any UA from the list
go to serp
search for "what's my user agent"
Ensure UA detected is the expected one

UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

@aitorvs I will ping you once I solve the conflicts in this PR.

@cmonfortep can you take a look at this? I can review it since @aitorvs is away

@aitorvs this is ready for a second review.


feat: New relative_path property for BeforeExecution and AfterExecution events

Codecov Report

Merging #849 (dd80519) into master (5948a55) will decrease coverage by 0.14%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #849      +/-   ##
==========================================
- Coverage   99.10%   98.95%   -0.15%
==========================================
  Files          62       62
  Lines        4225     4226       +1
  Branches      722      722
==========================================
- Hits         4187     4182       -5
- Misses         18       22       +4
- Partials       20       22       +2

Flag
Coverage Δ

unittests
98.95% <100.00%> (-0.12%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

src/schemathesis/runner/events.py
100.00% <100.00%> (ø)

src/schemathesis/_compat.py
50.00% <0.00%> (-50.00%)
:arrow_down:

src/schemathesis/cli/cassettes.py
98.30% <0.00%> (-1.70%)
:arrow_down:

src/schemathesis/extra/pytest_plugin.py
98.37% <0.00%> (-1.63%)
:arrow_down:

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 5948a55...dd80519. Read the comment docs.


Emulator Mangles quotes

The emulator transforms the quote types on its output.   From a debugging / testing point of view this complicates things as the output is not what one expects and turn valid JSON into non-valid JSON
It changes this:
"text"
To this:
“text”
Additionally, the latter types of quotes are not valid when using in JSON.

Can you provide more detailed repro steps? I'm not able to repro from your description. When I copy a json blob from the emulator into a text editor like notepad++, I see plain quotes:
This:

Pastes to this:
{
  "type": "conversationUpdate",
  "membersAdded": [
    {
      "id": "12345",
      "name": "User 1"
    }
  ],
  "id": "iikla18mb45dmf5f",
  "channelId": "emulator",
  "timestamp": "2017-03-20T19:53:00.

Here is what I get.   See first quote before "action"
{“action":{“5f7608e9-60a1-48dd-99f7-a759c5d9b60f":{“NegativeEntities":[],"RequiredEntities":[“2ad4d675-ac3c-48d9-b700-f09a33f9d498","0438a7df-9d3f-47e4-b89d-23bf54a62e96"],"action_type":"text","content":"$color
is a nice color,
$name."},"883106bd-2b59-4bba-8424-a64ee694ee9b":{“NegativeEntities":[“2ad4d675-ac3c-48d9-b700-f09a33f9d498"],"RequiredEntities":[“0438a7df-9d3f-47e4-b89d-23bf54a62e96"],"action_type":"text","content":"What
is your favorite color,
$name?"},"8868ae64-a188-43cc-bf6d-ba8b358532ce":{“NegativeEntities":[“0438a7df-9d3f-47e4-b89d-23bf54a62e96"],"RequiredEntities":[],"action_type":"text","content":"What
is your
name?"}},"blis-app-version":"1.0","entity":{“0438a7df-9d3f-47e4-b89d-23bf54a62e96":{“EntityType":"LUIS","LUISPreName":null,"name":"name"},"2ad4d675-ac3c-48d9-b700-f09a33f9d498":{“EntityType":"LUIS","LUISPreName":null,"name":"color"}},"traindialog":{“b1668d0f-432c-405d-a96e-3c5d1b8fbff7":{“turns":[{“input":{“context":{},"entities":[],"masked-actions":[],"text":"Hi","text-alts":[],"text-entities":[]},"output":"8868ae64-a188-43cc-bf6d-ba8b358532ce"},{“input":{“context":{},"entities":[“0438a7df-9d3f-47e4-b89d-23bf54a62e96"],"masked-actions":[],"text":"Lars","text-alts":[],"text-entities":[{“EndToken":3,"EntityType":"0438a7df-9d3f-47e4-b89d-23bf54a62e96","StartToken":0}]},"output":"883106bd-2b59-4bba-8424-a64ee694ee9b"},{“input":{“context":{},"entities":[“0438a7df-9d3f-47e4-b89d-23bf54a62e96","2ad4d675-ac3c-48d9-b700-f09a33f9d498"],"masked-actions":[],"text":"Blue","text-alts":[],"text-entities":[{“EndToken":3,"EntityType":"2ad4d675-ac3c-48d9-b700-f09a33f9d498","
On Mon, Mar 20, 2017 at 12:55 PM, Eric Anderson<EMAIL_ADDRESS>wrote:

Can you provide more detailed repro steps? I'm not able to repro from your
description. When I copy a json blob from the emulator into a text editor
like notepad++, I see plain quotes:
This:
[image: image]
https://cloud.githubusercontent.com/assets/12176807/24118815/55f97d94-0d6c-11e7-9d34-0a7ba2a2e5ff.png
Pastes to this:
{
"type": "conversationUpdate",
"membersAdded": [
{
"id": "12345",
"name": "User 1"
}
],
"id": "iikla18mb45dmf5f",
"channelId": "emulator",
"timestamp": "2017-03-20T19:53:00.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/BotFramework-Emulator/issues/134#issuecomment-287878574,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGOd5rsddE0YLlSp1HkWtQpWW3iGER5oks5rntmwgaJpZM4Mi59O
.

Clarification.  It's not copying the text the right pane.  This occurs for the Bot's output.

I still don't know how to repro this.

Have your bot output some JSON.  If you swing by my office I can demo.  Thx
On Mar 20, 2017 3:46 PM, "Eric Anderson"<EMAIL_ADDRESS>wrote:
I still don't know how to repro this.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/BotFramework-Emulator/issues/134#issuecomment-287921808,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGOd5m6B5M7MJRbNg6N8Mud5I3fNiR3Wks5rnwHDgaJpZM4Mi59O
.

Thanks for the clarification. Am able to repro now. This is the WebChat control's rendering of the text, the emulator isn't involved. @danmarshall for tracking, but you might want to file an issue there.

As a workaround, you could preformat the message. Example:
reply.text('```\n{"this": "that"}\n```');

I think what you're seeing is correct behavior. Unless you're preformatting the text, the chat control doesn't know you're trying to show code.

Surrounding text with a single backtick does result in code formatting in GitHub e.g. {code} so I would tend to think that since Marked supports "GitHub flavored markdown" it would work.
Next question: why would it quote quotes inside curly brackets?

So the other chat canvases (i.e. Skype, Facebook, etc.) to not have this
issue.  They display the text in the chat canvas exactly as it is sent to
to bot.  It's only in the WebChat/Emulator that it substitutes the quote
type (to one that causes JSON parse failures).
On Tue, Mar 21, 2017 at 9:44 AM, Bill Barnes<EMAIL_ADDRESS>wrote:

Surrounding text with a single backtick does result in code formatting in
GitHub e.g. {code} so I would tend to think that since Marked supports
"GitHub flavored markdown" it would work.
Next question: why would it quote quotes inside curly brackets?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/BotFramework-Emulator/issues/134#issuecomment-288140864,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGOd5i5bbzehkEGEIBxCcm9ZI-ilsUBLks5rn_5mgaJpZM4Mi59O
.

(Seems that requiring preformatting on one canvas but not others causes confusion)

@LarsLiden This will require a change to the WebChat control. Can you file an issue there?


"Failed to produce diagnostic for expression" for SwiftUI View

Describe the bug
The following code produces "Failed to produce diagnostic for expression; please submit a bug report (https://swift.org/contributing/#reporting-bugs) and include the project" on the ContentView body method.
I am aware that the issue is missing braces .padding()
struct ContentView: View {
    var body: some View {
        VStack (alignment: .leading){
            Text("Some text")
                .font(.title)
                .foregroundColor(.black)
            HStack {
                Text("Subheadline 1").font(.subheadline)

                Spacer()

                Text("Subheadline 2").font(.subheadline)
            }
        }
        .padding
    }
}

Screenshot

Thank you for reporting, this issue with un-called reference to padding is something that we are aware of and it should be fixed by https://github.com/apple/swift/pull/58879

Appears to be fixed on main:
error: type '(EdgeInsets) -> some View' cannot conform to 'View'
        .padding
         ^
 note: only concrete types such as structs, enums and classes can conform to protocols
        .padding
         ^
note: required by static method 'buildExpression' where 'Content' = '(EdgeInsets) -> some View'
        .padding
         ^

@ dialadahabi please verify using the latest snapshot of main from swift.org and resolve this issue.

@xedin resolved thanks


Zoom Out keyboard shortcut on Ubuntu

VSCode Version: Code 1.19.3
OS Version: Linux x64 4.13.0-32-generic

I encounter the problem with the VSCode Zoom Out keyboard shortcut on Ubuntu (Ctrl + NumPad_Subtract) it is not working with the laptop keyboard without NumPad layout.

@ASHWINI-GUPTA Please bind the shortcut to a different keybinding using the Keybindings Editor (ctrl+k ctrl+s)


[Question] Client?

Is this a client-only mod or is it required to be on the server as well?

either client, server or both.


Error updating Sceneform Tools 1.11.0

When I updated the plugin Google Sceneform Tools (Beta) to v.1.11.0, I started to get this error message:

Plugin 'google-sceneform-tools' failed to initialize and will be disabled.  Please restart Android Studio.
java.lang.UnsatisfiedLinkError: /tmp/sceneform-loader-jni2523188150614532625/libloader-jni.so: /tmp/sceneform-loader-jni2523188150614532625/libloader-jni.so: undefined symbol: _ZN8filament6Engine7destroyEPKNS_12VertexBufferE
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1941)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1857)
at java.lang.Runtime.loadLibrary0(Runtime.java:870)
at java.lang.System.loadLibrary(System.java:1122)
at com.google.ar.sceneform.plugin.viewer.SceneformSFBProvider.startEngine(SceneformSFBProvider.java:129)
at com.google.ar.sceneform.plugin.viewer.SceneformSFBProvider.initComponent(SceneformSFBProvider.java:37)
at com.intellij.openapi.components.impl.ComponentManagerImpl$ComponentConfigComponentAdapter.getComponentInstance(ComponentManagerImpl.java:486)
at com.intellij.openapi.components.impl.ComponentManagerImpl.createComponents(ComponentManagerImpl.java:104)
at com.intellij.openapi.application.impl.ApplicationImpl.lambda$createComponents$9(ApplicationImpl.java:447)
at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcess$2(CoreProgressManager.java:164)
at com.intellij.openapi.progress.impl.CoreProgressManager.registerIndicatorAndRun(CoreProgressManager.java:582)
at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:532)
at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:87)
at com.intellij.openapi.progress.impl.CoreProgressManager.runProcess(CoreProgressManager.java:151)
at com.intellij.openapi.application.impl.ApplicationImpl.createComponents(ApplicationImpl.java:471)
at com.intellij.openapi.components.impl.ComponentManagerImpl.init(ComponentManagerImpl.java:88)
at com.intellij.openapi.application.impl.ApplicationImpl.load(ApplicationImpl.java:405)
at com.intellij.openapi.application.impl.ApplicationImpl.load(ApplicationImpl.java:391)
at com.intellij.idea.IdeaApplication.run(IdeaApplication.java:217)
at com.intellij.idea.IdeaApplication.lambda$initApplication$0(IdeaApplication.java:77)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:762)
at java.awt.EventQueue.access$500(EventQueue.java:98)
at java.awt.EventQueue$3.run(EventQueue.java:715)
at java.awt.EventQueue$3.run(EventQueue.java:709)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:80)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:732)
at com.intellij.ide.IdeEventQueue.dispatchEvent(IdeEventQueue.java:348)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)

The 1.10.0 version was working fine, now the plugin doesn't work anymore.
OS is Ubuntu 18.04.3 LTS
Android Studio is 3.4.2

I have the same issue.
I also tried Android studio 3.4.1
The only solution I found was to use the Sceneform plugin version 1.7.0 from https://github.com/google-ar/sceneform-android-sdk/releases. This works with studio version 3.4.2
But it gives me some API warnings

WARNING: API 'variant.getMergeAssets()' is obsolete and has been replaced with 'variant.getMergeAssetsProvider()'.
It will be removed at the end of 2019.
For more information, see https://d.android.com/r/tools/task-configuration-avoidance.
To determine what is calling variant.getMergeAssets(), use -Pandroid.debug.obsoleteApi=true on the command line to display more information.
Affected Modules: app

Also, it does not generate the sfb file.

I have the same issue too。

Thanks for the report.  We are working on a fix for the Sceneform plugin.

I've got the same problem, Android Studio 3.4.2 plugin v1.11.0.
But, as a temporary workaround it's possible to use scenefrom assert converter by command line - it generates .sfb and works fine in application, but, sure, no any preview in studio
Link to converter - https://github.com/gdamoreira/google-ar-asset-converter
Hope it'll help someone

We just released v1.11.1 which has the fix for this issue which occurred on Linux and Windows machines.

I still have this problem in MAC OS.

I updated my android studio version to 3.5 and the sceneform to v1.11 (latest version) but then the program crashes with a javaLang error

Hi there:
Android Studio 3.5 + Sceneform plugin v1.11.1 combo seems not to work properly, as it's not able to generate SFA nor SFB files from a FBX file.
Coming back to a fresh Android Studio 3.4 at the moment.


Missing incoming_customers type

Hi!
The Push type has IncomingCustomers payload enum, but there is no type definition for its payload.

It seems that the supposed structure for this payload is:
interface IncomingCustomers {   customers: Customer[];   customer_monitoring_level?: CustomerMonitoringLevel; }

It will be addressed in https://github.com/livechat/lc-sdk-js/pull/120 and following pull requests in previous versions

Issue has been fixed in all non-deprecated versions (v3.3, v3.4, v3.5 and v3.6)


DE report with Solus Budgie reports as "Gnome" instead of Budgie

General description of bug:

What happened:

fastfetch reports DE as "Gnome" instead of "Budgie" with Solus Budgie 4.4 ( not yet released at this moment )

What should happen:

DE should be "Budgie 10.7.2"

Did it work in an older version:

idk

Where did you get the binary:

Built from source myself

Does this issue still occurs in the latest dev build?

yes
Often helpful information:
I patched the source with
diff --git a/src/detection/displayserver/linux/wmde.c b/src/detection/displayserver/linux/wmde.c
index 3022f873..abdff51a 100644
--- a/src/detection/displayserver/linux/wmde.c
+++ b/src/detection/displayserver/linux/wmde.c
@@ -286,6 +286,8 @@ static void applyPrettyNameIfDE(FFDisplayServerResult* result, const char* name)
         return;
     else if(strcasestr(name, "plasma") != NULL || strcasecmp(name, "KDE") == 0)
         getKDE(result);
+    else if(strcasestr(name, "budgie:gnome") != NULL)
+        getBudgie(result);
     else if(
         strcasecmp(name, "polkit-gnome") != 0 &&
         strcasecmp(name, "gnome-keyring") != 0 &&

and this fixed it.

Please test if it works for you


Corsi translation improvements

RPUICorsiBlockTappingActivityBody had no translations.
added trsnaltions for english and french

the corsi intro iamge was blurry and in english only. Sharpened tohe image, and added a french version
Note; I can send the ppt so you can generate the other languages
Note 2: I could not figure out how to get the language code from CPlocalizations, so I used a kludgy compare of  translate.

you can find the corsi images here: https://docs.google.com/presentation/d/1S9vK0f83KZvGiQg4SyRUB-F4VZeBpWzr/edit?usp=sharing&ouid=107492831009102129141&rtpof=true&sd=true