emcc/webgpu_runtime.cc:206:71: error: non-virtual member function marked 'final' hides virtual member function

HI,
I met the following errors while running the script prep_deps.sh. Can anybody please give me a hand ???
➜  web-llm git:(main) ✗ ./scripts/prep_deps.sh
+ emcc --version
emcc (Emscripten gcc/clang-like replacement + linker emulating GNU ld) 3.1.41 (71634e036d20209a5d81c2b2171e145b44de1e12)
Copyright (C) 2014 the Emscripten authors (see AUTHORS.txt)
This is free and open source software under the MIT license.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

+ npm --version
9.7.1
+ TVM_HOME_SET=
+ [[ -z '' ]]
+ [[ ! -d 3rdparty/tvm-unity ]]
+ export TVM_HOME=3rdparty/tvm-unity
+ TVM_HOME=3rdparty/tvm-unity
+ cd 3rdparty/tvm-unity/web
+ make
emcc -I....../web-llm/3rdparty/tvm-unity -I....../web-llm/3rdparty/tvm-unity/include -I....../web-llm/3rdparty/tvm-unity/3rdparty/dlpack/include -I....../web-llm/3rdparty/tvm-unity/3rdparty/dmlc-core/include -I....../web-llm/3rdparty/tvm-unity/3rdparty/compiler-rt -I....../web-llm/3rdparty/tvm-unity/3rdparty/picojson -O3 -std=c++17 -Wno-ignored-attributes -c -MM -MT dist/wasm/webgpu_runtime.bc emcc/webgpu_runtime.cc >dist/wasm/webgpu_runtime.d
emcc -I....../web-llm/3rdparty/tvm-unity -I....../web-llm/3rdparty/tvm-unity/include -I....../web-llm/3rdparty/tvm-unity/3rdparty/dlpack/include -I....../web-llm/3rdparty/tvm-unity/3rdparty/dmlc-core/include -I....../web-llm/3rdparty/tvm-unity/3rdparty/compiler-rt -I....../web-llm/3rdparty/tvm-unity/3rdparty/picojson -O3 -std=c++17 -Wno-ignored-attributes -emit-llvm -c -o dist/wasm/webgpu_runtime.bc emcc/webgpu_runtime.cc
emcc/webgpu_runtime.cc:206:71: error: non-virtual member function marked 'final' hides virtual member function
  206 |   void SaveToFile(const String& file_name, const std::string& format) final {
      |                                                                       ^
....../web-llm/3rdparty/tvm-unity/include/tvm/runtime/module.h:174:16: note: hidden overloaded virtual function 'tvm::runtime::ModuleNode::SaveToFile' declared here: type mismatch at 2nd parameter ('const String &' vs 'const std::string &' (aka 'const basic_string<char> &'))
  174 |   virtual void SaveToFile(const String& file_name, const String& format);
      |                ^
1 error generated.
emcc: error: '/opt/emsdk/upstream/bin/clang++ -target wasm32-unknown-emscripten -fignore-exceptions -fvisibility=default -mllvm -combiner-global-alias-analysis=false -mllvm -enable-emscripten-sjlj -mllvm -disable-lsr -DEMSCRIPTEN --sysroot=/opt/emsdk/upstream/emscripten/cache/sysroot -Xclang -iwithsysroot/include/fakesdl -Xclang -iwithsysroot/include/compat -I....../web-llm/3rdparty/tvm-unity -I....../web-llm/3rdparty/tvm-unity/include -I....../web-llm/3rdparty/tvm-unity/3rdparty/dlpack/include -I....../web-llm/3rdparty/tvm-unity/3rdparty/dmlc-core/include -I....../web-llm/3rdparty/tvm-unity/3rdparty/compiler-rt -I....../web-llm/3rdparty/tvm-unity/3rdparty/picojson -O3 -std=c++17 -Wno-ignored-attributes -emit-llvm -c emcc/webgpu_runtime.cc -o dist/wasm/webgpu_runtime.bc' failed (returned 1)
make: *** [Makefile:38: dist/wasm/webgpu_runtime.bc] Error 1
+ rm -rf tvm_home
+ ln -s 3rdparty/tvm-unity tvm_home
+ npm install

up to date, audited 760 packages in 737ms

61 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities
+ cd examples/simple-chat
./scripts/prep_deps.sh: line 22: cd: examples/simple-chat: No such file or directory

Thank you ...

Actually, tvm-unity is automatically downloaded by the script prep_deps.sh ....
➜  web-llm git:(main) ./scripts/prep_deps.sh
+ emcc --version
emcc (Emscripten gcc/clang-like replacement + linker emulating GNU ld) 3.1.41 (71634e036d20209a5d81c2b2171e145b44de1e12)
Copyright (C) 2014 the Emscripten authors (see AUTHORS.txt)
This is free and open source software under the MIT license.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

+ npm --version
9.7.1
+ TVM_HOME_SET=
+ [[ -z '' ]]
+ [[ ! -d 3rdparty/tvm-unity ]]
+ echo 'Do not find TVM_HOME env variable, cloning a version as source.'
Do not find TVM_HOME env variable, cloning a version as source.
+ git clone https://github.com/mlc-ai/relax 3rdparty/tvm-unity --recursive
Cloning into '3rdparty/tvm-unity'...
remote: Enumerating objects: 182700, done.
remote: Counting objects: 100% (9791/9791), done.
remote: Compressing objects: 100% (1530/1530), done.
remote: Total 182700 (delta 8446), reused 9292 (delta 8206), pack-reused 172909
Receiving objects: 100% (182700/182700), 68.74 MiB | 33.81 MiB/s, done.
Resolving deltas: 100% (141930/141930), done.
Submodule '3rdparty/OpenCL-Headers' (https://github.com/KhronosGroup/OpenCL-Headers.git) registered for path '3rdparty/OpenCL-Headers'
Submodule '3rdparty/cnpy' (https://github.com/rogersce/cnpy.git) registered for path '3rdparty/cnpy'
Submodule '3rdparty/cutlass' (https://github.com/NVIDIA/cutlass.git) registered for path '3rdparty/cutlass'
Submodule 'dlpack' (https://github.com/dmlc/dlpack.git) registered for path '3rdparty/dlpack'
Submodule 'dmlc-core' (https://github.com/dmlc/dmlc-core.git) registered for path '3rdparty/dmlc-core'
Submodule '3rdparty/libbacktrace' (https://github.com/tlc-pack/libbacktrace.git) registered for path '3rdparty/libbacktrace'
Submodule '3rdparty/rang' (https://github.com/agauniyal/rang.git) registered for path '3rdparty/rang'
Submodule '3rdparty/vta-hw' (https://github.com/apache/tvm-vta.git) registered for path '3rdparty/vta-hw'
Cloning into '....../web-llm/3rdparty/tvm-unity/3rdparty/OpenCL-Headers'...
remote: Enumerating objects: 1276, done.
remote: Counting objects: 100% (299/299), done.
remote: Compressing objects: 100% (119/119), done.
remote: Total 1276 (delta 244), reused 199 (delta 177), pack-reused 977
Receiving objects: 100% (1276/1276), 742.53 KiB | 2.55 MiB/s, done.
Resolving deltas: 100% (828/828), done.
Cloning into '....../web-llm/3rdparty/tvm-unity/3rdparty/cnpy'...
remote: Enumerating objects: 164, done.
remote: Total 164 (delta 0), reused 0 (delta 0), pack-reused 164
Receiving objects: 100% (164/164), 52.32 KiB | 396.00 KiB/s, done.
Resolving deltas: 100% (94/94), done.
Cloning into '....../web-llm/3rdparty/tvm-unity/3rdparty/cutlass'...
remote: Enumerating objects: 20969, done.
remote: Counting objects: 100% (1016/1016), done.
remote: Compressing objects: 100% (528/528), done.
remote: Total 20969 (delta 502), reused 928 (delta 469), pack-reused 19953
Receiving objects: 100% (20969/20969), 31.45 MiB | 29.81 MiB/s, done.
Resolving deltas: 100% (15302/15302), done.
Cloning into '....../web-llm/3rdparty/tvm-unity/3rdparty/dlpack'...
remote: Enumerating objects: 462, done.
remote: Counting objects: 100% (99/99), done.
remote: Compressing objects: 100% (42/42), done.
remote: Total 462 (delta 72), reused 67 (delta 57), pack-reused 363
Receiving objects: 100% (462/462), 1.70 MiB | 4.61 MiB/s, done.
Resolving deltas: 100% (160/160), done.
Cloning into '....../web-llm/3rdparty/tvm-unity/3rdparty/dmlc-core'...
remote: Enumerating objects: 6294, done.
remote: Counting objects: 100% (158/158), done.
remote: Compressing objects: 100% (110/110), done.
remote: Total 6294 (delta 67), reused 98 (delta 31), pack-reused 6136
Receiving objects: 100% (6294/6294), 1.68 MiB | 4.75 MiB/s, done.
Resolving deltas: 100% (3813/3813), done.
Cloning into '....../web-llm/3rdparty/tvm-unity/3rdparty/libbacktrace'...
remote: Enumerating objects: 459, done.
remote: Counting objects: 100% (311/311), done.
remote: Compressing objects: 100% (36/36), done.
remote: Total 459 (delta 285), reused 275 (delta 275), pack-reused 148
Receiving objects: 100% (459/459), 1.03 MiB | 3.58 MiB/s, done.
Resolving deltas: 100% (341/341), done.
Cloning into '....../web-llm/3rdparty/tvm-unity/3rdparty/rang'...
remote: Enumerating objects: 735, done.
remote: Counting objects: 100% (31/31), done.
remote: Compressing objects: 100% (27/27), done.
remote: Total 735 (delta 9), reused 15 (delta 3), pack-reused 704
Receiving objects: 100% (735/735), 265.43 KiB | 1.33 MiB/s, done.
Resolving deltas: 100% (371/371), done.
Cloning into '....../web-llm/3rdparty/tvm-unity/3rdparty/vta-hw'...
remote: Enumerating objects: 3312, done.
remote: Counting objects: 100% (330/330), done.
remote: Compressing objects: 100% (137/137), done.
remote: Total 3312 (delta 258), reused 193 (delta 193), pack-reused 2982
Receiving objects: 100% (3312/3312), 1.43 MiB | 3.66 MiB/s, done.
Resolving deltas: 100% (1442/1442), done.
Submodule path '3rdparty/OpenCL-Headers': checked out 'b590a6bfe034ea3a418b7b523e3490956bcb367a'
Submodule path '3rdparty/cnpy': checked out '4e8810b1a8637695171ed346ce68f6984e585ef4'
Submodule path '3rdparty/cutlass': checked out '92ebbf1dc4612bf838ace6f2e6d262919f0abd63'
Submodule path '3rdparty/dlpack': checked out 'e2bdd3bee8cb6501558042633fa59144cc8b7f5f'
Submodule path '3rdparty/dmlc-core': checked out '09511cf9fe5ff103900a5eafb50870dc84cc17c8'
Submodule path '3rdparty/libbacktrace': checked out '08f7c7e69f8ea61a0c4151359bc8023be8e9217b'
Submodule path '3rdparty/rang': checked out 'cabe04d6d6b05356fa8f9741704924788f0dd762'
Submodule path '3rdparty/vta-hw': checked out '36a91576edf633479c78649e050f18dd2ddc8103'
+ export TVM_HOME=3rdparty/tvm-unity
+ TVM_HOME=3rdparty/tvm-unity
+ cd 3rdparty/tvm-unity/web
+ make
emcc -I....../web-llm/3rdparty/tvm-unity -I....../web-llm/3rdparty/tvm-unity/include -I....../web-llm/3rdparty/tvm-unity/3rdparty/dlpack/include -I....../web-llm/3rdparty/tvm-unity/3rdparty/dmlc-core/include -I....../web-llm/3rdparty/tvm-unity/3rdparty/compiler-rt -I....../web-llm/3rdparty/tvm-unity/3rdparty/picojson -O3 -std=c++17 -Wno-ignored-attributes -c -MM -MT dist/wasm/wasm_runtime.bc emcc/wasm_runtime.cc >dist/wasm/wasm_runtime.d
emcc -I....../web-llm/3rdparty/tvm-unity -I....../web-llm/3rdparty/tvm-unity/include -I....../web-llm/3rdparty/tvm-unity/3rdparty/dlpack/include -I....../web-llm/3rdparty/tvm-unity/3rdparty/dmlc-core/include -I....../web-llm/3rdparty/tvm-unity/3rdparty/compiler-rt -I....../web-llm/3rdparty/tvm-unity/3rdparty/picojson -O3 -std=c++17 -Wno-ignored-attributes -emit-llvm -c -o dist/wasm/wasm_runtime.bc emcc/wasm_runtime.cc
emcc -I....../web-llm/3rdparty/tvm-unity -I....../web-llm/3rdparty/tvm-unity/include -I....../web-llm/3rdparty/tvm-unity/3rdparty/dlpack/include -I....../web-llm/3rdparty/tvm-unity/3rdparty/dmlc-core/include -I....../web-llm/3rdparty/tvm-unity/3rdparty/compiler-rt -I....../web-llm/3rdparty/tvm-unity/3rdparty/picojson -O3 -std=c++17 -Wno-ignored-attributes -c -MM -MT dist/wasm/tvmjs_support.bc emcc/tvmjs_support.cc >dist/wasm/tvmjs_support.d
emcc -I....../web-llm/3rdparty/tvm-unity -I....../web-llm/3rdparty/tvm-unity/include -I....../web-llm/3rdparty/tvm-unity/3rdparty/dlpack/include -I....../web-llm/3rdparty/tvm-unity/3rdparty/dmlc-core/include -I....../web-llm/3rdparty/tvm-unity/3rdparty/compiler-rt -I....../web-llm/3rdparty/tvm-unity/3rdparty/picojson -O3 -std=c++17 -Wno-ignored-attributes -emit-llvm -c -o dist/wasm/tvmjs_support.bc emcc/tvmjs_support.cc
emcc -I....../web-llm/3rdparty/tvm-unity -I....../web-llm/3rdparty/tvm-unity/include -I....../web-llm/3rdparty/tvm-unity/3rdparty/dlpack/include -I....../web-llm/3rdparty/tvm-unity/3rdparty/dmlc-core/include -I....../web-llm/3rdparty/tvm-unity/3rdparty/compiler-rt -I....../web-llm/3rdparty/tvm-unity/3rdparty/picojson -O3 -std=c++17 -Wno-ignored-attributes -c -MM -MT dist/wasm/webgpu_runtime.bc emcc/webgpu_runtime.cc >dist/wasm/webgpu_runtime.d
emcc -I....../web-llm/3rdparty/tvm-unity -I....../web-llm/3rdparty/tvm-unity/include -I....../web-llm/3rdparty/tvm-unity/3rdparty/dlpack/include -I....../web-llm/3rdparty/tvm-unity/3rdparty/dmlc-core/include -I....../web-llm/3rdparty/tvm-unity/3rdparty/compiler-rt -I....../web-llm/3rdparty/tvm-unity/3rdparty/picojson -O3 -std=c++17 -Wno-ignored-attributes -emit-llvm -c -o dist/wasm/webgpu_runtime.bc emcc/webgpu_runtime.cc
emcc/webgpu_runtime.cc:206:71: error: non-virtual member function marked 'final' hides virtual member function
  206 |   void SaveToFile(const String& file_name, const std::string& format) final {
      |                                                                       ^
....../web-llm/3rdparty/tvm-unity/include/tvm/runtime/module.h:174:16: note: hidden overloaded virtual function 'tvm::runtime::ModuleNode::SaveToFile' declared here: type mismatch at 2nd parameter ('const String &' vs 'const std::string &' (aka 'const basic_string<char> &'))
  174 |   virtual void SaveToFile(const String& file_name, const String& format);
      |                ^
1 error generated.
emcc: error: '/opt/emsdk/upstream/bin/clang++ -target wasm32-unknown-emscripten -fignore-exceptions -fvisibility=default -mllvm -combiner-global-alias-analysis=false -mllvm -enable-emscripten-sjlj -mllvm -disable-lsr -DEMSCRIPTEN --sysroot=/opt/emsdk/upstream/emscripten/cache/sysroot -Xclang -iwithsysroot/include/fakesdl -Xclang -iwithsysroot/include/compat -I....../web-llm/3rdparty/tvm-unity -I....../web-llm/3rdparty/tvm-unity/include -I....../web-llm/3rdparty/tvm-unity/3rdparty/dlpack/include -I....../web-llm/3rdparty/tvm-unity/3rdparty/dmlc-core/include -I....../web-llm/3rdparty/tvm-unity/3rdparty/compiler-rt -I....../web-llm/3rdparty/tvm-unity/3rdparty/picojson -O3 -std=c++17 -Wno-ignored-attributes -emit-llvm -c emcc/webgpu_runtime.cc -o dist/wasm/webgpu_runtime.bc' failed (returned 1)
make: *** [Makefile:38: dist/wasm/webgpu_runtime.bc] Error 1
+ rm -rf tvm_home
+ ln -s 3rdparty/tvm-unity tvm_home
+ npm install
npm WARN deprecated<EMAIL_ADDRESS>See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated<EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated<EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated<EMAIL_ADDRESS>See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated<EMAIL_ADDRESS>Use your platform's native performance.now() and performance.timeOrigin.
npm WARN deprecated<EMAIL_ADDRESS>Please use @jridgewell/sourcemap-codec instead
npm WARN deprecated<EMAIL_ADDRESS>some dependency vulnerabilities fixed, support for node < 10 dropped, and newer ECMAScript syntax/features added

added 759 packages, and audited 760 packages in 3s

61 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities
+ cd examples/simple-chat
./scripts/prep_deps.sh: line 22: cd: examples/simple-chat: No such file or directory


Use local

How to use tenantable in localhost?
I create virtual hosts point to the same dir, but $resolver->getActiveTenant(); only return null.

you need to make sure your computers host file points that domain to localhost, and the virtual host for the webserver also sends that domain to the same location as well.
The package simply reads the "domain()" function of the laravel request, how you get there is soemthing you need to setup on your own as it can be different across multiple different os's.
the best solution would be to use laravel homestead, because you can map multiple domains to the same share folder, then you just setup the host file on your machine, nice and simple.

Thank you leemason and congratulations! great lib :)


Add noindex Checkbox in Admin Page View

Added in https://github.com/hrw-fablab/cms/commit/7de5806656e38287f834fd8bf7a6524cd1191c0c


SteamVR doesnt work with Unity 2019 and postprocess V2

I am using Unity 2019.2.11f1, SteamVR 2.4.5 and HTC VIVE shows a black screen when Unity post process layer has activated "Directly to camera target" and when is disabled the VR image is very distorted.

Doesnt work either with postprocess V1

Thanks for the report but unfortunately this is a Unity XR issue, not a SteamVR Plugin issue. I'd recommend posting on their unity answers forum: https://answers.unity.com/


[ART-6056] update coverity url

according to https://groups.google.com/a/redhat.com/g/aos-team-art/c/67VaN9kjuZI

Codecov Report
Base: 35.45% // Head: 35.39% // Decreases project coverage by -0.06% :warning:

Coverage data is based on head (1b57968) compared to base (29fc1c0).
Patch coverage: 23.68% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #730      +/-   ##
==========================================
- Coverage   35.45%   35.39%   -0.06%
==========================================
  Files          47       47
  Lines       11779    11829      +50
  Branches     2576     2519      -57
==========================================
+ Hits         4176     4187      +11
- Misses       7311     7349      +38
- Partials      292      293       +1

Impacted Files
Coverage Δ

doozerlib/cli/__main__.py
0.00% <ø> (ø)

doozerlib/cli/images_streams.py
0.00% <ø> (ø)

doozerlib/coverity.py
12.24% <0.00%> (ø)

doozerlib/image.py
33.20% <0.00%> (-0.14%)
:arrow_down:

doozerlib/metadata.py
58.13% <0.00%> (-1.25%)
:arrow_down:

doozerlib/runtime.py
26.31% <20.00%> (-0.06%)
:arrow_down:

doozerlib/cli/release_gen_payload.py
59.65% <33.33%> (-1.75%)
:arrow_down:

doozerlib/assembly.py
73.61% <100.00%> (+0.16%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

/lgtm


OpenAPI/Swagger.json definition is broken.

The api specs seem to be broken. If you go to https://editor-next.swagger.io/ and paste the openapi.json you will see the errors.

It's not plugin problem
It's correct, https://metadataapi.net/docs


[feat]: support check PR name and automatically add labels based on PR title

Signed-off-by: mango<EMAIL_ADDRESS>
(If this PR fixes a github issue, please add Fixes #<xyz>.)
Fixes #15311
(or if this PR is one task of a github issue, please add Master Issue: #<xyz> to link to the master issue.)
Master Issue: #
Motivation
Support check PR name and automatically add labels based on PR title
Explain here the context, and why you're making that change. What is the problem you're trying to solve.
Modifications
Ref: autolabeler
semantic
Describe the modifications you've done.
Verifying this change

[x] Make sure that the change passes the CI checks.

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API: (yes / no)
The schema: (yes / no / don't know)
The default values of configurations: (yes / no)
The wire protocol: (yes / no)
The rest endpoints: (yes / no)
The admin cli options: (yes / no)
Anything that affects deployment: (yes / no / don't know)

Documentation
Check the box below or label this PR directly.
Need to update docs?

[ ] doc-required
(Your PR needs to update docs and you will update later)

[x] doc-not-needed
Those changes related to ci

[ ] doc
(Your PR contains doc changes)

[ ] doc-complete
(Docs have been already added)

Hi @Anonymitaet PTAL when you have free time

@mangoGoForward I have some questions on this PR. Can we have a talk through Zoom/Tencent/...? Want to align requirements firstly

@mangoGoForward I have some questions on this PR. Can we have a talk through Zoom/Tencent/...? Want to align requirements firstly

OK, Zoom or Tencent all is ok.

@mangoGoForward How can I contact you personally?

@mangoGoForward How can I contact you personally?

QQ:<PHONE_NUMBER> please @Anonymitaet

@mangoGoForward wechat invitation sent

Thank you very much for your help! @maxsxu @mangoGoForward
Here are TO-DOs:

Add this to https://github.com/apache/pulsar-test-infra/tree/master/docbot instead of dependent GitHub Actions.
Benefits:

Workflow becomes more compact and clean
Able to customize features based on our needs

Test this function in your repo first, then submit PR to the pulsar repo.

Thank you very much for your help! @maxsxu @mangoGoForward
Here are TO-DOs:

Add this to https://github.com/apache/pulsar-test-infra/tree/master/docbot instead of dependent GitHub Actions.
Benefits:

Workflow becomes more compact and clean
Able to customize features based on our needs

Test this function in your repo first, then submit PR to the pulsar repo.

Thanks your patient guidance, I will improve this PR later.

Hi @mangoGoForward, I think you should follow the https://docs.google.com/document/u/1/d/1d8Pw6ZbWk-_pCKdOmdvx9rnhPiyuxwq60_TrD68d7BA/edit.

Want to align requirements firstly

Thanks, @Anonymitaet aligned the requirements with me this afternoon, and I will improve it.

We had a great requirements alignment meeting, thanks for your contributions! @mangoGoForward

This PR actually did two things:

Validating the PR title
Labeling automatically via the PR title

We can split this PR into two PRs to make our intention more clearly.

Why is this called release-drafter.yaml when we are discussing a pr-labelling.yaml improvement?

Yes, the name of workflow should be like pr-labelling.yaml, and the file of release-drafter.yml in root of .github is a configuration file, it can specified like:
      - uses: release-drafter/release-drafter@v5
        # (Optional) specify config name to use, relative to .github/. Default: release-drafter.yml
        # with:
        #   config-name: my-config.yml
        #   disable-autolabeler: true
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

I have commit a new PR #17557 to solve, so I will close this pr.


FR: add ability to more easily bounce between accounts with tier switch

What are you trying to do?
Move back and fourth between accounts created with tier switch with out manually managing the tier.state file.
How should we solve this?
When creating a new account with switch -c it would be nice to provide some lookup key / name, like:
tier switch -c a
and then
tier switch -c b
and then tier switch a would switch back to a. This would also eliminate the need to rename, delete the tier.state file, because switch can handle that for the user.
What is the impact of not solving this?
Less than ideal UX/DX
Anything else?
No response

Closing due to age.


Duplicate log_softmax

Looking throughh the source code for torch.nn.CrossEntropyLoss(), it seems to be doing log_softmax inside it. The model is also doing a log_softmax at the end. Isn't this a duplicate? Is it needed?
From model.py:
    def forward(self, x):
        ...

        # flatten for input to fully-connected layer
        x = x.view(x.size(0), -1)
        x = self.fc(x)
        return F.log_softmax(x, dim=1)

From Pytorch source code:
class CrossEntropyLoss(_WeightedLoss):
...
    def __init__(self, weight=None, size_average=None, ignore_index=-100,
                 reduce=None, reduction='elementwise_mean'):
        super(CrossEntropyLoss, self).__init__(weight, size_average, reduce, reduction)
        self.ignore_index = ignore_index

    def forward(self, input, target):
        return F.cross_entropy(input, target, weight=self.weight,
                               ignore_index=self.ignore_index, reduction=self.reduction)

def cross_entropy(input, target, weight=None, size_average=None, ignore_index=-100,
                  reduce=None, reduction='elementwise_mean'):
...
    if size_average is not None or reduce is not None:
        reduction = _Reduction.legacy_get_string(size_average, reduce)
    return nll_loss(log_softmax(input, 1), target, weight, None, ignore_index, None, reduction)

same qusetion


JBPM-5476 - vacuumlo deletes active large objects of jBPM CLOB data (…

…#709)

jenkins retest this


Make dppl rt threadlocal

Stores the sycl device queues in a thread local storage. The DpplRuntime object is no longer exposed, but new global prebound functions exposes the same API.

Also contains the changes from PR #7


Issue for mapping multiple objects inside the same path response

Hello, after reading some of other solutions I finally end using :

(NSDictionary<NSString *,Class> *)responseClassesByResourcePath

I've create a OVCResponse:
+(NSString *)resultKeyPathForJSONDictionary:(NSDictionary *)JSONDictionary
{
return @"data.user";
}
The problem is that it only model the user json response, I don't know how to achieve the result of modeling the "packs" array. I figured out that does not make sense to do a new OVCResponse for "packs" since it's an array of pack and its inside the same response.
+(NSString *)resultKeyPathForJSONDictionary:(NSDictionary *)JSONDictionary
{
return @"data.packs";
}
The JSON response is (I've setup the model entities and MTLModel classes, User and Pack):
data =     {
    packs =         (
                    {
            created =<PHONE_NUMBER>;
            id = 208684;
            name = Aname;
            settings =                 {
                isOpen = 1;
            };
            status =                 {
                balance = 20000000;
                bids = 0;
                offers = 0;
                points = 0;
            };
            type = normal;
            user =                 {
                group = manager;
                id = 848796;
                name = yoquese;
            };
        }
    );
    user =         {
        checked = 0;
        created =<PHONE_NUMBER>;
        email = "anEmail@email";
        id = 23412;
    };
    version = 100;
};

Thanks in advance.

I have no quick idea about how to add this feature request into Overcoat now. Any suggestion? We may discuss about this :smile:
A workaround would be create a new Mantle model class like:
@interface SomeAPIResultAdapter : MTLModel

// Remember to apply NSValueTransformers to convert dictionary result into instances of these 2 classes.
@property (nonatomic, strong, readonly) User *user;
@property (nonatomic, strong, readonly) NSArray<Pack *> *packs;

@end

Same to #101


Hosted control named [Contoso About Toolbar Container]'s display group should set as AboutPanel

Hosted control named [Contoso About Toolbar Container]'s display group should set as AboutPanel, not ToolbarPanel, otherwise it will display in the ToolbarPanel, not the AboutPanel as the step 6 Test the Application shows.

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

ID: 3b1e303e-da91-e9b0-7bf3-263ee688218e
Version Independent ID: ca002be0-6e4f-72ca-00e2-e4d5fa6071a1
Content: Walkthrough 2: Display an external webpage in your agent application
Content Source: ce/unified-service-desk/walkthrough2-unified-interface-display-an-external-webpage-in-your-agent-application.md
Service: usd
GitHub Login: @kabala123
Microsoft Alias: kabala

@luoyong0201 : Thanks for sharing the feedback. I will update the topic and release it in couple of days.
So as of now I am resolving this comment. please continue to share more feedback so we can enhance the quality of the documentation.


Correct sorting issues for expected_purge_date and expected_purge_date

We discovered the when importing or creating users through the API that fields based on last_date_of_exposure aren't sorting correctly. The following two modifications resolve this issue.
Description
Jira Ticket: SARAALERT-###
We discovered the when importing or creating users through the API that fields based on last_date_of_exposure aren't sorting correctly. The following two modifications resolve this issue.
(Feature) Demo/Screenshots
In SaraAlert v1.11.1

(Bugfix) How to Replicate
Create a user without a last_date_of_exposure via the API or import function. The columns mentioned above will not sort correctly. Also any user-entered with continued exposure will sort based on their created_date or last_date_of_exposure, since they are continually exposed we place them above the latest exposures.
(Bugfix) Solution
The PR implements the same logic as the end_of_monitoring field via SQL allowing for the table to be sorted reliably.
Important Changes
This only modifies public_health_controller.rb
Adjusting the end_of_monitoring and expected_purge_date sorting.
Testing
This fix was tested on the following browsers (submitter must check all those that apply):

[ X] Chrome
[ X] Firefox
[ ] Safari
[ ] IE11

Please describe the tests needed to verify your changes. Provide instructions for reproducing these tests. List any relevant details for your test configuration.
Loading demo data and then using the API or the import tool to create a record without an last_date_of_exposure value.

This "incorrect-sorting-issue" has been fixed in https://github.com/SaraAlert/SaraAlert/pull/439. It's a very similar change, but with slight differences.


Added body parameters support

Though reading schema of parameters is a required functionality to be able to do validations and requests. For instance with current functionality we cannot validate complex input types and cannot create a valid request where body should be an array and not an object

@pouyanh I think release v0.1.0-beta. How do you think about it?

Not yet. Because as I've mentioned above reading schema is an important issue

Sorry for not updating typescript. @olaferlandsen

Don't worry, I can edit it!


Remove powershell when starting jobs in Windows

[#134103211]
Signed-off-by: Charlie Vieth<EMAIL_ADDRESS>

do we need to manually test this change or was it tested in your CI ?

it is also unclear to me how does this diff fix the problem in the original story, can you provide a little explanation of the problem you're trying to solve and the solution. thanks!

We realized that using powershell to start up jobs causes them to sometimes be orphaned upon redeploy because we are unable to kill the powershell process properly (powershell swallows some exit signals etc.). The original story description was actually a symptom of this powershell problem that we discovered later was the cause. We fixed this by collecting the arguments to rep.exe in the monit file, eliminating the need for the start.ps1 script.
As far as I know, this has not yet been run in CI but has been verified manually (e.g. deploy garden-windows and the rep should be functioning as expected and not be running under a powershell process).

cool, thanks @sunjayBhatia

Thanks, @sunjayBhatia. Prioritizing for the Diego team to review.
Best,
Eric

Looks good!

@jenspinney && @bdshroyer


chore: bump version of expo-linear-gradient for expo 50 compatability

Fixes #1673

Hey @jeffrey-dot-li, Thanks for the PR but we are removing linear-gradient creator from @gluestack-ui/themed.
you can have look at this PR.
We are in the process of updating docs for better understanding with more examples. Once that is done we will release it.
Appreciate your efforts ❤ .


Finish extracting arcjet package

This pull request includes several updates to improve the security and organization of imports across multiple files. The most important changes involve consolidating the import of request from @repo/security and updating the configuration for bot detection.
Security and Import Organization:

apps/app/app/(authenticated)/layout.tsx: Moved the import of request from @arcjet/next to @repo/security to consolidate security-related imports.
apps/web/middleware.ts: Updated the import of arcjet and detectBot to come from @repo/security instead of @arcjet/next.
packages/security/index.ts: Added the export of request from @arcjet/next to ensure it is available for other modules.

Configuration Updates:

apps/web/middleware.ts: Changed the configuration of arcjet to use the withRule method for better clarity and maintainability.

Dependency Cleanup:

apps/app/package.json: Removed the dependency on @arcjet/next as it is no longer needed.

Summary by CodeRabbit

New Features

Enhanced bot detection and access control in the AppLayout component.
Streamlined middleware configuration for improved bot protection.

Bug Fixes

Resolved issues related to bot detection logic and request handling.

Chores

Removed dependency on @arcjet/next from the application.

Looks good 👍
You could clarify this:

apps/app/package.json: Removed the dependency on @arcjet/next as it is no longer needed.

to read:

apps/app/package.json: Removed the dependency on @arcjet/next as it is no longer needed (it is now included in packages/security/package.json)


Fix/theme switch

Codecov Report

Merging #66 into master will not change coverage.
The diff coverage is 0.00%.

@@          Coverage Diff           @@
##           master     #66   +/-   ##
======================================
  Coverage    3.92%   3.92%
======================================
  Files          78      78
  Lines         688     688
  Branches      182     182
======================================
  Hits           27      27
  Misses        661     661

Impacted Files
Coverage Δ

src/components/ThemeSwitch/switch.tsx
0.00% <0.00%> (ø)

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 de6ab19...65f179b. Read the comment docs.


Add missing tests for DataFrameAllCloseOperator

Codecov Report
Patch and project coverage have no change.

Comparison is base (8e90533) 100.00% compared to head (00752cd) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #144   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           11        11
  Lines          670       670
  Branches       169       169
=========================================
  Hits           670       670

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Add rpcs

Update RPCs

separate basic RPC by group
update the API of rpc#localNodeInfo, rpc#txPoolInfo, and rpc#getPeers
add new RPCs: rpc#syncState, rpc#clearTxPool, rpc#setNetworkActive, rpc#addNode and rpc#removeNode

Codecov Report

Merging #477 into develop will decrease coverage by 4.20%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           develop     #477      +/-   ##
===========================================
- Coverage    95.34%   91.14%   -4.21%
===========================================
  Files           41       47       +6
  Lines         1504     1400     -104
  Branches       299      289      -10
===========================================
- Hits          1434     1276     -158
- Misses          70      121      +51
- Partials         0        3       +3

Impacted Files
Coverage Δ

packages/ckb-sdk-rpc/src/Base/chain.ts
100.00% <100.00%> (ø)

packages/ckb-sdk-rpc/src/Base/experimental.ts
100.00% <100.00%> (ø)

packages/ckb-sdk-rpc/src/Base/index.ts
100.00% <100.00%> (ø)

packages/ckb-sdk-rpc/src/Base/indexer.ts
100.00% <100.00%> (ø)

packages/ckb-sdk-rpc/src/Base/net.ts
100.00% <100.00%> (ø)

packages/ckb-sdk-rpc/src/Base/pool.ts
100.00% <100.00%> (ø)

packages/ckb-sdk-rpc/src/Base/stats.ts
100.00% <100.00%> (ø)

packages/ckb-sdk-rpc/src/paramsFormatter.ts
100.00% <100.00%> (ø)

packages/ckb-sdk-rpc/src/resultFormatter.ts
100.00% <100.00%> (ø)

packages/ckb-sdk-rpc/src/index.ts
44.00% <0.00%> (-56.00%)
:arrow_down:

... and 30 more


resolver: Filter current state by path

Sometime is needed for a capture to reference just a part of current
state without comparing any value. This change add the possibility to
pass a path to a capture and return a Nmstate with data at that path.
This allow policies like the following:
capture:
  eth1-iface: interfaces.name == "eth1"
  eth1-routes: routes.running.next-hop-interface == "eth1"
  dns: dns-resolver.running
desiredState:
  interfaces:
  - name: eth1
    type: ethernet
    state: up
    ipv4:
      address: "{{ capture.eth1-iface.interfaces.0.ipv4.address }}"
      dhcp: false
      enabled: true
  routes:
    config: "{{ capture.eth1-routes.running }}"
  dns-resolver:
    config: "{{ capture.dns.dns-resolver.running }}"

Signed-off-by: Enrique Llorente<EMAIL_ADDRESS>

Sometime is needed for a capture to reference just a part of current state without comparing any value. This change add the possibility to pass a path to a capture and return a Nmstate with data at that path.
This allow policies like the following:
capture:
  eth1-iface: interfaces.name == "eth1"
  eth1-routes: routes.running.next-hop-interface == "eth1"
  dns: dns-resolver.running
desiredState:
  interfaces:
  - name: eth1
    type: ethernet
    state: up
    ipv4:
      address: "{{ capture.eth1-iface.interfaces.0.ipv4.address }}"
      dhcp: false
      enabled: true
  routes:
    config: "{{ capture.eth1-routes.running }}"
  dns-resolver:
    config: "{{ capture.dns.dns-resolver.running }}"

One of the TODO items we have for nmpolicy is wildcards. Aren't wildcards enough to achieve what this PR is trying to achieve?

dns: dns-resolver.running

Whildcards are not related to capture all the dns config with dns: dns-resolver.running

dns: dns-resolver.running

Whildcards are not related to capture all the dns config with dns: dns-resolver.running

I mean dns-resolver.config.search="*". But as we discussed offline the approach in the PR is more elegant so let's proceed with it.


Apply "interestingness" to all practices and CCGs and show on their dashboards

I think this could use a description

To expand: I think dashboards should not just sort by outlierness, but only show (by default, at least) measures we would deem interesting in alert emails.
See #1434 for more context


Update Organization.yaml

add IMBA https://sagebionetworks.jira.com/jira/servicedesk/projects/NFOSI/queues/custom/8/NFOSI-1201

Thanks!


CI for M1 Mac

I'm trying Bitrise and build errors due to the broken static lib (https://github.com/pion/mediadevices/pull/428) can be reproduced.
https://app.bitrise.io/build/51dbe91e-8d3b-4a8c-a2e3-755a0d6480c3
Bitrise seems having free plan including 300 credits/month and M1 mac build takes 6 credits/run.
https://www.bitrise.io/pricing
Problems:

the free plan doesn't have a feature to manage the repo by multiple users
credits are belong to the user on the free plan

Tried to reach out to you on the Gophers slack, but my company can sponsor this and more of pion. Let's chat there!


Native pull to refresh

Would be nice to have a native pull to refresh feature, because (almost) none of the HTML5 variants feel native and work cross device.
Forum post: https://forums.appgyver.com/#!/steroids:pull-to-refresh

+1

+1

+1

+1

+1

+1, can we start holding our breath yet? :)

+1

+1

+1

+1

OMG +1

+100500

@AndreyAntipov Ionic's feature is not native (which is the scope of this pull request).
You can use the Ionic feature with AppGyver Steroids.

@pre Ah, thank you

+1

+1

+1
I just needed this for my app, and searched google and came here. I guess i will have the refresh button for now.

+1

+1

+1

+1

+1

@pre, @AndreyAntipov I am really new at AppGyver, how do I mix Ionic and AppGyver together? especially for this Pull Down to refresh feature?
Thanks!

@badallen last I saw, mixing both had various issues and bugs, and was not recommended or supported

+1

i don't think ionic js framework is compatible yet with supersonic @badallen . for now you can only use the ionic css framework.
anyone correct me if i'm wrong.

For those using angular - I found a workable solution to having the refresh button:
http://community.appgyver.com/t/pull-to-refresh/3803/13

+1

1+ year old issue, this is madness.

It's still definitely upcoming, just fighting back the Spartan horde of more immediate backlog things. Getting a new native UI feature like this right for both platforms requires work – for example, our initial development sprint hit a problem with Crosswalk WebViews not supporting the view overscroll native event properly... But we're getting there!

:+1:

+1

+1

+1

+1 need! :-)

+1

I am subscribed to notifications on this, getting +1 emails constantly is so annoying, btw +1

+1

+1


Issues with resolving using getaddrinfo (two simultaneous DNS requests from same port)

I have been investigating a DNS lookup issue on my local network that seems to stem from a combination of glibc's implementation of getaddrinfo and Unbound DNS. The problem usually manifests itself in a ~5s delay before a connection is established. I can reliably trigger this condition with the following program:
#include <sys/types.h>
#include <sys/socket.h>
#include <netdb.h>
#include <stdio.h>
#include <unistd.h>

int main(int argc, char *argv[])
{
    struct addrinfo *res;
    int rc=getaddrinfo(argv[1], "http", NULL, &res);

    printf("getaddrinfo returned %d\n", rc);

    if (rc == 0)
        freeaddrinfo(res);
}

When I run this program it looks like this:
$ time ./a.out heise.de
getaddrinfo returned 0

real	0m5.018s
user	0m0.000s
sys	0m0.004s

And (using tcpdump) I see one of two traffic patterns (on both the client and the server). Either the traffic looks like this
18:58:57.473342 IP <IP_ADDRESS>.57832 > <IP_ADDRESS>.53: 12887+ A? heise.de. (26)
18:58:57.473371 IP <IP_ADDRESS>.57832 > <IP_ADDRESS>.53: 44126+ AAAA? heise.de. (26)
18:58:57.475099 IP <IP_ADDRESS>.53 > <IP_ADDRESS>.57832: 44126 1/0/0 AAAA 2a02:2e0:3fe:1001:302:: (54)
18:59:02.478389 IP <IP_ADDRESS>.57832 > <IP_ADDRESS>.53: 12887+ A? heise.de. (26)
18:59:02.479246 IP <IP_ADDRESS>.53 > <IP_ADDRESS>.57832: 12887 1/0/0 A <IP_ADDRESS> (42)
18:59:02.479337 IP <IP_ADDRESS>.57832 > <IP_ADDRESS>.53: 44126+ AAAA? heise.de. (26)
18:59:02.479755 IP <IP_ADDRESS>.53 > <IP_ADDRESS>.57832: 44126 1/0/0 AAAA 2a02:2e0:3fe:1001:302:: (54)

or it looks like this
18:59:12.504525 IP <IP_ADDRESS>.50399 > <IP_ADDRESS>.53: 5644+ A? heise.de. (26)
18:59:12.504581 IP <IP_ADDRESS>.50399 > <IP_ADDRESS>.53: 31252+ AAAA? heise.de. (26)
18:59:12.505954 IP <IP_ADDRESS>.53 > <IP_ADDRESS>.50399: 5644 1/0/0 A <IP_ADDRESS> (42)
18:59:17.509496 IP <IP_ADDRESS>.50399 > <IP_ADDRESS>.53: 5644+ A? heise.de. (26)
18:59:17.510501 IP <IP_ADDRESS>.53 > <IP_ADDRESS>.50399: 5644 1/0/0 A <IP_ADDRESS> (42)
18:59:17.510611 IP <IP_ADDRESS>.50399 > <IP_ADDRESS>.53: 31252+ AAAA? heise.de. (26)
18:59:17.511055 IP <IP_ADDRESS>.53 > <IP_ADDRESS>.50399: 31252 1/0/0 AAAA 2a02:2e0:3fe:1001:302:: (54)

That is, my client (<IP_ADDRESS>; Debian 10) sends two requests using the same UDP port, one for the A and one for the AAAA record. However, Unbound (<IP_ADDRESS>; OPNsense 21.1.1) only answers one of them initially. Later both of those requests are served. Furthermore, when enabling request logging in Unbound, only one of the initial two requests is logged.
Another interesting observation, is that successive calls to getaddrinfo for don't have the same problem (even when looking up diffrent domains).
This problem disappears when using options single-request in /etc/resolve.conf. However, I can't do that for every affected machine in my home: I have a Synology NAS and it is affected as well.
This problem seems to be well known (e.g. https://bugzilla.redhat.com/show_bug.cgi?id=459756), but I did not find an issue about it in this tracker. Appologies if this is a duplicate.
I also took a look through the code base to see if I can fix this bug myself, but I don't really have a clue. My best bet is that some events are dropped when requests arrive nearly simultaneously. I don't know what the reason is, but tcpdump shows that sucessive calls have a longer delay between the DNS requests.
19:56:44.760471 IP <IP_ADDRESS>.44566 > <IP_ADDRESS>.53: 48161+ A? heise.de. (26)
19:56:44.760500 IP <IP_ADDRESS>.44566 > <IP_ADDRESS>.53: 57895+ AAAA? heise.de. (26)
19:56:44.761752 IP <IP_ADDRESS>.53 > <IP_ADDRESS>.44566: 57895 1/0/0 AAAA 2a02:2e0:3fe:1001:302:: (54)
19:56:49.765386 IP <IP_ADDRESS>.44566 > <IP_ADDRESS>.53: 48161+ A? heise.de. (26)
19:56:49.766307 IP <IP_ADDRESS>.53 > <IP_ADDRESS>.44566: 48161 1/0/0 A <IP_ADDRESS> (42)
19:56:49.766367 IP <IP_ADDRESS>.44566 > <IP_ADDRESS>.53: 57895+ AAAA? heise.de. (26)
19:56:49.766848 IP <IP_ADDRESS>.53 > <IP_ADDRESS>.44566: 57895 1/0/0 AAAA 2a02:2e0:3fe:1001:302:: (54)
19:56:49.768002 IP <IP_ADDRESS>.39166 > <IP_ADDRESS>.53: 64667+ A? google.com. (28)
19:56:49.768940 IP <IP_ADDRESS>.53 > <IP_ADDRESS>.39166: 64667 1/0/0 A <IP_ADDRESS> (44)
19:56:49.769021 IP <IP_ADDRESS>.39166 > <IP_ADDRESS>.53: 64673+ AAAA? google.com. (28)
19:56:49.769838 IP <IP_ADDRESS>.53 > <IP_ADDRESS>.39166: 64673 1/0/0 AAAA 2a00:1450:4016:806::200e (56)

Unbound should be able to answer two request from the same port at the same time.  Because lookups vary in lookup time, especially when the cache is empty, the response to the two queries is going to take a different amount of time, and it should answer the first and then the next one when it is done.
If unbound does not log both requests, that means they did not arrive at the unbound query port.  Only one arrived.  Are you using TCP and an older version of unbound?  That would process the queries one by one.
For UDP, that means the message did not arrive. Unbound logs the request after it did the udp receive, so if it does not log the query, then it likely did not receive anything on the UDP socket.  This is weird, since your tcp dump shows it.  How is that possible?  Is there some sort of VM and firewall or connection tracking?

Yeah, this is weird.  I am checked that it's using UDP (tcpdump wasn't really obvious about it). I also ran tcpdump on the opnsense box too and it showed the same result, so the packet did at least arrive on the interface. The default firewall for that interface is configured, but it allows everything on that interface.
Maybe a race condition?

Okay, disabling the firewall completly fixes the issue... I'll report this in the opnsense issue tracker instead. Thanks!

https://github.com/opnsense/core/issues/4708


Use of plugin as a singleton

In this current form, this plugin requires that the user create an analytics instance and use it throughout the app, which requires either

using a global analytics variable (which is not recommended and is an antipattern)
wrapping it with a singleton class(inconvenient)
dependency injecting it (using prop drilling or state management solutions).

Rather than this, it would be beneficial if it was a singleton instance like Segment.Instance just like how Firebase analytics does it with FirebaseAnalytics.Instance

Hi @DebkanchanSamadder  thank you for your report, we start looking into this and we will check your PR.

Not doing singletons is part of the design of the library to enable support for multiple clients by default. This is better to handle per app at the moment.


Implement global debug print function

It would make sense to have a possibility to switch on / off all serial output debug messages at once. I will research if there is such a method in mbed. Otherwise we can define our own macro DEBUG_PRINT (or is there something more suitable from C++ world, @hogthrob ?) in the main.h file.

Sounds good. Would do the job. Probably a C++ crack would have some ideas how to do this without the preprocessor, but your proposal will do the job just fine.

This approach sounds good. I would suggest we implement a 4th function print_comms in order to set the comms debug messages separately.


[Humble] MicroROS2 does not support serial on Windows

Describe the bug
Humble includes MicroROS2. However, MicroROS2 does not support serial on Windows!
https://github.com/eProsima/Micro-XRCE-DDS-Agent/blob/master/CMakeLists.txt
AB#509360

Just in case it may help someone... i've added the Serial support for MicroROS2 on Windows for us, working for us but with no strong guarantee it will work in any case. See PR https://github.com/eProsima/Micro-XRCE-DDS-Agent/pull/349


fix(ui): RHIDP-2044 enable frontend plugin loading

Description
This change removes the authentication requirement for the scalprum backend as it's used to serve static javascript content and related manifests.  This commit also adds identity support to the dynamic plugins info list frontend and migrates the backend to use the httpAuth service.
This change adds the new upstream guest authentication provider to the backend.  This provider is enabled by adding a "guest" entry to the auth.providers map.  This change also removes the dynamic-plugins-info-backend e2e test, as
it relies on an unauthenticated endpoint that isn't available anymore.  This functionaly is already covered by the UI e2e test and the component's unit test.
Which issue(s) does this PR fix

Fixes RHIDP-2044
Fixes RHIDP-2043

PR acceptance criteria
Please make sure that the following steps are complete:

[ ] GitHub Actions are completed and successful
[ ] Unit Tests are updated and passing
[ ] E2E Tests are updated and passing
[ ] Documentation is updated if necessary (requirement for new features)
[ ] Add a screenshot if the change is UX/UI related

How to test changes / Special notes to the reviewer
This PR also adds the new upstream guest authentication provider.  You should be able to log into the app using this provider (or github/keycloak etc), click on the Administration tab and see the list of available plugins as a regular user.  There should be no HTTP 401 errors logged to the browser console when accessing the scalprum backend.  To use the guest authentication provider it now must be explicitly enabled in the auth provider map like so:
# When running locally with "yarn start" only this is needed
auth:
  providers:
    guest: {}

# When running against a built image:
auth:
  providers:
    guest:
      dangerouslyAllowOutsideDevelopment: true

/lgtm

Looks like fixing the tests could require fixing RHIDP-2043 as well, or the test must be adjusted to use a proper login and not the guest login.

/retest

Looking into the test failure, had success running locally Friday but figured I couldn't be so lucky as to have the tests pass first try :smile:

Think this quay e2e test is failing due to a different issue, @gustavolira is there an issue for fixing this test?:

/retest

/lgtm

I deployed the image build from this PR on our OCP cluster where RHDP has been deployed using the Helm chart and pod is crashing as it cannot read an id
Loading config from MergedConfigSource{FileConfigSource{path="/opt/app-root/src/app-config.yaml"}, FileConfigSource{path="/opt/app-root/src/app-config.example.yaml"}, FileConfigSource{path="/opt/app-root/src/app-config.example.production.yaml"}, FileConfigSource{path="/opt/app-root/src/dynamic-plugins-root/app-config.dynamic-plugins.yaml"}, FileConfigSource{path="/opt/app-root/src/app-config-rhdh.yaml"}, FileConfigSource{path="/opt/app-root/src/app-config-from-configmap.yaml"}, EnvConfigSource{count=1}}
(node:1) MaxListenersExceededWarning: Possible EventTarget memory leak detected. 11 abort listeners added to [AbortSignal]. Use events.setMaxListeners() to increase limit
(Use `node --trace-warnings ...` to show where the warning was created)
skipping '/opt/app-root/src/dynamic-plugins-root/app-config.dynamic-plugins.yaml' since it is not a directory
failed to load dynamic plugin manifest from '/opt/app-root/src/dynamic-plugins-root/lost+found' [Error: ENOENT: no such file or directory, open '/opt/app-root/src/dynamic-plugins-root/lost+found/package.json'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/opt/app-root/src/dynamic-plugins-root/lost+found/package.json'
}
2024-05-07T08:49:55.016Z backstage info Found 6 new secrets in config that will be redacted
2024-05-07T08:49:55.020Z backstage info skipping '/opt/app-root/src/dynamic-plugins-root/app-config.dynamic-plugins.yaml' since it is not a directory
2024-05-07T08:49:55.025Z backstage error failed to load dynamic plugin manifest from '/opt/app-root/src/dynamic-plugins-root/lost+found' ENOENT: no such file or directory, open '/opt/app-root/src/dynamic-plugins-root/lost+found/package.json' errno=-2 code=ENOENT syscall=open path=/opt/app-root/src/dynamic-plugins-root/lost+found/package.json stack=Error: ENOENT: no such file or directory, open '/opt/app-root/src/dynamic-plugins-root/lost+found/package.json'
2024-05-07T08:49:55.923Z backstage info loaded dynamic backend plugin 'backstage-plugin-kubernetes-backend-dynamic' from 'file:///opt/app-root/src/dynamic-plugins-root/backstage-plugin-kubernetes-backend-dynamic-0.16.4'
2024-05-07T08:49:56.048Z backstage info loaded dynamic backend plugin 'backstage-plugin-scaffolder-backend-module-azure-dynamic' from 'file:///opt/app-root/src/dynamic-plugins-root/backstage-plugin-scaffolder-backend-module-azure-dynamic-0.1.8'
2024-05-07T08:49:56.102Z backstage info loaded dynamic backend plugin 'backstage-plugin-scaffolder-backend-module-bitbucket-cloud-dynamic' from 'file:///opt/app-root/src/dynamic-plugins-root/backstage-plugin-scaffolder-backend-module-bitbucket-cloud-dynamic-0.1.6'
2024-05-07T08:49:56.126Z backstage info loaded dynamic backend plugin 'backstage-plugin-scaffolder-backend-module-bitbucket-server-dynamic' from 'file:///opt/app-root/src/dynamic-plugins-root/backstage-plugin-scaffolder-backend-module-bitbucket-server-dynamic-0.1.6'
2024-05-07T08:49:56.167Z backstage info loaded dynamic backend plugin 'backstage-plugin-scaffolder-backend-module-gerrit-dynamic' from 'file:///opt/app-root/src/dynamic-plugins-root/backstage-plugin-scaffolder-backend-module-gerrit-dynamic-0.1.8'
2024-05-07T08:49:56.300Z backstage info loaded dynamic backend plugin 'backstage-plugin-scaffolder-backend-module-github-dynamic' from 'file:///opt/app-root/src/dynamic-plugins-root/backstage-plugin-scaffolder-backend-module-github-dynamic-0.2.6'
2024-05-07T08:49:56.430Z backstage info loaded dynamic backend plugin 'backstage-plugin-scaffolder-backend-module-gitlab-dynamic' from 'file:///opt/app-root/src/dynamic-plugins-root/backstage-plugin-scaffolder-backend-module-gitlab-dynamic-0.3.2'
2024-05-07T08:49:57.050Z backstage info loaded dynamic backend plugin 'backstage-plugin-techdocs-backend-dynamic' from 'file:///opt/app-root/src/dynamic-plugins-root/backstage-plugin-techdocs-backend-dynamic-1.10.3'
2024-05-07T08:49:57.052Z backstage info loaded dynamic backend plugin '@janus-idp/backstage-scaffolder-backend-module-quay-dynamic' from 'file:///opt/app-root/src/dynamic-plugins-root/janus-idp-backstage-scaffolder-backend-module-quay-dynamic-1.3.10/alpha'
2024-05-07T08:49:57.094Z backstage info loaded dynamic backend plugin '@janus-idp/backstage-scaffolder-backend-module-regex-dynamic' from 'file:///opt/app-root/src/dynamic-plugins-root/janus-idp-backstage-scaffolder-backend-module-regex-dynamic-1.3.10/alpha'
2024-05-07T08:49:57.173Z backstage info loaded dynamic backend plugin '@qshift/plugin-quarkus-backend-dynamic' from 'file:///opt/app-root/src/dynamic-plugins-root/qshift-plugin-quarkus-backend-dynamic-0.1.28/alpha'
2024-05-07T08:49:57.260Z backstage info loaded dynamic backend plugin 'roadiehq-backstage-plugin-argo-cd-backend-dynamic' from 'file:///opt/app-root/src/dynamic-plugins-root/roadiehq-backstage-plugin-argo-cd-backend-dynamic-3.0.0'
2024-05-07T08:49:57.342Z backstage info loaded dynamic backend plugin 'roadiehq-scaffolder-backend-argocd-dynamic' from 'file:///opt/app-root/src/dynamic-plugins-root/roadiehq-scaffolder-backend-argocd-dynamic-1.1.25'
2024-05-07T08:49:57.353Z backstage info loaded dynamic backend plugin 'roadiehq-scaffolder-backend-module-http-request-dynamic' from 'file:///opt/app-root/src/dynamic-plugins-root/roadiehq-scaffolder-backend-module-http-request-dynamic-4.1.10'
2024-05-07T08:49:57.442Z backstage info loaded dynamic backend plugin 'roadiehq-scaffolder-backend-module-utils-dynamic' from 'file:///opt/app-root/src/dynamic-plugins-root/roadiehq-scaffolder-backend-module-utils-dynamic-1.14.1'
2024-05-07T08:49:57.457Z rootHttpRouter info Listening on :7007
2024-05-07T08:49:57.483Z auth info Enabled Provider Factories : {}
2024-05-07T08:49:57.507Z scalprum info Loaded dynamic frontend plugin 'backstage-plugin-kubernetes' from 'file:///opt/app-root/src/dynamic-plugins-root/backstage-plugin-kubernetes-0.11.8'
2024-05-07T08:49:57.507Z scalprum info Loaded dynamic frontend plugin 'backstage-plugin-techdocs' from 'file:///opt/app-root/src/dynamic-plugins-root/backstage-plugin-techdocs-1.10.3'
2024-05-07T08:49:57.507Z scalprum info Loaded dynamic frontend plugin '@janus-idp/backstage-plugin-rbac' from 'file:///opt/app-root/src/dynamic-plugins-root/janus-idp-backstage-plugin-rbac-1.17.4'
2024-05-07T08:49:57.507Z scalprum info Loaded dynamic frontend plugin '@janus-idp/backstage-plugin-tekton' from 'file:///opt/app-root/src/dynamic-plugins-root/janus-idp-backstage-plugin-tekton-3.5.18'
2024-05-07T08:49:57.507Z scalprum info Loaded dynamic frontend plugin '@janus-idp/backstage-plugin-topology' from 'file:///opt/app-root/src/dynamic-plugins-root/janus-idp-backstage-plugin-topology-1.18.14'
2024-05-07T08:49:57.508Z scalprum info Loaded dynamic frontend plugin '@qshift/plugin-quarkus' from 'file:///opt/app-root/src/dynamic-plugins-root/qshift-plugin-quarkus-0.1.28'
2024-05-07T08:49:57.508Z scalprum info Loaded dynamic frontend plugin '@qshift/plugin-quarkus-console' from 'file:///opt/app-root/src/dynamic-plugins-root/qshift-plugin-quarkus-console-0.1.28'
2024-05-07T08:49:57.508Z scalprum info Loaded dynamic frontend plugin 'roadiehq-backstage-plugin-argo-cd' from 'file:///opt/app-root/src/dynamic-plugins-root/roadiehq-backstage-plugin-argo-cd-2.6.4'
2024-05-07T08:49:57.512Z proxy info [HPM] Proxy created: /quay/api  -> https://quay.io/
2024-05-07T08:49:57.512Z proxy info [HPM] Proxy rewrite rule created: "^/api/proxy/quay/api/?" ~> "/"
2024-05-07T08:49:57.513Z proxy warn skipped configuring /sonarqube due to Proxy target for route "/sonarqube" must be a string, but is of type undefined
2024-05-07T08:49:57.513Z proxy warn skipped configuring /jenkins/api due to Proxy target for route "/jenkins/api" must be a string, but is of type undefined
2024-05-07T08:49:57.513Z proxy warn skipped configuring /jira/api due to Proxy target for route "/jira/api" must be a string, but is of type undefined
2024-05-07T08:49:57.513Z proxy warn skipped configuring /acr/api due to Proxy target for route "/acr/api" must be a string, but is of type undefined
2024-05-07T08:49:57.513Z proxy warn skipped configuring /jfrog-artifactory/api due to Proxy target for route "/jfrog-artifactory/api" must be a string, but is of type undefined
2024-05-07T08:49:57.513Z proxy info [HPM] Proxy created: /pagerduty  -> https://api.pagerduty.com
2024-05-07T08:49:57.513Z proxy info [HPM] Proxy rewrite rule created: "^/api/proxy/pagerduty/?" ~> "/"
2024-05-07T08:49:57.514Z proxy warn skipped configuring /dynatrace due to Proxy target for route "/dynatrace" must be a string, but is of type undefined
2024-05-07T08:49:57.514Z proxy warn skipped configuring /nexus-repository-manager due to Proxy target for route "/nexus-repository-manager" must be a string, but is of type undefined
2024-05-07T08:49:57.545Z auth info Configuring "database" as KeyStore provider
2024-05-07T08:49:57.551Z scaffolder info Starting scaffolder with the following actions enabled quay:create-repository, regex:replace, quarkus:app:create, quarkus:quickstart:clone, publish:azure, publish:bitbucketCloud, bitbucket:pipelines:run, publish:bitbucketServer, publish:bitbucketServer:pull-request, publish:gerrit, publish:gerrit:review, github:actions:dispatch, github:autolinks:create, github:deployKey:create, github:environment:create, github:issues:label, github:repo:create, github:repo:push, github:webhook, publish:github, publish:github:pull-request, gitlab:group:ensureExists, gitlab:issues:create, gitlab:projectAccessToken:create, gitlab:projectDeployToken:create, gitlab:projectVariable:create, gitlab:repo:push, publish:gitlab, publish:gitlab:merge-request, http:backstage:request, roadiehq:utils:zip, roadiehq:utils:sleep, roadiehq:utils:fs:write, roadiehq:utils:fs:append, roadiehq:utils:json:merge, roadiehq:utils:merge, roadiehq:utils:fs:parse, roadiehq:utils:fs:replace, roadiehq:utils:serialize:yaml, roadiehq:utils:serialize:json, roadiehq:utils:jsonata, roadiehq:utils:jsonata:yaml:transform, roadiehq:utils:jsonata:json:transform, argocd:create-resources, fetch:plain, fetch:plain:file, fetch:template, debug:log, debug:wait, catalog:register, catalog:fetch, catalog:write, fs:delete, fs:rename
/opt/app-root/src/node_modules/@backstage/backend-app-api/dist/index.cjs.js:1768
            provides: Array.from(moduleInit.consumes).map((c) => c.id)
                                                                   ^

TypeError: Cannot read properties of undefined (reading 'id')
    at /opt/app-root/src/node_modules/@backstage/backend-app-api/dist/index.cjs.js:1768:68
    at Array.map (<anonymous>)
    at /opt/app-root/src/node_modules/@backstage/backend-app-api/dist/index.cjs.js:1768:55
    at Array.map (<anonymous>)
    at /opt/app-root/src/node_modules/@backstage/backend-app-api/dist/index.cjs.js:1762:31
    at Array.map (<anonymous>)
    at BackendInitializer.doStart_fn (/opt/app-root/src/node_modules/@backstage/backend-app-api/dist/index.cjs.js:1758:18)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async BackendInitializer.start (/opt/app-root/src/node_modules/@backstage/backend-app-api/dist/index.cjs.js:1611:5)
    at async BackstageBackend.start (/opt/app-root/src/node_modules/@backstage/backend-app-api/dist/index.cjs.js:1881:5)

Node.js v18.18.2

@cmoulliard This PR doesn't change the backend loading really so I don't see how this would have been introduced by this particular code change.  Keep in mind that there's also been a few other changes merged in the past couple days as well along with dependency updates.  I think probably the first step in troubleshooting this issue would be to start disabling external plugins first and see if the backend loads or not with only the provided plugins.  Please open an issue if this problem persists.


Mismatch of dcsr.prv when interrupt followed by a debug request

Observed Behavior

When there is an interrupt from U-mode followed by debug request, Ibex fetches the first instruction of the handler and when the debug request comes in, it takes it and jumps to corresponding address. Privilege mode already switched to M-mode and after debug request, when dcsr is read, dcsr.prv is 'b11.

Expected Behavior

Since we are feeding Spike with debug request or nmi interrupt (when multiple interrupts happen back to back before previous interrupt handler's first instruction execution), it doesn't have the transition from U-mode to M-mode, so we see dcsr.prv = 'b00 from Spike.
It seems that changes might be needed in Ibex cosim.
Steps to reproduce the issue

cd dv/uvm/core_ibex
make --keep-going IBEX_CONFIG=opentitan SIMULATOR=xlm ISS=spike ITERATIONS=1 SEED=23054 TEST=riscv_assorted_traps_interrupts_debug_test WAVES=1

My Environment

Operating system:

Ubuntu Linux 20.04
Version of the Ibex source code:

ba527fed80ccd3d98f47f01a712dbb60f5d53860 (Draft PR)
/cc @GregAC @hcallahan-lowrisc @ctopal

estimate 8

estimate range: 4 - 8


Integration Test - Release - 2022/05/06 08:07:46

Auto create for integration test. IssueCommandFlow

#pri1

Just type '#pri3'

#pri2

#pri3

#assign PRMergerTest1

#assign NonAllowedUser

#reassign PRMergerTest2

#reassign NonAllowedUser

GitHub user PRMergerTest2 has been removed from the MicrosoftDocs organization, so they were automatically removed as an assignee.

The following users don't have valid GitHub IDs, or are not collaborators on this repo: nonalloweduser

#please-close

#unassign PRMergerTest1

#unassign NonAllowedUser


Missing unprofitable trade message

I am hitting an existing bid ( it is a real bid - yours @bthaile)

added- closing


WIP: Implement instance-independent manifest caching

This pull request implements caching of manifests to the bucket used for layer storage. Manifests are cached based on a key that is determined as a combination of the package source and image contents.
Note that manifests will only be cached for package sources which are not moving targets, i.e. either a full git commit hash of a private package repository or of nixpkgs.
This prevents rebuilds of identical manifests between different instances of Nixery.
See individual commits for details. This relates to #50 in that it implements the first step of the new proposed build process.

Note that the CI build is running against a moving target (nixos-unstable) and will not cache the manifest.


Start to address #1236 (Django HTML indentation)

Automated message from Dropbox CLA bot
@showell, it looks like you've already signed the Dropbox CLA. Thanks!

see #1236

Merged, thanks @showell!


Update SB SDK to T2

Heaths has reviewed this in another PR-Azure-Samples/key-vault-dotnet-manage-key-vaults#8
we decide to use await for async code, followed by .ConfigureAwait(false).

@jsquire - Can you please review?

I'm going to avoid going through a lot of the detail here, as I think this sample mirrors the feedback that I left in another.     Please see my thoughts in this sample.   To reflect the most important bits:

The sample is unfocused;  it's not sure whether it wants to show off a management library or a client library.   We should be working against a tight focus and adapting the sample to that purpose.   In either case, we should not be using Fluent as it is no longer under active development and is only receiving critical fixes.
If this sample is attempting to demonstrate "how do you create Service Bus resources using the management libraries" then we should strip out the Azure.Messaging.ServiceBus use and wait to update until Azure.ResourceManager.ServiceBus is available.
If this sample is attempting to demonstrate "how do I use the administration features of Azure.Messaging.ServiceBus to create resources like queues and topics in my existing Service Bus namespace" then we should strip out all Fluent and other management use,  bootstrap using an ARM template to create the namespace and demonstrate the administration client similar to how this sample does.

@jongio: You may want to weigh in here, as I think this is salient to both the core content of the sample as well as the scheduling. Thoughts?

@jsquire - Could you please help us close this PR? Because Wantedfast has resigned and we don't have permissions to modify this PR. We will create a new PR to replace it later.

PR https://github.com/Azure-Samples/service-bus-dotnet-manage-queue-with-advanced-features/pull/5 replaces this PR https://github.com/Azure-Samples/service-bus-dotnet-manage-queue-with-advanced-features/pull/4, so we can close this PR.


Remove CreateLinkedTokenSource

Resolves  #407

That might work. @halter73?

Need a CancellationTokenSourceSlim that can have its registrations reset; unfortunately  CancellationTokenSource is pretty heavyweight and CancellationToken's constructor is internal and only takes CancellationTokenSource :(

Or a dump registrations on CancellationToken

Added https://github.com/dotnet/coreclr/issues/2113

I think this changes behavior slightly. If Connection.Abort was called between requests and an app registered a callback with the RequestAborted token on the next request, the callback would be triggered immediately.
In the end, I don't think this matters since both the request and response are poisoned. Just thought it would be worth mentioning that the behavior changes slightly.

The next request and response streams aren't poisoned I guess, but we still close the socket and poison SocketInput so I still think we're OK.

If Connection.Abort was called between requests and an app registered a callback with the RequestAborted token on the next request, the callback would be triggered immediately.

Isn't that correct because that request if it managed to start would be correctly aborted? Or do you mean it should be receiving a different error?

@benaadams That quote was me trying to describe the old behavior. I don't think the abort callback for the next request will be called after this change.

Ah kk

@stephentoub's added changes completely clear up the allocations


FileSystemClient.get_paths() throws a ContainerNotFound error even when container exists

Package Name: azure-storage-file-datalake
Package Version: 12.6.0
Operating System: OSX
Python Version: 3.9

Describe the bug
FileSystemClient.get_paths() throws a ContainerNotFound error even thought the container exists
To Reproduce
Steps to reproduce the behavior:
This code throws a ContainerNotFound error every time:
from azure.storage.filedatalake import FileSystemClient

fsc = FileSystemClient( account_url=ACCOUNT_URL, file_system_name=CONTAINER_NAME, credential=SAS_TOKEN)
paths = fsc.get_paths()
for path in paths:
    print("\t" + path.name)

but this equivalent code from the azure-storage-blob does not:
from azure.storage.blob import ContainerClient

container_client = ContainerClient( account_url=ACCOUNT_URL, container_name=CONTAINER_NAME, credential=SAS_TOKEN,)
blob_list = container_client.list_blobs()
for blob in blob_list:
    print("\t" + blob.name)

and for what it's worth, I created the SAS token by logging in to the azure cli az login with a user account with both owner and contributor permissions on the storage account, and used the following python code:
import requests
from datetime import datetime, timezone, timedelta
from azure.mgmt.storage import StorageManagementClient
from azure.identity import AzureCliCredential
from azure.storage.blob import generate_account_sas, ResourceTypes

# Generate a temporary and specific SAS token
azure_creds = AzureCliCredential()
storage_client = StorageManagementClient(azure_creds, AZURE_SUBSCRIPTION_GUID)
storage_keys = storage_client.storage_accounts.list_keys(RESOURCE_GROUP_NAME, STORAGE_ACCOUNT)
rr = requests.get("http://ipv4.icanhazip.com/")
my_ip = rr.text.rstrip("\n")
SAS_TOKEN = generate_account_sas(
    account_name=STORAGE_ACCOUNT,
    container_name=CONTAINER_NAME,
    start=datetime.now(timezone.utc) - timedelta(minutes=1),
    expiry=datetime.now(timezone.utc) + timedelta(hours=1),
    account_key=storage_keys.keys[0].value,
    permission="rl",
    ip=my_ip,
    resource_types=ResourceTypes(container=True, object=True, service=True),
)

Expected behavior
FileSystemClient.get_paths().next() should get a path from a ADLS container without throwing an error
Screenshots
N/A
Additional context
N/A

@jdthorpe  Thanks for the issue - we will investigate this asap
@jalauzon-msft Can you take a look?

Hi @jdthorpe Jason, I was looking into this issue alongside @jalauzon-msft and we were able to successfully reproduce your error.
After further testing, we have discovered that there is some odd service behavior with SAS tokens generated using generate_account_sas(). We noticed that you are using generate_account_sas() but also providing a container_name, and so below we have provided some workarounds that will allow you to generate a SAS token at a container-level (which seems to be sufficient for your use-case).
Note: In your provided code, we are unsure of your value for ACCOUNT_URL, but please note that when using the Datalake library, the account_url should be in the pattern of: 'https://<ACCOUNT_NAME>.dfs.core.windows.net',
while using the Blob library should be in the pattern of 'https://<ACCOUNT_NAME>.blob.core.windows.net'.
DataLake Example:
from azure.storage.filedatalake import generate_file_system_sas
sas_token = generate_file_system_sas(
        account_name=STORAGE_ACCOUNT,
        file_system_name=CONTAINER_NAME,
        expiry=datetime.now(timezone.utc) + timedelta(hours=1),
        credential=account_key,
        permission="rl",
    )

Blob Example:
from azure.storage.blob import generate_container_sas
sas_token = generate_container_sas(
        account_name=STORAGE_ACCOUNT,
        container_name=CONTAINER_NAME,
        expiry=datetime.now(timezone.utc) + timedelta(hours=1),
        account_key=account_key,
        permission="rl",
    )

And with the above samples, you can add back in any parameters necessary that I have omitted from the sample (i.e. ip=, etc.)
Hopefully this will help you resolve this issue, and we have already started an internal discussion with the service team regarding the odd service behavior with account SAS tokens and will update you here if we have any follow-ups.
Thanks!

Thanks!  Yes, this resolves my specific issue.
As a user, I'm often confused by the fact that the account url sometimes matters and sometimes doesn't, in part because of the fact that at least some of the functions in the filedatalake library are just thin wrappers around the blob library (for example, DataLakeServiceClient.list_file_systems() just calls self._blob_service_client.list_containers())
As an aside, I know that this is out of scope of this question, but it would be great if there were some hinting around the reason for auth errors.  For example, an error like ("requesting a resource from dfs.core.windows.net but the token is aurhorized for a resource in blob.core.windows.net" or "request was made from IP xx.xx.xx.xx but token is authorized for yy.yy.yy.yy" instead of the generic "Server failed to authenticate the request".  Helpful error messages like that could have saved me hours and hours of frustration (and would certainly save me hours in the future too).

Hi @jdthorpe Jason, I'm glad you were able to resolve the issue and thanks for the additional feedback.
The interaction between blob and datalake can be a confusing topic but the general recommendation is to always use blob.core.windows.net URLs with the blob SDK and dfs.core.windows.net URLs with the datalake SDK. While some operations are interchangeable, this should ensure all requests work as expected. That being said, we are considering adding a feature in the near future where, at least the datalake SDK, will accept either a blob or dfs account URL and do the "translation" for the user. I believe other languages have a similar feature.
As for auth error messages, this is managed almost entirely by the service. Auth error messages can be tricky since there are security concerns with giving too much information in the error, etc. The service team has been working on improving the error messages where they can and has made some improvements in certain scenarios. Your points about non-matching SAS params (like IP) seem like valid areas for improvement. We can relay your feedback to the service team, thanks!


Re-add undefined assignability check

Follow up to #53490 (refer to @ahejlsberg's comment).

Can you explicitly add the test from: https://github.com/microsoft/TypeScript/pull/53490#issuecomment-1487305036

Hm, that is effectively the right test, yes. It sounds like maybe everyone has a different idea about the desired behavior? Or, is this test's settings matrix missing noImplicitReturns?

Hmmm. I think it would make sense to add // @noImplicitReturns: true, false to these and these.


Update extensions.json

Remove editorconfig plugin from recommended plugins, it's built into VSCode.

I thought that was the case too but then tested it and noticed that without the extension, certain .editorconfig options aren't followed. Maybe I'm missing something though?
Here's how I tested: I disabled the extension and hit Enter inside a code block, and it intents with spaces even with the following config:
[*]
indent_style = tab

Turning the extension on correctly inserts tabs.

Closing this for the reasons I mentioned previously.


about the discriminator

hi,thank you for your great work,
can i ask your discriminator architecture?It seems that you just use the reconstruction loss about image and mask to constrain the input and output mask shape,how about the reconstruction loss doesn't work well ?do you have any discriminator about the constrain between input and mask shape?

Hi, we have 2 discriminators, whose structures are similar to EG3D, one only takes RGB as input, and the other takes RGB + label map as input. Please check our paper for more details.


[Bug] Datahandler Type Error

I have the following error

Type 'DataHandler<{ id: string; (some other columns) startDate: Date; endDate: Date; (more columns) ... 7 more ...;  }>' is missing the following properties from type 'DataHandler': triggerHandler, onChange, invalidate, setTotalRows

I have redacted some of the database information in the above error message and the sample table below but otherwise it's only happening for the RowsPerPage and Pagination Component. Both components came from here. It doesn't affect the overall use of it, it's just a nagging error.  Let me know if you need more info.

		<Search {handler} />
		<RowsPerPage {handler} /> // issue here

			placeholder/Th>
			placeholder/Th>

		{#each $rows as row}

				{row.placeholder}
				{row.placeholder}

						More info

		{/each}

	<RowCount {handler} />
	<Pagination {handler} /> // issue here

Oh you would be correct. After I remove the remote and the handler.invalidate();  from both files, the error goes away.


Bot: Allow for misc text after the !rules alias call

For instance if we wish to link to a set of rules + mention the one we're sending them to.  This allows for command usage like !rules 5 6 @tagptroll1

Closed by #723


Illuminate\Foundation\Console\ClearCompiledCommand uses methods not defined in contract

See https://github.com/laravel/framework/blob/5.0/src/Illuminate/Foundation/Console/ClearCompiledCommand.php#L28
Illuminate\Foundation\Console\ClearCompiledCommand::fire() uses two methods that are actually not part of the Illuminate\Contracts\Foundation\Application interface:
$compiledPath = $this->laravel->getCachedCompilePath(); $servicesPath = $this->laravel->getCachedServicesPath();
As the command objects depend on the Application contract / interface only (https://github.com/laravel/framework/blob/5.0/src/Illuminate/Console/Command.php#L382), not the Illuminate\Foundation\Application implementation, should any commands rely on methods not available in the interface?
The ClearCompiledCommand::fire() seems to be tightly-coupled to the implementation class, not the interface.

Adding methods to interfaces is a breaking change and could result in fatal errors. We'd accept a pull to 5.1 though.

This should not be closed. Having the command depend on the interface means right now this breaks on any scenario where the Application object is not the default Laravel one, but does adhere to Illuminate\Contracts\Foundation\Application. Not fixing this is as problematic as accepting the fix, as both BC change and bug are edge use cases.

It was closed because I'd requested a pull request to go to 5.1.


Add babel-register to devDependencies

Dumb small pull request but babel-register isn't in package.json so npm test was failing. Added it.

Thanks!

I also ran into this issue on node@4.


Send its own errors to fields and display it instantly

Hi, i'm working with a lot of third party to get the data used to populate my forms (like select options for example) and i would like to display my errors messages under the fields as error validation do it. But i can't find a way with form.io to set the error status of a field to allow me to display such message.
Is there a way to do it?
Thanks in advance for your answer and sorry for my possibly bad english.

Hello,
You can accomplish this with our Custom Error Message on the validation tab of most of our components. This will allow you to customize the error message that displays underneath the field and override the existing.
Here is a screenshot of where you can find the custom error message textfield.
https://www.screencast.com/t/YbH8xqMt

Hi Will, thanks for your answer,
I've already explore this but my problem is to display errors whenever i want on a field, not only when change, blur or submit event is triggered, and after form is rendered. Is there a way to do this, with the refresh properties for example?

Probably the best way to do this right now is to implement options.hooks.customValidation. This only runs on submit but can be used to do asynchronous validation and set custom messages on fields. We don't have lots of documentation around this yet but you can see the code here: https://github.com/formio/formio.js/blob/master/src/Webform.js#L1186

Thanks for your time Randall, i will take this as final answer, and will conclude that it's not possible right now to manage my errors exactly like i want.
I close the issue, thanks to you two.


try these ?

https://primer.style/css/getting-started/
https://vanillaframework.io/docs
https://github.com/tabler/tabler

Could you please give more detail about this issue?


chore(v2): remove useless stylelint-copyright peerDependency

Motivation
The dep stayed on older version alpha 66 after this change: https://github.com/facebook/docusaurus/pull/3766#discussion_r527910313
But it seems declaring the peer deps here is not required, so maybe we can just remove it?

@slorber thanks!


keep only loop routes or routes in both directions

add logic for "both directions" and loops here: https://github.com/MetropolitanTransportationCommission/RegionalTransitDatabase/blob/simplify/R/examples/example_get_hf_geoms.R#L79-L81

check on why route 48 is included even though it is only valid for pm headways.


Lcg/node utf8 sanitize

This patch cleans up any bad utf8 data in the node.save so that node.save will never throw a UTF8 exception.

@chef/client-core @chef/client-engineers this should stop all the node.save utf8 exceptions.

how is bad utf8 data cleaned up? just ignored?

via str.encode!("utf-8", "binary", :undef => :replace)
https://github.com/chef/ffi-yajl/blob/master/lib/ffi_yajl/encoder.rb#L44

so it gets the funny <?> unicode symbol

Is that safe?
Maybe it'd be safe to replace that with an object where we base64 encode the content?
something like
{ '__type__': 'binary', content: '...'}

However that would make decoding more complicated

I think replacing is optimal, it at least remains human readable for anyone who cares to look at it, and realistically this is probably data the user doesn't care about, like some field in AD set to ISO-whateveritis encoding on a machine configured as UTF-8.

define 'safe'?  its valid utf8 json that we render so it passes validation in the server, and gets stored in the database fine.  you lose data, but its just the bad characters.  when you view the fields later you'll get a '?' for a single bad character in a name (which is easy to diagnose and fix) or else you'll see a pile of garbage for binary that got rendered to utf8.  and at this level we don't know if its binary and should be hex encoded.  the use case i care more about is someone's GECOS name in europe with a latin-1 character that isn't valid utf8 and base64 encoding that is real silly.
if someone really cares about the binary data being rendered accurately then ohai should be fixed to base64 encode it.  this enables a good bug report on that since we'll get "hey, node['windows']['registry']['silliness'] is garbage, looks like its binary data being managled by utf8 can we fix that to base64 encode it?" rather than "why am i getting bad utf8 token ???a?r4???#$? at the end of my chef run?"

That makes sense. I thought you were going after the windows registry binary thing.

:+1: other than Travis

Yeah, travis failures are whack tracking then down now..

so @danielsdeleo @jdmundrawala are you :+1: ?

Yep, :+1:

:+1:


[Bunkr] Add extractor

IMPORTANT: PRs without the template will be CLOSED
Description of your pull request and other information

Add support for bunkr.is (both single files and albums).
Closes #4556
Template

Before submitting a pull request make sure you have:

[x] At least skimmed through contributing guidelines including yt-dlp coding conventions
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8 and ran relevant tests

In order to be accepted and merged into yt-dlp each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Fix or improvement to an extractor (Make sure to add/update tests)
[x] New extractor (Piracy websites will not be accepted)
[ ] Core bug fix/improvement
[ ] New feature (It is strongly recommended to open an issue first)

@rdnkarchiver this is unlikely to be merged as #4556 deemed it to be a piracy site


Remastering a Custom Docker Image overwrites /etc/os-release

https://elemental.docs.rancher.com/customizing/#remastering-a-custom-docker-image includes the following snippet in the Dockerfile:
ARG IMAGE_REPO=norepo
ARG IMAGE_TAG=latest
RUN echo "IMAGE_REPO=${IMAGE_REPO}"          > /etc/os-release && \
    echo "IMAGE_TAG=${IMAGE_TAG}"           >> /etc/os-release && \
    echo "IMAGE=${IMAGE_REPO}:${IMAGE_TAG}" >> /etc/os-release

This entirely replaces the existing /etc/os-release file, so it only includes the IMAGE_* variables, and no longer has the OS name, version, id etc.
Given the elemental teal base image already includes those IMAGE_* variables, maybe something like this would be better?
RUN \
    sed -i -e "s/^IMAGE_REPO=.*/IMAGE_REPO=\"${IMAGE_REPO}\"/g"    /etc/os-release && \
    sed -i -e "s/^IMAGE_TAG=.*/IMAGE_TAG=\"${IMAGE_TAG}\"/g"       /etc/os-release && \
    sed -i -e "s/^IMAGE=.*/IMAGE=\"${IMAGE_REPO}:${IMAGE_TAG}\"/g" /etc/os-release

(Of course, that won't work if those IMAGE_* variables aren't present in the base /etc/os-release file for some reason)

Thanks @tserong, good catch !


Allow configurable endpoint url

Addresses #25

Thank you for the PR @Nintorac! As long as it doesn't break the app's default, it should be fine. I'll add it to my testing workflow and see if any changes need to be made before it's patched in.


Combo box support

i might've forgotten some stuff in the deploy scripts but should be fine otherwise. just edit the japanese strings in the 240 folder and it should work perfectly

Okay, it seems that I have time now. Will check things now and do some changes.
By the way, is the .py script works on Python 2 or 3? The script works on Python 3 and not 2 here. Also, is it possible to encode it to UTF-8 and not Shift-JS again?
Also, I made some changes on the folder structure, if you don't mind.

Okay, did all the needed changes, for now. Merging.


PEAR-2185 - Error handling modal does not appear on summary page

Description
Move cohort error modal up so it works on pages with cohort manager bar
Checklist

[x] Added proper unit tests
[x] Left proper TODO messages for any remaining tasks
[x] Scanned for web accessibility with aXe, and mitigated or documented
flagged issues

Screenshots/Screen Recordings (if Appropriate)

works great! 👍


fix chinese translate

Fixed 2 incorrect Chinese translations

Amazing! I'll merge this now but won't be able to push the site for a few days (currently moving), but really appreciate the contribution 👏🏻

pushed!

This is my first open source contribution, thank you:)


Update Robolectric to 3.1

[Current coverage][cc-pull] is 78.01%

Merging [#187][cc-pull] into [master][cc-base-branch] will not change coverage

@@             master       #187   diff @@
==========================================
  Files            38         38
  Lines           555        555
  Methods           0          0
  Messages          0          0
  Branches         47         47
==========================================
  Hits            433        433
  Misses           92         92
  Partials         30         30

Powered by Codecov. Last updated by [40045de...bce1c7b][cc-compare]
[cc-base-branch]: https://codecov.io/gh/artem-zinnatullin/qualitymatters/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/artem-zinnatullin/qualitymatters/compare/40045de24585ad0f3c619f9ce8ee630805c75bb2...bce1c7bd35ba305f911797d9c4bbbd2b314aa3ce?src=pr
[cc-pull]: https://codecov.io/gh/artem-zinnatullin/qualitymatters/pull/187?src=pr

👍 any of you guys notice any performance change?

We have only one test that runs under robolectric (all other tests are plain jvm tests and others are instrumentation) and I'm going to migrate last robolectric test to instrumentation this week, can't really say.
Lemme ask huge user of robolectric cc @karlicoss: is robolectric 3.1 slower that 3.0?

👍

Thanks, @Plastix!

@vanniktech @artem-zinnatullin I've heard of performance downgrades (see https://github.com/robolectric/robolectric/issues/2328), but haven't noticed any significant difference in our project