[MM-17614] Handle error fetching project e.g. a project was deleted

Summary
This PR lets the webapp gracefully handle when a project is missing from an existing channel subscription. The modal would normally crash in this case. This PR also keeps into account deleted custom fields and issue types.
Ticket Link
https://mattermost.atlassian.net/browse/MM-17614

@levb

If it is not intended for 5.14, I'd 1/5 suggest consolidating all this logic in the server

The server side should definitely be doing the data validation. However, I wasn't sure where in the webhook/subscription pipeline the validation/cleanup would occur. The main requirement here was to not have the modal crash.
Having a lingering project/event etc in the subscription currently does not negatively affect the webhook processing, though we don't want stale data. This PR makes it so the next time the user saves the subscription, the stale data is removed.
The UX around this issue can be improved as well. The error message returned from the backend when a project's metadata cannot be fetched from Jira is You do not have permission to create issues in that project. Please contact your Jira admin. I haven't verified, but I assume that as far as our backend's knowledge goes when processing Jira's response, these two scenarios may be identical (project deleted vs lack of permissions). With that in mind, we should try to explicitly separate these two scenarios, as we don't want to destroy a subscription's config just because the user doesn't have permissions to manage the configured project.

Is it intended for 5.14? If so, we should label the Jira ticket and this PR accordingly.

I'm not sure about the impact of the fix, so I'm not sure about when this should be released. Considering this is likely not a all-inclusive solution, maybe this should hold off?

@mickmister What should I be reviewing on this?

@aaronrothschild This is mainly a fix for not crashing the modal, so I suppose not anything to review. I have a more detailed explanation in a comment above but here are screenshots:
Before project is deleted in Jira

Project is deleted before opening modal this time


ISPN-11472 fixes for Hot Rod Client docs

https://issues.redhat.com/browse/ISPN-11472
needs backport to 10.1.x

integrated! thanks @oraNod !


CapacitorStripeProvider for Angular

Describe the solution you'd like
Would like to implement Stripe with different publishkey depends on currency as we having multi national stripe account.
CapacitorStripeProvider seem can fit my requirement but I only find the implementation for React but no angular version.
Any possible to have this work on angular? Thanks

No, CapacitorStripeProvider is use React hooks. So can't work on Angular.


liked and unliked error on Posts

in the first image, i liked the post, but the count of the like is not increasing,

in the second image, i unliked the post , but still the count is same,

and the like button is not filled with blue, sometimes, (as i liked it before)

finally the color is not changing,but the count is changing

the color is changing only when we  refresh the page,

so the possible solution is not to use the material UI, like button, but to use our own like button, where we can change the css styles, when it is liked and unliked.

I am working on this.

the color is changing only when we refresh the page,

Yes, This is true. Good issue.


code of docs about create pptx result without any content

[ √ ] Question on library usage

https://docs.microsoft.com/en-us/office/open-xml/how-to-create-a-presentation-document-by-providing-a-file-name
sample code same to docs
ConsoleApp.zip
result:

link doesn't resolve, but this appears to be the correct link now: https://learn.microsoft.com/en-us/office/open-xml/presentation/how-to-create-a-presentation-document-by-providing-a-file-name?tabs=cs


ds-12872 ocp-latest-version 4.14

RHODS-12872, update ocp-latest-version attribute to 4.14, replace 4.13 in links with attribute

I focused on checking the links. It looks good.


Improve cold-start and package installation

Maybe it helps to check if a cached response is already available. Especially for the default snippet ...

I was now able to squeeze in everything to the lambda package using npm-prune. Cold start is quite awesome now :-)

Fixed by packaging all the modules into the lambda deployment package


Why use minimal action set and not legal action set like in Revisiting ALE paper?

I think this is an issue for reproducibility and comparaison.
The paper "Revisiting ALE [...]" by Machado et al. (2018) use the full action set (18 actions) on all games and it's hard to know what is exactly the impact of giving MinimalActionSet compared to FullActionSet.
I know that this was an issue to reproduce Breakout result:
"DeepMind used a minimal set of four actions in Breakout (xitari), several versions of OpenAi gym’s Breakout have six actions. Additional actions can alter the difficulty of the task the agent is trying to learn drastically! The Breakout-v4 and BreakoutDeterministic-v4 environments have four actions (check with env.unwrapped.get_action_meanings())." (from this blog)

Fair point, in hindsight minimal actions were a mistake from day one. IIRC it was more difficult to use the full action set when operating via Gym. It would also make the results less comparable to what's already published (but we've pushed this with enabling sticky actions anyway).


test(test-tooling): fix flaky rustc-container-target-nodejs.test

Marking this as a good first issue because most likely it's due to some race condition
in the code that someone with sufficient general knowledge of programming should be
able to debug with little knowledge/understanding about the architecture of Cactus
as a whole.
The path of the test file is:
packages/cactus-test-tooling/src/test/typescript/integration/rustc-container/rustc-container-target-nodejs.test.ts
Logs
Full CI logs archive: logs_11827.zip
It passes fine most of the time, but every now and then it fails with logs like this:
2021-12-08T05:46:29.9872651Z
2021-12-08T05:51:34.8397514Z FAIL packages/cactus-test-tooling/src/test/typescript/integration/rustc-container/rustc-container-target-nodejs.test.ts (312.72 s)
2021-12-08T05:51:34.8468546Z   ● Console
2021-12-08T05:51:34.8469295Z
2021-12-08T05:51:34.8470197Z     console.log
2021-12-08T05:51:34.8471691Z       [2021-12-08T05:46:28.662Z] DEBUG (RustcContainer): Created instance of RustcContainer OK
2021-12-08T05:51:34.8472203Z
2021-12-08T05:51:34.8473384Z       at Logger.<anonymous> (node_modules/loglevel-plugin-prefix/lib/loglevel-plugin-prefix.js:106:24)
2021-12-08T05:51:34.8474072Z
2021-12-08T05:51:34.8474412Z     console.log
2021-12-08T05:51:34.8475465Z       [2021-12-08T05:46:28.682Z] DEBUG (RustcContainer): Pulling image ghcr.io/hyperledger/cactus-rust-compiler:1.0.3...
2021-12-08T05:51:34.8476061Z
2021-12-08T05:51:34.8477071Z       at Logger.<anonymous> (node_modules/loglevel-plugin-prefix/lib/loglevel-plugin-prefix.js:106:24)
2021-12-08T05:51:34.8477757Z
2021-12-08T05:51:34.8478102Z     console.log
2021-12-08T05:51:34.8479275Z       [2021-12-08T05:46:29.100Z] DEBUG (containers#tryPullImage()): Started ghcr.io/hyperledger/cactus-rust-compiler:1.0.3 pull progress stream OK
2021-12-08T05:51:34.8479962Z
2021-12-08T05:51:34.8481012Z       at Logger.<anonymous> (node_modules/loglevel-plugin-prefix/lib/loglevel-plugin-prefix.js:106:24)
2021-12-08T05:51:34.8481695Z
2021-12-08T05:51:34.8482029Z     console.log
2021-12-08T05:51:34.8483059Z       [2021-12-08T05:46:29.122Z] DEBUG (containers#tryPullImage()): "Pulling from hyperledger/cactus-rust-compiler"
2021-12-08T05:51:34.8483650Z
2021-12-08T05:51:34.8484695Z       at Logger.<anonymous> (node_modules/loglevel-plugin-prefix/lib/loglevel-plugin-prefix.js:106:24)
2021-12-08T05:51:34.8485377Z
2021-12-08T05:51:34.8485726Z     console.log
2021-12-08T05:51:34.8486680Z       [2021-12-08T05:46:30.123Z] DEBUG (containers#tryPullImage()): "[==========>                                        ]  40.03MB/195.5MB"
2021-12-08T05:51:34.8487102Z
2021-12-08T05:51:34.8488163Z       at Logger.<anonymous> (node_modules/loglevel-plugin-prefix/lib/loglevel-plugin-prefix.js:106:24)
2021-12-08T05:51:34.8488855Z
2021-12-08T05:51:34.8489240Z     console.log
2021-12-08T05:51:34.8490182Z       [2021-12-08T05:46:31.125Z] DEBUG (containers#tryPullImage()): "[=============================================>     ]  178.6MB/195.5MB"
2021-12-08T05:51:34.8490645Z
2021-12-08T05:51:34.8491692Z       at Logger.<anonymous> (node_modules/loglevel-plugin-prefix/lib/loglevel-plugin-prefix.js:106:24)
2021-12-08T05:51:34.8492385Z
2021-12-08T05:51:34.8492745Z     console.log
2021-12-08T05:51:34.8493666Z       [2021-12-08T05:46:32.194Z] DEBUG (containers#tryPullImage()): "[=>                                                 ]  5.571MB/195.5MB"
2021-12-08T05:51:34.8494100Z
2021-12-08T05:51:34.8495165Z       at Logger.<anonymous> (node_modules/loglevel-plugin-prefix/lib/loglevel-plugin-prefix.js:106:24)
2021-12-08T05:51:34.8495856Z
2021-12-08T05:51:34.8496195Z     console.log
2021-12-08T05:51:34.8497956Z       [2021-12-08T05:46:33.197Z] DEBUG (containers#tryPullImage()): "[=======>                                           ]  28.41MB/195.5MB"
2021-12-08T05:51:34.8498407Z
2021-12-08T05:51:34.8499477Z       at Logger.<anonymous> (node_modules/loglevel-plugin-prefix/lib/loglevel-plugin-prefix.js:106:24)
2021-12-08T05:51:34.8500338Z
2021-12-08T05:51:34.8500711Z     console.log
2021-12-08T05:51:34.8501689Z       [2021-12-08T05:46:34.202Z] DEBUG (containers#tryPullImage()): "[===================>                               ]  75.76MB/195.5MB"
2021-12-08T05:51:34.8502123Z
2021-12-08T05:51:34.8503244Z       at Logger.<anonymous> (node_modules/loglevel-plugin-prefix/lib/loglevel-plugin-prefix.js:106:24)
2021-12-08T05:51:34.8503957Z
2021-12-08T05:51:34.8504296Z     console.log
2021-12-08T05:51:34.8505236Z       [2021-12-08T05:46:35.203Z] DEBUG (containers#tryPullImage()): "[=============================>                     ]  114.2MB/195.5MB"
2021-12-08T05:51:34.8505671Z
2021-12-08T05:51:34.8506744Z       at Logger.<anonymous> (node_modules/loglevel-plugin-prefix/lib/loglevel-plugin-prefix.js:106:24)
2021-12-08T05:51:34.8507455Z
2021-12-08T05:51:34.8507815Z     console.log
2021-12-08T05:51:34.8508754Z       [2021-12-08T05:46:36.231Z] DEBUG (containers#tryPullImage()): "[========================================>          ]  158.2MB/195.5MB"
2021-12-08T05:51:34.8509184Z
2021-12-08T05:51:34.8510493Z       at Logger.<anonymous> (node_modules/loglevel-plugin-prefix/lib/loglevel-plugin-prefix.js:106:24)
2021-12-08T05:51:34.8513936Z
2021-12-08T05:51:34.8514351Z     console.log
2021-12-08T05:51:34.8515505Z       [2021-12-08T05:46:37.232Z] DEBUG (containers#tryPullImage()): "[==================================================>]  195.5MB/195.5MB"
2021-12-08T05:51:34.8515930Z
2021-12-08T05:51:34.8516943Z       at Logger.<anonymous> (node_modules/loglevel-plugin-prefix/lib/loglevel-plugin-prefix.js:106:24)
2021-12-08T05:51:34.8517625Z
2021-12-08T05:51:34.8517977Z     console.log
2021-12-08T05:51:34.8518764Z       [2021-12-08T05:46:39.037Z] DEBUG (containers#tryPullImage()): "Pull complete"
2021-12-08T05:51:34.8519208Z
2021-12-08T05:51:34.8520229Z       at Logger.<anonymous> (node_modules/loglevel-plugin-prefix/lib/loglevel-plugin-prefix.js:106:24)
2021-12-08T05:51:34.8520896Z
2021-12-08T05:51:34.8521225Z     console.log
2021-12-08T05:51:34.8522119Z       [2021-12-08T05:46:40.037Z] DEBUG (containers#tryPullImage()): "[===================>                               ]  20.45MB/51.15MB"
2021-12-08T05:51:34.8522539Z
2021-12-08T05:51:34.8523542Z       at Logger.<anonymous> (node_modules/loglevel-plugin-prefix/lib/loglevel-plugin-prefix.js:106:24)
2021-12-08T05:51:34.8524217Z
2021-12-08T05:51:34.8524565Z     console.log
2021-12-08T05:51:34.8525422Z       [2021-12-08T05:46:41.041Z] DEBUG (containers#tryPullImage()): "[=================================================> ]  50.86MB/51.15MB"
2021-12-08T05:51:34.8525843Z
2021-12-08T05:51:34.8526856Z       at Logger.<anonymous> (node_modules/loglevel-plugin-prefix/lib/loglevel-plugin-prefix.js:106:24)
2021-12-08T05:51:34.8527537Z
2021-12-08T05:51:34.8583151Z     console.log
2021-12-08T05:51:34.8584645Z       [2021-12-08T05:46:42.041Z] DEBUG (containers#tryPullImage()): "[>                                                  ]  557.1kB/102.8MB"
2021-12-08T05:51:34.8585082Z
2021-12-08T05:51:34.8586158Z       at Logger.<anonymous> (node_modules/loglevel-plugin-prefix/lib/loglevel-plugin-prefix.js:106:24)
2021-12-08T05:51:34.8586839Z
2021-12-08T05:51:34.8587196Z     console.log
2021-12-08T05:51:34.8588068Z       [2021-12-08T05:46:43.058Z] DEBUG (containers#tryPullImage()): "[===========================================>       ]  89.13MB/102.8MB"
2021-12-08T05:51:34.8588486Z
2021-12-08T05:51:34.8589552Z       at Logger.<anonymous> (node_modules/loglevel-plugin-prefix/lib/loglevel-plugin-prefix.js:106:24)
2021-12-08T05:51:34.8590224Z
2021-12-08T05:51:34.8590557Z     console.log
2021-12-08T05:51:34.8591452Z       [2021-12-08T05:46:44.094Z] DEBUG (containers#tryPullImage()): "[===============================================>   ]  96.93MB/102.8MB"
2021-12-08T05:51:34.8592343Z
2021-12-08T05:51:34.8593366Z       at Logger.<anonymous> (node_modules/loglevel-plugin-prefix/lib/loglevel-plugin-prefix.js:106:24)
2021-12-08T05:51:34.8594042Z
2021-12-08T05:51:34.8594393Z     console.log
2021-12-08T05:51:34.8595390Z       [2021-12-08T05:46:45.099Z] DEBUG (containers#tryPullImage()): "[==================================================>]  102.8MB/102.8MB"
2021-12-08T05:51:34.8595813Z
2021-12-08T05:51:34.8596837Z       at Logger.<anonymous> (node_modules/loglevel-plugin-prefix/lib/loglevel-plugin-prefix.js:106:24)
2021-12-08T05:51:34.8597513Z
2021-12-08T05:51:34.8597844Z     console.log
2021-12-08T05:51:34.8598636Z       [2021-12-08T05:46:45.699Z] DEBUG (containers#tryPullImage()): "Pull complete"
2021-12-08T05:51:34.8599060Z
2021-12-08T05:51:34.8600062Z       at Logger.<anonymous> (node_modules/loglevel-plugin-prefix/lib/loglevel-plugin-prefix.js:106:24)
2021-12-08T05:51:34.8600737Z
2021-12-08T05:51:34.8601090Z     console.log
2021-12-08T05:51:34.8602224Z       [2021-12-08T05:46:45.705Z] DEBUG (containers#tryPullImage()): Finished ghcr.io/hyperledger/cactus-rust-compiler:1.0.3 pull completely OK
2021-12-08T05:51:34.8602894Z
2021-12-08T05:51:34.8603913Z       at Logger.<anonymous> (node_modules/loglevel-plugin-prefix/lib/loglevel-plugin-prefix.js:106:24)
2021-12-08T05:51:34.8604589Z
2021-12-08T05:51:34.8604918Z     console.log
2021-12-08T05:51:34.8605933Z       [2021-12-08T05:46:45.706Z] DEBUG (RustcContainer): Pulled image ghcr.io/hyperledger/cactus-rust-compiler:1.0.3 OK
2021-12-08T05:51:34.8606523Z
2021-12-08T05:51:34.8607524Z       at Logger.<anonymous> (node_modules/loglevel-plugin-prefix/lib/loglevel-plugin-prefix.js:106:24)
2021-12-08T05:51:34.8608198Z
2021-12-08T05:51:34.8608543Z     console.log
2021-12-08T05:51:34.8609590Z       [2021-12-08T05:46:45.706Z] DEBUG (RustcContainer): Starting ghcr.io/hyperledger/cactus-rust-compiler:1.0.3 with options:  {
2021-12-08T05:51:34.8610650Z         WorkingDir: '/usr/src/host-sources-dir/',
2021-12-08T05:51:34.8611121Z         Env: [],
2021-12-08T05:51:34.8611510Z         Healthcheck: {
2021-12-08T05:51:34.8611901Z           Test: [
2021-12-08T05:51:34.8612390Z             'CMD-SHELL',
2021-12-08T05:51:34.8613111Z             'rustup --version && rustc --version && cargo --version'
2021-12-08T05:51:34.8613582Z           ],
2021-12-08T05:51:34.8613958Z           Interval:<PHONE_NUMBER>,
2021-12-08T05:51:34.8614366Z           Timeout:<PHONE_NUMBER>,
2021-12-08T05:51:34.8614752Z           Retries: 10,
2021-12-08T05:51:34.8615179Z           StartPeriod:<PHONE_NUMBER>
2021-12-08T05:51:34.8615539Z         },
2021-12-08T05:51:34.8616021Z         HostConfig: { AutoRemove: true, Binds: [] }
2021-12-08T05:51:34.8616442Z       }
2021-12-08T05:51:34.8616656Z
2021-12-08T05:51:34.8632372Z       at Logger.<anonymous> (node_modules/loglevel-plugin-prefix/lib/loglevel-plugin-prefix.js:106:24)
2021-12-08T05:51:34.8633129Z
2021-12-08T05:51:34.8633482Z     console.log
2021-12-08T05:51:34.8635558Z       [2021-12-08T05:46:45.988Z] DEBUG (RustcContainer): Started ghcr.io/hyperledger/cactus-rust-compiler:1.0.3 successfully. ID=23aa7af045225cfc5b3c8fbda68dfd5a81e1ec3ffb9936d14f93f138f657938c
2021-12-08T05:51:34.8636785Z
2021-12-08T05:51:34.8637812Z       at Logger.<anonymous> (node_modules/loglevel-plugin-prefix/lib/loglevel-plugin-prefix.js:106:24)
2021-12-08T05:51:34.8638520Z
2021-12-08T05:51:34.8638892Z     console.log
2021-12-08T05:51:34.8639771Z       [2021-12-08T05:46:45.991Z] DEBUG (RustcContainer): Registered container log stream callbacks OK
2021-12-08T05:51:34.8640274Z
2021-12-08T05:51:34.8641297Z       at Logger.<anonymous> (node_modules/loglevel-plugin-prefix/lib/loglevel-plugin-prefix.js:106:24)
2021-12-08T05:51:34.8641977Z
2021-12-08T05:51:34.8642309Z     console.log
2021-12-08T05:51:34.8643147Z       [2021-12-08T05:46:45.991Z] DEBUG (RustcContainer): Starting to wait for healthcheck...
2021-12-08T05:51:34.8643604Z
2021-12-08T05:51:34.8644609Z       at Logger.<anonymous> (node_modules/loglevel-plugin-prefix/lib/loglevel-plugin-prefix.js:106:24)
2021-12-08T05:51:34.8645549Z
2021-12-08T05:51:34.8645900Z     console.log
2021-12-08T05:51:34.8647078Z       [2021-12-08T05:46:46.699Z] DEBUG (containers#tryPullImage()): "Status: Downloaded newer image for ghcr.io/hyperledger/cactus-rust-compiler:1.0.3"
2021-12-08T05:51:34.8647876Z
2021-12-08T05:51:34.8648920Z       at Logger.<anonymous> (node_modules/loglevel-plugin-prefix/lib/loglevel-plugin-prefix.js:106:24)
2021-12-08T05:51:34.8649596Z
2021-12-08T05:51:34.8649930Z     console.log
2021-12-08T05:51:34.8650711Z       [2021-12-08T05:46:49.010Z] DEBUG (RustcContainer): Healthcheck passed OK
2021-12-08T05:51:34.8651133Z
2021-12-08T05:51:34.8652129Z       at Logger.<anonymous> (node_modules/loglevel-plugin-prefix/lib/loglevel-plugin-prefix.js:106:24)
2021-12-08T05:51:34.8652802Z
2021-12-08T05:51:34.8653811Z   ● compiles Rust code to NodeJS targeted .wasm › compiles Rust code to NodeJS targeted .wasm
2021-12-08T05:51:34.8654305Z
2021-12-08T05:51:34.8654823Z     expect(received).toEqual(expected) // deep equality
2021-12-08T05:51:34.8655220Z
2021-12-08T05:51:34.8655690Z     - Expected  - 5
2021-12-08T05:51:34.8656069Z     + Received  + 0
2021-12-08T05:51:34.8656318Z
2021-12-08T05:51:34.8656635Z       Array [
2021-12-08T05:51:34.8657001Z         ".gitignore",
2021-12-08T05:51:34.8658455Z     -   "hello_world.d.ts",
2021-12-08T05:51:34.8659028Z     -   "hello_world.js",
2021-12-08T05:51:34.8659575Z     -   "hello_world_bg.wasm",
2021-12-08T05:51:34.8660182Z     -   "hello_world_bg.wasm.d.ts",
2021-12-08T05:51:34.8660752Z     -   "package.json",
2021-12-08T05:51:34.8661124Z       ]
2021-12-08T05:51:34.8661334Z
2021-12-08T05:51:34.8661782Z       94 |     expect(filesOnFs).toBeTruthy();
2021-12-08T05:51:34.8662421Z       95 |     expect(Array.isArray(filesOnFs)).toBe(true);
2021-12-08T05:51:34.8663093Z     > 96 |     expect(filesOnFs).toEqual(expectedFiles);
2021-12-08T05:51:34.8663621Z          |                       ^
2021-12-08T05:51:34.8663968Z       97 |
2021-12-08T05:51:34.8664498Z       98 |     const fileChecks = filesOnFs.map(async (fileName) => {
2021-12-08T05:51:34.8665346Z       99 |       const containerFilePath = path.join(containerPkDir, fileName);
2021-12-08T05:51:34.8665848Z
2021-12-08T05:51:34.8667242Z       at Object.<anonymous> (packages/cactus-test-tooling/src/test/typescript/integration/rustc-container/rustc-container-target-nodejs.test.ts:96:23)
2021-12-08T05:51:34.8668465Z           at runMicrotasks (<anonymous>)
2021-12-08T05:51:34.8668788Z

2021-12-08T05:54:55.7496373Z Summary of all failing tests
2021-12-08T05:54:55.7503536Z FAIL packages/cactus-test-tooling/src/test/typescript/integration/rustc-container/rustc-container-target-nodejs.test.ts (312.72 s)
2021-12-08T05:54:55.7505502Z   ● compiles Rust code to NodeJS targeted .wasm › compiles Rust code to NodeJS targeted .wasm
2021-12-08T05:54:55.7506256Z
2021-12-08T05:54:55.7506958Z     expect(received).toEqual(expected) // deep equality
2021-12-08T05:54:55.7507534Z
2021-12-08T05:54:55.7508244Z     - Expected  - 5
2021-12-08T05:54:55.7508835Z     + Received  + 0
2021-12-08T05:54:55.7509263Z
2021-12-08T05:54:55.7509769Z       Array [
2021-12-08T05:54:55.7510312Z         ".gitignore",
2021-12-08T05:54:55.7511055Z     -   "hello_world.d.ts",
2021-12-08T05:54:55.7511817Z     -   "hello_world.js",
2021-12-08T05:54:55.7512580Z     -   "hello_world_bg.wasm",
2021-12-08T05:54:55.7513387Z     -   "hello_world_bg.wasm.d.ts",
2021-12-08T05:54:55.7514213Z     -   "package.json",
2021-12-08T05:54:55.7514763Z       ]
2021-12-08T05:54:55.7515149Z
2021-12-08T05:54:55.7515801Z       94 |     expect(filesOnFs).toBeTruthy();
2021-12-08T05:54:55.7516609Z       95 |     expect(Array.isArray(filesOnFs)).toBe(true);
2021-12-08T05:54:55.7518110Z     > 96 |     expect(filesOnFs).toEqual(expectedFiles);
2021-12-08T05:54:55.7518806Z          |                       ^
2021-12-08T05:54:55.7519257Z       97 |
2021-12-08T05:54:55.7519923Z       98 |     const fileChecks = filesOnFs.map(async (fileName) => {
2021-12-08T05:54:55.7520928Z       99 |       const containerFilePath = path.join(containerPkDir, fileName);
2021-12-08T05:54:55.7521540Z
2021-12-08T05:54:55.7523128Z       at Object.<anonymous> (packages/cactus-test-tooling/src/test/typescript/integration/rustc-container/rustc-container-target-nodejs.test.ts:96:23)
2021-12-08T05:54:55.7529444Z           at runMicrotasks (<anonymous>)
2021-12-08T05:54:55.7530052Z
2021-12-08T05:54:55.7530377Z
2021-12-08T05:54:55.7531049Z Test Suites: 1 failed, 77 passed, 78 total
2021-12-08T05:54:55.7531761Z Tests:       1 failed, 105 passed, 106 total
2021-12-08T05:54:55.7532748Z Snapshots:   0 total
2021-12-08T05:54:55.7533270Z Time:        850.936 s
2021-12-08T05:54:55.7533795Z Ran all test suites.

Version
1.0.0-rc.3

Inspecting the cargo / wasm-pack build output logs with the debugger offered some clues:
wasmPackBuildOut
'[INFO]: Checking for the Wasm target...
info: (Bdownloading component 'rust-std' for 'wasm32-unknown-unknown'
info: (Binstalling component 'rust-std' for 'wasm32-unknown-unknown'
info: (Busing up to 500.0 MiB of RAM to unpack components

  6.9 MiB /  13.2 MiB ( 53 %)   0 B/s in  1s ETA: Unknown

  9.8 MiB /  13.2 MiB ( 74 %)   6.9 MiB/s in  2s ETA:  0s

 13.2 MiB /  13.2 MiB (100 %)   4.9 MiB/s in  2s ETA:  0s
[INFO]: Compiling to Wasm...
   Compiling proc-macro2 v1.0.36
   Compiling unicode-xid v0.2.2
   Compiling log v0.4.14
   Compiling wasm-bindgen-shared v0.2.78
   Compiling syn v1.0.85
   Compiling cfg-if v1.0.0
   Compiling lazy_static v1.4.0
   Compiling bumpalo v3.9.1
error[E0658]: arbitrary expressions in key-value attributes are unstable
 --> /usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/bumpalo-3.9.1/src/lib.rs:1:10
  |
1 | #![doc = include_str!("../README.md")]
  |          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  |
  = note: see issue #78835 <https://github.com/rust-lang/rust/issues/78835> for more information

   Compiling wasm-bindgen v0.2.78
error: aborting due to previous error

For more information about this error, try `rustc --explain E0658`.
error: could not compile `bumpalo`

To learn more, run the command again with --verbose.
warning: build failed, waiting for other jobs to finish...
error: build failed
Error: Compiling your crate to WebAssembly failed
Caused by: failed to execute `cargo build`: exited with exit code: 101
  full command: "cargo" "build" "--lib" "--release" "--target" "wasm32-unknown-unknown"
'


Silent crash of whole application when redix has password configured for redis with auth disabled

I had hard time debugging this today.
Redix is crashing whole app when we provide redis password for redix and there's no configured password/auth on redis side.
When it would be ok, there's no error thrown or logged so debugging was pain.

@JuniorJPDJ can you provide an small reproducing example, maybe using Docker?

I'm not erlang/elixir programmer, but I suspect you know how to log into redis using your library ;)
Normal redis server container running doesn't automatically enable auth, so just start redis docker container and try to connect to this redis server using correct host, port and provide random password (any). It should crash silently.
We are using ~1.1.5 redix version.

No need for snark 🙃

I meant I don't really know but you probably can figure it out :D
Nothing mean from my side.
Thank you for fix!


Add intro/outro to video

Related Issue
No response
Description
Video here

Add intro/outro (if necessary)
Mosaic the URL

Hi @Steve-Mcl the video is here. I've applied the FlowFuse outro, added the FlowFuse logo to the intro, blurred the URLs, and made some audio adjustments.
I think it looks pretty good but, next time, I'd recommend using the full width of the screen for the video, unless we're doing something different, like a YouTube short or content for Instagram (even though we don't currently have an account), which might require specific proportions.
I realise you didn't have a guide to work on this, will update the handbook to provide some 😉

https://www.youtube.com/watch?v=pCYzJGVkG8s


Feature Request:  Filter or search options when adding a new queue/printer

Would it be possible to add search and filter options for the following areas when adding printers/print queues for the web admin interface?
"Discovered Network Printers" - search or filter via IP or other search criteria to narrow down from the list
Based on the text that's auto populated in discovery it can be hard to determine which printer is which, especially if no IP is
shown.  This can be problematic on networks with over 20 printers.
"Model" - search via model number to narrow PPD list
This is especially difficult when setting up an HP printer as the selection list for PPD's is quite long.
Attaching screenshots of said areas.
Apologies if this is the wrong venue for feature requests.

Hi @jcdouglas ,
thank you for the feature request!
Ad the first part - the PR #397 should help with that, so please check the PR in question.
Ad the second part - the listed models there are actually drivers which you have on your machine, and CUPS is going to remove the driver support in the near future, so we are not going to implement such filters for model lists.


Add a reference to assignment descriptions to the grader

@aemonk summarized all assignment descriptions from the cc2020 slack channel into a Markdown file as a quick reference. In the grader, we could add references back to the descriptions of each assignment so that the aim of each assignment is easier to understand.
Reference: https://cksystemsteaching.slack.com/archives/CUQUKPD61/p1598390644002700

One question that we may need to discuss is how the link to the document should be made. The way I see it, there are two possible ways:

Head of master: The description link points to the newest commit pushed to a specific branch. If we change the description of an assignment, we don't necessarily have to update the link in the grader to point to the newest version.
(e.g. https://github.com/cksystemsteaching/selfie/blob/grader/grader/compiler-assignments.md#assignment-0)
Specific commit: The description link points to a specific commit. If new changes are pushed to any branch on the repository, the link to the description will still point to the same version as before. This approach requires manual adjustment even if we just refine the description, but makes the history more understandable, e.g. if we introduced a lot of changes to an assignment, older commits with the old assignment version would still point to an older version of the assignment description instead of the newer, potentially incompatible one.
(e.g. https://github.com/cksystemsteaching/selfie/blob/9073bc2c49f688b9ff14a3332fed5787f594dd34/grader/compiler-assignments.md#assignment-0)

I recommend to do head of master but not number the assignments. Just use names. Is that possible?

GitHub automatically creates IDs corresponding to the heading. We could try to explicitly add another ID, as suggested by this StackOverflow answer. If this did not work, we would need to edit the heading itself.

Ok!


String "" causes the code to stop when embedded into html

In remark.min.js, the part of the code:
{end:"</script>",returnEnd:!0,subLanguage

produces an end to remark processing when remark is placed inline in an html file due to the string </script> being parsed as end of remark script
changing that string to <\/script> seems to "fix" the problem

Example of remark output with inline script

Closed due to inactivity


Fix bn_addrelu's bitmask type error

This patch converts torch.cuda.LongTensor's argument of bn_addrelu's
bitmask to int to fix the type error.

@sarunyap Can you mention the error and testcase/command you were running into that needed this fix?

We ran SSD and got the following error:
File "/opt/conda/lib/python3.7/site-packages/apex/contrib/groupbn/batch_norm.py", line 69, in forward     bitmask = torch.cuda.LongTensor(((nhw + 3) & ~3) * grid_dim_y) TypeError: expected TensorOptions(dtype=long int, device=cuda, layout=Strided, requires_grad=false (default), pinned_memory=false (default), memory_format=(nullopt)) (got TensorOptions(dtype=long int, device=cpu, layout=Strided, requires_grad=false (default), pinned_memory=false (default), memory_format=(nullopt)))
This patch fixes this error

Okay merging this PR, although the Apex CI build is broken for unrelated reasons, which I'm looking into.


Update free-courses-en.md

What does this PR do?
Add resource(s)
For resources
Added Computer Organization & Architecture courses
Why is this valuable (or not)?
Yes, it is valuable.
How do we know it's really free?
It is available on YouTube.
For book lists, is it a book? For course lists, is it a course? etc.
Checklist:

[x] Read our contributing guidelines.
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction).
[x] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

@sohansai Please merge this pull request.


Events out of order

Events can come through out of order due to use of async in forEach. Iterations of the forEach loop execute concurrently which allows a later call to complete before an earlier call.
https://github.com/pozil/pub-sub-api-node-client/blob/da3be87e9511f95244830a583205cc55e5e7ac66/src/client.js#L327

I've released a new version thanks to @eltoroit PR. This should reduce the frequency of the issue.
Next step to fully remove asynchronicity from the event processing chain will be to remove the EventEmitter from the architecture. This will require a major release. I'll keep this issue open in the meantime.

I'm happy to share that I finally managed to release v5, a major version that addresses this issue by removing asynchronicity from the event processing chain 🎉


Changing Tendril Atomicity with SendTendril produces garbage.

My understanding is that this should not modify the text of the tendril and that this is a reasonable thing to do.
#[cfg(test)]
mod tests {
    use tendril::{fmt::UTF8, Atomic, NonAtomic, Tendril};

    #[test]
    fn it_works() {
        let s: Tendril<UTF8, NonAtomic> = "
Hello!
, World!".into();
        dbg!(&s);
        let s: Tendril<UTF8, Atomic> = s.into_send().into();
        dbg!(&s);
    }
}

But the output is something like:
[src/lib.rs:8] &s = Tendril<UTF8>(owned: "
Hello!
, World!")
[src/lib.rs:10] &s = Tendril<UTF8>(owned: "i>Hello!
, World!\u{0}\u{0}\u{0}\u{0}")

It turns out the headers are different sizes so the transmute is weird.
std::mem::size_of::<Header<Atomic>>() = 16
std::mem::size_of::<Header<NonAtomic>>() = 12

I don't know if the Header should get #[repr(align(16))] or if there's a less platform-specific thing or something; but it seems like it might be a bug idk.  ¯\_(ツ)_/¯

This is definitely a bug. It looks like this functionality is not tested at all, lovely.
My suspicion is on PackedUsize, which has #[repr(C, packed)] but is only used for NonAtomic. It was introduced in https://github.com/servo/tendril/pull/46 … maybe as an attempt to preserve some of the effect of #[repr(packed)] that was previously on Header? @xfix, is that right?
This in turn was added in b39ee1f7e21c51d37ce26dc054d2b4bcd8ab6645 which talks about the C API. Since we removed that, we should probably remove PackedUsize as well.

Removing PackedUsize fixes this immediate issue, but that it happened in the first place only reinforces my feeling that Tendril’s casual and pervasive use of unsafe is dangerous. It might have been sound once, but when all of the library is responsible to maintain invariant that are only known by the original author it’s not surprising that things break is subtle ways when other folks make changer over the years.
I’d recommend not to use Tendril if you can, though presumably you need it in order to use html5ever.
I started a rewrite of Tendril at https://github.com/servo/html5ever/tree/zbuf/ with the idea of having unsafe much more limited, self-contained, and documented. But I never quite finished it or ported html5ever to it. Though maybe making yet another unsafe-using library is not a great plan and html5ever should rather use something better maintained like https://crates.io/crates/bytes instead.

Oops, didn't realize that into_send is a method. I wonder how did the tests didn't break... And shouldn't std::mem::transmute require that the types are the same size?
The intent of PackedUsize was to have an usize whose alignment was 4 to stay compatible with C API. The reason why I did that for non-atomic API only is that packing is just not correct for atomic variables.

But yeah, there is way too much unsafe in this crate. I believe I did write something to that effect in https://lib.rs/crates/tendril/crev: "There is ridiculous amount of unsafe. I have no idea how anything in this crate works." I did try fixing some things, but to be fair, it's still one of crates I'm least certain about in my program dependencies (and I use this due to using ammonia).


how to test own dataset by multi-template?

i want to test my own dataset by multi-template, but i found only single template can be select in './demo/main/video/sot_video.py'.
'python3 ./main/test.py --config 'experiments/siamfcpp/test/vot/siamfcpp_alexnet-multi_temp.yaml' ' can use multi-temp but only for open-dataset.

You can also use the experiments/siamfcpp/test/vot/siamfcpp_alexnet-multi_temp.yaml in the sot_video.py. Just change the config file path to adopt the multi_temp pipeline.

thanks a lot~ another question, if i want to track multi objects, can i put multi object templates into a template pool, then do correlation operation synchronizely in a minibatch.

Hello, could you please explain how to track multi objects in details? Thanks a lot.


Feature | Debug Helper Method

This PR introduces a new and exciting way to debug Saloon requests - the debug() helper method! This method is designed to be used to see exactly what is being sent to the server without any extra fluff.
Let's say you are sending a request like this:
$connector->send($request);

Here's how you use the debugger:
use function Saloon\debug;

debug($connector)->send($request);

Or...
use function Saloon\debug;

$connector->send(debug($request));

Or...
use function Saloon\debug;

debug($request);

$connector->send($request);

This will produce the following output in your terminal or browser:

It is a raw output of the PSR request being sent to the server including the request body!
By default, the debugger will die-and-dump but you can use the second argument to just dump and continue execution:
debug($connector, die: false);

Todo

[ ] Write tests
[ ] Finalise name

Random idea: Call it yeehaw() and print a big YEEHAW before a request is being sent?

Here's how it looks in the browser

Now with better styling

Just replying here instead of twitter.
So what I mean by my suggestion was to update the HasDebugging Trait to have two new functions:

trait HasDebugging
{
    public function dump()
    {
        return debug($this);
    }

    public function dd()
    {
        return debug($this, true);
    }

    ............

So instead of importing it when used, we could do:
$connector->send($request->dump());

Side note in terms of the code itself. I think laravel Octane has a problem with exit, from memory it causes it to crash octane?
Can't remember the specifics but I know I've run into it a few times when debugging things

I actually really love that idea. We already have the HasDebugging trait so I can add to it, maybe I just need some heavy docs to make sure people don't get confused and when they call it, expect something to happen?

I think as long as its documented it'll be fine. People always reach for the docs when trying to debug things like this anyway
This however might make it easy enough to remember for next time instead of having to look it up again (like I always do)

I've added it to the trait, is that what you were thinking? I'm still considering it - I might remove it if I feel it could clash too much with Laravel

What do you guys think about it also including the response too?

Having both would be perfect and would have saved me a lot of time in the past.
Might be counter intuitive having it on the request instead of the connection but thats minor in comparison to the benefit you get here

Okay so I've made some more changes - now we have on the connector/request the following:
$connector->debug($die = false); // Outputs request and response
$connector->debugRequest(); // Outputs request (no die)
$connector->debugRequest($closureHandler); // Old functionality
$connector->debugResponse(); // Outputs response (no die)
$connector->debugResponse($closureHandler); // Old functionality

Not even sure if we need the debug() helper if we have this

That looks neat and very usable. Likely easy to remember too

Thank you for the help with this!

What do you guys think about it also including the response too?

If you debug the connector, include as much as possible for the lifecycle.
If you debug the request, it’s typically because I want to see what is being sent, though I can see a scenario where seeing the response (that would otherwise end up triggering the exception handling), would be helpful

Hey @ClaraLeigh @michaeldyrynda I have updated the description at the top with the final changes. I have also removed the helper.php file as well as the debug() helper method as I don't think it's needed with the methods described above. Let me know your final thoughts on this! I'll need to write some tests but I'm very pleased with this implementation and I think it's going to be instantly useful.

Hi @Sammyjo20!
Thanks for simplifying debugging!
And what about "entering a debug mode" as using cache or not? For me $connector->debug()->send(); is still too cumbersome ;) If we had something like $this->debugMode we would just with one method like enableDebugMode() display all debugging info, without the need to change the core code ($connector->send();) in different places. Maybe $this->debugMode could be string accepting 'both' / 'request' / 'response'?
PS. Will the old way of debugging be still active? To keep it backwards compatible?

Hey @Sammyjo20! I'm loving the newer version of the debugRequest() method. I think it'd be relatively easy for other developers to discover it too with IDE autocomplete. So I'm all for it 😄

Hey @boryn thank you for taking a look at this although I don't think I can get it too much simpler than ->debug() 😅! I think if you wanted to debug without adding the method, you could add it via the constructor? I will consider the property or maybe adding a trait.
public function __construct()
{
    $this->debug();
}

Yes the previous functionality will remain 🙌

These changes saved me a lot of time this week doing two new api integrations. Very helpful and easy to remember, ty

Woohoo! That’s great 😀 thank you for letting me know!


Change clean cmd. remove localnodes.list if option is 'all'.

this cmd has issue. maybe
> gopm clean -a

following dir is deleted after exec gopm clean -a.

.gopm/temp
.gopm/repos

but following file is not deleted.

.gopm/data/localnodes.list

in this case,
go get will be failed, because re- acquisition of dependency is not performed.
please look this.
> gopm get -g -v -u
・・・
[GOPM] 15-11-12 11:24:44 [ INFO] Command executed successfully!

> gopm clean -a

> gopm get -g -v -u
[GOPM] 15-11-12 11:52:15 [ INFO] App Version: <IP_ADDRESS>5 Beta
[GOPM] 15-11-12 11:52:15 [ INFO] Local repository path: /user/home/.gopm/repos
[GOPM] 15-11-12 11:52:15 [ INFO] Indicated GOPATH: /user/home/git/myproject
・・・
[GOPM] 15-11-12 11:52:40 [ INFO] Downloading package: github.com/hoge/test@branch:<UTD>
[GOPM] 15-11-12 11:52:41 [ INFO] Package(github.com/hoge/test) hasn't been changed
[GOPM] 15-11-12 11:52:41 [DEBUG] Linking github.com/hoge/test...
[GOPM] 15-11-12 11:52:41 [ INFO] Got github.com/hoge/test@branch:<UTD>
[GOPM] 15-11-12 11:52:41 [ERROR] %!(EXTRA string=Fail to copy to GOPATH:)
[GOPM] 15-11-12 11:52:41 [FATAL] %!(EXTRA string=	not a directory or does not exist: /user/home/.gopm/repos/github.com/hoge/test)

> cat /user/home/.gopm/data/localnodes.list
[github.com/hoge/test]
value = fe6ea2c8e398672518ef204bf0fbd9af858d0e15

> rm /user/home/.gopm/data/localnodes.list

> gopm get -g -v -u
・・・
[GOPM] 15-11-12 11:24:44 [ INFO] Command executed successfully!

Thanks!

Thanks!!


Add option to set the random seed via seed_override

Add an option to set the random seed.
Background: From BWAPI version 4.0.1 Beta onwards, there is a seed_override option in bwapi.ini that allows users to fix the random seed at the start of a game (including multi-player).  Here's the corresponding comments about this option in the default bwapi.ini (pasted from BWAPI 4.2.0):
; Random seed override. This uses a fixed seed at the start of the game so that if played out the exact same way,
; the same occurrences will happen every time. This value must be a decimal integer.
;
; When this key is commented out, Starcraft will use the system time as a seed. This is the default behaviour.
;
; Note: This option affects both single AND multi-player modes (for game hosts only). This means that hosting a multi-player
; game with this option enabled will distribute this fixed seed to all other players in the game.
;seed_override = 123456789

I'm creating this issue on behalf of @davechurchill who requested on Facebook that I create this issue.  I don't plan to use this option personally, but others might find it useful.

Low priority, but can be included with the next update @richard-kelly

@richard-kelly has this been implemented? just trying to close issues


⚠ Adacta-fintech.com has degraded performance

In 3abafb3, Adacta-fintech.com (https://www.adacta-fintech.com) experienced degraded performance:

HTTP code: 502
Response time: 682 ms

Resolved: Adacta-fintech.com performance has improved in 7de8545.


Could not establish a secure connection to the server

Description
I run "client list" I got
$ knife client list
ERROR: SSL Validation failure connecting to host: chefserver.example.com - SSL_connect SYSCALL returned=5 errno=0 state=SSLv2/v3 read server hello A
ERROR: Could not establish a secure connection to the server.
Use knife ssl check to troubleshoot your SSL configuration.
If your Chef Server uses a self-signed certificate, you can use
knife ssl fetch to make knife trust the server's certificates.
Original Exception: OpenSSL::SSL::SSLError: SSL_connect SYSCALL returned=5 errno=0 state=SSLv2/v3 read server hello A
Briefly describe the issue
But the odd thing is that both "check" and "fetch" return normally
mqian@chefwork:~/chef-repo$ knife ssl check
Connecting to host chefserver:443
Successfully verified certificates from `chefserver'
mqian@chefwork:~/chef-repo$ knife ssl fetch
WARNING: Certificates from chefserver will be fetched and placed in your trusted_cert
directory (/home/mqian/chef-repo/.chef/trusted_certs).
Knife has no means to verify these are the correct certificates. You should
verify the authenticity of these certificates after downloading.
Adding certificate for chefserver in /home/mqian/chef-repo/.chef/trusted_certs/chefserver.crt
Chef Version
Tell us which version of chef-client you are using (see below for Server+ChefDK bugs).
Chef Version: 12.3.0
Platform Version
Tell us which Operating System distribution and version chef-client is running on.
Ubuntu 14.04 desktop
Replication Case
Tell us what steps to take to replicate your problem.  See How to create a Minimal, Complete, and Verifiable example
for information on how to create a good replication case.
Client Output
The relevant output of the chef-client run or a link to a gist of the entire run, if there is one.
The debug output (chef-client -l debug) may be useful, but please link to a gist, or truncate it.
Stacktrace
Please include the stacktrace.out output or link to a gist of it, if there is one.
NOTE: CHEF CLIENT BUGS ONLY
This issue tracker is for the code contained within this repo -- chef-client, base knife functionality (not
plugins), chef-apply, chef-solo, chef-client -z, etc.

Server issues
ChefDK issues
Cookbook Issues (see the https://github.com/chef-cookbooks repos or search Supermarket or GitHub/Google)

are you using the omnibus packages for 12.3.0 or are you using RVM, and which version of the openssl libraries are you linking against?
see http://stackoverflow.com/questions/25814210/opensslsslsslerror-ssl-connect-syscall-returned-5-errno-0-state-sslv3-read

Hey, just to make sure: in the output from knife ssl check you have chefserver, but in knife client list you have chefserver.example.com; is this just you redacting your urls by hand, or are they actually different?

I actually have both chefserver and chefserver.example.com in both server and client's hosts
Regards
Mark

On Apr 20, 2016, at 10:09 AM, Thom May<EMAIL_ADDRESS>wrote:
Hey, just to make sure: in the output from knife ssl check you have chefserver, but in knife client list you have chefserver.example.com; is this just you redacting your urls by hand, or are they actually different?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub

What is in your client.rb for chef_server_url?

Since I was installing workstation so I don't have a client.rb.
I only have ~/chef-repo/.chef/knife.rb:
log_level                :info
log_location             STDOUT
node_name                'admin'
client_key               '~/chef-repo/.chef/admin.pem'
validation_client_name   'hds-validator'
validation_key           '~/chef-repo/.chef/hds.pem'
chef_server_url          'https://chefserver/organizations/hds'
syntax_check_cache_path  '~/chef-repo/.chef/syntax_check_cache'
cookbook_path [ '~/chef-repo/cookbooks' ]
Regards
Mark
Date: Wed, 20 Apr 2016 10:17:45 -0700
From<EMAIL_ADDRESS>To<EMAIL_ADDRESS>CC<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [chef/chef] Could not establish a secure connection to the server (#4836)
What is in your client.rb for chef_server_url?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub

Yeah, I meant knife.rb
Have you tried changing your chef_server_url to https://chefserver.example.org/organizations/hds?

Yes, I did but the same result. Does chef use its own proxy setting for reconfigure?
I could ping, telnet, and wget with no problem...
Regards
Mark
Date: Wed, 20 Apr 2016 10:24:14 -0700
From<EMAIL_ADDRESS>To<EMAIL_ADDRESS>CC<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [chef/chef] Could not establish a secure connection to the server (#4836)
Yeah, I meant knife.rb
Have you tried changing your chef_server_url to https://chefserver.example.org/organizations/hds?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub

If you (re-)install the omnibus package for 12.3.0 and attempt to replicate does it still fail?
% curl https://omnitruck.chef.io/stable/install.sh | sudo bash -s -- -v 12.3.0
% /opt/chef/bin/knife client list

can you also run
/opt/chef/embedded/bin/openssl s_client -connect chefserver:443 -showcerts

/opt/chef/embedded/bin/openssl s_client -connect chefserver.example.org:443 -showcerts

and send the output to<EMAIL_ADDRESS>(or suitably expurgate them and post them here)

Hi,
I'm going to close this issue for lack of response. Should you feel this isn't correct, please reopen the ticket with the information we requested.
Thanks for using Chef!


Add support for space cloud prepared queries

Because of adding support for transforming the request body in remote services, we can now allow the user to trigger a customised graphql query back to space cloud. (AKA Space Cloud Prepared Queries)
Space Cloud prepared queries are nothing but special type of endpoints in a remote service which queries the Space Cloud's auto-generated GraphQL APIs rather than the remote service's endpoints. The user specifies the GraphQL query and variable templates rather than specifying method, path, etc as compared to a normal endpoint.

Done. Coming in v0.18.0


Build error for esp32s3 (IDFGH-5129)

Environment

Development Kit:      [none]
IDF version (run git describe --tags to find it):
// v4.3-beta2-2-g9a2d251912
Build System:         [idf.py]
Compiler version (run xtensa-esp32-elf-gcc --version to find it):
// xtensa-esp32s3-elf-gcc.exe (crosstool-NG esp-2020r3) 8.4.0
Operating System:     [Windows]
(Windows only) environment type: PowerShell].
Using an IDE?: [No]

Problem Description
Config:
CONFIG_PM_ENABLE=y
CONFIG_IDF_TARGET="esp32s3"
CONFIG_IDF_TARGET_ESP32S3=y
[688/1313] Building C object esp-idf/bt/CMakeFiles/__idf_bt.dir/controller/esp32s3/bt.c.obj
FAILED: esp-idf/bt/CMakeFiles/__idf_bt.dir/controller/esp32s3/bt.c.obj
C:/DevOps/agt10/_work/1/s/SW/WifiBle/repo4/esp-idf/components/bt/controller/esp32s3/bt.c: In function 'btdm_sleep_enter_phase1_wrapper':
C:/DevOps/agt10/_work/1/s/SW/WifiBle/repo4/esp-idf/components/bt/controller/esp32s3/bt.c:774:28: error: implicit declaration of function 'btdm_lpcycles_2_us'; did you mean 'btdm_lpcycles_2_hus'? [-Werror=implicit-function-declaration]
uint32_t us_to_sleep = btdm_lpcycles_2_us(lpcycles);
^~~~~~~~~~~~~~~~~~
btdm_lpcycles_2_hus
cc1.exe: some warnings being treated as errors

Hi @twomas,
Thanks for reporting the issue. May I know the hardware version you are using now, S3-beta2 or S3-beta3?
You can refer to the Samples Notes:

ESP32-S3 Beta 2 (marked ‘Marlin9_1B'). Preview support is available in ESP-IDF branch release/v4.3 and the v4.3 release ONLY.
ESP32-S3 Beta 3 (marked 'Marlin9'). Preview support is available in the current ESP-IDF master branch but will be removed from ESP-IDF when the final chip is available.
Thanks.

Hi @TianaESP
Now I'm using esp32 hw for my project.
So I only did a test build for esp32-s3 with my existing project
https://www.espressif.com/en/products/socs/esp32-s3
Do you know if it is possible to get a devkit with ESP32-S3 mounted?

Hi @twomas
Please contact our sales team at Contact Us.
Or by emailing<EMAIL_ADDRESS>Thanks.

Thanks for reporting, feel free to reopen.


Enforce noImplicitThis and noImplicitReturns on src

@EricJizbaMSFT @PrashanthCorp Eric, how confident are you in letting this get checked in before the release?  I'd prefer to delay.

We have a separate release branch: https://github.com/Microsoft/vscode-cosmosdb/tree/rel/0.5.0
None of the lint stuff will be included

Ah.  Okay, then.  Is that just this extension that has a separate release branch?
From: Eric Jizba<EMAIL_ADDRESS>Sent: 28 February, 2018 2:13 PM
To: Microsoft/vscode-cosmosdb<EMAIL_ADDRESS>Cc: Stephen Weatherford<EMAIL_ADDRESS>Review requested<EMAIL_ADDRESS>Subject: Re: [Microsoft/vscode-cosmosdb] Enforce noImplicitThis and noImplicitReturns on src (#374)
We have a separate release branch: https://github.com/Microsoft/vscode-cosmosdb/tree/rel/0.5.0https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fvscode-cosmosdb%2Ftree%2Frel%2F0.5.0&data=04|01|Stephen.Weatherford%40microsoft.com|97522f1cdd564d4360f908d57ef867ab|72f988bf86f141af91ab2d7cd011db47|1|0|636554527765478351|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D|-1&sdata=gCotmrONfGDRFedvjd6skDvmbCtnqBgQnOyQPaCVVG4%3D&reserved=0
None of the lint stuff will be included
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fvscode-cosmosdb%2Fpull%2F374%23issuecomment-369401438&data=04|01|Stephen.Weatherford%40microsoft.com|97522f1cdd564d4360f908d57ef867ab|72f988bf86f141af91ab2d7cd011db47|1|0|636554527765478351|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D|-1&sdata=HJobrBhwMBXEdOw5MBi79HSfOO2Cij7xvtaXsD8ABWY%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAGl9SlboD6G0N31TLAAiDZuMW98TLUAWks5tZc9fgaJpZM4SV7F2&data=04|01|Stephen.Weatherford%40microsoft.com|97522f1cdd564d4360f908d57ef867ab|72f988bf86f141af91ab2d7cd011db47|1|0|636554527765478351|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D|-1&sdata=oUFmPuLwyRMWbVLg%2Bd6hm%2BFJ7WCFwNGooIT12WJ9g7o%3D&reserved=0.

Yeah - we did it specifically because of the lint work


bug in forgetting metric

def forgetting(all_preds, all_targets, all_tasks):
    """Measures the average forgetting.

    Reference:
    * Riemannian Walk for Incremental Learning: Understanding Forgetting and Intransigence
      Chaudhry et al. ECCV 2018

    See eq. 3.
    """
    k = len(all_preds)  # Number of seen tasks so far
    # TODO if we take in account zeroshot, we should take the max of all_tasks?
    if k <= 1:
        return 0.

    f = 0.
    for j in range(k - 2):
        # Accuracy on task j after learning current task k
        a_kj = _get_R_ij(k - 1, j, all_preds, all_targets, all_tasks)
        # Best previous accuracy on task j
        max_a_lj = max(_get_R_ij(l, j, all_preds, all_targets, all_tasks) for l in range(k - 2) if l >= j)
        f += max_a_lj - a_kj  # We want this results to be as low as possible

    metric = f / (k - 1)
    assert -1.0 <= metric <= 1.0, metric
    return metric

for j in range(k-2) should be for j in range(k-1), otherwise after the k_th task only the first k-2 tasks are considered and the denominator when averaging over past tasks is  is also mistaken.

Hi @Jillian-h ,
Thanks for your issue.
The index issue is already fixed in the master branch (and also on the pip version, I believe); where did you get this version of the code?
Have a nice day.
Timothée


Image view method should be able to display regions

This will mean giving Images some awareness of regions, my current thinking is that they can be either passed in on declaration or set in a property.
Either of those ways will trigger a function to load them in and convert them to pixel coordinates

To be clear, I just want a filepath to be passed in for the region file


zebra-state: replace sled with rocksdb

Motivation

Solution

The code in this pull request has:

[ ] Documentation Comments
[ ] Unit Tests and Property Tests

Review

Related Issues

Follow Up Work

😬  on debian-buster

grimacing on debian-buster

oh joy, more c++ dependency management


Rename to d2l loading spinner

@mdedys @dlockhart @GianD2L

@dlockhart Looks good?
@mdedys Could you merge it if it is good?

Yes I can. I will also up the version to 3.0.0 and tag it.

Question: should the bower name be d2l-loading-spinner-ui or d2l-loading-spinner?

Following the other repo names it should be d2l-loading-spinner I believe

Yep, agreed.

Cool this LGTM!


!write command, builds command in an editor

Leverages the easily installable vipe executable:

opens default terminal editor
passes any arguments to !write as the initial text in the editor
collects final text from the editor when closed
outputs text to screen for viewing
sends text as the entered command.

May be possible to use other pipe editors, did not investigate since vipe is so widely available.
On a personal note, this feature is a game changer for me. To be able to 'prepare' my command using my native editor, leverage keyboard shortcuts, see syntax highlighting, edit mistakes, etc., makes this CLI tool far more useful and fun!

I modified the command to !editor in main for clarity


Domain Name is not used when creating an environment

When I use the Create Environment task and pass a DomainName it is not used when excecutig. All other fields are used like DisplayName.  Can you please fix?

@oarbaji
Can you provide the article where you saw this documented?


HomeAssistant 'version' warning

Hey, I am getting a warning in my logs in home assistant.
[homeassistant.loader] No 'version' key in the manifest file for custom integration 'sonoff'. This will not be allowed in a future version of Home Assistant. Please report this to the maintainer of 'sonoff'

refer issue #374


Update command-line.yml

Clearer wording of the answers about commands argument omitting.

Thanks for your contribution @a-menshchikov


chore: drop support for node 4

The build is currently failing anyway, and node 4 has been unsupported for ages. This would save contributors time spend on trying to figure out why their PR is failing.

Sweet, cheers for the PR. I'm completely in favour of this personally. I don't see it being controversial, so happy to merge it soon if I don't hear back from @jamiebuilds .
Would you mind updating the error message in bin.js too though?
if (majorVer < 4) {
  throw new Error(
    'Node version ' +
      ver +
      ' is not supported in Bolt, please use Node.js 4.0 or higher.'
  );
}

Thanks heaps for the contribution @ForbesLindesay , the change has been done in #246 now, which should be released today (sorry, didn't think to cherry pick your commit 🤦♂ ).
Will update with which version this releases in.

Released in 0.24.0


Add descriptions to metrics to match otelgrpc

When otelconnect and otelgrpc are used in the same project, the Prometheus exporter fails because the descriptions of the metrics produced by the two libraries differ. See #154 for details.
This PR copies over the metrics descriptions used in the otelgrpc instrumentation to metrics produced by otelconnect.
Fixes #154

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

This approach seems extremely brittle, but I'm merging anyway since I don't have any better ideas for other solutions/work-arounds right now.
Thanks for the contribution, @charithe!


java.lang.OutOfMemoryError, JdbcDatabaseSnapshot:1557, table argument is always NULL

Search first

[x] I searched and no similar issues were found

Description
JdbcDatabaseSnapshot at line 1557, table argument is always null
 Caused by:
    **java.lang.OutOfMemoryError: Java heap space**
      at java.base/java.lang.StringLatin1.toUpperCase(StringLatin1.java:539)
      at java.base/java.lang.String.toUpperCase(String.java:3469)
      at liquibase.executor.jvm.ColumnMapRowMapper.getColumnKey(ColumnMapRowMapper.java:67)
      at liquibase.executor.jvm.ColumnMapRowMapper.mapRow(ColumnMapRowMapper.java:39)
      at liquibase.executor.jvm.RowMapperResultSetExtractor.extractData(RowMapperResultSetExtractor.java:72)
      at liquibase.snapshot.ResultSetCache$ResultSetExtractor.extract(ResultSetCache.java:318)
      at liquibase.snapshot.ResultSetCache$ResultSetExtractor.extract(ResultSetCache.java:287)
      at liquibase.snapshot.JdbcDatabaseSnapshot$CachingDatabaseMetaData$4.getPkInfo(JdbcDatabaseSnapshot.java:1553)
      at liquibase.snapshot.JdbcDatabaseSnapshot$CachingDatabaseMetaData$4.fastFetchQuery(JdbcDatabaseSnapshot.java:1437)
      at liquibase.snapshot.ResultSetCache$SingleResultSetExtractor.fastFetch(ResultSetCache.java:342)
      at liquibase.snapshot.ResultSetCache.get(ResultSetCache.java:69)
      at liquibase.snapshot.JdbcDatabaseSnapshot$CachingDatabaseMetaData.getPrimaryKeys(JdbcDatabaseSnapshot.java:1406)
      at liquibase.snapshot.jvm.PrimaryKeySnapshotGenerator.snapshotObject(PrimaryKeySnapshotGenerator.java:39)
      at liquibase.snapshot.jvm.JdbcSnapshotGenerator.snapshot(JdbcSnapshotGenerator.java:65)
      at liquibase.snapshot.SnapshotGeneratorChain.snapshot(SnapshotGeneratorChain.java:49)
      at liquibase.snapshot.DatabaseSnapshot.include(DatabaseSnapshot.java:313)
      at liquibase.snapshot.DatabaseSnapshot.init(DatabaseSnapshot.java:106)
      at liquibase.snapshot.DatabaseSnapshot.<init>(DatabaseSnapshot.java:59)
      at liquibase.snapshot.JdbcDatabaseSnapshot.<init>(JdbcDatabaseSnapshot.java:34)
      at liquibase.snapshot.SnapshotGeneratorFactory.createSnapshot(SnapshotGeneratorFactory.java:214)
      at liquibase.snapshot.SnapshotGeneratorFactory.createSnapshot(SnapshotGeneratorFactory.java:243)
      at liquibase.snapshot.SnapshotGeneratorFactory.has(SnapshotGeneratorFactory.java:132)
      at liquibase.precondition.core.PrimaryKeyExistsPrecondition.check(PrimaryKeyExistsPrecondition.java:83)
      at liquibase.precondition.core.AndPrecondition.check(AndPrecondition.java:39)
      at liquibase.precondition.core.PreconditionContainer.check(PreconditionContainer.java:213)
      at liquibase.changelog.ChangeSet.execute(ChangeSet.java:644)
      at liquibase.changelog.visitor.UpdateVisitor.executeAcceptedChange(UpdateVisitor.java:120)
      at liquibase.changelog.visitor.UpdateVisitor.visit(UpdateVisitor.java:70)
      at liquibase.changelog.ChangeLogIterator$2.lambda$run$0(ChangeLogIterator.java:110)
      at liquibase.changelog.ChangeLogIterator$2$$Lambda$934/0x000000080138d788.run(Unknown Source)
      at liquibase.Scope.lambda$child$0(Scope.java:197)
      at liquibase.Scope$$Lambda$894/0x00000008012d13c0.run(Unknown Source)

Steps To Reproduce

Create DB
Create 1000+ tables
Run migrations for all tables

Expected/Desired Behavior
It should not throw OOM error
Analyzed dump shows
Root object j.u.ArrayList@7e4163fa0
->j.u.ArrayList 493,990Kb (94.9%), self 2,822Kb (0.5%), 1 object(s)
  {list elements} 491,168Kb (94.3%), 542,880 reference(s)  **LEAK CANDIDATE**
  ->liquibase.snapshot.CachedRow 491,168Kb (94.3%), self 8,482Kb (1.6%), 542,880 object(s)
    ->.row 482,685Kb (92.7%), 542,880 reference(s)
      j.u.LinkedHashMap 482,685Kb (92.7%), self 182,373Kb (35.0%), 542,880 object(s)
      ->{keys} 169,650Kb (32.6%), 3,257,280 reference(s)
        String 169,650Kb (32.6%), self 169,650Kb (32.6%), 3,257,280 object(s)
      ->{values} 130,662Kb (25.1%), 2,171,520 reference(s)
        String 130,662Kb (25.1%), self 130,662Kb (25.1%), 2,171,520 object(s)

Liquibase Version
micronaut-liquibase:5.7.2
Database Vendor & Version
PostgreSQL 12
Liquibase Integration
micronaut-liquibase
Liquibase Extensions
No response
OS and/or Infrastructure Type/Provider
All
Additional Context
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR (Thank you!)

Hello @vchepeli, I'll need some more information in order to test this effectively.
Are you creating the 1000+ tables through Liquibase? Is that part giving any errors?
Regarding the migrations: what kind of changes are you making? And are you running them for all tables?
Thank you in advance
Tatiana

Hi @tati-qalified, below are replies for your questions
Are you creating the 1000+ tables through Liquibase?
Yes, tables are created with Liquibase migrations
Is that part giving any errors?
Yes, migrations started but its frozen after and couple minutes it throws OOM
Regarding the migrations: what kind of changes are you making?
Creating tables, add/remove columns, adding checks, indexes
And are you running them for all tables?
Yes, for all tables it runs
Thanks, Vitalij

I couldn't reproduce the out of memory error, but I analysed the memory usage when running thousands of changesets, and it looks like the garbage collector isn't being fast enough. In my program, memory usage reached 1200+Mb before the garbage collector kicked in.
Thank you for letting us know of this issue, I'll forward this to the development team so they can evaluate how to move forward.

@tati-qalified you described actually what happened, I have 500MB for tests and I truncated databasechange table, so all migrations were gone, and after run all migrations again to simulate this issue, and it start to use log of MEM >500MB, rafter limit passed OOM, if you have some drive I can try to push heap dump

@tati-qalified here is link, try to download it and let me know

Hi @vchepeli,
If it's not too time-consuming, could you please try again with our latest version to see if you are experiencing the same performance issue? During the last couple of releases there were some PRs merged that according to some other users performance has been improved for them.
Thanks,
Daniel.


Mustache.to_html() striping blank lines

If JSON data contains a string with blank lines ("str\n\n\nstr"), when this string is applied to the template, the blank lines are removed, this may be an issue if, for example, the string is inside <pre>.
One possible solution is to remove blank line test from send function

Would you please test this out against master? Version 0.5 is much more strict about whitespace than previous versions were, and your issue may be fixed.

This is fixed in this commit.


chore: remove v1.22.0

Summary
This PR removes v1.22.0 of K8s from cdk8s-plus.

💔 All backports failed

Status
Branch
Result

❌
k8s-23/main
Backport failed because of merge conflicts

❌
k8s-24/main
Backport failed because of merge conflicts

Manual backport
To create the backport manually run:
backport --pr 1294

Questions ?
Please refer to the Backport tool documentation

💚 All backports created successfully

Status
Branch
Result

✅
k8s-24/main

Questions ?
Please refer to the Backport tool documentation

💚 All backports created successfully

Status
Branch
Result

✅
k8s-23/main

Questions ?
Please refer to the Backport tool documentation


Ignore certain parameters like timing_stim during live editting

Let's leave this open until we get it working through the plugin files.

@GavinQ1 @kristiyip This is another thing that we need to work on that involves changes to both the GUI and to jsPsych itself. We should flag certain parameters as "ignored" during live editing. We can add a live_edit_value parameter to any params that should be ignored (usually timing parameters that would cause the experiment to hide). Whatever value is passed in there is used during live edit mode. Let's try and get this working as a proof of concept with the image-keyboard-response plugin, where stim_duration and trial_duration should both have live_edit_value: -1.


Cannot read property 'readerQR' of undefined

Please add this lib react-native-lewin-qrcode
with xcode add see

Closing due to inactivity.


executor services are shut down after submitting tasks

This change seems to fix https://github.com/mozafari/verdictdb/issues/195

Codecov Report

Merging #197 into master will increase coverage by 0.28%.
The diff coverage is 96.12%.

@@            Coverage Diff             @@
##           master     #197      +/-   ##
==========================================
+ Coverage   73.08%   73.35%   +0.28%
==========================================
  Files         141      141
  Lines        8333     8410      +77
  Branches     1325     1345      +20
==========================================
+ Hits         6089     6168      +79
+ Misses       1886     1885       -1
+ Partials      358      357       -1

Impacted Files
Coverage Δ

.../VerdictResultStreamFromExecutionResultReader.java
61.54% <ø> (ø)
:arrow_up:

...c/main/java/org/verdictdb/sqlsyntax/SqlSyntax.java
85.72% <ø> (ø)
:arrow_up:

...ctdb/core/resulthandler/ExecutionResultReader.java
57.15% <ø> (ø)
:arrow_up:

...g/verdictdb/core/execplan/ExecutionTokenQueue.java
54.55% <ø> (ø)
:arrow_up:

.../verdictdb/coordinator/SelectQueryCoordinator.java
93.34% <ø> (-0.08%)
:arrow_down:

...ictdb/core/resulthandler/ExecutionTokenReader.java
63.64% <ø> (ø)
:arrow_up:

...ain/java/org/verdictdb/sqlsyntax/SqliteSyntax.java
13.05% <ø> (ø)
:arrow_up:

...rc/main/java/org/verdictdb/sqlsyntax/H2Syntax.java
59.1% <ø> (ø)
:arrow_up:

.../verdictdb/core/execplan/ExecutableNodeRunner.java
83.66% <0%> (-1.64%)
:arrow_down:

...java/org/verdictdb/sqlwriter/CreateTableToSql.java
89.87% <100%> (+0.33%)
:arrow_up:

... and 11 more

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 39f73b2...3996701. Read the comment docs.


Improve failure message for AJ matcher

Printing unmatched jobs should help in finding failure reason.
If you have some suggestions how to improve this message, let me know.

Thanks :)


Re-enable NUMA memory binding on newer kernels

lib/ljsyscall/syscall/linux/syscalls.lua: More robustly create
multi-word bitmasks.

src/lib/numa.lua: Remove facility for blacklisting kernel versions.
Re-enable bind_to_numa_node generally.

WDYT @takikawa, @eugeneia, and @dpino ?

I hate that this is some complicated, but this PR seems to make it simpler overall. :+1: Since this touches ljsyscall, maybe @justincormack has more insight.

I also wonder about our relation with upstream ljsyscall, we have https://github.com/snabbco/snabb/pull/1122 lying around. Would be nice to sync with upstream (both directions.)

Regarding upstream, there's https://github.com/justincormack/ljsyscall/pull/193 sitting around because I am a bad person and haven't done the last-mile there; so on the up side of things there won't be conflicts with upstream :P

One problem about upstream is that I was reluctant to switch to LuaJit 2.1 branch as there has never actually been a proper release, and some of the PRs were not compatible due to syntactic differences. There are a couple of options, 1. fix the differences with some (probably a bit ugly) workarounds 2. drop support for the 2.0 branch 3. switch to raptorjit as the upstream...

I will try to get in the workarounds upstream.


Update VPC Creation TF

Environment

UDF Blueprint

Describe the bug
There are several interpolation expressions still in the TF to create a VPC. These have been deprecated and should be updated.
Warning: Interpolation-only expressions are deprecated

  on vpc.tf line 19, in resource "aws_subnet" "f5-volterra-management-1":
  19:   vpc_id                  = "${aws_vpc.f5-volterra-vpc.id}"

Terraform 0.11 and earlier required all non-constant expressions to be
provided via interpolation syntax, but this pattern is now deprecated. To
silence this warning, remove the "${ sequence from the start and the }"
sequence from the end of this expression, leaving just the inner expression.

Template interpolation syntax is still used to construct strings from
expressions when the template includes multiple interpolation sequences or a
mixture of literal strings and interpolations. This deprecation applies only
to templates that consist entirely of a single interpolation sequence.

(and 10 more similar warnings elsewhere)

updated via terraform fmt in 4f0fd8c


Please support .tool-versions file

Is your feature request related to a problem? Please describe.
I'm working in an org which has recently adopted opentofu and tenv. I notice that tofuutils org has an asdf plugin for tenv, and you compare tenv with asdf. I have difficulty understanding why tenv doesn't support .tool-versions files.
I use asdf to install tools like kubectl and helm, and prior to my org adopting tenv, opentofu and atmos, I used it for terraform and terragrunt. asdf uses an in-repo config file named .tool-versions which lists the tools and their versions for that repo.
tenv uses a separate file for each tool, which is inconvenient and feels wholly unnecessary to me.
Additionally, we have team members who still use asdf for opentofu and atmos installation. Specifying the version for asdf users means we have to declare it twice, and the two version files can get out of sync, causing headaches.
Describe the solution you'd like
I'd like tenv to look for .tool-versions in the repo and read it if found. I'd like .tool-versions to take priority over any .<toolname>-version file but not over environment variables.
Supporting this would allow us to consolidate. We currently have a .tool-versions file for our asdf managed tools, and atmos and opentofu version files for the tenv managed tools. tenv could simply read the same file and ignore the tools it doesn't support.
It will also allow those who haven't switched (from an asdf installed atmos and opentofu to a tenv installed atmos and opentofu) to still rely on the same tool versions without needing to double declare by having them in a .atmos-version and .opentofu-version file alongside also having them in .tool-versions as we need to do today to support anyone who hasn't switched.
Describe alternatives you've considered
I thought of making a symbolic link for .tool-versions to the atmos version file but I need to include kubectl, helm, and opentofu, so a symbolic link is not going to accommodate this.
Additional context
Add any other context or screenshots about the feature request here.

Hi @tspearconquest! Thank you for reporting this issue. I agree that it makes sense to support .tools-version. We'll try to implement this support soon.

Thanks! Please be aware it is .tool-versions rather than .tools-version

done by @kvendingoldo in #303 , new release coming soon

Unfortunately, it doesn't appear to be working. I removed .opentofu-version, then ran asdf local opentofu 1.8.6 to create .tool-versions, then ran tenv tofu install to try to install opentofu 1.8.6 via tenv.
$ pwd
/tmp
$ ls -la 2>/dev/null |grep version
-rw-r--r-- 1  502 dialout     5 Dec 23 18:46 .opentofu-version
-rw-r--r-- 1  502 dialout    29 Dec 23 16:54 .tool-versions
$ cat .opentofu-version
1.8.6
$ cat .tool-versions
opentofu 1.8.6
$ tenv tofu install
Resolved version from /tmp/.opentofu-version : 1.8.6
Installing OpenTofu 1.8.6
Fetching release information from https://api.github.com/repos/opentofu/opentofu/releases/tags/v1.8.6
^c
$ rm -fv .opentofu-version
removed '.opentofu-version'
$ tenv tofu install
No version files found for OpenTofu, fallback to latest strategy
Fetching all releases information from https://api.github.com/repos/opentofu/opentofu/releases
^C

Please help check what I've done wrong.

Further testing reveals it does seem to be working fine for atmos, just not for opentofu.
My CI gives the following:
$ tenv tofu install
No version files found for OpenTofu, fallback to latest strategy
Fetching all releases information from https://api.github.com/repos/opentofu/opentofu/releases
Found compatible version remotely : 1.8.7
Installing OpenTofu 1.8.7
Fetching release information from https://api.github.com/repos/opentofu/opentofu/releases/tags/v1.8.7
Downloading https://github.com/opentofu/opentofu/releases/download/v1.8.7/tofu_1.8.7_linux_amd64.zip
Downloading https://github.com/opentofu/opentofu/releases/download/v1.8.7/tofu_1.8.7_SHA256SUMS
Downloading https://github.com/opentofu/opentofu/releases/download/v1.8.7/tofu_1.8.7_SHA256SUMS.sig
Downloading https://github.com/opentofu/opentofu/releases/download/v1.8.7/tofu_1.8.7_SHA256SUMS.pem
cosign executable not found, fallback to pgp check
Downloading https://github.com/opentofu/opentofu/releases/download/v1.8.7/tofu_1.8.7_SHA256SUMS.gpgsig
Downloading https://get.opentofu.org/opentofu.asc
Installation of OpenTofu 1.8.7 successful
$ tenv atmos install
Resolved version from /opt/jenkins_agent/workspace/re_switch_to_tool_versions_files/.tool-versions : 1.115.0
Installing Atmos 1.115.0
Fetching release information from https://api.github.com/repos/cloudposse/atmos/releases/tags/v1.115.0
Downloading https://github.com/cloudposse/atmos/releases/download/v1.115.0/atmos_1.115.0_linux_amd64
Downloading https://github.com/cloudposse/atmos/releases/download/v1.115.0/atmos_1.115.0_SHA256SUMS
Installation of Atmos 1.115.0 successful

Further down when it tries to run tofu:
$ tofu fmt -check -recursive
Failure during tofu call : fork/exec /usr/bin/tenv: inappropriate ioctl for device

#307 should fix this. Apologies as I'm not very good with Go.


Missing Materials, Spamming lua errors in console

http://cloud-4.steamusercontent.com/ugc/707401792819944152/F10CA9B59966529BC881829D2353932BB1406C82/
http://cloud-4.steamusercontent.com/ugc/707401792819942875/CAF5236F44470053131DF9B2E47213902085B971/
http://cloud-4.steamusercontent.com/ugc/707401792819939036/087D2F1A34A4A53A711A2DE47D68318F6E5E3AB1/
[ERROR] stack overflow

gmatch - [C]:-1
GetTextSize - gamemodes/clockwork/framework/sh_kernel.lua:1485
3. WrappedText - gamemodes/clockwork/framework/libraries/cl_chatbox.lua:622
4. Add - gamemodes/clockwork/framework/libraries/cl_chatbox.lua:924
5. ClockworkAddText - gamemodes/clockwork/framework/libraries/client/cl_chatbox.lua:61
6. PrintColoredText - gamemodes/clockwork/framework/sh_kernel.lua:2266
7. Add - gamemodes/clockwork/framework/libraries/cl_chatbox.lua:956
8. ClockworkAddText - gamemodes/clockwork/framework/libraries/client/cl_chatbox.lua:61
9. PrintColoredText - gamemodes/clockwork/framework/sh_kernel.lua:2266
10. Add - gamemodes/clockwork/framework/libraries/cl_chatbox.lua:956
11. ClockworkAddText - gamemodes/clockwork/framework/libraries/client/cl_chatbox.lua:61
12. PrintColoredText - gamemodes/clockwork/framework/sh_kernel.lua:2266
13. Add - gamemodes/clockwork/framework/libraries/cl_chatbox.lua:956
14. ClockworkAddText - gamemodes/clockwork/framework/libraries/client/cl_chatbox.lua:61
15. PrintColoredText - gamemodes/clockwork/framework/sh_kernel.lua:2266
16. Add - gamemodes/clockwork/framework/libraries/cl_chatbox.lua:956

Due to the garrysmod update, many functions have been removed from garrysmod which clockwork relied on. Until then, we must wait for the developers to fix it, I have looked into it myself and I couldn't quite make out what was wrong, however I am sure they can.
Forum Thread: http://forums.cloudsixteen.com/threads/patch-clockwork-0-93.11874/

But those errors don't even relate to anything that got removed?

i managed to fix it by just re-installing clockwork. retarded.

@Chessnut Since the new garrys update, the content for the gamemode hasn't been working as it should.


v0.0.6 bundle doesn't include changes from PR #1

Just installed tailwind-merge-rtl-plugin and the content of the dist directory still looks the same as in v0.0.5

Missed this issue, yes I released 0.0.7 that should be fine.

Nice, thanks! 😊


How to run visualize code in server?

Hi,
When I run the scripts python visualizer.py configs/ScanNet/scene0000.yaml --output output/vis/scannet/scans/scene0000_00, I met the error below.
I ran the script in a server, there is not a monitor.

Hi, please check #61.


we need timestamp on deposits

we need timestamp on deposits table

this was done on the sql server directly


TIME object cycle Period

I want to use TIME object as producer but I don't see any way to set cycle period.
CO_CANopenInit call CO_TIME_init and set TIMECyclePeriod to 0. Currently, I need to change the call of CO_TIME_init to set the cycle period I want. Is there a way to do this that I haven't seen?

I am in the same situation as you. The library does not change TIME->periodTime nor TIME->periodTimeoutTime from other place than CO_TIME_init.
My guess is that this setting is application specific, and should be set up by the application outside the library, by accessing directly the CO object. I.e. setting a timeout of 1sec:
CO->TIME->periodTime = 1000
CO->TIME->periodTimeoutTime = 1000 * 1.5
And the library will begin producing TIME objects

No I implemented a basic Time producer and tested this as I am not using it on my applications. Feel free to propose pull request if you have some improvments.

Sorry for the delay I missed your issue notification ...

No I implemented a basic Time producer and tested this as I am not using it on my applications.

Sorry, I don't understand your sentence.
Do you tested it and it did not work?
Or do you tested it and it did work?
Just enabling the OD object 0x1012 to be a producer does not generate any TIME message. This was the original issue.
The solution I proposed is to have the application initialise the CO->TIME variables to a timeout suitable for the application purposes, which is why I think it may be left untouched, so the applicaiton can set it up.
This can be done after CO_CANopenInit.
With this, it correctly generates TIME messages.
I don't know if this behaviour was intended or was a bug. My feeling is that it was intended, so no pull request would be needed.

I tested TIME producer and consumer on v1.3 branch (when I added this functionnality) and it was working pretty well. But as I don't use TIME producer on my applications you may have some improvments to add if you need to change period outisde initialisations...
Please note that a lot of changes to CANopenNode since that contribution could have been affected TIME, I did not tested it again with master branch but I am currently starting a new project with this branch and will re test this soon.

Ok.
I was talking about the master branch. Don't know about v1.3, since I have not used it.
In the master branch, the app has to do the changes I stated. Otherwise it will not generate TIME messages.
I thought it was intended, but from your comment, it seems to be actually a bug.

I have just pushed CO_time.h/c updated to newOD branch. Time producer in Linux, if enabled, sends correct time-stamp message (from system RTC). Internal variables ms and days are precisely updated on each CANopen_process() pass. Consumer also updates them on reception of the time-stamp message.
Enabling/disabling producer/consumer works dynamically.
Take a look in the commit https://github.com/CANopenNode/CANopenNode/commit/464a856a3f13417769f0f36eba3ce2901df381f1

I have just pushed CO_time.h/c updated to newOD branch. Time producer in Linux, if enabled, sends correct time-stamp message (from system RTC). Internal variables ms and days are precisely updated on each CANopen_process() pass. Consumer also updates them on reception of the time-stamp message.
Enabling/disabling producer/consumer works dynamically.
Take a look in the commit https://github.com/CANopenNode/CANopenNode/commit/464a856a3f13417769f0f36eba3ce2901df381f1


perf: tweak peak related calculation

This PR tweaked the peak related calculations by using an unified algorithm, optimized performance and simplified the code.
Benchmark on my pc shows around 5~6% improvement.
MMR insertion/times/10000
                        time:   [8.7440 ms 8.7798 ms 8.8227 ms]
                        change: [-5.5398% -3.7561% -2.1591%] (p = 0.00 < 0.05)

MMR insertion/times/100000
                        time:   [95.951 ms 96.536 ms 97.145 ms]
                        change: [-6.6566% -5.5857% -4.5850%] (p = 0.00 < 0.05)

MMR insertion/times/1000000
                        time:   [1.0498 s 1.0569 s 1.0645 s]
                        change: [-6.7619% -5.8593% -4.9284%] (p = 0.00 < 0.05)

MMR gen proof           time:   [6.6808 µs 6.7964 µs 6.9333 µs]
                        change: [-7.8288% -4.9973% -1.9181%] (p = 0.00 < 0.05)

MMR verify              time:   [6.3648 µs 6.4368 µs 6.5346 µs]
                        change: [-9.4028% -6.0025% -2.4343%] (p = 0.00 < 0.05)

please note that some unit test of get_peaks fn have been modified since the logic of invalid mmr size calculation is changed, however, it does not affect the valid mmr calculation.

In my own humble opinion, it's hard to say whether performance improved or not.
Benchmark on my laptop -- an old mobile workstation.


Enable ability to use preexisting S3 bucket

Provide the ability within the Assisted Log Enabler for AWS to use a preexisting S3 bucket for storing the logs.

Hello have you made progress on this issue? Otherwise I would pick it up

Hello have you made progress on this issue? Otherwise I would pick it up

I have not! However, feel free to pick it up as you stated. Pinging @cydneystude as well.

Feature added in latest release.


Revert "fix(UI): put legacy label on the old js curriculum title (#52980)"

This reverts commit 48d4d2f27ae0ce304f3ee30da4ad35398f544aa0.
It seems that this pr was not finished, there were many bugs I came across after the merge. The new JavaScript Certification is not accessible at the moment and the Legacy cert is shown twice on the settings page.

Everything is too scattered around the code base.


fix(core/rhino/gh/revit/navis): Adds enhancedLogContext config option and disables it on mac

Fixes logger initialisation issues in:

Rhino for mac
Grasshopper
Revit
Navisworks

Merging in. Discussed changes with @gjedlicska, and verified connectors locally.


Updated known bugs

Extended known bug  for link elements.

A version number would be nice, but for bugs I don't mind not knowing exactly.


Issue330 update identifiers

I added some identifier slots we've discussed and updated some descriptions.
Please review my changes & make sure everything still looks correct!
I did NOT add emsl_study_identifier because @turbomam  and I did that in a branch he had open.

#330


Icon request: Fexl & Scratch 2/3 Save

At this point, I'm just looking around my filesystem for files without icons. Fexl- *.fxl Scratch 2 - *.sb2 Scratch 3 - *.sb3

At this point, I'm just looking around my filesystem for files without icons

Digging through unfamiliar directories or codebases is actually the best way to discover formats you're missing. Keep it up. 😉
Moved the issue here as that's ideally where new icon requests should be filed (though the file-icons/atom repository continues to be updated separately…)


Issue 914: feat(ecmwf): ECMWF subset as a HySDS job

Refs #914
Purpose
HySDS package and job for subsetting ECMWF files to leverage autoscaling.
Proposed Changes

[ADD] HySDS package and job for subsetting ECMWF files

Issues
issue-914
Testing
tested on dev cluster

Tested with
sh run_subsetter_by_range_linux.sh  --start-date=2022-01-03 --end-date=2022-01-04 --bucket=opera-ecmwf --target-bucket=opera-dev-lts-fwd-hyunlee --release=issue_914


Caleb/flow meter cleanup

General code quality cleanup. Added tests, fixed typos, respected limits for numerical issues, numerical optimizations, corrected types, removed a few uses of numpy.

coverage: 85.893% (+0.02%) from 85.87%
when pulling 354809eeafaf337f58c5a7691715a702cb842b66 on caleb/flow_meter_cleanup
into 6f695b330e8f5517a1f67ea1d2b7e310d4e7f987 on master.


Feature/multiple qbs

Fair amount of rework in this PR - questionnaire banks now have a classification and any number of them can be associated with a single organization.
Reworked internals for AssessmentStatus, to make it easier to understand and work with.
UI may need a little attention, as we're still trying to generate multiple cards from a single intervention_strategy.

Of note, we need https://github.com/uwcirg/ePROMs-site-config/pull/29 which breaks out the indefinite QuestionnaireBank from the baselines.


add Zenodo integration file

You can log in to http://zenodo.org using your GitHub account. Then, you can enable tracking of this repo by Zenodo. If you create a new tag, Zenodo will grab it and create a DOI for this repo (that can be used to cite this software).
The file I added here will be read by Zenodo to generate appropriate citation information.

Welcome to Codecov :tada:
Once merged to your default branch, Codecov will compare your coverage reports and display the results in this comment.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


I continuously being asked of the password

*RancherOS Version: 0.6.0 *
Where are you running RancherOS? OpenStack Mirantis
I have tried:

adding ssh keys from Customization Script

and using

OpenStack key-pair functionalitiy

I continuously being asked of the password.
Thanks
Sotiris

I have met the same problem！ And in the same environment，V0.5.0 works fine, V0.6.0 can't work!

@codergr @chinaares Just to double check, you are trying to log in using the rancher user, correct?

Yup correct.

Also for configuration if it help I have tried both with Disk Partition:Automatic Configuration Drive checked and unchecked.
If there is a hidden flag which I can put from Configuration to enable more printouts and send you complete log please indicate.

@deniseschannon Yes, I log in using rancher!

We're not using Mirantis, but we haven't been able to recreate this issue in our OpenStack setup. Can you check to see if /var/lib/rancher/conf/metadata exists when using OpenStack key-pair functionality? When you tried adding SSH keys through a customization script, what did your cloud-config look like?

@joshwget I had checkd them,the fact is:
on rancheros-0.5.0 instance:
$ sudo cat /var/lib/rancher/conf/metadata
PublicIPv4: []
PublicIPv6: []
PrivateIPv4: []
PrivateIPv6: []
Hostname: rancheros1.novalocal
SSHPublicKeys:
rancheros1: ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDQ5w8rSX273xlK5lBoIveRClrTRbrK45xgS/Kj0vrkaVxqKoJroUFlT7jap74VXjBD7klwBHMjZuJYWJqUbiEyS5fDhJ0XpNGWVWt1GOBZYhXX3UFHdtthl/FUBx16et9z55Y+alLRK9pSHLZ56EKtiq8uAqT7WOc8yqy6FPLDhBRaw5T3XGCk4jutqgcTWNLTw1wNeEWc2xZ7Or+xMxIvow2gK6rHrler8U7YkOFErZxlCMQoWwHb4KvWGiJpAZyAW+fj/4XMeVPY8Tn1UE+kkmE9Smdr4+acK9ezJ5V0yzvtKslkGew+PTw+Z5TyqtU+7a7R74d58wVOPaR0BXYZ
Generated-by-Nova
NetworkConfig: null
on rancheros-0.6.0 instance:
$ sudo cat /var/lib/rancher/conf/metadata
cat: can't open '/var/lib/rancher/conf/metadata': No such file or directory

Anyone give some help?

Was hoping that v0.6.1 would have addressed this, but it doesn't look like it.
Removing the rancher password has basically locked us out of the openstack VM.
As a workaround, I've been spinning up v0.5.0 and then upgrading.....

Same here, Mirantis OpenStack Kilo, RancherOS 0.6.1.
Some errors found on instance console on boot:

Seems kernel/fs/fat/vfat.ko, kernel/fs/fat/fat.ko, kernel/fs/fat/vfat.ko and kernel/fs/nls/nls_cp437.ko are missing in 4.4.19-rancher kernel

Thanks

28 sep. 2016 kl. 11:37 skrev Arkadiy Shinkarev<EMAIL_ADDRESS>Seems kernel/fs/fat/vfat.ko, kernel/fs/fat/fat.ko, kernel/fs/fat/vfat.ko and kernel/fs/nls/nls_cp437.ko are missing in 4.4.19-rancher kernel
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

+1

you need to enable configure drive, if you are running in openstack
https://docs.rancher.com/os/running-rancheros/cloud/openstack/

There is a fix going into v0.8.1 that will fix the iso based config drive for openstack (we broken it in some changes that went into v0.8.0)

@SvenDowideit sorry i might have misunderstood the problem.
I just tested the rancheros-openstack image about 2-3 hours ago. It worked fine when i followed the Configuration Drive guide https://docs.rancher.com/os/running-rancheros/cloud/openstack/
Do you mean the next version v0.8.1 will work even without turning on the Configuration Drive option for openstack?

interesting! - see #1614 for the issue report - I was under the impression that the config drive needed to be ISO or VFAT - and both those were broken (in my testing too)

I cannot get it working with 0.8 in Openstack, even with the box checked it does not take the correctly.

same problem with 0.9 - in #1643 there is a milestone 0.10 for this problem.
any chance to fix install on openstack before 0.10 ?

ok - i have installed 0.9.1 on OpenStack with some dirty hacks ;-)

upload rancher-0.5

create instanse with extended configuration with cloud-config (here an example https://gist.github.com/qrpike/cfd5245d4459a2d6efd8)

login in ssh and...

sudo ros os upgrade
4.1 reboot

remove from known_hosts my rancher host

login in ssh and sudo ros console switch ubuntu
6.1 reboot

remove from known_hosts my rancher host

login in ssh and

sudo ros config set rancher.docker.tls true
sudo ros tls gen --server -H localhost -H <myhostnames>
sudo system-docker restart docker

and now i have 0.9.1 installed on OpenStack

@allustin nice one - that's exactly the same kind of hack I use when I am working with a build where installation is a a problem.
The fix I made was to get the config-2 iso to be used as metadata - I guess there's something more that openstack is doing - which we'll need to work through :(

I'm able to deploy a RancherOS v1.0.1 instance on Openstack with a keypair, which is added to the rancher user authorized_keys, allowing me to logon.


Highlight Stuff in curly brackets in f-strings

It would be very, very helpful if all the stuff in the curly brackets of f-strings could be highlighted and not appear in the same, green color of the general string

Hi @GoofyPy,
Thanks for the feedback, we already have planned working towards a new syntax highlighting backend that will enhance the colors of the editor including this case. I cannot estimate when this will be ready but it is going to be done in a future.
Thanks for reporting!


Issue in dataloader -- total perplexity in paper incorrect

Hi, your dataloader uses the default collate_fn in pytorch 0.4.1. This truncates every batch to the length of the shortest sentence in that batch. By extension your experiments are only operating on about 20% of the total datasets.
When fixed, this increases perplexity to about 300 for both FedAtt and FedAvg on the Penn Treebank dataset.

Can you provide the parameters used to reproduct the results in the paper? epochs, local epochs, learning rate, etc


Docs use old ChainConsumer API

It looks like the ChainConsumer API has changed completely since the parameter inference example was written.  I'm happy to make a PR to fix it, there's only a few lines that need to be changed.

Ah yes, my solution thus far been to not upgrade... Very welcoming to PR's fixing this!


add /usr array of java_home locations

open-jdk-1.8 for centos 6 installs into /usr/bin/java.  Adding /usr to the JAVA_HOME array lets it find it easily.

LGTM
@tumblr/collins - any thoughts about this?

It does JAVA_HOME=/usr is correct for that RPM :+1:


Set the default WSL starting directory to ~

The update that enables this on 20H1+, KB5007253, went out in November
2021.

@PankajBhojwani what is that at the top!

what is that at the top!

That's wild, do you have any repro steps?

@msftbot make sure @zadjii-msft signs off

@msftbot merge this in 1 minute


Not all translations displaying

Not all translations displaying on word detail screen.
Preconditions:

log in by Google account<EMAIL_ADDRESS>account

Steps to reproduce:

open English-Russian dictionary;
choose bigwig word and open to edit screen

Result: not all translations are displaying
Expected result: all translations display

Bug is not reproduce yet on build from dev branch.


Work on web3torrent storybook.

this issue is a duplicate of #1395 I think?

Yup, this was added during the meeting as #1395 was not on the project board.


opening URI doesn't work in all browsers

The Open URI in New Tab button doesn't actually open the URI in all browsers, such as Chromium, but rather opens a blank tab. Possibly blocked by ad-blocking extensions as well.

Works in Firefox!


scripting errors on import

When I try to import the .unitypackage or the zipped folder to my VRchat world, there is a lot of scripts that are having errors with these kinds of descriptions :
The type or namespace name 'View' 'Pool' 'UdonEvent' etc... could not be found (are you missing a using directive or an assembly reference?)
'PlayerAudioController.OnEvent(string)': no suitable method found to override

To Reproduce
Steps to reproduce the behavior:

Download the latest unitypackage from https://Guribo.github.io/TLP/index.json
Extract the files into the world directory
Simply open your project and watch the console telling which errors are making the scripts unable to compile
See error

Expected behavior
Apparently, everything should be fine.
Plattform:

[Windows 10] Desktop

Additional context
I tried using the Unity 2019 version and 2022 version. None of them worked properly

You are missing some dependencies. Please don't try to use the unity package directly but install via VCC: https://guribo.github.io/TLP/

I actually tried to do it via the VCC, but unfortunately it gives me as much errors as the manual download :

Forgot that CyanObjectPool is something you need to add manually. Sorry: https://cyanlaser.github.io/CyanPlayerObjectPool/

Oh thanks a lot!! its working perfectly fine now. Sorry I missed the second asset that I needed to add