asymptote: 2.41 -> 2.42

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/asymptote/versions.
These checks were done:

built on NixOS
ran ‘/nix/store/2qw7zf6brwdbj56dbrn9342s3l51j2d1-asymptote-2.42/bin/asy -h’ got 0 exit code
ran ‘/nix/store/2qw7zf6brwdbj56dbrn9342s3l51j2d1-asymptote-2.42/bin/asy --help’ got 0 exit code
found 2.42 with grep in /nix/store/2qw7zf6brwdbj56dbrn9342s3l51j2d1-asymptote-2.42
directory tree listing: https://gist.github.com/ea517431d1ae476366452121c7871132

cc @7c6f434c @peti for review

Success on x86_64-linux (full log)
Attempted: asymptote
Partial log (click to expand)
renamed '/nix/store/2qw7zf6brwdbj56dbrn9342s3l51j2d1-asymptote-2.42/share/info/asymptote/asymptote.info' -> '/nix/store/2qw7zf6brwdbj56dbrn9342s3l51j2d1-asymptote-2.42/share/info/asymptote.info'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/2qw7zf6brwdbj56dbrn9342s3l51j2d1-asymptote-2.42
shrinking /nix/store/2qw7zf6brwdbj56dbrn9342s3l51j2d1-asymptote-2.42/bin/asy
gzipping man pages under /nix/store/2qw7zf6brwdbj56dbrn9342s3l51j2d1-asymptote-2.42/share/man/
strip is /nix/store/fzcs0fn6bb04m82frhlb78nc03ny3w55-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/2qw7zf6brwdbj56dbrn9342s3l51j2d1-asymptote-2.42/bin
patching script interpreter paths in /nix/store/2qw7zf6brwdbj56dbrn9342s3l51j2d1-asymptote-2.42
/nix/store/2qw7zf6brwdbj56dbrn9342s3l51j2d1-asymptote-2.42/share/asymptote/GUI/xasyVersion.py: interpreter directive changed from "/usr/bin/env python" to "/nix/store/sz9x7gpmlpk05q952b9vq87hbgn26hkc-python-2.7.14/bin/python"
checking for references to /build in /nix/store/2qw7zf6brwdbj56dbrn9342s3l51j2d1-asymptote-2.42...

Failure on x86_64-darwin (full log)
Attempted: asymptote
Partial log (click to expand)
    gc_allocator(const gc_allocator&) throw() {}
    ^
/nix/store/mhxplaan93d6lja3vnzxsi5gcvdb0vbc-libc++-5.0.1/include/c++/v1/memory:1558:69: note: passing argument to parameter '__a' here
        select_on_container_copy_construction(const allocator_type& __a)
                                                                    ^
1 error generated.
make: *** [Makefile:319: settings.o] Error 1
make: *** Waiting for unfinished jobs....
builder for '/nix/store/sa0j8i40l7fkyf1qz9b4nx0x2vji9qlc-asymptote-2.42.drv' failed with exit code 2
error: build of '/nix/store/sa0j8i40l7fkyf1qz9b4nx0x2vji9qlc-asymptote-2.42.drv' failed


Use openssl library for runtime dependent

How to reproduce
Commit: f244842eab995a794ac35e5fe27e399cb4f2fa21
# In /with-nix-flakes directory...
nix build
./result/bin/lisp-webserver

Error is:
Unhandled SIMPLE-ERROR in thread #<SB-THREAD:THREAD tid=61208 "main thread" RUNNING
                                    {10002D8143}>:
  Error opening shared object "libcrypto.so.3":
  libcrypto.so.3: cannot open shared object file: No such file or directory.

Backtrace for: #<SB-THREAD:THREAD tid=61208 "main thread" RUNNING {10002D8143}>
0: (SB-DEBUG::DEBUGGER-DISABLED-HOOK #<SIMPLE-ERROR "Error opening ~:[runtime~;shared object ~:*~S~]:
  ~A." {10002D90F3}> #<unused argument> :QUIT T)
1: (SB-DEBUG::RUN-HOOK *INVOKE-DEBUGGER-HOOK* #<SIMPLE-ERROR "Error opening ~:[runtime~;shared object ~:*~S~]:
  ~A." {10002D90F3}>)
2: (INVOKE-DEBUGGER #<SIMPLE-ERROR "Error opening ~:[runtime~;shared object ~:*~S~]:
  ~A." {10002D90F3}>)
3: (ERROR "Error opening ~:[runtime~;shared object ~:*~S~]:
  ~A." "libcrypto.so.3" "libcrypto.so.3: cannot open shared object file: No such file or directory")
4: (SB-SYS:DLOPEN-OR-LOSE #S(SB-ALIEN::SHARED-OBJECT :PATHNAME #P"libcrypto.so.3" :NAMESTRING "libcrypto.so.3" :HANDLE NIL :DONT-SAVE NIL))
5: (SB-ALIEN::TRY-REOPEN-SHARED-OBJECT #S(SB-ALIEN::SHARED-OBJECT :PATHNAME #P"libcrypto.so.3" :NAMESTRING "libcrypto.so.3" :HANDLE NIL :DONT-SAVE NIL))
6: (SB-SYS:REOPEN-SHARED-OBJECTS)
7: (SB-IMPL::FOREIGN-REINIT)
8: (SB-IMPL::REINIT T)
9: ((FLET SB-UNIX::BODY :IN SB-IMPL::START-LISP))
10: ((FLET "WITHOUT-INTERRUPTS-BODY-3" :IN SB-IMPL::START-LISP))
11: (SB-IMPL::%START-LISP)

unhandled condition in --disable-debugger mode, quitting

nix-shell -p nix-info --run "nix-info -m" 's result
 - system: `"x86_64-linux"`
 - host os: `Linux 6.6.27, NixOS, 24.05 (Uakari), 24.05.20240414.f32598c`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.2`
 - nixpkgs: `/nix/store/83pgzk2zgc2iji8d65479wijairr0vgy-source`

@hraban I'm sorry to mention this, but could you help me out a little?
In case you are wondering, I have limited knowledge of CommonLisp and English, so it would be helpful if you could take that into account when you talk to me.

I couldn't reproduce this bug. However sometimes a bug can be hidden on Mac while it shows up on NixOS. This is because Mac has more global libraries available, especially for stuff like crypto.
However I did run into a different problem which I solved like this:
diff --git i/with-nix-flakes/flake.nix w/with-nix-flakes/flake.nix
index 7c40da9..f8b3e08 100644
--- i/with-nix-flakes/flake.nix
+++ w/with-nix-flakes/flake.nix
@@ -19,6 +19,7 @@
         src = pkgs.lib.cleanSource ./.;
         lispDependencies = with pkgs.lispPackagesLite; [
           clack
+          clack-handler-hunchentoot
           hunchentoot
         ];
         meta = with lib; {
diff --git i/with-nix-flakes/lisp-webserver.asd w/with-nix-flakes/lisp-webserver.asd
index 2f1b2d9..1627962 100644
--- i/with-nix-flakes/lisp-webserver.asd
+++ w/with-nix-flakes/lisp-webserver.asd
@@ -7,4 +7,4 @@
   :build-pathname "bin/lisp-webserver"
   :entry-point "lisp-webserver:main"
   :components ((:file "main"))
-  :depends-on ("clack" "hunchentoot"))
+  :depends-on ("clack" "hunchentoot" "clack-handler-hunchentoot"))

Now I can run your app:
$ nix run
Hunchentoot server is started.
Listening on <IP_ADDRESS>:8080.
$

It immediately exits because clack doesn't keep the app alive, so if nothing else keeps the app alive it quits. But that's not a problem with Nix, that's just how Clack works.
I can try on a NixOS virtual machine later but for now I don't see anything immediately wrong with this app.


SPARROW front end UI start

Added all aspects of the SPARROW mockups to the page with a mockup map in background.  One functionality I implemented was the advanced options toggle, was just needed to not show all the buttons right away.

http://stackoverflow.com/questions/107701/how-can-i-remove-ds-store-files-from-a-git-repository

@isuftin This take care of the DS_Store thing?

@mwernimont Perfect!

@isuftin better?


Consolidating all configuration scripts into a simple CLI.

Describe the the feature you would like
For the Humble release we are looking to simplify TurtleBot 4 configuration by combining the setup scripts into a single script that would have a simple menu with options for Wi-Fi setup, ROS configuration, robot_upstart install/uninstall, and more.
We are looking for some feedback from the community on your experience with the current way that we do robot configuration, and what your thoughts are on this approach. If you have any ideas or suggestions please let us know.

@roni-kreinin I have some issues transferring between RP4 and iCreate3. Therefore, I hope the procedure or process of connecting both of them could be renewed or got better. I have followed instructions from User Manual or retail dealer but there were no better results than keeping original state. Thanks!

I agree that to start working with this robot, this are rather complicated. Especially considering that this is a robot targetting beginners. I am not easily convinced that GUIs (even text mode) are always a gain, but here it is a good option. Even better however would be sane(r) defaults (e.g. fastdds) and a network setup which is less involved/more robust (no base wifi).

Here is a sample of the CLI wifi setup, let me know what you think:

@alexswerner FastDDS will be the default RMW for Humble and we will ship robots with it as the default. It will also be much easier to switch between RMW using this tool.
Regarding #26, we have found a configuration using Discovery Servers that works. iRobot is testing it and will be adding options for this to the Create3 webserver. I will add similar options to this CLI tool to make it as easy as possible to set up. There will be some configuration required on the user PC as well but I think it should be fairly simple. We still need to test performance with many robots on the same network, but I think we will see significant improvements.

Looks helpful. Small suggestion: I suggest to put the line which switches from AP to client above the SSID etc.

Humble has been released with the turtlebot4_setup tool.


test for #639

The way this is failing is... interesting, but technically irrelevant to #639. The failures are happening with the runtime objects but that should have no effect on the generated types (which it isn't). So there is a bug, but it's not the one in #639 and I haven't identified if it's a bug with how types are generated or with groq-js.


Update what-is-application-proxy.md

The note "Internal users who unnecessarily use Application Proxy can introduce unexpected and undesirable performance issues." has caused some confusion with customers when discussing adoption of a Zero Trust network architecture.
This note appears to have been migrated from pre-pandemic sources, and apart from this one note, the performance and reliability of Azure App Proxy to access internal resources from an "internal network" is no longer a significant concern.

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

@kenwith
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@jlaundry - thanks for taking the time to update the docs. I checked with support engineering and the product team and they gave the feedback that accessing a web app hosted in the internal network from the internal network directly is always faster than accessing it through app proxy. Their concern is that internal users might overload the network infrastructure of the company with generating extra outgoing / incoming traffic. I believe the note is saying that if someone is already on the internal network then routing should be configured to access the web app directly instead of going out through the Internet connection to app proxy and then back into the Internal network. Perhaps the note needs to be reworded? Thoughts?

Hi @kenwith! I understand the concern, however with the evolution into video conferencing and onto Wi-Fi, in practice, users in an office environment are more likely to cause network issues through VC applications than internal web apps.
At the same time, we're trying to move customers away from having an "internal" network at all, and statements like this note undermine the Zero Trust messaging - not to mention the security and complexity considerations with maintaining an "internal" routing and firewall rule set.

@jlaundry - I see your point and agree and contacted the product team. There is a feature in development that should release soon and then the note will be removed. Until that feature is released they would like to leave the note. Let's close this one and I will look into rewording it to make it clearer until the feature they referenced is released then we can remove the note all together. Thank you for being proactive on this. I appreciate it. #please-close
Below is the quote from the product team:
"Local access for app proxy is a feature currently in design, with authentication going through Azure AD with CA policy enforcement for enabling zero trust model. Once authenticated the data path would not need to traverse through the Internet but stay within a corporate network for better performance and reduced latency.
The above note was intended for admins as a reminder to consider network infrastructure and performance implications before implementing app proxy for internal users on a corporate network. We have seen corporate networks successfully implementing app proxy for internal users on corporate a network specially for critical applications for better security."


Send require for manage existing school

As a school-manager (SM) I want to be able to send require to be linked to a particular school because I am his SM so that I can manage existing info about my school
Acceptance criteria:

a SM send require to be a manager of particular school after click the button in page/ card of school from sign-in account.
after the verification process a SM see school in his account and can to manage it
link this SM as a school-manager of particular school inside database

We decide that it's too much


Removing cf-expandable and jquery easing

We no longer use cf-expandable or JQuery easing so I'm removing them. This is a move toward elimination of all external JS libraries and frameworks.
Testing

Run npm install && bower install && gulp build. Visit the site and browse; shouldn't see any errors in the console.

Review

@anselmbradford
@Scotchester

Checklist

[ ] Changes are limited to a single goal (no scope creep)
[ ] Code can be automatically merged (no conflicts)
[ ] Code follows the standards laid out in the front end playbook
[ ] Passes all existing automated tests
[ ] New functions include new tests
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged
[ ] Visually tested in supported browsers and devices
[ ] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)

Minor: Can you strip out easing from https://github.com/cfpb/cfgov-refresh/blob/flapjack/TERMS.md too?

LGTM 👍


Does it support self-intersecting paths?

Hi,
Would like to see if the library supports self-intersecting paths?

Yes, this doesn't affect simplifcation in any way.

thank you @mourner

what this feature also same like d3-geopath for intersection on every path like when draw multiLineString to intersect with existing point?


Traces api use local state index

Closes: #???
Description

For contributor use:

[ ] Targeted PR against master branch
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Code follows the standards mentioned here.
[ ] Updated relevant documentation
[ ] Re-reviewed Files changed in the Github PR explorer
[ ] Added appropriate labels

Closing in favor of: https://github.com/onflow/flow-evm-gateway/pull/635


fix(deps): update module github.com/operator-framework/api to v0.27.0

This PR contains the following updates:

Package
Type
Update
Change

github.com/operator-framework/api
require
minor
v0.18.0 -> v0.27.0

Release Notes

operator-framework/api (github.com/operator-framework/api)
v0.27.0
Compare Source
What's Changed

Fix some typos in cel.go by @logonoff in https://github.com/operator-framework/api/pull/343
Bump k8s.io/apiextensions-apiserver from 0.30.1 to 0.30.2 by @dependabot in https://github.com/operator-framework/api/pull/344
Bump github.com/spf13/cobra from 1.8.0 to 1.8.1 by @dependabot in https://github.com/operator-framework/api/pull/346
Fix codecov-action params by @m1kola in https://github.com/operator-framework/api/pull/349
Bump k8s.io/apiextensions-apiserver from 0.30.2 to 0.30.3 by @dependabot in https://github.com/operator-framework/api/pull/353
Bump sigs.k8s.io/controller-runtime from 0.18.4 to 0.18.5 by @dependabot in https://github.com/operator-framework/api/pull/356
Bump kubernetes libraries to v0.31.0 and controller-runtime to v0.19.0 by @perdasilva in https://github.com/operator-framework/api/pull/357

New Contributors

@logonoff made their first contribution in https://github.com/operator-framework/api/pull/343

Full Changelog: https://github.com/operator-framework/api/compare/v0.26.0...v0.27.0
v0.26.0
Compare Source
What's Changed

Bump github.com/sirupsen/logrus from 1.9.2 to 1.9.3 by @dependabot in https://github.com/operator-framework/api/pull/338
Bump sigs.k8s.io/controller-runtime from 0.18.2 to 0.18.3 by @dependabot in https://github.com/operator-framework/api/pull/339
Bump sigs.k8s.io/controller-runtime from 0.18.3 to 0.18.4 by @dependabot in https://github.com/operator-framework/api/pull/341
remove default value of catsrc.spec.grpcPodConfig.securityContextConfig by @joelanford in https://github.com/operator-framework/api/pull/342

Full Changelog: https://github.com/operator-framework/api/compare/v0.25.0...v0.26.0
v0.25.0
Compare Source
What's Changed

:seedling: Adds dependabot config to repo by @perdasilva in https://github.com/operator-framework/api/pull/326
:bug: fix ClusterServiceVersion CRD Generation by @perdasilva in https://github.com/operator-framework/api/pull/324
:seedling: Add GHA to test CRDs against kind by @perdasilva in https://github.com/operator-framework/api/pull/325
build(deps): bump actions/checkout from 3 to 4 by @dependabot in https://github.com/operator-framework/api/pull/327
build(deps): bump actions/cache from 2 to 4 by @dependabot in https://github.com/operator-framework/api/pull/328
build(deps): bump sigs.k8s.io/controller-runtime from 0.18.0 to 0.18.2 by @dependabot in https://github.com/operator-framework/api/pull/332
build(deps): bump github.com/stretchr/testify from 1.8.4 to 1.9.0 by @dependabot in https://github.com/operator-framework/api/pull/330
build(deps): bump actions/setup-go from 4 to 5 by @dependabot in https://github.com/operator-framework/api/pull/329
build(deps): bump k8s.io/apimachinery from 0.30.0 to 0.30.1 by @dependabot in https://github.com/operator-framework/api/pull/333
update kube libraries to v0.30.1 by @perdasilva in https://github.com/operator-framework/api/pull/335

Full Changelog: https://github.com/operator-framework/api/compare/v0.24.0...v0.25.0
v0.24.0
Compare Source
What's Changed

build(deps): bump golang.org/x/net from 0.21.0 to 0.23.0 by @dependabot in https://github.com/operator-framework/api/pull/321
K8s 1.30 version update and go 1.22 by @Neo2308 in https://github.com/operator-framework/api/pull/322

Full Changelog: https://github.com/operator-framework/api/compare/v0.23.0...v0.24.0
v0.23.0
Compare Source
What's Changed

:seedling: bump codecov to v4 by @grokspawn in https://github.com/operator-framework/api/pull/315
add missing comments for status fields by @grokspawn in https://github.com/operator-framework/api/pull/316
enabling merge queues by adjusting dco policy, workflows by @grokspawn in https://github.com/operator-framework/api/pull/314
build(deps): bump google.golang.org/protobuf from 1.31.0 to 1.33.0 by @dependabot in https://github.com/operator-framework/api/pull/318
Add tidy to the verify target by @tmshort in https://github.com/operator-framework/api/pull/320
Update modules to support k8s v0.29.2 by @Neo2308 in https://github.com/operator-framework/api/pull/319

New Contributors

@Neo2308 made their first contribution in https://github.com/operator-framework/api/pull/319

Full Changelog: https://github.com/operator-framework/api/compare/v0.22.0...v0.23.0
v0.22.0
Compare Source
What's Changed

OCPBUGS-25989: go.mod: bump to golang 1.21 by @stevekuznetsov in https://github.com/operator-framework/api/pull/311
Add field Subscription.Spec.Config.Annotations by @cognifloyd in https://github.com/operator-framework/api/pull/312

New Contributors

@cognifloyd made their first contribution in https://github.com/operator-framework/api/pull/312

Full Changelog: https://github.com/operator-framework/api/compare/v0.21.0...v0.22.0
v0.21.0
Compare Source
What's Changed

[chore]: Update opentelemetry to v1.20.0 by @tmshort in https://github.com/operator-framework/api/pull/309
k8s 1.28 version update and go 1.20 by @acornett21 in https://github.com/operator-framework/api/pull/292
[chore]: Re-bump opentelemetry to v1.20.0 by @joelanford in https://github.com/operator-framework/api/pull/310
Catch whitespace csv.spec.provider.name values by @komish in https://github.com/operator-framework/api/pull/272

New Contributors

@komish made their first contribution in https://github.com/operator-framework/api/pull/272

Full Changelog: https://github.com/operator-framework/api/compare/v0.20.0...v0.21.0
v0.20.0
Compare Source
What's Changed

OWNERS: Remove timflannagan from reviewers by @timflannagan in https://github.com/operator-framework/api/pull/305
Add 'OperatorDeprecated' status condition for Subscription by @dtfranz in https://github.com/operator-framework/api/pull/306
Additional Deprecation Types by @dtfranz in https://github.com/operator-framework/api/pull/307
Replace github.com/ghodss/yaml with sigs.k8s.io/yaml by @Juneezee in https://github.com/operator-framework/api/pull/308

New Contributors

@dtfranz made their first contribution in https://github.com/operator-framework/api/pull/306
@Juneezee made their first contribution in https://github.com/operator-framework/api/pull/308

Full Changelog: https://github.com/operator-framework/api/compare/v0.19.0...v0.20.0
v0.19.0
Compare Source
What's Changed

Separate Category and Capability Validation by @kevinrizza in https://github.com/operator-framework/api/pull/304

Full Changelog: https://github.com/operator-framework/api/compare/v0.18.0...v0.19.0

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: go.sum
Command failed: go get -d -t ./...
go: github.com/opendatahub-io/opendatahub-operator/v2/controllers/datasciencecluster tested by
	github.com/opendatahub-io/opendatahub-operator/v2/controllers/datasciencecluster.test imports
	sigs.k8s.io/controller-runtime/pkg/envtest imports
	k8s.io/apiextensions-apiserver/pkg/client/clientset/clientset imports
	k8s.io/apiextensions-apiserver/pkg/client/clientset/clientset/typed/apiextensions/v1 imports
	k8s.io/client-go/gentype: cannot find module providing package k8s.io/client-go/gentype


SP5 Tests: Why does dotnet test crash but running tests in VS works? 🔥

Open the full solution and run tests, no problem

However if I open a console in src\ScottPlot5\ScottPlot5 Tests and dotnet test I get:
The active test run was aborted. Reason: Test host process crashed : Unhandled exception. System.NullReferenceException: Object reference not set to an instance of an object.
   at SkiaSharp.SKAbstractManagedWStream.WriteInternal(IntPtr s, Void* context, Void* buffer, IntPtr size)
   at SkiaSharp.SkiaApi.sk_canvas_destroy(IntPtr param0)
   at SkiaSharp.SKCanvas.DisposeNative()
   at SkiaSharp.SKNativeObject.Dispose(Boolean disposing)
   at SkiaSharp.SKObject.Dispose(Boolean disposing)
   at SkiaSharp.SKCanvas.Dispose(Boolean disposing)
   at SkiaSharp.SKNativeObject.Finalize()

It seems to be sensitive to the number of tests. Using various --filter options I found that this error happens when there are about 35 images, but no test itself causes the crash

More info, the ScottPlot cookbook test project seems heavier, but it runs fine (61 tests)

Adding [SetUpFixture] to each class solves this issue, but I'm still unsure why

minimal reproducible error:
Keep just these files

dotnet test --filter=RenderTests

new information: combining all [Test] methods into a single class prevents this issue

new information: added [Parallelizable(ParallelScope.Children)] to classes prevents this issue
https://docs.nunit.org/articles/nunit/writing-tests/attributes/parallelizable.html

More details! I can recreate the issue if I run the VS tests in debug mode

I think this bit of code may be the culprit
https://github.com/ScottPlot/ScottPlot/blob/6b3ee06f5f946c4a35312cf9922974bd424d2e28/src/ScottPlot5/ScottPlot5/Legends/Legend.cs#L63-L70

I think this bit of code may be the culprit
https://github.com/ScottPlot/ScottPlot/blob/6b3ee06f5f946c4a35312cf9922974bd424d2e28/src/ScottPlot5/ScottPlot5/Legends/Legend.cs#L72-L79

After several hours I figured out the two tests that call GetLegendImage() and GetLegendSvg() can be disabled and tests run fine. I suspect this bug was introduced in #3062. I'll close this issue and re-open #2934


episodes byITunesId duration

The Schema for episodes By iTunes Id states duration to be in minutes but it seems to be in seconds.
All the best
Sig

Thanks for pointing that out. I'll push an update soon.


Add note on conceallevel option for config

Clarification from info collected in #264 to help people who wish to enable or disable the function.

Thanks @Msouza91!


Update changes

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
Proper branching of python assigment-1
What did you learn from the changes you have made?
Correctly branching in Git/shell
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
Nothing
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
New learning, and to read the instruction first.
How were these changes tested?
In python with different arguments
A reference to a related issue in your repository (if applicable)
N/A
Checklist

[X ] I can confirm that my changes are working as intended

you did a great job here!
Please go ahead and close this pull request now. Thanks!


Use port 8443 to communicate with cmsweb services

Fixes #8565
Replaces #8704
Instead of changing every single place that defines a cmsweb endpoint, we can simply change it in this base class and make sure the other Services modules inherit from it (there seems to be a few that don't).

smart. :smile:, Is there any case we are not using Service class?  how about dbs apis?

Yes, I see quite a few, including DBS3Reader and possibly some legacy modules.
I'll create those changes in another PR, if it's straight forward, then we add to today's agent release, otherwise this change will touch the bulk of the cmsweb requests.

BTW, I ran the DMWM tests on an agent with this patch and I see data was uploaded to the DQM GUI, workflows properly completed, dbs and phedex stuff also done. I think we're good with this change.

Thanks Alan,

Before I forget, @belforte @hufnagel if you build T0/CRAB using tag 1.1.15 or newer, this change will be in. So any of those modules under WMCore/Services that inherit from Service class, will be talking to CMSWEB services through the port 8443 instead of 443.
It should be transparent to your services, but just in case :)

thanks

Hi Alan, I am likely missing something, but looking at what's new there (to get a sense
of what to test) I do not see anything in the way of DBS URL.
On 10/08/18 20:57, Alan Malta Rodrigues wrote:

Before I forget, @belforte https://github.com/belforte @hufnagel https://github.com/hufnagel if you build T0/CRAB using tag 1.1.15 or newer, this change will be in. So any of those modules under WMCore/Services that inherit from |Service| class, will be talking to CMSWEB services through the port 8443 instead of 443.
It should be transparent to your services, but just in case :)

forgot the URL I have used to compare
https://github.com/dmwm/WMCore/compare/1.1.14_crab...1.1.15_cmsweb
On 17/08/18 18:30, Stefano Belforte wrote:

Hi Alan, I am likely missing something, but looking at what's new there (to get a sense
of what to test) I do not see anything in the way of DBS URL.
On 10/08/18 20:57, Alan Malta Rodrigues wrote:

Before I forget, @belforte https://github.com/belforte @hufnagel https://github.com/hufnagel if you build T0/CRAB using tag 1.1.15 or newer, this change will be in. So any of those modules under WMCore/Services that inherit from |Service| class, will be talking to CMSWEB services through the port 8443 instead of 443.
It should be transparent to your services, but just in case :)

Hi Stefano, you are right. DBS is not included here. We can temporary switch DBS port here by overwriting URLs in WMCore/Service/DBS package, Or wait for DBS client source handle this. I think it is cleaner dbs client handle that. But if you prefer we can add that here temporary.

thanks @ticoann. Let's wait. I do not need do to test things now. Only wanted to have a sense of what to look if I build with new tag.


Add checks for genotype file uploads

Confirm that the user uploaded genotype files are valid before starting each analysis

Confirm that their are no duplicate sample IDs

If there are, list the IDs to the user, and add the option to have them removed from the analysis or to pause the analysis

Check that the max ploidy level in the genotypes file agrees with the user selected ploidy level
Check if there are multiallelic markers
Check if the required field is present. Exemple: GT, AD, DP

VCFs without updog quality measures are returning errors in the VCF Filtering tab.

Currently, each tab has a different way to process the VCF and MADC file, filtering for different aspects. It would be better if we have a single function applied to every tab to check the files format and if they have all information needed. This will reduce code redundancy and avoid bugs while users are uploading files.


Get Swift compiling with MSVC again

Commit 1
Fixes "error C2678: binary '!=': no operator found which takes a left-hand operand of type 'Serialized' (or there is no acceptable conversion)"
There is an acceptable conversion, MSVC!
https://connect.microsoft.com/VisualStudio/feedback/details/3121202
#include <iostream>

class Decl { };

// Has to be a subclass - using Decl works.
class ValueDecl : public Decl { };

class Serialized {
public:
  /*implicit*/ operator Decl *() const {
    return nullptr;
  }
};

// Has to be const.
void Execute(const ValueDecl *parent) {
  Serialized serialized;

  if (serialized != parent) {
    std::cout << "Hello, World";
  }

  // Replacing the if block with the following is the workaround.
  /*
  Decl *converted = serialized;
  if (converted != parent) {
    std::cout << "Hello, World";
  }*/
}

int main() {
  Execute(nullptr);
}

Commit 2
Fixes warnings "not all control paths return a value"
All control paths are covered, MSVC!
https://connect.microsoft.com/VisualStudio/feedback/details/3121201/msvc-doesnt-detect-a-fully-covered-switch-statement-of-an-enum-class

@swift-ci please smoke test

LGTM, thanks!


Error Code. Pop! OS v 20.10

Error Code: 110775B5D101FB36BC6C911BEB774491D9FF06E2: Key Expired
If the message persists report the above error

Maybe it's way less secure but because of that error I installed the .deb version in the pop_shop which worked but maybe not that isolated like a flatpak. Not sure if this is important.

Same issue as #543.

@MotherOfPerls Do you use a Flatpak Tor Browser Launcher or a regular deb one?

I fixed the issue. Instead of downloading it from the pop shop (package manager), I just downloaded it from the website and it worked fine lol.

Duplicate of #534


Update discord link

Just found out about svelte-ux, looks great.
It seems that tour discord links are outdated, maybe you could refresh them?
Thx

Thanks!  Not sure why the link broke. I'm currently AFK and having trouble updating on my phone. I think the server ID is now cKChJ4R6. Not sure why it changed, or when. Could you send a PR by chance?

@jycouet Fixed.  Thanks for the report.  Not sure what caused it to change


MERC-409: Enable theme specific builds

What
Removing JSPM in favor of Webpack. Also, enable developers to utilize their own stencil-cli integrated build process if Webpack is not a favored tool for the developer of a theme.
Why

Remove the need to install JSPM as a global tool and requiring jspm install.
Speed up the page load time by downloading a single bundle rather than many files over multiple ajax connections.
Enable the build to be completely theme driven and not forced by the platform.

Testing
Fetch and checkout this branch and then npm install
Clone stencil utils and checkout this branch https://github.com/bigcommerce/stencil-utils/pull/56
npm link stencil-utils and npm link @bigcommerce/stencil-utils here in the theme
Fetch and checkout this branch https://github.com/bigcommerce/stencil-cli/pull/201
npm install within stencil-cli
stencil start and develop like normally.
See stencil.conf.js for the development and production build steps.

Build here is failing because it depends on a new version of stencil-utils.

Anything before I merge this?

:+1: Do we need QE to test this?


Remove unncessary GOARCH and GOOS from .ensure-httpserver

Those keep the integration tests from running on non-amd64
hosts with golang.
Signed-off-by: Christy Perez<EMAIL_ADDRESS>

Just doing a little golang exploration and ran into an build failure as part of the test run. I tested this patch in a few different environments and everything seems fine -- but I feel like these env vars probably weren't put there just for fun, so if anyone has any insight as to why they might need to stay, I can always go another route.

Looked weird indeed
LGTM

mmm I feel like we need that to run the windows cli suite, but the build is too broken to verify :pensive:

/cc @jhowardmsft

I've got to be honest, I have absolutely no idea or context as to what this change means to be able to constructively comment on it. We don't currently have CI running against a Windows daemon, although I'm working actively on getting much of the integration-cli suite running. I haven't come across a test yet that uses an HTTP server in this way while going through that exercise. I don't think it would make a difference for a Windows client running CI against a Linux daemon, but I'm not certain. We need @jfrazelle to fix the current Windows to Linux CI machines to verify that! ;) They've been out for way too long now.

Yes, this was added specifically for testing the windows CLI, but the whole
thing could be replaced with a frozen nginx image instead.

I originally had a different version of this that defaulted to what's currently there, but if the proc (checking uname -p) was ppc64* or s390*, then GOARCH was changed to uname -p.
I could also look into the nginx image. @tianon, WDYT?

ping @tianon

I think switching to the nginx image is probably our best bet at this point -- the reason this cross-compiles is so that we create a linux/amd64 binary to inject into the tests so that we can test on a Windows client platform with a Linux daemon.  If we use a frozen image, that's not really a concern anymore (and then new backends "just" need to figure out some way to get a copy of nginx).  Alternatively, we could vendor the "golang" image and just use that directly in the tests to compile the source via docker build; I'm not really partial to one way or another except that a golang image would probably be easier to create on new architectures than an nginx image might be.

Just FYI, I got a lgtm in #17480 from the author of this file.

@tianon Can you explain what you mean by "vendor the "golang" image?" I'm guessing you mean add another image that would then be pulled in as a "frozen" image -- and we'd build httpserver using that. The thing that I think makes me hesitate there is that we'd need another Dockerfile (one for each arch) for that, IIUC.

@taianon, et al., please ignore this latest build for now.

Where are we on this?
@clnperez wrt your last comment, is this ready for another review, or were you working on it?

@thaJeztah, I'd like to hear back from @tianon to clear up the confusion on my end -- and also see what he thinks of this recent if block approach. It's a lot simpler (but would need some other architectures added, like s390 and maybe arm).

ping @tianon can you give a look and answer https://github.com/docker/docker/pull/16664#issuecomment-155607880? Trying to move some PRs :heart:
(Thanks @clnperez )

ping @tianon

@clnperez Could you please test again, if your PR is already necessary? We just introduced a fix for this problem on a non-"linux/amd64" architecture with #17803. Our fix works great on "linux/arm" and should also work on all other platforms as well.

As @DieterReuter points out, this is not necessary anymore. Closing this PR.
Thank you all!

Hey, great. I just tested this out and it looks like it works for me now.  Thanks guys!

Thanks for the feedback. Glad to help.


Update files and create a starter Makefile: build_bundler.sh, bundle.c and create a Makefile to start things off

Updated build_bundle.sh to include compiler-found logic - if it cannot find clang, use gcc, if thats not found either, use cc
Updated bundle.c to include -h and --help to help show usage and improved file readability.
Create a Makefile to get things started. To learn about a thing or two about Makefile (like how I did) click here
Update the README.md to be up to date

hi! thank you for pull request, but some things gonna change after merging:

my personal nit: i like everything lowercase
i dont see a point in build scripts with a mature makefile


Only keep mitigated items from scan reports, and don't reactivate them

Is your feature request related to a problem? Please describe
This problem comes with specific scanners. Mostly, scanners that do no have mitigation timestamps, or a triage system.
They will always return all findings, and the only way to remove them is to add comments in your source etc...
The problem with that is that defectdojo's reimport API will keep reactivating findings, even if you triaged things in Defectdojo.
If the scan has "mitigated" timestamps it could be easy to understand where the finding has been mitigated first: defectdojo or your scanner. But this isn't the case and that's why the idea is the following:
Describe the solution you'd like
Add a Do not reactivate check box in the reimport form, with a subtext like "Select if the import should ignore active findings from the report, and keep existing findings closed, without reactivating them."
When checked, the parsing will ignore incoming active findings that match a closed finding in Defectdojo. This prevents reactivating them for no reason, and you can set that option for the "dumb" scanners that give reports without enough information.
Basically, it will enable users to accumulate triage information without reopening findings. Even for "smarter" scanners that including triage information, it can be useful to basically let Defectdojo override any opened issue coming from a scanner, if the triage was done once, it will stay like that. (Can be dangerous if your scanner will reopened issues legitimately...)
Describe alternatives you've considered
There is no alternative, because semgrep, tfsec and other scanners don't have that information in their report. You need to persist the triage information otherwise it can reopen the findings for no reason.

The PR was merged. Can we close this @mtesauro?


Fixing sample for runtimes list - Mac OS case

The sample had the command for SDK, not runtimes
Summary
Describe your changes here.
Fixes #Issue_Number (if available)

Thanks for catching this!


Update: stackless.stackless version 3.3.5

Removing old versions to reduce clutter
Microsoft Reviewers: Open in CodeFlow

/azp run


Car app export path is forgotten

Car app export ask for the path again and it's not even starting at the previous location.

The latest release v1.1.1 has resolved this issue. Please reopen if the problem persists.


[Wasm] Initialise go wasm to be used in the Meshery-UI and Meshery-extensions

Notes for Reviewers
Need for wasm:

Some complex decisions like schema verification and its alterations is being done in JS that makes the code less performant, neither we can rely on server for its execution because of network trip, rather it is required to be executed via our wasm binaries that runs them in the browser itself in a type-safe manner(unlike JS)
In extension, the ctx-aware relationships and calculations should be done via some typesafe and faster language rather than JS.

Setup:

Wasm go-files can be located anywhere, if it solves for Meshery, it can go under Meshery or if for extension, it can go under extension.
But, the final binary produced should come under "/public/static" folder so that next.js could pick it up and it is not bundled in extension.

playground route: /wasm-playground
This PR fixes #
Signed commits

[x] Yes, I signed my commits.

Woah, using WASM could be a game-changer in terms of long-term performance. This is nice. :rocket:

@Abhishek-kumar09 How is this being built?
Is there a command being used to build, either with Tinygo or Go itself with the WASM turned on?

Thanks for pointing out, I've to add the command in the makefile and the npm scripts.
For handy, it can be: GOOS=js GOARCH=wasm go build -o main.wasm

Okay, we're just doing a different directory that house the Go code for WASM purposes right?

Yes.


Stateful connections?

Hello, and thank you for making this project! My question is this: Will channels eventually support stateful connections?
I found this statement in the excellent documentation:

Channels is network-transparent and can run on multiple workers, so you can’t just store things locally in global variables or similar.

I'm currently using Tornado's WebSocketHandler for websockets (hackily integrated with Django) and Django for all else. The websocket handler performs an I/O expensive step when a connection is opened, but can respond to messages received over the websocket quickly afterward. It seems as though using channels for my use case would require this expensive step to be performed for each message received.

Channels' design deliberately prevents you from having local state on connections, since it's inherently difficult to scale unless all your connections are exactly equal. Instead, channel_session is provided, which uses the Django session framework to allow you to persist things against sockets, so you can do things at connection or during a message receive and retrieve them later.
It does not, however, help you if the thing you're doing to a socket state is inherently local, such as opening a subprocess or a local file; if that's the case, Channels is likely the wrong design for you and you need to go another route and sticky WebSockets to custom local processes, and design your own broadcast/inter-node routing system.


(feature request): include unicode icons

if there could be away to include unicode_page_00.png to unicode_page_ff.png in the exported ttf that would be super useful
if you are able to or have the time to, it would be very helpful

Hi, are you trying to get the Unicode icons from the default resource pack or from a custom resource pack? I ask because the Unicode icons in the default resource pack are identical to the GNU Unifont, so depending on your situation you could just download the GNU Unifont.

I would also like this feature, the unicode icons from the default pack. The GNU Unifont aren't exactly the same. Some character like ▚ are different.


Figuring out HTML 5

OPS Build status updates of commit 001a651:
:clock10: Preparing: average preparing time is 38 sec(s)

OPS Build status updates of commit 001a651:
:clock10: Incremental building: average incremental building time is 18 sec(s)

OPS Build status updates of commit 001a651:
:warning: Validation status: warnings

File
Status
Preview URL
Details

enterprise-graph/index.yml
:warning:Warning

Details

enterprise-graph/index.yml

[Warning] Author Stephen Flanagan cannot be recognized in GitHub.

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


Provide a docker image that works on arm64

I'm trying to use excludarr, however my setup is all running in a raspberry pi 4 (arm64 processor). I'd really love to include this application in my setup since space is an issue and being a Python script I think it could be done relatively easy.

Hi! Thanks for your request. Sounds like a plan! Never thought about it that the current one is not working on arm :). I will run some tests the upcoming days and try to add a dockerfile as soon as possible.

Thanks for the promp request, I think it would be a valuable addition to the image (it would definitely be valuable for me). Best regards!

Hi, I have changed the build workflow so that it now also creates a arm64 container. However I am not able to test this. Could you maybe test this for me? Version v1.0.6 (or just latest) is build for arm64.
Looking forward to hear from you!

I’ll test this today and report back to you as soon as I can 😉

It seems to be working alright so far, I think it's safe to close the issue.

Thanks for testing it out and glad that it works! So you are saying that the SONARR_EXCLUDE="Queen of the South, Breaking Bad" should be SONARR_EXCLUDE=Queen of the South, Breaking Bad in order to get it working?

At least in my setup, yes

Thanks! Will update it :)


Do not delete connection (WalletConnect) when reset wallet

Describe the bug
Do not delete connection (WalletConnect) when reset wallet
To reproduce the behavior
Steps:

Connected dApp via WalletConnect successfully
Perform reset wallet
After reset successfully, import account then re-open list connection of the WalletConnect

Actual: Still show connection
Expect: Delete connection when reset wallet

Version test: https://file.cdmteck.com/s/4oimk9zDJ8R5Aai/download?path=%2F&files=./upgrade-ui-pr-1764-build-1.1.7-0-2023-08-09T05-24-20UTC.zip
Validation passed for cases:

Forget account
Erase all
Re-check Upgrade version


Feature/#43

Description of what I changed:

Added to cards shadows
Change what we do text colour and padding

@Bawanthathilan right side text is not balanced with the left side lot of space. Can you fix it as well?


Azure OpenAI: 2.1.0-beta.1, including /realtime preview support

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.AI.OpenAI


ANY.RUN: New App - new connector

Please ensure your pull request (PR) adheres to the following guidelines:

Please refer to our contributing documentation for any questions on submitting a pull request, link: Contribution Guide

Pull Request Checklist
Please check if your PR fulfills the following requirements:

[x] Testing of all the changes has been performed (for bug fixes / features)
[x] The manual_readme_content.md has been reviewed and added / updated if needed (for bug fixes / features)
[x] Use the following format for the PR description: <App Name>: <PR Type> - <PR Description>
[ ] Provide release notes as part of the PR submission which describe high level points about the changes for the upcoming GA release.
[ ] Verify all checks are passing.
[x] Do NOT use the next branch of the forked repo. Create separate feature branch for raising the PR.
[x] Do NOT submit updates to dependencies unless it fixes an issue.

Pull Request Type
Please check the type of change your PR introduces:

[x] New App
[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation
[ ] Other (please describe):

Security Considerations (REQUIRED)

[ ] If you are exposing any endpoints using a REST handler,
please document them in the manual_readme_content.md.
[x] If this is a new connector or you are adding new actions

[x] Please document in the manual_readme_content.md all methods (eg, OAuth) used to authenticate
with the service that the connector is integrating with.
[ ] If any actions are unable to run on SOAR Cloud, please document this in the manual_readme_content.md.

[ ] Are you introducing any new cryptography modules? If yes, please elaborate their purpose:
[x] Are you are accessing the file system? If yes, please verify that you are only accessing paths returned through
the Vault API.
[ ] Are you are marking code to be ignored by Semgrep with nosemgrep?
If yes, please provide justification in an additional comment next to the ignored code.

Release Notes (REQUIRED)

Provide release notes as part of the PR submission which describe high level points about the changes for the upcoming GA release.

What is the current behavior? (OPTIONAL)

Describe the current behavior that you are modifying.

What is the new behavior? (OPTIONAL)

Describe the behavior or changes that are being added by this PR.

Other information (OPTIONAL)

Any other information that is important to this PR such as screenshots of how the component looks before and after the change.

Pay close attention to (OPTIONAL)

Any specific code change or test case points which must be addressed/reviewed at the time of GA release.

Screenshots (if relevant)

Thanks for contributing!

@anyrun-integrations - This submission is great! Is this connector going to fully replace community developed https://github.com/splunk-soar-connectors/anyrun ?

@edro15 - Preferably yes, with time. We plan to fully support this connector in a long run and improve it, based on our clients feedback. I still consider it an early version and i'm pretty sure that there will be many changes to it, since our API will evolve and improve as well.

@edro15 - Preferably yes, with time. We plan to fully support this connector in a long run and improve it, based on our clients feedback. I still consider it an early version and i'm pretty sure that there will be many changes to it, since our API will evolve and improve as well.

Hi @anyrun-integrations
Our security system has detected a security vulnerability in the 3.9.3 version of the 'aiohttp' library. These vulnerability issues are fixed in the version 3.9.4
So, we would recommend that we update the library version 3.9.4
Please provide your feedback regarding the same.

Hey @ishans-crest
I've replaced 3.9.3 with 3.9.4 in the last commit. Please have a look.

Hi @anyrun-integrations.
There seems to be a typo in the licensing of your pip package - here
It is one of the reasons why the static test is failing.

Hi @ishans-crest
anyrun pip package isn't ours. In this app we use a different package that wasn't published yet - anyrun-py. I can remove it from requirements.txt for now, if it's an option.

Hi @anyrun-integrations
Yes. Please remove it from the requirements.txt if the code doesn't use it.

Hi @anyrun-integrations
We have made the necessary changes from our end.
Could you please test the latest code from your end?
Thank you.

Absolutely. Do upgrade the Library. Please re-test the app after doing so.
Thanks.

Hello.
We have some changes planned for our API, that will require some parts of the app to be adjusted. The changes are expected to be implemented within next 2 weeks. Can we delay the app release until then?

Hey @ishans-crest
We have finished testing, everything seems to be working as expected. Apologies for keeping you waiting, please take a look.


[sealer-app] add sealer app build context and kubefile

Describe what this PR does / why we need it
1, add helm :registry.cn-qingdao.aliyuncs.com/sealer-apps/helm:v3.6.0
Does this pull request fix one issue?

Describe how you did it
Describe how to verify it
Special notes for reviews

already split this pr via image type, so close it.


Improvements non git mixin

This is the start of getting the improvements-non-git-mixin up to speed and worked towards its completion.
Basic changes found here:

upload_file now takes in a commit_message. This was part of the intended implementation, so trickled it up. This also allows for the back-ends to write custom messages for if something is a weight, tokenizer, etc, mimicking how Repository can do so already.
Added a test in test_hubmixin that makes sure the timings for uploading a new file to a blank repo, and uploading a new file to a repo with fairly large files is about the same. Currently the fake repo uploads 5 .5mb files (locally this took 12 seconds to accomplish. If we want to lower that to one .5mb file that's okay)

Nope! That should be about it for this PR. Will make the adjustment + merge, then will work towards the list


debug flag

EDIT: the actual use case: a mobile developer has a toggle in the app that allows him to mark all requests the app makes to the server with "please trace" flag (e.g. http header or by other means). When the server receives such request and starts a new trace, it wants to mark that trace as "debug" to ensure that it is preserved regardless of the sampling decisions.

It would be nice for start_trace method to accept an optional debug flag. Ultimately, all tracing systems will have to do some form of sampling, either before or after the trace. A debug flag allows users to force the sampling of the trace regardless of other sampling decisions.
While we can handle debug flag as an optional tag using the approach in #19, for systems that make upfront sampling decisions there are certain housekeeping operations that can be skipped (for efficiency reasons) when the span is being created if the tracer decided not to sample it. Examples may include adding various tags to the span, that would be a waste of CPU clocks and memory for non-sampled span. Therefore, setting a debug flag after span creation may cause those spans to be missing the tags they would've gotten had it been known that they are going to be sampled.

Why not make debug-ness the responsibility of the Recorder? (That's what I'd had in mind) I completely agree that it's an important use case, but I'm not clear why it needs to be part of the StartTrace signature.

I updated the description with the actual use case. The "debug"-ness is a property of an individual trace controlled by some custom property of the incoming request. It's not a mode of the Recorder, the same tracer/recorded should be able to accommodate both debug and non-debug traces.

Dapper dealt with this by propagating a "trace_mask" along with the "trace_id" and "span_id" over the wire. The mask encoded information about the sampling rate and whether there was an "explicit" sampling or the usual pseudorandom sampling.
Somewhat related: I think there's definitely value (is there even an alternative??) to propagating whether and how the current context is sampled for systems like zipkin/dapper that do a priori sampling, I wouldn't want to equate that with a "debug" context. I.e., maybe all debug contexts are explicitly sampled, but all explicitly sampled contexts are not debug contexts.

Zipkin also encodes debug / sampled as bits in the flags trace context field, but that doesn't help with the question of how the debug bit gets set when starting a new trace.
Interesting point on debug context, it indeed can mean more than just forced sampling, but how do we mark a context as debug? Users don't even have a say in context creation, all they do is call start_trace.

In golang, how about just myTracer.StartTrace("opname").TraceContext().SetTraceTag("debug", "true")? I.e., this seems like precisely the sort of thing we should be able to accomplish with trace tags / metadata.

Sure, that's the simplest way, but as I mentioned, StartTrace() may already do some data collection, or rather not do it because the sampler turned down the new trace.

Ah, I see what you're saying, and I think you raise a good point. It's an edge case but one we should be able to support (at least in a "make the hard things possible" sort of way).
Something similar to StartTraceWithTags(operationName string, traceTags map[string]string)? Or StartTraceWithContext(opName string, ctx TraceContext)? (I like the latter more than the former, though neither makes me feel cheerful about API clutter)

If you're open to extending the API in such manner, then I have slight preference for the former, because forcing instrumentation to create context manually is a lot more work than passing a debug=true attribute. Root context can only be created from the Source, and instrumentation doesn't even need to be exposed to the concept of the Source. Note that API clutter is primarily a Go issue only, in Python I would just do
def start_trace(self, operation_name, **trace_tags)

BTW, as I was converting our Python to OTAPI naming, I kept the name metadata instead of trace tags, with methods context.set_metadata(key, value). I like that it clearly separates key/values on the Context from tags on the Span and on the Recorder (which also ultimately become part of the span). I.e. tags are per-span, and stored out of band, thus are relatively cheap, while metadata is per trace, and propagates in-band.

(Agreed that this is easy in python, Java, js, etc, etc...)
At the moment there's little distinction between the two things I proposed since TraceContext per se doesn't really expose anything beyond SetTag at StartSpan()-time. If we add other capabilities to TraceContext, though – or helpers like the ones in ext/ – that might change. I also don't feel strongly but still think it'd be preferable to take a TraceContext since it's more general and this is not the common case.
Re metadata vs trace tags: On the one hand, I also don't love trace tags since they aren't even compliant with the opentracing.Tags type (string -> string, the key restrictions, etc). That said, the term "metadata" is so general: I wish we could come up with something self-descriptive. I have sat here for a few minutes and came up empty, though :)

Do you have some examples in mind what other functions might be added to the trace context?
Just read through wikipedia on "metadata", no revelations either. Strictly speaking, span tags are also metadata of spans, depends on where we draw the line what the span data is. Having said that, when I mention "context metadata" to people, they usually grasp right away what I mean.
Another possible term is "attribute". We're propagating a context, and context has attributes. The word "attribute" seems more tightly coupled with the containing entity than "tag": tag is external to the entity (ie metadata, damn), while attribute is internal, inseparable.

"Attribute" seems better than "metadata" to me. What it still doesn't convey (I doubt any common word does) is how these tracecontext-level key:value pairs propagate. But I can live with Attribute for sure.
By the way, as an optimization I could imagine restricting attribute setting to Span construction time... This would allow the span's TraceContext to be immutable and thus lock-free for reads. (I don't like optimizing without a hotspot in a profile, though)

hm, requiring all context attributes to be known upfront may be unrealistic. I can imaging a scenario where some security credentials are retrieved/calculated and added to the context after the trace has started. Like you I am not too worried about optimizing for locks until we need to.

let's go with attributes then, this is a fairly common term that implies propagation / permanence, e.g. in HttpSessions etc.

(re knowing context attrs up-front: the implication would be to start a sub-span if need be)

Sounds good to me re "Trace Attributes". So, before closing this, we want to:

%s/TraceTag/TraceAttribute/g
make it possible to add trace attributes as part of StartSpan (in golang I'd still like to enable this by allowing a user-provided TraceContext)

want to share the actual instrumentation code in Python:

    def before_request(request, tracer):
        context = tracer.unmarshal_trace_context_str_dict(
            trace_context_id=request.headers,
            attributes=request.headers
        )
        operation = request.operation
        if context is None:
            span = tracer.start_trace(operation_name=operation)
        else:
            span = tracer.join_trace(operation_name=operation, parent_trace_context=context)
        # add various tags from request
        return span

In order to support debug flag, I think the main piece would change like this:
        if context is None:
            context = tracer.new_root_trace_context()
            if request.is_debug():
                context.set_trace_attribute("debug", True)
            span = tracer.start_span_with_context(operation_name=operation, trace_context=context)
        else:
            span = tracer.join_trace(operation_name=operation, parent_trace_context=context)

i.e. tracer.start_trace() is not used

^^^ makes sense... I like the look of start_span_with_context in this code, I hope it works for you?

Yeah, I think it works. It bothers me that we don't seem to need start_trace anymore :smile: but I think it has its use for making easy things easy. FWIW, we've had a round of NodeJS apps instrumentation, with the help of app owners, and they really didn't want to write the code like above, we ended up providing a helper function like getSpanFromHeaders.
I'm going to close this issue.


[BrokenLinksH2] Fixed the link path

Fixing link

Global effort to fix broken links
@MandiOhlinger
The Content & Learning team is fixing broken links on docs.microsoft.com for the rest of H2. This effort will eliminate potential accessibility, security, and usability issues. This Draft PR includes a broken link to an article that we could not locate in this source page. Please review within five business days and point us to the right direction, or comment in the PR with any changes you'd like to see. Thanks!

Docs Build status updates of commit d879239:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

biztalk/adapters-and-accelerators/accelerator-hl7/step-12-configure-orchestration-shapes.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit c3f6461:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

biztalk/adapters-and-accelerators/accelerator-hl7/step-12-configure-orchestration-shapes.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@v-sidlama Thank you!


README Updates: Added Headings & Fixed Grammar/Typos

I noticed some small typos as I created the documentation for this repository, so I cleaned up any remaining typos and updated the README also to reflect that.
I also added extra headings to improve the structure of the README, and added extra sentences for further illustration, however, feel free to remove these where you see fit.

@silvia-odwyer I am really thankful for your help with documentation page and the readme.


made changes the in project sections that was not working properly earlier.

made changes only in project data files as error was in that file only. Now both links are working properly.

Check it and verify before merging


Add azure public ip label

Add a public IP label to Azure config

Can you add a DCO and update the docs?

Can you add a DCO and update the docs?

Added Docs and rebased with DCO.

That's failing to build. Are you sure you've the right field name?

Thanks!


[iOS] libRNCSlider.a not found in release mode

Environment
RN 0.59.1
Plugin V : latest
Platform : iOS
Description
Run into production mode appears this issue

Reproducible Demo

I've added a PR for this, fixed by #30

Thanks @IjzerenHein and @cinder92
It's a release blocker, @michalchudziak can the PR be reviewed soon ?

Yes, I'll take care of it today. Thanks for submitting a PR @cinder92

Actually it was @IjzerenHein 's PR (https://github.com/react-native-community/react-native-slider/pull/30). It's already merged and published in version 1.0.4.


CI: Fix most deprecation warnings from GitHub Actions

This fixes most deprecation warnings from GitHub Actions.
Changes:

CI: Replace deprecated ::set-output command
CI: Replace deprecated ::save-state command
CI: Bump dtolnay/rust-toolchain from v1 to master
CI: Replace Ana06/get-changed-files by tj-actions/changed-files

Fixes #1074

I'll add a changelog in my next rebase.
I'll also try to find a good replacement for the (apparently) unmaintained Ana06/get-changed-files action.

I'll add a changelog in my next rebase.

The changes are internal so it's not required, since it's just a change to our Github actions.

For the dtolnay/rust-toolchain action, I'll also have to use @master instead of @v1, just to get rid of other ::set-output warnings. Is that okay with you guys?

I'm personally fine with that until a new release is out, especially since it's dtolnay.

I'll also try to find a good replacement for the (apparently) unmaintained Ana06/get-changed-files action.

Thanks, if you can't find one, any contribution is more than enough. We might have to fork it, change the output variables, pin it, and hope it's minimal work to update again.

From the action

readarray -t added_modified < <(jq -r '.[]' <<<'[".changes/1135.json"]')
parse error: Invalid numeric literal at line 1, column 3

Not sure why this is showing up now, I'm more than happy to add the no changelog label once this is merged because that shouldn't be happening.

Okay, I think the changes look good now.
The 'changelog check' job is getting skipped now, but just to make sure it still works, I tested it on on my local repository and it passed. (test commit here)
I also renamed the PR because I ended up changing more stuff other than just the ::set-output warnings.

Okay, I tried to address @Emilgardis's comment to the best of my Rust knowledge.
Hope it isn't that bad... 😅

Just that minor nit on the panic, since we return a result now. Otherwise, looks good to me. I'll leave the full review to Emil.

I addressed the last two comments. Thanks a lot for the reviews, by the way. :)

bors try --target unknown-linux

Okay, we're down from 1000+ warnings to 478, which is still quite an expressive number.
I think I underestimated a bit the complexity of your CI... 😆
However, it should be fairly easy to fix the remaining warnings as well.
Let me know if I should do it in this PR, or if I should open a new one.
Thanks!

I think we can fix the remaining warnings
need to update docker/setup-buildx-action to v2 and docker/login-action to v2 (unsure if docker/login-action@v2 would solve it but I think it would)

@guihkx I added you as a member in bors so you can run bors try

need to update docker/setup-buildx-action to v2 and docker/login-action to v2 (unsure if docker/login-action@v2 would solve it but I think it would)

Yup, updating these two should get rid of most warnings.
There's also<EMAIL_ADDRESS>which is displaying warnings about NodeJS 12, but this issue in specific has been fixed in v2.2.1. Although a couple of set-output warnings still remain.
Nevertheless, I think it should be fairly harmless to just use @v2 instead of a fixed version.

@guihkx I added you as a member in bors so you can run bors try

Thank you. I'll take this opportunity to check if there are other actions that can be easily updated too.

bors try --target unknown-linux

Down to 7 warnings. Nice!

The first 2 warnings I'm not sure how to address right now. 🤔
The next 4 warnings are related to usage of set-output, and as I mentioned earlier, come from here, and once upstream addresses them, they'll go away naturally since we've switched to @v2.
And the very last warning seems harmless to me. It's just GitHub informing that the macos-latest runner will soon use macOS 12 instead of 11.

Only the set-output ones are warnings worth dealing with: we use macOS latest intending to use 13 when available, and there's no real reason to check if rustfmt is already installed since attempting to install it does so anyway.

Nice! In that case, the PR is ready on my side.

Ah, I see...
readarray trips when we pass an empty "here string" as argument. For example, this:
readarray -d ';' -t added_modified <<< ''
echo "array size: ${#added_modified[@]}"

Outputs:
array size: 1

My mistake. In this case, readarray isn't the right tool for the job.
This is easily fixable, though. I'll send a PR soon.


"Create missing override" quick-fix should add brackets if missing

Raised by @ktoosiu at from https://github.com/Dart-Code/Dart-Code/issues/1923.
This quick-fix appears even when the class doesn't have brackets, and then inserts code in a way that's not valid. While the original code wasn't valid either, it seems like it's harder to fix after the overrides were added, so it should probably inserts the brackets or not show the quick-fix unless the brackets are there.
Hi there, I realised that somethimes when I'm using snippets like automatic overrides creation It doesn't create brackets,

I wonder how to detect if the brackets are missing, since it seems they are being added, and are available as children of targetClass inside CreateMissingOverrides

You can ask the tokens whether they are synthetic (isSynthetic). A synthetic token is one that isn't in the source code but was added by the parser in order to recover from incomplete code. You'll need to ask each token independently because either one of them could have been in the source.

https://dart-review.googlesource.com/c/sdk/+/210961


request

If possible can u give kwik (animepahe.ru) server its fast and has high quality videos compared to other servers

With gogo having loading issues I might look into it.

With gogo having loading issues I might look into it.

Great


refactor(pg): store empty map as {} not null

Description
A detailed explanation of the changes in your PR.
Feel free to remove this section if it is overkill for your PR, and the title of your PR is sufficiently descriptive.
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
TODO(replace-me)
Use this space to explain how you tested your PR, or, if you didn't test it, why
you did not do so. Valid reasons include, for example, "CI is sufficient",
"No testable changes". Feel free to attach JSON snippets, curl commands,
screenshots.
In addition to reviewing your code, reviewers must also review your testing
instructions and make sure they are sufficient.

Current dependencies on/for this PR:

master

PR #6929   👈

PR #6915

PR #6916

This comment was auto-generated by Graphite.

What about all the preexisting entries in the DB using the old format?

What about all the pre existing entries in the DB using the old format?

I think they are fine. Queries will be the same a before and will work, when upsert will happen we will replace them with {}. I thought about using v4 approach and store 'null' but this doesn't make much sense.

If we change all the values to {}, will pgx v4 still work the same way? We need to ensure any changes are completely backwards compatible

That's tricky. If we want be 100% backward compatible then we should store 'null'.
The only incompatibility I could think of is a query that checks exact value or if value is a string and not map. I think our code does not allow such queries but I'm not an expert in this area. @md2119 do we expose any other queries than tested for maps?

That's tricky. If we want be 100% backward compatible then we should store 'null'.
The only incompatibility I could think of is a query that checks exact value or if value is a string and not map. I think our code does not allow such queries but I'm not an expert in this area. @md2119 do we expose any other queries than tested for maps?

We pretty much have to be backwards compatible in the event of a rollback from 4.2 to 4.1.  Greatly increases the amount of testing required to verify that we can make this change.

I added test for this behaviour

https://github.com/stackrox/stackrox/pull/6937

/retest

/retest

/retest

@janisz merged this pull request with Graphite.


feat: port Analysis.Calculus.FDeriv.Mul

[x] depends on: #4239
[x] depends on: #4221

This PR/issue depends on:

leanprover-community/mathlib4#4239
leanprover-community/mathlib4#4221
By Dependent Issues (🤖). Happy coding!

This PR/issue depends on:

leanprover-community/mathlib4#4239
leanprover-community/mathlib4#4221
By Dependent Issues (🤖). Happy coding!

bors merge


encrypt backups before storing them to end location

migrated to the shield project itself: https://github.com/starkandwayne/shield/issues/256


The "--ip-address" can't afford a list of IPs

Describe the bug
When we want to add several IPs using "az storage account network-rule add" the parameter --ip-address" can't support more than one IPs.
Related command
az storage account network-rule add --ip-address ip1 ip2 ip3
Errors
unrecognized arguments:
Issue script & Debug output
cli.knack.cli: Command arguments: ['storage', 'account', 'network-rule', 'add', '--account-name', 'xxxxx', '--resource-group', 'xxxxx', '--ip-address', 'xxxxx', 'xxxxxx', '--debug']
cli.knack.cli: init debug log:
Enable color in terminal.
cli.knack.cli: Event: Cli.PreExecute []
cli.knack.cli: Event: CommandParser.OnGlobalArgumentsCreate [<function CLILogging.on_global_arguments at 0x7efd371bd1f0>, <function OutputProducer.on_global_arguments at 0x7efd370d7d30>, <function CLIQuery.on_global_arguments at 0x7efd37070310>]
cli.knack.cli: Event: CommandInvoker.OnPreCommandTableCreate []
cli.azure.cli.core: Modules found from index for 'storage': ['azure.cli.command_modules.storage', 'azext_storage_preview']
cli.azure.cli.core: Loading command modules:
cli.azure.cli.core: Name                  Load Time    Groups  Commands
cli.azure.cli.core: storage                   0.050        58       272
cli.azure.cli.core: Total (1)                 0.050        58       272
cli.azure.cli.core: These extensions are not installed and will be skipped: ['azext_next']
cli.azure.cli.core: Loading extensions:
cli.azure.cli.core: Name                  Load Time    Groups  Commands  Directory
cli.azure.cli.core: ai-examples               0.113         1         1  /usr/lib/python3.9/site-packages/azure-cli-extensions/ai-examples
cli.knack.cli: Event: CommandLoader.OnLoadCommandTable []
cli.azure.cli.core: storage-preview           0.010        14        36  /home/jeremie_rouelle/.azure/cliextensions/storage-preview
cli.azure.cli.core: Total (2)                 0.123        15        37
cli.azure.cli.core: Loaded 65 groups, 295 commands.
cli.azure.cli.core: Found a match in the command table.
cli.azure.cli.core: Raw command  : storage account network-rule add
cli.azure.cli.core: Command table: storage account network-rule add
cli.knack.cli: Event: CommandInvoker.OnPreCommandTableTruncate [<function AzCliLogging.init_command_file_logging at 0x7efd36514430>]
cli.azure.cli.core.azlogging: metadata file logging enabled - writing logs to '/home/jeremie_rouelle/.azure/commands/2023-09-19.12-53-34.storage_account_network-rule_add.1204.log'.
az_command_data_logger: command args: storage account network-rule add --account-name {} --resource-group {} --ip-address {} {} --debug
cli.knack.cli: Event: CommandInvoker.OnPreArgumentLoad [<function register_global_subscription_argument..add_subscription_parameter at 0x7efd364bf040>]
cli.knack.cli: Event: CommandLoader.OnLoadArguments []
cli.knack.cli: Event: CommandInvoker.OnPostArgumentLoad []
cli.knack.cli: Event: CommandInvoker.OnPostCommandTableCreate [<function register_ids_argument..add_ids_arguments at 0x7efd364f50d0>, <function register_cache_arguments..add_cache_arguments at 0x7efd3647fee0>]
cli.knack.cli: Event: CommandInvoker.OnCommandTableLoaded []
cli.knack.cli: Event: CommandInvoker.OnPreParseArgs []
urllib3.connectionpool: Starting new HTTPS connection (1): app.aladdin.microsoft.com:443
urllib3.connectionpool: https://app.aladdin.microsoft.com:443 "GET /api/v1.0/suggestions?query=%7B%22command%22%3A+%22storage+account+network-rule+add%22%2C+%22parameters%22%3A+%22%22%7D&clientType=AzureCli&context=%7B%22versionNumber%22%3A+%222.52.0%22%2C+%22errorType%22%3A+%22UnrecognizedArguments%22%2C+%22correlationId%22%3A+%224a523397-7292-47c1-b200-0186e2ebdacd%22%2C+%22subscriptionId%22%3A+%228e152e9e-e3b9-4b44-a286-3893ae868626%22%2C+%22eventId%22%3A+%2224dfc215-693f-4a77-8b1d-056732e6e10d%22%7D HTTP/1.1" 200 None
cli.azure.cli.core.azclierror: NoneType: None
cli.azure.cli.core.azclierror: unrecognized arguments:
az_command_data_logger: unrecognized arguments:
Examples from AI knowledge base:
az storage account network-rule add --resource-group myRg --account-name mystorageaccount --subnet $subnetId
Create a rule to allow access for a subnet in another resource group.
az storage account network-rule add --resource-group myRg --account-name mystorageaccount --vnet-name myvnet --subnet mysubnet
Create a rule to allow access for a subnet.
https://docs.microsoft.com/en-US/cli/azure/storage/account/network-rule#az_storage_account_network_rule_add
Read more about the command in reference docs
cli.knack.cli: Event: Cli.PostExecute [<function AzCliLogging.deinit_cmd_metadata_logging at 0x7efd36514670>]
az_command_data_logger: exit code: 2
cli.main: Command ran in 0.434 seconds (init: 0.123, invoke: 0.310)
telemetry.main: Begin splitting cli events and extra events, total events: 1
telemetry.client: Accumulated 0 events. Flush the clients.
telemetry.main: Finish splitting cli events and extra events, cli events: 1
telemetry.save: Save telemetry record of length 3816 in cache
telemetry.main: Begin creating telemetry upload process.
telemetry.process: Creating upload process: "/usr/bin/python3.9 /usr/lib/az/lib/python3.9/site-packages/azure/cli/telemetry/init.py /home/jeremie_rouelle/.azure"
telemetry.process: Return from creating process
telemetry.main: Finish creating telemetry upload process.
Expected behavior
I would like to add more than 1 IP by command executed
Environment Summary
{
"azure-cli": "2.52.0",
"azure-cli-core": "2.52.0",
"azure-cli-telemetry": "1.1.0",
"extensions": {
"ai-examples": "0.2.5",
"databricks": "0.10.2",
"k8s-extension": "1.4.2",
"logic": "0.1.4",
"ml": "2.19.1",
"resource-graph": "2.1.0",
"ssh": "2.0.1",
"storage-preview": "0.7.0"
}
}
Additional context
No response

Thank you for opening this issue, we will look into it.

What format of ip are you trying to add? Multiple ips should be accepted.

Another thing that might affect this is the extension version, old extension version for storage-preview could be affecting this command. I see you have 0.7.0 installed, the latest should be 1.0.0b1, can you run az extension add -n storage-preview --upgrade to try it with the latest version.

Hi @calvinhzy
Thanks for your answer, indeed, upgrading storage-preview extension fixed it !
(I use IPV4 adresses as well)
Thank you!


Jobs with orchestrator not picking up custom workflow commands

Example: https://github.com/motatoes/test-digger-workflow-run-steps/actions/runs/7977161282
expecting to see a "I WAS PLANNED" workflow as per the custom workflow but instead not seeing any messages
Meanwhile if I use normal workflow with action events I can see that the custom workflow is picked: https://github.com/motatoes/test-digger-workflow-run-steps/actions/runs/7977445612/job/21780338972

@chvima yes should be! Released in the most recent version so you can test it out :) if you confirm I will close this issue

workflows:
lambda:
apply:
steps:
- init
- plan # Plan is not working so we are using below
- run: terraform plan
- apply
With this custom workflow we were able to run the plan before apply.
tested this in digger version 0.4.13.. works fine. thanks @motatoes

In that case I'm closing the issue 💯


Sys Tray Icon and Notifications

Particularly with i3 WM in Linux.

can you explain better?

You really need a tray. pic
Implement this function, please.
My OS: ArchLinux and WM: AwesomeWM.

^^ A large appeal of desktop apps for me is the convenient notification functionality in my WM on Linux based OS.

yes, very much needed notification


some CSS work on new datagrid

The branch ildipo/datagrid contains a new implementation of our table display.
This has several menus to control how data are shown etc.
Jake, please go through all the CSS and templates and make them 'beaker' like.
Also we would like to see if we can have a single menu with submenus - maybe adding an icon top right of the table.
To test the data grid you can open the R example.

Work on the branch but don't do a PR yet please


Properly listen for whisper worker errors

Just correcting a minor typo. Love the site!

Thanks for catching that!


Dialogflow CX supports old (GAPIC) client instead of new (V2) client surface

We should make sure the libraries are generated for the new V2 Surface only
See https://github.com/googleapis/google-cloud-php/pull/6806

Removed previous v1-surface clients as well


Make Marketing Text Legible above the image on the home page

Could be create a new image, could be taking out the image completely.
May include mock ups and a few iterations.

Reworking the home page. I've made the navbar consistent with the other portions of the site and have started to "rough in" the basic blocks a piece at a time. Flash messages and announcements are next then I'll work on the color scheme a bit to make the content less blue.

@olendorf I've just blocked in some sections, updated spacing, and added a pinch of color. Thoughts so far?

@mtribone  This is looking pretty good. Couple questions/thoughts.

What does the Explore Collections tab do?
Does the yellow seem a bit incongruous to you? I'm feeling maybe a lighter green or blue would be more in keeping with the theme.
The search box seems really lost to me. Would it be possible to make it more Googley and make it big and prominent, maybe just below where the new feature block goes?

@olendorf

The explore collections tab lists the administrative collections created by administrators.
The yellow is definitely noticeable! :-) I can try out a different color and see if it recedes too much visually
I certainly can move it to the middle and under the announcement block. I moved it up to the bar to keep it consistent with the rest of the site. However, if we're trying to promote discovery a bit more how about in a row right under the marketing block?

Trying out a green...

And the search in the middle...

@olendorf I had to go one step darker for both the share button background and the new feature background. Yes/No? Otherwise I would need to make the white text larger with the previous colors to hit sufficient contrast.

I'm starting to question the WAVE tool's contrast evaluator. Black over dark blue shouldn't pass!

I worked it out with bigger text


SLF4J: Class path contains multiple SLF4J bindings.

I see the page,this write
`libraryDependencies += "com.typesafe.scala-logging" % "scala-logging_2.11" % "3.1.0"
libraryDependencies += "ch.qos.logback" % "logback-classic" % "1.1.2"
but I getSLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/Users/wangxiaoke/.ivy2/cache/org.slf4j/slf4j-log4j12/jars/slf4j-log4j12-1.7.16.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/Users/wangxiaoke/.ivy2/cache/ch.qos.logback/logback-classic/jars/logback-classic-1.1.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
if I writelibraryDependencies += "com.typesafe.scala-logging" % "scala-logging_2.11" % "3.1.0"
`
I will ok! so I think the author is wrong at README?

Nowhere is slf4j-log4j12 mentioned in the README.


Perl logo is badly cropped

I don't know if this technically counts as a bug, but it irks me.
The Perl logo (representing which languages a kata is available in) is badly cropped.

Notice the missing left side of the circle is missing.
That is all, have a nice day.

For me (Zoom : 200 %, Browser : Firefox 89, OS : Linux mint)

Which seems to me to be of good shape.

So another user with Chrome has reported no issue. I guess it is something on my end, perhaps a buggy extension. Apologies for the false alarm.


Add doc for ssl

[ ] Breaking change? (if so, please describe the impact and migration path for existing application instances)

What changes did you make? (Give an overview)
Is there anything you'd like reviewers to focus on?
How Has This Been Tested? (put an "x" (case-sensitive!) next to an item)

[x] No need to
[x] Manually (please, describe, if necessary)
[x] Unit checks
[x] Integration checks
[x] Covered by existing automation

Checklist (put an "x" (case-sensitive!) next to all the items, otherwise the build will fail)

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation (e.g. ENVIRONMENT VARIABLES)
[x] My changes generate no new warnings (e.g. Sonar is happy)
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged

Check out Contributing and Code of Conduct
A picture of a cute animal (not mandatory but encouraged)

Done: https://docs.kafka-ui.provectus.io/configuration/helm-charts/configuration/ssl-example


gnmi-1.4: enable backplane-facing-capacity unsup. deviation for Nokia

This PR enables backplane-facing-capacity-unsupported deviation for Nokia and removes vendor-specific chip naming restriction from the test code that was used together with the deviation

This code is a Contribution to the OpenConfig Feature Profiles project ("Work") made under the Google Software Grant and Corporate Contributor License Agreement ("CLA") and governed by the Apache License 2.0. No other rights or licenses in or to any of Nokia’s intellectual property are granted for any other purpose. This code is provided on an "as is" basis without any warranties of any kind.

Pull Request Functional Test Report for #1859 / bcb31cd7adfbd6043ea6900241bbfb9b27977ab9
Virtual Devices

Device
Test
Test Documentation
Job
Raw Log

Arista cEOS

gNMI-1.4: Telemetry: Inventory

Cisco 8000E

gNMI-1.4: Telemetry: Inventory

Cisco XRd

gNMI-1.4: Telemetry: Inventory

Juniper cPTX

gNMI-1.4: Telemetry: Inventory

Nokia SR Linux

gNMI-1.4: Telemetry: Inventory

Openconfig Lemming

gNMI-1.4: Telemetry: Inventory

Help

Opened internal b/291118285 to verify this PR

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 47.486%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1341

Relevant Lines:
2824

💛  - Coveralls


Correct PrintOK doctest examples

As per the branch name, it's a super-important fix.
🚀

Whoops, gotta rebase to comply with the "controversial commits" convention.

:joy:
At first I didn't recognize the profile picture, and didn't see the username, so I was like "who is this clown" :clown_face: :joy:
Also, you killed me with "controversial commits" :skull: :joy:
Glad you didn't have to work more for TAOS!
Best PR here. Keep up the good work.


Missing HTTPS Redirection

Describe the bug
Currently we are not redirecting http traffic (port 80) to be https instead (port 443).
This is because of a missing configuration in our Elastic Beanstalk deployment.
The API can already be reached over SSL via https://api.nowcasting.io (or api-dev respectively).
Additionally, however, we should be upgrading http connections as well.
To Reproduce
Steps to reproduce the behaviour:

Go to '...'
See Not Secure in browser navigation bar

Expected Behaviour
All connections to http://nowcasting-api... get redirected to https://nowcasting-api...
Additional Context
This can be resolved by following this AWS Guide.

thanks @flowirtz for putting this together

This is no longer an issue


[CPP] Add missing metadata on Arrow schemas returned by Flight SQL #11999

This add an auxiliary class FlightSqlColumnMetadata meant to read and write known metadata for Arrow schema fields, such as CATALOG_NAME, SCHEMA_NAME, TABLE_NAME, PRECISION, SCALE, IS_AUTO_INCREMENT, IS_CASE_SENSITIVE, IS_READ_ONLY and IS_SEARCHABLE.

Closed this pull request because both implementation JAVA and C++ are now in the same Pull Request
https://github.com/apache/arrow/pull/11999


Convert to Terrapin gem because Cocaine is obsolete.

duplicate of https://github.com/jonbuda/miro/pull/37


End-to-end IDL tests for all the language pairs in separate repository

https://github.com/kaishh/izumi-petstore


external: download Parity-hosted binaries

Consider using those version lists:
https://vanity-service.parity.io/parity-binaries
http://releases.parity.io

@PhilippLgh can any of those feeds be used with the App Updater?
it seems there are some variables to tweak to get more specific results: https://vanity-service.parity.io/parity-binaries?version=v2.5.1


如何更新Lvgl的版本？ (IDFGH-9288)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
使用idfv5.0里面的例程，但是例程使用的是Lvgl v8.2的版本，Lvgl组件还有版本保护的，我应该如何更新到v8.3的版本呢？

https://github.com/espressif/esp-idf/blob/master/examples/peripherals/lcd/spi_lcd_touch/main/idf_component.yml#L3


Avoid a duplicate declaration of openldap-clients package

This happens on RedHat osfamily when a server is also configured as a
client.

@chutzimir I'd prefer include openldap::client::utils in openldap::client::install if osfamily == RedHat

Oh, I pushed a different version before seeing this comment... let me rework it.

@chutzimir please fix unit tests

The unit files are actually catching an interface change. Having include openldap::client::utils in openldap::client::install prevents overriding the default $::openldap::client::package on RedHat systems.
openldap::server::install never had the ability to override the utils package as it was already doing an include. Updating the new include in openldap::client::install to a class which passes in package allows all unit tests to pass.

Fixed in #123


Questions related to HEALPix support

Hello,
I have been working on interfacing s2fft with https://github.com/CMBSciPol/jax-healpy (currently only the transform for spin 0 is included, I am working on the interface towards spin=-2 and 2 and the adaptation of other healpy routines). Our goal is to have jittable and differentiable JAX adaptations of the healpy routines.
For this interface, I had some questions related to the methods jax and jax_healpy.
First, is I am not sure if the best practice would be to use only the jax method for both CPU and GPU, or if on CPU it would be better to switch to jax_healpy (for instance using jax.lax.platform)
Following this point, the forward function with the jax_healpy method is currently not jitable as the healpy_forward expects a jnp.array, but it transforms it right away into a np.array which is not tracable, here: https://github.com/astro-informatics/s2fft/blob/5d1d13fc47f4a4f8ed1ca0cf952819ff21ac141a/s2fft/transforms/c_backend_spherical.py#L331
Would it be possible to have it jittable? This can probably be solved with a pure_callback to make it jittable, and on which you have already the custom_jvp in place to make it auto-differentiable, but I am not sure if it is the best way to proceed.
Otherwise, I guess the only way to proceed is to use the jax method instead?
I also saw that you were using jnp.repeat here: https://github.com/astro-informatics/s2fft/blob/5d1d13fc47f4a4f8ed1ca0cf952819ff21ac141a/s2fft/transforms/spherical.py#L733 in the forward_jax. On my side, I found jnp.broadcast_to to be in general more performant for the same use. In the specific line I highlighted, you may be able to replace this line with indices = jnp.broadcast_to(jnp.arange(L), (2 * L - 1, L,)).T to obtain the same result with a gain of a factor 2 in average (for L = 255 in my benchmark) for this specific execution.
Again, thanks a lot for all of your hard work!

Hi @Magwos, apologies for our slow reply!

For this interface, I had some questions related to the methods jax and jax_healpy. First, is I am not sure if the best practice would be to use only the jax method for both CPU and GPU, or if on CPU it would be better to switch to jax_healpy (for instance using jax.lax.platform)

At the moment the healpy wrapper implementation corresponding to method = "jax_healpy" is significantly faster than the alternative pure JAX implementation corresponding to method = "jax" when running on CPU for larger bandlimits L, so on CPU I would say that is probably the best bet in terms of performance for now. Some illustrative benchmark results comparing s2fft.forward and s2fft.inverse for method = "jax" and method = "jax_healpy" for various L when running on a CPU:
forward
An NVIDIA GPU may be present on this machine, but a CUDA-enabled jaxlib is not installed. Falling back to cpu.
(method: jax, L: 64, L_lower: 0, sampling: healpix, spin: 0, reality: True, spmd: False):
    min(time):  0.0095s, max(time):   0.011s
(method: jax, L: 128, L_lower: 0, sampling: healpix, spin: 0, reality: True, spmd: False):
    min(time):   0.081s, max(time):   0.084s
(method: jax, L: 256, L_lower: 0, sampling: healpix, spin: 0, reality: True, spmd: False):
    min(time):    0.77s, max(time):    0.78s
(method: jax_healpy, L: 64, L_lower: 0, sampling: healpix, spin: 0, reality: True, spmd: False):
    min(time):  0.0040s, max(time):  0.0044s
(method: jax_healpy, L: 128, L_lower: 0, sampling: healpix, spin: 0, reality: True, spmd: False):
    min(time):   0.015s, max(time):   0.035s
(method: jax_healpy, L: 256, L_lower: 0, sampling: healpix, spin: 0, reality: True, spmd: False):
    min(time):   0.041s, max(time):   0.050s
inverse
(method: jax, L: 64, L_lower: 0, sampling: healpix, spin: 0, reality: True, spmd: False):
    min(time):   0.012s, max(time):   0.014s
(method: jax, L: 128, L_lower: 0, sampling: healpix, spin: 0, reality: True, spmd: False):
    min(time):   0.092s, max(time):   0.096s
(method: jax, L: 256, L_lower: 0, sampling: healpix, spin: 0, reality: True, spmd: False):
    min(time):    0.84s, max(time):    0.90s
(method: jax_healpy, L: 64, L_lower: 0, sampling: healpix, spin: 0, reality: True, spmd: False):
    min(time): 0.00037s, max(time): 0.00045s
(method: jax_healpy, L: 128, L_lower: 0, sampling: healpix, spin: 0, reality: True, spmd: False):
    min(time): 0.00080s, max(time): 0.00086s
(method: jax_healpy, L: 256, L_lower: 0, sampling: healpix, spin: 0, reality: True, spmd: False):
    min(time):  0.0031s, max(time):  0.0032s

As of #244 being merged, the healpy wrapper also supports forward- and higher-order automatic differentiation.

Following this point, the forward function with the jax_healpy method is currently not jitable as the healpy_forward expects a jnp.array, but it transforms it right away into a np.array which is not tracable, here:
https://github.com/astro-informatics/s2fft/blob/5d1d13fc47f4a4f8ed1ca0cf952819ff21ac141a/s2fft/transforms/c_backend_spherical.py#L331
Would it be possible to have it jittable? This can probably be solved with a pure_callback to make it jittable, and on which you have already the custom_jvp in place to make it auto-differentiable, but I am not sure if it is the best way to proceed.
Otherwise, I guess the only way to proceed is to use the jax method instead?

We updated the implementation of the healpy wrappers in #244 after I think you first wrote the above. We now define custom JAX (linear) primitives healpy_map2alm and healpy_alm2map in s2fft.transforms.c_backend_spherical which wrap the corresponding healpy.map2alm and healpy.alm2map functions, and define custom transposition rules to support both forward and reverse mode automatic differentiation. Currently we do not define lowerings however for these primitives so they are still not compatible with jax.jit. Unfortunately now that we are defining these as custom primitives it is also not possible to use jax.pure_callback to make them JITable as even if we  use jax.pure_callback in their implementations in
https://github.com/astro-informatics/s2fft/blob/8f6e4d5a8e4601ae99df01694d9e08600cef2549/s2fft/transforms/c_backend_spherical.py#L300-L301
https://github.com/astro-informatics/s2fft/blob/8f6e4d5a8e4601ae99df01694d9e08600cef2549/s2fft/transforms/c_backend_spherical.py#L347-L348
when JIT transformed JAX bypasses these implementation rules and instead looks for lowering rules for the current platform resulting in something like
 NotImplementedError: MLIR translation rule for primitive 'healpy_alm2map' not found for platform cpu

One option I think would be to define a lowering rule for the CPU which uses the compiled C++ functions healpy is wrapping. Alternatively if jax-ml/jax#24726 or something like it is merged, we may be able to use jax.pure_callback and still define custom derivative behaviour for both forward and reverse mode without using the internal primitive API.

I also saw that you were using jnp.repeat here:
https://github.com/astro-informatics/s2fft/blob/5d1d13fc47f4a4f8ed1ca0cf952819ff21ac141a/s2fft/transforms/spherical.py#L733
in the forward_jax. On my side, I found jnp.broadcast_to to be in general more performant for the same use. In the specific line I highlighted, you may be able to replace this line with indices = jnp.broadcast_to(jnp.arange(L), (2 * L - 1, L,)).T to obtain the same result with a gain of a factor 2 in average (for L = 255 in my benchmark) for this specific execution.

Thanks for the heads up, we'll have a look at using this alternative!


Add biggest german cities

Cities where taken from Wikipedia - Liste der Groß- und Mittelstädte in Deutschland
Cities sorted alphabetical
Each line splitted by capital letter

Great!


Multi-presenter display needs a comma or something

See e.g. /session/29. I may have broken this in the presenter-api work.

Fixed in a32c8711c42d27a3208c6962e7cbbf7906c0eb60