gitleaks: 7.2.2 -> 7.3.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/zricethezav/gitleaks/releases.
meta.description for gitleaks is: "Scan git repos (or files) for secrets"
meta.homepage for gitleaks is: "https://github.com/zricethezav/gitleaks"
meta.changelog for gitleaks is: ""
Updates performed

Golang 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 7.3.0 with grep in /nix/store/7pgsk1hzamlybbdyjykii7sxz4fhhzjm-gitleaks-7.3.0

directory tree listing: https://gist.github.com/8b110ee7c0894018bb9cfb0534efd28f

du listing: https://gist.github.com/b0cc57e8acf734b3f33d7b684ff4cf58

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

4 total rebuild path(s)

1 package rebuild(s)

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

First fifty rebuilds by attrpath
gitleaks

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/7pgsk1hzamlybbdyjykii7sxz4fhhzjm-gitleaks-7.3.0 \
  --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 gitleaks https://github.com/r-ryantm/nixpkgs/archive/81a6eb97ec66ebc1ee573f9e01640bf0fc29b135.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/7pgsk1hzamlybbdyjykii7sxz4fhhzjm-gitleaks-7.3.0
ls -la /nix/store/7pgsk1hzamlybbdyjykii7sxz4fhhzjm-gitleaks-7.3.0/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:

gitleaks

Maintainer pings
cc @fabaff @kalbasit for testing.

Result of nixpkgs-review pr 115844 run on x86_64-linux 1

1 package built:

gitleaks


failed with shopify

the tool got incorrect favicon link from shopify.com
-> https://www.shopify.com/favicon.ico
correct one is https://cdn.shopify.com/static/shopify-favicon.png

The favicon is correctly detected.
If you open your web console, you will see this warning with this message: CORS blocking favicon access of https://cdn.shopify.com/static/shopify-favicon.png. Sending it to background
The problem is that as we fetch the image from "https://www.shopify.com", but the image is hosted on the subdomain "cdn.shopify.com". Consequently, CORS are blocking the request because it's not on the same site.
For the moment I didn't found any viable solution to access those favicons blocked by CORS without infringing on the privacy of users of the extension (going through a proxy to fetch the favicon would enable the owner of the proxy to monitor the websites you are visiting).
If you have some suggestions, don't hesitate.

A new issue will be created soon to resolve this problem, closing this issue.


system-upgrade-controller: bump to v0.7.0

Fixes problem with system-upgrade-controller and FQDN https://github.com/rancher/system-upgrade-controller/issues/110

Features and Enhancements
Bump wrangler to v0.8
Support Env and EnvFrom entries on Plans
Bug Fixes
Fix for incorrect job names for nodes with FQDN

Now as a draft as v0.7.0 is a pre-release

@voima-eetu thanks for getting this on my radar today as I hope to be cutting releases soon-ish. Is there a particular reason this is in draft and not ready to merge?

@dweomer Thanks! Only reason why it was marked as a draft was because system-upgrade-controller v0.7.0 was released as a 'Pre-release'.


Provide username in log data on auth failure

What does this PR do?

This PR adds the username in the log data, if present, on auth failure for middlewares basic auth and digest auth.
Motivation

fixes #6722
Providing the user on auth failure in the access log is an expected behavior for some tools, at least fail2ban.
More

[x] Added/updated tests
[ ] ~Added/updated documentation~

Additional Notes

Nice thanks!


Message is included in the block even if PayForData transaction fails

Even if submit PFD returns error (signature verification error), message/data is included in the block.
Example:
Failed TX: https://celestia.explorers.guru/transaction/F7DABD37A745A32E63BEBADDEACE62FE9D37D521457B64B973C4F956D463497A
Block with data: https://rpc-mamaki.pops.one/block?height=11482
May be related to: #452 (see: https://github.com/celestiaorg/celestia-app/issues/452#issuecomment-1140052535)

due to tendermint's deferred execution mechanism, there isn't actually a way avoid this.

we might want to consider also checking the PfD signatures when we call CheckTx on a wirePfD, to make it more difficult for this to happen.

closing for now @tzdybal but pls feel free to continue the conversation or reopen if you see fit.


Add Bitcoin Cash to Any Signer

Next time start from a new branch off recent master :)   (lots of unrelated commits are shown in the history of this PR)

Clean pr please


Improve documentation about usage of variables?

I am new to tower-cli (I wanted to use it inside a python-script) and really had some struggle to understand how I am able to add variables e.g. when creating a new host.
I ended up searching through the source-code of this repo to find examples where variables get used and finally was successful by adding them to a host.
Afterwards I was asking myself if I was the only one who did not know how to declare variables e.g. when creating hosts because there was no information about this topic in the documentation? I think everything else of the API is really intuitive or described inside of the documentation, but adding variables is not.
I am willing to add this additional documentation infomation as a PR, but only if you think that it is a good idea. I probably would add it under "API reference/introduction".

This looks like it's the same root issue as 564, and it really comes down to the fact that tower-cli has some variables processing to help, but that was not applied to host variables. It should be much easier and more self-documenting if we just change the type of that field. The concerns are not breaking people using the command in its existing form, and if we might break the call pattern of the tower_host module in Ansible. Still, I think this should be done and it's pretty minor to accomplish.


[MXNET-703]  Remove race condition in onnx build

Description
This removes a race condition in onnx build.  This is a work around, the correct fix should be made to the onnx repo.
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[x] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[x] Changes are complete (i.e. I finished coding on this PR)
[x] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[x] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[x] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Comments

This commit decreases the number of workers during the onnx buil but this should have minimal impact on overall build times.  Building the onnx native lib only takes a few seconds.

@nswamy Tested this with 6 test builds.  It seems to have gotten rid of the build issues.  If CI passes I'd appreciate a merge to master.  If we are still seeing failures I'll disable the TRT stage to unblock devs.

I don't have the context on this, I saw it fail yesterday on one of the PR
builds(can't recall which one), What changes have you made to fix the
flakiness, is there another PR?
On Fri, Aug 17, 2018 at 11:06 AM Kellen Sunderland<EMAIL_ADDRESS>wrote:

@nswamy https://github.com/nswamy Tested this with 6 test builds. It
seems to have gotten rid of the build issues. If CI passes I'd appreciate a
merge to master. If we are still seeing failures I'll disable the TRT stage
to unblock devs.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/incubator-mxnet/pull/12225#issuecomment-413945520,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABJxQmfTCEVQ2wwIeoVUCnC_6Vpr7Jr5ks5uRwYygaJpZM4WB5KJ
.

I meant to ask how does this change fix the issue?

For the record: Tracked at https://github.com/onnx/onnx/issues/933


Page seems to imply that EF Core 5 has not been released

Confusing - this whole section (High Level Plan and What's New) seems to imply that EF Core 5 has not been released yet, but it was released on Nov 10.

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

ID: 32360b50-1129-b3d2-2d71-c6b89cd9f2c6
Version Independent ID: 4f18f8dc-5cd5-cb37-0f59-fb1767609b2b
Content: What's New in EF Core 5.0
Content Source: entity-framework/core/what-is-new/ef-core-5.0/whatsnew.md
Product: entity-framework
Technology: entity-framework-core
GitHub Login: @ajcvickers
Microsoft Alias: avickers

...Or maybe the problem is that this is a roadmap page, but I'm trying to figure out how to upgrade to EF Core 5. It wasn't clear that this is part of a roadmap.

#2904 should help here, we should also decide at some point what to do with the high-level plan page.
/cc @ajcvickers


Installs version from active environment instead of provided version

Reproduction Case
pyenv install 3.7.4

pyenv install 3.7.9

pyenv-venv install 3.7.9 env379

pyenv-venv activate env379

pyenv-venv install 3.7.4 env374

The output will say
Installing env: test374 using Python v3.7.4
But if you look in the directory and start the python.exe you will see that its the wrong version (3.7.9 in this case)

@Jerakin Hey, I added a fix for this to a testing branch. Can you download the updated bin files and copy the files to your pyenv-venv installation directory's bin and check if this fixes the issue for you?
https://github.com/pyenv-win/pyenv-win-venv/tree/issue8_fix


Will the jQuery dependency be dropped

@techdavid said in an older, now closed , that the next version von BS will drop the jQuery dependency.
For systems that require very fast loading websites this might be a nice feature, to not having to load jQuery first (if it's not cached), but only the really needed JS.
What do you think? Is it good to drop that dependency? Will it happen?

it's already in progress :)
https://github.com/twbs/bootstrap/tree/v4-without-jquery

Just chiming in; while waiting for v4-without-jquery to be completed, you might be able to use https://github.com/thednp/bootstrap.native to drop jQuery + popper.js dependencies.

@ryanelian I use this in a production environment.  It works great!  Plus you can custom build with their webpack-loader.


Correctly report CodeQL version when using cache

Merge / deployment checklist
A one-line change to correctly update the version reported to our telemetry when we used a cached CodeQL bundle.
Open questions (cc @henrymercer):

I am unsure how to test this without waiting for the next CodeQL release and monitoring our telemetry during the period of time when the older cached version is used.

I'm also not sure if this warrants a changelog post because the only visible changes are to internal users viewing our telemetry.

[x] Confirm this change is backwards compatible with existing workflows.

[x] Confirm the readme has been updated if necessary.

[ ] Confirm the changelog has been updated if necessary.

I am unsure how to test this without waiting for the next CodeQL release and monitoring our telemetry during the period of time when the older cached version is used.

There are some unit tests that call setupCodeQL, but use it to configure CodeQL without checking the return value. See if you can extend those, or write simpler new ones, so that they check the return value from this function, while mocking different conditions of the toolcache/GitHub API/user config.

I'm also not sure if this warrants a changelog post because the only visible changes are to internal users viewing our telemetry.

Nothing user-facing, so indeed no change note.

I am unsure how to test this without waiting for the next CodeQL release and monitoring our telemetry during the period of time when the older cached version is used.

There are some unit tests that call setupCodeQL, but use it to configure CodeQL without checking the return value. See if you can extend those, or write simpler new ones, so that they check the toolsVersion in the return value from this function, while mocking different conditions of the toolcache/GitHub API/user config.

I'm also not sure if this warrants a changelog post because the only visible changes are to internal users viewing our telemetry.

Nothing user-facing, so indeed no change note.

I am unsure how to test this without waiting for the next CodeQL release and monitoring our telemetry during the period of time when the older cached version is used.

I see some unit tests that call setupCodeQL, but use it to configure CodeQL without checking the return value. See if you can extend those, or write simpler new ones, so that they check the toolsVersion in the return value from this function, while mocking different conditions of the toolcache/GitHub API/user config. By mocking these conditions and checking the toolsVersion, you'll be able to simulate what gets reported to the telemetry and make sure we are handling the various possible cases, without having to actually reach that situation during a real workflow run.

I'm also not sure if this warrants a changelog post because the only visible changes are to internal users viewing our telemetry.

Nothing user-facing, so indeed no change note.

You could test this by running the the action in a testing repo using this branch. But, the changes look reasonable to me. I suggest we merge and then check if it is working.


Update mrtk-porting-guide.md

Docs Build status updates of commit 564cf48:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/mrtk-porting-guide.md
:bulb:Suggestion
View
Details

mixed-reality-docs/mrtk-porting-guide.md

Line 6: [Suggestion] Invalid date format for 'ms.date': '10/14/19'. Must be a date in format MM/DD/YYYY, no more than 30 days from today. NOTE: This Suggestion will become a Warning on 11/25/2019.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Distribute the database

As we all know, writing to just 1 folder can be too slow.  So why don't
we increase the size of the folder cluster?
I did some testing and it appears to be bug free.
TODO:  Async IO

Smart feature.  Can you make it so that the DB is not distributed by default but so that distribution can be turned on?  You can use the same kind of interface that we use for webscale mode in the Python port.

I pushed it!  https://asciinema.org/a/18447

*I pushed the update


Add a WinUI3 Sample

Is your feature request related to a problem? Please describe.
Need a sample for WinUI3

Have a look at #373

Thanks for that.  Love it.  The PR will be sitting there for a while so I can figure out the problem with the library; once I've got that done, I'll be able to merge it in.  I appreciate your submission!

You are welcome. Btw. downgrading to 5.0.2 works like a charm (obviously). :)

Hmm - that's actually stranger, because the "per-platform" code was introduced in 5.0.2 - 5.0.3 was just an upgrade to the SQLite version.  I will investigate.

Uhmm. Not at work atm and I'm not completely sure, I didn't downgrade to 5.0.1.

No worries - I'm not working on this until Friday - would be good to have an idea.

Figured out the problem with WinUI - It's going to require a release, so there will be a 5.0.4 that supports WinUI3.  Basically, net6.0-windows was using Microsoft.Maui.Storage - I switched it to use Windows.Storage instead, then tested on WPF, UWP, WinUI, and MAUI Windows to ensure it works properly.  Once 5.0.4 is out, I'll be able to work on the WinUI tutorial.


NicoVideo video ID issue

I would like to raise an issue regarding NicoVideo video id problem. As of the source code, the video id is "locked" with smxxxxxx where xxxxx are represented with number. However, NicoVideo video id DOES contains other than "smxxxxxxx" such as "nmxxxxxxxx" and "soxxxxxxxx". You may refer to my user page in Kancollewiki zh: http://zh.kcwiki.moe/wiki/User:KyoriAsh
My suggestion is:
'url_regex'		=> [
'#nicovideo.jp/watch/(sm[\d]+)#is'
],
'id_regex'		=> [
'#^(sm[\d]+)$#is'
]
change to
'url_regex'		=> [
'#nicovideo.jp/watch/([A-Za-z]{2}\d+)#is'
],
'id_regex'		=> [
'#^([A-Za-z]{2}\d+)$#is'
]
so that it will cover those aforementioned video id.

I am on bugs this week so I am putting this into my queue to fix it.

I tested the issue and also found they now also use pure numeric video IDs.  I updated the regex and made a new release to fix the issue.
https://github.com/Alexia/mediawiki-embedvideo/releases/tag/v2.2.6


Issue #234 configurable layout

Samples:
Null

Bottom - current layout

Right

Scratchy

As you can see, the scratchy layout is the greenest of all them, but I think it is a good starting point

The code seems nice to me.
I don't completely like the names of the layout. You are talking implicitly of the position of the editor, but your property is called layout. So, I would either:

rename it to editor_position
or rename the enum values to editor_right, editor_bottom, no_editor, scratchy


update arrayToHtmlList to more high efficiency

update arrayToHtmlList to more high efficiency
What does your PR belong to?

[x] Snippets

Types of changes

[x] Enhancement (non-breaking improvement of a snippet)

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have checked that the changes are working properly
[ ] I have checked that there isn't any PR doing the same
[ ] I have read the CONTRIBUTING document.

Do not change readme.md, that is an auto generated file. You should change the snippet file if you want to update a snippet

You should open a new pull request with the updated snippet file and close this one for charities/history sake to fix this issue


Mark subs as throwing exceptions

+1 from me. Only comment (nitpick): would ValueError be more appropriate than RuntimeError?


No cashout is created.

Summary
Cashout has not been generated since last week when the network had a problem.

6 March, cashout has failed with null error. from then on i cannot cashout any more.
there are only 2 peers always, but i can see the log 'successfully connected to peer '.
(but when i call /peers, the peer-id what i saw in the log is not exist.)
i can see the log 'could not send payment threshold announcement to peer '.

should i backup the wallet and create new node? or Is there any way to solve the problem?

Please have a look at our trouble shoot guide for cashout problems: https://hackmd.io/95rvXRswSh-xm9Td_Xl2cg?view
If the issue persists, my advice would be to make a backup of your private key and start a new node.


Fixes/favicon

Related Issue(s)
Fixes #
Resolves #
Closes #
Proposed Changes

[x]

Checklist

[x] I have followed the repository's contribution guidelines.
[x] I have added necessary documentation or updated existing documentation.
[x] My code follows the established code style and formatting of the project.
[x] I have tested my changes and they function as expected.
[ ] I have added suitable unit tests (if applicable).

Screenshots

To-Do

[ ]

Additional Information

Resolves #39

@Codebox124 still not fixed : https://realfavicongenerator.net/favicon_checker?protocol=https&site=app-decenterai-com-git-fixes-favicon-decenter-ai.vercel.app

@Codebox124 update the pr

there are unwanted changes, I guess


upower: Fix a race condition in test_sibling_priority_no_overwrite

The latest upower release contains a race condition in test_sibling_priority_no_overwrite, resulting in spurious test failures.
This change applies a trivial patch from upstream to correct the issue: https://gitlab.freedesktop.org/upower/upower/-/commit/9ee76826bd41a5d3a377dfd6f5835f42ec50be9a.patch

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@ofborg build upower
Not sure if this is a great idea but the build seems to have failed / timed out previously.


Fix the isUds logic

/lgtm
/approve

@wattli: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
a3edf5befdf1fc8fd2e9faf99a10e27d5bf8e14e
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@wattli: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
4ff4ef5f484c5e9523742ea099a3df6fe43f6783
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


50 url lengthener

I stole most of the core implementation from Bixo's UrlLengthener, but I wrote all the test code.

I think we should have an integration test that tries a "known" bit.ly URL (one I've already set up) to confirm that it's doing the right thing. Probably should also have a test for a redirect to a redirect.

Similar to robots fetching, we want to have a specially configured fetcher for processing redirects from lengtheners. E.g. set max redirects to 0, so we get the exception that has the redirected URL in it, and we don't following additional redirects from the target domain. and a very small fetch size, and a very low timeout, as these lengtheners should all be very fast, unless something is borked. So maybe a FetcherUtils class that has a static method to create an appropriate builder for the redirect fetcher?

I believe I've addressed all of the comments Ken made above with the exception of the user agent.


Send a direct message

I'm trying in any possible way to send a direct message to an user, but I can't find a way on Python. Please can you help me?
Using NodeJS it can be obtained like this:
const userId = await ig.user.getIdByUsername('username');
const thread = ig.entity.directThread([userId.toString()]);
await thread.broadcastText('Message from node');

@annalitvin which library you are using for NodeJS ?

@annalitvin which library you are using for NodeJS ?

https://github.com/dilame/instagram-private-api


Integration tests are not being included with default test command

In the 'collator' branch, when I run the tests with cargo test it does not picking up and run the tests that are in the tests/ directory anymore. It only runs the new tests that are within the implementation files. So to run all tests at the moment we have to run cargo test --test cli_test && cargo test instead of just cargo test, which is not ideal

Closing as cargo test does now run all tests including integration tests.


Add a sync status getter to augur-state

This should be the v2 equivalent of augur.augurNode.getSyncData

Eventually this will probably be emitted using whatever we decide here: #2183.


Allow for custom css definition in front end

This would create a fork of the css that would then be loaded in dynamically based on the themes default. This way people could modify it completely through the UI now that templates are separates from state are separated from styles

The new custom theme supports part of this in the custom theme but we could also do the same for the site itself

Any site rather


Cargo doesnt identify rust-toolchain.toml

Steps To Reproduce
Steps to reproduce the behavior:

clone https://github.com/muppi090909/ROS
run nix-build default.nix

Build log
this derivation will be built:
  /nix/store/mn12nnx901q76ddk38rpryzb9cpmjhcn-ros-0.1.0.drv
building '/nix/store/mn12nnx901q76ddk38rpryzb9cpmjhcn-ros-0.1.0.drv'...
unpacking sources
unpacking source archive /nix/store/znpmyxzm8n92mbqjhpc8b4qq18lp0rqw-ROS
source root is ROS
patching sources
configuring
no configure script, doing nothing
building
Building kernel
    Updating crates.io index
 Downloading crates ...
  Downloaded bootloader v0.9.22
error: "/nix/store/slmsxfx879zlkdcr1vmm0nlacj9dhwqv-rustc-1.61.0/lib/rustlib/src/rust/Cargo.lock" does not exist, unable to build with the standard library, try:
        rustup component add rust-src
Error: Kernel build failed.
Stderr:
error: builder for '/nix/store/mn12nnx901q76ddk38rpryzb9cpmjhcn-ros-0.1.0.drv' failed with exit code 1

Additional context
My rust-toolchain.toml
[toolchain]
channel="nightly"
components = ["rust-src", "llvm-tools-preview", "cargo"]
targets = ["x86_64-ros"]

x86_64-ros.json
{
    "llvm-target": "x86_64-unknown-none",
    "data-layout": "e-m:e-i64:64-f80:128-n8:16:32:64-S128",
    "arch": "x86_64",
    "target-endian": "little",
    "target-pointer-width": "64",
    "target-c-int-width": "32",
    "os": "none",
    "executables": true,
    "linker-flavor": "ld.lld",
    "linker": "rust-lld",
    "panic-strategy": "abort",
    "disable-redzone": true,
    "features": "-mmx,-sse,+soft-float"
}

The problem is that cargo is not identifying rust-toolchain.toml.
Notify maintainers
@retrry
Metadata
this path will be fetched (0.00 MiB download, 0.00 MiB unpacked):
/nix/store/ym48rw2727g45akp4bd6bgng9wwil5y5-nix-info
copying path '/nix/store/ym48rw2727g45akp4bd6bgng9wwil5y5-nix-info' from 'https://cache.nixos.org'...

system: "x86_64-linux"
host os: Linux 5.15.0-39-generic, Ubuntu, 22.04 LTS (Jammy Jellyfish), nobuild
multi-user?: no
sandbox: yes
version: nix-env (Nix) 2.9.1
channels(perseus): "nixpkgs"
nixpkgs: /home/perseus/.nix-defexpr/channels/nixpkgs

What does

./configuration.nix # Your system configuration.
mean?

Any way I can use

[ (import (builtins.fetchTarball "https://github.com/oxalica/rust-overlay/archive/master.tar.gz")) ]

local only?

Yes

how

But your target is a bit exotic, I doubt whether there's prebuilt toolchain for that.

Its a custom toolchain.

This sounds, a bit challenging, what about resorting to rustup for now?

So how do I do that?

Just do whatever you would do on other distributions?
Also I checked that there was support for custom rust targets in nixpkgs, but broken now for some reason. I would investigate into that later.


fixed [!NOTE] markup

fixed [!NOTE] markup

@mmascolino : Thanks for your contribution! The author(s) have been notified to review your proposed change.


[VEN-1172] Fix/int rates

Description
This PR adds reserveFactor to vToken constructor and adjusts the deployment config. It also chagnes BaseJumpRateModelV2.blocksPerYear  value with the correct one for BSC
Resolves # VEN-1172
Checklist

[ ] I have updated the documentation to account for the changes in the code.
[ ] If I added new functionality, I added tests covering it.
[ ] If I fixed a bug, I added a test preventing this bug from silently reappearing again.
[ ] My contribution follows Venus contribution guidelines.

the reason for that is because setReserveFactor is access controlled and we need to give deployer default access to this function. If deployer account gets compromised at some point that might be a big problem. Also on the other hand it really makes logic of deployment scripts more complicated... Setting this in the initialise function we call the _setReserveFactorFresh which is internal and not guarded... I think that we actually discussed this possible implementation (only change in the deployment script) but we agreed on changing the smart contract logic for reserveFactorMantissa initialisation


[EventHubs][Perf] Remove uampq perf CI testing

This reduces the perf testing time in the nightly CI pipeline. Perf tests using the uamqp transport is being moved away from in favor of the python-based amqp transport, so these perf numbers aren't as critical anymore.

@pvaneck Thank you so much for handling this :)


Add echo_nest_converter

A tool to export analysis data from Amen to a JSON encoded string that is compatible with Remix.js

This change is

This looks good at a glance!  My dev environment is not yet up on my new machine, but I will try to get it done / get to this this week.

Nice work - will try to find time to work on this / adding features to this soon.


ZXP bundling does not include .jsx files

When I run 'yarn build' the project is built successfully, and everything functions as expected.
However, when I run 'yarn zxp' and install that file, the extension does not work.
After some digging, I figured out that the zxp bundle did not include the same jsx folder and index.js file that the build, and manual install for the extension does.
My current workaround is dragging the jsx folder into the installed zxp, which works for now.
I'm not sure exactly where to begin on fixing this and haven't seen any similar issues in the repo.
Thank you!

I had the same problem. @justintaylor-dev just fixed it by updating the vite-cep-plugin.
Please run yarn add vite-cep-plugin to update the plugin. And then rerun yarn zxp

I had the same problem. @justintaylor-dev just fixed it by updating the vite-cep-plugin.
Please run yarn add vite-cep-plugin to update the plugin. And then rerun yarn zxp

Thank you so much!


Add Jobs section to deployment concepts

assign to @CloudyMind

is this closed?

Nope, still need work.


Profile: Add ability to make properties readonly

See https://github.com/describo/profiles/issues/1

Handled in ace47174349f9b7c44d40a4c48cbc663691f5c9d


'Management Solutions' category no longer exists

I believe it was renamed to Log Analytics when exploring available solutions in the gallery

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

ID: a2902958-bbda-b892-6da7-1b8ed598c6bb
Version Independent ID: 7f63a743-b2a7-245a-dcee-07d4b357051c
Content: Monitoring solutions in Azure Monitor
Content Source: articles/azure-monitor/insights/solutions.md
Service: log-analytics
GitHub Login: @bwren
Microsoft Alias: bwren

@stewartadam Thanks for your question. We are checking on this and will respond to you soon.

@stewartadam Monitoring solutions were previously referred to as management solutions.

In the Azure portal open All services and locate Solutions.

@stewartadam We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

It's still incorrect, the current title is Log Analytics, not Management Solutions or Monitoring Solutions.
Because of all these renames, the overall UX attempting to get new monitoring solutions is poor since Azure ARM resources (like App Insights or Log Analytics workspaces) are mixed in the listings with Log Analytics solutions.

@stewartadam Could you share the screenshot of the portal?

@stewartadam @SadiqhAhmed-MSFT At the moment, I think, It should be a bug of azure portal, the Management Solutions sub-category is missing while comparing with Azure Marketplace. see my latest updates in #36560


Is it possible to learn the functionality of a Set data structure with DNC?

I am trying to train a DNC to replicate the Set data structure, but all of my efforts so far have been unsuccessful. I have described the problem in a greater detail in the link below:
https://www.reddit.com/r/deeplearning/comments/8zk6vt/need_help_how_to_train_the_neural_network_to/
Is the DNC the right choice for these sort of tasks? Any help/suggestion is very much appreciated.
Thank you,
Rahim

The DNC is certainly capable of learning this function, in fact it just needs content-based attention to perform the retrieval. Other than that, it only needs to learn how to relate the commands to the relevant gating operations. If I were you, and struggling to see it work, I would ensure my sequences are quite short to begin with and the training data is procedurally generated so the network cannot overfit and begin memorizing values. You can still have a held-out validation set, just blacklist some values or something.
I am guessing you are only feeding back the gradients from the loss for time steps when you expect 1/0 contains result. That might help reduce noise (vs feeding gradients back at each time step).

Thanks a lot for your comment. I have tried passing back the max of the content-based addressing pre-normalization, but the model still was making mistakes on the training data (it was procedurally generated). What I noticed was that the errors were made when the two numbers were close to each other (absolute difference < 3). When one-hot encoding the numbers on the other hand it achieved 100% accuracy. I trained on a sequence of 8 numbers with memory height of 10. Interestingly, once I increased the memory height to 11, the error rate jumped. However, for longer sequences of length 12 for example, increasing the memory height reduced the error twice. One-hot encoding has another problem that the width of the input sequence is now fixed, which means it will not scale for larger numbers. I think this problem can be solved though, maybe if I use a convolutional layer to reduce the dimensions of the encoded number. Also, the values stored in the memory are hard to interpret, because they are almost equal in each row (each very close to 1 or -1). I am not sure how does the network decide if it has seen the number before.


⚠ Bofrost.lu has degraded performance

In e94c6cb, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 949 ms

Resolved: Bofrost.lu performance has improved in 6a636b4 after 6 minutes.


NOMERGE PR.js Build Improvements

PR.js Build Improvements
Please note

This PR does not complete everything that I had in mind for sprucing up PR.js. I'll list below what I've completed & what I haven't.
I've been reassigned to JS training & Pixwel. Due to this, I'm very wary of leaving these commits unmerged. I don't want to return to them in 3 or 6 months & have no memory of what I was doing. Worse, I don't want the work to be lost due to accidental deletion. On the other hand, I don't want anything prematurely completed merged into master.

Overall Goal

Create of a build/ dir for development & a dist/ dir where everything works "out of the box"
100% test coverage.
CI

Completed

Modularization of gulp setup
gulp serve now has live reload
Minified css and img/ go to dist/
buildjs task is incomplete

It creates build.min.js and build.min.js.maps. If there is other JS that needs minification, it hasn't been done yet.

Testing: parsers/ and validators/ are tested, but not UI/
Travis CI builds the functionality listed above

Incomplete

UI/ tests with PhantomJS
html build & minification (this is tricky due to Angular partials)
less build & minification
ESLint
jspm style enforcement
npm publication
nsp automated security auditing for dependencies
test coverage reports (Istanbul?)
No live reload yet for css, less, html, etc.
Possibly missing 100% test coverage.
gulp watch isn't set up
Lots and lots of pretty badges :eyes:

Conclusion

I'm not certain how to move forward at this point. Here are some possibilities

Merge the existing work, with little to no cleanup, & put the remaining tasks on the back-burner
Complete the remaining tasks. However, this would cut into Pixwel/JS time.
Just leave everything as is. Write up the situation so that when I return to this in the future, I'll have notes to jog my memory.

@nateabele @gavD @ovaska Feedback appreciated.


OSCORE fallback use cases

Using OSCORE, I found a pretty simple use case where the client will not be able to connect to the server anymore.

I launch a leshan-server-demo
I create oscore config for my device in the UI
I launch a leshan-client-demo using the corresponding OSCORE setting
simulate a crash (kill -9 PID on linux), this way the client doesn't send a deregister.
then I try to relaunch the client (same OSCORE config)
and I get a : Registration failed: UNAUTHORIZED(401) Replay detected.

@rikard-sics any idea about this ? and how we could handle this ?

Spontaneous reaction: This should be solved by making sure the Client uses the Appendix B.2 procedure defined in the OSCORE RFC here:
https://datatracker.ietf.org/doc/html/rfc8613#appendix-B.2
It will re-establish a new OSCORE Security Context, most importantly new Sender/Recipient Keys and a fresh replay window on the server. By doing that the Client restarting from Sender Sequencer Number 0 is not Key and Nonce reuse, and not a replay either. (Note that the Appendix B.2 procedure changes the ID Context but keeps the same Sender/Recipient IDs).
So basically if the client loses mutable state information in the context (like the Sender Sequence Number), it must use this procedure the first time it resumes communication with the server. I believe in the current code the Client will at least use this procedure when it registers to the server.
That being said I need to investigate this case to understand if the Client is trying to use Appendix B.2 in this case. If not, using it should solve this. If the client is trying to use it already, we need to investigate things further.

This should be solved by making sure the Client uses the Appendix B.2 procedure defined in the OSCORE RFC here:
https://datatracker.ietf.org/doc/html/rfc8613#appendix-B.2

I don't know what should be done in the code to be sure that appendex B.2 is used ? :thinking:

I believe in the current code the Client will at least use this procedure when it registers to the server.

I think it makes sense.
But as you said that "Note that the Appendix B.2 procedure changes the ID Context "
What the purpose to set the Context ID in OSCORE object (21) at bootstrap time :thinking:  ?

@rikard-sics I would really appreciate if we can find a fix (or at least workaround) for this. :pray:

I try to investigate on this.

I don't know what should be done in the code to be sure that appendex B.2 is used ?

Looking at cf test, I saw that maybe the carlifornium API to do that is :
// Enable context re-derivation functionality (in general)
ctx.setContextRederivationEnabled(true);
// Explicitly initiate the context re-derivation procedure
ctx.setContextRederivationPhase(PHASE.CLIENT_INITIATE);

So I tried to add this to InMemoryOscoreContextDB.deriveContext :
private static OSCoreCtx deriveContext(OscoreParameters oscoreParameters) {
    try {
        OSCoreCtx osCoreCtx = new OSCoreCtx(oscoreParameters.getMasterSecret(), true,
                oscoreParameters.getAeadAlgorithm(), oscoreParameters.getSenderId(),
                oscoreParameters.getRecipientId(), oscoreParameters.getHmacAlgorithm(), 32,
                oscoreParameters.getMasterSalt(), null, 1000);
        osCoreCtx.setContextRederivationEnabled(true);
        // 👇 I try to add this line below 👇
        osCoreCtx.setContextRederivationPhase(PHASE.CLIENT_INITIATE);
        return osCoreCtx;
    } catch (OSException e) {
        LOG.error("Unable to derive context from {}", oscoreParameters, e);
        return null;
    }
}

But then I'm not able to connect with OSCORE anymore because of :
java.lang.IllegalArgumentException: Internal Leshan operations should always use a null ID Context.
Raised by InMemoryOscoreContextDB.getContext(byte[] rid, byte[] IDContext)
So I tried to remove the check just for testing but this failed with :
org.eclipse.californium.scandium.dtls.cipher.InvalidMacException: MAC validation failed
	at org.eclipse.californium.scandium.dtls.cipher.CCMBlockCipher.decrypt(CCMBlockCipher.java:406)
	at org.eclipse.californium.scandium.dtls.cipher.CCMBlockCipher.decrypt(CCMBlockCipher.java:335)
	at org.eclipse.californium.cose.EncryptCommon.AES_CCM_Decrypt(EncryptCommon.java:134)
	at org.eclipse.californium.cose.EncryptCommon.decryptWithKey(EncryptCommon.java:74)
	at org.eclipse.californium.cose.Encrypt0Message.decrypt(Encrypt0Message.java:138)
	at org.eclipse.californium.oscore.Decryptor.decryptAndDecode(Decryptor.java:140)
	at org.eclipse.californium.oscore.RequestDecryptor.decrypt(RequestDecryptor.java:105)
	at org.eclipse.californium.oscore.ObjectSecurityLayer.prepareReceive(ObjectSecurityLayer.java:104)
	at org.eclipse.californium.oscore.ObjectSecurityLayer.receiveRequest(ObjectSecurityLayer.java:312)

Finally, I get to the conclusion that I'm not really able to do that without someone who really well understands OSCORE RFC and OSCORE Californium code, so I give up for now to try to do this alone.
@rikard-sics, I'm waiting for your help :pray: !

@rikard-sics, I'm waiting for your help pray !

Hmm, it is hard to say what is going wrong from just a look at the output. I will try to take some time to test and see if I can figure out what is happening. Today is a bit tricky but I will try to do it as soon as I can.

@rikard-sics
I reproduced the bug described in this issue and I have first question- the second response from the server is COAP not OSCORE message:

However in client log I see the message "Incoming response is NOT OSCORE protected but is expected to be! ":
2023-07-28 16:59:15,874 UdpMatcher           [TRACE] received response ACK-4.01   MID=36245, Token=1C0DEB1355706ECA, OptionSet={"Content-Format":"text/plain", "Max-Age":0}, "Replay detected" from UDP(<IP_ADDRESS>:5683)
2023-07-28 16:59:15,876 EndpointContextUtil  [TRACE] udp context receiving, PLAIN: "" == ""
2023-07-28 16:59:15,876 ObjectSecurityLayer  [INFO] Incoming response is NOT OSCORE protected but is expected to be!
2023-07-28 16:59:15,876 BlockwiseLayer       [DEBUG] [LWM2M Client-coap://<IP_ADDRESS>:0]  received error ACK-4.01   MID=36245, Token=1C0DEB1355706ECA,

The question is : should the 401 response be a plain text COAP or OSCORE protected message ?

Based on information from this and this  example, I concluded that maybe we need two different implementations of deriveContext method in InMemoryOscoreContextDB class ?:
for server:
    private static OSCoreCtx deriveContext(OscoreParameters oscoreParameters) {
        try {
            OSCoreCtx osCoreCtx = new OSCoreCtx(oscoreParameters.getMasterSecret(), false,
                    oscoreParameters.getAeadAlgorithm(), oscoreParameters.getSenderId(),
                    oscoreParameters.getRecipientId(), oscoreParameters.getHmacAlgorithm(), 32,
                    oscoreParameters.getMasterSalt(), null, 4096);
            osCoreCtx.setContextRederivationEnabled(true);
            return osCoreCtx;
        } catch (OSException e) {
            LOG.error("Unable to derive context from {}", oscoreParameters, e);
            return null;
        }
    }

and for client:
    private static OSCoreCtx deriveContext(OscoreParameters oscoreParameters) {
        try {
            OSCoreCtx osCoreCtx = new OSCoreCtx(oscoreParameters.getMasterSecret(), true,
                    oscoreParameters.getAeadAlgorithm(), oscoreParameters.getSenderId(),
                    oscoreParameters.getRecipientId(), oscoreParameters.getHmacAlgorithm(), 32,
                    oscoreParameters.getMasterSalt(), null, 4096);
            osCoreCtx.setContextRederivationEnabled(true);
            osCoreCtx.setContextRederivationPhase(ContextRederivation.PHASE.CLIENT_INITIATE);
            return osCoreCtx;
        } catch (OSException e) {
            LOG.error("Unable to derive context from {}", oscoreParameters, e);
            return null;
        }
    }

Another problem is related to the DEREGISTRATION/REGISTRATION event in EventServlet on server site. As result of context rederivation procedure client is deregistered and registered again and therefore removeContext method in OscoreContextCleaner is cleaning the context. To prevent this, I made the following modification in removeContext method.
    private void removeContext(byte[] rid) {
        OSCoreCtx context = oscoreCtxDB.getContext(rid);
        if (context != null)
            //JL test
            if (!oscoreCtxDB.getContext(rid).getContextRederivationEnabled()) {
                oscoreCtxDB.removeContext(context);
            }
    }

I don't know if checking contextRederivationEnabled flag is the best solution - but currently I don't have better idea ...
The next problem concerns the use of IDContext. Leshan operations can use internally  null ID Context also during context rederivation procedure. I set IDContext=null in client and server site and procedure described in OSCORE appendix-B.2 is finishing succesfully.
This PoC is available here
I found in appendix-B.2 that IDContext is used:

If the client has a unique identifier in some namespace, then that  identifier can be used as ID Context.
The ID Context may be used to add randomness into new Sender and  Recipient Contexts, see Appendix B.2.
In the case of group communication [Group-OSCORE], a group  identifier is used as ID Context to enable different security contexts for a server belonging to multiple groups.

Does it mean that if we assume in leshan internally IDContext=null can we lose some OSCORE functionality ? :worried:

@sbernard31  Do you have any LwM2M device with OSCORE that you could recommend for testing ? I'm looking for device with properly/fully implemented OSCORE that I could to use for testing my changes in Leshan code.

No idea, I didn't play so much with OSCORE.
At first sight :

libcoap seems to support it but this is CoAP only.
anjay also seems to support it but in the commercial version only.

I prepared next PoC oriented on Appendix.B.2 implementation. In deriveContext method in InMemoryOscoreContextDB class I'm using IDContext!=null.
Please find here full implementation here.
Unfortunately to working this implementation properly following modification is mandatory on Califorium site (class ContextRederivation line 340):
			if (contextID == null|| (Arrays.equals(contextID, ctx.getIdContext()))
                                  &&!ctx.getContextRederivationEnabled())  //<- my modification
                         {
				return ctx;
			}

@rikard-sics  How do you see the possibility adding such modification to OSCORE library in Cf ?

@rikard-sics What is Your opinion about such procedure of context derivation initialization ?

Let me take a look during the beginning of next week, and I can follow up in this thread.

Reading  carefully OSCORE Appendix B.2 I found that:
The server sends a 4.01 (Unauthorized) response protected with the second security context, containing R2 wrapped in a CBOR bstr as  'kid context', and caches R2.

In this PoC leshan-client-demo is starting OSCORE Appendix B.2 procedure based on 4.01 (Unauthorized) response from the server.

@rikard-sics What is Your opinion about such procedure of context derivation initialization ?

@rikard-sics Does this mean that mentioned above the 401 Unauthorized message should be also OSCORE encoded?