Support OCI media types on pull in addition to docker media types

This PR is composed of two commits:

Fixes a bug in rules_pkg's sha256

Fixes #74. Adds support for OCI media types. Currently, pull only supports the media types from the docker standard, but it should also support the media types from the OCI standard.

Relevant specs:

Docker standard (already supported)
OCI standard (support added in this PR)

Error this PR is fixing:
Setup:
bazel_dep(name = "aspect_bazel_lib", version = "1.29.2")
bazel_dep(name = "platforms", version = "0.0.5")
bazel_dep(name = "rules_oci", version = "0.3.8")
bazel_dep(name = "rules_pkg", version = "0.8.1")

oci = use_extension("@rules_oci//oci:extensions.bzl", "oci")
oci.pull(
    name = "distroless_cc",
    digest = "sha256:8aad707f96620ee89e27febef51b01c6ff244277a3560fcfcfbe68633ef09193",
    image = "gcr.io/distroless/cc",
    platforms = [
        "linux/amd64",
        "linux/arm64",
    ],
)
use_repo(oci, "distroless_cc")

Error message:
ERROR: An error occurred during the fetch of repository 'rules_oci~0.3.8~oci~distroless_cc_linux_arm64':
   Traceback (most recent call last):
        File "/private/var/tmp/_bazel_brian.myers/7c67ba1d63a5ecf4b1e2bbf1c99fe09a/external/rules_oci~0.3.8/oci/pull.bzl", line 333, column 13, in _oci_pull_impl
                fail("Unrecognized mediaType {} in manifest file".format(mf["mediaType"]))
Error in fail: Unrecognized mediaType application/vnd.oci.image.index.v1+json in manifest file
ERROR: <builtin>: fetching oci_pull_rule rule @rules_oci~0.3.8//oci:rules_oci~0.3.8~oci~distroless_cc_linux_arm64: Traceback (most recent call last):
        File "/private/var/tmp/_bazel_brian.myers/7c67ba1d63a5ecf4b1e2bbf1c99fe09a/external/rules_oci~0.3.8/oci/pull.bzl", line 333, column 13, in _oci_pull_impl
                fail("Unrecognized mediaType {} in manifest file".format(mf["mediaType"]))
Error in fail: Unrecognized mediaType application/vnd.oci.image.index.v1+json in manifest file
ERROR: /private/var/tmp/_bazel_brian.myers/7c67ba1d63a5ecf4b1e2bbf1c99fe09a/external/rules_oci~0.3.8~oci~distroless_cc/BUILD.bazel:1:6: @rules_oci~0.3.8~oci~distroless_cc//:distroless_cc depends on @rules_oci~0.3.8~oci~distroless_cc_linux_arm64//:distroless_cc_linux_arm64 in repository @rules_oci~0.3.8~oci~distroless_cc_linux_arm64 which failed to fetch. no such package<EMAIL_ADDRESS>Unrecognized mediaType application/vnd.oci.image.index.v1+json in manifest file

thank you for the PR. i have PR already fixing OCI mediatypes here https://github.com/bazel-contrib/rules_oci/pull/105/files.
I'd be happy to land the change for rules_pkg though.

Yah. Happy with whatever fixes the issue. @alexeagle asked me to add a rust example to https://github.com/aspect-build/bazel-examples and I hit this bug; so figured I'd send you a PR to fix it, but I'm indifferent to how it's fixed. Thanks!

+1 to each PR doing just one thing, by the way - thanks

Looking at your PR, though, it seems to do a lot more than fix this bug

right. most of them are already in their PRs. I need to rebase that PR after I land other PRs. If we are going to land this, let's use a method like in my pr. I don't think we need to keep a list of media types, we only got two for each.

I'm going to merge since it's minimal and green and to get Brian on our committer list - we can refactor to be less general if we like.


[boringssl] build failure

Host Environment

OS: [Windows10]
Package: boringssl:x86-windows
Vcpkg version: 2020.06.15-nohash

To Reproduce
Steps to reproduce the behavior:
vcpkg install boringssl:x86-windows
Failure logs
-- Using cached D:/vcpkg/downloads/google-boringssl-5902657734e2a796a514731e0fd0e80081ae43dc.tar.gz
-- Cleaning sources at D:/vcpkg/buildtrees/boringssl/src/0081ae43dc-6a46c5d035.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source D:/vcpkg/downloads/google-boringssl-5902657734e2a796a514731e0fd0e80081ae43dc.tar.gz
-- Applying patch 0001-vcpkg.patch
-- Using source at D:/vcpkg/buildtrees/boringssl/src/0081ae43dc-6a46c5d035.clean
-- Configuring x86-windows
-- Building x86-windows-dbg
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:136 (message):
    Command failed: D:/vcpkg/downloads/tools/cmake-3.17.2-windows/cmake-3.17.2-win32-x86/bin/cmake.exe --build . --config Debug --target install -- -v
    Working Directory: D:/vcpkg/buildtrees/boringssl/x86-windows-dbg
    See logs for more information:
      D:\vcpkg\buildtrees\boringssl\install-x86-windows-dbg-out.log

Call Stack (most recent call first):
  scripts/cmake/vcpkg_build_cmake.cmake:91 (vcpkg_execute_build_process)
  scripts/cmake/vcpkg_install_cmake.cmake:24 (vcpkg_build_cmake)
  ports/boringssl/portfile.cmake:45 (vcpkg_install_cmake)
  scripts/ports.cmake:76 (include)

Error: Building package boringssl:x86-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with `.\vcpkg update`, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
  Package: boringssl:x86-windows
  Vcpkg version: 2020.06.15-nohash

Additional context
boringssl:x64-windows is work

@ZdDroid  Thanks for reporting this issue!
Could you please provide the failure logs?
Thanks.

I have the same problem building boringssl.
I am using Build Tools 16.7.1 MSVC v142 (v14.27)
vcpkg install boringssl:x64-windows-static
Package: boringssl:x64-windows-static
Vcpkg version: 2020.06.15-nohash
Last log entry is:
[416/434] C:\PROGRA~2\BUILDT~1\VC\Tools\MSVC\1427~1.291\bin\Hostx64\x64\cl.exe   /TP -DBORINGSSL_DISPATCH_TEST -DBORINGSSL_IMPLEMENTATION -DNOMINMAX -DWIN32_LEAN_AND_MEAN -D_CRT_SECURE_NO_WARNINGS -D_HAS_EXCEPTIONS=0 -D_STL_EXTRA_DISABLED_WARNINGS="4774 4987" -IC:\Users\din\vcpkg\buildtrees\boringssl\src\0081ae43dc-6a46c5d035.clean\third_party\googletest\include -IC:\Users\din\vcpkg\buildtrees\boringssl\src\0081ae43dc-6a46c5d035.clean\ssl..\include -utf-8 -Wall -WX  -wd4061 -wd4100 -wd4127 -wd4200 -wd4204 -wd4221 -wd4242 -wd4244 -wd4267 -wd4371 -wd4388 -wd4296 -wd4350 -wd4365 -wd4389 -wd4464 -wd4510 -wd4512 -wd4514 -wd4548 -wd4610 -wd4623 -wd4625 -wd4626 -wd4628 -wd4668 -wd4706 -wd4710 -wd4711 -wd4800 -wd4820 -wd5026 -wd5027 -wd5045  -w44265 /D_DEBUG /MTd /Z7 /Ob0 /Od /RTC1 /showIncludes /Fossl\CMakeFiles\ssl_test.dir\ssl_test.cc.obj /Fdssl\CMakeFiles\ssl_test.dir\ /FS -c C:\Users\din\vcpkg\buildtrees\boringssl\src\0081ae43dc-6a46c5d035.clean\ssl\ssl_test.cc
Microsoft (R) C/C++ Optimizing Compiler Version 19.27.29111 for x64
Copyright (C) Microsoft Corporation.  All rights reserved.
ninja: build stopped: subcommand failed.

@dimdin Could you provide the full log and Visual Studio version?
Thanks.

Thank you very much @JackBoosY for the great job.
I am using Visual Studio Build Tools to Build. Visual Studio Installer displays: Visual Studio Build Tools 2019 (BuildTools) 16.7.1
components: _MSVC v142 - VS 2019 C++ x64/x86 build tools (v14.27)
I am running: .\vcpkg.exe install boringssl:x64-windows-static
The log file is:
install-x64-windows-static-dbg-out.log
_
The vcpkg command output is:
Computing installation plan...
The following packages will be built and installed:
    boringssl[core]:x64-windows-static
Detecting compiler hash for triplet x64-windows-static...
Starting package 1/1: boringssl:x64-windows-static
Building package boringssl[core]:x64-windows-static...
Could not locate cached archive: C:\Users\din\AppData\Local\vcpkg\archives\1d\1d91f483e56af817ea98e3c3aae2122b50997370.zip
-- Using cached C:/Users/din/vcpkg/downloads/google-boringssl-5902657734e2a796a514731e0fd0e80081ae43dc.tar.gz
-- Cleaning sources at C:/Users/din/vcpkg/buildtrees/boringssl/src/0081ae43dc-6a46c5d035.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source C:/Users/din/vcpkg/downloads/google-boringssl-5902657734e2a796a514731e0fd0e80081ae43dc.tar.gz
-- Applying patch 0001-vcpkg.patch
-- Using source at C:/Users/din/vcpkg/buildtrees/boringssl/src/0081ae43dc-6a46c5d035.clean
-- Configuring x64-windows-static
-- Building x64-windows-static-dbg
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:139 (message):
    Command failed: C:/Users/din/vcpkg/downloads/tools/cmake-3.17.2-windows/cmake-3.17.2-win32-x86/bin/cmake.exe --build . --config Debug --target install -- -v
    Working Directory: C:/Users/din/vcpkg/buildtrees/boringssl/x64-windows-static-dbg
    See logs for more information:
      C:\Users\din\vcpkg\buildtrees\boringssl\install-x64-windows-static-dbg-out.log

Call Stack (most recent call first):
  scripts/cmake/vcpkg_build_cmake.cmake:91 (vcpkg_execute_build_process)
  scripts/cmake/vcpkg_install_cmake.cmake:24 (vcpkg_build_cmake)
  ports/boringssl/portfile.cmake:45 (vcpkg_install_cmake)
  scripts/ports.cmake:79 (include)

Error: Building package boringssl:x64-windows-static failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with `.\vcpkg update`, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
  Package: boringssl:x64-windows-static
  Vcpkg version: 2020.06.15-nohash

Additionally, attach any relevant sections from the log files above.

C:\Users\din\vcpkg\buildtrees\boringssl\src\0081ae43dc-6a46c5d035.clean\decrepit\bio\base64_bio.c(525): error C2220: the following warning is treated as an error
C:\Users\din\vcpkg\buildtrees\boringssl\src\0081ae43dc-6a46c5d035.clean\decrepit\bio\base64_bio.c(525): warning C4065: switch statement contains 'default' but no 'case' labels

Confirmed.

Hi @ZdDroid, could you test my PR #12967?
Thanks.

I applied the patch, and got:
[404/434] C:\PROGRA~2\BUILDT~1\VC\Tools\MSVC\1427~1.291\bin\Hostx64\x64\cl.exe   -DBORINGSSL_DISPATCH_TEST -DBORINGSSL_IMPLEMENTATION -DNOMINMAX -DWIN32_LEAN_AND_MEAN -D_CRT_SECURE_NO_WARNINGS -D_HAS_EXCEPTIONS=0 -D_STL_EXTRA_DISABLED_WARNINGS="4774 4987" -IC:\Users\din\vcpkg\buildtrees\boringssl\src\0081ae43dc-72f74bc822.clean\third_party\googletest\include -IC:\Users\din\vcpkg\buildtrees\boringssl\src\0081ae43dc-72f74bc822.clean\decrepit\..\include -utf-8 -Wall -WX  -wd4061 -wd4100 -wd4127 -wd4200 -wd4204 -wd4221 -wd4242 -wd4244 -wd4267 -wd4371 -wd4388 -wd4296 -wd4350 -wd4365 -wd4389 -wd4464 -wd4510 -wd4512 -wd4514 -wd4548 -wd4610 -wd4623 -wd4625 -wd4626 -wd4628 -wd4668 -wd4706 -wd4710 -wd4711 -wd4800 -wd4820 -wd5026 -wd5027 -wd5045  -w44265 /D_DEBUG /MTd /Z7 /Ob0 /Od /RTC1    /wx4065 /showIncludes /Fodecrepit\CMakeFiles\decrepit.dir\bio\base64_bio.c.obj /Fddecrepit\CMakeFiles\decrepit.dir\decrepit.pdb /FS -c C:\Users\din\vcpkg\buildtrees\boringssl\src\0081ae43dc-72f74bc822.clean\decrepit\bio\base64_bio.c
FAILED: decrepit/CMakeFiles/decrepit.dir/bio/base64_bio.c.obj
C:\PROGRA~2\BUILDT~1\VC\Tools\MSVC\1427~1.291\bin\Hostx64\x64\cl.exe   -DBORINGSSL_DISPATCH_TEST -DBORINGSSL_IMPLEMENTATION -DNOMINMAX -DWIN32_LEAN_AND_MEAN -D_CRT_SECURE_NO_WARNINGS -D_HAS_EXCEPTIONS=0 -D_STL_EXTRA_DISABLED_WARNINGS="4774 4987" -IC:\Users\din\vcpkg\buildtrees\boringssl\src\0081ae43dc-72f74bc822.clean\third_party\googletest\include -IC:\Users\din\vcpkg\buildtrees\boringssl\src\0081ae43dc-72f74bc822.clean\decrepit\..\include -utf-8 -Wall -WX  -wd4061 -wd4100 -wd4127 -wd4200 -wd4204 -wd4221 -wd4242 -wd4244 -wd4267 -wd4371 -wd4388 -wd4296 -wd4350 -wd4365 -wd4389 -wd4464 -wd4510 -wd4512 -wd4514 -wd4548 -wd4610 -wd4623 -wd4625 -wd4626 -wd4628 -wd4668 -wd4706 -wd4710 -wd4711 -wd4800 -wd4820 -wd5026 -wd5027 -wd5045  -w44265 /D_DEBUG /MTd /Z7 /Ob0 /Od /RTC1    /wx4065 /showIncludes /Fodecrepit\CMakeFiles\decrepit.dir\bio\base64_bio.c.obj /Fddecrepit\CMakeFiles\decrepit.dir\decrepit.pdb /FS -c C:\Users\din\vcpkg\buildtrees\boringssl\src\0081ae43dc-72f74bc822.clean\decrepit\bio\base64_bio.c
Microsoft (R) C/C++ Optimizing Compiler Version 19.27.29111 for x64
Copyright (C) Microsoft Corporation.  All rights reserved.

cl : Command line warning D9002 : ignoring unknown option '/wx4065'
C:\Users\din\vcpkg\buildtrees\boringssl\src\0081ae43dc-72f74bc822.clean\decrepit\bio\base64_bio.c(525): error C2220: the following warning is treated as an error
C:\Users\din\vcpkg\buildtrees\boringssl\src\0081ae43dc-72f74bc822.clean\decrepit\bio\base64_bio.c(525): warning C4065: switch statement contains 'default' but no 'case' labels

Perhaps -wd4065 instead of /wx4065?

@dimdin Oh sorry, you're right!

It builds correctly. But I am trying to figure out how to run the test suite.
found an ssl/ssl_test.exe with 262 tests and all pass.
But I don't think that this is the extended go test suite.
The instructions of ssl/test/README.md guide me to run go test from the ssl/test/runner. Of course when I run it from the sources I am getting:
--- FAIL: TestAll (0.14s)
panic: exec: "../../../build/ssl/test/bssl_shim": file does not exist [recovered]
        panic: exec: "../../../build/ssl/test/bssl_shim": file does not exist

Is there some way to run the go test suite? Do I need to combine the sources with the build directory or is there a better way?

I...don't know, maybe we doesn't install that test file.

I found a way. I am describing it hear for futures searches.
C:\Users\din\vcpkg\downloads\tools\go\go\bin\go.exe test
0/0/4387/4387/4387
PASS
ok      boringssl.googlesource.com/boringssl/ssl/test/runner    43.139s

I am running the go.exe from vcpkg.
The current directory is:
C:\Users\din\vcpkg\buildtrees\boringssl\src\0081ae43dc-e280239335.clean\ssl\test\runner

The folder name after src is random but you can find the correct one from its timestamp.
You need to make the following path by creating build/ssl/test folders.
C:\Users\din\vcpkg\buildtrees\boringssl\src\0081ae43dc-e280239335.clean\build\ssl\test

And place there a copy of files:
bss_shim.exe
bss_shim.exe.manifest
bss_shim.pdb

from:
C:\Users\din\vcpkg\buildtrees\boringssl\x64-windows-static-rel\ssl\test

The commands to build and run are:
PS C:\Users\din\vcpkg\buildtrees\boringssl\src\0081ae43dc-e280239335.clean\ssl\test\runner> C:\Users\din\vcpkg\downloads\tools\go\go\bin\go.exe test -c
PS C:\Users\din\vcpkg\buildtrees\boringssl\src\0081ae43dc-e280239335.clean\ssl\test\runner> C:\Users\din\vcpkg\downloads\tools\go\go\bin\go.exe test
0/0/4387/4387/4387
PASS
ok      boringssl.googlesource.com/boringssl/ssl/test/runner    43.349s

Running this test suite is essential for a build. Using this kind of library, without running its test suite, is really high risk.
Please consider running the test suites for these kind of libraries (i.e. crypto, compression, protocol parsing) allways when installing using vcpkg install (i.e. by default without a flag).
For boringssl it will take 3 minutes to build instead of 2 and you minimise the risk for broken build systems and faulty patches.

@dimdin Fine, I will add it as a feature, but not by default.

I think it already test it.
From SOURCE/CMakeLists.txt l614:
add_custom_target(
    run_tests
    COMMAND ${GO_EXECUTABLE} run util/all_tests.go -build-dir
            ${CMAKE_BINARY_DIR}
    COMMAND cd ssl/test/runner &&
            ${GO_EXECUTABLE} test -shim-path $<TARGET_FILE:bssl_shim>
              ${HANDSHAKER_ARGS} ${RUNNER_ARGS}
    WORKING_DIRECTORY ${CMAKE_SOURCE_DIR}
    DEPENDS all_tests bssl_shim handshaker
    ${MAYBE_USES_TERMINAL})

I cannot believe it, it allready runs the tests when building!
The build problem is solved with your pull request. I am waiting for it to be merged into the master tree.
Thank you very much @JackBoosY


Docs update

This will fix some usability & readability issues with the current documentation.
Adding a grey box around code blocks, updating the Markdown rendered to redcarpet, and making sure there will be no erroneous whitespaces in front of commands/code in code blocks.
Adding website contributing documentation that's hopefully easier to follow, and a GitHub link in the footer.
Signed-off-by: Jonas Rosland<EMAIL_ADDRESS>

Codecov Report

Merging #727 into master will increase coverage by 0.12%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #727      +/-   ##
==========================================
+ Coverage   39.92%   40.05%   +0.12%
==========================================
  Files          69       69
  Lines        3902     3902
==========================================
+ Hits         1558     1563       +5
+ Misses       2243     2240       -3
+ Partials      101       99       -2

Impacted Files
Coverage Δ

pkg/plugin/aggregation/aggregator.go
72.16% <0%> (+5.15%)
:arrow_up:

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 f2c885d...5856d0b. Read the comment docs.


Add Date-slider to graphs

currently some graph has a 2-weeks toggle, would be great to have a control that can slide between how many days to show
---------O---------
Min is the first day of data availability
default is 30
max is 14
not show the control if less than 14 days of data.

Slider added, but the "not show if less than 14 days of data" feature is implemented.

thank you!


Add READMEs to application, crypto, and dynamics directories

Scope
Top-level README's are being added to the application/, crypto/, and dynamics/ directories.
Why?

This is being done to assist understanding of the code base.
Contributes to #290

Todos
Continue adding additional information throughout.

@chgorman Awesome notes! After doing a bit of research, this documentation might make better sense as package level comments which will get pulled into documentation hosted on the Go Packages repository.
For an example, our cloudflare package is following this convention already, and you can see how that gets rendered here.
See godoc documentation for best practices.

Okay, I will cancel this, then.


rebase token server element module

Signed-off-by: Periyasamy Palanisamy<EMAIL_ADDRESS>

This would fix #286


nan problem of SIFID calculation

We would like to ask if you have encountered nan problems when calculating SIFID? My colleague and I cannot get the correct result when running the SIFID program given by SinGAN, the program gives a nan error.
The error message is as follows:
SIFID/sifid_score.py:262: RuntimeWarning: Mean of empty slice.
print('SIFID: ', sifid_values.mean())
../sinGAN/SinGAN-master/mypython/lib/python3.6/site-packages/numpy/core/_methods.py:161: RuntimeWarning: invalid value encountered in true_divide
ret = ret.dtype.type(ret / rcount)
SIFID: nan

Hi, I don't think we ever got that error. But if I remember correctly there were some issues about that in the SinGAN Github. Maybe check the (closed) issues there to see if you can find a solution.


Reach out to Centro wallet for phone number mapping

Assigning @codyborn for visibility because you brought this up 🙏

Met with human from Centro wallet. Have running Discord group DM.


Image size in the thank you page of the quiz Make the Plastic Tide Turners Pledge

On a computer screen, after you submit the "Make the Plastic Tide Turners Pledge" you're redirected to the Thank you page where the following picture

appears in a odd shape.
The text "You did it! Thank you for signing the Plastic Tide Turners Pledge. If you haven't already, check out these important activities to reduce plastic use in your community: How to: Reduce your Plastic Consumption, Activities at Home, Activities in the Community,
Start a Climate Campaign" appears all in small characters, so from an user point of view the all page looks not quite right.
The same goes if I do it from a phone. The image is elongated and looks not quite right.

@micheladegiusti Can you add a link to the page?

https://global.iogt.site/en/sections/youth/climate-change/take-the-plastic-challenge/make-the-plastic-tide-turners-pledge/ for the quiz, and after submitting it it takes me to this page:
https://global.iogt.site/en/sections/youth/climate-change/take-the-plastic-challenge/make-the-plastic-tide-turners-pledge/?back_url=/en/sections/youth/climate-change/take-the-plastic-challenge/make-the-plastic-tide-turners-pledge/&form_length=4

I have difficulties in adding a screenshot at the moment..

This happens also when I do it on the phone

It appears that this got fixed via #1040


Upgrade Jedi to 0.17

https://github.com/davidhalter/jedi/issues/1063#issuecomment-613692208
Docs at https://jedi.readthedocs.io/
Last release to support Python 2.7 and Python 3.5

https://github.com/microsoft/vscode-python/pull/11252#discussion_r412437991
We might have to bump it up once https://github.com/davidhalter/jedi/issues/1548 gets released.
Future work:

Ideally I think we'd pass in the actual project root (which VSCode knows) rather than getting jedi to guess it, however I couldn't immediately see that in the available data. This spelling keeps the existing behaviour, though we may be able to do better in the future.

0.17.1 PR: #12471
0.17.2 PR: #13037


Resolves #2552 - Issues with footer CSS on resizing of page

Closes: #2552
What's Changed

Update CSS to to better account for footer resizing.
TODO

[ ] Explanation of Change(s)
[ ] Attached Screenshots, Payload Example
[ ] Unit, Integration Tests
[ ] Documentation Updates (when adding/changing features)
[ ] Example Plugin Updates (when adding/changing features)
[ ] Outline Remaining Work, Constraints from Design

Static sizing was causing the overflow issue.


rectify geometric delay

only the first term below is currently implemented

it's already implemented in drafts but not released yet.

see also:
https://github.com/ufrgs-gnss-lab/atm-interf-sph-dev/issues/26

keeping both new and old versions:
    da = N.*Dlp;
    dg = dDi + N.*(Dip-Dlp);
    dt = (1+N).*Dip - Di;
      %dt_alt = da + dg;
      %tmp = max(abs(dt-dt_alt))
      %tmp < sqrt(eps(max(dt)))  % DEBUG

    if ~opt.complete_formulation  % legacy incomplete formulation
        dg = dDi;
        dt = da + dg;
    end


UPD Ignore stop command if location does not exist

This should be the new PR version. Ready to be merged to master. Waiting on @orpiske to confirm if this works for you as well.
Thank you

Please see my latest changes for fixes.
Hopefully this is ready for merge.
Thank you for review.

LGTM after the changes.

Validate certs commit was added a few minutes later than original PR.
Thanks! Hopefully all will work. Please verify with me tomorrow. If help needed, I can fix it asap.


I want to add a function to export offline documents to swagger.How do I submit?

This looks well beyond the scope of what I envision for the project. Have you considered creating a separate add-on library

This looks well beyond the scope of what I envision for the project. Have you considered creating a separate add-on library


Resize images to fix iOS TabBar

Fix the #1115

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

@tuliocll I really appreciate your enthusiasm here 😁 We always need people like you that are willing to help out. However, due to this really being a bug with .NET MAUI, I think that we should leave the tutorial as-is and hope it's fixed soon in a patch. If we're 6months later and it's still a problem, then perhaps we can add a note to the tutorial that says iOS should manually resize the images before use.


metal-flash-attention support

Can this project help for you? https://github.com/philipturner/metal-flash-attention
So far, metal-flash-attention can indeed provide the fastest generation speed for stable diffusion on MacOS.

I came here to suggest the same thing.

What needs to be done to make this happen? I'm not very good with cpp, but I want to help.

https://github.com/leejet/stable-diffusion.cpp/pull/386


Extensible guardrail framework for JSON API

Guardrails are a helpful concept for limiting harmful usage of a database or data service API. Reference CEP-3 for the Cassandra project as an example.
Since the JSON API shredding algorithm breaks documents up into many cell values and makes extensive use of Cassandra features including indexes, collections, LWTs, etc., we are establishing limits that apply at the JSON API level. Many are already implemented in DocumentLimitsConfig. (There are also a couple of values in OperationsConfig that seem like limits as well.)
We should provide a way to override this implementation. For example, in Astra DB deployments we will want an implementation that allows guardrails to have different values by tenant. It may make sense to design a more generalized guardrail framework that we can apply across multiple Stargate APIs in the future.

Existing config limits are overridable via system properties / ENV variables, FWTW, using standard Quarkus config override mechanism.

Are these guardrails to be supported at tennat level? Then system properties may not be the way to go. FYI., currently in server less guardrail overrides maintained manually as a kubernetes resource.

I would be strongly against per-tenant guardrails; vast complexity for unclear benefits. Put another way: finding useful global settings seem like a better way to go at first. They can also be changed (if we must) for dedicated kubes.
But trying to provide these for shared kubes on per-tenant basis is orders of magnitude more complicated.

We will consider this as a future post-GA improvement.

As the API is now GA we are immediately seeing cases where this would be very useful to do.


New package: SpikingNeuralNetworks v0.1.0

Registering package: SpikingNeuralNetworks
Repository: https://github.com/jpsamaroo/SpikingNeuralNetworks.jl
Created by: @jpsamaroo
Version: v0.1.0
Commit: 422c1c52890c3f28a6b7b8146433fbd1d051b048
Reviewed by: @jpsamaroo
Reference: https://github.com/jpsamaroo/SpikingNeuralNetworks.jl/commit/422c1c52890c3f28a6b7b8146433fbd1d051b048#commitcomment-35734872

Please close this PR


Sort recipe catalog alphabetically

I'm not entirely sure how the recipe catalog is sorted right now - but it's definitely not alphabetically. If possible, we should sort so that's it clearer what recipes exist.

in the SaaS I believe we sort by number of recipes included, so the categories with the most recipes are surfaced first.


Is the public repository served?

I store the font files as local assets under the /public directory, but when I try to import them from stories I get a "failed to load resources" error.

Can you create a repro with https://node.new/ladle ? Thanks

@kingjack05, once #72 is merged, /public will be served by default with the possibility to set it like in vite.


Remember device cookie

I noticed that the remember_device cookie isn't set to HttpOnly.
def remember_device
    id = @resource.id
    cookies.signed[:remember_device] = {
      :value => {expires: Time.now.to_i, id: id}.to_json,
      :secure => !(Rails.env.test? || Rails.env.development?),
      :expires => resource_class.authy_remember_device.from_now
    }
end

Is there a particular reason why it is not set? I can submit a PR if needed

You know, I don't think there's a reason this isn't set. Happy to accept a PR about this.
One thing I'm trying to think of though, is whether this is likely to break anything for existing users. I can't see why anyone would be reading the value of this cookie from their client side, but I don't want to be wrong either.

Thanks! I think it's safe to assume that no one wants users to access cookies from client scripts. This is my first time contributing to something like this do I have access to push branches or to create a PR?

You are in luck as it's Hacktoberfest and the Internet is awash with descriptions of how to contribute to a project like this!
The quick run down is that you need to:

Fork the repo to your own account
Clone that repo
Open a new branch
Make the changes (including tests if you think that would be useful)
Make sure the tests run successfully
Commit and push your branch to your fork of the project
Open a pull request against this repo

Digital Ocean have a good, in depth, guide to all of this. Or if you want the most fun way to learn how to commit to open source, check out the Open Pixel Project and our TwilioQuest mission that walks you through making your first contribution.

Let me know if I can help any other way.

This is released in version 2.0.0.


Provide an option to invoke TypeScript in non-watch mode even when webpack is in watch mode

Feature motivation

TypeScript has some strange behavior that regular build is much faster a watch-mode build (sometimes the watch-mode build is 30x slower). This slows down forked type checking significantly.
Feature description

Provide an option to always invoke TypeScript in non-watch mode. This will make type checking time much more consistent and often shorter.
For example, with my project, tsc (complete build) is consistently completed within 60 seconds. tsc -w initial compilation takes about 9 minutes. Subsequent recompilation in watch mode time ranges from 1 second to several minutes. Even worse, if I change another file while type checking is still running, the webpack bundling process will be slowed down too.
Feature implementation

watch: "auto" (follows webpack) or "off"

I will release an alpha version with this implemented - I would like to ask you to test if this solves your issue :)

Sure, I'll be glad to try that out. Note: it is watch or incremental that causes this issue, so be sure to turn off both. In case you are interested, here is the TypeScript bug: https://github.com/microsoft/TypeScript/issues/35729.
I just found out with TS 3.9.7 our project can be built in 20 seconds (regular build, no watch, no incremental)! This means even if we use fork-ts-checker-webpack-plugin to start a full type checking pass, it is very acceptable, compared to the uncertainty in watch/incremental mode.

The solution that I implemented works that way:

if you use build: true mode, then use SolutionBuilder API, regardless of webpack
if you run webpack in watch mode, then use WatchProgram API
otherwise, use Program API

For now, there is no configuration for that. If you would like to use Program API  also for watch mode in webpack, I can try to implement that with configuration options (that was the first implementation of the plugin, before WatchProgram API was available)

I think the Program API is what I need, and the whole purpose of the feature request is to enforce it, even when webpack is in watch mode.
The reason:

--build implicitly enables incremental build, which is slow due to TS bug 35729.
WatchProgram API is equivalent to TS watch mode, which is slow due to same TS bug 35729.

My current workaround is removing fork-ts-checker-webpack-plugin, running tsc in a separate task using nodemon to monitor file changes. It's not as convenient as fork-ts-checker-webpack-plugin because the bundling output and type checking output are in two different window, but at least both are fast.

I found very interesting PR: https://github.com/microsoft/TypeScript/pull/42960. I will publish alpha version anyway, but I will wait for this PR before releasing this on the latest channel. Maybe it will solve the WatchProgram issue :)

Maybe it will solve the WatchProgram issue :)

Yes that was the intent of this PR.
I figured that even this that improvement fork-ts-checker-webpack-plugin is a little bit slower compared to tsc --watch directly. Maybe that's because of the different Filesystem...

I will profile the plugin again after releasing your PR :)

Maybe it will solve the WatchProgram issue :)

Yes that was the intent of this PR.
I figured that even this that improvement fork-ts-checker-webpack-plugin is a little bit slower compared to tsc --watch directly. Maybe that's because of the different Filesystem...

Do you have any idea how "slower" it would be. Currently, with my project, a non-watch build takes 20 seconds. tsc --watch takes 9 minutes! I didn't measure fork-ts-checker-webpack-plugin, but it is not only slow, it will also block webpack bundling if I make another file change while previous type checking is still in progress.
I'm hoping with a proper fix, tsc --watch will take just a little longer than non-watch build, while fork-ts-checker-webpack-plugin may add a little more. But those should be just the first pass, file changes should trigger a watch build pass that is much faster.

:tada: This issue has been resolved in version 7.0.0-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

Maybe it will solve the WatchProgram issue :)

Yes that was the intent of this PR.
I figured that even this that improvement fork-ts-checker-webpack-plugin is a little bit slower compared to tsc --watch directly. Maybe that's because of the different Filesystem...

Do you have any idea how "slower" it would be. Currently, with my project, a non-watch build takes 20 seconds. tsc --watch takes 9 minutes! I didn't measure fork-ts-checker-webpack-plugin, but it is not only slow, it will also block webpack bundling if I make another file change while previous type checking is still in progress.
I'm hoping with a proper fix, tsc --watch will take just a little longer than non-watch build, while fork-ts-checker-webpack-plugin may add a little more. But those should be just the first pass, file changes should trigger a watch build pass that is much faster.

I was talking about 10-20%, so it may take 25-30s. But it could also benefit from incremental mode so you only have to pay that on the first compile.

@cnshenj did you tried @sokra's PR or the alpha version of the plugin?

@piotr-oles I haven't. As we discussed before, the fix I need is to make TypeScript run in non-watch mode, even when webpack is in watch mode. But according to what you described, the alpha version will make TypeScript run in watch mode when webpack is in watch mode.
Currently I use nodemon to monitor project changes and start a *full TypeScript compilation when a change is detected. A full compilation pass only needs 20 seconds, compared to several minutes to incremental compilation in watch mode.
I also had some discussion with @sokra in the PR. I believe he made changes to address the specific scenario I described (modify several files and save at the same time). Now we are just waiting for the TypeScript team to incorporate the fix and release TypeScript 4.3.

That makes sense, let's wait :)

@cnshenj Could you try the latest TypeScript beta version? It contains @sokra's fix :)

I will assume it fixed the problem. If not, I will re-open the issue :)

:tada: This issue has been resolved in version 7.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fix(Quantic): New properties and slot in the QunaticCaseAssistInterface  and QuanticDocumentSuggestion

SFINT-4376
Changes Made:
QuanticDocumentSuggestion:

Default value of  maxDocuments updated to be 3 instead of 5.
New slot added named no-suggestions to give the user the ability to customize what the component will display when there is no suggestions to display.

QuanticCaseAssistInterface:

New property preventLogCaseStartOnInit added to prevent sending a caseStartEvent on init.
New property preventFetchClassificationOnInit added to prevent fetching case classification on init (This property is added in the QuanticCaseAssistInterface instead of QuanticCaseClassification because fetching classification will fetch the classifications for all the possible fields in one call).

I don't think we should be saying "oh well ¯_(ツ)_/¯ " while approving a PR in this repo. Let's try to be as rigorous as we can to avoid future headaches. 😅

As far as the breaking changes go, I would give the go ahead on it since officially the quantic case assist components are not "released" right?
I mean they have been merged into master, but the case assist cookbook is not out yet and AFAIK nobody uses JUST the quantic components to do something by themselves. So I would be okay renaming attributes until we have our first version of the cookbook released and "published" for customers to use.
@nathanlb What do you think?

As far as the breaking changes go, I would give the go ahead on it since officially the quantic case assist components are not "released" right?
I mean they have been merged into master, but the case assist cookbook is not out yet and AFAIK nobody uses JUST the quantic components to do something by themselves. So I would be okay renaming attributes until we have our first version of the cookbook released and "published" for customers to use.
@nathanlb What do you think?

@erocheleau Unfortunately, you can't presume a component is not used as part of an implementation because it is not used in the cookbook.


The example provided does not work

The example message body provided does not work. It results in HTTP 400: "summary or text is required" when sending the webhook to a Microsoft Teams channel endpoint.

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

ID: 2606e423-7aff-b44e-3c88-1a96d16ed1fc
Version Independent ID: 29e8d7ba-d255-f533-7781-aa2aa14a040e
Content: Get started with actionable messages via connectors - Outlook Developer
Content Source: docs/actionable-messages/send-via-connectors.md
Product: outlook
Technology: o365-connectors
GitHub Login: @jasonjoh
Microsoft Alias: jasonjoh

@thisnameissoclever there is a text field in the example so I'm not sure what the problem is with Teams. These docs were written for Outlook connectors - there may be some subtle difference I'm not aware of.
Have you tried adding a summary field? If I can figure out how to make the Teams connector accept this in a way that doesn't break the Outlook connector I'm happy to update the example card.

Hey @jasonjoh,
I literally copy-and-pasted the JSON from the default example poll (and others) built using this tool. Here is the response I get:

When I add a "summary" node, I just get a blank message in the channel like so:

When adding a "text" node, I get only that text and nothing else:

I think that the problem is specific to AdaptiveCard types when sent to a MS Teams endpoint. A regular ol' "MessageCard" type is accepted and seems to work just fine, but of course I can't add any "action" buttons to it. The documentation seems to indicate that I should be able to (if I'm correctly interpreting what an "action" is) but alas, nothing shows up when I add the potentialActions node anywhere.

Oh ok. I thought you were referring to the example markup supplied on the page. Yes you're correct - connectors do not support AdaptiveCard (called out at the top of that page). There are MessageCard examples in the tool near the end of the dropdown.


NodeContainer bug with anchored: false

Description

Not really sure how to go into this, but if you have a prototype with - type: NodeContainer and Physics: anchored: false on it, it will throw this.
[FATL] unhandled: System.ArgumentException: An item with the same key has already been added. Key: Content.Server.GameObjects.Components.NodeContainer.Nodes.AdjacentNode
   at System.Collections.Generic.Dictionary`2.TryInsert(TKey key, TValue value, InsertionBehavior behavior)
   at System.Collections.Generic.Dictionary`2.Add(TKey key, TValue value)

The easiest way to replicate this is to go to Prototypes\Entities\Constructible\Specific\Engines\Singularity\emitter.yml and change anchored: true to anchored: false.

Will look at it


No such file or directory 2016_04_10_18_37_40_0200/docProps/app.xml

Hello
I have faced the following issue No such file or directory 2016_04_10_18_37_40_0200/docProps/app.xml
Any help?

Please provide the sample file you are having problems with.

here is file
sheet

Are you sure you are using the latest version? Current RubyXL version is 3.3.17.
> require 'rubyXL'
 => true
> RubyXL::Parser.parse 'worksheet.xlsx'
 => #<RubyXL::Workbook:0x000000027557e0 ......>

Works just fine.


⚠ Bofrost.es has degraded performance

In 40e4b8f, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1516 ms

Resolved: Bofrost.es performance has improved in 57304d2 after 9 minutes.


arm64: assertion failed: pc_rel <= self.max_pos_range() as i64

Similar to https://github.com/bytecodealliance/wasmtime/issues/4626 this popped out of a generated adapter module from the component_api fuzzer. Again the type hierarchy is probably a bit too deep here and should validate against it, but still we probably also shouldn't panic on the input:
$ export CARGO_PROFILE_RELEASE_DEBUG_ASSERTIONS=true
$ cargo run --release --features all-arch compile adapter.wasm --wasm-features all --target aarch64
    Finished release [optimized] target(s) in 0.21s
     Running `target/release/wasmtime compile adapter.wasm --wasm-features all`
thread '<unnamed>' panicked at 'assertion failed: pc_rel <= self.max_pos_range() as i64', cranelift/codegen/src/isa/aarch64/inst/mod.rs:2760:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Oops forgot to attach the actual module: adapter.wasm.gz

I think this is probably related to https://github.com/bytecodealliance/wasmtime/issues/3277, but the intra-function case rather than the inter-function case.

I would have expected https://github.com/bytecodealliance/wasmtime/pull/4627 to fix this given that the exact same code is used for intra- and inter-function relocations AFAIK.

This appears to be a veneer island that is emitted a few thousand bytes too late: there is a Branch19 at the start of a very large (> 1MiB) function body, and the range of the Branch19 relocation is +/- 1MiB. emit_island is invoked around offset 1050000 (2^20 is 1048576). Looking into it more...


Update the condition for vue HMR

Hello, i have add function isRecorded on vue-hot-reload-api (this PR).
Now the VueComponentPlugin require<EMAIL_ADDRESS>I have two question, would not it be better to add plugin dependencies in peerDependencies.
Do you want replace ws lib by uws for have more performance on HMR and less dependencies.
End for end, the watch dependencies is not used ?
Yep i search how to reduce dependencies size :)
Thanks.

Great! There are quite many peerDeps, I am not sure if adding all of them is a good idea.
uws that's a library? We can, but there are many places that would require refactoring.

Great! There are quite many peerDeps, I am not sure if adding all of them is a good idea.
uws that's a library? We can, but there are many places that would require refactoring.

Ok, if you want i can make the refactoring in next days.

@orblazer You have to be very careful with that one. You can't break the API

Yes, i know.

@orblazer Try to make it simpler to review, I will be very strict with it because this change can affect a lot of projects. ;-)

And BTW, thanks a lot for contributing! I really appreciate it! I hope we can get more people onboard!


remmina: <IP_ADDRESS> -> <IP_ADDRESS>

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/remmina/versions.
meta.description for remmina is: '"Remote desktop client written in GTK+"'.

Checks done (click to expand)

built on NixOS
/nix/store/7b5i8wwghn7g4xs67drkq1fwz1d2z0zb-remmina-<IP_ADDRESS>/bin/.remmina-wrapped passed the binary check.
/nix/store/7b5i8wwghn7g4xs67drkq1fwz1d2z0zb-remmina-<IP_ADDRESS>/bin/remmina passed the binary check.
Warning: no invocation of /nix/store/7b5i8wwghn7g4xs67drkq1fwz1d2z0zb-remmina-<IP_ADDRESS>/bin/.remmina-gnome-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/7b5i8wwghn7g4xs67drkq1fwz1d2z0zb-remmina-<IP_ADDRESS>/bin/remmina-gnome had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/7b5i8wwghn7g4xs67drkq1fwz1d2z0zb-remmina-<IP_ADDRESS>/bin/.gnome-session-remmina-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/7b5i8wwghn7g4xs67drkq1fwz1d2z0zb-remmina-<IP_ADDRESS>/bin/gnome-session-remmina had a zero exit code or showed the expected version
2 of 6 passed binary check by having a zero exit code.
0 of 6 passed binary check by having the new version present in output.
found <IP_ADDRESS> with grep in /nix/store/7b5i8wwghn7g4xs67drkq1fwz1d2z0zb-remmina-<IP_ADDRESS>
directory tree listing: https://gist.github.com/67fb608ac0712bb33ac5923abff23d3b
du listing: https://gist.github.com/dbeddd1998c93208e287466faf273fd1

Test this build with Cachix (click to expand)

One time setup in nixpkgs Git checkout:
cachix use r-ryantm
git remote add r-ryantm https://github.com/r-ryantm/nixpkgs.git

Test this build:
git fetch r-ryantm && git checkout 07399bd609e41fb7e594874ad38982013edb0880 && nix-shell --pure -I nixpkgs=. -p remmina

cc @melsigl @ryantm for testing.

Success on x86_64-linux (full log)
Attempted: remmina
Partial log (click to expand)
/nix/store/day9bcmapfi1vy1hvic2jlbxfq77crx7-remmina-<IP_ADDRESS>/share/remmina/external_tools/remmina_filezilla_sftp.sh: interpreter directive changed from "/bin/sh" to "/nix/store/dkh7l9a4sx7zqh8riqbj3z21sz25p8xy-bash-4.4-p23/bin/sh"
/nix/store/day9bcmapfi1vy1hvic2jlbxfq77crx7-remmina-<IP_ADDRESS>/share/remmina/external_tools/remmina_nslookup.sh: interpreter directive changed from "/bin/sh" to "/nix/store/dkh7l9a4sx7zqh8riqbj3z21sz25p8xy-bash-4.4-p23/bin/sh"
/nix/store/day9bcmapfi1vy1hvic2jlbxfq77crx7-remmina-<IP_ADDRESS>/share/remmina/external_tools/launcher.sh: interpreter directive changed from "/bin/sh" to "/nix/store/dkh7l9a4sx7zqh8riqbj3z21sz25p8xy-bash-4.4-p23/bin/sh"
/nix/store/day9bcmapfi1vy1hvic2jlbxfq77crx7-remmina-<IP_ADDRESS>/share/remmina/external_tools/remmina_filezilla_sftp_pki.sh: interpreter directive changed from "/bin/sh" to "/nix/store/dkh7l9a4sx7zqh8riqbj3z21sz25p8xy-bash-4.4-p23/bin/sh"
/nix/store/day9bcmapfi1vy1hvic2jlbxfq77crx7-remmina-<IP_ADDRESS>/bin/remmina-gnome: interpreter directive changed from "/bin/sh" to "/nix/store/dkh7l9a4sx7zqh8riqbj3z21sz25p8xy-bash-4.4-p23/bin/sh"
/nix/store/day9bcmapfi1vy1hvic2jlbxfq77crx7-remmina-<IP_ADDRESS>/bin/gnome-session-remmina: interpreter directive changed from " /bin/sh" to "/nix/store/dkh7l9a4sx7zqh8riqbj3z21sz25p8xy-bash-4.4-p23/bin/sh"
checking for references to /build in /nix/store/day9bcmapfi1vy1hvic2jlbxfq77crx7-remmina-<IP_ADDRESS>...
Wrapping program /nix/store/day9bcmapfi1vy1hvic2jlbxfq77crx7-remmina-<IP_ADDRESS>/bin/remmina-gnome
Wrapping program /nix/store/day9bcmapfi1vy1hvic2jlbxfq77crx7-remmina-<IP_ADDRESS>/bin/remmina
Wrapping program /nix/store/day9bcmapfi1vy1hvic2jlbxfq77crx7-remmina-<IP_ADDRESS>/bin/gnome-session-remmina

Failure on aarch64-linux (full log)
Attempted: remmina
Partial log (click to expand)
shrinking /nix/store/yhlk62i0ilcymv4w3n4yf9jb75wz9aja-libnice-0.1.14/bin/stund
shrinking /nix/store/yhlk62i0ilcymv4w3n4yf9jb75wz9aja-libnice-0.1.14/bin/stunbdc
strip is /nix/store/zrs21zqcchgyabjf4xfimncdq16njizc-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/yhlk62i0ilcymv4w3n4yf9jb75wz9aja-libnice-0.1.14/lib  /nix/store/yhlk62i0ilcymv4w3n4yf9jb75wz9aja-libnice-0.1.14/bin
patching script interpreter paths in /nix/store/yhlk62i0ilcymv4w3n4yf9jb75wz9aja-libnice-0.1.14
checking for references to /build in /nix/store/yhlk62i0ilcymv4w3n4yf9jb75wz9aja-libnice-0.1.14...
cannot build derivation '/nix/store/y54vxm03q84kjpxpk2k0mc6ch6dv5ih7-gst-plugins-bad-1.14.0.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/mcmp1crngycvg9z0452hmp5g1p66hyr7-webkitgtk-2.20.3.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/94mvcdz59qp9vbdlhgr9hw6cggpkania-remmina-<IP_ADDRESS>.drv': 4 dependencies couldn't be built
error: build of '/nix/store/94mvcdz59qp9vbdlhgr9hw6cggpkania-remmina-<IP_ADDRESS>.drv' failed

aarch64 was already failing on Hydra, so it's probably unrelated. Tested connecting to a Windows machine via RDP


Axis input refactor

Adding the Input and Axis classes and their implementation as part of new InputModule

Input Module requires an improved Input Matrix with rewritable Axises and mouse support.


use tape instead of mocha

resolves #34,  doesn't add the warning though.
Ping @dominictarr @indutny @calvinmetcalf and @fanatid on whether we should add that warning, reference: https://github.com/crypto-browserify/pbkdf2/issues/34#issuecomment-231659459

Tests all passing, just coverage is below the threshold


when changing navigation in small browser window, close nav after changing pages

Version - master UI 3/3
Steps to Reproduce:

Make you browser small enough that the nav is in the ... and becomes a drop-down
Click on the ... and change pages

Results: The navigation stays up and you can't see the page you changed to because the nav is so long.
Expected: Close the navigation so you can see the page

Version - master 3/3
Verified fixed


Proxy ip

Could anyone help me? I've added proxy ip  to curl inside V1 classes and seems working but I'm getting thousands of cookies in cf-cookies
Thanks in advanced

It is recommended you use V2, V1 is deprecated.

I didn't switch to V2 because everything seemed just working fine . But as soon as I add proxy ip into curl it generates thousands of cookies that I thought was strange

What are the pros for switching to V2 ?
Thanks

Using V2 now with no issues thanks

Sorry for the delayed response. V2 is just a cleaner version of V1 which is now being maintained by myself, @railken, and some other collaborators. If you come across any issues just raise them here, and I will do my best to get back to you. If I don't, @railken may do.
Its that time where I am busy again. There are things which are still outstanding for this project e.g. licenses, versioning, and adding to packagist which I will do in a few weeks.


implement skip writing out default

Motivation
The primary goal of this feature is to mimic protobuf behavior, where fields with default values are omitted from the wire format. Additionally, a new printout option allows users to override this behavior if they wish to include fields with default values. To support this flexibility, the skip_null_members flag in Opts has been redefined as a bitmask, allowing independent control over skipping null and default values.
Key Changes

Conditional Skipping with custom Wrapper: The custom wrapper now enables users to define a function that determines whether a field should be omitted based on specific conditions. An associated bitmask has been introduced to allow compile-time checks, which control whether user-defined functions should be evaluated based on the Opts::skip_null_members setting during serialization.
New skip_write_default Wrapper: A skip_write_default wrapper provides a concise way to skip fields with default values, streamlining the setup for this common use case.

Note
This feature can be used to resolve IS #1410

I am glad you like it. However, from the github action run , there is a race condition in repe_test which I don't think is introduced by my change. You may need to tackle it.

@huangminghuang, yes I saw that race condition recently and need to tackle it.

One other aspect of this pull request that we might want to change is the behavior of the skip_null_members options when the skip_default_flag is set. Currently in Glaze the skip_null_members option is globally applied, which means that you don't have to use glz::custom to get the behavior and you can use it with reflected types that have no glz::meta. I feel like we want the skip_default_flag to work the same way, so as to not require a glz::meta nor require glz::custom. I do like the fine grained approach of being able to customize the behavior for each field, but often this is desired as a global effect for the glz::write call.
This requires some more work, but I think it will be worth it in the long run. If you don't feel comfortable tackling this, I can work on it when I have time. But, it would be great if you were able to mimic the behavior of the other options and get global behavior working.

One other aspect of this pull request that we might want to change is the behavior of the skip_null_members options when the skip_default_flag is set. Currently in Glaze the skip_null_members option is globally applied, which means that you don't have to use glz::custom to get the behavior and you can use it with reflected types that have no glz::meta. I feel like we want the skip_default_flag to work the same way, so as to not require a glz::meta nor require glz::custom. I do like the fine grained approach of being able to customize the behavior for each field, but often this is desired as a global effect for the glz::write call.

I think we should consider the semantic carefully about this. The current design is to use glz::custom to declare a field has a default value, and use the glz::opts to control whether we should skip the default. If I understand you right, you want that every field has a default value implicitly and can be skipped using skip_default_flag. In the case, you may want a way to declare a field cannot be skipped anyway; use glz::custom with skip_mask=0 may work. However,  I feel we need two different flags: skip_custom_default_flag and skip_implicit_default_flag to differentiate between the two scenarios.

I agree, any general option for skipping defaults would need an opt-out option, like you've noted with glz::custom.


Compiling with Javascript tools=yes fails (no exceptions support for Clipper and Assimp build)

Godot version:
master (https://github.com/godotengine/godot/commit/2c9536b655d006c697a3cf830ad3352f1a1ed9f2)
OS/device including version:
Arch Linux
Issue description:
The javascript export (html5) fails with tools=yes.
I think it should work because there was the website http://godot.online.
[ 72%] Compiling ==> editor/collada/collada.cpp
thirdparty/misc/clipper.cpp:901:7: error: cannot use 'throw' with exceptions
      disabled
      throw clipperException("Coordinate outside allowed range");
      ^
thirdparty/misc/clipper.cpp:1049:5: error: cannot use 'throw' with exceptions
      disabled
    throw clipperException("AddPath: Open paths must be subject.");
    ^
thirdparty/misc/clipper.cpp:1081:5: error: cannot use 'throw' with exceptions
      disabled
    throw; //range test fails
    ^
thirdparty/misc/clipper.cpp:1065:3: error: cannot use 'try' with exceptions
      disabled
  try
  ^
thirdparty/misc/clipper.cpp:1445:5: error: cannot use 'throw' with exceptions
      disabled
    throw clipperException("UpdateEdgeIntoAEL: invalid call");
    ^
thirdparty/misc/clipper.cpp:1513:5: error: cannot use 'throw' with exceptions
      disabled
    throw clipperException("Error: PolyTree struct is needed for open pa...
    ^
thirdparty/misc/clipper.cpp:1563:3: error: cannot use 'try' with exceptions
      disabled
  try {
  ^
thirdparty/misc/clipper.cpp:2841:5: error: cannot use 'throw' with exceptions
      disabled
    throw clipperException("ProcessIntersections error");
    ^
thirdparty/misc/clipper.cpp:2830:3: error: cannot use 'try' with exceptions
      disabled
  try {
  ^
thirdparty/misc/clipper.cpp:3005:8: error: cannot use 'throw' with exceptions
      disabled
  else throw clipperException("DoMaxima error");
       ^
10 errors generated.
shared:ERROR: compiler frontend failed to generate LLVM bitcode, halting
scons: *** [thirdparty/misc/clipper.javascript.opt.tools.64.bc] Error 1
scons: building terminated because of errors.

Steps to reproduce:
scons p=javascript tools=yes target=release_debug bits=64 -j 8

OS: Windows 10 WSL
Godot version: 33897d9
While trying to resolve this issue and in order to test #29003 I got this error:
$ scons platform=javascript target=release_debug tools=yes bits=64 -j4 warnings=extra
scons: Reading SConscript files ...
Using custom build name: Xrayez
WebM SIMD optimizations are disabled. Check if your CPU architecture, CPU bits or platform are supported!
Checking for C header file mntent.h... (cached) yes
scons: done reading SConscript files.
scons: Building targets ...
[  2%] Compiling ==> platform/javascript/os_javascript.cpp
[  5%] Linking Static Library ==> main/libmain.javascript.opt.tools.64.bc
[  5%] Compiling ==> main/tests/test_astar.cpp
[  5%] Compiling ==> main/tests/test_gdscript.cpp
Ranlib Library         ==> main/libmain.javascript.opt.tools.64.bc
[  5%] Compiling ==> main/tests/test_gui.cpp
[  5%] Compiling ==> main/tests/test_main.cpp
platform/javascript/os_javascript.cpp:997:6: error: use of undeclared identifier 'emscripten_sample_gamepad_data'
        if (emscripten_sample_gamepad_data() == EMSCRIPTEN_RESULT_SUCCESS)
            ^
1 error generated.
ERROR:root:compiler frontend failed to generate LLVM bitcode, halting
scons: *** [platform/javascript/os_javascript.javascript.opt.tools.64.bc] Error 1
scons: building terminated because of errors.

Ok, I've had an outdated 1.38.4 Emscripten SDK, updated to 1.38.31 now, but I get these errors now:
$ scons platform=javascript target=release_debug tools=yes bits=64 debug_symbols=no -j4 warnings=extra
scons: Reading SConscript files ...
Using custom build name: Xrayez
WebM SIMD optimizations are disabled. Check if your CPU architecture, CPU bits or platform are supported!
Checking for C header file mntent.h... yes
scons: done reading SConscript files.
scons: Building targets ...
[  2%] Compiling ==> platform/javascript/os_javascript.cpp
[  5%] Linking Static Library ==> main/libmain.javascript.opt.tools.64.bc
[  5%] Compiling ==> main/tests/test_math.cpp
[  5%] Compiling ==> main/tests/test_oa_hash_map.cpp
Ranlib Library         ==> main/libmain.javascript.opt.tools.64.bc
[  5%] Compiling ==> main/tests/test_ordered_hash_map.cpp
[  5%] Compiling ==> main/tests/test_physics.cpp
[  5%] Compiling ==> main/tests/test_physics_2d.cpp
[  5%] Compiling ==> main/tests/test_render.cpp
[  5%] Compiling ==> main/tests/test_shader_lang.cpp
[  6%] Compiling ==> main/tests/test_string.cpp
[  6%] Compiling ==> modules/register_module_types.gen.cpp
[  7%] Compiling ==> thirdparty/assimp/code/BaseImporter.cpp
[  7%] Compiling ==> thirdparty/assimp/code/BaseProcess.cpp
[  7%] Compiling ==> thirdparty/assimp/code/Bitmap.cpp
[  7%] Linking Static Library ==> main/tests/libtests.javascript.opt.tools.64.bc
In file included from thirdparty/assimp/code/BaseImporter.cpp:48:
In file included from thirdparty/assimp/include/assimp/BaseImporter.h:47:
thirdparty/assimp/include/assimp/Exceptional.h:96:13: error: cannot use 'throw' with exceptions disabled
            throw;
            ^
thirdparty/assimp/include/assimp/Exceptional.h:95:9: error: cannot use 'try' with exceptions disabled
        try {
        ^
In file included from thirdparty/assimp/code/BaseProcess.cpp:46:
In file included from thirdparty/assimp/include/assimp/BaseImporter.h:47:
thirdparty/assimp/include/assimp/Exceptional.h:96:13: error: cannot use 'throw' with exceptions disabled
            throw;
            ^
thirdparty/assimp/include/assimp/Exceptional.h:95:9: error: cannot use 'try' with exceptions disabled
        try {
        ^
In file included from thirdparty/assimp/code/BaseImporter.cpp:50:
In file included from thirdparty/assimp/code/FileSystemFilter.h:51:
thirdparty/assimp/include/assimp/fast_atof.h:190:9: error: cannot use 'throw' with exceptions disabled
        throw std::invalid_argument( std::string( "The string \"" ) + in + "\" cannot be converted into a value." );
        ^
thirdparty/assimp/include/assimp/fast_atof.h:288:9: error: cannot use 'throw' with exceptions disabled
        throw std::invalid_argument("Cannot parse string "
        ^
[  7%] Compiling ==> thirdparty/assimp/code/CInterfaceIOWrapper.cpp
thirdparty/assimp/code/BaseImporter.cpp:99:5: error: cannot use 'try' with exceptions disabled
    try
    ^
In file included from thirdparty/assimp/code/BaseImporter.cpp:323:
In file included from thirdparty/assimp/code/../contrib/utf8cpp/source/utf8.h:31:
thirdparty/assimp/code/../contrib/utf8cpp/source/utf8/checked.h:76:13: error: cannot use 'throw' with exceptions disabled
            throw invalid_code_point(cp);
            ^
thirdparty/assimp/code/../contrib/utf8cpp/source/utf8/checked.h:110:21: error: cannot use 'throw' with exceptions disabled
                    throw not_enough_room();
                    ^
thirdparty/assimp/code/../contrib/utf8cpp/source/utf8/checked.h:145:17: error: cannot use 'throw' with exceptions disabled
                throw not_enough_room();
                ^
thirdparty/assimp/code/../contrib/utf8cpp/source/utf8/checked.h:149:17: error: cannot use 'throw' with exceptions disabled
                throw invalid_utf8(*it);
                ^
thirdparty/assimp/code/../contrib/utf8cpp/source/utf8/checked.h:151:17: error: cannot use 'throw' with exceptions disabled
                throw invalid_code_point(cp);
                ^
thirdparty/assimp/code/../contrib/utf8cpp/source/utf8/checked.h:167:13: error: cannot use 'throw' with exceptions disabled
            throw not_enough_room();
            ^
thirdparty/assimp/code/../contrib/utf8cpp/source/utf8/checked.h:173:17: error: cannot use 'throw' with exceptions disabled
                throw invalid_utf8(*it); // error - no lead byte in the sequence
                ^
thirdparty/assimp/code/../contrib/utf8cpp/source/utf8/checked.h:184:17: error: cannot use 'throw' with exceptions disabled
                throw invalid_utf8(*it); // error - no lead byte in the sequence
                ^
thirdparty/assimp/code/../contrib/utf8cpp/source/utf8/checked.h:218:25: error: cannot use 'throw' with exceptions disabled
                        throw invalid_utf16(static_cast<uint16_t>(trail_surrogate));
                        ^
thirdparty/assimp/code/../contrib/utf8cpp/source/utf8/checked.h:221:21: error: cannot use 'throw' with exceptions disabled
                    throw invalid_utf16(static_cast<uint16_t>(cp));
                    ^
thirdparty/assimp/code/../contrib/utf8cpp/source/utf8/checked.h:226:17: error: cannot use 'throw' with exceptions disabled
                throw invalid_utf16(static_cast<uint16_t>(cp));
                ^
thirdparty/assimp/code/../contrib/utf8cpp/source/utf8/checked.h:280:15: error: cannot use 'throw' with exceptions disabled
              throw std::out_of_range("Invalid utf-8 iterator position");
              ^
thirdparty/assimp/code/../contrib/utf8cpp/source/utf8/checked.h:292:15: error: cannot use 'throw' with exceptions disabled
              throw std::logic_error("Comparing utf-8 iterators defined with different ranges");
              ^
thirdparty/assimp/code/BaseImporter.cpp:331:9: error: cannot use 'throw' with exceptions disabled
        throw DeadlyImportError("File is too small");
        ^
fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.
shared:ERROR: compiler frontend failed to generate LLVM bitcode, halting
scons: *** [thirdparty/assimp/code/BaseImporter.javascript.opt.tools.64.bc] Error 1
thirdparty/assimp/code/BaseProcess.cpp:80:5: error: cannot use 'try' with exceptions disabled
    try
    ^
3 errors generated.
shared:ERROR: compiler frontend failed to generate LLVM bitcode, halting
scons: *** [thirdparty/assimp/code/BaseProcess.javascript.opt.tools.64.bc] Error 1
Ranlib Library         ==> main/tests/libtests.javascript.opt.tools.64.bc
scons: building terminated because of errors.

@fire seems like your assimp module fails too in platforms with disabled exceptions, this needs to be fixed by either disabling assimp for web with tools enabled, or provide similar fixes like I did with Clipper (see above). 😃

@Xrayez Those throw and try errors are expected. I just deleted those when compiling with tools=yes

@Xrayez throw and try errors are expected. I just deleted those when compiling with tools=yes

@LinuxUserGD yeah, I could do the same but the aim is to fix this for all users. I fixed it for your original issue, but more thirdparty libraries were added since the issue was created.

@Xrayez Thank you, compiling works now but the screen is black when running godot.html.
Should I close this issue now?

compiling works  with  : scons platform=javascript tools=no target=release
the screen is black when running godot.html   ,used chrome
console :

how to deal with the problem

@Aunter1992 Did you start a local Web server? This is most likely required to bypass browser security restrictions. See the top of this page.

@Aunter1992 Did you start a local Web server? This is most likely required to bypass browser security restrictions. See the top of this page.
godot version  release 3.2.2
yes,  used Nginx.
it seems   the compiled result is   a  template,   not a online  editor

@Aunter1992 When you compile using tools=no, you get an export template, not an editor. Building the editor for HTML5 isn't fullysupported yet.

@Aunter1992 When you compile using tools=no, you get an export template, not an editor. Building the editor for HTML5 isn't fully supported yet.

i see,
thank u  very much
looking forward to the  futhure  release version  ~_~


Helm Charts broken after clicking chart name

With latest alpha (Lens: 5.6.0-alpha.5.2), it seems opening Helm charts results in a crash when clicking the name of the chart in the list.

confirmed that this is fixed by https://github.com/lensapp/lens/pull/5667


SAK-34596 Samigo : Do not remove drafts when publishing

I think @ern may want to just revert SAK-34596 from 22.x and close this? I think makes more sense.

Closing as this was already reverted


update VisibilityCard component

I want to merge this change because...

PR intended to be tested with API branch: add-searchable-and-available-for-purchase-flags-to-product
Screenshots

Pull Request Checklist

[x] All visible strings are translated with proper context.
[x] All data-formatting is locale-aware (dates, numbers, and so on).
[x] Translated strings are extracted.
[x] Number of API calls is optimized.
[x] The changes are tested.
[x] Data-test are added for new elements.
[x] Type definitions are up to date.
[x] Changes are mentioned in the changelog.

Test environment config

API_URI=https://master.staging.saleor.rocks/graphql/

Task linked: CU-7epck0 Dashboard changes for "visible in listings" feature

As @dominik-zeglen mentioned there are small styling differences between the screenshot and designs:

"Set availability date" and "Set publication date" shouldn't have any underline
"Will become available on" and "Since " text have different styles - grey color and smaller line spacing
"Disabling this checkbox will remove product ..." - this text is also using a different styling - grey text and smaller line spacing


sharding.jdbc.datasource.names only support datasource names separated by comma

Feature Request
For English only, other languages will not accept.
Please pay attention on issues you submitted, because we maybe need more details.
If no response more than 7 days and we cannot make decision by current information, we will close it.
Please answer these questions before submitting your issue. Thanks!
Is your feature request related to a problem?
No.
Describe the feature you would like.
hope the sharding.jdbc.datasource.names in application.properties can support expression like ds,ds_${0..3}。
but， the SpringBootConfiguration show me that only support datasource names separated by comma. if tens of names， the conf is unfriendly at all.

Hope to support formmated names like ds_00,ds_01,...,ds_15, rather than ds_0,ds_1,...,ds_15

I also encountered this problem. How can I solve it?

@boycai hi, we will release this feature at 3.1.0.M1

@boycai sorry, not for 3.1.0.M1, it should be include at 3.1.0

duplicate with #1686


refactor!:  require the builder pattern for module initalisation

This PR makes sure that the way structs are constructed is consistent and encourages the builder pattern.
It is based on this question: https://github.com/testcontainers/testcontainers-rs-modules-community/pull/156#discussion_r1660236432
For the changelog:
We now require you to use the builder pattern (instead of some structs being unit structs) for all modules.
This ensures that if we add a field in the future that this will not break your existing code.
This change is breaking for these modules:

Module
before
after

cncf_distribution::CncfDistribution
CncfDistribution.start()
CncfDistribution::default().start()

dynamodb_local::DynamoDb
DynamoDb.start()
DynamoDb::default().start()

elasticmq::ElasticMq
ElasticMq.start()
ElasticMq::default().start()

mongo::Mongo
Mongo.start()
Mongo::default().start()

kwok::KwokCluster
KwokCluster.start()
KwokCluster::default().start()

rabbitmq::RabbitMq
RabbitMq.start()
RabbitMq::default().start()

redis::stack::RedisStack
RedisStack.start()
RedisStack::default().start()

redis::standalone::Redis
Redis.start()
Redis::default().start()

victoria_metrics::VictoriaMetrics
VictoriaMetrics.start()
VictoriaMetrics::default().start()

Let's clean this up (rustfmt & etc)

Sorry for that part. Forgot to do rustfmt after doing the (apparently missing doctests) testing run

I don't know why the test for mssql_server added in https://github.com/testcontainers/testcontainers-rs-modules-community/pull/72 is failing.
Cannot debug this locally.
@kymmt90 I am assuming you are using this in your testing infra. Is this flaky for you too?

This is definitely unrelated to the PR and seems to be flaky - yes.
Need to address this but in separate PR for sure


Channel balance-based Monitoring threshold

Fixes #1369
Short description
Implements a new config value for the SDK: rateToSvt, which holds a token => wei mapping. Only tokens present on this mapping will have monitoring enabled, and monitoring will be requested (i.e. paid to MS as rewards) only after channel's received total (off and on-chain unlocked sum), normalized through this rate, surpasses monitoringReward config, which default now is set to 5 SVT (same as raiden-py,  hopefully enough for a MS to pick up our request, may be tweaked if needed). The rateToSvt config is empty by default, meaning receiving is still disabled by default and therefore no monitoring is applied.
Definition of Done

[x] Steps to manually test the change have been documented
[x] Acceptance criteria are met
[ ] Change has been manually tested by the reviewer (dApp)

Steps to manually test the change (dApp)

In served dApp, set the rate:

// rate=5e18 means 1e18wei of TKN (1TKN if decimals=18) is worth 5SVT, so 1+TKN is needed to trigger monitoring
raiden.updateConfig({ rateToSvt: { "<token_addr>": "5000000000000000000" } });

Receiving gets enabled
In another dApp account, transfer 0.9TKN to first client. Transfer should be received, but no monitoring signatures are requested
Make new transfer, worth 0.11TKN; threshold cross value of default monitoringReward of 5SVT, monitoring prompt happens 15s later and is sent to global rooms: messageGlobalSend actions to meta: { roomName: "raiden_goerli_monitoring" } containing the type: "RequestMonitoring" messages.

@kelsos Yes, it is going to be the following issue https://github.com/raiden-network/light-client/issues/1373


error bug bash: breaking changes for PolicySetError and LinkingError

Description of changes
Breaking changes split out from #190, for error variants to carry more information about the error.
Checklist for requesting a review
The change in this PR is (choose one, and delete the other options):

[x] A breaking change requiring a major version bump to cedar-policy (e.g., changes to the signature of an existing API).

I confirm that this PR (choose one, and delete the other options):

[x] Updates the "Unreleased" section of the CHANGELOG with a description of my change (required for major/minor version bumps).

I confirm that cedar-spec (choose one, and delete the other options):

[x] Does not require updates because my change does not impact the Cedar Dafny model or DRT infrastructure.

Disclaimer
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

If we want to regularly split out breaking changes in future pull requests, we should enable "rebase merge" as a merge option on the repository. That way we could setup a single PR as two commits, one breaking and the other a patch, and then merge that preserving the history. Then the non-breaking change could be cherry-picked. We'd have to be careful not to use that option when we have a messy history.

We could do that, but it might be cleaner to review breaking and non-breaking changes in separate PRs, particularly if we plan to release the non-breaking changes separately.


PodDisruptionBudget documentation Improvements

Improved PDB documentation.
Removes old docs/tasks/administer-cluster/configure-pod-disruption-budget.md.
Replaces with a Concept Guide and a new Task, and improvements to an existing task.

This change is

This depends on and includes #3885.

@foxish @bdbauer @maisem @mml may be interested.

All Janet's comments addressed except where replied otherwise.
Will tackle @cody-clark 's detailed comments later this week.

Ok, just ping me when this is ready to be merged.

All Cody's comments addressed.

Addressed review comments from mml and maisem.

Addressed all comments from @mml and @maisem.

Once they give the tech lgtm, I will squash and merge this. Thanks @erictune !

FYI, all feedback must be addressed and LGTMs given by EOD Tue, June 27th so that this can be merged for the 1.7 release on June 28th.

@tengqm I've addressed your feedback in PR #4215.


UI: Add a order completion route additionally

When the shipment reaches the customer address, the shipment carrier (delivery person) should be able to complete the order,
Actions:

[X] An Additional route with /order_complete to complete the order
[X] Form with two input field: orderId and Completion Secret
[X] Integration with the contracts

Additional Enhancements:

[X] On orderId Input fetch and show the orderId Details before submitting secret

#11 Closes This


Regression in bag playback

Hi, thanks for open sourcing webviz!
We've noticed a regression in bag playback. For certain bags with gaps in them the playback halts at the start of the gap instead of continuing playback through them:

A minimal bag that reproduces the issue on https://webviz.io/try/ : playback_issue_minimal.bag.gz
Created with the following script: make_bag.py.gz, basically it has 2 seconds of data, then a gap of two seconds, and then 30 seconds more data. If the last data part is 29 seconds the playback / cache mechanism jumps over the gap.
I think this was introduced in #273, commits before this don't have this issue. Looking further at the changes in this PR I identified the these values to affect the behaviour. Changing BLOCK_SIZE_NS to something larger (say 2.0e9) makes the playback work as expected.
@janpaul123 commented in the code that the numbers were determined emperically for good performance. So far increasing the block size doesn't seem to affect the performance too much, but I don't know exactly how the caching mechanism works or how this actually prevents the issue from manifesting.

Thanks for reporting this and the excellent test case. I'll release a fix shortly.

(If you're interested, this line was the culprit: https://github.com/cruise-automation/webviz/pull/283/files#diff-ff549a830b60d70e1ed51ce42222356fL85-R85)

If you're interested, this line was the culprit

Ah yes, I see, thanks for linking that.
Really appreciate the quick response and resolution @janpaul123 :+1:  . Confirmed the issue is resolved in the latest master.


[RFR] [SVCS-290] Expand postman collections to include move_files and move_folders.

Purpose:
SVCS-290
Expand locally-runnable Postman test suite for testing providers
Changes:
Updated  docs/api.rst  for new collections
Added  tests/postman/collections/move_files.json Postman collection
Added tests/postman/collections/move_folders.json Postman collection
Side effects
None
[#SVCS-290]

Coverage remained the same at 75.731% when pulling 9c185d9d9643902d09d01d875d6b4a9cfa7483c3 on TomBaxter:feature/svcs-290 into 425a3296014126931847d466b77673716516e2a7 on CenterForOpenScience:develop.


How to fix the typescript type model in insertGraph and fetch?

I have a lot of trouble with typescript and i was wondering why nobody else run in to this. I tried for hours but i don't came up with any working solution. Please help me out!
Lets use insertGraphAndFetch to add a Person (Peter) and another Person (Lisa) within the relation "oneLove".
import { Model } from "objection";
import knex from "../../../database/knex";

Model.knex(knex);

class PersonModel extends Model {
  id!: number;
  name: string;
  nickname: string | null;

  oneLove: PersonModel | null;
}

type PersonResponse = {
  id: number;
  name: string;
  nickname: string | null;
  oneLove: PersonResponse | null;
}

type ExpectedOutput = PersonResponse;

const run = async () => {

  const addedPeter = await PersonModel.query().insertGraphAndFetch({
    name: "Peter",
    oneLove: { name: "Lisa" } // <-- typescript error
  });

  const jsonResponse: ExpectedOutput = addedPeter;
  console.log(jsonResponse);
};

run();

Typescript error:
Type '{ name: string; }' is missing the following properties from type 'PersonModel': id, nickname, oneLove, $modelClass, and 36 more.
Thats odd. I saw a lot of issues related on this. The solution: Partial the Model.

import { Model } from "objection";
import knex from "../../../database/knex";

Model.knex(knex);

class PersonModel extends Model {
  id!: number;
  name: string;
  nickname: string | null;

  oneLove: Partial<PersonModel> | null; // <-- added
}

type PersonResponse = {
  id: number;
  name: string;
  nickname: string | null;
  oneLove: PersonResponse | null;
}

type ExpectedOutput = PersonResponse;

const run = async () => {

  const addedPeter = await PersonModel.query().insertGraphAndFetch({
    name: "Peter",
    oneLove: { name: "Lisa" }
  });

  const jsonResponse: ExpectedOutput = addedPeter; // <-- typescript error
  console.log(jsonResponse);
};

run();

Typescript error:
Type 'Partial<PersonModel>' is not assignable to type 'PersonResponse'.
  Types of property 'id' are incompatible.
    Type 'number | undefined' is not assignable to type 'number'.
      Type 'undefined' is not assignable to type 'number'.

Oh no. Because Partial makes the attributes optional the response attributes are now not assignable/compatible.
{id: number} is not compatible with {id: number | undefined}.
For the insert i'd like to use the Partial and for fetching the PersonModel.
is this possible? What i'm doing wrong?

Hi @marko-x, I will reply to you here then, because it's more related to your example than mine.
I haven't used PartialModelGraph but I think I understand what it's meant to do.
But I'm not sure if you need it actually.
But firstly, can you explain a few things. Why do you have PersonModel and PersonResponse defined separately when they basically have identical properties? Is it because you want to force the return object to be of that type without tying yourself to the PersonModel class in your whole project (basically you want to decouple from the Data Access Layer)?
I think in that case you can try how I did it. I don't know if Types work the same for that as Interfaces, but I used an Interface and I made the Model implement that, like this:
class PersonModel extends Model implements PersonResponse
Sorry, I didn't test it myself, just a suggestion that you can try. If that doesn't work, I think you'd need to change your type to an interface. If you can't do that, then maybe you need to use your solution.
But in this case, I'm not sure if the PartialModelGraph does what you want, it might just skip some type checks which is ignoring your problem, not solving it.
And another thing, why have you defined 2 types for your properties? If your property "nickname" is of type string, it can be null anyways, I don't think you have to define 2 types for it. This makes it more difficult to use it I think because you always have to handle the "null" case separately then.

No activity. Closing.


fix behavior of only-Nbits comments

Fixes https://github.com/rust-lang/miri/issues/2206

@bors r+

:hourglass: Testing commit 7308f8f3cfbdaf13613278140d256e85ecc1c84c with merge f6641963afe6de73650551111ee399df74ff55db...

:sunny: Test successful - checks-actions
Approved by: oli-obk
Pushing f6641963afe6de73650551111ee399df74ff55db to master...


Add HEXL-FPGA compatibility for DyadicMultiply and KeySwitch

Added an internal implementation for DyadicMultiply and KeySwitch and a CMake option and compiler flag to disable the normal DyadicMultiply and KeySwitch and only leave the internal one available. This makes HEXL compatible with HEXL-FPGA. With this both libraries can use HEXL's header but HEXL-FPGA can override DyadicMultiply and KeySwitch with its own implementation while leaving the internal implementation as a fallback if the user desires to use the CPU implementation.
Renamed all instances of CKKS in all functions and file names.
Added a new root_of_unity_powers_ptr option to KeySwitch. This option will be used in HEXL-FPGA.

continue as PR 109.


update slack room link

Signed-off-by: Xiang Dai<EMAIL_ADDRESS>Changes
Update slack room link.

Duplicate of https://github.com/thanos-io/thanos/pull/1570/?

just pick one

closing in favor of #1570


check-memory-percent.sh: Corrected units in performance data output

Pull Request Checklist
Is this in reference to an existing issue?
General

[x] Update Changelog following the conventions laid out on Keep A Changelog

[ ] Update README with any necessary configuration snippets

[ ] Binstubs are created if needed

[x] RuboCop passes

[x] Existing tests pass

Purpose
check-memory-percent.sh: Corrected units (from MB to %) in performance data output
Known Compatablity Issues

Nice catch @ttarczynski.


First animation works but not the subsequent ones

Hi,
I've a problem I can't resolve, I tried everything I found on the doc and google without success.
The first fade animation when filtering works, but then it just disappear / appear in a instant.
Example here  : https://clean.hypnoscient.fr/contenus/
Thanks

Hi there - looks like your project is working fine, so guessing you already figured this out. However I did notice you are using MixItUp v2. You might want to upgrade to the latest version (v3), and then you can take advantage of all the document and demos at kunkalabs.com/mixitup, plus various GitHub issues here
There is a migration guide here which you may find useful: https://www.kunkalabs.com/mixitup/migration-guide/


changes for flutter 3.0

Changes in this PR:
Changes for #60 issue.
Motive / Approach
Adding not null checks
Reference GitHub Issues:
#60
Related Screenshots:

Would appreciate if you can add more details around why and screenshots from the running example

In the meanwhile @reeteshranjan and I will review the PR. Thanks for the contribution!

#62 looks more likely to be merged as of now and as it is already tackling #60 and more. Keeping this PR in hold for now.


[Bug]: Jest can't resolve ipfs-http-client

Version
29.2.2
git@github.com:ssadler/jest-resolver-ipfs.git
Steps to reproduce
Check out repository: https://github.com/ssadler/jest-resolver-ipfs
yarn
npx jest

Expected behavior
Is able to import the module
Actual behavior
Can't import the module
Additional context
Digging into it further, I found it resolves the module folder but when it gets to the point of resolving the entrypoint from "exports" it fails. If you add "import" to options.conditions, then it does import the module but fails with a parse error when it encounters import ... in the code.
In my Typescript project, I have set transformIgnorePatterns: [],, but this doesn't seem to help.
Also tried enhanced-resolve (doesn't make any difference), and jest-light-runner which gives: Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: No "exports" main defined
Thanks
Environment
System:
    OS: Linux 5.15 Ubuntu 22.04 LTS 22.04 LTS (Jammy Jellyfish)
    CPU: (16) x64 AMD Ryzen 7 PRO 4750U with Radeon Graphics
  Binaries:
    Node: 18.12.0 - ~/.nvm/versions/node/v18.12.0/bin/node
    Yarn: 3.2.1 - ~/.nvm/versions/node/v16.16.0/bin/yarn
    npm: 8.19.2 - ~/.nvm/versions/node/v18.12.0/bin/npm

I think you should do the following below:
npm uninstall --save ipfs-http-client
npm i --save<EMAIL_ADDRESS>

Ok so here is the solution. ipfs-http-client is designed to be used in the backend only. When you try to use it in the frontend it lacks certain node.js modules as far as I understood. The solution is to not use ipfs-http-client at all. If you are only uploading and downloading files using a gateway you can directly access that gateway using fetch () :)
`export interface IpfsData{
Name :string,
Hash : string,
}
export interface IpfsError {
Message : string,
Code : number,
Type : string, // this just states "error"
}
export type IpfsDataOrError = IpfsData |IpfsError;
export const IPFSGateways ={
InfuraGateway: "https://ipfs.io/ipfs/",
MavonDedicatedGateway :"https://mavon.infura-ipfs.io/ipfs/"
};
const projectId = '2HGHdTiN42FFzbgVNPDyWcPRNSq';   // <---------- your Infura Project ID
const projectSecret = 'f0ad7900da65e68aaf75a58b1ff567c9';  // Infura Secret - should never be on the real client
export function ReplaceInfuraWithMavonGateway(jsonOrUrl : string) : string{
return jsonOrUrl.replaceAll(IPFSGateways.InfuraGateway , IPFSGateways.MavonDedicatedGateway);
}
export async function downloadFromIPFS(ipfsUri : string) : Promise
{
ipfsUri = ReplaceInfuraWithMavonGateway(ipfsUri);
const res = await fetch(ipfsUri)
let receivedObject :T;
let text;
try {
text = await res.text();
let textButWithMavonGateway = ReplaceInfuraWithMavonGateway(text);
receivedObject = JSON.parse(textButWithMavonGateway) as T;
} catch(err){
throw new Error("could not parse json, got text instead: " + JSON.stringify(err) + " parsed text:" + text + "  ");
}
return receivedObject;
}
export async function uploadToIPFS(data :string | Blob |File ) : Promise{
const result = await callIpfsCommand("add" , data);
let url = IPFSGateways.MavonDedicatedGateway + result.Hash;
return url;
}
function isIpfsData( toBeDetermined : IpfsDataOrError) : toBeDetermined is IpfsData{
if ( (toBeDetermined as IpfsData).Hash ){
return true;
}
return false;
}
async function callIpfsCommand( args :string , data : string | Blob |File) : Promise{
const auth = 'Basic ' + Buffer.from(projectId + ':' + projectSecret).toString('base64');
const formData = new FormData();
if((data as File).name){
formData.append("file" , data , (data as File).name);
} else {
formData.append("file" , data );
}
const options = {
  method: 'POST',
  headers:{
    Accept: "application/json",
    Authorization :auth,
  },
  mode: "cors",
  body: formData,
} as RequestInit ;

let res = await fetch("https://ipfs.infura.io:5001/api/v0/" + args, options);
let text = await res.text();
let json;
try {
  json = JSON.parse(text);
} catch (err){
  console.error(err);
}

if(isIpfsData(json)){
  return json;
}else if( (json as IpfsError).Message){
  throw new Error (json.Message);
} else {
  throw new Error("error parsing result " + text);
}

}`

Like mentioned above, this module is ESM only<EMAIL_ADDRESS>Just follow the instructions here: https://jestjs.io/docs/ecmascript-modules

I'm not sure what any of this means. Can you repost the gist ?  I'm not using Infura, I'm trying to use a private gateway.

Hi jdbertron,
sorry, I had changed my username which removed the gist link, but here it is:
https://gist.github.com/aignermax/c495c98003da974d17b9c4c481ac23be


Development boards/arduino images cannot be displayed

https://erc-bpgc.github.io/handbook/electronics/Development_Boards/Arduino/ pictures aren't visible

Solved. Looks like HTML tags in md files don't work for mkdocs

I used  tags so that i could resize the images, but mkdocs gave bt. So instead one can use attr_list as shown here https://github.com/mkdocs/mkdocs/issues/1678


all api response have problem

my env

go version: go1.16
os sys: macos catalina

test code in main.go：
package main

import (
	"context"
	"fmt"
	"net/http"
	"net/url"

	"github.com/goharbor/go-client/pkg/sdk/v2.0/client/user"

	httptransport "github.com/go-openapi/runtime/client"
	"github.com/goharbor/go-client/pkg/harbor"
)

func main() {
	urlObj, err := url.Parse("https://my-harbor-addr")
	if err != nil {
		fmt.Println(err)
	}

	cs := harbor.NewClientSet(&harbor.Config{
		URL:       urlObj,
		Transport: http.DefaultTransport,
		AuthInfo:  httptransport.BasicAuth("admin", "********"),
	})

	res, err := cs.V2().User.ListUsers(context.TODO(), &user.ListUsersParams{})
	fmt.Println("get res: ", res)
	fmt.Println("get error: ", err)
}

go run main.go will output :
get res:  <nil>
get error:  X-Total-Count in header must be of type int64: ""

if change the request api to
res, err := cs.V2().User.GetUser(context.TODO(), &user.GetUserParams{UserID: 6})

will output
get res:  <nil>
get error:  &{false  0001-01-01T00:00:00.000Z  <nil>  false 0001-01-01T00:00:00.000Z 0 } (*models.UserResp) is not supported by the TextConsumer, can be resolved by supporting TextUnmarshaler interface

I try many api request，no one can work

Hi @schecterdamien thanks for trying it out!
Sorry we are still actively trying to fix the issue since we just published this repo.
You can try the v0.24.3 tag for use. That was verified

Right now main branch also has the working code


updated containerd/cri selinux support

bump containerd/containerd to 1.3.6
backport latest selinux tweaks containerd/cri for 1.3 series of containerd
remove $NOTIFY_SOCKET, if present, from env when invoking containerd to
prevent gratuitous notifications sent to systemd.

Signed-off-by: Jacob Blain Christen<EMAIL_ADDRESS>

Marked this as DRAFT until I replace the references to my personal forks of rancher/containerd and rancher/cri.

https://gist.github.com/dweomer/c085922ca4df344945a1e6cd1838bc33#results


bundle application.json or ability to use json object only

making always an extra http request for the application.json on production seems unneeded. i'd like an option either to bundle the json somehow, or to removing the autoloading and using setAll myself with an json object i have in eg main.js without the then unneeded application.json loading

There will be an option to both use server-side loaded JSON, client-side and bundled options as well. This will be in the next version.

sounds great. tx

There is a merge function in release 1.0.4 that should support working with objects.


Vendor<EMAIL_ADDRESS>and drop dependency injection functions

How to categorize this PR?

/area open-source
/kind cleanup
What this PR does / why we need it:
The package controller-runtime/pkg/runtime/inject  has been removed in controller-runtime v0.15. This package contained long deprecated injection functions (like InjectScheme, InjectLogger, InjectConfig, InjectClient, InjectCache, etc.).
The runtime injection functionality has been deprecated since Controller Runtime 0.10; all of the above fields can be passed from the Manager to structs or interfaces that need them.
Which issue(s) this PR fixes:
Part of https://github.com/gardener/gardener/issues/7991
Special notes for your reviewer:
Release note:

The `security.gardener.cloud/pod-security-enforce` annotation in the ControllerRegistration is set to `baseline`. With this, the pods running in the extension namespace should comply with `baseline` pod-security standard.

The security.gardener.cloud/pod-security-enforce annotation in the ControllerRegistration is set to baseline. With this, the pods running in the extension namespace should comply with baseline pod-security standard. See https://github.com/gardener/gardener/pull/8099 for more details.
During release validation, we have to make sure that the pod can run with this standard, or we have to either change it to privileged or adapt the component.


vite define and object property value shorthand dev and build inconsistencies

Describe the bug
Vite config define: {APP_DOMAIN: JSON.strinfigy('x')}
and vue component source
data(){
        return {
                APP_DOMAIN
        }
},

works fine in dev mode, but on build returns error on APP_DOMAIN position
[rollup-plugin-dynamic-import-variables] Unexpected token (166:6)
App.vue:166:6
error during build:
SyntaxError: Unexpected token (166:6)

Tried also APP_DOMAIN: APP_DOMAIN which works as expected in dev mode, but build translate it to x: 'x'
Webpack didn't have issue with this.
Reproduction
none
System Info
System:
    OS: macOS 12.1
    CPU: (8) x64 Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
    Memory: 403.77 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 14.18.2 - /usr/local/opt/node@14/bin/node
    npm: 6.14.15 - /usr/local/opt/node@14/bin/npm
  Browsers:
    Chrome: 97.0.4692.99
    Firefox: 95.0.2
    Safari: 15.2
  npmPackages:
    @vitejs/plugin-legacy: ^1.6.4 => 1.6.4
    @vitejs/plugin-vue: ^2.1.0 => 2.1.0
    vite: ^2.7.13 => 2.7.13

Used Package Manager
npm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Don't use object property value shorthand
Don't let your object key and value to be same define CONSTANT value
You can try use it like below:
define: {
    __APP_DOMAIN: JSON.stringify('x'),
    APP_DOMAIN: JSON.stringify('y'),
}

data() {
    return {
     // APP_DOMAIN: APP_DOMAIN, // error on build
     // APP_DOMAIN,  // error on build
     DOMAIN: APP_DOMAIN, // ok
      APP_DOMAIN: __APP_DOMAIN, // ok
      __APP_DOMAIN: APP_DOMAIN, // ok
    }
  }

@psaren thanks for suggestions
I have quite a lot of those shorthand assignments in a big webpack based project. Actually, it bothers me that works fine in vite dev mode, but breaks when building.

Is there a way to override this replacement somehow? This is the only thing blocking me from switching to Vite. Too much code needs to be changed, just to pass the build.  When is replacement with esbuild planned? v5?


Binaries missing from 2.2.0 release

Documentation states that binaries are available on releases from v2.2.0 for use in a non-docker environment
Expected:
Release https://github.com/thomseddon/traefik-forward-auth/releases/tag/v2.2.0 should have binary in "assets" section.
Actual:
No binaries found

These will be added to the next release, apologies for the delay


added hourly chime support

i like to have a hourly chime in my clock but not so annoying as in original firmware, just a short beep. also i like functionality and logic of your firmware. so here is the patch for hourly chime support. chime display is right after alarm, both displays are with timeout when not adjusting. 12h/24h supported, dot1/dot3 are pm indicators for start/stop hours, dot2 - chime on/off, shown only at chime display.
works fine with my STC15W404AS.
of course, chime can be disabled with WITHOUT_CHIME at compile time.

when using super capacitor (like 0.47F/5.5V) instead of cr1220 just define WITH_CAPACITOR for activating ds1302 trickle charging mechanism.
shouldn't be used with lithium batteries like crXXXX to avoid damages.

nice... apologies I haven't gotten around yet to test and merge, but I hope to have some time in the next week or so as things slow down at work for holidays...


feat(tutorials): E2E tutorial Connector Kit - local playground with own edc

Description
This is a documentation task aimed at providing a step-by-step guide for adding and registering a new TractusX EDC named Trudy within the local dataspace. The process involves utilizing the related HelmChart with PostgreSQL database and HashiCorp Vault. Additionally, the documentation should cover how to handle data transfer within the local dataspace.
Please note that although the registering process is more complex without the portal, it is essential for a better understanding of the TractusX EDC ecosystem.
Documentation Tasks
The documentation should address the following tasks in a step-by-step manner, including necessary links, prerequisites, and other relevant information to enhance user understanding.

Configure the New TractusX EDC (Trudy):

Provide detailed instructions on how to configure the new TractusX EDC (Trudy).
Highlight the important properties and where to obtain the required information.

Run TractusX EDC (Trudy) in the Dataspace:

Explain the process of running TractusX EDC (Trudy) within the local dataspace.
Include any specific configurations or settings required for seamless integration.

Example cURL Commands for Data Management:

Provide a set of example cURL commands for adding assets, policies, and contract definitions to TractusX EDC (Trudy).
Include explanations and comments to aid users in understanding the purpose and usage of each command.

Testing Access Control Policies:

Describe how to create specific policies to test access control for TractusX EDC (Trudy).
Include scenarios where access may be granted or restricted between TractusX EDCs.

Goal of the Issue
The objective of this documentation task is to empower users to add and register a new TractusX EDC (Trudy) within their own local dataspace. The provided step-by-step guide, along with example cURL commands and testing scenarios, should enable users to successfully set up a fully running and working third TractusX EDC in their dataspace.
Note: Please note that this issue does not involve code implementation but focuses solely on creating comprehensive documentation.

This issue can be closed because the tutorial with required content is already online https://eclipse-tractusx.github.io/docs/tutorials/e2e/


make check timestamp when per-binary build

When build per-binary, it doesn't check timestamp.
If there is a binary always make says below even the binary is old.
make build/infrakit-*
make: 'build/infrakit-*' is up to date.

This PR make it check *.go file time stamp.
Signed-off-by: YujiOshima<EMAIL_ADDRESS>

Please sign your commits following these rules:
https://github.com/moby/moby/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "fixmake" git@github.com:YujiOshima/infrakit.git somewhere
$ cd somewhere
$ git rebase -i HEAD~842356607768
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.