[3.0] Fix appendAttribute key

What is the purpose of the change
Brief changelog
Verifying this change

Checklist

[x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Add some description to dubbo-website project if you are requesting to add a feature.
[ ] GitHub Actions works fine on your own branch.
[ ] If this contribution is large, please follow the Software Donation Guide.

Codecov Report

Merging #8847 (8a50bf5) into 3.0 (d3f7ab4) will decrease coverage by 0.23%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##                3.0    #8847      +/-   ##
============================================
- Coverage     63.77%   63.53%   -0.24%
+ Complexity      315      311       -4
============================================
  Files          1169     1169
  Lines         49216    49218       +2
  Branches       7361     7339      -22
============================================
- Hits          31389    31273     -116
- Misses        14406    14506     +100
- Partials       3421     3439      +18

Impacted Files
Coverage Δ

...c/main/java/org/apache/dubbo/config/Constants.java
100.00% <ø> (ø)

...ain/java/org/apache/dubbo/config/MethodConfig.java
84.31% <ø> (ø)

...n/java/org/apache/dubbo/config/AbstractConfig.java
80.28% <100.00%> (+0.11%)
:arrow_up:

...ng/transport/dispatcher/all/AllChannelHandler.java
62.06% <0.00%> (-27.59%)
:arrow_down:

...ntext/event/AwaitingNonWebApplicationListener.java
60.56% <0.00%> (-22.54%)
:arrow_down:

...dubbo/common/status/support/LoadStatusChecker.java
46.15% <0.00%> (-15.39%)
:arrow_down:

...ng/transport/dispatcher/WrappedChannelHandler.java
47.82% <0.00%> (-15.22%)
:arrow_down:

...ache/dubbo/remoting/transport/AbstractChannel.java
75.00% <0.00%> (-12.50%)
:arrow_down:

...ubbo/registry/client/AbstractServiceDiscovery.java
87.50% <0.00%> (-12.50%)
:arrow_down:

...in/java/org/apache/dubbo/common/utils/JVMUtil.java
81.13% <0.00%> (-11.33%)
:arrow_down:

... and 35 more

Continue to review full report at Codecov.

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

looks good


Updated Documentation

Added Asset Package download location to Getting Started.md
Added Input Class Diagrams to Input/Readme.
https://github.com/Microsoft/HoloToolkit-Unity/issues/431 Removed reference to GestureManipulator.cs in Input/readme.
https://github.com/Microsoft/HoloToolkit-Unity/issues/380 Removed Main Camera.prefab reference in Utilities/Readme.md and GettingStarted.md
https://github.com/Microsoft/HoloToolkit-Unity/issues/411 Removed reference to ManualCameraControl in GettingStarted.md
Moved Project specific settings changes into Using HoloToolkit-Unity in Your Project instead of Preparing a Scene for Holographic Content in GettingStarted.md
Added more content to Preparing a Scene for Holographic Content in GettingStarted.md
Minor Formatting.

@NeerajW changes completed.

I don't know what the overall opinion is, but I'd prefer to not have spaces in folder and file names:

External/HoloToolkit/Asset Packages/HoloToolkit.unitypackage
External/ReadMeImages/Cursor System Diagram.PNG
External/ReadMeImages/Input System Diagram.png

This would also make the embedded image paths look nicer, although, yes they won't be seen, but ![alt text](/External/ReadMeImages/Input%20System%20Diagram.png)

Agreed. I'll make these changes asap.

@HodgsonSDAS Looks like the first space in the images was removed, but the second wasn't. The links were updated completely though.

@NeerajW I would advise to making a new release tag with the current version before merging this.

@HodgsonSDAS I agree. We will not merge this until we have a new release tag and a new unity package corresponding to that tag :)

@NeerajW I started a draft release

Now that we have a release version how does this look?

@keveleigh, @NeerajW Now that we have a release version how does this look?


DoNotMerge | Add a new kusto version with changes

The main changes in this PR:
Add a new version
Add a path for 'database move command'
Add a new property enablePurge for ClusterProperties

You don't have permission to trigger SDK Automation.
Please add yourself to Azure group from opensource portal if you are MSFT employee,
or please ask reviewer to add comment *** /openapibot sdkautomation ***.
Please ask<EMAIL_ADDRESS>(or NullMDR in github) for additional help.

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

Can one of the admins verify this patch?

Hi @zoharHenMicrosoft there are too many services get changed in this pr, and I believe some of them are just format change. I suggest you revert those changes on those services that you do not want to update. We can find another way to fix the formatter CI.

Hi @zoharHenMicrosoft there are too many services get changed in this pr, and I believe some of them are just format change. I suggest you revert those changes on those services that you do not want to update. We can find another way to fix the formatter CI.

Hi @zoharHenMicrosoft there are too many services get changed in this pr, and I believe some of them are just format change. I suggest you revert those changes on those services that you do not want to update. We can find another way to fix the formatter CI.

done

Hi! any updates? :)

Hi @zoharHenMicrosoft since there is no update for quite a long time, I will close this PR for now. If you would make more update on this PR, please feel free to reopen this then.

Hi @zoharHenMicrosoft since there is no update for quite a long time, I will close this PR for now. If you would make more updates on this PR, please feel free to reopen this then.

please reopen, as I just added a few more changes :) thanks!

@ArcturusZhang Hi! can you reopen this PR, please?

please notice that customers are waiting for this, so I would appreciate it if you could respond as soon as possible, thanks!! @ArcturusZhang @majastrz

the changes in the other PR have been approved by ARM and the only other change here is to rename the api-version. signing off from ARM side on this.

please notice that customers are waiting for this, so I would appreciate it if you could respond as soon as possible, thanks!! @ArcturusZhang @majastrz

Sorry about the delay. and would you please resolve the last comment that @ravbhatnagar just left? Or please let me know you have already resolved that.

please notice that customers are waiting for this, so I would appreciate it if you could respond as soon as possible, thanks!! @ArcturusZhang @majastrz

Sorry about the delay. and would you please resolve the last comment that @ravbhatnagar just left? Or please let me know you have already resolved that.

Hi! can you please clarify what is the issue I should resolve? as we indeed wish to rename this version, and it seems we pass all tests and requirements :). @ravbhatnagar  @ArcturusZhang

please notice that customers are waiting for this, so I would appreciate it if you could respond as soon as possible, thanks!! @ArcturusZhang @majastrz

Sorry about the delay. and would you please resolve the last comment that @ravbhatnagar just left? Or please let me know you have already resolved that.

Hi! can you please clarify what is the issue I should resolve? as we indeed wish to rename this version, and it seems we pass all tests and requirements :). @ravbhatnagar @ArcturusZhang

SOrry about this that I just re-read @ravbhatnagar 's comment and it turns out that I mis-understand his meanings then. I will merge this as soon as the CI passes.

/azp run


Upgrade request

for node-webkit-builder and lodash
> npm install

npm WARN deprecated<EMAIL_ADDRESS>WARNING: This module has been renamed to nw-builder. Install using nw-builder instead, node-webkit-builder will no longer be updated.
npm WARN prefer global<EMAIL_ADDRESS>should be installed with -g
npm WARN deprecated<EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained. Upgrade to<EMAIL_ADDRESS>npm WARN optional dep failed, continuing<EMAIL_ADDRESS>

It appears gulp-node-webkit-builder has renamed to gulp-nw-builderand has the newer nw-builder
  "dependencies": {
    "gulp-util": "^3.0.6",
    "nw-builder": "^2.0.2",
    "through2": "^2.0.0"
  }


MWPW-138026 Add tags to lana logs

Add tags
Replace consoles with lana

Resolves: MWPW-138026

Test URLs:

Before: https://main--bacom--adobecom.hlx.live/?martech=off
After: https://bmarshal-lana-logs--bacom--adobecom.hlx.live/?martech=off

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (3833c81) 97.19% compared to head (eaa5de4) 97.19%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #160      +/-   ##
==========================================
- Coverage   97.19%   97.19%   -0.01%
==========================================
  Files           8        8
  Lines         714      712       -2
==========================================
- Hits          694      692       -2
  Misses         20       20

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Add qwen config and and input config simplification

:rocket: What

Adds QWEN support to TRTLLM build configuration
Removes max_input_len and max_output_len configuration in favor of max_seq_len
Adds defaults for max_batch_size and max_num_tokens

:computer: How

:microscope: Testing

once this lands we should get https://github.com/basetenlabs/docs.baseten.co/pull/99 out


First reveal is always a no mine near field.

First game reveal will always be a no mine near field.

Why close


fix: don't map the image name in sbom reports

fixes: #645

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 12.95%. Comparing base (09054d3) to head (b85341a).
Report is 136 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff             @@
##             main     #647       +/-   ##
===========================================
- Coverage   25.13%   12.95%   -12.18%
===========================================
  Files           6       13        +7
  Lines         565     1212      +647
===========================================
+ Hits          142      157       +15
- Misses        406     1033      +627
- Partials       17       22        +5

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


non-interactive automated alignment

Hi again! Instead of manually interacting with the Shiny app, I want to automate the process and get the results directly in a single run.
Is there a way to convert the interactive steps that runs entirely in R with automated registration?
Originally posted by @smc9477 in https://github.com/BIMSBbioinfo/VoltRon/issues/144#issuecomment-2556434257

Hey there,
We have an implemented for this now which is still on development stage:
https://artur-man.github.io/VoltRon/registration.html#Automated_Image_Alignment
You can also pull this version from the dev branch, and let us know if it works properly. Otherwise we can iterate over it!


Update README.md

snake-charmer set project version from 1.3.0 to 1.3.1. If you do not want to release a new version with this PR remove the release label from this PR


Add support for Cypress 10

Cypress 10 changes it's config from JSON to .config.js/.ts/.mjs/.cjs and removes JSON support. This complicates things significantly, especially for Typescript configs as these cannot be read easily in the compiled Javascript that is used in the action. I need to find a way to accomplish this in order to make the action useful for future Cypress versions.
Cypress 10 migration guide: https://docs.cypress.io/guides/references/migration-guide#Configuration-File-Changes
Cypress 10 config: https://docs.cypress.io/guides/references/configuration#Configuration-File

Hi Any update on this?

Sorry, I currently have no time to implement this. But I'm happy to accept pull requests!

@tgamauf first of all, thanks a lot for this plugin. It has allowed me to run our Cypress e2e test suites in parallel using scheduled run on CI using GitHub Actions. Unfortunately, we're stuck when updating to Cypress 10 due to this dependency. Are there any updates on this issue?
I would be willing to make a Pull Request, but I will need some assistance on how to contribute to it. Can you offer me some pointers on which files are responsible for what? What are the challenges? How to test if my possible fix is working?...etc...

Sure, I would be happy for a solution!
There really is only a single file that is relevant for this: https://github.com/tgamauf/cypress-parallel/blob/283d8935c81e7eb304238e080019470cca7a9c4a/src/parsing.ts. Two parts have to be adapted:

the function findWorkingDirectory looks for the Cypress config file. At the moment this will always look for the cypress.json file, but now has to look for all possible versions: cypress.config.js, cypress.config.ts, cypress.config.mjs, cypress.config.cjs. Another issue here is if there are multiple config files found, but this isn't valid according to the migration guide anyway
the function loadCypressConfig is responsible for parsing the config file and providing the configuration values that are relevant for us. Up to now this was componentFolder, ignoreTestFiles, integrationFolder, testFiles. However, this changed to specPattern and excludeSpecPattern. Also, there might be more changes that I haven't found yet - need to check the migration guide for that as well.

Testing is pretty simple, you can find everything test related in __tests__ - simply replace the current fixtures with fixtures for all of the different config file types and change and extend the tests in https://github.com/tgamauf/cypress-parallel/blob/283d8935c81e7eb304238e080019470cca7a9c4a/__tests__/parsing.test.ts.
The main problem here is this: up to version 10, Cypress configuration was done by the cypress.json file in the Cypress root. As it was JSON it was trivial to read with Javascript. In version 10 they changed that to a cypress.config.js (and a few other file endings), which doesn't contain static key-value pairs, but Javascript/Typescript code. Something like that:
const { defineConfig } = require('cypress')

module.exports = defineConfig({
  e2e: {
    baseUrl: 'http://localhost:1234'
  }
})

or something very similar in Typescript.
I don't see any easy way to reliably parse this myself. As this can contain functional JS/TS code I basically would have to implement an interpreter that reads the file, "understands" it, and then provide the few config values that are actually relevant for cypress-parallel. My preferred solution would be to use the original Cypress code - there has to be some function in the Cypress code that actually reads this config and it should be possible to reuse this. Most likely it isn't public, which means that we would have to copy the code (which is rarely a good approach, but better than nothing). As I don't know the Cypress internals well, I couldn't find the parts responsible for parsing the config when I looked.
I also know that a number of widely used JS projects like Webpack use this or a very similar JS config scheme, so it is possible that a general "Javascript config parsing library" exists. I couldn't find anything when I looked, though.

Btw. backward compatibility doesn't matter - this version of the action will remain the version up to Cypress 10.

I just ran into the problem when trying to use this action in one project where Cypress 10 was already in use. I was wondering whether it would be a temporary workaround to add a parameter test-location to the action. This could then be used to directly specify the folder and skip the parsing of the configuration file. Or are there other parts taken from the configuration?

As mentioned above, the following Cypress config options are currently used: componentFolder, ignoreTestFiles, integrationFolder, and testFiles. In Cypress 10 the corresponding options are specPattern and excludeSpecPattern. This allows filtering of test specs. So sadly it‘s not as simple as that …

Alright, guys, sorry that this took so long. But Cypress 10+ should work now.
Thanks to @kgw4it for pointing me in the right direction and starting the implementation!


Coin Smart Contract

Description
With the help of this smart contract u can send coins to other people, The contract allows only its creator to mint new coins.
Fixes #<32>
Type of change

[x] Add a new project

Domain of Contribution

[x] Project using only Solidity

[x] Project Test on the Remix IDE

Checklist ✓
Please delete options that are not relevant. In order to tick the check box just put x inside them for example [x] like this

[x] l have performed a self-review of my own code or work.

[x] I have commented on my code, particularly in hard-to-understand areas.

[x] I'm SSOC'22 contributor

Screenshots/Gif (Recommended)

@AnmolSirola  make your branch updated . Look's lile your branch is behind from mine .
All set  for merging . :smile:

Sir, can u check it now

Great @AnmolSirola


Updation

Please update it to work with google api level 35.

Hi, thanks for using the plugin. Version 1.2.3 will feature upgrade to target sdk 35!


chore: add yarn release

I needed to add this file from mainline in order to use the sst2 branch

team uses pnpm for sst2 which is A-OK!


images gradually shrinks

video of my problem nsfw

I am indeed having this problem. It's weird - the image just...shrinks away whenever I click on one from the timeline

Issue title should be renamed as we can't  recognize the problem until watch the video. I suggest some titles:

Picture displayed on modal window gradually shrinks step by step, if window size is not enough

The issue improved once I cleared the cache that I originally had.

this is still happening for me with latest version.

Does this still happen?

The issue is fixed. Thank you.
David Linville
@.***
On Tue, Sep 5, 2023 at 7:41 AM dimden @.***> wrote:

Does this still happen?
—
Reply to this email directly, view it on GitHub
https://github.com/dimdenGD/OldTweetDeck/issues/17#issuecomment-1706547778,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIV44DS5QBQZLMBBTG2JJGLXY4MY3ANCNFSM6AAAAAA3XYIK3U
.
You are receiving this because you commented.Message ID:
@.***>


Add AQA_AUTO_GEN option to force generate AQA test jobs

Force generating AQA test jobs is needed for updating out-of-date test jobs. This PR allows users to set AQA_AUTO_GEN option for the pipeline.
Related: https://github.com/eclipse-openj9/openj9/issues/14318
Signed-off-by: lanxia<EMAIL_ADDRESS>

run tests

FYI @smlambert

afaik, there is no pipeline that I can use to properly test this PR - from starting the SDK build to triggering the test pipeline. The PR builds are just partial testing.


feat(send): add validation for send amount screen

Description
Adds the error states for send enter amount screen. The prepare transaction stuff is mocked based on the upcoming implementation in #4378
Test plan
Unit tests, manual

Above balance
Max amount
No balance for gas

Related issues

Fixes ACT-943

Backwards compatibility
Yes

@satish-ravi it seems like input doesn't handle comma's which are used for decimals in Europe. PR #3074 fixed a similar issue on the swaps screen. I also saw it attempted to convert the input amount to a number when only adding . resulting in a NaN displayed.

@satish-ravi it seems like input doesn't handle comma's which are used for decimals in Europe. PR #3074 fixed a similar issue on the swaps screen. I also saw it attempted to convert the input amount to a number when only adding . resulting in a NaN displayed.

thanks @MuckT, addressed in a4bd260


If the table contains |, it will not be formatted well

If the table contains |, it will not be formatted well
When formatting a table containing | using markdowntable.format (markdowntable.nextCell or markdowntable.prevCell) as shown below gives the following results:

Before format

|contents|description |
| :---: | :--- |
| If the table contains `|` | it will not be formatted well |

Result (After format)

|        contents         | description |
| :---------------------: | :---------- |
| If the table contains ` | `           | it will not be formatted well

I expect the following results:

Expected result

|         contents          | description                   |
| :-----------------------: | :---------------------------- |
| If the table contains `|` | it will not be formatted well |

It's a easy-to-use extension and it's very helpful.
Thank you.

@takumisoft68 I love this extension, but I am running in to this problem too.
Would you consider allowing \| as a way of escaping the pipe character, so that it can be allowed as cell content?

Alternately, using the | HTML entity works

@Yarakashi-Kikohshi, @lunelson
I allowed inline-code and escaping | in table, in v0.7.1.
And I released it on 5 Dec 2020.
Try using it!

I'm so glad to hear that @Yarakashi-Kikohshi ! This will certainly make things easier, not to have to remember the HTML entity code for it 😄
It seems to work great, with one exception: keyboard tabbing through cells still gets caught on the escaped character:

Thank you for supporting this issue!:smile:
However, as already mentioned by lunelson, keyboard tabbing through cells still gets caught on inline-code too...

@lunelson @Yarakashi-Kikohshi
This is fixed at #34, and v0.7.2 has been released.

With v0.7.2, I can do what I expected!
Thank you for your support. :relaxed:


bitwarden: 1.23.1 -> 1.24.6

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/bitwarden/desktop/releases.
meta.description for bitwarden is: "A secure and free password manager for all of your devices"
meta.homepage for bitwarden is: "https://bitwarden.com"
meta.changelog for bitwarden is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 1.24.6 with grep in /nix/store/8lf0h3nim5qw9gqgba98lb76zqhcvp3g-bitwarden-1.24.6

directory tree listing: https://gist.github.com/1c3b7cc50b7db9f530f01aa422d210a6

du listing: https://gist.github.com/75338528c1f3fcca4c8db88152d5663b

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
0 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
0 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
bitwarden

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/8lf0h3nim5qw9gqgba98lb76zqhcvp3g-bitwarden-1.24.6 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A bitwarden https://github.com/r-ryantm/nixpkgs/archive/4e4d872b0b05c413d2c4d5c4add7fa0b4c474520.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/8lf0h3nim5qw9gqgba98lb76zqhcvp3g-bitwarden-1.24.6
ls -la /nix/store/8lf0h3nim5qw9gqgba98lb76zqhcvp3g-bitwarden-1.24.6/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

bitwarden

Maintainer pings
cc @Kiwi for testing.

passed nixpkgs-review. Waiting for darwin CI to merge (but darwin seems to never complete...)

passed nixpkgs-review. Waiting for darwin CI to merge (but darwin seems to never complete...)

It won't
https://github.com/NixOS/nixpkgs/blob/4e4d872b0b05c413d2c4d5c4add7fa0b4c474520/pkgs/tools/security/bitwarden/default.nix#L86-L88
it's on a very long todo list ;(

It won't
https://github.com/NixOS/nixpkgs/blob/4e4d872b0b05c413d2c4d5c4add7fa0b4c474520/pkgs/tools/security/bitwarden/default.nix#L86-L88
it's on a very long todo list ;(

shouldn't that check goto meta.platforms instead ?!

shouldn't that check goto meta.platforms instead ?!

I think this is how @worldofpeace told me to

I think this is how @worldofpeace told me to


Can't get it working after building.

Works fine in dev mode, but when using yarn build none of the string are showing up.
next.config.js
module.exports = {
  i18n: {
    locales: ["en", "de"],
    defaultLocale: "en",
  },
};

en.ts
import { Locale } from ".";

export const table: Locale = {
  login: {
    forgot_password: "Forgot Password?",
    log_in: "Log In",
  },
};

in `app.tsx`

```l
<I18nProvider table={pageProps.table}>
     <Component {...pageProps} />
</I18nProvider>

login.tsx
function Login() {
  const i18n = useI18n<Locale>();
  const { t, locale } = i18n;
  console.log(locale())
 return (
    <div>{t("login.log_in")}</div>
  )
}

export const getStaticProps: GetStaticProps<I18nProps<Locale>> = async (
  context
) => {
  const locale = context.locale || context.defaultLocale;
  const { table = {} } = await import(`i18n/${locale}`)
  console.log(locale);
  return { props: { table } };
};

It seems when I check locale() in the console that it is undefined.  Am I doing something wrong here?

I think is this line:
const { table = {} } = await import(`i18n/${locale}`)

Try using a relative path
const { table = {} } = await import(`../i18n/${locale}`)

I think is this line:
const { table = {} } = await import(`i18n/${locale}`)

Try using a relative path
const { table = {} } = await import(`../i18n/${locale}`)

Hey, I think it was actually a bug in NextJS, upgrading to v10.0.5-canary.1 fixed it for me.  FYI the issue was that the locale returned from useRouter was undefined.

Hey, I think it was actually a bug in NextJS, upgrading to v10.0.5-canary.1 fixed it for me.  FYI the issue was that the locale returned from useRouter was undefined.


Recommend to ZIP your JSON folder? How about rendered courses?

Bear with me please, but I just have a few questions in regards to how to save our downloaded courses (NOT RENDERED YET).
Is it okay to compress the folder and upload it to our DropBox, etc? Or do we risk losing some JSON data?
And for courses that have been rendered, is it okay to compress them as ZIP file as well or do we risk of losing some content? I tried it and I don't really see any folder size difference at all.
Lastly, any advice on how to keep track of things I installed via terminal? I'm running on Mac Catalina and if anyone has any advice on how to keep track of things I downloaded via terminal like miniconda, node, npm, Udacimak, etc. will be greatly appreciated it.
I'm thinking of resetting my laptop to factory setting soon b/c it's just so messy right now, and I would like to just be prepared.
Sometimes I just fall into the Github rabbit hole and just pip install everything I'm told to do and forget how to uninstall them. Then I realize that they don't show you how to uninstall them OR I just don't even know what exactly I downloaded b/c it's not visible like softwares.
Right now, I can't download anything really if I don't do sudo install. And I just want to make a separate partition that's just for doing stuff like this and none of the downloads will be installed onto the Main Drive.
Ahhh, a long post. Than you for reading  if you got this far but I'm just trying to get my life together lol.

Is it okay to compress the folder and upload it to our DropBox, etc? Or do we risk losing some JSON data?
And for courses that have been rendered, is it okay to compress them as ZIP file as well or do we risk of losing some content? I tried it and I don't really see any folder size difference at all.

Yes, you should always keep your JSON files - they are the main data source to get the course contents. There's no problem compressing and uploading them on your cloud storage.

Lastly, any advice on how to keep track of things I installed via terminal? I'm running on Mac Catalina and if anyone has any advice on how to keep track of things I downloaded via terminal like miniconda, node, npm, Udacimak, etc. will be greatly appreciated it.

For Node, you can use nvm  to manage your Node js installed versions.
For the rest, you just need to learn on how to uninstall them by looking at their documentation 😄
Using Docker can also be a good idea to isolate the development environment from your local machine.

Thank you :)
And oh one more question...Will the index.html file still run without all other files?
Meaning, can I just keep the index.html file only and delete the other rendered files/folders?
I was looking to save space and since all the videos can be viewed via index.html, I thought this may be a good way to go.
Thank you :)

No we shouldn't delete any files in the rendered folders because they are the resources that the HTML file will look up when opening the web page.
Have fun! :smile:

Ahhh gotcha!
Thank YOU!

I have successfully added another feature to the Node package which allows you to use original Udacity youtube videos embedded in HTML files instead of downloading all the videos to your disk. (Data Science V3 nanodegree was reduced from 7+GB to somewhere near 100+MB. Will make a pull request soon.


Verifiable credentials libraries in Rust?

Problem
Want to continue to work in Rust, because that is the environment where the official didcomm-rs (DIDComm v2) implementation is being maintained. The problem is that there are no good Verifiable Credential-libraries in Rust, AFAIK. Please prove me wrong :pray:
What about didkit? - https://github.com/spruceid/didkit
The way I see it Didkit has 2 issues:

didkit is written in Rust, but does not provide a rust-library. Rust is not even mentioned for the future:

didkit is difficult to compose with didcomm-rs and did-kit, because it uses .jwk. And I don't currently have a way to transform my did:key to a jwk.
didkit requires making calls to a CLI - no direct rust function calls.

TODO

[ ] Find a way to transform did:key to a jwk, to enable easier integration between didkit and rust-code.

Related didkit-issue https://github.com/spruceid/didkit/issues/120

Using https://github.com/spruceid/ssi/


Path resolve error for translations

This is a copied issue from https://github.com/ipfs/go-ipfs/issues/2609. .
From @leochan007:

when access via 5001/webui got this output:
ERROR core/serve: Path Resolve error: no link named "webui-zh.json" under QmcnV8mXz9B4kuNEUymZ2mhqDLy2e76iMMk8SnmPDnxp6H gateway_handler.go:510

@dignifiedquire:

sounds like the shipped version doesn't serve/contain webui-zh.json

@thenain38:

@dignifiedquire Same for french (e.g. webui-fr.json)

@dignifiedquire:

You can see the list of supported locales here: https://github.com/ipfs/webui/tree/master/dist/locale if it's not in there it will fail (it will try for every locale and if it does not find it use the default english one)

Same for japanese (e.g. webui-ja.json)

Closing language related issues in favor of #675.


Allow overriding the API URIs

The Mixpanel support team have asked me to use the new "beta" version of the API to resolve some performance issues. However, since the base API URIs are coded in string literals, it's not possible to use an alternate URI. I've created this branch to allow you to override any of the three API URIs by passing them as part of the config parameters when creating a new instance.

Thanks for this PR! This seems like a rare edge case and I worry that it's going to create more confusion than benefit. I'm going to leave it open for now to see if anyone else wants this feature.

Mixpanel now offers EU data residency with separate API URLs, which makes needing to change them less of an edge case:
https://developer.mixpanel.com/reference/overview

Standard Server: api.mixpanel.com
EU Residency Server: api-eu.mixpanel.com

Thanks guys, this has been merged into 5.1.0.


Module 3 exercises [Emmanuel Elorm Delanyo]

WS2_M3E1_Template.docx

Well done, Emmanuel. You clearly grasped the material outlined in Module 3 and successfully applied it to these exercises. Thank you for your participation! Please be sure to fill out the post-Module survey before you begin the next Module.


Encoding failed error when Exporting to WebM

I have installed laravel-ffmpeg today on my Laravel 5.3.
First I was getting Encoding failed error when I was exporting the video to mp4:
FFMpeg::fromDisk('videos')
              ->open('steve_howe.mkv')
              ->export()
              ->inFormat(new FFMpeg\Format\Video\X264)
              ->save('short_steve.mp4')

After reading the topics here, I fixed it by adding libmp3lame audio codec and it worked:
FFMpeg::fromDisk('videos')
              ->open('steve_howe.mkv')
              ->export()
              ->inFormat(new FFMpeg\Format\Video\X264('libmp3lame'))
              ->save('short_steve.mp4')

However, I am at the moment unable to convert the video to WebM format. I have this at the moment:
FFMpeg::fromDisk('videos')
              ->open('steve_howe.mkv')
              ->export()
              ->inFormat(new FFMpeg\Format\Video\WebM)
              ->save('short_steve.webm')

I tried adding libvorbis codec to it but I still keep getting Encoding failed error. How can I convert the videos to WebM? Do I need to add any specific audio codec to make this work?
Thank you for your help.

Neel.

Ok, here is an update on this. I reinstalled ffmpeg again using the flags --with-libvpx --with-libvorbis. After this, the WebM videos are being converted. However, the quality is extremely poor. Its so poor that you can't even view the video and it just looks like a static video.
brew reinstall ffmpeg --with-libvpx --with-libvorbis -v

./configure --prefix=/usr/local/Cellar/ffmpeg/3.4.1 --enable-shared --enable-pthreads --enable-version3 --enable-hardcoded-tables --enable-avresample --cc=clang --host-cflags= --host-ldflags= --enable-gpl --enable-libmp3lame --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libxvid --enable-opencl --enable-videotoolbox --disable-lzma

FFMpeg::fromDisk('videos')
              ->open('steve_howe.mkv')
              ->export()
              ->inFormat(new FFMpeg\Format\Video\WebM)
              ->save('short_steve.webm')

Why am I having so much issues with WebM conversion? Any advise please?

I finally got it resolved. Installing just libvorbis was not enough. I also had to use libvpx-vp9 video codec instead of the default one. Without this, the video was very pixelated and green. I resolved it by doing this:
Reinstalled ffmpeg with these dependencies:
brew reinstall ffmpeg --with-fdk-aac --with-libass --with-sdl2 --with-x265 --with-freetype --with-libvorbis --with-libvpx --with-opus --with-theora

Used libvorbis and libvpx-vp9 codecs like this:
new \FFMpeg\Format\Video\WebM('libvorbis', 'libvpx-vp9')

Finally after the above updates, the videos are now converted to WebM properly.
Neel.


"Olteni" and "Perii Broșteni" are listed in the drop-down menu

Description:
"Olteni" and "Perii Broșteni" are listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Olteni" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Olteni, TELEORMAN (Olteni)" and "Comuna Olteni, TELEORMAN".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Type "Perii Broșteni" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Perii Broșteni, TELEORMAN (Olteni)".


Site is showing 404.

Describe the bug and the expected behavior

Conform version
v1.2.2
Steps to Reproduce the Bug or Issue
Just access the page & docs.
What browsers are you seeing the problem on?
No response
Screenshots or Videos
No response
Additional context
No response

It should be up now. I didn't notice the github token is just expired. Thanks for reporting!


General questions

I have been testing the combination of ws-tcp-relay and websocket-nats using a simple web client.
In my particular scenario, I'm using Docker to launch several ws-tcp-relay instances and connect them to a single NATS server. Then, I have a webapp that uses websocket-nats to connect to a ws-tcp-relay instance randomly and open a websocket session.
I have some general questions about ws-tcp-relay and I'm wondering if you can share some insight.

do you have any info on how many connections a single ws-tcp-relay instance can handle?

at what point does ws-tcp-relay relays the NATS connection?, when a client first connects to the relay? [via nats.connect('ws://localhost:4223')] or when the client first subscribes to a NATS topic?

does ws-tcp-relay keeps the relay session to NATS alive? or is this the responsibility of the client using websocket-nats?

I'm interested in evaluating the scalability of ws-tcp-relay in combination with websocket-nats and I'm wondering if you might have any suggestions or feedback.
Thanks,
A.

Unfortunately I haven't done any stress testing; I haven't yet tried to use this in a large scale project, so that's a bit of uncharted territory. This code is extremely simple though, so I imagine a single instance can handle however many concurrently open connections golang.org/x/net/websocket can handle.
Connections are opened as soon as a websocket opening handshake is received (this is handled by golang.org/x/net/websocket). ws-tcp-relay doesn't know anything about NATS since all it does is stream data between websockets and TCP. With regard to websocket-nats, this indeed happens during nats.connect(...), which internally opens the websocket.
Connections are kept open as long as both the websocket and TCP connections remain open. Either the client or server can terminate the connection at any time, so for usage with NATS, gnatsd should handle timeout and keep-alive. Otherwise, it appears that golang.org/x/net/websocket does not implement ping/pong messages, so it may be worth investigating replacing that with something like github.com/gorilla/websocket.

That all being said, your approach sounds like the right way to go, although I would do the "connect to a ws-tc-relay instance randomly" using a load balancer rather than in the client. I would be interested to see how you're setting up your Docker instances, it may be helpful for others to include a simple Dockerfile in the project. Also, would it be easier if I published binaries?

Hi @isobit, thank you for your prompt response. I'll be happy to do some stress testing ;-). Below are some Bash scripts I'm using to get Docker to launch 10 instances of the relay server:
First, you need to launch NATS using Docker:
#!/usr/bin/env bash

docker run -d --rm --name="nats-server" --memory=128M -p 4222:4222 -p 8222:8222 nats

#!/usr/bin/env bash

SERVERS=10
NATS_SERVER_IP="<IP_ADDRESS>"
RELAY_SERVER_PORT=6001
COUNT=0

while [ $(($COUNT < $SERVERS)) == 1 ];
do

  docker run -it --rm --name="nats-relay-$COUNT" --memory=128M -p $RELAY_SERVER_PORT:$RELAY_SERVER_PORT golang sh -c "go get github.com/joshglendenning/ws-tcp-relay && exec ws-tcp-relay -p $RELAY_SERVER_PORT $NATS_SERVER_IP:4222"

  echo -e "[$COUNT] - WS-TCP RELAY [$RELAY_SERVER_PORT] STARTED";

  COUNT=$(($COUNT + 1))
  RELAY_SERVER_PORT=$(($RELAY_SERVER_PORT + 1))

done

then you can use docker stats to see the containers running.
I'm in the process of documenting my setup and I will be happy to share it when ready.

Hey, I'm very interested in stress testing. please share your results
Thank you!

Here is the Docker image that I'm using for the testing. Unfortunately, I didn't get to do stress testing so far because I only have one application that connects via WebSocket.

Thank you for the update. I will try to make stress testing and will update.


could not reset ssh

A VMAccessForLinux extension with name enablevmaccess already exists. Updating it with your settings...
Deployment failed. Correlation ID: 65ff78cb-52ed-4021-b9da-2339fc00006f. VM has reported a failure when processing extension 'enablevmaccess'. Error message: "Enable failed: expected string or buffer".

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

ID: da03fed0-ae3d-5516-8312-8a79501bb29b
Version Independent ID: d1214d67-665f-0b7f-148e-1d23aac80725
Content: Troubleshoot SSH connection issues to an Azure VM
Content Source: articles/virtual-machines/troubleshooting/troubleshoot-ssh-connection.md
Service: virtual-machines-linux
GitHub Login: @genlin
Microsoft Alias: genli

I will close this out for now. If you need additional help please let me know and we can reopen and continue.


Option to validate templates using jinja2schema

https://github.com/aromanovich/jinja2schema can be used to determine all of the variables used in jinja2 templates .  It is far from complete.  There are enhancements in PRs, and forks , such as https://github.com/brkastner/jinja2schema and https://github.com/jayvdb/jinja2schema .
It can be used (for basic template) to verify that the templates only use variables which are supplied by statik, and that the assumed type of the jinja2 variable in the template is the same as the type of exposed by statik.
This option would fail for more complicated templates, as a result of its imperfections, but these will spur on development of jinja2schema . If jinja2schema raises an exception on a template, the exception needs to be caught , logged as a warning, and ignored, as it is likely the library that is at fault rather than the template.
It must be an optional feature so that it can be turned off whenever doesnt raise an exception but does incorrectly determine the type of a variable.

Here is a script I have been working on to add jinja schema support to moban
https://gitlab.com/jayvdb/mobans/commit/3eedcea1ec450599de08b9c3f7cb91739f2acef6


Fmt 10.1.1 update

Description
Update fmt dependency
Make a workaround for one fmt::format call.

Reopen https://github.com/oneapi-src/oneDAL/pull/2366 with small fix

/intelci: run

Its necessary for support icpx in bazel


Multi-Factor Authentication

Is your feature request related to a problem? Please describe.
Not a problem, but accounts would be more secure if they could opt-in to multi factor authentication. This is especially useful for stackers who either:

have a large balance
have attached wallets with large balances
own territories
have a well-known reputation

Describe the solution you'd like
I'd like to be able to configure MFA in the form of (at least) TOTP on my account. I think this could be used in the following ways:

Required on login after first factor is complete
Required when performing "high risk" actions like transferring a territory, or transacting over a certain (configurable?) threshold

I said ideally TOTP because MFA over SMS is bad, and email is only slightly better. It would be best to be able to use an open source authenticator app.
Describe alternatives you've considered
There's no real alternative that I can think of for things like territory ownership, but for balance concerns, you can link to an external wallet with budgets to help minimize risk.
Additional context
Discussed here

TOTPs would be great! I also like passkeys.


Performance improvements for visibility management flows

Some SM flows regarding visibility management require more optimal performance due to high parallel load. The PR introduces improvements that are later on reused in the internal SAP flows.

allow updating labels without updating the actual visibility via a new DB storage API - the reason for this being needed is that updating the actual visibility locks the row in the table until the transaction finishes. Certain transactions can take up to 30 seconds and they would slowly lock the whole visibility table row by row making any parallel visibility management requests work synchronously slowing down exponentially as more requests come (the last of five requests would take 5*x time to complete where x is average time a single request takes)
BULK insert and BULK delete labels during label management requests - this makes sure we don't execute multiple DB queries when multiple labels are changed
Remove GET label checks to see if label already exists or not and bake this logic in the actual INSERT label query
make use of the list without labels DB API to list visibilities without labels whenever possible

Coverage decreased (-0.5%) to 86.538% when pulling da1c65a91cb4860c0638376258ef02a7c15923e2 on fix-perf into 0622abb0757cb8b443b5929b79d42aa75c046ca2 on master.


Add parameter --scholar_start

--scholar_start is used to choose the starting page from witch start the search on scholar

Hello. My pull request #28 solves a similar problem. But I didn't add a new option.

Yes thank you, it was exactly it. The changes and fixes are now available with version 1.1.0


doc: close bold tag

doc: close bold tag

Everything after the implementation note of the "If statements" section
was accidentally bolded.

Thanks!


avoid the B031 errors reported by flake8

Avoid replacing the generator type with a list. Use a new variable for that.

fixes #1823

Checklist:

[ ] Add tests that demonstrate the correct behavior of the change. Tests should fail without the change.
[ ] Add or update relevant docs, in the docs folder and in code.
[ ] Add an entry in CHANGES.rst summarizing the change and linking to the issue.
[ ] Add .. versionchanged:: entries in any relevant code docs.
[x] Run pre-commit hooks and fix any issues.
[x] Run pytest and tox, no tests failed.

Thanks, but I already fixed it in the 3.1.x branch, just need to merge it forward. https://github.com/pallets/jinja/commit/be0bcb61f9e2918c85cbe0ccb04e1d7b36c68a70


Problem with SPFx and the compostability model in Yeoman Generator

Category

[ ] Question
[ ] Typo
[x] Bug
[ ] Additional article idea

Expected or Desired Behavior
SPFx generator should call its own sub-generators in compose with install try to evaluate global installed SPFx generator.
Observed Behavior
The SPFx community generator that comes with a dependency to SPFx 1.6 that should work independently from the installed generator. This dependency gets called correctly in the community generator if a lower version lets say 1.4.0 is installed on the client it always uses 1.4.0 instead of 1.6.0.
The problematical code was identified in the utility @microsoft/generator-sharepoint/lib/common/utilities.js JavaScript that composes with global generators instead of sub-generators.
// tslint:disable-next-line
function compose(generator, base, options) {
    base.composeWith(`@microsoft/sharepoint:${generator}`, options);
}

The code needs to be adapted to the following line to make a proper composeWith call.
// tslint:disable-next-line
function compose(generator, base, options) {
    base.composeWith(path.resolve(path.join(__dirname, '../generators/', generator)), options);
}

The changed code leed to another problem because the generator folder search folders for the generator are not defined in the Yeoman Documentation under folder tree is not referenced in the package.json.
The files entry should at least point to the following folder: lib/generators.
Steps to Reproduce
It is not that easy to have two generators installed on one machine so to reproduce this is recommended to install the community generator 1.0.2.
npm install -g<EMAIL_ADDRESS>
Run community generator with a different version installed as the main generator 1.5.0 at least for example.
npm install -g<EMAIL_ADDRESS>
Run a new project using the community generator and check the installed dependencies. This should all reference to 1.5.0 instead of 1.6.0.

FYI for others tracking this. We will have a one-to-one meeting with Stefan on checking the pending Yeoman issues he has found.

We've added this to the feedback.  Thanks,


add preallocated and indexed MSMs

See: https://github.com/lurk-lab/grumpkin-msm/pull/13
Replaces: https://github.com/lurk-lab/sppark/pull/2

Closing in favor of https://github.com/lurk-lab/arecibo/pull/374


Include relevant Push Notification Payload for iOS

Problem
Currently, push notifications only contain title and description.
Solution
We should put in all the relevant data connected to the push notifications on iOS in a format given by @nriedman. This format is mostly simply going to reflect how a UserMessage currently looks like in Firestore. We may also want to add images?
Additional context
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct and Contributing Guidelines

I put in the most important data already - if something is still missing, let me know or open a new issue.


DDX solvent support

Description
This PR adds support for the new DDX solvent model interface in Psi4 which should be slightly faster than PCM and scale better with molecule size. The other benefit is direct control over the solvent dielectric constant, which will be used in an upcoming charge model dataset.
Todos
Notable points that this PR has either accomplished or will accomplish.

[x] add ddx option validation
[x] add tests

Questions

[ ] Question1

Status

[x] Ready to go

Oh, please also update the release notes!


Name property is empty in cross-section of type CrossSectionComponent

          @nathanlukeIDEA The problem seems still to be there, but for sections of type xsi:type="CrossSectionComponent" (they are called "General cross-section" in IDEA). Despite assigning a specific name to the cross-section, the XML export contains the value "General" as name.

  <CrossSection xsi:type="CrossSectionComponent">
    <Id>1</Id>
    <Name>General</Name>
    <CrossSectionRotation>0</CrossSectionRotation>
    <IsInPrincipal>false</IsInPrincipal>
    <Components>
      ...
    </Components>
  </CrossSection>

Originally posted by @philip-smet in https://github.com/idea-statica/ideastatica-public/issues/379#issuecomment-1860699925

@nathanlukeIDEA  I thought it might be better to open a new issue for this problem...

Hi @philip-smet, I think this may be fixed now can you confirm, please?

Closing issue due to no response.


Respect user defined v4l2-ctl video capture format [VIDIOC_G_FMT]

I own a CA FLINT 4KP USB FullHD HDMI grabber attached to an odroid XU4 (Pi doesn't work) via USB3.
I've not been able to get hyperion-v4l2 working with this device properly when I want to forward the flatbuffer to another hyperion instance running on a Pi v2 which drives the LEDs, it would always crash shortly after it's started:
terminate called after throwing an instance of 'std::runtime_error'
what():  Unable to parse message
Aborted
To see what is being used I did this:
hyperion-v4l2 -d /dev/video2 -s 1 --screenshot
Signal detection informations
dimension after decimation: 1920 x 1080
So hyperion is reading the maximum resolution available (see bottom for a list of all resolutions), and that's just too much to handle it seems.
My solution to make it work:
1)
hack "libsrc/grabber/v4l2/V4L2Grabber.cpp" and rebuild:
// set the settings
max_width=720; // hack: force height/width
max_height=480; // hack: force height/width

v4l2-ctl -d /dev/video2 --set-fmt-video=width=720,height=480,pixelformat='YUYV' -p 30

hyperion-v4l2 -d /dev/video2 -a <IP_ADDRESS>:19400 -s 3
And the video is transmitted and show in "Live video" on the Pi.
Without this hack, I would have to use a much higher "-s" to shrink the video even more, but that leaves my odroid XU4 using 4 of it's 8 cores at 100% (so ~50% in total) - and the fan gets very loud then...
With this hack, the CPU utilization is ~ 12% in total and spread across 6 cores, the fan remains quiet.
It would be nice if there was a parameter so that I could just define the VIDIOC_G_FMT via v4l2-ctl and hyperion would use that information instead of going to the maximum resolution available.
Here is what the device supports:
v4l2-ctl --list-formats-ext --verbose -d /dev/video2
VIDIOC_QUERYCAP: ok
ioctl: VIDIOC_ENUM_FMT
Index       : 0
Type        : Video Capture
Pixel Format: 'MJPG' (compressed)
Name        : Motion-JPEG
Size: Discrete 720x480
Interval: Discrete 0.017s (60.000 fps)
Interval: Discrete 0.033s (30.000 fps)
Size: Discrete 1280x720
Interval: Discrete 0.017s (60.000 fps)
Interval: Discrete 0.033s (30.000 fps)
Size: Discrete 1920x1080
Interval: Discrete 0.017s (60.000 fps)
Interval: Discrete 0.033s (30.000 fps)
Index       : 1
Type        : Video Capture
Pixel Format: 'YUYV'
Name        : YUYV 4:2:2
	Size: Discrete 720x480
		Interval: Discrete 0.017s (60.000 fps)
		Interval: Discrete 0.033s (30.000 fps)
	Size: Discrete 1280x720
		Interval: Discrete 0.017s (60.000 fps)
		Interval: Discrete 0.033s (30.000 fps)
	Size: Discrete 1920x1080
		Interval: Discrete 0.017s (60.000 fps)
		Interval: Discrete 0.033s (30.000 fps)

Same Problem for me to, hyperion is using full HD resolution from the grabber which causing to much CPU power for the pi3.
Would be great to have a opportunity  to select the possible resolutions.

I am running hyperion.ng with following hardware
Rpi0 W
Leds: APA102
Grabber: EasyCap (534d:0021)
Everything works great except the pi's CPU is constantly 100%.
When I disable the grabber the CPU drops to 3-4%.
I know that the Grabber I have is not a recommended one but it actually works.
Is there a fix for this? please let me know!

should be fixed with #766


Infer gets confused between files with the same name

Infer version v1.0.0-12c582a69
macOS Big Sur 11.1 (20C69)
This happens when running Infer on the Teku project.
Infer reports over 20 THREAD_SAFETY_VIOLATIONs on a file named StatusLogger.java in the project. However, the line numbers make no sense; the file is 318 lines long, but the reports go up to line 411. And even in the cases where the numbers are plausible, the traces point to blank lines while mentioning events that obviously aren't happening there.
Interestingly, the project uses Log4j, which includes a file coincidentally named StatusLogger. The traces make sense when referred to this file.
One of the confused traces:
https://gist.github.com/hmijail/ca40439f6c8544a5b3c4e55ac98a0d2c
Teku's StatusLogger.java:
https://gist.github.com/hmijail/9e4a2573b18928080b27d12d44597e36
Log4j StatusLogger.java:
https://gist.github.com/hmijail/9faa3d2afcaff27df31ad10d2bec662b
In case it matters, I'm using an .inferconfig file with {"dump-duplicate-symbols": true}.
Let me know if more information is necessary.

This issue is still current as of today's Infer version (v1.0.0-63545b1e6)

This issue is still current as of today's Infer version (v1.0.0-63545b1e6)

Issue still current as of current commit (8b32da127eb001d604f506c3e8a4154d27996fde).
A further example of the issue has appeared: the project contains a file named SecretKey.java. Infer reports 6 thread safety issues in that file. But as before, the line numbers and traces in those issues make no sense.
There are 3 other SecretKey.java files in libraries used by the project, so they must be confusing Infer.

Thanks for the report. Source files are stored relative to the project root, eg in your first paste "infrastructure/logging/src/main/java/tech/pegasys/teku/infrastructure/logging/StatusLogger.java" so it's not obvious why this happens. One possibility would be that the files are captured with different project roots, eg if the build system did cd dir1/ && infer ... -- javac SecretKey.java then cd dir2/ && infer ... -- javac SecretKey.java but given the long prefix in your first example that seems very unlikely.
What commands do you use to run infer?

This happens no matter how I run infer; either with a plain infer run, with separate capture and analysis, with or without extra checkers.
But for completeness, my full command line right now is
./gradlew clean && $INFER_PATH/infer run -o $INFER_OUT_PATH -- ./gradlew installDist -Davt.disableErrorProne=true

(The installDist is to avoid the project from running its tests, and the -D is to disable ErrorProne, which messes up the CLI reported to Infer and causes it to error out - as reported in #1105)


Harvest jobs eventually failing during certificate/proxy check

Interesting case... the harvesting job fails most of the times during the authentication step [*]. I assume it cannot find my proxy in the X509_USER_PROXY env var, though it's there according to the condor.stdout logs.. Even more interesting, it works just fine with DQMHarvest workflows, but mostly fails in the other workflows that have harvesting enabled.
BTW, Matteo has just hit this issue in production as well.
[*]
INFO:root:HTTP Upload is about to start:
=> URL: https://cmsweb-testbed.cern.ch/dqm/dev;https://cmsweb.cern.ch/dqm/relval-test
=> Filename: /storage/local/data1/condor/execute/dir_3057657/glide_GVbWPk/execute/dir_3686180/job/WMTaskSpace/cmsRun1/DQM_V0001_R000202209__JetHT__CMSSW_7_2_0-RECODreHLT_TaskChain_LumiMask_multiRun_HG1705_Validation_TEST_Alan_v5-v11-202205-202209__DQMIO.root
INFO:root:HTTP POST upload arguments:
==> checksum: md5:bff80c3eafc583b07b48c926edb66aed
==> size: 63537411
ERROR:root:HTTP upload failed with response:
Problem unknown.
Error: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:662)>
Traceback: Traceback (most recent call last):
File "/storage/local/data1/condor/execute/dir_3057657/glide_GVbWPk/execute/dir_3686180/job/WMCore.zip/WMCore/WMSpec/Steps/Executors/DQMUpload.py", line 161, in httpPost
(headers, data) = self.upload(uploadURL, args, filename)
File "/storage/local/data1/condor/execute/dir_3057657/glide_GVbWPk/execute/dir_3686180/job/WMCore.zip/WMCore/WMSpec/Steps/Executors/DQMUpload.py", line 255, in upload
result = urllib2.build_opener(HTTPSCertAuthenticate()).open(datareq)
File "/cvmfs/cms.cern.ch/COMP/slc6_amd64_gcc493/external/python/2.7.13/lib/python2.7/urllib2.py", line 429, in open
response = self._open(req, data)
File "/cvmfs/cms.cern.ch/COMP/slc6_amd64_gcc493/external/python/2.7.13/lib/python2.7/urllib2.py", line 441, in _open
'default_open', req)
File "/cvmfs/cms.cern.ch/COMP/slc6_amd64_gcc493/external/python/2.7.13/lib/python2.7/urllib2.py", line 407, in _call_chain
result = func(*args)
File "/storage/local/data1/condor/execute/dir_3057657/glide_GVbWPk/execute/dir_3686180/job/WMCore.zip/WMCore/WMSpec/Steps/Executors/DQMUpload.py", line 241, in default_open
return self.do_open(HTTPSCertAuth, req)
File "/cvmfs/cms.cern.ch/COMP/slc6_amd64_gcc493/external/python/2.7.13/lib/python2.7/urllib2.py", line 1198, in do_open
raise URLError(err)
URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:662)>

 Harvest jobs eventually failing during certificate/proxy check

Hi,
any news about this issue? Seems its repeating itself for some urgent RelVals

@amaltaro would a plain DQMHarvest workflow succeed ?

I tried to reproduce this issue (with another DQM root file and CMSSW release) but with no success.
From my testbed tests, yes, DQMHarvest request type works just fine.
@vlimant is it failing for 100% of the automatic relval harvesting jobs? Are these harvesting jobs running at CERN or FNAL (apparently they only fail at FNAL...though it doesn't make much sense since the python interpreter+libraries are loaded from cvmfs...)

Hi,
as discussed in hypernews its not 100%. For AlCa validation few workflows failed, seems it was reproduced for one as it failed once they resubmitted it on friday.

@amaltaro can you try with the prod relval DQM and the dqmio dataset for which that has failed ? At least to get the files uploaded while you figure this out

Yes, it's reproducible but not interactively by me :( Just ran again one of the failing configurations and the same code and it just works fine.
Jean-Roch, are you asking me to create DQMHarvest workflows for those that failed? Can you point me to one small campaign? Should I assign it to the relval team or unified is going to pick that up? Anything especial?
Meanwhile, I'm going to run the same config at FNAL just to rule out one suspicious...

While pdmv has the handle to submit DQMHarvest workflows and notify Ops that they are in and should be taken care of in an Add-Hoc way, it seems that communication lines are broken and people sitting on blaming each others.
If you can create and assign to relval team these harvesting for
https://cmsweb.cern.ch/reqmgr2/fetch?rid=rverma_PR_newco_RelVal_276950_170428_191716_3771
=> /MET/CMSSW_8_0_27-2017_04_28_19_16_PRnewco_80X_dataRun2_2016LegacyRepro_v3-v1/DQMIO
https://cmsweb.cern.ch/reqmgr2/fetch?rid=rverma_PR_reference_RelVal_276950_170428_191705_6912
=> /MET/CMSSW_8_0_27-2017_04_28_19_16_PRref_80X_dataRun2_2016SeptRepro_v5-v1/DQMIO
that would help move things forward a bit.

or show @prozober the scripts

@prozober I have just updated this script:
https://github.com/amaltaro/scripts/blob/master/injectHarvest.py
and I also created DQMHarvest workflows for those 2 requests pointed by @vlimant
Request 'amaltaro_PR_newco_RelVal_276950_Harv_170504_115945_6835' successfully created.
Request 'amaltaro_PR_reference_RelVal_276950_Harv_170504_120126_6277' successfully created.
Can you please run a quick check on them and if everything is fine, assign it to the relval team?

The workflows were assigned to CERN, and relval team. Let's keep an eye on them.

The workflows succeeded and got announced.

@prozober  please reply back to the thread https://hypernews.cern.ch/HyperNews/CMS/get/relval/7417/1/2/2.html

@vkuznet as we discussed in the WMAgent meeting, indeed there were changes to the HTTPSConnection class and a few keyword args were deprecated (py 2.7.9) and it now requires a ssl context object to be passed (which holds the certificate credentials and further info).
As you suggested, I picked the DBS HTTPS handling code and added to WMCore, after a few adjustments it works fine in my interactive/local test, however it still fails when running an agent job in the grid.
I'm still investigating (and struggling to get access to the worker nodes). It may be that some environment var is screwing this up at the worker node...

Alan,
you may add debug printouts in your code too, e.g.
class HTTPSClientAuthHandler(urllib2.HTTPSHandler):
    def __init__(self, key=None, cert=None, level=0):
        urllib2.HTTPSHandler.__init__(self, debuglevel=level)

and for time being setup debuglevel to be non-zero all the time to debug the
problem. I would suggest that you dump env on worker node, add non-zero
debuglevel and run some job. Please also capture both stdout/stderr output
that we can see the message.
Also, please show how you create SSLContext, e.g.
context = ssl.SSLContext(ssl.PROTOCOL_TLS)
urllib2.urlopen(req, context=context)
that we'll check how request is open.
Valentin.
On  0, Alan Malta Rodrigues<EMAIL_ADDRESS>wrote:

@vkuznet as we discussed in the WMAgent meeting, indeed there were changes to the HTTPSConnection class and a few keyword args were deprecated (py 2.7.9) and it now requires a ssl context object to be passed (which holds the certificate credentials and further info).
As you suggested, I picked the DBS HTTPS handling code and added to WMCore, after a few adjustments it works fine in my interactive/local test, however it still fails when running an agent job in the grid.
I'm still investigating (and struggling to get access to the worker nodes). It may be that some environment var is screwing this up at the worker node...
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/dmwm/WMCore/issues/7821#issuecomment-299815475

Hi,
is there and ETA when this issue will be fixed? Currently for 910pre3 all workflows failed to upload DQM root files and this stops release validation. Alca validation was delayed when the files got re-uploaded.
If this issue is not resolved asap i would suggest to backport to previous python version.  As current situation does not allow for offline release validation to work.
Best regards,
Antanas Norkus

I forgot updating this issue, we've rolled back the runtime python version used by the relval agent. So it's again using 2.7.6 instead of 2.7.13 and harvesting should be working just fine now.
The real fix is still to come, maybe by tomorrow.

and are there any news on 910pre3 harvesting worflows finishing?
i see that all of them are still in assignment-approved status since yesterday.

Apparently CompOps is still deciding how to proceed here, I suggest you to get in touch with the PnR team.

@vkuznet I created a patch here #7844 which was working fine. However, today in my final tests I saw it failing again. I'm going to update it again to print the trusted CERN CAs, just in case.
According to the library documentation, it suggests not to create a context object with SSLContext(), but with the default method that sets up the most secure protocol/cyphers/etc. You can see the code yourself (I also added comments explaining the settings being used).
I think the real problem is that some worker nodes don't have the CERN CAs in their capath, which then fails to verify the server certificate. I'm going to check these CAs, but if that's the case, maybe we'll need to NOT verify the server certificate... which is not desired and secure, but...

I think the real problem is that some worker nodes don't have the CERN CAs in their capath, which then fails to verify the server certificate. I'm going to check these CAs, but if that's the case, maybe we'll need to NOT verify the server certificate... which is not desired and secure, but...

It very well may be the case, but I disagree with you sneaky proposal :)
Why not to install CAs on worker nodes and do this in a proper way, instead of
"usual" hacking way?

It does seem to be something that CERN IT should be interested in helping us with.  I could involve Kate (our contact), if you let me know.

I talked to Diego G. this afternoon and it seems this was a struggle in the past, where the working solution was skipping the server certificate verification (surprise surprise it only bugs us now :)).
Moreover, he told me the system default CA path is /etc/grid-security/certificates and ALL worker nodes should trust CERN CAs. So the default SSL settings point to a different location (maybe somewhere in the python libraries). Thus, I updated the patch to always load CAs from the path previously mentioned.
Initial tests are promising, I likely have to run a few more tests (a couple of other sites would be good) before we declare it solved ;)
Thanks, Liz, I hope it won't be needed.

@amaltaro can you please confirm whether this is fully fixed and pushed to the agents ?
There was a failure for one of the harvesting https://cms-logbook.cern.ch/elog/Workflow+processing/26486 created for one of the data reprocessing harvesting. That's probably before the fix was made. We need this deployed on all agents.


Add support for command line piping

Can we add functionality so that when installed globally with npm -g install ansi_up, we can pipe input output?
E.g.:
 ls -lah --color | ansi_up  > test.html

As seen in:

agnoster/ansi2html (node)
ralphbean/ansi2html (python)
ansi2html.sh (bash)

That would really make this module versatile.

@redsandro - that is an interesting suggestion and easy to add.

I am closing this issue. However, if someone really wants this and will submit a pull, I will gladly review it.


org.mortbay --> org.eclipse

We shouldn't need both the old org.mortbay.jetty and the new org.eclipse.jetty.
Upgrade to org.eclipse.jetty exclusively.

https://github.com/google/google-oauth-java-client/issues/130
Not immediately clear to me why we have to explicitly depend on org.mortbay.jetty simply because one of our dependencies does.


How add more  constraints to improve map precision in case of structured buildings

Hi:
Everyone, We find in case of structured scene, such as some buildings, maybe only some wall and corner or pillar, cartographer builds map looks like more thick and rough, so we want to utilize the information of building's  fixed straight wall and wall corner to restrain cartographer local scan-match or global optimization.How can I do, It's pleasure  that anyone can give me some advices.Thanks!

@larics , This problem has confused me two weeks, but I don't one good idea to resolve it so far. I find you are expert at cartographer , so could you give me some advices? Thanks advance!
I have tried one method is that add additional sensor type WALL_INFO , ros topic is /wall_info that uses laser scan data to extract wall line's scan data , then In SensorBridge call HandleLaserScan() like origin laser scan handle scan data, /wall_info and /scan has the same frame_id and timestamp, like sampling_ratio, I set wall_info_sampling_ratio in .lua file, but the mapping won't work well, How do you think this method?

@ojura I do this work intended to improve map precision , in detail, wall should be one straight line, but currently my map's edge look like  not smooth , like belows:

full map likes this:


Does VerneMQ supports federation ?

Hello, Our question is related clusters/regions and federation.
Real case example is that we have 3 kubernetes clusters of 3 VerneMQ containers each.
We would like them to be federated (replicate messages and their states across federation).
This means, when message is pushed to any of them, no matter to which region the client is subscribed, the message will be delivered.
for example, client is subscribed to west cluster, and message is published to east cluster.
The message being never consumed unless vernemq is federated.
Thank You :)

Thanks @xbugster for asking that question :)
:+1:  Federation... I like it.
I dream of this. Clusters of Clusters. Stars. C beams near the Tannhauser Gate. :star2:
[For now, VerneMQ only has bridging to somehow connect clusters]

Closing.


Accurate sizeof for pandas string[python] dtype

Follow-up to #9776

This looks good to me.  @jrbourbeau I defer to you though.


fix(demos): update feature-hub/react external declaration

@KingHenne Maybe we should take over the getPkgVersion function as a convenience function for integrators. It's best to integrate it somehow elegantly into createFeatureHub function...


Transaction fails to broadcast (Invalid Schnorr signature) when spending P2TR and P2WPKH.

Describe the bug
Building a transaction with two inputs (one P2TR utxo and one P2WPKH utxo), transaction successfully builds but error non-mandatory-script-verify-flag (Invalid Schnorr signature) happens when trying to broadcast.
To Reproduce
Using 4.1.0 release, test_sign_with_p2tr_and_p2wpkh test passes, but the built transaction fails to broadcast.
To prove that signing a tx with a single P2TR input works as expected, we wrote test_sign_with_p2tr_only. That test passes, and the resulting transaction was broadcasted successfully.
import WalletCore
import XCTest

final class Tests: XCTestCase {
    func test_sign_with_p2tr_and_p2wpkh() throws {
        // TestNet3 Data

        let p2trReceiveAddress0 = "tb1pcm7lhn5g6c4ueefe9kfvxgvv8xgaqrw9a80tvewn2gesdwjaeqfswarlgw"
        let p2trTxId = "9e85eb060fd9ac650fe0ae97a0f7940a8fdefe094d9f51335891727d70d380e7"
        let p2trValue: Int64 = 889
        let p2trIndex: UInt32 = 0
        let p2tr_pk_str = "ba04e058c795e864fc07199ba36178708b4374b8449db298b43e4d39ba78e86f"

        let p2wpkhReceiveAddress0 = "tb1qal5xl77a7d9vtaafda960lcxexn3uw9fqpdds5"
        let p2wpkhTxId = "902f0828ffcd8f35fe3f4903bd0a871c429cb5685b7a74cf262287f590ef40d2"
        let p2wpkhValue: Int64 = 1_100
        let p2wpkhIndex: UInt32 = 2
        let p2wpkh_pk_str = "1ec2a0f68e84edf0a6811dc2d35cf366bb495cf2475dbdf7a0545aab54864b22"

        // P2TR UTXO

        let p2trPrivateKeyData = Data(hexString: p2tr_pk_str)!
        let p2trPrivateKey = PrivateKey(data: p2trPrivateKeyData)!
        let p2trPublicKey = p2trPrivateKey.getPublicKeySecp256k1(compressed: false)
        let p2trUtxo = BitcoinV2Input.with {
            $0.outPoint = BitcoinV2OutPoint.with {
                $0.hash = Data.reverse(hexString: p2trTxId)
                $0.vout = p2trIndex
            }
            $0.value = p2trValue
            $0.sighashType = BitcoinSigHashType.all.rawValue
            $0.scriptBuilder = .with { $0.p2TrKeyPath = p2trPublicKey.data }
        }

        // P2WPKH UTXO

        let p2wpkhPrivateKeyData = Data(hexString: p2wpkh_pk_str)!
        let p2wpkhPrivateKey = PrivateKey(data: p2wpkhPrivateKeyData)!
        let p2wpkhPublicKey = p2wpkhPrivateKey.getPublicKeySecp256k1(compressed: false)
        let p2wpkhUtxo = BitcoinV2Input.with {
            $0.outPoint = BitcoinV2OutPoint.with {
                $0.hash = Data.reverse(hexString: p2wpkhTxId)
                $0.vout = p2wpkhIndex
            }
            $0.value = p2wpkhValue
            $0.sighashType = BitcoinSigHashType.all.rawValue
            $0.scriptBuilder = .with { $0.p2Wpkh = .with { $0.pubkey = p2wpkhPublicKey.data } }
        }

        let out0 = BitcoinV2Output.with {
            $0.value = p2trValue
            $0.toAddress = p2trReceiveAddress0
        }

        let changeOutput = BitcoinV2Output.with {
            $0.value = 1_100 - 210
            $0.toAddress = p2wpkhReceiveAddress0
        }

        let signingInput = BitcoinV2SigningInput.with {
            $0.version = .v2
            $0.privateKeys = [p2trPrivateKeyData, p2wpkhPrivateKeyData]
            $0.inputs = [p2trUtxo, p2wpkhUtxo]
            $0.outputs = [out0, changeOutput]
            $0.inputSelector = .useAll
            $0.chainInfo = BitcoinV2ChainInfo.with {
                $0.p2PkhPrefix = 0
                $0.p2ShPrefix = 5
            }
            $0.dangerousUseFixedSchnorrRng = false
            $0.fixedDustThreshold = 546
        }

        let legacySigningInput = BitcoinSigningInput.with { $0.signingV2 = signingInput }
        let output: BitcoinSigningOutput = AnySigner.sign(input: legacySigningInput, coin: .bitcoin)
        XCTAssertEqual(output.error, .ok)

        let outputV2 = output.signingResultV2
        print(outputV2.encoded.hexString)
        XCTAssertEqual(outputV2.error, .ok)
        /*
         encoded:
<PHONE_NUMBER>0101c4320fa80886ec307e36be4f866e2728c6a85d6e42f87503afea37108ebe91bd0000000000ffffffff011603000000000000225120c6fdfbce88d62bcce5392d92c3218c3991d00dc5e9deb665d3523306ba5dc813014081b692f9224e8d2e934bc497360957efb7c3b6bf13514a0f1acc666a4d101ba16f3f35cedc8b43a5ab45fa362d459b53b5d182695784e10090203bd5d34af55800000000
         */
    }

    func test_sign_with_p2tr_only() throws {
        // TestNet3 Data

        let p2trReceiveAddress0 = "tb1pcm7lhn5g6c4ueefe9kfvxgvv8xgaqrw9a80tvewn2gesdwjaeqfswarlgw"
        let p2trTxId = "bd91be8e1037eaaf0375f8426e5da8c628276e864fbe367e30ec8608a80f32c4"
        let p2trValue: Int64 = 1_000
        let p2trIndex: UInt32 = 0
        let p2tr_pk_str = "ba04e058c795e864fc07199ba36178708b4374b8449db298b43e4d39ba78e86f"

        // P2TR UTXO

        let p2trPrivateKeyData = Data(hexString: p2tr_pk_str)!
        let p2trPrivateKey = PrivateKey(data: p2trPrivateKeyData)!
        let p2trPublicKey = p2trPrivateKey.getPublicKeySecp256k1(compressed: false)
        let p2trUtxo = BitcoinV2Input.with {
            $0.outPoint = BitcoinV2OutPoint.with {
                $0.hash = Data.reverse(hexString: p2trTxId)
                $0.vout = p2trIndex
            }
            $0.value = p2trValue
            $0.sighashType = BitcoinSigHashType.all.rawValue
            $0.scriptBuilder = .with { $0.p2TrKeyPath = p2trPublicKey.data }
        }

        let out0 = BitcoinV2Output.with {
            $0.value = 1_000 - 210
            $0.toAddress = p2trReceiveAddress0
        }

        let signingInput = BitcoinV2SigningInput.with {
            $0.version = .v2
            $0.privateKeys = [p2trPrivateKeyData]
            $0.inputs = [p2trUtxo]
            $0.outputs = [out0]
            $0.inputSelector = .useAll
            $0.chainInfo = BitcoinV2ChainInfo.with {
                $0.p2PkhPrefix = 0
                $0.p2ShPrefix = 5
            }
            $0.dangerousUseFixedSchnorrRng = false
            $0.fixedDustThreshold = 546
        }

        let legacySigningInput = BitcoinSigningInput.with { $0.signingV2 = signingInput }
        let output: BitcoinSigningOutput = AnySigner.sign(input: legacySigningInput, coin: .bitcoin)
        XCTAssertEqual(output.error, .ok)

        let outputV2 = output.signingResultV2
        print(outputV2.encoded.hexString)
        XCTAssertEqual(outputV2.error, .ok)
        /*
         encoded:
<PHONE_NUMBER>0101c4320fa80886ec307e36be4f866e2728c6a85d6e42f87503afea37108ebe91bd0000000000ffffffff017903000000000000225120c6fdfbce88d62bcce5392d92c3218c3991d00dc5e9deb665d3523306ba5dc8130140685522251f628c5ea05e83380d5d64611649e294bbeb692587cf5cd8b573ab78a49f492fa7a3e1bf74817bafaa8ba39bb1d41eca08bae4314b9e28a2ac300cbe00000000
         hash:
         9e85eb060fd9ac650fe0ae97a0f7940a8fdefe094d9f51335891727d70d380e7
         */
    }
}

Expected behavior
Transaction is broadcasted successfully.
Additional context
This unit test runs on TestNet3, but the same issue happens on mainnet.
Broadcaster: https://mempool.space/testnet/tx/push
Note that if two P2TR inputs are used, transaction can be broadcasted successfully.

This issue has been preview on the Pull Requests. To resolve,
Contact the dAppNode page to initiate a chat with the live agent on the chat button to get more information about your request via dAppNode
@paulo-bc

Hi @paulo-bc, thank you for opening the issue. Could you please advise do you tweak the p2tr_pk_str private key? In WalletCore, we take original ECDSA/Schnorr private keys, and tweak them ourselves.

Hi @satoshiotomakan, I have not tweaked the p2tr_pk_str private key, it is the standard one for the m/86'/1'/0'/0/0 derivation.
Do you mean I have to tweak it myself and then use the result in BitcoinV2SigningInput.with, or that BitcoinV2SigningInput.with will already tweak it?

Hi @paulo-bc, thank you for the giving the context. No, the private key has to be not tweaked, so your code looks good. I'll try to reproduce the same problem today and will be right back

Hi @paulo-bc, the I fixed the issue at the PR https://github.com/trustwallet/wallet-core/pull/3979


parsing metadata should catch ENOENT

Completed scanning all COBOL files in workspace              (77841.00ms)
Error:processAllFilesInWorkspaces/1
Error: ENOENT: no such file or directory, scandir '/home/me/test/src/typo'
	at Object.readdirSync (fs.js:795:3)
	at Object.fs.readdirSync (electron/js2c/asar.js:605:39)
	at Object.fs.readdirSync (electron/js2c/asar.js:605:39)
	at Function.processAllFilesDirectory (/home/me/.vscode-oss/extensions/bitlang.cobol-6.5.18/out/vscobolquickparse.js:109:29)
	at Function.processAllFilesInWorkspaces (/home/me/.vscode-oss/extensions/bitlang.cobol-6.5.18/out/vscobolquickparse.js:86:43)
	at /home/me/.vscode-oss/extensions/bitlang.cobol-6.5.18/out/extension.js:411:41
	at new Promise (<anonymous>)
	at /home/me/.vscode-oss/extensions/bitlang.cobol-6.5.18/out/extension.js:410:16
	at _executeContributedCommand (/usr/share/codium/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:631:163)
	at _.$executeContributedCommand (/usr/share/codium/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:631:538)
	at m._doInvokeHandler (/usr/share/codium/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:801:683)
	at m._invokeHandler (/usr/share/codium/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:801:375)
	at m._receiveRequest (/usr/share/codium/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:800:14)
	at m._receiveOneMessage (/usr/share/codium/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:798:832)
	at /usr/share/codium/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:797:34
	at l.fire (/usr/share/codium/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:45:801)
	at v.fire (/usr/share/codium/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:235:849)
	at /usr/share/codium/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:975:744
	at l.fire (/usr/share/codium/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:45:801)
	at v.fire (/usr/share/codium/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:235:849)
	at t.PersistentProtocol._receiveMessage (/usr/share/codium/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:240:276)
	at /usr/share/codium/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:237:357
	at l.fire (/usr/share/codium/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:45:801)
	at p.acceptChunk (/usr/share/codium/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:233:393)
	at /usr/share/codium/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:232:753
	at Socket.t (/usr/share/codium/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:241:826)
	at Socket.emit (events.js:203:13)
	at addChunk (_stream_readable.js:295:12)
	at readableAddChunk (_stream_readable.js:276:11)
	at Socket.Readable.push (_stream_readable.js:210:10)
	at Pipe.onStreamRead (internal/stream_base_commons.js:166:17)
Completed scanning all COBOL files in workspace              (1309.00ms)

It does catch the exception and for diag purposes it shows it, thus allowing you to correct your configuration issue.

It is good that the error is catched, I suggest to not output the stacktrace and instead "this looks like an extension error" the point of "hey, I had a typo" is easier to get.

@spgennard Can we have an error message without the stack trace? Especially when there are multiple ones it gets messy fast (and currently I have multiple ones on purpose - one set contains absolute paths for "windows" the other for "linux" + the always working "main" set that uses relative paths.


Custom variables don't interpolate into panel titles

I've got a few panels that are using both query and custom variables in their title. The query variables always interpolate correctly, but the custom variables do not. I've confirmed it has nothing to do with the values (if I switch a query variable to a custom variable with the same value, it no longer interpolates into the panel title).
An example of a panel:
new VizPanel({
    pluginId: 'barchart',
    $data: getQueryRunner(metrics),
    title: 'Response latency by phase: $probe ⮕ $job / $instance',  <= these three are a mix of custom and query variables
    ...

How the variables are set up:
 const probe = new QueryVariable({
    includeAll: true,
    allValue: '.*',
    defaultToAll: true,
    isMulti: true,
    name: 'probe',
    query: `label_values(sm_check_info{check_name="${checkType}"},probe)`,
    refresh: VariableRefresh.onDashboardLoad,
    datasource: metrics,
  });

   const job = new CustomVariable({
      name: 'job',
      value: checks[0].job,                <= this value is a string
      hide: VariableHide.hideVariable,
   });
   const instance = new CustomVariable({
      name: 'instance',
      value: checks[0].target,                 <= this value is a string
      hide: VariableHide.hideVariable,
   });

@rdubrock variables have a value and text representation (think of them as id and display text), your only setting the value not the text representation. And in panel titles we use the text representation .
Possible PR to help with this scenario, but not sure it's the right thing
https://github.com/grafana/scenes/pull/591


Notification: i suggest a feature to keep open the notification when mouse hovered.

Suggest

i suggest a feature to keep open the notification when mouse hovered :)
Similarly there is primeVue's no-hover-pause option. (link)
if no-hover-pause option sets to true, pause a timeout when the mouse hovers the Notification.

(Video: The first notification will close after a certain period of time. The second notification remains open when the mouse is hovered over it.)
https://github.com/indielayer/ui/assets/37934668/e48644ce-bcbe-4884-b704-a86c8729a4cb

Thanks @KumJungMin, added here: https://github.com/indielayer/ui/commit/b840ba7fabe277935bfed71191ebf967bce48fa7


Sources: missing localizations

Describe the bug
There are hard-coded strings in the sources page.
To Reproduce
Steps to reproduce the behavior:

Go to the 'sources' page
See error

Expected behavior
All strings, including aria labels, need to be added to our en.json file for localization.
Screenshots
sourceSettings/filterToolbar.tsx

sourceSettings/sourceSettings.tsx

I'm probably missing something but I can't find where I missed localization in the above pictures.

It's the English strings (e.g., Add Source), and aria labels (e.g., select property for use for filtering).


freeze --version

Can  --version flag be added to the freeze command, to allow for better dependency checks and installation?

Thanks so much for the issue @DannyBen, definitely should have added this to begin with for easier debugging. This is now fixed by #69!


Add extra error checking around upgrade_to_8

Fix #325.
@ryansanford I tested moving from bali 3.1 to this commit without any issue, please test yourself to confirm.

LGTM

Confirmed internally that latest update fixes the bad state, and upgrades from a good state work as well. Thanks @nagem ! I'm merging.


Lxc issue #7423 -> Add more flags or filters to lxc list

Hello,
this branch contains the changes to the lxc list command to support additional filter flags/shorthands as suggested in issue #7423. Sry for the messy branch in general.
thank you : )
Signed-off-by: Sascha Bast<EMAIL_ADDRESS>

This pull request didn't trigger Jenkins as its author isn't in the whitelist.
An organization member must perform one of the following:

To have this branch tested by Jenkins, use the "ok to test" command.
To have a one time test done, use the "test this please" command.

Those commands are simple Github comments of the format: "jenkins: COMMAND"

Ok, so here are a few thoughts:

As far as I can see you implemented flags for r, s, f, con and vm. According to this https://github.com/lxc/lxd/issues/7423#issuecomment-695125151 @stgraber would be against that I guess.
So I assume this might be removed, but you can wait for the Teams comment on this.
I assume you also implemented the concept mentioned here (https://github.com/lxc/lxd/issues/7423#issuecomment-694531799) ? Sry as I am no programmer I can't be sure, but I see things like this:
 func matchByStatus(cInfo *api.Instance, query string) bool {
return strings.ToLower(cInfo.Status) == strings.ToLower(query)
}
So if thats the case, that would be very useful indeed :+1:.
Some minor things:

the commits titles should probably be something like lxc/list: say what you change in one sentence instead of just lxc/list: Change; followed by a more detailed description whenever necessary.
The Pull request title should probably be something like: lxc/list: Add more flags and filters.
there are some minor spelling mistakes, I might mark them in the code review.

Indeed, I'd prefer not to introduce a variety of new flags but instead focus on filtering as described in https://github.com/lxc/lxd/issues/7423#issuecomment-694531799

@stgraber I was wondering if it would be useful to create single letters for the filters. [ type,t; status,s; architecture,a; name,n; location,l; ] would be possible. In the daily use I would find this probably practical.

Other than that tiny nit I mentioned and having the functions be part of the cmdList struct, this is looking very good.
So with that fixed and a bit of a rebase so we end up with just two commits:

lxc/list: Add more instance filters
i18n: Update translation templates

And we'll be good to merge this, thanks!

Shure, i will fix the remaining tasks. Unfortunately i will not be able to do so before the beginning of next week.

@stgraber hi, I have completed the remaining tasks and squashed the commits into two commits. I hope that was the kind of rebasing you meant. If not let me know :)

@my5t3ry  It seems that did not work the way it is intended.
There are now 19 commits, though it should be only 2.

@toby63 thanks, i think  it now looks better. did not get it to work this way without force pushing it, and it feelt wrong doing so. i hope this now works for you guys :)

jenkins: test this please

@toby63 thanks, i think it now looks better. did not get it to work this way without force pushing it, and it feelt wrong doing so. i hope this now works for you guys :)

Thx.
OT: It's ok to force-push, it's the only way to update branches with a new HEAD. But I understand that it feels a bit wrong to do so :slightly_smiling_face:.

jenkins: test this please

jenkins: test this please

Thanks!
I just had to do a few tiny fixups to make go vet and golint happy, now all good!

@stgraber i'm glad it finally got merged. I'm going to take work on issue 7237 now, is the correct way to get this right to run go vet; golint ./... from folders with changed files?

Yeah, usually you'll want to run some version of:

gofmt -s -w ./...
go vet ./...
golint on any package you touched, not all are clean currently so recursive runs don't work with this one yet


Implement Sankey plots

Description
Shankey plots are very useful in showing flows such as in : patient distribution, cash allocation, marketing channel attribution.
They can be a useful visualization of unsupervised mapping, shapley values analysis etc

This is my favorite plot and I would love to see a native solution, especially for theme reasons, but in the mean time you can use the plotly versions like so:
import plotly.graph_objects as go
from plotly import io as pio

from h2o_wave import main, app, Q, ui

fig = go.Figure(
    data=[
        go.Sankey(
            node=dict(
                pad=15,
                thickness=20,
                line=dict(color="black", width=0.5),
                label=["A1", "A2", "B1", "B2", "C1", "D1", "D2"],
                color="blue",
            ),
            link=dict(
                source=[0, 1, 0, 2, 3, 3, 4],
                target=[2, 3, 3, 4, 4, 6, 5],
                value=[8, 4, 2, 8, 4, 2, 6],
            ),
        )
    ]
)

fig.update_layout(title_text="Basic Sankey Diagram", font_size=10)

html = pio.to_html(fig, validate=False, include_plotlyjs="cdn", config={"scrollZoom": False, "displayModeBar": None})

@app('/')
async def serve(q: Q):
    q.page["sankey"] = ui.frame_card(
        box="1 1 -1 -1",
        title="",
        content=html
    )
    await q.page.save()