support private _main in Dart?

This bug is more a channel for discussion. I ran recently into this situation and it made me ponder things a bit.
I was wondering if there are any reasons why 'main' has to be public, or if it should actually be private (for example, suppose we call it '_main').
The rationale for this is that it would make it easy to write libraries that serve both as libraries and entrypoints, without having to hide their 'main' method.
For example:
 a.dart:
  library a;
  x = 1;
  _main() => print(x);
 b.dart:
  import 'a.dart';
  y = x + 1;
  _main() => print(y);
The idea is that these programs would have no conflicts in their imports and could be run as entrypoints ("dart a.dart" prints '1', "dart b.dart" prints '2').
This sounds like a minor improvement because you could write this with 'hide' directives today:
 a.dart:
  library a;
  x = 1;
  main() => print(x);
 b.dart:
  import 'a.dart' hide main;
  y = x + 1;
  main() => print(y);
But it brings up two questions:
 - what is more appropriate: a public or private method?
 - should we support this in the future?

Not a bad idea, but also probably not worth the effort. Given how ancient this request is, we seem to be able to live without it OK. :)


display box

I think display box would fit in well here.
http://compass-style.org/reference/compass/css3/box/
http://www.html5rocks.com/en/tutorials/flexbox/quick/#toc-center

Can I disable erasing 'display: -webkit-box' from output css?
I'm using it for pure CSS multiline ellipsis. http://codepen.io/anon/pen/NPYzgw

+1 to what Vargentum said.


APIKA: In Settings page, the following pane texts need Finnish translations

Adding API

Sähköposti

GitHub

@baijat Verified it on nightly. it's reproduced. I'm researching the problem

@bajiat Check it again. Client ID and Secret are specified so in Finnish file. See below:
https://github.com/Digipalvelutehdas/APIKA/blob/develop/core/lib/i18n/fi.i18n.json#L659-L663

What about "Sähköposti" form - it has Finnish translate, but it doesn't work

Adding APIs has translate (screen)

"Only platform administrators are allowed to add new APIs" has translate as well, but it doesn't work


Add visual link for presentation

The project is a single-page application (SPA) built with React and Redux.
The data retrieved from the API is stored in the Redux store.
Filtered the data retrieved from the API using a Filter stateless component.
Every page (the main page and the pages for each item) is a unique route within the SPA
The project is deployed and accessible online

Hi @kene-creator,
Kindly use the updated version  of the microverse readme template for your readme, this is a requirement to get a review

Hi @kene-creator
While you made a great effort in this project, unfortunately, I cannot proceed to review your code.
Invalid Code Review Request
You have submitted a project, that does not have the updated microverse readme
Your Code Review Request will be marked as invalid in your Dashboard, so please submit a new one once you are ready 🙏
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification @prolajumokeoni.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

Invalid Code Review Request does not count into the code reviews limit.


deprecated -Cinline-threshold and wrong sector start address

fixes #13 and #16

Will do it in seperate branches...


MVP-110: Typography component

🎯 Summary

MVP-110

TRY ME -> First run npm run setup-git-aliases and then use command git changes while on this branch to see file changes made on this branch.

Added Typography component.
Added useDynamicStyles hook.
Modified JSDoc comments on some components.
Typing new format for React components.

🔰 Checklist

[x] I have read and agree with the following checklist and am following the guidelines in our Code of Conduct document.

I have performed a self-review of my code.
I have commented my code, particularly in hard-to-understand areas.
I have made corresponding changes to the documentation where required.
I have tested my changes to the best of my ability.
I have consulted with the team if introducing a new dependency.
My changes generate no new warnings.

looks good. I wonder if it may be better for the humans reading the files if the jsdoc comments were at the top of the file?

I see your point, but the way that the IDE picks up on the JSDoc comment is by it being above where the component is defined. That way it shows as a result of you hovering over the component name when you use it in your code.


Worked, with lots of cleanup afterwards

Thank you for this! I tried a few of the combinations in your readme and this worked for an archive from October 2023:
java -jar colornote-decrypt.jar 0000 28 < ~/Downloads/colornote-20231026.backup > ~/Downloads/notes.json

Hi johnhe4, great that you got it to work. What is the number 28 here? You're command does run (unlike the suggestions in the readme) but unfortunately the output is nonsense hexadecimal numbers. I take it you managed to get some human readable json?

If you scrub through the readme you'll see an example claiming:

...28 is a magic offset

I tried different values and that was the one that worked for me.
The output isn't perfect but I do have json-ish text. The biggest issue was invalid characters that I removed manually by loading the resulting file in Visual Studio Code and fixing the errors.

It looks like the JSON can be cleaned up with the cleanup scripts, e.g.
./ColorNote-backup-decryptor/fixup-v3 notes.json test.json


[4.7 Beta/Dev] import.meta reports invalid "Cannot find name 'meta' ts(2304)" error

Bug Report
🔎 Search Terms
"Cannot find name 'meta'" "2304"
🕗 Version & Regression Information

This is an issue with new "nodenext" support

⏯ Playground Link
The issue doesn't present in the playground (however it has it's own issues with the code sample).
Instead here is a repo with the issue.
💻 Code
const u = new URL(import.meta.url);

🙁 Actual behavior
It produces the error:
Cannot find name 'meta'.ts(2304)

The error vanishes if you edit tsconfig in any way, however if you then edit the file again it reappears.

While this error is shown, the rest of the behaviour of import.meta is still fine, like the type is correct and such.
🙂 Expected behavior
There should be no error.

Looks like this is another services issue that flew under the radar when we had separate services and error-reporting checkers - our symbol lookup logic for import.meta is incorrect and triggers a diagnostic in the process of doing the wrong thing. (It looks up meta inside the global ImportMeta type, fails that (naturally), then falls back to looking up meta in the surrounding scope, wat. I have to assume we have no tests for goto-def on the meta in import.meta!) As usual with issues like this, I think the fix is pretty simple (correct the logic in getSymbolAtLocation for meta properties), but the test for the regression is going to be just a bit more annoying to write than usual (since it essentially requires a test that requests diagnostics after requesting symbols for the file).

Lol, we do have tests for goto-def for import.meta, they just all expect to fail with a missing symbol (?!), even though there was (incorrect) logic to look up a symbol in place. Looks like #44364 and #45031 didn't actually mesh all that well together.


Automated cherry pick of #4542: Fix that TrafficControlTable is always created by default

Cherry pick of #4542 on release-1.10.
#4542: Fix that TrafficControlTable is always created by default
For details on the cherry pick process, see the cherry pick requests page.

/test-all


Many deoptimizations/invalidations when a benchmark ends

I've noticed this on TruffleRuby:
[engine] opt inval. id=1137  Integer#==                                                                                |Timestamp<PHONE_NUMBER>6666|Src (core):1|Reason hierarchy is unmodified Array

And many many other invalidations after the last iteration was measured.
So the good news is it shouldn't affect the captured times.
The bad news is this may cause the process to take a while longer to terminate, may cause more memory to be used due to extra invalidations & compilations, etc.
Given the above means a module was included or prepended to Integer, this is almost certainly the side effect of require 'json' so late: https://github.com/Shopify/yjit-bench/blob/5b1ec56ad5ff9ba4a159bf91d2711db36cad1d71/harness/harness-common.rb#L60
Maybe we could just serialize to json ourselves to avoid this, given the data we dump is so simple (RUBY_DESCRIPTION and floats). Any thoughts on that?
Requiring json early doesn't seem good, especially for smaller benchmarks.
Of course it's not great the json gem does such things (https://github.com/flori/json/blob/248bc5bf7ea597d7a20396a8def855a1988bf490/lib/json/common.rb#LL69C11-L69C18 and https://github.com/flori/json/blob/248bc5bf7ea597d7a20396a8def855a1988bf490/lib/json/pure/generator.rb#L285) but I don't think we can do anything about that here. In fact if it would not include but just define the methods directly it wouldn't be an issue for per class & method name caches like in TruffleRuby (and I think in CRuby too).

Maybe we could just serialize to json ourselves to avoid this

This definitely looks more like a bug in TruffleRuby than a problem with the benchmarking harness.
If there are simple changes that could be made to the json gem to make it more amenable for optimization, I would say take it up with them.

This definitely looks more like a bug in TruffleRuby than a problem with the benchmarking harness.

I would think this also causes invalidations on many Ruby implementations (or those which use inline caches and a JIT at least).
Is there a flag to tell YJIT to show code thrown away due to invalidations like monkey-patching?
For example one must invalidate the inline cache of someInteger.is_a?(someModule) if the hierarchy of Integer changes.

Does TR take a noticeable amount of time to terminate because of this?

Not really, no, but in this case I was tracing compilation (--engine.TraceCompilation) and it's basically causing a ton of noise. Similarly if I would gather compilation statistics I would then see a big number of deops/invalidations which are actually not caused by the benchmark, but by the harness.
I could use yet another harness, but OTOH I would want the same information, so not really a solution.
My initial concern was that it may skew the memory measurement, but  the RSS is collected actually just before require "json" so that's fine if that's the main place we measure memory (and would also work if we switch to getrusage()'s maxrss).
In general I think it's valuable that the benchmark harness adds as little work as possible.
Hence I think here it would make a lot of sense to just serialize to JSON ourselves, it should be trivial, I'll try it.

Either way, the json gem is obviously pretty common, and people do tend to require gems at the top of the file.

Yes, and if it's required early it's no problem for invalidations of course. So here the issue is the harness tries to avoid to load things unrelated to the benchmark (good), but then has the side effect to cause tons of invalidations due to the late require monkey patching/including modules in about every core class. We can easily have the best of both, I'll make a PR.

I've looked at usages of the hierarchy assumption, and it's used in only in https://github.com/oracle/truffleruby/blob/master/src/main/java/org/truffleruby/language/objects/IsANode.java.
It is needed for the example I gave above:

For example one must invalidate the inline cache of someInteger.is_a?(someModule) if the hierarchy of Integer changes.

But it is not needed for the case receiver.is_a?(someClass), since the superclass chain cannot change.
And that's by far the most common case of course.
The reason it cannot change is non-trivial because Class#initialize can mutate a Class.allocate class's superclass. But Class.allocate.new is not allowed hence it's not possible to create an instance of a class where the superclass is not set yet.
This would be a concern for "is A subclass of B" cases though (e.g. Module#<, when the receiver and arguments are classes).
I guess CRuby doesn't do any inline cache inside is_a?/Moduel#<, hence this is not seen (yet) as a problem on CRuby.
The bottom line is we can indeed fix this specific case in TruffleRuby and that removes most invalidations caused by require "json" (477->47), but not as much as when not requiring json.


fix flaky scp routines by allowing for timeouts to happen.

problem with scp is that sometimes it seems like there is a problem where the data push doesn't happen.  We should implement a timeout whereby if no message response occurs, it resends a the data.

fixed in f9439a0


WebDeviceInputSystem: Added workaround for MacOS Chromium based Browsers

There was an issue found with Chromium based browsers on MacOS where if the cursor left the browser window after clicking on the canvas with a mouse button other than left click, pointer capture will be lost and the canvas will still think that there's a button down.  Because this is a Chromium issue, the only thing that we can do is to create a workaround until it's fixed.  This workaround will catch the lostpointercapture event generated and release the button, if necessary.

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/14210/merge
Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14210/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14210/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/14210/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/14210/merge
https://gui.babylonjs.com/?snapshot=refs/pull/14210/merge
https://nme.babylonjs.com/?snapshot=refs/pull/14210/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/14210/merge#BCU1XR#0

is this issue tracked by chromium?

Yeah, it looks like it's been on their radar for a while but hasn't gotten any traction:
https://bugs.chromium.org/p/chromium/issues/detail?id=1131348

Visualization tests for webgl2 have failed. If some tests failed because the snapshots do not match, the report can be found at
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14210/merge/testResults/webgl2/index.html
If tests were successful afterwards, this report might not be available anymore.

Visualization tests for webgl1 have failed. If some tests failed because the snapshots do not match, the report can be found at
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14210/merge/testResults/webgl1/index.html
If tests were successful afterwards, this report might not be available anymore.

Not the biggest fan of such a custom solution integrated in the constructor TBH.
Maybe move the function registration to a polyfill/browser dependent file, outside of ths web device input system context? You could also register the event in case the environment is mac + chromium, instead of registering it on all browsers. This way the if in the function itself will be much simpler as well.

I can do that, lemme make that change now

Visualization tests for webgl1 have failed. If some tests failed because the snapshots do not match, the report can be found at
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14210/merge/testResults/webgl1/index.html
If tests were successful afterwards, this report might not be available anymore.

Visualization tests for webgl2 have failed. If some tests failed because the snapshots do not match, the report can be found at
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14210/merge/testResults/webgl2/index.html
If tests were successful afterwards, this report might not be available anymore.


Support client side (react-script)

Would you consider support for client side?
Right now, if I try to use the lib in a react app, I get this errors:
Module not found: Error: Can't resolve 'crypto' in<EMAIL_ADDRESS>
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
	- add a fallback 'resolve.fallback: { "crypto": require.resolve("crypto-browserify") }'
	- install 'crypto-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
	resolve.fallback: { "crypto": false }
ERROR in<EMAIL_ADDRESS>8:20-40
Module not found: Error: Can't resolve 'constants' in<EMAIL_ADDRESS>
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
	- add a fallback 'resolve.fallback: { "constants": require.resolve("constants-browserify") }'
	- install 'constants-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
	resolve.fallback: { "constants": false }

Unfortunately react-script is a little bit of its own beast... it uses webpack 5 but has a very complex internal config, that makes it practically impossible to override it. So, the solution "add resolve.fallback" is not straightforward in a real/new react application (and most workaround you can find on google just work for a limited amount of time, then people stop maintaining them).
In summary, the solution would be to make it possible to just link the relevant parts of the library without direct dependency on node's crypto and constants.
For additional context, I'm signing requests on the client side (react app) using two types of signers:

ed25519 using https://github.com/paulmillr/noble-curves
webauthn, ed25519 or es256

I would be prepared to support client-side, yes - but I don't have a real-world use-case for it, so I wouldn't be putting it through any battle hardening, which can be fairly important for reliable libraries.
As I understand it, the 2 areas that would need to be addressed would be:

Decoupling crypto engine so that there is no reliance on node's crypto package - that is kind of done, in that a consumer can provide any signing/verifying function they like (see recent update to README).
Remove explicit dependency on Buffer - either by relying on Uint8Array internally instead, or allowing strings to be passed around as well as buffers.

In my opinion, there is little value in using this package on the client side for signing because the secret signing key will have to be available to the browser - possibly verifying is also not very useful because if the client is communicating with a compromised server (that has been able to break SSL, etc, then they can just turn off the message signing and even just change the secret, etc).
But, I can see from #156 that there is value in being able to use it in stripped down JS environments that may not have access to NodeJS packages, but they do have access to the web APIs.

In summary, the solution would be to make it possible to just link the relevant parts of the library without direct dependency on node's crypto and constants.

Right - I think I see the problem. We have the algorithm/index.ts file which imports crypto (node library) and that gets exported so that consumers have access to the "built-in" crypto helpers, which means that (without tree-shaking, I suppose) it'll break for any non-nodejs environment.

Yes, you got all the points.
As for the keys, we use webauthn so the key is actually stored in a separated device, whether it's a hardware security key or a mobile phone (passkey). Webauthn requires user interaction for every signature, therefore for better ux we: 1) generate an ephemeral ed25519 key in the browser, 2) issue a signed-with-webauthn api request to register this session cred, 3) use this cred to sign all following api requests. The server only ever stores public keys.
The custom signer is great, and I don't see many issues managing keys and signatures. The big advantage for me personally is to use your lib for all the serialization part, as the standard is pretty complex :)

Would you be prepared to provide a PR for a side-by-side node/browser implementation/build?

I gave it a try but I got stuck :/
First a good news, changing the types from Buffer -> Uint8Array is kind of smooth, at least algorithm/index.ts seems to remain valid because Buffer implements Uint8Array. (assuming algorithm will only be used/available for node).
It remains to replace Buffer.from in various places, essentially handling conversions from string and/or base64. For string, for example, the common way is new TextEncoder().encode(str), however it appears that TextEncoder is only available in node 16+, and if I read it correctly you're supporting 12+? Unfortunately I don't know enough about node to say what's the best way to replace Buffer and/or what's the ideal minimum version to support.


Scouting Schema

From Rhea
quantitative:

auto (how many notes do they score, which pieces they intake or is it just preloaded, do they get “leave”)
each time they make a cycle (should calculate how many cycles per match and how many seconds per cycle)
where they intake on the field (ground/source zone)
where they outtake (speaker/amp/trap) & do they succeed in their outtake
endgame (do they get “spotlight,” do they hang onstage, do they get trap)
which RP do they get in a match,
did they DC and if so when
did they tip or almost tip and if so when

qualitative:
rank defensive bots on the alliance (write in comments for each bot)
rank offensive bots on the alliance (write in comments for each bot)
pit scouting:
robot dimensions (length, width, height with and without extensions)
robot weight
amp or speaker preferred
average cycle time/average cycles per match for each
have they ever disconnected on the field
have they ever tipped over
photo of the robot
Implement a schema into the database of this. Also write Zod schemas

Do we want to add intake preference to pit scouting?


LIDAR example fails to run, Assertion error

Hi,
I am attempting to run the LIDAR tour example but i get this error when the scenario loads.

It seems an assertion is failing when running the poll_sensors method.

@vNemesis I'm also running into this issue - I see you closed it, did you find a solution?

@nebriv No sorry, I no longer needed to use it. I did find that there was a similar issue when using a camera. it seems to be caused when using the step part of the code.

Some combination of removing these these lines stopped the issue when using a camera, not sure if it works the for the LIDAR as well sorry!


Remove timestamp from logs

When used with Docker/k8s, the timestamp is added by the container, basically duplicating the timestamp. Would be great to have an option to disable the timestamp.

Definitely 👍 .

Fixed in v2.11.0.


SyntaxError: Unexpected token {

Versions

nuxt: 2.13.3
node: v8.10.0

Reproduction
https://fr.nuxtjs.org/guide/installation
Simply follow the installation guide.

mkdir project
npm install --save nuxt

When running npm run dev or nuxt command, it returns SyntaxError: Unexpected token {.

Logs

$ npm install --save nuxt
npm WARN deprecated<EMAIL_ADDRESS>core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN deprecated<EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated<EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated<EMAIL_ADDRESS>Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated<EMAIL_ADDRESS>fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.

><EMAIL_ADDRESS>postinstall /home/alex/projects/front-cycling-stats/node_modules/core-js
> node -e "try{require('./postinstall')}catch(e){}"

Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!

The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
> https://opencollective.com/core-js
> https://www.patreon.com/zloirock

Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)

><EMAIL_ADDRESS>postinstall /home/alex/projects/front-cycling-stats/node_modules/ejs
> node ./postinstall.js

Thank you for installing EJS: built with the Jake JavaScript build tool (https://jakejs.com/)

><EMAIL_ADDRESS>postinstall /home/alex/projects/front-cycling-stats/node_modules/nuxt
> opencollective || exit 0

                                                 :-:
                                               .==-+:
                                              .==. :+- .-=-
                                             .==.   :==++-+=.
                                            :==.     -**: :+=.
                                           :+-      :*+++. .++.
                                          :+-      -*= .++: .=+.
                                         -+:      =*-   .+*: .=+:
                                        -+:     .=*-     .=*-  =+:
                                      .==:     .+*:        -*-  -+-
                                     .=+:.....:+*-.........:=*=..=*-
                                     .-=------=++============++====:

                                     Thanks for installing nuxtjs 🙏
                             Please consider donating to our open collective
                                    to help us maintain this package.

                                       Number of contributors: 229
                                          Number of backers: 339
                                        Annual budget: 68 539 $US
                                       Current balance: 25 768 $US

                       👉  Donate: https://opencollective.com/nuxtjs/donate

NPM logs

$ cat /home/alex/.npm/_logs/2020-07-11T07_54_22_811Z-debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/local/bin/npm', 'run', 'dev' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'predev', 'dev', 'postdev' ]
5 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>6 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>7 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
8 verbose lifecycle<EMAIL_ADDRESS>PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/alex/projects/front-cycling-stats/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/bin
9 verbose lifecycle<EMAIL_ADDRESS>CWD: /home/alex/projects/front-cycling-stats
10 silly lifecycle<EMAIL_ADDRESS>Args: [ '-c', 'nuxt' ]
11 silly lifecycle<EMAIL_ADDRESS>Returned: code: 1  signal: null
12 info lifecycle<EMAIL_ADDRESS>Failed to exec dev script
13 verbose stack Error<EMAIL_ADDRESS>dev: `nuxt`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter. (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack     at emitTwo (events.js:126:13)
13 verbose stack     at EventEmitter.emit (events.js:214:7)
13 verbose stack     at ChildProcess. (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack     at emitTwo (events.js:126:13)
13 verbose stack     at ChildProcess.emit (events.js:214:7)
13 verbose stack     at maybeClose (internal/child_process.js:925:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
14 verbose pkgid<EMAIL_ADDRESS>15 verbose cwd /home/alex/projects/front-cycling-stats
16 verbose Linux 5.3.0-62-generic
17 verbose argv "/usr/bin/node" "/usr/local/bin/npm" "run" "dev"
18 verbose node v8.10.0
19 verbose npm  v6.14.6
20 error code ELIFECYCLE
21 error errno 1
22 error<EMAIL_ADDRESS>dev: `nuxt`
22 error Exit status 1
23 error Failed at the<EMAIL_ADDRESS>dev script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

Merci :)

Upgrading to node v12 solved the issue.
I did not find any "requirement page" with minimal versions needed on nuxtjs' website.
We might need it :)

Hey!
The Node.js 8.x Maintenance LTS cycle expired on December 31, 2019 . I think it's reasonable to not expect the latest Nuxt version to work on unmaintained Node releases.

But you're right that a better error message could be displayed in the terminal. Something like "Your current Node version is not supported. Please upgrade". I wonder if this could be specified in package.json.

Hey!
The Node.js 8.x Maintenance LTS cycle expired on December 31, 2019 . I think it's reasonable to not expect the latest Nuxt version to work on unmaintained Node releases.

I think too!
But to be honest I was not thinking I was using outdated Node version since this is the latest one for Ubuntu 18.04: https://packages.ubuntu.com/bionic/nodejs.
A message would be nice :)

Hey!
The Node.js 8.x Maintenance LTS cycle expired on December 31, 2019 . I think it's reasonable to not expect the latest Nuxt version to work on unmaintained Node releases.

I think too!
But to be honest I was not thinking I was using outdated Node version since this is the latest one for Ubuntu 18.04: packages.ubuntu.com/bionic/nodejs.
A message would be nice :)

We will show the minimum Node version in the upcoming documentation rework 👍
Also keep in mind that Ubuntu packages are frozen, so updating things like node should ideally happen outside of those packages, e.g. via the node installer or node version manager.


Query for language

I'm trying to use
Card.where(language='portuguese').all()
and i'm always geting empty list, i'v try as well:
Card.where(language='russian').where(name=3).all()
that are the same of
https://api.magicthegathering.io/v1/cards?language=russian&name=3
and i'm getting empty list too.

I believe we worked this out via discord. Let me know otherwise.

Yes, we solve through discord.
The problem was that the language portuguese is in different syntax.
Card.where(language="Portuguese (Brazil)")


Update crystal deb packages - Request

Would it be possible to update the crystal branch and release a new version of the debian packages?
With the crystal packages the URDF visualization via /robot_description topic is not working, while with latest sources it does. It would be nice if we could rely on a crystal deb package while the dashing version arrives.

@nzlz do you know which PR fixed the issue? If you can find it, and it can be backported without breaking ABI, then it can be added to the next crystal patch release https://github.com/ros2/ros2/issues/684

Seem like the commit that solved the issue was: https://github.com/ros2/rviz/commit/023dddcea431395cff9f0a830c17f1fb19941976, coming from PR https://github.com/ros2/rviz/pull/378 .

@wjwwood do you think #378 can be backported? The removal 1 and addition of 2 virtual methods would break ABI in a publicly accessible class, but since the class is a Display plugin does that kind of ABI change matter?
https://github.com/ros2/rviz/blob/314150c4c38d9ef4a56b0dc1750ea8f1c928683c/rviz_default_plugins/include/rviz_default_plugins/displays/robot_model/robot_model_display.hpp#L118-L119

@nzlz it looks like Dashing will be the first distro to have that fix. The PR was dropped from Crystal patch release 3 (ros2/ros2#656) because of the API change.
Display the robot description correctly in rviz. Breaks API. Will not be released into Crystal.

    ros2/rviz#382 backports:
        ros2/rviz#378

In the meantime you might have to build rviz_default_plugins from source. https://index.ros.org/doc/ros2/Tutorials/Colcon-Tutorial/

Thanks @sloretz ! we will have to wait a few weeks then.


Rename LabeledGlobalKey's argument to debugLabel

The old name was confusing.
Fixes #462

@Hixie

LGTM


adlfs: use fsspec.asyn.get_running_loop()

Resolves #251

@hayesgb can you make a release that includes this fix?

Done

On Jul 12, 2021, at 2:07 AM, Batuhan Taskaya @.***> wrote:

@hayesgb can you make a release that includes this fix?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.


Don't use run_command for building cython --cplus code

This is now done in scipy.stats, see https://github.com/rgommers/scipy/pull/23#issuecomment-868983390. It should be using custom_target, not run_command.

Thanks for opening the issue. I will open a PR on Monday to fix this.

It was bothering me, since on each ninja invocation it was rebuilding all those files. So I had a look, and it's mostly fixed in gh-27.

fixed in gh-27


Story web non valide

Hi,
I created my first web story with WordPress Web Stories but when I test it with https://search.google.com/test/amp?hl=fr, it tells me that the web story is non valid.
Here is the web story url : https://www.pg-linguistics.fr/stories/pourquoi-engager-agence-seo/
Someone could check it please ?
With best regards,
Pierre

I do see the validation issues in the AMP test results. Could you tell me if you have WP Rocket plugin installed? If you do, you'll want to ensure that either the JS combine option is disabled or exclude story URLs from optimization in the settings. Please note we are working on a solution from the Web Stories plugin side to improve the compatibility with that plugin.

Thanks for your answer !
The web story is now valid.

I am glad your issue has been resolved.

Hey @LuckynaSan you response helped me as well. Thanks a million my friend


Add command to change the master password

A command to change the safe's master password would be nice.

👍 Any ideas on a command name for that one?

Yeah, I thought about that too. No idea.
Maybe $ pick safe password?

Adding a safe command, with children commands is an interesting idea.
This would potentially abstract less-used commands, keeping the top level CLI more streamlined. I could imagine sticking the backup and export commands in there, too.
$ pick --help
Available Commands:
  add         Add a credential
  cat         Cat a credential
  cp          Copy a credential to the clipboard
  ls          List all credentials
  rm          Remove a credential
  safe        Safe things....
  version     Print the version number of pick
...

$ pick safe --help
The safe command is used to perform operations on the safe

Available Commands:
  backup      Backup the safe
  export      Export decrypted credentials in JSON format
  password      Change the master password of the safe

I'm not sure this is a good idea, but it's a thought.

I like the idea. Should I implement it?

Sure!

Merged to develop :whale:


Roll HarfBuzz and update font-subset to the current API

The version of HarfBuzz currently in the engine's dependencies is based on 2.7.1, which is over a year old.
It should be updated to HarfBuzz 3.0.x.  When that happens the use of the font subsetting API should be updated to match the finalized API (see https://github.com/flutter/engine/pull/29266)

@jason-simmons I'd love to take this one if you're cool with it!

I don't see where flutter is dependent on this API? Do you have an idea where a good place to look is?
Do we know what changes were made to the API that needs to be updated on the flutter side?

I started working on this earlier today and verified that Flutter works as expected with HarfBuzz 3.1.1.
As part of updating Flutter to the new version I'd like to move Flutter's HarfBuzz repository to a new location (see https://github.com/flutter/flutter/issues/93571)
The https://github.com/flutter/engine/tree/master/tools/font-subset tool is using a HarfBuzz API that is now obsolete.  Once that repository is set up I can point the engine's DEPS file at the new version and reland the changes to the font-subset tool.

Ah ok great makes sense, sounds like you got it.
Let me know if there's anything I can do to help!


feat(portal): support context in TemplatePortal

Closes #6310
cc @jelbourn

@jelbourn Why does it fail?

e2e tests are just timing out, which happens sometimes


spark 3 scala 2.12 support

Pull Request Description
spark 3 scala 2.12 support

Open discussion:
should we actually change our artifact id to reflect the scala version instead of the library version ?
other libraries have a different artifactId per scala version, but we didnt use it like that from the begining .. should we release from now on two artifacts? as in:
spark-kusto-connector_2.11 and spark-kusto-connector_2.12
or should we leave the old one untouched ?

Open discussion:
should we actually change our artifact id to reflect the scala version instead of the library version ?
other libraries have a different artifactId per scala version, but we didnt use it like that from the begining .. should we release from now on two artifacts? as in:
spark-kusto-connector_2.11 and spark-kusto-connector_2.12
or should we leave the old one untouched (currently used in this PR)?

I don't know. Who knows what is the common practice?

Open discussion:
should we actually change our artifact id to reflect the scala version instead of the library version ?
other libraries have a different artifactId per scala version, but we didnt use it like that from the begining .. should we release from now on two artifacts? as in:
spark-kusto-connector_2.11 and spark-kusto-connector_2.12
or should we leave the old one untouched (currently used in this PR)?

@ohadbitt -

Per our discussion, this would be self-evident and user-friendly.
kusto-spark_<n.n.n for spark version>_<n.n for Scala version only>
E.g. kusto-spark_3.0.0_2.12

And we can do this going forward

And firm up the docs to emphasize this change


Change placement of libs to build_dir/Config

Placement of ort-genai libs:
Windows:

When build_dir provided: build_dir\Config
When build_dir not provided: build\Windows\Config\Config

Linux:

When build_dir provided: build_dir/Config
When build_dir not provided: build/Linux/Config

Thank you for the review. :)


Replace SendGrid service

SendGrid replacement

Replace with SMTP login to our personal mailbox
Update README accordingly

Postponed
We have enough credit to continue until we scale it to ~thousands of users.

"Replace with SMTP login to our personal mailbox" may be more difficult to setup and maintain than a (service-based) library like SendGrid.


action-cable-testing does not work with rspec-rails 4.0 and rails 5

The issue happens due to the following check in action_cable/testing/rspec.rb:
if RSpec::Rails::FeatureCheck.respond_to?(:has_action_cable_testing?).
It does not account for a fact that though the method is present it still returns false for Rails 5.
I suggest using if RSpec::Rails::FeatureCheck.respond_to?(:has_action_cable_testing?) && RSpec::Rails::FeatureCheck.has_action_cable_testing? instead.

Looks like my suggestion does not help :(

I finally solved the issue by doing the following in rails_spec.rb:
module RSpec::Rails::FeatureCheck
  module_function

  def has_action_cable_testing?
    true
  end
end
require 'action_cable/testing/rspec'

and completely removing require 'rspec/rails'.

Seems that feature check in rspec-rails is checking the Rails version: https://github.com/rspec/rspec-rails/blob/d810df59bb3b4ea7f3a2a0d0b169f2f2b9d390ac/lib/rspec/rails/feature_check.rb#L27
I think, that's correct: event though rspec-rails implementation is extracted from this gem, they could go out of sync. So, it's better to rely on the gem in Rails 5 even with the latest rspec-rails.
What was the problem with if RSpec::Rails::FeatureCheck.respond_to?(:has_action_cable_testing?) && RSpec::Rails::FeatureCheck.has_action_cable_testing? patch?

@palkan, it looks like require "rspec/rails" from action_cable/testing/rspeccauses to loadrspec/rails/example/channel_example_group.rbfromrspec-railsbeforehas_action_cable_testing?get a chance to be redefined  to returntrueresulting inRSpec::Rails::ChannelExampleGroupbeing empty. RSpec::Rails::ChannelExampleGroupis not loaded fromaction-cable-testingas it was already loaded fromrspec-rails` with an incomplete definition.
The workaround I use seems right to me. It tells rspec-rails to assume ActionCable testing is present and action-cable-testing gem is needed indirectly to provide the missing piece of functionality that was extracted into ActionCable 6. The other part is already in rspec-rails.

I had trouble getting the sample from @syakovyn to work in my case. If I didn't require "rspec/rails" before the monkey patch, RSpec::Rails::FeatureCheck was not defined. On the other hand, if I required it after the money patch, not all the methods were defined.
This is the solution that seems to be working for me:
require "action_cable/testing"
require "rspec/rails/feature_check"

RSpec::Rails::FeatureCheck.module_eval do
  module_function

  def has_action_cable_testing?
    true
  end
end

require "rspec/rails"


Attestation service responses and exceptions

Checklist:

[x] Code contains relevant tests for the problem you are solving
[x] Ensure all new and existing tests pass
[x] Update any relevant READMEs and docs
[x] Submit to the develop branch instead of master

Description:
Please explain the changes you made here:
Implements #29, #33, #42, #40:

standard return type for VerificationService methods
separate exceptions for each claim type
exception handling for Twilio and Sendgrid API calls
phone numbers are validated using the Twilio lookup API (supports both US and international numbers)

In addition,

handling of web3 account exceptions (for when an invalid account is passed in)
use web3 auto-initialization off of environment variable (web3 provider URI added to dotenv file)
request handler outputs a standard format for errors (array of strings, 422 status code)

One inconsistency with develop (which probably should be resolved before this PR is merged) is that #29 was implemented with exceptions having an string rather than dictionary value, so handle_request now returns two error responses:

In the event of an exception being raised in VerificationService (an array of strings): https://github.com/OriginProtocol/bridge-server/pull/48/commits/980d61822c2c6e3e5e8f119392244cd9cdb68b2e#diff-c6a86d88d4862dc3dc261772dc68e5daR41)
In the event of a validation error from Marshmallow (an array of dictionaries): https://github.com/OriginProtocol/bridge-server/blob/develop/api/helpers.py#L26

A dapp developer calling the attestation service endpoints will get a different error response format returned depending on whether they made the error-causing request with bad params, or the request hit an exception.
I wasn't sure if the [code/path/message] format that was originally implemented was meant for filtering on, and if it's ok to use string error messages (the errors could also be filtered based on class type).
If so, returning the errors as strings would change a request that fails Marshmallow validation from
{
    "errors": [
        {
            "code": "INVALID_REQUEST",
            "path": "code",
            "message": "Missing data for required field."
        },
        {
            "code": "INVALID_REQUEST",
            "path": "email",
            "message": "Not a valid email address."
        },
        {
            "code": "INVALID_REQUEST",
            "path": "identity",
            "message": "Not a valid string."
        }
    ]
}

to
{
    "errors": ["code - Missing data for required field.",
               "email - Not a valid email address.",
               "identity - Not a valid string."
    ]
}

Thoughts?

api/README has been updated

@ambertch Looking good! I can approve once the conflicts have been resolved.


chore: replacing the toolbox plugin with hardhat-zksync

What :computer:

Replacing the hardhat-zksync-toolbox plugin with hardhat-zksync

Why :hand:

The hardhat-zksync-toolbox plugin has been deprecated in favor of the new hardhat-zksync plugin, which offers a faster and easier way to use all plugins and their commands, along with task overrides.

In-progress: @dutterbutter

@kiriyaga-txfusion please address conflicts.


Why VM-UNet performance is less than standard UNet ?

Hello, Thanks for sharing the code. I found that the results of other comparative experiments were exactly the same as some papers, such as MALUNet, Transunet, swinunet, etc.  Furthermore, when I run UNet on the isic18 dataset (same data split 70 / 30), its performance （mIoU of 82.2% std +- 0.8%）much higher than VM-Unet. I don't know if there is something wrong ? 😢

@FengheTan9
Hello, thank you for your interest in this work. I clicked on the link you provided and noticed that the UNet you used has a parameter count of 34.52M, which is significantly larger than the UNet used in the original article (about 7M). Therefore, it is reasonable that the UNet you used achieved good performance. Furthermore, this paper only explores the potential applications of SSM-based models in the medical segmentation field, rather than obtaining state-of-the-art results.

@FengheTan9 Hello, thank you for your interest in this work. I clicked on the link you provided and noticed that the UNet you used has a parameter count of 34.52M, which is significantly larger than the UNet used in the original article (about 7M). Therefore, it is reasonable that the UNet you used achieved good performance. Furthermore, this paper only explores the potential applications of SSM-based models in the medical segmentation field, rather than obtaining state-of-the-art results.

Thank you for your reply. I agree with some of your points, but for example, some lightweight networks such as UNeXt, CMUNeXt or the Egeunet you previously published have higher performance than VM-UNet. Does this actually indicate that it is difficult for Manba to model weak targets?

@FengheTan9
Hello, MALUNet and EGE-UNet are designed for the task of skin lesion segmentation, while VM-UNet belongs to a general medical image segmentation model. You can draw an analogy as follows: Swin Transformer -> Swin-UNet is analogous to VMamba -> VM-UNet. The core aim of this paper is to demonstrate that, similar to Swin, Mamba also shows feasibility in medical image tasks. This is emphasized in Section 4.3 of the paper: "For instance, our model surpasses Swin-UNet, which is the first pure Transformer-based model, by 1.95% and 2.34mm in DSC and HD95 metrics. The results demonstrate the superiority of the SSM-based model in medical image segmentation tasks."

@FengheTan9  I agree with you

Swin Transformer and Swin Unet have better performance


New version: ModelConstructors v0.1.5

Registering package: ModelConstructors
Repository: https://github.com/FRBNY-DSGE/ModelConstructors.jl
Created by: @FRBNY-DSGE-Team
Version: v0.1.5
Commit: e0ad519bb4243ed561c30d1a75564cb8daf86d86
Reviewed by: @FRBNY-DSGE-Team
Reference: https://github.com/FRBNY-DSGE/ModelConstructors.jl/commit/e0ad519bb4243ed561c30d1a75564cb8daf86d86#commitcomment-35960334

Do you want to add the bounds?


Login not working in Franz, but works in website

When I try to login into Franz using my account credentials, I get the message "Email or password not valid". But when I login on meetfranz.com using the same credentials, it succeeds.

Expected Behavior

I should be able to login into Franz using my account credentials.
Current Behavior

After entering my login credentials and clicking on "Sign in", I get the message "Email or password not valid".
Screenshots (if appropriate):
Possible Solution

Steps to Reproduce (for bugs)

Open Franz
Click on "Login to your account"
Enter email address and password
Click on "Sign in"

Context

Your Environment

Franz Version used: 5.0.0-beta.18
Operating System and version: Windows 10 version 10.0.16299 Build 16299

Resetting my password using the website seems to have resolved the issue.


Enable Docs.MS PR Tagging

Return JSON representation of some of the github<->ms mapping, so we can resolve identities to a github username to add it to a PR.
@danieljurek thanks for the discussions, this is where I ended up. I want to share kusto access code without going to an external package for now. I'm certain @weshaggard will have some suggestions for how we factor that out.
@Azure/azure-sdk-eng
EDIT:
successful release
Resulting PR:

Update 7/10: Example Release including CODEOWNERS
Further EDIT prior to checkin 7/13. Test release with ONLY the changes to eng/common, but no updates to archetype-python-release. We did this to be certain that merging the eng/common changes won't break anything before we update the releases for each language.

Where do you plan to add in the call from the MS->github name mapping? I assume you plan to use the CODEOWENERS file directly and if so why do we even need to translate the id's?

I'm NOT only using codeowners file. I'm going after the person who queued the release.
Plan is to add a step to the release itself that grabs the Build.QueuedBy variable and resolves it before passing the resolved github user to the
Whether I place that in a common template published in sdk-tools,  or do it individually per repo, haven't decided yet. Today/tomorrow.

@scbedd and @weshaggard, I'm curious as to why we're doing this? Also, if we're doing this are we setting whomever queued the release to the owner? That's usually the problem with auto increment PRs, the person that queued the job sees the PR and approves it instead of assigning it to themselves (like something is going to come along and magically check it in).

@JimSuplizio had a chat offline about this, but answering here for clarify of anyone seeing your question.
This currently tags a reviewer specifically. Not an assignee

@JimSuplizio had a chat offline about this, but answering here for clarify of anyone seeing your question.
This currently tags a reviewer specifically. Not an assignee

Ultimately, we need to make this distinction, especially with auto created version increment PRs (but not right this moment). Whomever kicked off the release needs to be assigned the increment PRs and not added as a reviewer as it confuses ownership. I'd say just please create an issue for follow up to change this if it goes in tagging only reviewer.

/check-enforcer override

/check-enforcer override


[DRAFT] [WIP] Pyspark api wrapper

This take over https://github.com/dmlc/xgboost/pull/4656 , this is still WIP.

Out of curiosity, what's the difficulty of basing pyspark support on python package instead of jvm packages?

There is no difficulty, except that you need to translate all existing xgboost4j-spark code to python

Unfortunately I'm unable to import from sparkxgb after following those steps on 1.0.0
from pyspark.sql import SparkSession
spark = SparkSession.builder.config('spark.jars','xgboost4j-spark_2.12-1.0.0.jar').config('spark.jars', 'xgboost4j_2.12-1.0.0.jar').getOrCreate()
spark.sparkContext.addPyFile("xgboost4j-spark_2.12-1.0.0.jar")
spark.sparkContext.addPyFile("./xgboost4j_2.12-1.0.0.jar")
from sparkxgb import XGBoostClassifier, XGBoostClassificationModel
ModuleNotFoundError                       Traceback (most recent call last)
 in
----> 1 from sparkxgb import XGBoostClassifier, XGBoostClassificationModel
ModuleNotFoundError: No module named 'sparkxgb'
I'm running this on Jupyter, not sure if it matters or not.
Until this is packages officially, is there a workaround? I looked at some other threads but none seemed to work. Is there a zip file for 1.0.0 I can download (i saw one for 0.0.9/0.0.8)

we use a modified version of sparkxgb, it works on spark3.0 and xgboost master now. let me know if it can help.
Steps:

os.environ['PYSPARK_SUBMIT_ARGS'] = '--jars xgboost4j_2.12-1.3.0-SNAPSHOT.jar, xgboost4j-spark_2.12-1.3.0-SNAPSHOT.jar pyspark-shell'
sc.addPyFile('file:///sparkxgb.zip')

any updates on this issues ?

@WeichenXu123 Sorry if this is the wrong place to inquire, but do you know what the plan is for the Pyspark API wrapper? Is this PR still the latest effort?

@WeichenXu123 Sorry if this is the wrong place to inquire, but do you know what the plan is for the Pyspark API wrapper? Is this PR still the latest effort?

@WeichenXu123 @CodingCat Still interested in this PR (or pyspark xgboost4j support broadly speaking). Any progress on this front?

@WeichenXu123
Is this attempt still active?

we use a modified version of sparkxgb, it works on spark3.0 and xgboost master now. let me know if it can help.
Steps:

os.environ['PYSPARK_SUBMIT_ARGS'] = '--jars xgboost4j_2.12-1.3.0-SNAPSHOT.jar, xgboost4j-spark_2.12-1.3.0-SNAPSHOT.jar pyspark-shell'
sc.addPyFile('file:///sparkxgb.zip')

hello , I have seen you can run xgboost on spark3, and I  use pyspark3.1.2 that I failed many times to develop xgb, I download the file sparkxgb-1.24.zip,  but  where can I find the two jars  named xgboost4j_2.12-1.3.0-SNAPSHOT.jar and xgboost4-saprk-j_2.12-1.3.0-SNAPSHOT.jar ?
Have you changed the param in sparkxgb.init.py   version? should it be changed to 1.3.0?
Hoping your reply , I don't know how to solve the problem, thanks very much!

This is the latest one we used. We only tested on Spark3.0. Not sure if it works on spark3.1
https://github.com/Intel-bigdata/xgboost/blob/arrow-to-dmatrix/jvm-packages/xgboost4j-spark/contrib/sparkxgb_1.24.zip

thanks for your reply,  I mean  can you give me the link to download two jar packages?  I can't find them.  Thank you ~~

One jar used Gazelle's Arrow native parquet reader to read the data, another Jar transform Arrow data format into xgboost Dmatrix directly. They are all outdated. We didn't update them anymore since no one use them.


Add option to choose color scheme for profile

Steam has ability to set custom color schemes:
DefaultTheme, SummerTheme, MidnightTheme, SteelTheme, CosmicTheme, DarkModeTheme are already available for all users for free.
However, there are a lot of other colors schemes from 'Game Profiles' Point Shop section which you can't preview with your background.
When you set color scheme it changes class in body. In my opinion we can parse all available color schemes and make an option to choose color scheme

Unfortunately, with the way the site is designed, this isn't possible without massive rewrites


Control+Command leads to Switch between original TouchBar and Pock

It seems a bug to me that when I click Control+Command, the switch will be toggled. The standard shortcut double control also works. The toggle by Control+Command is quite annoying since many other shortcuts have these two keys.
macOS 11.5.2

If I remember correctly, this behavior worked properly on my machine before the 0.9 Pock rewrite. I'm thinking if we just use the previous HotKey.swift implementation, it will resolve this issue.
P.S. Also, ever since 0.9 I wasn't able to work on the Pock source code; the build keeps failing because XCode is looking for some folder that is not present in the repo. Found this problem because I was trying to open a PR the one above 😅


Voltage * Current != Active Power, is that correct?

I am using the Expandable 6 Channel ESP32 Energy Meter with 2x 120A/40mA Current Transformer YHDC SCT-016 and ESPHome.
The problem I have is that while Voltage and Current match that of my golden Kill-A-Watt, the Wattage doesn't equal Voltage * Current.
Reported by the sensor:
Voltage Phase A: 123.37 V
Current A: 0.53 A
Active Power A: 8.27 W
Calculated
123.37V * 0.53A = 65.38W != 8.27 W
Am I understanding this incorrectly? I know I'm using ESPHome but I want to understand I got the theory right first.

What do you have for your config file in ESPHome?  Also, what version of the meter?
It looks like one of the CT's is backwards. Normally one of the currents would report as negative if this were the case, but if you have a multiplier in the config, it'll come out as positive. It could also be on the opposite
There is another variable that the meter takes into account when calculating active power. Power factor. (Voltage * Current) * Power Factor = Active Power
A perfect power factor, that of a pure resistive load, is 1.

So indeed I had both clamps with the arrow pointing towards the distribution box with a multiply: -1 filter, I fixed it and removed the filter but I can't tell if anything changed. I added a Voltage on phase_b with the gain just to have a second measurement (reports similar voltage).
Voltage A | 123.27 V
Current A | 0.78 A
Active Power A | 13.82 W
Voltage B | 123.32 V
Current B | 1.02 A
Active Power B | 102.81 W
How is power factor calculated? is it a parameter or is it something that the chip can measure?
Here is my config, and I'm on the dev channel

sensor:
  - platform: atm90e32
    cs_pin: 5
    phase_a:
      voltage:
        name: "Voltage A"
        id: voltage_a
      current:
        name: "Current A"
        id: current_a
      power:
        name: "Active Power A"
        id: active_power_phase_a
      gain_voltage: 7314
      gain_ct: 21111
    phase_b:
      voltage:
        name: "Voltage B"
        id: voltage_b
      current:
        name: "Current B"
        id: current_b
      power:
        name: "Active Power B"
        id: active_power_phase_b
      gain_voltage: 7314
      gain_ct: 21111
    frequency:
      name: "Line 1 Frequency"
    line_frequency: 60Hz
    gain_pga: 2X
    chip_temperature:
      name: "Temperature"
    update_interval: 5s
  - platform: template
    name: "Calculated Power A"
    id: calculated_power_a
    unit_of_measurement: W
    update_interval: 5s
    lambda: |-
      return id(voltage_a).state * id(current_a).state;
  - platform: template
    name: "Calculated Power B"
    id: calculated_power_b
    unit_of_measurement: W
    update_interval: 5s
    lambda: |-
      return id(voltage_b).state * id(current_b).state;

Okay I got it all figured out, there are some gaps on the esphome docs but I added the reactive_power and power_factor measurements and now it should add up. Thanks for your help!

Great! Glad you figured it out!
FYI, Power factor is calculated by the meter. Here's the math of how it is done.
(true power = active power) So you can see why if current is negative, that would throw everything off.


lovelace config for HA 0.107

Is your feature request related to a problem? Please describe.
with HA 0.107 version I'm unable to add your lovelace example:
  - type: 'custom:card-templater'
    card:
      type: picture-entity
      name_template: >-
        {{ states.sensor.bio.attributes.days }} days
      show_name: True
      show_state: False
      entity: sensor.bio
      state_image:
        "0": "/local/containers/bio_today.png"
        "1": "/local/containers/bio_tomorrow.png"
        "2": "/local/containers/bio_off.png"
    entities:
      - sensor.bio

Describe the solution you'd like
Can you give updated syntax for lovelace config and images for this config?
Describe alternatives you've considered
redo config
Additional context
NA

I have  0.107.5 and it works for me.

with this config:
card:
entity: sensor.raccolta_organico_mattino
name_template: '{{ states.sensor.bio.attributes.days }} days'
show_name: True
show_state: False
state_image:
"0": "/local/containers/bio_today.png"
"1": "/local/containers/bio_tomorrow.png"
"2": "/local/containers/bio_off.png"
type: picture-entity
entities:

sensor.bio
type: 'custom:card-templater'

I have this error:
Error: Custom element not found: card-templater

Ok, and do you have the card-templater plugin installed?

yes, sure

I have to modify something?

Home Assistant complains that it does have card templater installed.
You say that you have it, but then you send a screenshot of Multiple Entity Row, which is a different plugin. So I'd say the issue is, that you do not have the card templater installed or included in your resources. But if you say you do, I do not know what the issue is.

You are right, Now I installed also Lovelace card templater, but now I have this error:
No visual editor available for: custom:card-templater

This is not an error. It is just a message from Home Assistant that the card templater does not have visual editor, because it is a custom card. So that you have to configure it in text editor. Which you did.
The important thing is, does it show the card now?

it look empty:

I arranged better my lovelace code:
card:
entity: sensor.raccolta_organico_mattino
name_template: '{{ states.sensor.raccolta_organico_mattino.attributes.days }} days'
show_name: True
show_state: False
state_image:
"0": "/local/containers/bio_today.png"
"1": "/local/containers/bio_tomorrow.png"
"2": "/local/containers/bio_off.png"
type: picture-entity
entities:

sensor.raccolta_organico_mattino
type: 'custom:card-templater'

but it seem not found image:

where I can find these image?

/local/containers/bio_today.png
/local/containers/bio_tomorrow.png
/local/containers/bio_off.png

These are your images. You can put there any image you like. Draw it. Get it on Google. Up to you. That's the point of picture-entity card.
If this is too much effort for you, use the standard glance view.

ok, thanks very much

@bruxy70 last question: you know where is the location on HASSIO 0.107 lovelace storage?
/local/containers/bio_today.png

config/www/containers

thanks again for your help!


Add filebacked metastore default config in values.yaml

I was about to open an issue for that 😄 I can take a look at this as a follow up for quickwit-oss/quickwit#3164.

That would be great. The PR #43 tries to solve the issue by defining the metastore_uri but... adding a metastore uri is bit confusing when you define a postgres config. We probably want some validation too (#44).
This is what I have in mind:
config:
  metastore:
    # Define the URI.
    uri: s3://bucket/indexes
    # uri: postgres://username:password@host:port/database
    # You  can also define a postgres metastore like this
    # postgres:
    #   host: ""
    #   port: 5432
    #   database: metastore
    #   username: quickwit
    #   password: ""

Honestly, I would prefer removing the postgres, @clemcvlcs any thoughts on this?

@imotov I just added a metastore_uri. I need to add some validation to avoid a user setting both metastore_uri and postgres.


Mixin: Pin the mixtool version in CircleCI

In mixtool, the tip of master broke for our mixin - I have managed to trace it down and opened a PR (see https://github.com/grafana/dashboard-linter/pull/143) but for now, let's pin the version to make sure our CI is not affected.

This one at least fixes 1 of the 2 failures - I'd say let's merge this one and tackle the other one independently.


Allow more config options

I just tried the plugin and really like it, doesn't have flickering issues like the previous plugin I was using. However the look of the floating is kind of strange, I used to have options like: focusable, max_width, max_height. It's great if the plugin allows users to change those, for now, I'm adding options to lsp-overloads.handlers as a workaround.
Thank you 😄

Hi @goingtosleep , glad you like the plugin!
The extension of the floating window customization is definitely on my list of things to do. Admittedly, I've been pre-occupied with my neotest-dotnet adapter work and I've been neglecting this plugin a bit because of it. Adding some config options as you suggest shouldn't be too difficult though, so when I'm back from holiday in a couple of weeks. I'll look into adding them.
What was the last plugin you were using for this out of interest?

Cool, thanks @Issafalcon.
I was using lsp_signature.nvim. It's a good plugin but somehow when I use pylsp, it keeps closing the signature help popup right after appearing. And when it doesn't close the popup, there is still flickering. The issues don't happen with your plugin 😁

Ah, yeah. I was using lsp_signature, but it was because I needed something more geared towards handling overloaded methods, with more simplicity, that I created this. I found the flickering a bit annoying too 😃
I've added some more of the popup config options in now. Hopefully it caters for all needs now. Let me know if it's missing anything else you'd like to see from a config point of view @goingtosleep

Thanks a lot @Issafalcon. Actually I'm using the following configs:
{
    focusable = true,
    focus = false,
    max_width = 80,
    max_height = 15,
    close_events = {'BufHidden', 'InsertLeave'},
}

Just the close_events is missing 😜. It's quite handy for me as it keeps the floating open. It's very nice if you could consider adding them. Thanks again and have a good weekend 😄

Ah, I see. Yeah, close_events would be useful to override for sure. I'll line up some work to add that in as well

#12


The pod is interrupted within 100s

After the pipeline is triggered, the pod execution will be term within 100s, and the pod will be regenerated
go-server: 22.1.0
go-agent: 22.1.0
kubernetes-elastic-agents:  Try the following version，3.8.1-284，3.8.2-320，3.7.1-230

At present, the command is very simple. There is only  sleep 100. I want to know whether there are parameters that can prolong the lifetime of this pod

Sorry, I am not following what you are reporting. Is the job completing as you expect on an elastic agent, or being prematurely terminated and re-scheduled?
It's expected with the current design that after a job is completed, the pod will be terminated, and a new one created for a different job, or for a re-run of the job. But it shouldn't be dying if it is still in the middle of running a job's tasks.
If it's being prematurely terminated, can please look at the k8s API for the pod to see what the reason is for the pod being terminated, and preferably check/share the pod logs as well as the logs from the elastic agent plugin from the GoCD server?

Thanks for your reply,The pod was prematurely terminated and re-scheduled,The task (sleep 100) of this job has not yet been executed completely. I looked at the pod logs and the logs of the elastic agent plugin and didn't find a possible cause. I can't know if the reason for the abnormal termination was k8s or the KubernetesPlugin.
` the elastic agent logs:
2022-08-14 10:37:54,743 DEBUG [165@MessageListener for ServerPingListener] KubernetesPlugin:56 - [Refresh Instances] Syncing k8s elastic agent pod information for cluster PluginSettings{goServerUrl=' ', autoRegisterTimeout=20, maxPendingPods=, clusterUrl=' ', securityToken=' ', clusterCACertData=' ', namespace='devops', autoRegisterPeriod=null}.
2022-08-14 10:37:54,744 DEBUG [165@MessageListener for ServerPingListener] KubernetesPlugin:46 - Using previously created client.
2022-08-14 10:37:54,760 INFO  [165@MessageListener for ServerPingListener] KubernetesPlugin:72 - [refresh-pod-state] Pod information successfully synced. All(Running/Pending) pod count is 0.
2022-08-14 10:37:54,760 DEBUG [165@MessageListener for ServerPingListener] KubernetesPlugin:46 - [Server Ping] Deleting Agents: []
2022-08-14 10:37:54,761 DEBUG [165@MessageListener for ServerPingListener] KubernetesPlugin:46 - Using previously created client.
2022-08-14 10:37:54,761 WARN  [165@MessageListener for ServerPingListener] KubernetesPlugin:97 - [Server Ping] Was expecting a containers with IDs [k8s-ea-72370e51-c835-43d4-9dfc-40b1394bc577], but it was missing! Removing missing agents from config.
2022-08-14 10:37:54,761 DEBUG [165@MessageListener for ServerPingListener] KubernetesPlugin:46 - [Server Ping] Disabling Agents: [Agent{agentId='k8s-ea-72370e51-c835-43d4-9dfc-40b1394bc577', agentState='Building', buildState='Building', configState='Enabled'}]
2022-08-14 10:37:54,763 DEBUG [165@MessageListener for ServerPingListener] KubernetesPlugin:46 - [Server Ping] Deleting Agents: [Agent{agentId='k8s-ea-72370e51-c835-43d4-9dfc-40b1394bc577', agentState='Building', buildState='Building', configState='Enabled'}]
2022-08-14 10:37:57,676 DEBUG [160@MessageListener for CreateAgentListener] KubernetesPlugin:46 - [Create Agent] creating elastic agent for profile {PodSpecType=properties, Privileged=true, MaxCPU=4, Environment=, Image=<IP_ADDRESS>/base/gocd-agent-docker-jdk8-mvn3-node17:v22.1.0, PodConfiguration=apiVersion: v1
kind: Pod
metadata:
name: pod-name-prefix-{{ POD_POSTFIX }}
labels:
app: web
spec:
containers:
- name: gocd-agent-container-{{ CONTAINER_POSTFIX }}
image: {{ GOCD_AGENT_IMAGE }}:{{ LATEST_VERSION }}
securityContext:
privileged: true, SpecifiedUsingPodConfiguration=, RemoteFile=, MaxMemory=8G, RemoteFileType=json} in cluster PluginSettings{goServerUrl=' ', autoRegisterTimeout=20, maxPendingPods=, clusterUrl=' ', securityToken=' ', clusterCACertData=' ', namespace='devops', autoRegisterPeriod=null}
2022-08-14 10:37:57,677 DEBUG [160@MessageListener for CreateAgentListener] KubernetesPlugin:56 - [Refresh Instances] Syncing k8s elastic agent pod information for cluster PluginSettings{goServerUrl=' ', autoRegisterTimeout=20, maxPendingPods=, clusterUrl=' ', securityToken=' ', clusterCACertData='', namespace='devops', autoRegisterPeriod=null}.
2022-08-14 10:37:57,677 DEBUG [160@MessageListener for CreateAgentListener] KubernetesPlugin:46 - Using previously created client.
2022-08-14 10:37:57,686 INFO  [160@MessageListener for CreateAgentListener] KubernetesPlugin:72 - [refresh-pod-state] Pod information successfully synced. All(Running/Pending) pod count is 0.
2022-08-14 10:37:57,687 DEBUG [160@MessageListener for CreateAgentListener] KubernetesPlugin:46 - Using previously created client.
2022-08-14 10:37:57,687 DEBUG [160@MessageListener for CreateAgentListener] KubernetesPlugin:46 - [Create Agent] Setting memory resource limit on k8s pod: Quantity(amount=8192, format=M, additionalProperties={}).
2022-08-14 10:37:57,687 DEBUG [160@MessageListener for CreateAgentListener] KubernetesPlugin:46 - [Create Agent] Setting cpu resource limit on k8s pod: Quantity(amount=4, format=null, additionalProperties={}).
2022-08-14 10:37:57,687 INFO  [160@MessageListener for CreateAgentListener] KubernetesPlugin:72 - [Create Agent] Creating K8s pod with spec: Pod(apiVersion=v1, kind=Pod, metadata=ObjectMeta(annotations={PodSpecType=properties, Privileged=true, MaxCPU=4, Environment=, Elastic-Agent-Job-Identifier={"pipeline_name":"lawfrontendtest02","pipeline_counter":1,"pipeline_label":"1","stage_name":"stage1","stage_counter":"1","job_name":"build","job_id":329}, Image=<IP_ADDRESS>/base/gocd-agent-docker-jdk8-mvn3-node17:v22.1.0, PodConfiguration=apiVersion: v1
kind: Pod
metadata:
name: pod-name-prefix-{{ POD_POSTFIX }}
labels:
app: web
spec:
containers:
- name: gocd-agent-container-{{ CONTAINER_POSTFIX }}
image: {{ GOCD_AGENT_IMAGE }}:{{ LATEST_VERSION }}
securityContext:
privileged: true, SpecifiedUsingPodConfiguration=, RemoteFile=, MaxMemory=8G, RemoteFileType=json}, clusterName=null, creationTimestamp=2022-08-14T02:37:57Z, deletionGracePeriodSeconds=null, deletionTimestamp=null, finalizers=[], generateName=null, generation=null, labels={Elastic-Agent-Created-By=cd.go.contrib.elasticagent.kubernetes, Elastic-Agent-Job-Id=329, kind=kubernetes-elastic-agent, Elastic-Agent-Environment-Name=mvn}, managedFields=[], name=k8s-ea-7e4f7c8c-e6de-44e8-861b-1c5e8ea56b1a, namespace=null, ownerReferences=[], resourceVersion=null, selfLink=null, uid=null, additionalProperties={}), spec=PodSpec(activeDeadlineSeconds=null, affinity=null, automountServiceAccountToken=null, containers=[Container(args=[], command=[], env=[EnvVar(name=GO_EA_SERVER_URL, value= , valueFrom=null, additionalProperties={}), EnvVar(name=GO_EA_AUTO_REGISTER_KEY, value=8eb37a91-0ef7-41d6-bd58-f3c960559adc, valueFrom=null, additionalProperties={}), EnvVar(name=GO_EA_AUTO_REGISTER_ENVIRONMENT, value=mvn, valueFrom=null, additionalProperties={}), EnvVar(name=GO_EA_AUTO_REGISTER_ELASTIC_AGENT_ID, value=k8s-ea-7e4f7c8c-e6de-44e8-861b-1c5e8ea56b1a, valueFrom=null, additionalProperties={}), EnvVar(name=GO_EA_AUTO_REGISTER_ELASTIC_PLUGIN_ID, value=cd.go.contrib.elasticagent.kubernetes, valueFrom=null, additionalProperties={})], envFrom=[], image=<IP_ADDRESS>/base/gocd-agent-docker-jdk8-mvn3-node17:v22.1.0, imagePullPolicy=IfNotPresent, lifecycle=null, livenessProbe=null, name=k8s-ea-7e4f7c8c-e6de-44e8-861b-1c5e8ea56b1a, ports=[], readinessProbe=null, resources=ResourceRequirements(limits={memory=Quantity(amount=8589934592, format=null, additionalProperties={}), cpu=Quantity(amount=4, format=null, additionalProperties={})}, requests=null, additionalProperties={}), securityContext=SecurityContext(allowPrivilegeEscalation=null, capabilities=null, privileged=true, procMount=null, readOnlyRootFilesystem=null, runAsGroup=null, runAsNonRoot=null, runAsUser=null, seLinuxOptions=null, windowsOptions=null, additionalProperties={}), stdin=null, stdinOnce=null, terminationMessagePath=null, terminationMessagePolicy=null, tty=null, volumeDevices=[], volumeMounts=[], workingDir=null, additionalProperties={})], dnsConfig=null, dnsPolicy=null, enableServiceLinks=null, hostAliases=[], hostIPC=null, hostNetwork=null, hostPID=null, hostname=null, imagePullSecrets=[], initContainers=[], nodeName=null, nodeSelector=null, preemptionPolicy=null, priority=null, priorityClassName=null, readinessGates=[], restartPolicy=null, runtimeClassName=null, schedulerName=null, securityContext=null, serviceAccount=null, serviceAccountName=null, shareProcessNamespace=null, subdomain=null, terminationGracePeriodSeconds=null, tolerations=[], volumes=[], additionalProperties={}), status=PodStatus(conditions=[], containerStatuses=[], hostIP=null, initContainerStatuses=[], message=null, nominatedNodeName=null, phase=null, podIP=null, qosClass=null, reason=null, startTime=null, additionalProperties={}), additionalProperties={}).
2022-08-14 10:38:04,677 DEBUG [107@MessageListener for WorkFinder] KubernetesPlugin:46 - [should-assign-work] Job with identifier JobIdentifier{pipelineName='lawfrontendtest02', pipelineCounter=1, pipelineLabel='1', stageName='stage1', stageCounter='1', jobName='build', jobId=329} can be assigned to an agent k8s-ea-7e4f7c8c-e6de-44e8-861b-1c5e8ea56b1a.
2022-08-14 10:38:54,743 DEBUG [165@MessageListener for ServerPingListener] KubernetesPlugin:56 - [Refresh Instances] Syncing k8s elastic agent pod information for cluster PluginSettings{goServerUrl=' ', autoRegisterTimeout=20, maxPendingPods=, clusterUrl=' ', securityToken=' ', clusterCACertData='', namespace='devops', autoRegisterPeriod=null}.
2022-08-14 10:38:54,743 DEBUG [165@MessageListener for ServerPingListener] KubernetesPlugin:46 - Using previously created client.
2022-08-14 10:38:54,759 INFO  [165@MessageListener for ServerPingListener] KubernetesPlugin:72 - [refresh-pod-state] Pod information successfully synced. All(Running/Pending) pod count is 1.
2022-08-14 10:38:54,759 DEBUG [165@MessageListener for ServerPingListener] KubernetesPlugin:46 - [Server Ping] Deleting Agents: []
2022-08-14 10:38:54,759 DEBUG [165@MessageListener for ServerPingListener] KubernetesPlugin:46 - Using previously created client.
the pod logs:
jvm 1    | 2022-08-14 02:38:00,320 INFO  [WrapperJarAppMain] ServerBinaryDownloader:121 - Got server response
jvm 1    | 2022-08-14 02:38:00,416 INFO  [WrapperJarAppMain] ServerBinaryDownloader:129 - Piped the stream to admin/agent
jvm 1    | 2022-08-14 02:38:00,416 INFO  [WrapperJarAppMain] PerfTimer:52 - Performance: Downloading new admin/agent with md5 signature: eabe138e3f243e9613ac370aab80a47c took 102ms
jvm 1    | 2022-08-14 02:38:00,639 INFO  [WrapperJarAppMain] AgentProcessParentImpl:51 - Agent is version: 22.1.0-13913
jvm 1    | 2022-08-14 02:38:00,745 INFO  [WrapperJarAppMain] ServerBinaryDownloader:114 - Downloading agent-plugins.zip
jvm 1    | 2022-08-14 02:38:00,749 INFO  [WrapperJarAppMain] ServerBinaryDownloader:121 - Got server response
jvm 1    | 2022-08-14 02:38:00,798 INFO  [WrapperJarAppMain] ServerBinaryDownloader:129 - Piped the stream to admin/agent-plugins.zip
jvm 1    | 2022-08-14 02:38:00,799 INFO  [WrapperJarAppMain] PerfTimer:52 - Performance: Downloading new admin/agent-plugins.zip with md5 signature: ad4004952ba07c0a4b3fb1732e382aae took 54ms
jvm 1    | 2022-08-14 02:38:00,803 INFO  [WrapperJarAppMain] ServerBinaryDownloader:114 - Downloading tfs-impl.jar
jvm 1    | 2022-08-14 02:38:00,807 INFO  [WrapperJarAppMain] ServerBinaryDownloader:121 - Got server response
jvm 1    | 2022-08-14 02:38:00,871 INFO  [WrapperJarAppMain] ServerBinaryDownloader:129 - Piped the stream to admin/tfs-impl.jar
jvm 1    | 2022-08-14 02:38:00,871 INFO  [WrapperJarAppMain] PerfTimer:52 - Performance: Downloading new admin/tfs-impl.jar with md5 signature: 8c36de6f9628eb159a3a82210061c79b took 68ms
jvm 1    | 2022-08-14 02:38:00,873 INFO  [WrapperJarAppMain] AgentProcessParentImpl:68 - Launching Agent with command: /gocd-jre/bin/java -Xms128m -Xmx256m -Dgo.console.stdout=true -Dgo.console.stdout=true -Dagent.plugins.md5=ad4004952ba07c0a4b3fb1732e382aae -Dagent.binary.md5=eabe138e3f243e9613ac370aab80a47c -Dagent.launcher.md5=1fad7ac3e235ce0b244c8117b88f3568 -Dagent.tfs.md5=8c36de6f9628eb159a3a82210061c79b -Dagent.bootstrapper.version=22.1.0-13913 -jar agent.jar -serverUrl http://<IP_ADDRESS>:8153/go -sslVerificationMode FULL
jvm 1    | 2022-08-14 02:38:00,971 [stderr] - [Sun Aug 14 02:38:00 GMT 2022] Starting process:
jvm 1    | 2022-08-14 02:38:00,972 [stderr] - [Sun Aug 14 02:38:00 GMT 2022]   Working directory    : /go
jvm 1    | 2022-08-14 02:38:00,974 [stderr] - [Sun Aug 14 02:38:00 GMT 2022]   Application arguments: [-serverUrl, http://<IP_ADDRESS>:8153/go, -sslVerificationMode, FULL]
jvm 1    | 2022-08-14 02:38:00,974 [stderr] - [Sun Aug 14 02:38:00 GMT 2022]            GoCD Version: 22.1.0-13913
jvm 1    | 2022-08-14 02:38:00,974 [stderr] - [Sun Aug 14 02:38:00 GMT 2022]            Java Version: 17.0.2
jvm 1    | 2022-08-14 02:38:00,974 [stderr] - [Sun Aug 14 02:38:00 GMT 2022]        Operating System: Linux(5.14.15-1.el7.elrepo.x86_64)
jvm 1    | 2022-08-14 02:38:01,424 [stderr] - Could not find file config/agent-logback.xml'. Attempting to load from classpath. jvm 1    | 2022-08-14 02:38:01,424 [stderr] - Using classpath resource jar:onejar:lib/agent-22.1.0-13913-classes.jar!/config/agent-logback.xml'.
jvm 1    | 2022-08-14 02:38:01,563 [stdout] - 2022-08-14 02:38:01,560 INFO  [main] ClassPathXmlApplicationContext:583 - Refreshing org.springframework.context.support.ClassPathXmlApplicationContext@56620197: startup date [Sun Aug 14 02:38:01 GMT 2022]; root of context hierarchy
jvm 1    | 2022-08-14 02:38:01,593 [stdout] - 2022-08-14 02:38:01,593 INFO  [main] XmlBeanDefinitionReader:317 - Loading XML bean definitions from class path resource [applicationContext.xml]
jvm 1    | 2022-08-14 02:38:01,733 [stdout] - 2022-08-14 02:38:01,733 INFO  [main] XmlBeanDefinitionReader:317 - Loading XML bean definitions from class path resource [applicationContext-plugin-infra.xml]
jvm 1    | 2022-08-14 02:38:01,908 [stdout] - 2022-08-14 02:38:01,907 INFO  [main] DefaultListableBeanFactory:821 - Overriding bean definition for bean 'pluginLoader' with a different definition: replacing [Generic bean: class [com.thoughtworks.go.plugin.infra.PluginLoader]; scope=singleton; abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0; autowireCandidate=true; primary=false; factoryBeanName=null; factoryMethodName=null; initMethodName=null; destroyMethodName=null; defined in URL [jar:onejar:lib/go-plugin-infra-22.1.0-13913.jar!/com/thoughtworks/go/plugin/infra/PluginLoader.class]] with [Generic bean: class [com.thoughtworks.go.plugin.infra.PluginLoader]; scope=; abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0; autowireCandidate=true; primary=false; factoryBeanName=null; factoryMethodName=null; initMethodName=null; destroyMethodName=null; defined in class path resource [applicationContext-plugin-infra.xml]]
jvm 1    | 2022-08-14 02:38:02,073 [stdout] - 2022-08-14 02:38:02,072 INFO  [main] AutowiredAnnotationBeanPostProcessor:156 - JSR-330 'javax.inject.Inject' annotation found and supported for autowiring
jvm 1    | 2022-08-14 02:38:02,970 [stdout] - 2022-08-14 02:38:02,968 INFO  [main] AgentStatusHttpd:90 - Agent status HTTP API server running on http://localhost:8152.
jvm 1    | 2022-08-14 02:38:03,062 [stdout] - 2022-08-14 02:38:03,062 INFO  [main] AgentHTTPClientController:96 - Configured remoting type: RemotingClient
jvm 1    | 2022-08-14 02:38:03,077 [stdout] - 2022-08-14 02:38:03,077 INFO  [main] ThreadPoolTaskScheduler:166 - Initializing ExecutorService 'scheduler'
jvm 1    | 2022-08-14 02:38:03,517 [stdout] - 2022-08-14 02:38:03,516 INFO  [main] DefaultPluginJarChangeListener:67 - Plugin load starting: /go/plugins/bundled/gocd-yum-repository-poller-plugin.jar
jvm 1    | 2022-08-14 02:38:03,672 [stdout] - 2022-08-14 02:38:03,672 INFO  [main] DefaultPluginJarChangeListener:74 - Plugin load finished: /go/plugins/bundled/gocd-yum-repository-poller-plugin.jar
jvm 1    | 2022-08-14 02:38:03,682 [stdout] - 2022-08-14 02:38:03,681 INFO  [main] DefaultPluginJarChangeListener:67 - Plugin load starting: /go/plugins/external/docker-task-assembly-0.1.27.jar
jvm 1    | 2022-08-14 02:38:03,919 [stdout] - 2022-08-14 02:38:03,918 INFO  [main] DefaultPluginJarChangeListener:74 - Plugin load finished: /go/plugins/external/docker-task-assembly-0.1.27.jar
jvm 1    | 2022-08-14 02:38:03,928 [stdout] - 2022-08-14 02:38:03,928 INFO  [main] DefaultPluginJarChangeListener:67 - Plugin load starting: /go/plugins/external/gocd-docker-pipeline-plugin-1.0.0.jar
jvm 1    | 2022-08-14 02:38:04,161 [stdout] - 2022-08-14 02:38:04,161 INFO  [scheduler-1] SslInfrastructureService:78 - [Agent Registration] Starting to register agent.
jvm 1    | 2022-08-14 02:38:04,161 [stdout] - 2022-08-14 02:38:04,161 INFO  [scheduler-1] SslInfrastructureService:88 - [Agent Registration] Fetching token from server.
jvm 1    | 2022-08-14 02:38:04,176 [stdout] - 2022-08-14 02:38:04,175 INFO  [scheduler-1] TokenRequester:56 - The server has generated token for the agent.
jvm 1    | 2022-08-14 02:38:04,177 [stdout] - 2022-08-14 02:38:04,176 INFO  [scheduler-1] SslInfrastructureService:91 - [Agent Registration] Got a token from server.
jvm 1    | 2022-08-14 02:38:04,185 [stdout] - 2022-08-14 02:38:04,184 INFO  [scheduler-1] SslInfrastructureService:170 - This agent is now approved by the server.
jvm 1    | 2022-08-14 02:38:04,185 [stdout] - 2022-08-14 02:38:04,185 INFO  [scheduler-1] SslInfrastructureService:119 - [Agent Registration] Retrieved registration from Go server.
jvm 1    | 2022-08-14 02:38:04,217 [stdout] - 2022-08-14 02:38:04,216 INFO  [scheduler-1] SslInfrastructureService:81 - [Agent Registration] Successfully registered agent.
jvm 1    | 2022-08-14 02:38:04,301 [stdout] - 2022-08-14 02:38:04,301 INFO  [main] DefaultPluginJarChangeListener:74 - Plugin load finished: /go/plugins/external/gocd-docker-pipeline-plugin-1.0.0.jar
jvm 1    | 2022-08-14 02:38:04,310 [stdout] - 2022-08-14 02:38:04,310 INFO  [main] DefaultPluginJarChangeListener:67 - Plugin load starting: /go/plugins/external/script-executor-1.0.1.jar
jvm 1    | 2022-08-14 02:38:04,645 [stdout] - 2022-08-14 02:38:04,645 ERROR [scheduler-2] RemotingClient:166 - Server responded to action ping with: status[422 Unprocessable Entity], body[{
jvm 1    | 2022-08-14 02:38:04,645 [stdout] -   "message" : "Agent [Agent [k8s-ea-7e4f7c8c-e6de-44e8-861b-1c5e8ea56b1a, <IP_ADDRESS>, 0c5f489f-e16d-4aa8-8fed-cb8ed5ea53e4, null]] has no cookie set; nested exception is com.thoughtworks.go.server.service.AgentNoCookieSetException: Agent [Agent [k8s-ea-7e4f7c8c-e6de-44e8-861b-1c5e8ea56b1a, <IP_ADDRESS>, 0c5f489f-e16d-4aa8-8fed-cb8ed5ea53e4, null]] has no cookie set"
jvm 1    | 2022-08-14 02:38:04,646 [stdout] - }]
jvm 1    | 2022-08-14 02:38:04,647 [stdout] - 2022-08-14 02:38:04,647 ERROR [scheduler-2] AgentHTTPClientController:114 - Error occurred when agent tried to ping server:
jvm 1    | 2022-08-14 02:38:04,647 [stdout] - java.lang.RuntimeException: org.apache.http.client.ClientProtocolException: The server returned status code 422. Possible reasons include:
jvm 1    | 2022-08-14 02:38:04,647 [stdout] -    - This agent has been deleted from the configuration
jvm 1    | 2022-08-14 02:38:04,647 [stdout] -    - This agent is pending approval
jvm 1    | 2022-08-14 02:38:04,647 [stdout] -    - There is possibly a reverse proxy (or load balancer) that has been misconfigured. See https://docs.gocd.org/22.1.0/installation/configure-reverse-proxy.html#agents-and-reverse-proxies for details.
jvm 1    | 2022-08-14 02:38:04,648 [stdout] - 	at com.thoughtworks.go.agent.RemotingClient.post(RemotingClient.java:118)
jvm 1    | 2022-08-14 02:38:04,648 [stdout] - 	at com.thoughtworks.go.agent.RemotingClient.ping(RemotingClient.java:74)
jvm 1    | 2022-08-14 02:38:04,648 [stdout] - 	at com.thoughtworks.go.agent.AgentHTTPClientController.ping(AgentHTTPClientController.java:109)
jvm 1    | 2022-08-14 02:38:04,648 [stdout] - 	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
jvm 1    | 2022-08-14 02:38:04,648 [stdout] - 	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
jvm 1    | 2022-08-14 02:38:04,648 [stdout] - 	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
jvm 1    | 2022-08-14 02:38:04,648 [stdout] - 	at java.base/java.lang.reflect.Method.invoke(Unknown Source)
jvm 1    | 2022-08-14 02:38:04,648 [stdout] - 	at org.springframework.scheduling.support.ScheduledMethodRunnable.run(ScheduledMethodRunnable.java:65)
jvm 1    | 2022-08-14 02:38:04,648 [stdout] - 	at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54)
jvm 1    | 2022-08-14 02:38:04,648 [stdout] - 	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
jvm 1    | 2022-08-14 02:38:04,648 [stdout] - 	at java.base/java.util.concurrent.FutureTask.runAndReset(Unknown Source)
jvm 1    | 2022-08-14 02:38:04,648 [stdout] - 	at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
jvm 1    | 2022-08-14 02:38:04,648 [stdout] - 	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
jvm 1    | 2022-08-14 02:38:04,648 [stdout] - 	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
jvm 1    | 2022-08-14 02:38:04,648 [stdout] - 	at java.base/java.lang.Thread.run(Unknown Source)
jvm 1    | 2022-08-14 02:38:04,648 [stdout] - Caused by: org.apache.http.client.ClientProtocolException: The server returned status code 422. Possible reasons include:
jvm 1    | 2022-08-14 02:38:04,648 [stdout] -    - This agent has been deleted from the configuration
jvm 1    | 2022-08-14 02:38:04,648 [stdout] -    - This agent is pending approval
jvm 1    | 2022-08-14 02:38:04,648 [stdout] -    - There is possibly a reverse proxy (or load balancer) that has been misconfigured. See https://docs.gocd.org/22.1.0/installation/configure-reverse-proxy.html#agents-and-reverse-proxies for details.
jvm 1    | 2022-08-14 02:38:04,648 [stdout] - 	at com.thoughtworks.go.agent.RemotingClient.validateResponse(RemotingClient.java:141)
jvm 1    | 2022-08-14 02:38:04,648 [stdout] - 	at com.thoughtworks.go.agent.RemotingClient.post(RemotingClient.java:114)
jvm 1    | 2022-08-14 02:38:04,648 [stdout] - 	... 14 common frames omitted
jvm 1    | 2022-08-14 02:38:04,666 [stdout] - 2022-08-14 02:38:04,666 INFO  [main] DefaultPluginJarChangeListener:74 - Plugin load finished: /go/plugins/external/script-executor-1.0.1.jar
jvm 1    | 2022-08-14 02:38:04,666 [stdout] - 2022-08-14 02:38:04,666 INFO  [scheduler-1] AgentHTTPClientController:139 - About to get cookie from the server.
jvm 1    | 2022-08-14 02:38:04,673 [stdout] - 2022-08-14 02:38:04,673 INFO  [scheduler-1] AgentHTTPClientController:142 - Got cookie: 2b4d0ee5-80cc-4277-b251-2df714abec84
jvm 1    | 2022-08-14 02:38:14,762 [stdout] - 2022-08-14 02:38:14,761 INFO  [scheduler-2] HttpService:125 - Got back 200 from server
jvm 1    | 2022-08-14 02:38:14,763 [stdout] - 2022-08-14 02:38:14,762 INFO  [scheduler-2] DefaultGoPublisher:88 - Agent [k8s-ea-7e4f7c8c-e6de-44e8-861b-1c5e8ea56b1a, <IP_ADDRESS>, 0c5f489f-e16d-4aa8-8fed-cb8ed5ea53e4] is reporting status [Preparing] to Go Server for Build [lawfrontendtest02/1/stage1/1/build/329]
jvm 1    | 2022-08-14 02:38:17,010 [stdout] - 2022-08-14 02:38:17,009 INFO  [scheduler-2] HttpService:125 - Got back 200 from server
jvm 1    | 2022-08-14 02:38:17,010 [stdout] - 2022-08-14 02:38:17,010 INFO  [scheduler-2] DefaultGoPublisher:88 - Agent [k8s-ea-7e4f7c8c-e6de-44e8-861b-1c5e8ea56b1a, <IP_ADDRESS>, 0c5f489f-e16d-4aa8-8fed-cb8ed5ea53e4] is reporting status [Building] to Go Server for Build [lawfrontendtest02/1/stage1/1/build/329]
jvm 1    | 2022-08-14 02:38:17,021 [stdout] - 2022-08-14 02:38:17,020 INFO  [scheduler-2] CommandLine:318 - Running command: sleep 110
jvm 1    | 2022-08-14 02:38:24,758 [stdout] - 2022-08-14 02:38:24,757 INFO  [pool-2-thread-1] HttpService:125 - Got back 200 from server
wrapper  | TERM trapped.  Shutting down.

`

The final wrapper  | TERM trapped.  Shutting down. implies Kubernetes sent a kill signal to the pod. That might be because the plugin deleted the pod, or because it failed health check and was being restarted. It looks like the plugin is deleting the pod/agent because it has lost registration, however the logs you have attached seem to be missing the full time period for the two pods mentioned there.
For k8s-ea-72370e51-c835-43d4-9dfc-40b1394bc577 the pod logs aren't included so not sure how the times line up. Looks like the pod logs are from the second pod. It does say at one point Was expecting a containers with IDs [k8s-ea-72370e51-c835-43d4-9dfc-40b1394bc577], but it was missing! Removing missing agents from config which implies the plugin might be deleting the pod because its not registered with the server for some reason.
For k8s-ea-7e4f7c8c-e6de-44e8-861b-1c5e8ea56b1a the elastic agent plugin logs are missing the end part when the pod is deleted, so cannot confirm it had the same behaviour as the first.
Can I suggest it would help if you tried to build a timeline of what happened at exactly which timestamps, to ensure enough information is being included?
Perhaps try and look at the server log to find logs or errors relating to registration of the agent. For some reason it seems the GoCD Server things the agent is not there anymore so it is deleting the pod. you might want to check that the token for the service account you are using has all the correct permissions noted at https://github.com/gocd/kubernetes-elastic-agents/blob/master/docs/configure_cluster_profile.md#configure-cluster-profile

thank you!
According to your suggestions and documents, it restored normal after re granting service account permissions.

Thanks! It's a bit unfortunately that it didn't seem to log any errors due to the missing permissions. My guess is that it didn't have the right list permissions or something like that :-/


Nicer static methods for C#

To create a Result in Chessie, you have to explicitly specify both generic types e.g.: -
Result<MyMessage, string>.Succeed(myMessage)

This could be simplified by having static methods on a non-generic Result class e.g.
Result.Succeed<string>(myMessage)

Closing this - I was talking rubbish. C# can't do this - you still have to specify both type args.


Get candidates endpoint

Description
Endpoint to get all the candidates from a board
Fixes  #64
How to test?
You can test out in Swagger documentation: http://localhost:3000/api/documentation/#/Members/get_users__userId__boards__boardId__members
Checklist

[ ] I have performed a self-review of my own code
[ ] I have followed the name conventions for CSS Classnames and filenames, Components names and filenames, Style filenames, if you are in doubt check the the project README.MD and here https://github.com/HackYourFuture-CPH/curriculum/blob/master/review/review-checklist.md
[ ] I have commented my code, particularly in hard-to-understand areas, if you code was simple enough mark the box anyway
[ ] I have made corresponding changes to the documentation, if you code was simple enough mark the box anyway
[ ] This PR is ready to be merged and not breaking any other functionality

I don't see the validation yet but all the rest looks excellent 🙂

I don't see the validation yet but all the rest looks excellent 🙂
It's added now :)

Hmm, not quite but I suppose we need the Firebase integration first. Basically, we need to check first if the userId provided in the URL path corresponds to the user identified by the Firebase token. So, validating that the user is who they claim to be. Otherwise, with a valid token, you could check anyone else's data. But we don't have Firebase yet so it's good.

Hmm, not quite but I suppose we need the Firebase integration first. Basically, we need to check first if the userId provided in the URL path corresponds to the user identified by the Firebase token. So, validating that the user is who they claim to be. Otherwise, with a valid token, you could check anyone else's data. But we don't have Firebase yet so it's good.

We have authentication working now. All requests will be piped through the authenticate middleware by calling router.use(authenticate)


Prevent editing of  camps related to past events

Overview of the problem
Currently past events (such as Midburn2018) are editable - this shouldn't be functional after the event.

Steps to Reproduce

Navigate to camp management (in past event)
Editing is available.

Expected behavior
Editing old camps related to old event shouldn't be possible.

Actual behavior
Editing camps related to old event is possible.

Will be fixed via #991


Semi-supervised scArches

Thank you for creating this tool. I’ve been following your vignette for semi-supervised scArches with SCANVI, with a reference dataset (1 batch) and a query dataset (1 batch). However, when I train SCANVI on the reference, it achieves prediction accuracy of only 59%. Is there anything I can do to improve the performance?

Hey, thanks for using the model :) I would suggest you include more datasets in the reference building. There are two factors in having query integration:

The reference model needs to have seen multiple dataasts in order to understand the meaning of batch
The quality of the datasets are important and need to  include multiple cell types and enough cells in each batch

Thanks for your helpful feedback. I tried splitting the reference into two batches (10x v2 vs 10x v3 sequencing technology), but the improvement was marginal (accuracy of 61%).

The unsupervised trainer trains for 332 out of 500 epochs, and the semisupervised trainer trains for only 12 out of 200 epochs. Is there anything I can change about the training regime to improve performance?

In the reference dataset, I have approximately 200k cells, 400 genes, and 95 cell types. Is this too few cells and/or too few genes given the number of cell types?

Is the problem solved now? happy to follow up on this.

Thanks @M0hammadL the problem is unresolved.


Apply fixes from StyleCI

This pull request applies code style fixes from an analysis carried out by StyleCI.

For more information, click here.

please can you help me am relaly new to php how to include this after installing via composer
am not able to use


[EBPF] Add Ubuntu 24.04 to KMT

What does this PR do?

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/trigger-ci -v RUN_KMT_TESTS=on

/merge


Axes for all

[ ] xref/yref in annotations (next pr)

@nicolaskruchten this is a first pass that takes care of axes for all plot types, and does not use the plotly.Axes.list() function that doesn't work on plots other than cartesian.
I'm taking care of subplots next..
Would you give this a look?

💃


storage/fileset/index: Fix issue where levelWriter callback points to wrong level.

Previously we checked if a level needed to be created using the read lock with numLevels, then if necessary, we created a level using createLevel(lw *levelWriter).
The callback for a levelWriter is configured using the index which that levelWriter will be assigned to.  It can't go anywhere on the level stack.  It has to go at it's index or the callback will be messed up.
In createLevel we append without checking the length, potentially inserting a levelWriter with a callback for the wrong level at the end of the stack of levels.
These changes check whether a level needs to be added while holding the lock, and then add it, so that no other levelWriters will be created in between.  It also does a check with the read lock first, so that in the common case we only need the read lock to get a level writer.

Closing, after talking with @acohen4.  This would require two callbacks to be triggered for the same level, which is not supposed to happen.


NPM Audit vulnerability with @angular-devkit

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request
[x] Other... Please describe:

NPM Audit vulnerability

Current behavior

There is an NPM audit vulnerability in the @angular-devkit dependency of your package.
Prototype pollution
Package: set-value
Patched in: >=3.0.1
Path: @datorama/akita > schematics-utilities > @angular-devkit/core > ... > set-value
More info: https://npmjs.com/advisories/1012

Expected behavior

NPM vulnerability needs to be handled.
Minimal reproduction of the problem with instructions
Repro can be accomplished by running npm audit
Environment
Angular version 7.2.15
Akita version: 4.4.3
Node version: 12.4.0

It does not look like v0.802.0-next.0 of @angular-devkit/build-angular has a fix for the set-value package...

I am closing it for now as it's not an Akita issue.