Use the same property name for the FeedInfo object for all WZDx feeds

This PR replaces #268 and resolves #222 by "renaming" the road_event_feed_info property on the WZDxFeed object to feed_info for consistency with the SwzDeviceFeed and RoadRestrictionFeed, specifically:

Deprecate the road_event_feed_info property on the WZDxFeed object.
Add a feed_info property to the WZDxFeed with the same type as description as the deprecated road_event_feed_info to replace it.
Conditionally require either the road_event_feed_info or feed_info on the WZDxFeed.

In the next major release, road_event_feed_info will be removed and feed_info will be required.

Can we make a hyperlink for the creative commons public domain url so that the FeedInfo object table looks smooth?


transport_socket: permissive transport socket for opportunistic encryption

Description: add permissive transport socket for opportunistic encryption
Risk Level: Low
Testing: unit test, manual testing
Docs Changes: N/A
Release Notes: https://github.com/envoyproxy/envoy/compare/master...crazyxy:oe?expand=1#diff-d8d3e33358b55e6c0466dd1bb5f40c79
Fixes #Issue: https://github.com/envoyproxy/envoy/issues/7135

The implementation was split into two separate prs. I am going to send the second one after this is merged.

At a high level, I'm curious if @envoyproxy/maintainers think this is a generally useful extension or if it will only be used by Istio. Any thoughts? If the latter it could just live with Istio for now. Will assign over to @lizan to drive resolution of that at a high level before review.

At a high level, I'm curious if @envoyproxy/maintainers think this is a generally useful extension or if it will only be used by Istio. Any thoughts? If the latter it could just live with Istio for now. Will assign over to @lizan to drive resolution of that at a high level before review.

@mattklein123 fwiw, we would probably use it... cc: @fishcakez

OK as long as at least someone else wants to use it, SGTM. Let's proceed!

@crazyxy is the second one is support Reconnect in ConnectionImpl? I'd like to see that altogether with this PR, can you open a draft PR for that? I don't think it conflicts much with this one?
@PiotrSikora can you take a look on this too?

@lizan This is the second pr https://github.com/envoyproxy/envoy/pull/7310

I think this needs a master merge and codeowners, yes?

@alyssawilk I added owner of extensions/transport_sockets/permissive in CODEOWNERS. Not sure why format still fails.

Two owners required (and one should be a maintainer) - sorry if the error message doesn't make it clear what's wrong!

@mattklein123 fwiw, we would probably use it... cc: @fishcakez

I don't think we would use this @rgs1 . For previous TLS migrations we have either used a new discovery/port to ensure old/non-TLS clients can not come back after a migration is supposedly complete and send application data in their initial payload. The exception to this has been for protocols that perform a layer 7 handshake before sending application data. In those cases we have sometimes performed the opportunistic feature on the server side, whereby we detect if the client is attempting to perform a TLS handshake by peeking.
The server side approach has the advantage of not performing 2 attempts on the client side during the migration when one peer has not begun the migration. Also some protocols do not work well with opportunistic client side. For example, framed thrift requests use the first 4 bytes as big endian unsigned integer determining the length of the frame. The TLS client hello protocol for TLS v1.2 is likely to start 0x16 0x03 0x03 0x00 which would be interpreted as a length of 369296128. The non-TLS server would then wait to receive the 369MB request. Assuming the server hasn't set a (sane) max frame size, which not all implementations do, the request will time out as the server won't receive the bytes it expects. This could occur on either side. Therefore even security/privacy concerns aside it is not a protocol agnostic solution to do opportunistic client side TLS.
We would likely use a filter chain matcher that chooses a filter chain based on peeking at bytes for tls v non-tls - or equivalent feature in the listener side for future migrations

For the record, we (Istio) are abandoning work on this feature due to the security issues raised in #7135.
@crazyxy feel free to close this PR.


Periodically retry getting initial networks

In a cluster the master flannel or etcd might not be up yet when
flanneld starts, so periodically retry getting initial networks
instead of failing hard.

I'm confused why it's failing hard. There's a big for loop inside Network.Run: https://github.com/coreos/flannel/blob/master/network/network.go#L98

I'm confused why it's failing hard. There's a big for loop inside Network.Run: https://github.com/coreos/flannel/blob/master/network/network.go#L98

It was failing long before the Network.Run(), because with multinetwork mode, to even get a Network object, you have to ask etcd/flannel-remote for the list of networks.

It was failing long before the Network.Run(), because with multinetwork mode, to even get a Network object, you have to ask etcd/flannel-remote for the list of networks.

Makes sense though the retry loop is best placed around the operation of get the list of networks (https://github.com/dcbw/flannel/blob/6b38ffa5f879e3711f0b129f5edc9c198acc11b2/network/manager.go#L315) for more clarity.

@eyakubovich @jonboulle PTAL

@eyakubovich does that look like what you meant now?

LGTM

Thanks!


Fix misprint

Hey @frederikhors and thanks for the contribution 🙏🏻
The WithWhereFilters option is actually deprecated. Use the latest master of ent/contrib for now and we’ll release a new version soon.
https://github.com/ent/contrib/blob/master/entgql/extension.go#L124


Workflow cleanups

Switch to using pubspec_overrides.yaml files instead of manually parsing and writing pubspec files. This makes local development easier while still testing the published version in CI. Implementing https://github.com/dart-lang/pub/issues/4076 would simplify this even further.
Use health.yaml workflow for PR health checks. Waiting for https://github.com/dart-lang/ecosystem/pull/206 to land.

[x] I’ve reviewed the contributor guide and applied the relevant portions to this PR.

Contribution guidelines:

See our contributor guide for general expectations for PRs.
Larger or significant changes should be discussed in an issue before creating a PR.
Contributions to our repos should follow the Dart style guide and use dart format.
Most changes should add an entry to the changelog and may need to rev the pubspec package version.
Changes to packages require corresponding tests.

Note that many Dart repos have a weekly cadence for reviewing PRs - please allow for some latency before initial review feedback.

The CI was green as the overrides were not copied, so the packages were resolved via pub. Now the overrides are copied and point to the right package folders.

The PR description is out of date.
Please expand the description a bit with https://github.com/dart-lang/native/pull/846#discussion_r1415688162 so we can understand our own changes in 3 years. 😄


clusterpool: ensure clusterdeployments namespace has same rbac as cluster-pool-admin

xref: https://issues.redhat.com/browse/CO-1282
Any role bindings in the namespace of the clusterpool that refer the ClusterRole hive-cluster-pool-admin
will be used to provide the subjects the same permission in the namespaces created for various
clusterdeployments for the clusterpool.
The controller performs these additional actions for each reconcile,

lists all the rolebindings in clusterpool's namespace that refer the ClusterRole hive-cluster-pool-admin
to collect all the subjects.
This makes sure that no work needs to be done when there are such rolebindings. And since k8s ensures that a rolebinding
cannot be created when the ref doesn't exist, this will ensure that only when the ClusterRole exists would the controller
run the next steps.
lists all the namespaces attached to the clusterpool by using the constants.ClusterPoolNameLabel label selector.
creates/updates a rolebinding hive-cluster-pool-admin-binding in each namespace binding to the same ClusterRole.

The controller also adds new watchers,

changes to rolebindings in the clusterdeployment namespace
changes to any rolebindings with ref to ClusterRole hive-cluster-pool-admin triggers resync for all clusterpools
in that namespace.

NOTE: the controller can only pass on the permissions that it has i.e. the current hive-cluster-pool-admin cluster role is a subset of the hive-controller's permission. If the controller permissions are less that what the hive-cluster-pool-admin cluster role, then when creating a rolebinding in the clusterdeployment namespace we see an error like
time="2020-11-30T21:21:11.129Z" level=error msg="could not create rolebinding" clusterPool=default/adahiya-pool-1 controller=clusterpool error="rolebindings.rbac.authorization.k8s.io \"hive-cluster-pool-admin-binding\" is forbidden: user \"system:serviceaccount:hive:hive-controllers\" (groups=[\"system:serviceaccounts\" \"system:serviceaccounts:hive\" \"system:authenticated\"]) is attempting to grant RBAC permissions not currently held:\n{APIGroups:[\"\"], Resources:[\"pods/log\"], Verbs:[\"get\" \"list\" \"watch\"]}\n{APIGroups:[\"apiextensions.k8s.io\"], Resources:[\"customresourcedefinitions\"], Verbs:[\"get\" \"list\" \"watch\"]}" reconcileID=gn7pt9sd rolebinding=adahiya-pool-1-kpkbg/hive-cluster-pool-admin-binding

/lgtm

/retest

/retest


Use Distillery

Now that Distillery is in beta, could we use this instead of exrm?

Great suggestion, I'll check this within the next days.

As noted above I tried to experiment with the process. The configs are a bit different for distillery ( they must be present in a ~/rel/ folder). I also had to alter a couple of other steps in the process (images and scripts. I had to modify the docker-edib-tool image).
The experiment is still on its way.
I'll try to throw a couple of hours on this but not sure I'll be able to anytime soon :(

@JeremyBellows Thanks for your efforts.
For all and everybody interested in this change:
Sorry, I was (and still am) pretty busy these days.
Next week I'm at the EUC2016 conf and afterwards I hope to have more focus and energy for the required changes in the EDIB toolchain.

I think I got it working. Unfortunately my build process is broken due to the tar limitation on file name length. Been trying to figure out where it is coming from (probably a dependency).
I'll work on pushing the prototype up. It just needs to be tested

Here's what I have so far
Docker edib tool - https://github.com/JeremyBellows/docker-edib-tool/tree/15-UpgradeToDistillery
mix-Edib - https://github.com/JeremyBellows/mix-edib/tree/15-UseDistillery
I ran into an issue with erts versions and opened #18

Rebuilding the Docker image chain using those two forks worked for me with two additional changes:

Changed the version of Erlang to 19: https://github.com/edib-tool/docker-base-erlang
The check-distillery script on @JeremyBellows' fork didn't work for me even though I had distillery installed, so I just commented it out and everything seemed to work fine (https://github.com/JeremyBellows/docker-edib-tool/blob/15-UpgradeToDistillery/edib/check-distillery.mk)

The base erlang image is also officially updated to 19.x now btw.

@JeremyBellows Can you rebase and rebuild your changes against the updated toolchain to see if it (still/finally) works?

It works! Tested successfully on my project.
I'll submit the pull requests shortly

Two live pull requests
https://github.com/edib-tool/mix-edib/pull/20
and
https://github.com/edib-tool/docker-edib-tool/pull/7
Let me know if there is anything else I need to do :)

Done. 🎉


Add JSON OAS, export it in NPM manifest and add use instructions

Hi @elainefigma,
This PR is a proposal to add a JSON version of the OAS file (which I understand you generate automatically outside this repo, so some extra work would be needed to either output that JSON file or add CI jobs that can generate it from the local YAML file).
More importantly, the PR changes how OAS files (both YAML and JSON) are exported in package.json so that import resolvers can reach them, and adds examples on how to consume the JSON OAS from both ESM and CJS contexts.
Please let me know if you'd like additional context on my proposal, or if you'd like me to instead open a PR with only the exports and README changes and without the added JSON OAS file (though, that would significantly complicate the use of the spec in Node apps).

Thanks for the suggestion, we're tracking this request internally. As you mentioned, this would require a tooling and process change for us, so we can't merge your PR directly. We'll keep it open and resolve if/when we can make this addition.

Hey, thanks for the heads up. I'm happy to split the PR in too if you'd like the NPM exports but want to stay on YAML :)

Hey @Sidnioulz, sorry for the delay here. I thought a bit about this PR, and I think the solution that might make the most sense is to include JSON (but not YAML) in the exports, and bind it to the ./openapi path. I haven't done it recently, but IIRC, importing JSON should automatically deserialize into a JS object without requiring someone to call JSON.parse explicitly? I think this is probably what people would want 99% of the time, and means we don't have to commit to shipping YAML in the NPM package.

Hi @jefflee-figma, happy to hear that!
I went with showcasing how to open the JSON file because some tooling still has issues with supporting import attributes for JSON. With the change in syntax, some build tools support the legacy syntax and others the new one. I had trouble with getting esbuild and TS to agree on a syntax in my case.
I think it'd be great to mention import attributes, but not as a standalone solution.
Would you like me to add such an example and realign the export subpath to './openapi' for the JSON file on the PR?

This is the error I get with Node 22 when trying to import the JSON file as JSON with the right attributes. It's also impossible to directly import without the type: "json" attribute, but require does work.
I've pushed a new commit adjusting the export subpath and adding another example to the README. Please let me know if there's anything more I can do!

I really appreciate all the work and attention to detail you put in here. One thing your README diff helped me to realize is that, given the complexity of importing a JSON file in various module settings, I think the long-term better fix is simply to provide a separate openapi.js file that exports a true JS object. This will require a change in tooling on our end, but I suspect it won't be that complicated...I'll see if I can get some help with that over the next few weeks.
There is a question of whether we should export that object with TypeScript types (internally, we use openapi-types). I'm somewhat hesitant to add another dependency just for that use case, but having those annotations would make them easier to work with.

Sounds like a great idea! It could still be useful to preserve a JSON export for CLI tools e.g. https://the-guild.dev/graphql/mesh/v1/source-handlers/openapi which supports only YAML and JSON. It can be useful to write a Node script that resolves the path to a JSON file and then to pass it on to a CLI that only knows how to consume JSON.
By the way, if Figma is interested in maintaining a proper OAS-derived TypeScript client, there are tools out there that do a reasonably good job of generating such code with API methods. When I started using this package, I quickly realised I didn't know what to do with the type information. Because my client code is generated from OAS, I can't go back into the client code and manually patch in types from your NPM package (else, how can I automatically sync it when you publish updates?).
My (WIP) client uses https://github.com/acacode/swagger-typescript-api to generate very similar types, but directly within the client object. I have a Dependabot-based workflow to regenerate the client based on updates to your package, and then I add Axios interceptors for cache services and (very much WIP 🤣) rate limit safeguarding.
 I'm happy to help if you're interested in building something with a bit more reach than just the API and its types.

Feel free to check https://github.com/Sidnioulz/figmarine/tree/TMP/packages/rest (not published yet, name may change, etc., etc.) if you want to see how the client looks like.

Another example that came up in favour of also having the OAS as JSON: the Prism CLI, which I intend to use to mock the API in my integration tests, also supports passing a path to a JSON file.

Hi @jefflee-figma, just letting you know this issue is no longer urgent to me as I've built a workaround.
To anyone finding this issue and wanting to build an automatic process around the OAS:

How I download and use the existing YAML OAS file
How I trigger automatic releases when this here package gets updated

Hi Steve, appreciate you giving us a heads up and being patient with us! We've still got this on our radar, just haven't been able to give it its due.
I'm going to close this PR now, but we're tracking internally.

No worries! I'd love a little heads up when/if you delete the YAML file now that I depend on it, and I'll make the necessary adjustments on my end :)

Yep, I can say pretty confidently that we're unlikely to delete the YAML file...I think that would be a breaking change at the level of changing the major version of the package.


Update react-modal to work with React v0.14 and fix deprectated warnings.

Fixes #67
It might be a good idea to wait until React v0.14.0 gets released or maybe we can merge it in react-0.14 branch
:smile:

@rogeliog Thank you for the PR! Let's wait until 0.14.0 is released. In the mean time #65 will at least let you use the RC.

@rogeliog Looks like React 0.14 support was already merged in as of version 0.6.0.  I'm going to go ahead and close this one out to clean things up.


Avoid using DenseElementsAttr::getRawData

fixes https://github.com/openxla/stablehlo/issues/83
The PR implements  the underlying data storage of the tensor using an mlir::HeapAsmResourceBlob object represents a mutable blob of data. This provides two improvements:

No need for using DenseElementsAttr::getRawData() which cannot be relied  to provide contiguous representation of underlying data in cases like boolean and splats.
An mlir::HeapAsmResourceBlob object, being mutable, simplifies how we store the underlying Tensor data.

Let us port the discussion on mutability of tensor from https://github.com/openxla/stablehlo/pull/101 to this PR.

We will be addressing the comments from @joker-eph via ticket. Planning to merge this as this will unblock writing tests with boolean types and splat.


Add deploy user's public key

In order to help us migrate Performance Platform MongoDB data across to the
GOV.UK MongoDB stack, we need access from Jenkins running in Performance
Platform.
This does that.
Rather than add this key in to roles.mongo.yaml, it seemed better to add it
here so that we keep everything together, and so that the hash doesn't get
blatted accidentally.

Is this intended to be the preview key only? Looks good if so but it might be worth making a comment to that effect or something.

@jcbashdown Yes, for the moment. We'll eventually need to do staging and production when we come to their data stores. I'll go add a comment.

Copying in @alexmuller and @timmow.


Layout Kanas, Kanjis and Hanguls correctly under non-DBCS code page, which is what BOW is using

Please use the following bug reporting template to help produce actionable and reproducible issues:

A brief description
The current console CP (65001) cannot layout any CJK full-width characters correctly.
Expected results
The wide characters are fit into two console cells, instead of one.
Actual results (with terminal output if applicable)
The wide characters are shrunk into one console cell and unlegiable.
Your Windows build number
14372 (slow ring)
Steps / commands required to reproduce the error

Open WSL.
Run any program produces CJK output.
Look at it.

See our contributing instructions for assistance.

Any progress?

Silly question: what are some "CJK full-width characters" that we could try out for debugging purposes?

@RyanGlScott like
安あ

@benhillis @miniksa @zadjii-msft
Any progress?

Thanks for the discussion.
Closing this issue since:

The changes necessary to support MUCH more of the UNICODE text-space is underway, but will take a while to complete. Bear with us while we implement the necessary changes
This is the WSL issues repo, but this is an issue in Console which has its own Console GitHub Repo
GitHub doesn't allow issues to be moved between repos, preserving posters' identity :(

If you have further asks/issues, please file new issues on our Console GitHub Repo.


Improve discoverability/usability of packaging an application

ti-slack discussion
Is your feature request related to a problem? Please describe.
We want to improve the discoverability/usability of packaging applications. Currently it is only available from the Command Palette or via the icon on a platform shown in the Builder explorer.
Describe the solution you'd like
There's a number of solutions we could provide here, most likely we will end up implementing more than one:

Add a top level Package button alongside the Run button in the title bar of the Build Explorer
Add a Package option to the three dots dropdown in the title bar of the Build Explorer
Add a new Package sub-item to each platform in the Build Explorer that will list the possible distribution targets

The main problem is, that the package button is hidden. Display it without mouseover and everything's fine 😄

@caspahouzer, yup and that's why we're looking to improve it 🙂  Thanks for the feedback!


Restrict access to the Storage Account used for Flow logs

I have received a question from my customer on how to restrict the access to the SA.
In this documentation it looks like there is no way to restrict access.
I have investigated internally, and I have found an old post where the PG says this:
"NSG flow logs supports uploading logs to a storage account where private endpoint is enabled (but Microsoft trusted services are allowed to access). Also, if the communication is happening from the subnet to the storage account it would get recorded by the platform as well in the NSG flow logs"
This means the public documentation is not update, please can you verify if this is the case to update the doc?
The customer needs to have official evidence of their decision especially on security concern.
Thanks
Ric
[Enter feedback here]

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

ID: c2690676-f133-5fdc-2a49-f8ef1fefbff0
Version Independent ID: 3de811d4-4f40-a7a7-9129-38674e365c6f
Content: Manage NSG Flow logs - Azure PowerShell - Azure Network Watcher
Content Source: articles/network-watcher/network-watcher-nsg-flow-logging-powershell.md
Service: network-watcher
GitHub Login: @damendo
Microsoft Alias: damendo

@ripom
Thanks for your feedback! We have assigned the issue to author who will provide further updates.

#reassign: @Harsha-CS

@Harsha-CS
Can you please review this GitHub issue?

Thank you for you dedication to our documentation.
Unfortunately, we have been unable to review this issue in a timely manner. We sincerely apologize for the delayed response. We will create an internal tracking work item to address this issue. For now, we are closing this issue. If you have any additional information you would like to provide, please respond to this issue with any additional details.
Please continue to provide feedback about the documentation. We appreciate your contributions to our community.
#please-close

#reassign:halkazwini


Fixed pop the wrong page when changing the speed and added support for multiple resolutions

1. Fixed pop the wrong page when changing the speed
Issue: https://github.com/fluttercommunity/chewie/issues/618
2. Added support for multiple resolutions
Issue: https://github.com/fluttercommunity/chewie/issues/852
Now, to be able to change the video resolution, you need to pass the following parameters to the ChewieController:

allowQualityChanging: true
Map

qualities: {
        '240p': '<your link to a 240p video>',
        '360p': '<your link to a 360p video>',
        '720p': <your link to a 720p video>',
        '1080p': '<your link to a 1080p video>',
      }

The key can be any string that you want to display in the list of resolutions in the player. The value should be link to the video of this resolution.
Also, in order to be able to change the video resolution, I need to redefine the videoPlayerController inside the ChiewieController. Therefore, the onVideoControllerChange callback has been added, which will allow you to get a new controller when it is replaced.
The quality change has been added for iOS and Android only.

@akmalova Thanks for your contribution.
I do have a major concern with changing the resolution. Since this is driven primarily by VideoPlayerController, shouldn't it be relegated to re-creating the ChewieContoller instead of internally mutating the VideoPlayerController? Just trying to wrap my head regarding this change, because the change that you're proposing represents a fundamental shift in the way ChewieController behaves.
@brianegan and/or @Ahmadre, I would like your thoughts on the above.
Also, for the fix that addresses #618, if you can please split that one up into a separate PR, that would be easier for me to review and eventually approve, assuming any concerns that I may raise are eventually addressed.
Thanks in advance.


[WIP] Adding Makefile and docker-compose.yml

Adding Makefile/docker-compose in from old docker branch.
Run make alone and it will give you all the valid commands. My dev stack has been the following
make run and make clean
@0xdade Which readme would you like the documentation to go?

Orchestration documentation goes in /README.md. Documentation for how to run component containers individually should go in the respective component natlas-agent/README.md and natlas-server/README.md readmes (in case you'd like to document that as well as part of this issue, which is currently missing).

Things that need to be fixed before this goes through:

Create dev readme.
Look at security capabilities.
Screenshots are broke
Allowed Elasticsearch_URL to be loaded from env.

Is this how you launch natlas in production or development?
I would generally recommend that docker compose be setup for development environments. In production we shouldn't be making people install make. What if we automatically mount the source folders and set the flask-env to development? There's a bunch more configuration that we should probably do for a prod deployment.

@ajacques We could use both for prod when the env vars are set correctly, yes. docker-compose is an orchestration tool. It can be used to scale any service that is defined within depending on what you have your backend set to (ECS, Internal Docker Swarm, Openstack, etc).
Until I get some things ironed out and decide how i feel about the security of this I would only recommend it for development, but you can still use the containers for production if they are fully functional.
Your rebuild of the containers def made it fast, but I have a few things to fix as stated in the previous comments.

I understand that Docker compose can be used as an orchestration, I'm more suggesting it's not a very good production one because there's a bunch more things that should be supported that Docker-compose doesn't.
For example, in development, you generally want FLASK_ENV=development + mount the local source directory, and certain settings, whereas in a production environment you want to increase Elasticsearch replicas, front it all behind a possible shared NGINX instance, SSL certifficates, etc.  All stuff that we shouldn't be in the business of, but things like Helm/k8s/AWS ECS do much better.
I'm fine with a docker-compose, but I would only recommend it for development deployments.
These differences basically make a single Docker-compose.yml for both prod and dev kind of useless.

I don't mean to nay say, but docker compose can do "almost" everything kube can as far as orchestration/scaling. It all depends on how the app its self is designed. The elastic container supports scaling just like the natlas-agent will. The only part that doesn't from what I can tell is the natlas-server because of the sqlite db.
Where I work we run both kubernetes and docker-composed infra. Its more of a matter of preference rather than technology. Once we have a solid docker-compose.yml, It will be quick to run "kompose" to convert it to the kube spec, or I can translate it to helm.
For TLS Management you can do
  acme.sh:
    container_name: acme.sh
    image: neilpang/acme.sh:latest
    command: >
      sh -c -- "
      mkdir -p /acme.sh/nginx/domain.com
      echo Issue Cert &&
      --issue -d domain.com -d '*.domain.com'  --dns dns_freedns ;
      echo Installing Cert &&
      --install-cert -d domain.com --key-file /acme.sh/nginx/domain.com/key.pem --fullchain-file /acme.sh/nginx/domain.com/fullchain.pem"
    entrypoint: ""
    environment:
      - FREEDNS_User=
      - FREEDNS_Password=
    volumes:
      - /storage/letsencrypt/:/acme.sh/
      - /etc/localtime:/etc/localtime:ro

For nginx I plan to do something like with the current nginx deployment conf:
 nginx:
    container_name: nginx
    image: pryorda/docker-waf
    restart: always
    ports:
      - "80:80"
      - "443:443"
    volumes:
      - /storage/letsencrypt:/var/lib/letsencrypt
      - /storage/nginx/dhparams.pem:/etc/ssl/private/dhparams.pem
      - /etc/localtime:/etc/localtime:ro
      - /storage/nginx/proxy.conf:/etc/nginx/conf.d/default.conf
    networks:
      front-end:
        aliases:
          - nginx
      back-end:
        aliases:
          - nginx

To be 100% honest though, we should just have a boiler plate configuration that will work for most people and then let them do what they will with documentation and containers we build.

You can do this, but this is not something that each application, like natlas, should have to do. It means natlas has to maintain and fix issues with that, which doesn't make sense, especially if we're trying to target a ease of deployment.
Let's fix the last remaining issue(s) on the PR, then can merge. We can figure out the best way to deploy as a follow up. I did create a natlas/helm repo and have the start of a helm template because I'm running natlas on k8s right now.

Alright so I actually downloaded this and tried it out, but I'm not sure I agree with the model of using the Makefile to build the image. Docker compose users will expect to be able to do docker-compose build or up and it should mostly work, but in this case it only works through the Makefile.
I'm actually using Docker for Windows which would require me to install make. Why are we building the images using the makefile instead of using the build: hard-earned/Dockerfile paradigm in the yml?

You can do this, but this is not something that each application, like natlas, should have to do. It means natlas has to maintain and fix issues with that, which doesn't make sense, especially if we're trying to target a ease of deployment.
Let's fix the last remaining issue(s) on the PR, then can merge. We can figure out the best way to deploy as a follow up. I did create a natlas/helm repo and have the start of a helm template because I'm running natlas on k8s right now.

Awesome. Helm is good stuff.

Alright so I actually downloaded this and tried it out, but I'm not sure I agree with the model of using the Makefile to build the image. Docker compose users will expect to be able to do docker-compose build or up and it should mostly work, but in this case it only works through the Makefile.

I'm actually using Docker for Windows which would require me to install make. Why are we building the images using the makefile instead of using the build: hard-earned/Dockerfile paradigm in the yml?

To answer the more specific question about build:, I go back and fourth here. If you do the tag right it can support pulling from dockerhub or using the local built images.
I really like the make file as it shortens the commands  and formalizes the process. make run vs docker-compose build && docker-compose up -d elastic ; sleep 10 ; docker-compose up -d
I'm hoping to finish this PR so we can get it merged.

I'm going to yield the decision for this to @ajacques as I am not very familiar with this space. My primary focuses are on the application itself and my only real opinions on orchestration and deployment is that the natlas project itself should not be married to any single orchestration or deployment methodology. So changes to the application specifically to support one form of deployment/orchestration that change the way other forms of deployment/orchestration work are generally frowned upon.

I'd like to see docker-compose build work. Right now, this doesn't work without make and it can work without it.

Wow 52 comments later and I think we are there. Let me know your thoughts! This has been a good experience and I look forward to helping with this project in the furture !

I apologize for the long PR, this project is still new and we're still figuring out developer guidelines and practices, but we'll get better at it.
Merged. Thanks for your contribution


feat(aws-smithy-runtime): introduce tls-rustls-webpki feature

Motivation and Context
This allows (eventually) for downstream crates to not depend on native CA bundle, but rather use https://docs.rs/webpki-roots/latest/webpki_roots/
This is especially important, because on platforms where native CA bundle is missing, currently-used hyper-rustls panics at runtime (latest release uses version prior to https://github.com/rustls/hyper-rustls/commit/77154daea8663b9fd5263e70119ad145a050895e)
Description

Provide a feature flag, which gives downstream developers a choice of the PKI bundle
Testing
cargo test in respective crates with the new features (and old)
Checklist

[x] I have updated CHANGELOG.next.toml if I made changes to the smithy-rs codegen or runtime crates
[x] I have updated CHANGELOG.next.toml if I made changes to the AWS SDK, generated SDK code, or SDK runtime crates

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

Hey, thank you for taking the time to make this contribution!
Unfortunately, this isn't the approach we want to take for this. The problem with doing this via features is that the behavior becomes ambiguous in the case where both features are enabled, and other libraries could subtly break your TLS configuration depending on what features they enable. This kind of thing really needs to be explicit.
Addressing this will require some design. You're welcome to write a RFC in the design/rfcs directory if you still want to contribute this.

because on platforms where native CA bundle is missing, currently-used hyper-rustls panics at runtime

This has been addressed as of release-2023-12-12, i.e. loading native CA bundle will be delayed and only happen if the default HTTP client is not overridden.


the video that the playing is shrinking when scroll the RecyclerView

When I scroll the RecyclerView, the video that the playing is shrinking, and as you can see in the figure below, the red part appears to the right of the page.
What if I want to disable this feature? What should I do?
Thank you for your help

There are two recycleview in demo, one is smallwindow the other is no smallwindow.


Node Sass 3.4.0

This PR updates to the stable<EMAIL_ADDRESS>It also updates the error messages to use LibSass pre-formatted errors. This means gulp-sass will now produce the exact same error messages as LibSass, node-sass, and grunt-sass.
Before
test/scss/error.scss
property "font" must be followed by a ':'

After
test/scss/error.scss
Error: property "font" must be followed by a ':'
        on line 2 of stdin
>>   font 'Comic Sans';
   --^

Could you npm publish a new version of gulp-sass containing these changes please?
I’m currently using git://github.com/dlmanning/gulp-sass.git#d7ca6a45e89ce878645c6c0582407452899bd7c7 as a dependency which feels kind of dirty.

@mathiasbynens we're tracking the next release in https://github.com/dlmanning/gulp-sass/pull/375
Unfortunately there are some issues with the latest LibSass we want to get sorted first.


Please invite me to the GitHub Community Organization

Please invite me to the GitHub Community Organisation.

Name:Bikale Aberra @bikale

Additional Context:

through Traversy youtube channel

I am joining to learn , to experience, and to contribute to the community that gave me so much
:nerd_face:

Invitation sent for the GitHub Organisation. Welcome to the community 🎉
Don't forget after accepting to make it public so it appears on your GitHub profile for everyone else to see, you can do this by finding your name in the GitHub organisation list and change the dropdown to public https://github.com/orgs/EddieJaoudeCommunity/people
Tips for practising:
Customise your GitHub profile, here is a live stream on it https://www.youtube.com/watch?v=cT6GXCuS0Zo
Practice repo, instructions on how to add your name to the README in the README https://github.com/EddieJaoudeCommunity/hacktoberfest-practice
Remember contributing to open source is not just about code, its about collaboration, communication and adding value
I hope that helps


Sonner toast below vaul

If the Vaul Drawer is open and a toast notification from Sonner, how do I get the toast over the drawer?

Increase its zindex.

@emilkowalski can you give me an example about that? I tried like in below, but its still not working.
@/pages/_app.tsx
import type { AppProps } from "next/app";
import "../styles/globals.css";
import { Suspense } from "react";
import NavBar from "@/components/layout/navbar";
import { Toaster } from "sonner";

export default function App({
  Component,
  pageProps: { ...pageProps
  },
}: AppProps) {
  return (
<>
        <header>
          <Suspense fallback="...">
            <NavBar />
          </Suspense>
        </header>
        <main className="mx-5 py-32">
          <Component {...pageProps} />
        </main>
        <Toaster
          richColors
          toastOptions={{
            style: {
              zIndex: 99,
            },
          }}
        />
</>
  );
}

@/components/form.tsx -> form is inner at vaul
  const handleSubmit = async (values: FormValues) => {
    try {
       // ...
    } catch (error: any) {
      toast.error(error.message);
    }
  };

You found any solution?

Try putting the Toaster inside a portal

@andreasasprou and when the toast has a button? Clicking on it closes the dialog and right click > Inspect focuses on the <html..


Tab View Enhancement

The Problem
Tabs are not visually related to the content beneath them, as shown in the screenshot below:

This inconsistency is observed across the system and on various pages.
Proposed Solution
A small enhancement that adds an underline will effortlessly address this issue and create a better visual connection between the tabs and their corresponding content.
as shown in the screenshot below:

Please feel free to share your thoughts so we can further improve the user experience. Thank you!

@mmoulian
I looked for using underline with an active bigger underline, and it's okay to use them together
as shown in the screenshot below:

According to Carbon Design System that we rely on as a guideline for dashboards, more details on the following link
https://carbondesignsystem.com/components/tabs/usage/

Thanks @alfaris; I like the idea of increasing the visual connection to the tab with its corresponding content. I think the line is a good idea, but maybe we need something else. I did this couple of options. What do you think?:

@jpellizzari please kindly review and advise on the priority: do we have time and resources to implement this?

@jpellizzari please kindly review and advise on the priority: do we have time and resources to implement this?

I cannot advise on priority, as this is a subjective aesthetic change that the design team is asking for, and they would have to determine the priority.
I can say that I think this is a pretty simple change from a feasibility perspective.
@mmoulian @alfaris Have you come to a consensus on which concept you would like to go with?
Putting on my designer hat, this one makes the most sense to me:
https://user-images.githubusercontent.com/95616291/258847077-a0c05d59-9f4c-4293-bf3c-c8ffd8a87844.png

@jpellizzari  Thanks for your answer. We don't have a consensus. I also like the option you point out. How do you usually make a decision? A poll in Slack?

@jpellizzari Thanks for your answer. We don't have a consensus. I also like the option you point out. How do you usually make a decision? A poll in Slack?

Up to you how you want to arrive at a consensus :). Just comment here when we have the desired design selected.

@alfaris or @mmoulian Can you provide a link to the Figma for that view?

@jpellizzari
https://www.figma.com/file/IVHnM9iyeFWpd11evtY8ux/Weave-GitOps?type=design&node-id=19136-224722&mode=design&t=ZFNUhZUnh8t6oywH-4

@jpellizzari I'll not be able to attend the meeting tomorrow because I will be OOO, so I'll work on this ticket.

For what it's worth, I agree with the option that @jpellizzari proposes and @mmoulian agreed to. In my opinion, It looks nicer and more polished than what's currently in Figma and what's been done in #3989 .

+1 to @yiannistri's comment.

@mmoulian any updates, should we merge https://github.com/weaveworks/weave-gitops/pull/3989 or there's a change need to be done ?

I've made a dark mode version on the same link

I hope we can apply it across the system to be coherent experience, and let me know if you needed any help


Use TypeScript

This is a minimal implementation of TypeScript so that a typing definitions file will be available to TypeScript users.

Closed in favor of #5


receivers: fix record signal

Updates signal receiver with the update syntax from
invenio-records. Instead of sending just the record object,
the new syntax sends the sender as well as the record.

Signed-off-by: Harris Tzovanakis<EMAIL_ADDRESS>

@drjova looks good to me. I am still not sure why this is necessary (the whole thing)...but now it should work (according to my changes).

invenio-records version i think will need to be bumped to the latest version in order for travis to pass on lowest requirements.


Authentication and Navigation Overhaul with Context API

This PR introduces key updates to the authentication flow, navigation structure, and Context API for managing medical professional types. Some backend work remains incomplete.
Completed Tasks

[x] Authenticated path for account sign-in

/account/signin route for both patients and medical professionals.

[x] Improved navigability with SelectionUI and dashboard paths

Added SelectionUI, and moved dashboard to /dashboard.

[x] Context API for tracking medical professional type

Tracks whether the user is a doctor, nurse, or other healthcare role.

Incomplete Tasks

[ ] Authentication system pending database setup

No backend database for tracking users yet.

[ ] Context API update pending authentication

Further updates required after authentication backend is completed.

For milestone 1, I updated the authentication routes and navigability settings. No updates for the buttons and other functionalities yet. You can preview though the vercel deployment from my branch, or pull from my branch and run it locally.
We need a minimum of 2 approvals from our group for it to merge to main. Let me know if we need any changes!


Fancy zones preserve size of non-resizable windows

Summary of the Pull Request
Fancy zones is now taking into consideration that window could be non-resizable.
In that case it will place the window into zone without resizing it
PR Checklist

[x] Applies to #1883

Would it be possible to add a unit test for this?

I think so, I'll add them

Would it be possible to add a unit test for this?

We can try to create window using utils, call MoveWindowIntoZoneByIndex same way as here and test if it was resized.

Code looks good. Could you please give examples which windows are not resizable?

Outlook calendar reminder

I tried with office installation window which is not resizable manually, and it was resized,

@SeraphimaZ @PrzemyslawTusinski
you can try the tool to get the window attributes to see if there is anything that can help to identify this type of window
https://github.com/microsoft/PowerToys/tree/master/tools/FancyZones_zonable_tester

Code looks good.
Tested with outlook reminder and it works for me. But maybe better to place window into the center of zone?

Its worth  considering. Please keep it in mind that if static-size window is bigger that the zone, window it should be placed in top-left. It is consistent to place smaller window into top-left corner in my opinion

It is consistent to place smaller window into top-left corner in my opinion

I agree, you can leave it like this for now. Users will provide feedback if their expectation is to have a different behavior.

@SeraphimaZ
PTAL at the last commit. Thanks.


[Q] Display Every Version of the Artifact Table in the Weave Panel

I have the following script that logs an artifact table every x epoch:
sample_audios_table = wandb.Table(columns=["Epoch", "SID", "Sentences", "Audios"])
for k, v in sample_audios.items():
    for vv in v:
        sample_audios_table.add_data(epoch, k, vv[1], wandb.Audio(vv[0], sample_rate=int(hps.data.sampling_rate)))
wandb.log({"sample_audios_table": sample_audios_table})
sample_audios_artifact = wandb.Artifact(
    "sample-audios", type="table",
    description="15 sample SIDs we logged every 50 epoch"
)
sample_audios_artifact.add(sample_audios_table, "sample_audios")
wandb.log_artifact(sample_audios_artifact)

When I check the table under the file section in a specific artifact version it works great. For example, in https://wandb.ai/xxx/xxx/artifacts/table/sample-audios/v95/files/sample_audios.table.json URL I can see the table looking like this:

I was wondering if I can display every version of the sample_audios.table.json in a weave panel in my Run's workplace UI? runs.summary["sample-audios"] used to work but it doesn't anymore. Right now I can only display the logged table but it's just one artifact version:

hey @isdanni -here's a weave query that can display all versions of a single artifact:
project("<entity>", "<project>").artifact("sample-audios").versions.file("sample_audios.table.json")

Thanks! This worked.


Set contentCount values to 0

The fact that these values are set to 4 and 5 in the base test trait is likely complete oversight. For some context, these values are used in the list with real credentials, list with real credentials using the Version 1 API  and list with real credentials in non us-east-1 zone tests. In all of these cases, these are the first tests to run in the test suite and when they do run the buckets are empty which is why 0 is the correct value.
These tests were passing as expected in Minio since they were overridden to be 0 but they were failing in AWS S3.

Relevant CI passed, merging.


froster delete does not work under slurm

froster delete

SLURM JOB

  ID: 5803
  Type: delete
  Check status: "squeue -j 5803"
  Check output: "tail -n 100 -f<EMAIL_ADDRESS>  Cancel the job: "scancel 5803"

peterdir@arc1:~/gh/froster$
peterdir@arc1:~/gh/froster$
peterdir@arc1:~/gh/froster$
peterdir@arc1:~/gh/froster$ tail -n 100 -f<EMAIL_ADDRESS>
DELETING /tmp/froster.Jrd/6j0_subdir
There is no hashfile therefore cannot delete files in /tmp/froster.Jrd/6j0_subdir

local :)


⚠ Bofrost.de has degraded performance

In 00505da, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 892 ms

Resolved: Bofrost.de performance has improved in 43b47fe after 7 minutes.


Error: Invalid JWT form. A JWT consists of three parts separated by dots

Middleware works locally but when we deploy on Vercel the session cannot be parsed
Error: Invalid JWT form. A JWT consists of three parts separated by dots.
    at (node_modules/@clerk/backend/dist/esm/index.js:64:4787)
    at (node_modules/@clerk/backend/dist/esm/index.js:64:11143)
    at (node_modules/@clerk/backend/dist/esm/index.js:64:13218)
    at (node_modules/@clerk/backend/dist/esm/index.js:64:12937)
    at (node_modules/@clerk/backend/dist/esm/index.js:64:13099)
    at (node_modules/@clerk/backend/dist/esm/index.js:64:14093)
    at (node_modules/@clerk/nextjs/dist/server/withClerkMiddleware.js:37:0)
    at (node_modules/next/dist/esm/server/web/adapter.js:103:0) {
  reason: 'token-invalid',
  action: undefined
}

[x] Review the documentation: https://clerk.com/docs
[x] Search for existing issues: https://github.com/clerkinc/javascript/issues
[x] Go through package changelog files.
[x] Provide the Frontend API key from your application dashboard.

NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY=pk_test_cHVtcGVkLW1hZ2dvdC0yOS5jbGVyay5hY2NvdW50cy5kZXYk

Package + Version

[ ] @clerk/clerk-js
[ ] @clerk/clerk-react
[x] @clerk/nextjs ^4.16.2
[ ] @clerk/remix
[ ] @clerk/types
[x] @clerk/themes ^1.6.1
[ ] @clerk/localizations
[ ] @clerk/clerk-expo
[ ] @clerk/backend
[ ] @clerk/clerk-sdk-node
[ ] @clerk/shared
[ ] @clerk/fastify
[ ] @clerk/chrome-extension
[ ] gatsby-plugin-clerk
[ ] build/tooling/chore
[ ] other:

Dependencies + versions
Provide a json with the dependencies used in your project (copy paste from yarn.lock / package-lock.json) or a github project / template that reproduces the issue.
Include the @clerk/ packages and their versions!*
Example:
{
  "dependencies": {
    "@clerk/nextjs": "^4.16.2",
    "@clerk/themes": "^1.6.1",
    "@dqbd/tiktoken": "^1.0.6",
    "@tabler/icons-react": "^2.16.0",
    "@tanstack/react-query": "^4.29.3",
    "@trpc/client": "^10.20.0",
    "@trpc/next": "^10.20.0",
    "@trpc/react-query": "^10.20.0",
    "@trpc/server": "^10.20.0",
    "@yarnpkg/pnpify": "^4.0.0-rc.42",
    "bson": "^5.2.0",
    "clsx": "^1.2.1",
    "eventsource-parser": "^0.1.0",
    "i18next": "^22.4.14",
    "lodash": "^4.17.21",
    "mongodb": "^5.2.0",
    "next": "13.3.0",
    "next-i18next": "^13.2.2",
    "openai": "^3.2.1",
    "react": "18.2.0",
    "react-dom": "18.2.0",
    "react-gtm-module": "^2.0.11",
    "react-hot-toast": "^2.4.0",
    "react-i18next": "^12.2.0",
    "react-markdown": "^8.0.7",
    "react-syntax-highlighter": "^15.5.0",
    "remark-gfm": "^3.0.1",
    "superjson": "1.12.2",
    "uuid": "^9.0.0",
    "zod": "^3.20.2"
  },
  "devDependencies": {
    "@mozilla/readability": "^0.4.4",
    "@tailwindcss/typography": "^0.5.9",
    "@types/jsdom": "^21.1.1",
    "@types/lodash": "^4.14.194",
    "@types/node": "18.15.0",
    "@types/react": "18.0.28",
    "@types/react-dom": "18.0.11",
    "@types/react-gtm-module": "^2.0.1",
    "@types/react-syntax-highlighter": "^15.5.6",
    "@types/uuid": "^9.0.1",
    "@vitest/coverage-c8": "^0.29.7",
    "autoprefixer": "^10.4.14",
    "endent": "^2.1.0",
    "eslint": "8.36.0",
    "eslint-config-next": "13.2.4",
    "gpt-3-encoder": "^1.1.4",
    "jsdom": "^21.1.1",
    "postcss": "^8.4.21",
    "prettier": "^2.8.7",
    "prettier-plugin-tailwindcss": "^0.2.5",
    "tailwindcss": "^3.2.7",
    "tslib": "^2.5.0",
    "typescript": "4.9.5",
    "vitest": "^0.29.7"
  }
}

Browser/OS
Any
Description
We're using Clerk with tRPC in a similar way as it's defined in the starter https://github.com/clerkinc/t3-turbo-and-clerk
The middleware.ts is as follows:
import { withClerkMiddleware, getAuth } from '@clerk/nextjs/server'
import { NextResponse } from 'next/server'
import type { NextRequest } from 'next/server'
import { routes } from './routes'

// Set the paths that don't require the user to be signed in
const publicPaths = [`/sign-in*`, `/sign-up*`]

const isPublic = (path: string) => {
  return publicPaths.find((x) => path.match(new RegExp(`^${x}$`.replace('*$', '($|/)'))))
}

export default withClerkMiddleware((request: NextRequest) => {
  if (isPublic(request.nextUrl.pathname)) {
    return NextResponse.next()
  }
  // if the user is not signed in redirect them to the sign in page.
  const { userId } = getAuth(request)
  if (!userId) {
    // redirect the users to /pages/sign-in/[[...index]].ts

    const signInUrl = new URL(routes.signIn, request.url)
    signInUrl.searchParams.set('redirect_url', request.url)
    return NextResponse.redirect(signInUrl)
  }
  return NextResponse.next()
})

export const config = {
  matcher: [
    /*
     * Match all request paths except for the ones starting with:
     * - _next
     * - static (static files)
     * - favicon.ico (favicon file)
     * - public folder
     */
    '/(.*?trpc.*?|(?!static|.*\\..*|_next|favicon.ico|site.manifest).*)',
    '/',
  ],
}

The root / is not public, and we check the user authentication in order to provide proper redirects
The result is that the user ends up on /sign-in page even when they are authenticated.
I've manually checked every JWT in localStorage and cookies and they are all with valid signatures - __session, clerk-db-jwt, __dev_session
_clerk_js_version: 4.37.0

The issue was resolved by re-applying the environment variables in Vercel, seems when the secret key contains whitespace or is wrong Invalid JWT form error is thrown.


BUG ? eli5.show_weights displayed standard deviation does not agree with the values in feature_importances_std_

The PermutationImportance object has some nice attributes like feature_importances_ and feature_importances_std_.
To visualize in an HTML style this attributes I used eli5.show_weights function. However, I noticed that the displayed standard deviation does not agree with the values in feature_importances_std_.
More specifically, I can see that the displayed HTML values are equal to feature_importances_std_ * 2. Why is that ?
Code:
from sklearn import datasets
import eli5
from eli5.sklearn import PermutationImportance
from sklearn.svm import SVC, SVR

# import some data to play with
iris = datasets.load_iris()
X = iris.data[:, :2]  # we only take the first two features.
y = iris.target

clf = SVC()
perms = PermutationImportance(clf, n_iter=1000, cv=10).fit(X, y)

print(perms.feature_importances_)
print(perms.feature_importances_std_)
print(perms.feature_importances_std_* 2)
eli5.show_weights(perms)

Screenshot: https://pasteboard.co/IWLg5Fe.png

Found the *2 but WHY?
It's in the template generating the feature importances html table.
https://github.com/TeamHG-Memex/eli5/blob/63e99182dc682bbf225355c80a24807396a747b6/eli5/templates/feature_importances.html
        {% if not fw.std is none %}
            ± {{ "%0.4f"|format(2 * fw.std) }}
        {% endif %}

More specifically, I can see that the displayed HTML values are equal to feature_importances_std_ * 2. Why is that ?

value ± 2*sigma gives a ~95% confidence interval; I think that's common to use such confidence interval. See https://en.wikipedia.org/wiki/68–95–99.7_rule

That's not correct. value ± 2*sigma/sqrt(n) is the 95% interval

Thanks @seralouk for digging into this. I think this issue is completely related to https://github.com/TeamHG-Memex/eli5/issues/316 and can be merged.

That's not correct. value ± 2 * (sigma/sqrt(n)) is the 95% interval.

@seralouk this is the confidence interval for the value of the mean of n values drawn from the given normal distribution, which indeed becomes tighter as n increases - but I don't see how this is relevant here.
When we give x +- y for the weights, we mean to say that the true value of the weights lies in the given range with 95% probability. The issue is that our choice of 2 sigma is rather arbitrary. Do you know what would be the standard way to show means along with standard deviations? I've seen mean (std) being used but I think it would be confusing for more people.

I think this issue is completely related to #316 and can be merged.

Indeed this is the same issue, since #316 was posted earlier, let's continue there.


Fix CabGen exclusions for 2012

Docs Build status updates of commit 8b9dce2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/mapping/cabgenConfig.json
:white_check_mark:Succeeded

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 26637c8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/mapping/cabgenConfig.json
:white_check_mark:Succeeded

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


Sharing Service: Unable to get clients to connect to server via WLAN.

Currently unable to build the SharingTest scene get HoloLens devices to connect to the sharing server over a wireless local area network.
Repro Steps:

Open SharingTest.scene
Start Sharing Service.
Copy Sharing Service IP address from server log and paste into Sharing Stage: Server Address field on your SharingStage scene object.
Build Settings -> Add current scene.
Build and deploy to HoloLens via Remote Machine debugger.
Output shows it never connects, and server log never registers device connects.

Note: I tried both local and external IP and am able to connect via the editor using localhost.
Yes I made sure all the devices were connected to the same wireless network, seeing as I can connect to the device portal and deploy via remote machine.

So it worked over WiFi?

Does not work via WiFi.

It would be worth investigating which changes broke this. Was it the big refactor stuff or something later than that. Sorry I am stuck with snow and don't have a device at the moment :(

No worries, I'm pretty sure it's the binaries that are broken.

@matthejo might be able to help with specifics.

Actually... Seems like my firewall was blocking it.  Thought that it was configured properly.
Never got a new prompt to allow the Sharing Service through the firewall.
Gonna keep on with more testing, and might add that in the documentation.

@NeerajW I've tried about everything. I wrote my own UDP client/server. Works flawless in Windows 10. Not in Hololens. I've tried other ways of communicating with the Hololens but nothing seems to work. Except using your SharingService.exe. However it is way to feature heavy for what I want to do: simply change scenes using an Android device. How can I get a SharingService-like thing working on a mobile device? I cannot find the code for SharingService? Or are we simply bound to use this setup, involving a PC hosting the service?


⚠ Bofrost.be has degraded performance

In 28c0eae, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 3452 ms

Resolved: Bofrost.be performance has improved in 0fccd62.


Update sonatype endpoints

JIRA Ticket: https://fedora-repository.atlassian.net/browse/FCREPO-3794
Interested parties
Tag (@ mention) interested parties or, if unsure, @fcrepo/committers

updated main directly.


Can you make it more clear how to use this?

Hey, I'm having an issue where I'm using extract-text-webpack-plugin with codesplitting (currently react-loadable):
const LoadableFeatures = Loadable({
    loader: () => import('../components/features'),
    loading: Loading,
});

and this is using syntax-dynamic-import.    I'm trying to figure out what combination of things I need to do to use your libraries since they seem to be solving the thing I want.
Do I need react-universal-component or just babel-plugin-universal-import?   How do I dynamically load a component that has its own CSS and have that CSS chunked?
I've tried just using react-universal-component by itself:
const LoadablePricing = universal(() => import('../components/pricing'));

and the CSS doesn't get extracted to its own chunk.

You need to use all of the above. Not Loadable.
Study the react-universal-component + webpack-flush-chunks (primarily the latter) to get it all. Then babel-plugin-universal-component and extract-css-chunks-webpack-plugin will make more sense. Basically all 4 are to be used together.

Ok, so if I understand...

Replace extract-text-webpack-plugin with extract-css-chunks-webpack-plugin
Add babel-plugin-universal-import (Does this replace syntax-dynamic-import or in addition to?)
Replace react-loadable with  react-universal-component

I wasn't clear with what the use case was for webpack-flush-chunks, I don't do SSR (our backend is python, not javascript).  Do I still need it?

For the second point you usually don't have to have them both, but if it's not working try adding the additional plugin.
Since you aren't doing SSR there is another plugin by one of our users mentioned on the extract-css-chunks readme for SPAs that you need instead so dual import of both js plus CSS works.

ok... so this is almost working.

css-chunks-html-webpack-plugin is injecting the CSS files into my index.html

window.__CSS_CHUNKS__ = {"containers/learn_container": ... etc

extract-css-chunks-webpack-plugin is extracting them to their own bundles

 dist/css/|grep -v .gz|grep -v .map
app.3eeab27cb082ac4a6d995f1650c3c3f3.css
components
containers
design_patterns.d798f5725576fb5de8bcf5869c4464f4.css
forms.2cb9b80bc2f8de0082c276666755f97b.css
layout.15b6e4710135b445a5ac32cd60d4fc4e.css
site.96d6e7fd064029fe759ad4599df91022.css

but I'm not getting the file dist/css/components/pricing.7aee38290ce8cecb2f21a442a4c63bb3.css loaded when I load this component:
const LoadablePricing = universal(() => import('../components/pricing'));

what part did I screw up that would cause that last piece to not work?

Ok, I see whats happening.   Two issues:

This async fetches the CSS if the page isn't the first page load. But it doesn't load the asset if its the first page. So you have to visit a different page and then go back to see the styles.

It isn't running it through postcss-loader so the asset isn't completely processed.

Do you know how I could fix those two things?

The sass thing was my fault, I'm down to just #1.  The CSS from the async components aren't loaded on the initial requested, they are loaded after if they aren't on the initial request.


Default  Grafana docker name is agraf-3000

>./start-all.sh
>sudo docker ps
CONTAINER ID        IMAGE                    COMMAND                  CREATED             STATUS              PORTS                                                    NAMES
dff03413dfcf        grafana/grafana:4.1.1    "/run.sh"                16 seconds ago      Up 14 seconds       <IP_ADDRESS>:3000->3000/tcp                                   agraf-3000
113c8b8adc88        prom/prometheus:v1.5.2   "/bin/prometheus -..."   21 seconds ago      Up 20 seconds       <IP_ADDRESS>:9090->9090/tcp                                   aprom

Before  https://github.com/scylladb/scylla-grafana-monitoring/pull/210
the Grafana docker name was just agraf. This make kill-all.sh script incompatible

@duarten please take a look, I think this is a result of #210 which I already merged.
Please send a new PR with a fix.

Fixed by ffaa45a7e89d0e1eb3832ab20eb945011108c9c4.


Bump meilisearch dependency to 0.47

Pull Request

[!WARNING]
Do not merge before meilisearch-js releases v0.47

What does this PR do?

Bump meilisearch dependency to 0.47

@Strift no need to open the PR in advance, because as you can see here we need to update yarn.lock too
Bruno will do it the D-day, we don't prepare half of PR in advance 😉
I close the PR


Community meeting May 18 Agenda

Please add a topic in this thread and add a link to the Github issue associated with the topic.

Please make sure you give folks enough time to review/discuss the topic offline on Github before coming into the meeting :)

Topics:

As developer, I 'd to kick off build to generate a image with new tag, so that to do image version management: https://github.com/redhat-developer/build/issues/171. Also, ee need to discuss the user case for the image tagging. Issue 171 mixes two topics.
Extend tests scenarios to include an image deployment: https://github.com/redhat-developer/build/issues/202


Standardize "User [user] not found." in commands

This replaces old instances like "User [user] does not exist." with instances like "User [user] not found.".

I don't think I missed any, but tell me if otherwise.


[Feature] operator can add a config that let fe or be mount a shared RWX pvc to share additional resources like catalog jars

As shown in the title, can this feature be added in future versions

I will look into it. thx


bore-cli: 0.2.3 -> 0.4.0

Description of changes
https://github.com/ekzhang/bore/releases/tag/v0.4.0

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

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

1 package built:

bore-cli


Search via Receipt ID doesn't work

Hi,
NEAR explorer says that you can search by Search for Account ID, Receipt ID, Txn hash, Block hash, or Block height
This transaction
https://explorer.near.org/transactions/AAPtmqFMRK3gxeNrKNVEfRpJ6UzS3rW4qvUUy1ZDmzdR
has this receipt id: Gs8phoC6vYGUuDNSZJ714rseLKbAni4orm7VNJYjPBWM
when I try to find transaction by receipt id, NEAR explorer can’t find it

Thanks for pointing out!
The frontend didn't roll out properly and tried to fetch data from removed endpoints.
It's been fixed.


AJAX error on node creation forms

I get the following AJAX errors more often now when I'm adding resources to the website. See the screenshots below:

These were taken while I was trying to upload a logo, but it has also happened when I tried to click the "publish" button, or something else that the page had to 'load'.
As said, this doesn't happen every time, but I'm encountering it more often.
To go with the log of errors Jules requested, I've seen this mentioned in November last year (that I could find) and I've also mentioned it to Carlos last week that it happened a couple of times. Searched Github and couldn't find anything similar mentioned here.

Let try to put down some facts:

doesn't seem to be link to the OS or browser
the alerts are on (maybe more)

location field
image field

The jQuery version in lpbs (theme) is 2.1.4

Also happened on CT events, field file

Closing this as it doesn't seem to occur anymore
My guess was that is was essentially reminiscences of the old scripts and cache when we published the new theme.
Re-open if you still have this bug of course


Payment issue

How to add new payment method?
How to add card details?

@xyzgd Intuit has two APIs, accounting API and Payment API. The V3 PHP SDK is only support Accounting API rightnow. If you are referring to the payment API, unfortunately, it is not supported right now.

I ran into this limitation today, too! Are there plans to add Payment API support to the PHP SDK; is there a preferable way that the project would like to see support for the Payment API?
Should I copy the patterns from the Accounting portion of the SDK?

https://github.com/intuit/PHP-Payments-SDK


cloudflare_total_tls - missing import documentation / doesn't handle state mismatch

Confirmation

[X] My issue isn't already found on the issue tracker.
[X] I have replicated my issue using the latest version of the provider and it is still present.

Terraform and Cloudflare provider version
Terraform v1.3.2
on linux_amd64
Affected resource(s)
cloudflare_total_tls
Terraform configuration files
resource "cloudflare_total_tls" "tls_certs_by_default" {
  for_each              = local.managed_dns_zones
  zone_id               = each.value.zone_id
  enabled               = true
  certificate_authority = local.total_tls_certificate_authority
}

Link to debug output
n/a
Panic output
No response
Expected output
I'd expect the state to be automatically refreshed and the boolean value to be set as required by the IaC declaration.
However an error is thrown in case when:
total tls is enabled in a Cloudflare zone
total tls is being enabled in IaC state the first time
Actual output
cloudflare_total_tls.tls_certs_by_default[""]: Creating...
╷
│ Error: error creating updating total TLS: No state between current settings and new settings has changed. (1467)
│
│   with cloudflare_total_tls.tls_certs_by_default[""],
│   on main.tf line 35, in resource "cloudflare_total_tls" "tls_certs_by_default":
│   35: resource "cloudflare_total_tls" "tls_certs_by_default" {
│
╵
Steps to reproduce
terraform apply
Additional factoids
How can I import the cloudflare_total_tls resource?
I am happy with any help in terms of importing the resource. Unsure whether to open as a bug or as a feature.
References
No response

The cloudflare_total_tls resource does not support import as of now.


Provide debian package in release page?

How about provide debian package in the release page too? ;)

Hey,
Thanks for the suggestion, that sounds like a good idea, I'll look into it :)
Best


IMAGING-314: Add GeoTIFF metadata to output

This PR extends the current example application that shows how to extract tags and metadata from a TIFF file using the Apache Commons Imaging API.  The new logic includes a summary of GeoTIFF related elements. Some example output is given on the JIRA issue associated with this change.

Created placeholder issue https://issues.apache.org/jira/browse/IMAGING-314

Merged. Thanks @gwlucastrig !


add info about semantic versioning

link to semver site and explain semver. for issue #99

Looks good. Thanks @pravi!


logging: expose more syslog options

Expose more syslog options via --log-opt to make syslog more configurable.
Before this commit we can only log to the default facility kern
of localhost, which may pollute kernel log file.
Also, add a fatal out logic to cilium-agent, cilium-operator and cilium-health,
if an error is returned from SetupLogging.
The following option keys are added:
syslog.network
syslog.address
syslog.facility
syslog.severity
syslog.tag

configmap example for syslog driver: {"syslog.level":"info","syslog.facility":"local5","syslog.tag":"cilium-agent"}
Signed-off-by: Jaff Cheng<EMAIL_ADDRESS>Expose more syslog options

test-me-please

test-me-please

Runtime CI failed as I missed the newly added Alibaba operator cmdref, rebased and updated

test-me-please

For some reason jenkins didn't report the status. I've check and all have passed, only one flake found https://github.com/cilium/cilium/issues/15572. Merging...

(FYI, that flake is actually https://github.com/cilium/cilium/issues/15455.)


Fix sleep on WaitFor helper

Motivation
Need to sleep on error too

Codecov Report

Merging #2418 into master will decrease coverage by 3.69%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #2418      +/-   ##
==========================================
- Coverage   81.56%   77.86%    -3.7%
==========================================
  Files         258       21     -237
  Lines       16432      610   -15822
  Branches     1580       65    -1515
==========================================
- Hits        13403      475   -12928
+ Misses       2606      109    -2497
+ Partials      423       26     -397


wg-stories Meeting 2021-06-01

Meeting date/time (UTC)
2021-06-01 at 17:00 GMT
Instructions for joining the meeting
Stories Working Group Meeting
Tuesday, June 1 · 1:00 – 2:00pm
Google Meet joining info
Video call link: https://meet.google.com/mdz-axok-ndz
Or dial: (US) +1<PHONE_NUMBER> PIN: 560 064 923#
More phone numbers: https://tel.meet/mdz-axok-ndz?pin=2360109061691
Agenda
Note: Add a comment on this issue to propose items for the agenda.

Roadmap for the amp-story-player [amp version] to implement the features present on the non amp version, buttons, events...

Meeting notes
Attendees:
Pratik Ghela, Beto Garcia. Jon Newmuis, Gabriel Majoulet, Wei Hong, Matias Szylkowski, Philip Bell, Ryan Warrender
Story as landing page from Google ads
[Beto] Web Stories as landing pages for search ads has been a successful experience.
[Jon] We’ve seen that stories are a good content format for landing pages.
We’re happy to hear about experiments and findings.
Good use cases and examples can help us build the best experiences.
Data collection component / Lead generation
[Pratik] Is there any update on a data collection component?
We made a valid experience using amp-story-player and amp-form.
[Jon] Forms in the body of the story have UX limitations.
Forms in the page attachments is possible and we’re working it into our roadmap.
Web Stories CTA Updates I2S
[Jon] This will provide a common user experience to make things clear of what is clickable and set user expectation of post-click behavior.
[Pratik] Will amp-story-page-outlink have the same API as amp-story-page-attachment?
[Philip] It’s changed so that it accepts a child a tag. This will allow SEO optimization and all native browser benefits.
amp-story-cta-layer I2D
[Pratik] When do you plan on deprecating cta layer?
[Jon] Fairly long depreciation window of at least 3 months.
Where possible, we will automatically migrate from the old CTA layer to a amp-story-page-outlink.
If there is a CTA layer that contains one link, we will convert it to a button.
We will do the best we can to migrate the whole ecosystem.
Sidebar in amp-story
[Pratik] Is the sidebar deprecated in amp-story?
[Matias] we’re turning it off soon, bookend is deprecated already.
We have an example of an amp-story-player with a sidebar.
[Jon] We’re aiming to find a balance of elements that are specific to the story or the context in which the story is being displayed.
We want to better understand features that allow publishers to link back to content.
Amp Story Desktop One Panel I2I
[Jon] This will allow a more consistent UX and resolve accessibility issues.
[Philip] This will also allow removal of the viewport warnings so stories are supported on all screen sizes. Page transition components will also work on all different stories.
[Pratik] Do we know how many users view on desktop?
[Jon] We don’t track data on what size screens users.
[Pratik] Will the half and half template be brought back?
[Jon] We’re not currently developing half and half layouts.
Pre-created templates within the format have not seen usage in the community.
Some tools have integrated ways to design between both views.
[Ryan] In player context, are there any changes to the supports-landscape story?
[Jon] supports-landscape will be unchanged. We’re thinking of ways we can give a visual hint of next story when supports-landscape stories are in the player.
[Pratik] Visual indication of next page and not next story.
[Jon] The forward and back buttons next to the story are a visual affordance for page navigation.
We’re looking for ways to make multi page story experiences as available as possible.
Most of the time people want to see more stories and not just one.
This is a way for us to open up that possibility.
[Beto] How would the like and comment buttons work?
[Jon] We would allow publishers to add buttons that can control actions such as liking and commenting. (design is WIP)


Nominalize API names

Go from matchWhole -> wholeMatch(in:), which is more consistent with firstMatch etc.

@swift-ci please test


Data filed not being detected correctly?

Data files from stable diffusion UI look like this, each line is a different field.
twitch overlay, glowing, lights, neon, cyberpunk cover art, Octane Render, by Ismail Inceoglu, bubbles in the air, 8k, anime art style, great detail of depth, WLOP lighting, studio Ghibli
Width: 1024
Height: 512
Seed: 9621744
Steps: 50
Guidance Scale: 7.5
Prompt Strength: 0.8
Use Face Correction: None
Use Upscaling: RealESRGAN_x4plus
Sampler: ddim
Negative Prompt: nude, nfsw, watermark, burry, unfocused

Newer versions include more data.
mdjrny-v4 style, A beautiful blue rubber duck in a lake, anime
Width: 512
Height: 512
Seed: 544577117
Steps: 30
Guidance Scale: 7.5
Prompt Strength: 0.8
Use Face Correction: GFPGANv1.3
Use Upscaling: RealESRGAN_x4plus
Sampler: ddim
Negative Prompt: disfigured, kitsch, ugly, oversaturated, grain, low-res, Deformed, blurry, bad anatomy, disfigured, poorly drawn face, mutation, mutated, extra limb, ugly, poorly drawn hands, missing limb, blurry, floating limbs, disconnected limbs, malformed hands, blur, out of focus, long neck, long body, ugly, disgusting, poorly drawn, childish, mutilated, mangled, old, surreal
Stable Diffusion model: D:\stable-diffusion-ui\models\stable-diffusion\mdjrny-v4.ckpt.ckpt
VAE model: D:\stable-diffusion-ui\models\vae\vae-ft-mse-840000-ema-pruned


refactor: use swoole (compatible with Octane)

@carlosfgti Thank you for contribution. Already, you can use Swoole by overriding SERVER build argument. Is there any problem with this?


Ping audio duration limit // Enhancement?

Few days ago I've put a song as my ping sound by accident.
I honestly don't know anything QML audio, but from research I found that you can get file info and duration with it.
It would be great to put some kind of limit to duration of ping sounds.

Could be a prompt when you set the custom audio file - "The audio file you selected is 5m20s long, do you really want to set this as your highlight sound?"

This issue is out of scope of the Chatterino project.


Cart rule not getting applies if any Category is selected in "How to Choose Product" while creating cart rule.

Bug report
Title
Cart rule not getting applies if any Category is selected in "How to Choose Product" while creating cart rule.
Issue Description
Cart rule not getting applies if any Category is selected in "How to Choose Product" while creating cart rule.
Preconditions
1. framework Version-0.1.8

Steps to reproduce
1. step1- Create a cart rule and select any Category from "How to Choose Product section"

Expected result
Discount should get applied on product belongs to that category.
Actual result
Discount not getting applied.

Not getting this issue.

Any update on this?? Cart rules not been applied at all!! Very frustrating :(

@inimist
Which bagisto version you are using?

v0.1.0

I installed it using composer create-project bagisto/bagisto. I am not sure whether I should try to update it to latest stable version. I am also not sure how to do that. Can you please help me with this? I really need to let client know whether we should stay with bagisto as a ecommerce platform for his  business.

@inimist
Please use our latest version 0.2.2 from here.
https://github.com/bagisto/bagisto/releases/tag/v0.2.2

How to update it?

Have you installed 0.1.7 version through zip file?

Please message above:
I installed it using composer create-project bagisto/bagisto. I am not sure whether I should try to update it to latest stable version. I am also not sure how to do that. Can you please help me with this? I really need to let client know whether we should stay with bagisto as a ecommerce platform for his business.

Should I download zip and replace in packages/Webkul?? Should I also update composer.json in root for :
"replace": {
      "bagisto/laravel-user": "v0.1.0",
      "bagisto/laravel-admin": "v0.1.0",
      "bagisto/laravel-ui": "v0.1.0",
      "bagisto/laravel-core": "v0.1.0",
      "bagisto/laravel-attribute": "v0.1.0",
      "bagisto/laravel-checkout": "v0.1.0",
      "bagisto/laravel-customer": "v0.1.0",
      "bagisto/laravel-inventory": "v0.1.0",
      "bagisto/laravel-category": "v0.1.0",
      "bagisto/laravel-product": "v0.1.0",
      "bagisto/laravel-shop": "v0.1.0",
      "bagisto/laravel-theme": "v0.1.0",
      "bagisto/laravel-shipping": "v0.1.0",
      "bagisto/laravel-payment": "v0.1.0",
      "bagisto/laravel-sales": "v0.1.0",
      "bagisto/laravel-tax": "v0.1.0",
      "bagisto/laravel-api": "v0.1.0",
      "bagisto/laravel-paypal": "v0.1.0",
      "bagisto/laravel-discount": "v0.1.0"
    },

??

Install new one and use your existing database

Installed and Cart rules are working! (u)
However Currencies are not working now :(
I created new currency and set exchange rate for it. But it does not show the currency dropdown in header now. Is there a new bug?

Have you selected that currency in channel?

Installed v0.2.2 and cart rules are working now! :+1:

Have you selected that currency in channel?

Yes sorry I had not select it in Channel. It is working fine now.
Ps. I did a fresh install (created new db) with v0.2.2 to avoid any conflicts. All looks good now. Thanks! :+1:

Revamped the entire discount system.


Rich-Text-Editor

As a user I can edit texts in "Details" & "Info-Item"-fields with a WYSIWYG editor.
At least the following features shall be enabled:

Format bold/italic/underline
Bullet lists
Numbered lists
URL-Links
Nice-to-have: Colors, Fonts, Images, Headings

Removed. We will stick to Markdown for the time being...


9esp_timer_is_active ?

Hi,
in the Timer Wrapper,
we cannot ask if a Timer is active ?
https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/system/esp_timer.html#_CPPv419esp_timer_is_active18esp_timer_handle_t
can this be added somehow ?

@diplfranzhoepfinger Yes, this can be added. We will add something like the code in the following patch:
0001-WIP-feat-add-is_active.zip

cool.


CRITICAL ISSUE: Account cannot connect to agents

Describe the bug
Multiple accounts in Origin Asia that I have created and tested became unable to connect to their agents. As a result, these accounts are locked out completely.
I believe this is related to the update on 4th October to clear the databases in Origin Asia since I had never seen this kind of error before the update.
I could not figure out the cause of these errors as they seem to appear at random. @dhh1128 hypothesized that this error occurs when too many browser windows (6 windows) are opened simultaneously. It turns out not to be the case since the same error still occurs to more of my newly created accounts even though I wasn't using them.
Here are the list of affected accounts:

<EMAIL_ADDRESS>ZsYWGPeTxgPOlcxX1Esx5
<EMAIL_ADDRESS>ORBGa4ADp4zn5oBGognhB
<EMAIL_ADDRESS>CF0KaynOunMGuBdk6kD0s
<EMAIL_ADDRESS>EbT6PB116pNq1n73xhdkp
<EMAIL_ADDRESS>RwtabKxBioqQAcc6WwS3h
<EMAIL_ADDRESS>cL40hoY5XcVvwkOr5gLut
<EMAIL_ADDRESS>o09l0tIuzLHjt4vaTuToc
<EMAIL_ADDRESS>0NN3refPqEn0VnZhz67Vb
<EMAIL_ADDRESS>AYycZexAceKQ90UFU8ai0
<EMAIL_ADDRESS>jr0lHTNEvbTR568vhFHCA
<EMAIL_ADDRESS>eYjEzr1gS8m2DKmPEbxHm

To Reproduce
Unknown
Expected behavior
The accounts should be able to connect to KERIA agents
Screenshots
If applicable, add screenshots to help explain your problem.

 When I created a new account, generate a passcode, and paste it on the "Confirm your passcode" box, I encounter An error has occurred, please try again later.

The error of the Chrome dev tool is below.
CognitoUserPool.js:1 [zustand devtools middleware] Please install/enable Redux devtools extension
(anonymous) @ CognitoUserPool.js:1
Show 1 more frame
Show less
/v1/user-mgmt/auth/onboard:1

       Failed to load resource: the server responded with a status of 400 ()
/v1/keria/admin/identifiers:1

       Failed to load resource: the server responded with a status of 400 ()
CognitoUserPool.js:1 INIT_CLIENT_ERROR::: Error: HTTP POST /identifiers - 400  - {"title": "400 Bad Request", "description": "unknown witness BG6aVhGdmp-XtyvWE566MxTwAca3877ru0ni1TgBTv7c"}
(anonymous) @ CognitoUserPool.js:1
Show 1 more frame
Show less
/v1/keria/admin/identifiers/-as-user-at-origin:1

       Failed to load resource: the server responded with a status of 404 ()
/v1/keria/admin/identifiers/-as-user-at-origin/oobis?role=agent:1

       Failed to load resource: the server responded with a status of 404 ()

[from twin in jira]
This issue is being tracked in jira at https://eipi.atlassian.net/browse/DF-2566.
To send new comments there, start them with 'Tell jira:'.
The issue is assigned in jira to Cal Warshaw.
As of 2024-11-04T07:23Z, the status of the issue in jira is 'to do'.

[from twin in jira]
The issue is assigned in jira to Arshdeep Singh.
At 2024-11-05T09:02Z, Daniel Hardman said: Arsh has observed an interesting event in the logs that is almost certainly related to the root cause. He is investigating.

[from twin in jira]
As of 2024-11-05T16:51Z, the status of the issue in jira is 'doing'.
At 2024-11-05T16:51Z, Arshdeep Singh said: This issue is occurring for these accounts because there is a {{dot}} in the org name, for example, {{enauthn.id}},  {{enauthn.dev}}  The reason is that registry records stored in the {{regs}} table are keyed by the Registry Name like for the first account, one of the keys is {{enauthn.id-as-qvi-reg}}. The {{regs}} table is of type {{Komer}}, and in this type, the {{dot}} is used as a separator for combining a tuple of string keys into key bytes. When retrieving values from the database, the keys tuple is separated by splitting at this separator. Therefore, the db key for {{enauthn.id-as-qvi-reg}} becomes {{('enauthn', 'id-as-qvi-reg')}}. This causes an exception with the error {{ValueError: too many values to unpack (expected 1)}}.
We should avoid using {{dot}} in the org name or in the user’s first and last names. We will also add a validation check during onboarding to prevent the use of {{dot}} in names.

Tell Jira:
@Arsh-Sandhu the error also occurs if either name or surname has a {{dot}}.


[ci] Backport bot is broken

https://github.com/single-cell-data/TileDB-SOMA/actions/runs/8191331410
This is a nuisance as I can manually cherry-pick or diff-and-patch.
I don't know what broke or why.

Unbroken! :)


Simplify the starter app

Use the new —open flag provided by the latest webpack-dev-server to automatically open a browser to show the app.

Rename the starter app script to start, so that you can simply run npm start to run the starter app.

Update the README with the new instructions.

👍


Fixed issue #301 - Hardcoded 'em' namespace in installExtension() prevents some extensions from loading

Fixed installedExtension() in FirefoxProfile.php to remove hardcoded namespace prefix.
We now find the what namespace if any we need to use for the 'id' element before searching for it.

👍


⚠ Bofrost.es has degraded performance

In 4154ab3, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1600 ms

Resolved: Bofrost.es performance has improved in 463ba51 after 7 minutes.


Chart not rendering initially, only after chart updates

Anyone have any idea why my chart doesn't render initially, but if I update the component using the react-hot-loader (webpack), things redraw. This is my component:
I tried throwing on the "redraw" prop but it doesn't seem to help.
import React from "react";
import { Line } from "react-chartjs";

var chartOptions = {
    bezierCurve : false,
    datasetFill : false,
    pointDotStrokeWidth: 4,
    scaleShowVerticalLines: false,
    responsive: true
};

var styles = {
    "graphContainer" : {
        "backgroundColor" : "#fff",
        "height" : "235px",
        "width" : "1150px",
        "marginTop" : "15px",
        "padding" : "20px"
    }
};

export default class Histogram extends React.Component {
    constructor(props) {
        super(props);

        this.state = {
            chartData: {
                labels: ["January", "February", "March", "April", "May", "June", "July"],
                datasets: [
                    {
                        fillColor: "#25BDFF",
                        strokeColor: "#25BDFF",
                        pointColor: "#25BDFF",
                        pointStrokeColor: "#fff",
                        pointHighlightFill: "#fff",
                        pointHighlightStroke: "#25BDFF",
                        data: [28, 48, 40, 19, 86, 27, 90]
                    }
                ]
            }
        };
    }

    render() {
        return (

                    <Line data={this.state.chartData} options={chartOptions} width="1100" height="150" />

        );
    }
};

One thing I noticed is that in your code responsive: true which is NOT a chart option. According to Chart.js documentation, we need to set it like: Chart.defaults.global.responsive = true; globally.

Also, the state doesn't exist until the component is mounted according to React.js documentation. Therefore, placing chart data in this.state is not a good idea in this case. How about getting data through this.props from parent component?

Also, according to React.js documentation, we are not allowed to directly set this.state. We should use getInitialState() instead. How about this?

Provide data through props from parent component
Store the this.props.data in the component's state using getInitialState() like
getInitialState({chartData: this.props.data})

I tried setting global.responsive = true, but that doesn't seem to change anything.
I like the idea of providing data through props -- I assume that'll require a pull request?

Please take it easy. You do not need a pull request for that. It is about your implementation. In your code, you place the data using this.state, which is the source of the problem. We cannot control state ourselves, React does on our behalf.

Hmm ok, I think I misunderstood what you were originally saying.
I tried passing in some props to this component, and then passing down these props to my react-chartjs  component, but I still have the same behavior: it doesn't render based on the props until I re-render (hot load) or change the state.

Hey Steve, I just realized rules are a bit different for ES6 from other scripts. I was reading this. My apologies, you were not entirely wrong! I use CoffeeScript so I was just trying to directly translate word by word.
Having said that, I wrote something similar to what you were trying to do, selflessly converting everything into CoffeeScript. Then, it works perfectly at the very first rendering. Here is my code with my home made  chartjs wrapper:

InteractiveChartComponent
example/LineChart

My code is like a pseudo-code. I hope it will give you some ideas to solve your issues.

Ugh I still can't seem to get this to work. I think this must be a bug with react-chartjs. I'll try to do something similar to your home made chartjs wrapper, I think.

I wish I could look into it further with you but I need to learn the new syntax first ;)
I implemented it from scratch but working perfectly on my Rails app. Trust me. Try to translate it in your language. Let me know how it goes, because I want to improve it if necessary. Good luck!

It happened the same here, did you try with
<Line data={this.state.chartData} options={chartOptions} redraw width="1100" height="150" />

Any update to this? seems a common issue.

oh man I wish I saw this thread earlier, any updates

This should get you up and running
https://gist.github.com/rowinf/583fcbafe28d24eae323

Still an issue, not sure why this was closed

@contra chart.js current version is v2.4.0, react-chartjs peer dependency chart.js is v1.1.1. Downgrade chart.js to version v1.1.1 works well.


Better OAS-based configuration for policy configuration

Is your feature request related to a problem? Please describe.
Currently, from the docs, in order to configure rönd sidecar with OAS exposed by an application service you have to specify something link this:
{
  "x-permission": {
    "allow": "greetings_read",
    "resourceFilter": {
      "rowFilter": {
        "enabled": true,
        "headerKey": "x-acl-rows"
      }
    },
    "responseFilter": {
      "policy": "filter_response_example"
    },
    "options": {
      "enableResourcePermissionsMapOptimization": true
    }
  }
}

I find this configuration a bit redundant and suggest the following (heavily breaking) change:
{
  "x-rond-config": {
    "requestFlow": {
       "policyName": "greetings_read",
       "generateQuery":  true,
       "queryOptions": {
          "headerName": "...",
          "language": "..." // for future support to different query languages
       }
    },
    "responseFlow": {
      "policyName": "filter_response_example"
    },
    "options": {
      "enableResourcePermissionsMapOptimization": true
    }
  }
}

We could prevent the breaking change by defining a period where both configuration are accepted (with priority to the new one) so that people can adapt; we can start deprecating the x-permission keyword and then remove support in v2

With PR #84 I've added the new OAS configuration format (named x-rond) but made it non-breaking; as soon as the work is merged I'm going to close this PR and open a new one for the deprecation and removal of the old configuration to be done in v2


Gift Entry:  add DataImport__c.Donation_Donor__c field as a simulated Field Mapping

Critical Changes
Changes

Simulate DataImport__c.Donation_Donor__c field as a Field Mapping

Issues Closed
New Metadata
Deleted Metadata

**lurch: attach W-037936

**lurch: attach W-037936

Tracking W-037936


Sync workflows

Delete call-build-deb.yml
Delete call-build-tag.yml
Update call-chatOps.yml

Up to date with https://github.com/deepin-community/template-repository/commit/19a1058caf85ca87ad1e0dfcd67c7d238c8eff90.

/approve


Transport Endpoint is not connected when run on linux

I get this as an error while using my bot on a Linux machine, however not windows.
Specifically raspberry pi OS 32 bit and windows 10 pro

Both https://mcsrvstat.us, and https://mcstatus.io/status work and so does running it on linux

Sounds like this Linux machine has an outgoing firewall

Not enough information without a stacktrace, code, version of mcstatus, and firewall setup of the raspberry pi.

Please also provide server public IP (if it's public) and try to get status with https://statusmc.perchun.it (it uses mcstatus under the hood, so this eliminates the problem in your computer setup).

Sorry, got busy with work. The website that uses mcstatus works fine, and pi has default firewall configuration the code is just a copy + paste of the example minus the ping

The code is just that thrown into a disnake / command

The code is just that thrown into a disnake / command

Don't really understand what you mean. Just send code and traceback, it would be much better.

pi has default firewall configuration

What exactly is that configuration?

the code is just a copy + paste of the example minus the ping

The example in readme includes a query request, query needs to be enabled on the server, and utilizes UDP. It's possible that the firewall configuration prevents UDP here, or that the server you're trying to obtain query data from simply doesn't have query enabled (you need to set enable-query=true in server.properties)

pi has default firewall configuration

What exactly is that configuration?

the code is just a copy + paste of the example minus the ping

The example in readme includes a query request, query needs to be enabled on the server, and utilizes UDP. It's possible that the firewall configuration prevents UDP here, or that the server you're trying to obtain query data from simply doesn't have query enabled (you need to set enable-query=true in server.properties)

Ok, I see how that could be an issue but the problem is that the code works from a different device

That just means the raspberry pi likely has a firewall which prevents the connection. I don't know what the firewall configuration of raspberry pi is, so I can't tell you much more here, however it is clear that this is not an issue with mcstatus, rather with the configuration of your device. If you do need some more help, feel free to ask on our discord server: https://discord.gg/C2wX7zduxC

Disnake is kinda unrelated to the problem

I also can't send a stack trace because I lost the power cord for the pi that's throwing the error. I can however send the code

I also can't send a stack trace because I lost the power cord for the pi that's throwing the error. I can however send the code

That won't really help us considering it works on another device, again, this is not an issue with mcstatus, it's an issue with the configuration of your device.

from disnake.ext import commands
import disnake
from mcstatus import JavaServer

class minecraft(commands.Cog):
    def __init__(self, bot):
        self.bot = bot

    @commands.slash_command(name="status", description="Get minecraft server status")
    async def status(inter:disnake.CommandInteraction):
        await inter.response.defer()
        try:
            server = JavaServer.lookup("Karsonsserver.duckdns.org", 19132)
            query = server.query()

            emb = disnake.Embed(title=f"Server status", description="The server is Currently Online!", color=disnake.Color.green())

            emb.add_field(name=f"{query.players.online}/{query.players.max} Online", value=f"{', '.join(query.players.names)}")
        except TimeoutError:
            emb = disnake.Embed(title="The server is offline", color=disnake.Color.red())

        await inter.followup.send(embed=emb)

def setup(bot):
    bot.add_cog(minecraft(bot))

I refuse to give tge ip as the ip is unprotected and traces directly back to my home ip, I edited out the ip and deleted its context for my safety

If this same code works on another device, it's clear that query is enabled on the server, and the issue is that the raspberry pi just can't connect to it, this could be because of it's internal firewall configuration (likely blocking UDP), or a network-wide firewall, maybe it's on a VLAN that doesn't allow connections elsewhere, or maybe it's the device where the minecraft server is hosted that has the IP of the raspberry pi blocked.

But it's trying to connect via the same ip on both devices from the same network

Please, stop. We can't help with your firewall here, it is just not the right place.