Add dev friendly unsecured LZ V2 package set (no org policies that block redeployment of the GKE/KCC cluster)

A developer needs a repeatable way to create/delete packages but also to create/delete the GKE KCC cluster
Start with not deploying the gatekeeper-policies
https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/blob/main/docs/landing-zone-v2/README.md#gatekeeper-policies
See for example
-Re-creating the CC GKE cluster after deploying the landing-zone solution requires removal of the requireShieldedVM org policy

https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/issues/132
revisit the rest of the org policies

see also
#534
#549
#548
#541
#545
#546
#535

disable project liens as part of developer friendly workflow
For example - before the kpt live destroy - lifecyle can reconcile - we need to pre-disable the project or delete the lien
michael@cloudshell:~/dev/pdt-oldev/obriensystems (audit-prj-id-oldv1)$ gcloud config set project net-host-prj-prod-oldv1
Updated property [core/project].
michael@cloudshell:~/dev/pdt-oldev/obriensystems (net-host-prj-prod-oldv1)$ gcloud alpha resource-manager liens list
NAME: p553611293232-lb8bec0d8-ed46-45c2-81fb-3dda344e6008
ORIGIN: xpn.googleapis.com
REASON: This lien is added to prevent the deletion of this shared VPC host project. The host project should be disabled before it is deleted.
michael@cloudshell:~/dev/pdt-oldev/obriensystems (net-host-prj-prod-oldv1)$ gcloud alpha resource-manager liens delete  p553611293232-lb8bec0d8-ed46-45c2-81fb-3dda344e6008
Deleted [liens/p553611293232-lb8bec0d8-ed46-45c2-81fb-3dda344e6008].
michael@cloudshell:~/dev/pdt-oldev/obriensystems (net-host-prj-prod-oldv1)$

michael@cloudshell:~/dev/pdt-oldev/obriensystems (net-host-prj-prod-oldv1)$ kpt live destroy landing-zone
folder.resourcemanager.cnrm.cloud.google.com/infrastructure.networking.prodnetworking reconcile successful

add #588
add #132

Actually for 1 of the 2 - the historical Shielded - we are good with the following override
michael@cloudshell:~/kcc-oi/kpt (kcc-oi-9428)$ kubectl get gcp -n policies
NAME                                                                                AGE     READY   STATUS     STATUS AGE
resourcemanagerpolicy.resourcemanager.cnrm.cloud.google.com/compute-require-shielded-vm-except-mgt-project   9m36s   True    UpToDate   9m8s


[UPDATE] remove license holder option/prompt

changed LICENSE file to always have license holder "The Compute.io Authors. All rights reserved."
changed copyright notice in created README.md to "Copyright © <%= year %>. The Compute.io Authors."
removed option/prompt to specify license holder

Coverage decreased (-0.73%) to 68.24% when pulling eed61c906d5ecb7ef5e0ebc819d1f6e54aa5f566 on develop into cd3eb426ec27b87ff42be659cbe78fbc84cecedd on master.

Coverage decreased (-0.73%) to 68.24% when pulling eed61c906d5ecb7ef5e0ebc819d1f6e54aa5f566 on develop into cd3eb426ec27b87ff42be659cbe78fbc84cecedd on master.


Is it possible to flip a camera (back or front) while video streaming? if yes please provide the eg.

i hope anyone post solution

Hi, this is not too hard to do. You can create new video track with the back camera and sent it over instead the front camera video track. you can also enable and disable video tracks during the connection. Good luck.

I've been having problems with this, so if anyone could offer pointers I would appreciate it! At the moment I have:
if let localPeerConnection: RTCPeerConnection = self.localPeerConnection{     localPeerConnection.add(self.localStream.videoTracks[0], streamIds: [self.videoTrackDefaultID]) }
The above is similar to how I set up the connection in the first place with the front camera, which works just fine.
If I then iterate over localPeerConnection.senders, I now have three. The first two are the ones I originally added, and the new one:
id = videoID, streamIds = ["videoID"]
id = audioID, streamIds = ["audioID"]
id = 9ce691b7-7ba3-4ca0-8674-5da44ff2c45b, streamIds = ["audioID"]
I can try and removeTrack, but that doesn't actually remove the track - looking at the code this is apparently to be expected, as I'm using UnifiedPlan semantics, rather than PlanB semantics

As always, I managed to solve this (potentially in a bad way) shortly after asking for help. What I've done for the moment is get the RTCPeerConnection, find the matching entry in the connection's senders, and then set the track of that sender to the new video track. I then tell the connection to restartIce() and that seems to work OK!


x/pkgsite: warn if a module regularly breaks semver

On the right side of the module page there are checkmarks like "stable version" and "redistributable license". I think we should also add a checkmark along the lines of "follows semver". That is, that minor or bugfix versions don't repeatedly make clearly backwards-incompatible changes, like removing entire functions or packages.
Here's an example of such an obvious breakage: https://pkg.go.dev/google.golang.org/grpc/naming
That page does show a This package is not in the latest version of its module warning, but one would usually not find such a warning until after experiencing breakage when updating the module and finding build failures due to the now-missing package.
In other words, if I'm looking at what modules to add as dependencies and I looked at https://pkg.go.dev/google.golang.org/grpc, I'd think twice before adding that module if I saw an alert saying one of the following:

Last breaking change on date (or the version)
N v1 releases contain breaking changes (or N% of stable v1 releases)
N packages have had breaking changes since v1.0.0 (or N% of total packages*

Please realise that I'm only using grpc as an example since it's the one I've struggled with the most recently. The feature would equally apply to any other v1+ module which uses semver-like tags, but which actively breaks the semver compatibility rules.
cc @bcmills @heschik @julieqiu @leitzler

I would be inclined to only report breaking changes found in the latest patch release of each minor version.
(A breaking change corrected in a subsequent patch release is arguably “just a bug” — it should count toward “frequency of buggy releases” but not “frequency of intentional breaking changes”.)

I would be inclined to only report breaking changes found in the latest patch release of each minor version.
(A breaking change corrected in a subsequent patch release is arguably “just a bug” — it should count toward “frequency of buggy releases” but not “frequency of intentional breaking changes”.)

That sounds reasonable to me. If a later bugfix/patch release entirely fixed the breakage, I think that should normally make the breakage not matter for go get -u.

only report breaking changes found in the latest patch release

I assume you mean breaking relative to the first release in its major version, not relative to the immediately preceding release. That is, if v1.0.1 removed a package present in v1.0.0, and v1.0.2 is still missing the package, v1.0.2 still contains breaking changes even though it did not direcly remove a package itself.

That sounds reasonable to me. If a later bugfix/patch release entirely fixed the breakage, I think that should normally make the breakage not matter for go get -u.

only report breaking changes found in the latest patch release

I assume you mean breaking relative to the first release in its major version, not relative to the immediately preceding release. That is, if v1.0.1 removed a package present in v1.0.0, and v1.0.2 is still missing the package, v1.0.2 still contains breaking changes even though it did not direcly remove a package itself.

I assume you mean breaking relative to the first release in its major version, not relative to the immediately preceding release.

Yes. Specifically, breaking relative to the latest patch release of any preceding minor version.
(If a module author “cheats” by backporting the breaking change to a patch release of every preceding minor version... I guess that's a grey area of SemVer? It's essentially saying “the fact that this ever worked at all is a severe bug”, which is analogous to the “security” exception in the Go 1 compatibility policy.)

I assume you mean breaking relative to the first release in its major version, not relative to the immediately preceding release.

Yes. Specifically, breaking relative to the latest patch release of any preceding minor version.
(If a module author “cheats” by backporting the breaking change to a patch release of every preceding minor version... I guess that's a grey area of SemVer? It's essentially saying “the fact that this ever worked at all is a severe bug”, which is analogous to the “security” exception in the Go 1 compatibility policy.)


Hide UI primary and secondary path constraints on k-tool-bar but still maintain on k-info-panel edit

Currently we have this issue #263 to fix clearing constraint values when a circuit is created, but since it's taking longer than expected, and having nested reacted list objects made it a bit harder (vue :actions vs :sync), so until our team sort that out we'll hide these UI options in the meantime during creation of an EVC, but for editing they'll be there, so a network operator can still edit after creating a circuit, this is not optimal, but it's allow using the UI partially.

That way we also don't introduce extra technical debt if we were try to maintain these on k-tool-bar, it would require much more refactoring and duplicated code.

Landed on https://github.com/kytos-ng/mef_eline/pull/285 backport, and on master will land on 284


Question - Aeron Releases support

Which Aeron older releases still got fixes? Any recommendation about migrating from older versions?

We typically only apply patches to the latest release.  However, at the moment, we are patching 1.44.x and 1.46.x as 1.44.x is the last release that will support JDK8.  However, we won't continue fixes for 1.44.x indefinitely.

@callmerockett For people on commercial support we support old versions up to 1 year back. Since our release cadence is once a quarter it is roughly 4 latest major releases that are supported.
A recommendation is to always update to the latest Aeron release as it will contain the latest fixes and improvements.

Thank you for the reply!


fix omb build failure

Hotfix
CI failed to build omb with the following error:
[ERROR] Failed to execute goal on project driver-nats-streaming: Could not resolve dependencies for project io.openmessaging.benchmark:driver-nats-streaming:jar:0.0.1-SNAPSHOT: Failed to collect dependencies at io.nats:java-nats-streaming:jar:2.1.0 -> com.google.protobuf:protobuf-java:jar:3.22.0-RC1: Failed to read artifact descriptor for com.google.protobuf:protobuf-java:jar:3.22.0-RC1: Could not find artifact com.google.protobuf:protobuf-parent:pom:3.22.0-RC1 in central (https://repo.maven.apache.org/maven2) -> [Help 1]

This PR:

updates the version of java-nats-streaming: 2.1.0 -> 2.2.0: according to  https://github.com/nats-io/stan.java/releases/tag/2.2.0 updates the protobuf version
adds explicit dependency for guava: The above version update breaks the driver-nats-streaming/src/main/java/io/openmessaging/benchmark/driver/natsStreaming/NatsStreamingBenchmarkDriver.java script. More specifically, it cannot find the com.google.common.io  package:

[ERROR] /opt/openmessaging-benchmark/driver-nats-streaming/src/main/java/io/openmessaging/benchmark/driver/natsStreaming/NatsStreamingBenchmarkDriver.java:[19,28] package com.google.common.io does not exist

ref https://github.com/redpanda-data/devprod/issues/566

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

test in CI: https://buildkite.com/redpanda/redpanda/builds/22159#01860800-9427-4dd0-99df-93c75af9814e


APPS: remove duplicate definition of trace_data_stack

Note: It seems like the C compiler doesn't care about the duplicate. (The first definition is eight lines above.) The C++ compiler however didn't like it when I reused the tracing code snippets elsewhere.

Checklist

[ ] documentation is added or updated
[ ] tests are added or updated

This pull request is ready to merge

Marge, nice catch BTW.

Marge, nice catch BTW.

Pauli, you are doing me too much honour, it was the C++ compiler who caught it (see top description).


CAP command fixes

This PR contains a few minor fixes for the CAP command, and adds a workaround to let Weechat (and possibly other clients) actually use CAP negotiation when connecting to the server (which is required when registration is now properly suspended during CAP negotiation). If you'd like this squashed, let me know.

I don't know (yet) enough about IRCv3 to review this properly.

All good! CAP CLEAR was removed as a part of the CAP spec here, in the first bullet point in the Errata.
The default implementation forces the NICK and USER commands to end CAP negotiation and the registration suspension. What's actually supposed to happen is the client sends the CAP LS (starts the CAP negotiation phase which suspends registration), then sends NICK and USER, and while registration is suspended CAP negotiation happens. When CAP END is sent, registration continues as normal (here). The is detailed in the last line of the CAP LS spec here.
It also includes a CAP fix for weechat-1.4 which I think I was using at the time.


caddy -quic not working

1. What version of Caddy are you using (caddy -version)?
Caddy 0.11.0
2. What are you trying to do?
Use -quic function
3. What is your entire Caddyfile?
:11220 {
    gzip
}

4.
Server: caddy.exe -quic
Client: chrome with quic option enabled
6. What did you expect to see?
QUIC packets in wireshark
7. What did you see instead (give full error messages and/or log)?
TCP packets
Why isn't QUIC option using QUIC packets?

Probably because our QUIC lib has not been updated in a while, see here: https://github.com/mholt/caddy/issues/2194


Read an account from the service

Acceptance Criteria:
An API endpoint exists for fetching customer account details.
The service returns the correct customer information for valid IDs.
Proper error handling for invalid or non-existent accounts.
Definition of Done:
The API is functioning, and customer information can be retrieved in JSON format via the endpoint.

Estimated Story Points: 5 (M)


Bucket Support

you need to use gsutil -o GSUtil:parallel_composite_upload_threshold=150M cp bigfile gs://your-bucket or i think gsutil -m rsync -r does the same.


[0.10.7-insider] Intellisense with Salsa shows the argument which is the closure compiler style generics in jsdoc as any type at the caller place

Environment

VSCode, Version 0.10.7-insider (0.10.7-insider), 6c2d51a4b7b81753a3a4c46f9de9a15179e20304

with enabling Salsa preview

<EMAIL_ADDRESS>
which is specified with typescript.tsdk

Description
The closure compiler style JSDoc allows the generics like Array<T>, not only Array.<T>.
But the above environment shows the argument styled with its style as any in the intellisense.
problem case
/**
 * @params {Array<string>} v
 * @return {string}
 */
function bar(v) { //
  return v.join();
}

var b = bar(["1", "2"]); // Intellisense shows this signature as `bar(v: any)`;

non-problem case
It's ok Array.<T> or T[]which is allowed in http://usejsdoc.org/tags-type.html
/**
 * @params {Array.<string>} v
 * @return {string}
 */
function foo(v) {
  return v.join();
}

var b = foo(["1", "2"]); // Intellisense shows this signature as `foo(v: any)`;

What I expect
I want Salsa interprets the closure compiler style's generics annotation.
By any chance, I should report this to https://github.com/Microsoft/TypeScript?

This issue was moved to Microsoft/TypeScript#6826


Not working

Hello, I tried your plugin, however it's not really working.
It kind of works in unexpected way right after I input a tag-link combination. It opens the last link in the plugin settings list when pressing the hotkey irregardless of where my cursor is pointing (i.e. not on a tag). And as soon as I change to another note, the plugin stops working altogether. Obsidian restart doesn't fix it, nor does enabling and re-enabling the plugin.

Hi, can you please provide a minimal reproducible example (note and config), and explain the steps you're taking?

Disregard, I re-read the instructions and only now registered that it opens the tag on which the text cursor is. I re-tested it, and expectedly it works. It's a bit cumbersome to use on Kanban boards, where I actually use the tags, but I guess there's no better way to implement the tag links.

Yeah, unfortunately Obsidian doesn't really provide a way to change the behaviour when clicking. Using the text cursor + keyboard shortcut is the only way they provide to make it work.
I have some ideas for how I might be able to make it work on-click, but haven't had a chance to try them out.


Why tabs content is visible always

Hi,
I was trying to test how can I create tabs using materialize, and I was testing this code

Test 1

Test 2

Test 3

Test 4

Test 1

Test 2

Test 3

Test 4

The problem is that the content of all divs is always visible as shown in the following figure

I did intialize the tabs   with this line         $('ul.tabs').tabs();
Can you help me to know why am I getting this weird output? Thank you in advance.

It seems to be working fine (I only did a copy and paste): http://codepen.io/anon/pen/JdQbXP
Could you provide more information about your setup or a codepen illustrating the issue?

When I include it in my project, I got this output.
Here is the link for my project...
https://drive.google.com/file/d/0B2NyxfyoVjxcV2ZISUt6bWxQc0U/view?usp=sharing
I am also using jquery-ui at the same project..
Thank you in advance..

Please, help me to figure out why the tabs are not working in my project. I spent the whole day trying to solve the problem.

It's probably a jQuery ui conflict.

Do you have any idea how to solve this conflict?

It is not a materialize issue but  is a conflict with jqueryui tabs. If you add jqueryui to the codepen by @carlosperate, you can see your issue. If you need jqueryui, just build it without tabs included.

Sorry I did not get you .. How to build the jqueryui without tabs?

Thank you so much...

THANK YOU SO MUCH!
It was indeed a jqueryui issue. Was looking for this the last half hour...


feat: Tezos Provider

Adding Tezos Provider for WalletConnect SDK.
Usage example: PR#607
The old unused files are removed.
This is a DRAFT

Moved to https://github.com/trilitech/tezos-provider/pull/1


fix(protocol-designer): analytics opt in modal fixes

closes AUTH-1142
Overview
Fix when the opt in modal shows up and also adjust the copy and CTAs.
Test Plan and Hands on Testing
Test that this works in your dev env with the gate modal ff turned on like so: make -C protocol-designer dev OT_PD_SHOW_GATE=true. Test that if you select to accept and then go to the settings to toggle it off, it doesn't show up again unless you clear local cache.
Changelog
update modal to match designs
code wise, i added an appVersion prop to the opt_in action. If the appVersion is undefined, it will trigger the modal. also if the opt_in is null, it will trigger the modal. i believe this should force the user to see the modal even if they previously selected false.
Risk assessment
low

changed this back to a draft because the modal isn't working as I thought it was

changed this back to a draft because the modal isn't working as I thought it was

i guess that might be dispatch part that I pointed out.

design

sandbox

from the design, need to remove the header part

I think there is another issue.
when displaying GetModal,  all buttons are not clickable and there is no other option but to press confirm.

I think there is another issue. when displaying GetModal, all buttons are not clickable and there is no other option but to press confirm.

Isn't the the intended behavior though? @koji

I think there is another issue. when displaying GetModal, all buttons are not clickable and there is no other option but to press confirm.

Isn't that the intended behavior though? @koji

okay, i thought the desktop still allows to turn off the mixpanel setting when installing, but now without clicking agree, Opentrons app isn't installed.
The behavior is aligned with the Desktop app.

need to add the following to .eslintignore
**/.yarn-cache/**


Quote mysql params in alembic.tpl

Previously, passwords with special characters (namely %) would result in an error.  Quoting the parameters should allow for these special characters.

Coverage decreased (-4.1%) to 50.989% when pulling 7b9f347f6caf08cd4914a17bef067d7a3c7e2012 on tvon:escape-mysql-params into ddaad98526dbd708ee95d09a04ea0a4f278985a1 on vmware:master.

I'm kinda curious how coverage decreased by adding quotes around variables and removing some trailing whitespace.

It was suggested (in Slack) that the params would need to be uroquote()'d in python to work like this, which means this PR won't actually do anything.
As such, I'm going to close this.


add an option to wait for kube-proxy

Description
This commit is to add the flag in helm, which will enable init
container waiting for kube-proxy if required. The main reason is
to avoid any potential race condition between kube-proxy and
cilium agent. More context can be found in below related PR.
Relates: https://github.com/cilium/cilium/pull/20123
Signed-off-by: Michi Mutsuzaki<EMAIL_ADDRESS>Testing
(tam) The changes are done original by Michi, I just add below minor things:

Add check for kubeProxyReplacement not to be strict
Add securityContext as privileged for running iptables command
Correct manifest syntax error

Testing was done locally by setting this flag enabled (and kube proxy
replacement is not set).
$ helm install cilium install/kubernetes/cilium -n kube-system --set waitForKubeProxy=true

$ ksyslo ds/cilium --timestamps -c wait-for-kube-proxy
2022-07-14T09:44:18.298138416Z :KUBE-PROXY-CANARY - [0:0]
2022-07-14T09:44:18.298293549Z Found KUBE-IPTABLES-HINT or KUBE-PROXY-CANARY iptables rule in 'iptables-nft-save -t mangle'

$ ksysex ds/cilium --  iptables-nft-save -t mangle | grep -E '^:(KUBE-IPTABLES-HINT|KUBE-PROXY-CANARY)'
Defaulted container "cilium-agent" out of: cilium-agent, mount-cgroup (init), apply-sysctl-overwrites (init), mount-bpf-fs (init), clean-cilium-state (init), wait-for-kube-proxy (init)
:KUBE-PROXY-CANARY - [0:0]

/test-1.24-net-next

/mlh new-flake Cilium-PR-K8s-1.24-kernel-net-next

it's not a new flake, merging PR


An idea for add the Chinese version for website documents in opentelemetry.io

Desired feature or idea.
What would you like to see happen?
There are many developers who are always focus on OpenTelemetry in China. 😊
We already have a Chinese project in OpenTelemetry GitHub : https://github.com/open-telemetry/docs-cn.
As a maintainer, i try a better way to spread OpenTelemetry in China.
Our community team want to contribute the Chinese official documents in OpenTelemetry.io . I suggest that whether we can add a link in OpenTelemetry.io ,  which is from the Chinese official introduction project https://github.com/open-telemetry/docs-cn.
Additional context
Anything else you can think about that would be helpful.
I think it is a good way to preach the Technology of OpenTelemetry Observability and bring everyone's more passions in China community . I have already communicated with Ted for the topic ，and he is very nice and  suggested me  to file an issue .
Looking forward your suggestion too.
Please delete paragraphs that you did not use before submitting.

Wow, this is a really great initiative. I think we'd have to discuss what it would mean to have a Chinese version of the site, or at least the site's content.
I can see in the repo you linked that there's content there that summarizes some of the concepts in a different way than we do in this repo. That's both fantastic and a bit of a challenge -- we may need to work out a plan to merge content so that both the Chinese and English versions have the same content.
Some topics that come to mind that we'd have to work out:

Differences in content and how to move forward with that
How to handle site maintenance
How to adjust a contribution flow - for example, someone contributes content in English, how do we port to Chinese?
Multiple SIGs?

@chalin and @svrnm how would you like to proceed?

My first thoughts & comments:

As you probably know, Hugo + Docsy have support for multilingual sites.
We anticipated that other languages would come along and put the English docs under content/en already.
As a trial, we could mount the docs-cn under content/cn as is, and enable the (natural) language version menu.

I think that there are two main ways to approach this. One is to just mount docs-cn as is (with it's different structure), but ideally, both language versions should have the same structure because we'll then be able to setup the cn version of the docs to fall back to the en version when no cn page is present. That way, both sets of docs have all the pages, supporting an incremental translation of the docs.

Hey @laziobird , thanks! I agree with @cartermp that this is a great initiative and definitely something we should have, so we need to discuss the how we can have it, as @chalin outlined it already.
I agree with @chalin that ideally the two should have the same structure (and maybe even live out of the same repo?), I see us having more languages in the future so we should start with a good practice now.
@laziobird would you be able to attend one of our SIG meetings, there is one today at 10 am PST, not sure if this works for you? Otherwise we can discuss it async via the slack channel

Hey @laziobird , thanks! I agree with @cartermp that this is a great initiative and definitely something we should have, so we need to discuss the how we can have it, as @chalin outlined it already.
I agree with @chalin that ideally the two should have the same structure (and maybe even live out of the same repo?), I see us having more languages in the future so we should start with a good practice now.
@laziobird would you be able to attend one of our SIG meetings, there is one today at 10 am PST, not sure if this works for you? Otherwise we can discuss it async via the slack channel

@svrnm Thanks for your  invitation ！I probably can't attend this meetings , i hope to discuss it async via the slack channel continue .   I would like to attend next  SIG  meeting though my English speaking and listening are a little poor ，if you don't mind this . 😊

@laziobird no worries, I understand that. We can keep it async here or in the slack, whatever you prefer.

My first thoughts & comments:

As you probably know, Hugo + Docsy have support for multilingual sites.
We anticipated that other languages would come along and put the English docs under content/en already.
As a trial, we could mount the docs-cn under content/cn as is, and enable the (natural) language version menu.

I think that there are two main ways to approach this. One is to just mount docs-cn as is (with it's different structure), but ideally, both language versions should have the same structure because we'll then be able to setup the cn version of the docs to fall back to the en version when no cn page is present. That way, both sets of docs have all the pages, supporting an incremental translation of the docs.

I very agree it . It is necessary to keep the uniform structure . I would like to be open to support cn version of the docs .

We see a good example : istio
This is en version
https://istio.io/latest/
This is cn version
https://istio.io/latest/zh/docs/
You know , number of documents  is big , and sometime they are changed frequently.
Maybe we can translate the core and main documents first , that  give a fast way to preach OpenTelemetry in Chinese  community and encourage all members to distribute some contents. These contributors who are response for translating  must understand OpenTelemetry and Observability much more .
So we need some time and patience . 😊

@laziobird what we need to continue with this, is an understanding of how many people are there who are willing to help building the chinese version? We need a critical mass of people, who are willing to help with that, to be sure that we can maintain and run this long term, since the existing maintainers are not able to help with that.

Maybe we can translate the core and main documents first ,

Yes, I think there are some pages which are more important than others (https://opentelemetry.io/, https://opentelemetry.io/docs/concepts/, https://opentelemetry.io/docs/getting-started/ are the ones that should be there first, then the getting started for collector & all languages, etc., that's at least my suggestion)

@laziobird Is there any recent development on this topic?
As a native Chinese speaker, I would be delighted to contribute to the creation of a Chinese version.

@laziobird Is there any recent progress on this topic? As a native Chinese speaker, I would be delighted to contribute to the creation of a Chinese version.

Hi:
Petrie, you can join in the slack channel  https://join.slack.com/t/opentelemetry-china/shared_invite/zt-1rzmuyguc-N9DI692M4aa4AlmYr1vfdA . And we can communicate with each other deeply if you are interesting with this plan . My account  is 蒋志伟  in slack .

Cool! You already have so many Chinese pages. Could we use a simple structure like:
https://github.com/open-telemetry/opentelemetry.io/tree/main/content/en
https://github.com/open-telemetry/opentelemetry.io/tree/main/content/zh

It's not easy to find the docs-cn repository among the 63 repositories if I didn't receive tips from @svrnm.

@laziobird @windsonsea @open-telemetry/docs-cn-approvers unfortunately I don't have insights how the docs-cn project came around and what the status of it is.
To provide you some guidance on how we can accomplish a translation accessible via opentelemetry.io:

Our website supports multiple languages already, so the translated content should live under main/content/<two_letter_code> (as @windsonsea pointed out already)
Our point of reference is how kubernetes is doing their localization, see https://github.com/kubernetes/website
We need at least 2 ppl owning that content, so that changes can be approved (CODEOWNERSHIP will help with that)
We can start with the translation been hidden until we reach a point where enough material is translated to go live (with maybe some blog post & announcements around it)

Please anticipate that this is guidance on not a fixed set of rules: Chinese will the first language besides English we translate, so there might be some roadblockers we do not anticipate yet.

See https://github.com/open-telemetry/opentelemetry.io/discussions/4302 for future discussions on this matter.

Reopening since this work has started.

@laziobird @windsonsea et al. - FYI

#4465

All: after thinking about this more carefully, I'd like to make the following proposal:

zh site pages should live in another repo, that we would bring in here via a submodule

It could be open-telemetry/docs-cn or a new repo.
As maintainers know, there are advantages and disadvantages to the submodule approach vs. having the pages in this repo. I'm thinking that during the initial (potentially most intense) ramp up phase of bring in zh pages, it might be helpful to do so in a manner that is quantized, much like what we do for the specifications: e.g., we update spec repos when there is an official release. We could consider doing so for the zh pages too, at least for an initial period.
Thoughts @open-telemetry/docs-approvers @open-telemetry/docs-cn-approvers?
I'm not strongly in favor of either approach, I just wanted to articulate the submodule option in case some of you would consider it preferable (or at least worth trying).

I like the idea of a different repository for the mentioned reasons.
Ultimately, I'd rather follow the preference of @open-telemetry/docs-cn-approvers , as they surely have preferences in terms of localization process, etc.

I am conflicted, but overall I have a strong preference for not having the Chinese (or any other documentation) outside the opentelemetry.io repository for now:

Making this decision now feels premature, and reverting it is much harder than creating the repository later if we find out it's the right thing to do
Until we have gained some experience with localization I'd like to keep this close to docs approvers/maintainers who know the inner workings of the docs. Having translators work from their own repo requires us to take a look at them consistently as well.

I see the point that having more control over the release of translated pages, however I am not sure how to define when we update the releases and when not? We also do not do that for the English pages as of today and live with a set of bugs and issues. We might at some point in the future think about releasing the website vs having hot-updates, but not today.
I think we should keep things as is for today, but re-evaluate the situation in 3-6 months from now

I'm ok with rolling with what we have now, which is the pages living in this repo.

Should English banners show up on the zh homepage? That's how it is currently setup. It might seem reasonable to include the English banners when the Chinese versions aren't available?

Could we provide a placeholder-like? If no localized zh text, use the en banner; if localized, use the zh banner.

Yes, having the English banner would be great. They are often short lived but important, so providing a translation everytime might not be possible


fix vulnerability in minimist

As I mentioned in the ticket description, fixing this requires:

update react-native (on going)
bump eslint to version >7.0.0
add "minimist": "1.2.3" in resolutions entry in package.json, effectively forcing all dependencies to rely on 1.2.3.

This PR only does 3).
Doing 2) breaks our configuration and also, 7.0.0 is still in alpha. IMO, we can skip it because forcing resolution on 1.2.3 doesn't seem to break anything in eslint.
I'll keep this as a draft until 1) is completed.

Closing since this doesn't seem to be an issue anymore


npx changesets-gitlab - git fetch origin main - unable to access URL using bad/illegal format or missing URL

Running npx changesets-gitlab I'm having this error, and I couldn't find any info about what could be the reason.
URL https://gitlab.company.com/project/path/name.git is correct and I could access by the browser.
Could you help us with any clue to look for a solution?
$ npx changesets-gitlab
::set-output name=published::false
::set-output name=publishedPackages::[]
setting git user
[command]/usr/bin/git config user.name Bot
[command]/usr/bin/git config user.email<EMAIL_ADDRESS>setting GitLab credentials
[command]/usr/bin/git checkout changeset-release/main
error: pathspec 'changeset-release/main' did not match any file(s) known to git
[command]/usr/bin/git checkout -b changeset-release/main
Switched to a new branch 'changeset-release/main'
[command]/usr/bin/git fetch origin main
fatal: unable to access 'https://gitlab.company.com/project/path/name.git/': URL using bad/illegal format or missing URL
Error: The process '/usr/bin/git' failed with exit code 128
    at ExecState._setResult (/builds/project/path/name/node_modules/@actions/exec/lib/toolrunner.js:592:25)
    at ExecState.CheckComplete (/builds/project/path/name/node_modules/@actions/exec/lib/toolrunner.js:575:18)
    at ChildProcess.<anonymous> (/builds/project/path/name/node_modules/@actions/exec/lib/toolrunner.js:469:27)
    at ChildProcess.emit (node:events:514:28)
    at ChildProcess.emit (node:domain:489:12)
    at maybeClose (node:internal/child_process:1105:16)
    at ChildProcess._handle.onexit (node:internal/child_process:305:5)

[command]/usr/bin/git fetch origin main
fatal: unable to access 'https://gitlab.company.com/project/path/name.git/': URL using bad/illegal format or missing URL
Error: The process '/usr/bin/git' failed with exit code 128

Do you have a custom GITLAB_HOST environment?

Yes, Im using this variables:
variables:
  NPM_TOKEN: ${CI_JOB_TOKEN}
  GITLAB_HOST: https://${CI_SERVER_HOST}
  GITLAB_CI_USER_NAME: BOT
  GITLAB_CI_USER_EMAIL<EMAIL_ADDRESS>
Could be a change in the configuration? The Gitlab version is GitLab Community Edition 15.11.2

I have no idea with this, maybe you'll need to use patch-package to debug.

@Arnoid31 Does git fetch origin main run successfully when you debug manually? I can only imagine it to be a git issue itself?

Hello @JounQin, and thank you for your reactivity :)
I get exactly the same issue. But in fact I'm surprised we are using here an https: protocol with a .git suffix.
3 weeks ago, the job was working and the fetch was done this way:
[command]/usr/bin/git fetch origin my-branch
From https://gitlab.com/path/to/repository
 * branch            master     -> FETCH_HEAD

and everything was going well.
Another strange thing is, this is the only repository that fails this way, all the others using changesets-gitlab the exact same way are just fine.

@Arnoid31 Are you using different changesets-gitlab versions in different repositories? If so then maybe some recent releases could be related.

Installed version is 0.10.3. I also tried with v0.10.1 which is run by another (working) repository and no change.

Are they running on same git version?

You've got something here: working repo is running Git v2.20.1, not working is v2.39.2. Verified by using v2.20.1 on not working repo, and it works (but as a side effect I had to downgrade Node version from 20 to 16, so might also be related to Node version, but unlikely).

OK so, from what I see, it looks like finally the error comes from Node version. It works with a node:18.17 builder, but not with a node:20.
I can't investigate more for the moment, but maybe I'll get back to you if I have some time proceed to some more investigations.

@JounQin I contacted you at the email address on your GitHub profile (admin(at)1stg(dot)me) to fund this issue investigation, but I'm not sure you are using it on day-to-day.

Faced exactly the same issue with node:20 after adding GITLAB_CI_USER_NAME variable.
Without variable everything is ok.

I check the source codes, the error should only occur at
https://github.com/un-ts/changesets-gitlab/blob/54e3175ad30a3819b9e9610d72cfe0ea1e68760b/src/run.ts#L215
It could be a git compatibility issue, I may need some more useful info like git/node versions, and maybe volunteer to help debugging like #145.

i have the same issue : https://gitlab.com/robin.louarn/monorepo-test/-/jobs/7603795314
$ node -v
v22.6.0
$ git -v
git version 2.39.2
$ pnpm exec changesets-gitlab
::set-output name=published::false
::set-output name=publishedPackages::[]
setting git user
[command]/usr/bin/git config user.name Robin LOUARN
fatal: not in a git directory
Error: The process '/usr/bin/git' failed with exit code 128
    at ExecState._setResult (/builds/robin.louarn/monorepo-test/node_modules/.pnpm/@actions+exec@1.1.1/node_modules/@actions/exec/lib/toolrunner.js:592:25)
    at ExecState.CheckComplete (/builds/robin.louarn/monorepo-test/node_modules/.pnpm/@actions+exec@1.1.1/node_modules/@actions/exec/lib/toolrunner.js:575:18)
    at ChildProcess.<anonymous> (/builds/robin.louarn/monorepo-test/node_modules/.pnpm/@actions+exec@1.1.1/node_modules/@actions/exec/lib/toolrunner.js:469:27)
    at ChildProcess.emit (node:events:520:28)
    at ChildProcess.emit (node:domain:488:12)
    at maybeClose (node:internal/child_process:1105:16)
    at Socket.<anonymous> (node:internal/child_process:[45](https://gitlab.com/robin.louarn/monorepo-test/-/jobs/7603795314#L45)7:11)
    at Socket.emit (node:events:520:28)
    at Socket.emit (node:domain:[48](https://gitlab.com/robin.louarn/monorepo-test/-/jobs/7603795314#L48)8:12)
    at Pipe.<anonymous> (node:net:337:12)

i have the same issue : https://gitlab.com/robin.louarn/monorepo-test/-/jobs/7603795314
$ node -v
v22.6.0
$ git -v
git version 2.39.2
$ pnpm exec changesets-gitlab
::set-output name=published::false
::set-output name=publishedPackages::[]
setting git user
[command]/usr/bin/git config user.name Robin LOUARN
fatal: not in a git directory
Error: The process '/usr/bin/git' failed with exit code 128
    at ExecState._setResult (/builds/robin.louarn/monorepo-test/node_modules/.pnpm/@actions+exec@1.1.1/node_modules/@actions/exec/lib/toolrunner.js:592:25)
    at ExecState.CheckComplete (/builds/robin.louarn/monorepo-test/node_modules/.pnpm/@actions+exec@1.1.1/node_modules/@actions/exec/lib/toolrunner.js:575:18)
    at ChildProcess.<anonymous> (/builds/robin.louarn/monorepo-test/node_modules/.pnpm/@actions+exec@1.1.1/node_modules/@actions/exec/lib/toolrunner.js:469:27)
    at ChildProcess.emit (node:events:520:28)
    at ChildProcess.emit (node:domain:488:12)
    at maybeClose (node:internal/child_process:1105:16)
    at Socket.<anonymous> (node:internal/child_process:[45](https://gitlab.com/robin.louarn/monorepo-test/-/jobs/7603795314#L45)7:11)
    at Socket.emit (node:events:520:28)
    at Socket.emit (node:domain:[48](https://gitlab.com/robin.louarn/monorepo-test/-/jobs/7603795314#L48)8:12)
    at Pipe.<anonymous> (node:net:337:12)

git config --global --add safe.directory $(pwd)

fix my problem for me


Improve place facet grouping  (nested facets) (from 1749)

Problem Description:
It would be desirable to offer users the option to facet by a grouping of facets within the same hierarchy (eg, all things created at great britain)
triage notes:
very high dev costs/time; lack of data
Expected Behavior/Solution:
TBD
Requirements:
TBD
Needed for promotion:
If an item on the list is not needed, it should be crossed off but not removed.

[ ] Wireframe/Mockup - Mike
[ ] Cost benefit/Analysis
[ ] Committee discussions - Sarah
[ ] Feasibility/Team discussion - Sarah
[ ] Backend requirements - TBD
[ ] Frontend requirements- TBD
[ ] Questions
-is this functionality better handled by advanced search?
When this ticket was made we lacked data, (july 25th 2023) do we still lack data?

UAT/LUX Examples:
https://lux.collections.yale.edu/view/results/objects/?q={"text"%3A"stoneware"%2C"_lang"%3A"en"}&sq=stoneware (created at facet)
Dependencies/Blocks:
Related Github Issues:
Related links:
Bugherd:  https://www.bugherd.com/projects/284041/tasks/635
Wireframe/Mockup:

@brent-hartwig - can this be closed for an existing optic ticket?

@brent-hartwig Activities (Creation or otherwise) do not always take place at the same type of place--the place could be classified as a multitude of things (city, country, municipality, are just some examples), and also have multiple classifications. I could generate a list of options of what Places are currently classifiedAs, with the caveat it is could be subject to fluctuation with dataset updates. Let me know if that is helpful.

Thanks, @kkdavis14.  Let's wait to see when this becomes a priority.


SSL certificate doesn't work with new Browsersync setup

Problem
We've regressed back to needing to visit https://xxx.xxx.xxx.xxx:3000 and telling the browser to trust the URL every few days. This isn't as nice as creating a self-signed certificate once and never needing to worry about it again.
Let's try and get this working again!

I can't even get that to work (telling the browser to trust the URL). Very frustrating experience as a first time user of Slate. I followed the directions for getting started but https still doesn't work. What do I do?

Ran into the same issue. Running 'yarn deploy' as mentioned here works.

Related https://github.com/Shopify/slate/issues/726 -- closing this issue to keep discussion in one place.


Update CDI api references to be v1beta1 instead of v1alpha1

Signed-off-by: Alexander Wels<EMAIL_ADDRESS>
What this PR does / why we need it:
Currently KubeVirt uses v1alpha1 API of CDI to do things like upload and create datavolumes. CDI has updated their API to v1beta1 which may have additional fields not present in the v1alpha1 API. This PR updates all references to use the new API.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

CDI API version used is now v1beta1

/hold
Agreed, I am actually already working on adding a condition to the kubevirt cr.

Thinking about this a bit more, I don't think we should stop an upgrade. We have checks for features that require CDI. If CDI is not installed or not present, the features will simply not work. In combination with the condition that should give the user enough information to determine what they need to do to enable the features requiring CDI.

@davidvossel I added a condition to the kubevirt CR to indicate if it properly found CDI with a compatible version. The status is true if yes, and false if no. Added some functional tests to verify it is reporting properly. I still don't think we should stop kubevirt upgrade due to bad CDI, just some features won't be available until they also upgrade CDI

Added some functional tests to verify it is reporting properly. I still don't think we should stop kubevirt upgrade due to bad CDI, just some features won't be available until they also upgrade CDI

I get where you're coming from, and for the install case this makes sense.
However, for updates the thing that concerns me is people can be in a situation where their VM/VMI is up and running using a DataVolume, then after the update they're in a situation where that VM/VMI is unusable. It's possible it might even making existing workloads fail because our informer will fail to detect the datavolume exists.
I'm not sure it's a situation where features simply aren't available. For updates it appears like it can impact existing workloads as well.

However, for updates the thing that concerns me is people can be in a situation where their VM/VMI is up and running using a DataVolume, then after the update they're in a situation where that VM/VMI is unusable. It's possible it might even making existing workloads fail because our informer will fail to detect the datavolume exists.

That is a very good point.  But I suspect the number of cases in which a datavolume is looked up are few and could be handled by looking for a PVC of the same name (when in this state)?  I know the restore logic would have to deal with it somehow as well.
I am not necessarily opposed to aborting an upgrade if old CDI is detected.  In this situation, we should still be able to take advantage of the new condition because the KubeVirt CRD is updated at the same time as the operator, right?

The only potential issue I can think of, for running workloads is a live migration where the new pod on the new node needs to know the DV so it can attach the matching PVC to the new pod. Other than that, running workloads don't care about DVs because we use DVs to determine if the VM is able to run. Once its running it won't reference the DV again. Snapshots might be a different beast, haven't looked into those closely.
And thinking some more about the live migration scenario. The live migration simply won't complete due to the new pod not being able to start because of no DV support. You can start the live migration, and once CDI is updated it can compete. Seems like normal k8s behavior to me.

Other than that, running workloads don't care about DVs because we use DVs to determine if the VM is able to run.

i don't know for sure what will happen. It could lead to a confusing state for our VM controller if one one the DataVolumes in a VM's DataVolumeTemplate section is all of the suddened not present after the VMI has launched. Maybe it works fine, maybe things get weird. It's kind of undefined territory.

I am not necessarily opposed to aborting an upgrade if old CDI is detected. In this situation, we should still be able to take advantage of the new condition because the KubeVirt CRD is updated at the same time as the operator, right?

usually the crd is updated. i think 99% of the update flows people use are related to the olm flow. and in that case the crd is updated.


Not working with lowercase country code

Describe the bug
Not working with lowercase country code(en-us).
I want to use a lowercase URL plan. So I add locales with lowercase to next-i18next.config.js. But not translated.
Just in case using country code with uppercase(en-US)
Occurs in next-i18next version

"next": "^10.0.8"
"next-i18next": "^8.1.1"

Steps to reproduce

Repository: https://github.com/qvil/next-boilerplate
Demo: https://next-boilerplate.vercel.app/en-uk/i18n-lowercase

Expected behavior
I expect to translate, work normally.
Screenshots

OS (please complete the following information)

Windows 10 pro
Browser: Chrome 89.0.4389.82

Additional context
I guess country code recognize with uppercase. Because I saw the i18n conosle.log.

Not sure if this is on the i18next side, or the NextJs side, but I have observed this behaviour previously. The short answer is that: (1) those are invalid locales (with lowercase), and (2) this is not handled by next-i18next.

To those stumbling upon this issue that don't want to use uppercase region codes in their urls: i18next provides a setting to allow lowercase region (ISO-3166) codes to be used: lowerCaseLng (See: https://www.i18next.com/overview/configuration-options#languages-namespaces-resources )
It can be used like this with next-i18next:
module.exports = {
    i18n: {
        defaultLocale: 'nl',
        locales: ['en-us', 'nl'],
        lowerCaseLng: true
    }
};

Resurrecting this from the dead @DuckThom @isaachinman  but looks like this is no longer supported/not working?
warn  - Invalid next.config.js options detected:
  - The value at .i18n has an unexpected property, lowerCaseLng, which is not in the list of allowed properties (defaultLocale, domains, localeDetection, locales).

Was working on next 11 and next-i18next 10.3.0 but on 13 and 13 its not


Fix CI branch name

USER STORY
As a developer, the CI pipeline should work properly
ACCEPTANCE CRITERIA
GIVEN
A pull request to development
WHEN
Github actions are run
THEN
Actions should be run on development branch

Currently Github actions runs on master branch, but branch was renamed to development

Currently Github actions runs on master branch, but branch was renamed to development


Power spectrum class

This is the basic implementation for making power spectra and averaged power spectra.
I've written tests and docstrings, but not all of it has tests, so there's some work to do.
I am especially not sure if the implementation of the rms computation and the rms error is correct.
My main reason for submitting the pull request now is so that you can have a look at it, and see whether the structure makes sense. If it does, we can start building on that. Tests are run with nosetests and python 2.7.

One thing I'll work on next is adding array support for the FFTs and whatnot -- making sure it's applied over a specified axis.


How do I query the public key of my CreateAccount through code

I create a new account through the SystemProgram.CreateAccount(). If I don’t save the new account PublicKey, how can I query the public key through code?

If you do not save the key pair there is no way to query it by code.


Honda - Remove expriry points annually code

Regarding Honda team changed requirement of expriry points condition. We have to remove code expriry points annually in Honda live site. It will happen again on 30 December 2024
Umer Code : https://hondanont.zaviago.com/app/scheduled-job-type/overrides.reset_loyalty_points

@friendthita what the status on this please update with comment here.

Nabeel will talk with umer about o removal his code and Nabeel have stoped the cronjob so it will not gets executed next time ka @John-zaviago


Generalising the mouse button FSM.

Taking this out of the container package so it can be reused by widgets.
Fixes #21

Pull Request Test Coverage Report for Build 722

55 of 56 (98.21%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 90.289%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

mouse/button/button.go
41
42
97.62%

Totals

Change from base Build 715:
0.03%

Covered Lines:
4816

Relevant Lines:
5334

💛  - Coveralls

Pull Request Test Coverage Report for Build 722

55 of 56 (98.21%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 90.289%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

mouse/button/button.go
41
42
97.62%

Totals

Change from base Build 715:
0.03%

Covered Lines:
4816

Relevant Lines:
5334

💛  - Coveralls

Pull Request Test Coverage Report for Build 722

55 of 56 (98.21%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 90.289%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

mouse/button/button.go
41
42
97.62%

Totals

Change from base Build 715:
0.03%

Covered Lines:
4816

Relevant Lines:
5334

💛  - Coveralls

Pull Request Test Coverage Report for Build 722

55 of 56 (98.21%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 90.289%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

mouse/button/button.go
41
42
97.62%

Totals

Change from base Build 715:
0.03%

Covered Lines:
4816

Relevant Lines:
5334

💛  - Coveralls


Build failure: python3Packages.langchain, langchain-core, etc. builds don't match the version number

langchain is used to build generative AI clients. It contains a large number of components each of which is released on its own cadence. This means that some components have higher version numbers than others at a given time.
But an error in the last set of commits has set these all to the the same version >= the versions released since.
This blocks updating the packages to their actual versions.
How to reproduce
Compare the version numbers in source/Hydra (0.2.9) to the current releases below.

Component
Listed release
Release built
Current release
Notes

langchain
0.2.9
0.2.5
0.2.9
cannot update to latest

langchain-community
0.2.9
0.2.5
0.2.7
cannot update to latest

langchain-text-splitters
0.2.9
0.2.2
0.2.2
mis-labeled, should revert

langchain-core
0.2.9
0.2.9
0.2.20
Can update

langchain-chroma
0.2.9
0.1.2
0.1.2
mis-labeled, should revert

Root cause
The code is in a monorepo with individual releases for each specific component. Each release of the monorepo is tied to a specific component, for example, release langchain==0.25 is used to build langchain; langchain-core==0.29 to build langchain-core; etc. There's no way to sync these all to the same number, they are disparate releases by design.
The last commits replaced the specific release checkout for each component with langchain-core==0.29 release. This had the effect of inflating some version numbers without a corresponding release.
Proposed solution
Revert the following commits:

python3Packages.langchain: 0.2.5 -> 0.2.9
python3Packages.langchain-community: 0.2.5 -> 0.2.9
python3Packages.langchain-text-splitters: 0.2.1 -> 0.2.9
python3Packages.langchain-chroma: 0.1.1 -> 0.2.9

Then bump the version numbers correctly on langchain (0.2.5 -> 0.2.9), langchain-community (0.2.5 -> 0.2.7), and langchain-core (0.2.9 -> 0.2.20).
I could submit a PR but I'm not sure about rolling versions back in Hydra and reverting commits in PRs.
Notify maintainers
@mweinelt for patch reversion
@natsukium as listed maintainer
Note: I'm willing to join these as a maintainer. I'm also preparing to bring in langgraph
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[sec@dervish:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.6.37, NixOS, 24.11 (Vicuna), 24.11.20240709.feb2849`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.4`
 - channels(root): `"nixos-23.05"`
 - channels(sec): `""`
 - nixpkgs: `/nix/store/xr9wjzx0cdnwkmhzz74h8lphgn5jmyv3-source`

Add a :+1: reaction to issues you find important.

This was part of a bulk update of python packages, and the version was determined programatatically from the update script used for all Python packages.
I'll leave this with the maintainer.

Thank you for the quick response.

fixed in https://github.com/NixOS/nixpkgs/pull/328207


Actions can still be taken on already accepted submissions.

On the page for reviewing submissions for a given project, even after Accepting a task, you can again click the accept button. This is a little confusing.
Also the submissions can be returned or even rejected after already accepting it once.

this page has been redesigned this issue is addressed


Typo "avaiable" vs available

Describe the bug
In non-latest (deprecated) datasets, the standard blurb has a typo - "IMPORTANT! This dataset has been retracted and is no longer avaiable for download."
To Reproduce

browse here and
see this

Expected behavior
No typo

This shows how one can miss something in plain sight for years...

This will be available on aims2.llnl.gov shortly, been merged into master now.

Nice work gents, v1.2.0 looks shiny and typo-free!

Deployed!  Ensure you refresh your tab / or start a new browser session to see the corrected spelling.


Pushdown of slicing operator on arrays?

Hi, I would like to use dask.delayed on a sparse TileDB array like described here:
https://docs.tiledb.com/dask/tiledb-with-dask-delayed
Due to the sparse nature of my array (shape is [3x10^9, 3x10^9, 7000]), dividing the dataset into separate chunks and loading them into memory is quite wasteful to impossible.
Instead, I would like to make use of the fancy slicing capabilities of TileDB.
Is it possible to have a custom Dask delayed object that pushes down slicing to the underlying array?

EDIT to be more concrete:
What happens when I do the following:
x = dask.array.from_array(tdb, chunks=(1000,))[:1000]
y = x[:100]
z = y[:10]

Does Dask then call tdb[10] or does it call tdb[1000][100][10]?

I am not quite sure I understand your question. It'd help to have a reproducible example. Can you replace tbd with a numpy array that looks like your tiledb object?

OK, maybe this example shows my problem better.
The query:
dask.array.zeros(200000000000, chunks=(100000000000,))[:10000000000][:1000][:10].compute()

Expected result:
array([0., 0., 0., 0., 0., 0., 0., 0., 0., 0.])

Actual result:
Traceback (most recent call last):
  File "/opt/anaconda/envs/kipoi/lib/python3.7/site-packages/IPython/core/interactiveshell.py", line 3331, in run_code
    exec(code_obj, self.user_global_ns, self.user_ns)
  File "<ipython-input-18-3411c0606a9e>", line 1, in <module>
    dask.array.zeros(200000000000, chunks=(100000000000,))[:10000000000][:1000][:10].compute()
  File "/opt/anaconda/envs/def/lib/python3.7/site-packages/dask/base.py", line 166, in compute
    (result,) = compute(self, traverse=False, **kwargs)
  File "/opt/anaconda/envs/def/lib/python3.7/site-packages/dask/base.py", line 444, in compute
    results = schedule(dsk, keys, **kwargs)
  File "/opt/anaconda/envs/def/lib/python3.7/site-packages/dask/threaded.py", line 84, in get
    **kwargs
  File "/opt/anaconda/envs/def/lib/python3.7/site-packages/dask/local.py", line 486, in get_async
    raise_exception(exc, tb)
  File "/opt/anaconda/envs/def/lib/python3.7/site-packages/dask/local.py", line 316, in reraise
    raise exc
  File "/opt/anaconda/envs/def/lib/python3.7/site-packages/dask/local.py", line 222, in execute_task
    result = _execute_task(task, data)
  File "/opt/anaconda/envs/def/lib/python3.7/site-packages/dask/core.py", line 121, in _execute_task
    return func(*(_execute_task(a, cache) for a in args))
  File "/opt/anaconda/envs/def/lib/python3.7/site-packages/dask/core.py", line 121, in <genexpr>
    return func(*(_execute_task(a, cache) for a in args))
  File "/opt/anaconda/envs/def/lib/python3.7/site-packages/dask/core.py", line 121, in _execute_task
    return func(*(_execute_task(a, cache) for a in args))
MemoryError: Unable to allocate array with shape<PHONE_NUMBER>00,) and data type float64

or would it pass the slicing operator down to the underlying array?

Nope, we don't do predicate pushdown yet. This is one of the goals mentioned in https://github.com/dask/dask/issues/5644.

Thank you for your answer @TomAugspurger .
Is there an easy way to hack the slicing operator, e.g. by inheriting from Dask array?
This way, I could create an ArrayView that caches all slicing operations instead of materializing them.

I'm not sure, but that sounds somewhat difficult.
I'm not familiar with tiledb, but you might be able to construct smaller
chunks by using tiledb operations to do the filtering before it gets to
Dask data? Or perhaps your initial tasks could include the slicing?
On Fri, Jun 5, 2020 at 10:44 AM Florian R. Hölzlwimmer <
<EMAIL_ADDRESS>wrote:

Thank you for your answer @TomAugspurger
https://github.com/TomAugspurger .
Is there an easy way to hack the slicing operator, e.g. by inheriting from
Dask array?
This way, I could create an ArrayView that caches all slicing operations
instead of materializing them.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/issues/6288#issuecomment-639578373, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKAOIXPNDYVUYIAWUMFILDRVEHFFANCNFSM4NTBO6AQ
.

I'm not sure how feasible this is, but I figured I'd open this issue for discussion anyway.

We're lately looking again into https://github.com/dask/dask/issues/7933 and I expect us to push on this in the next couple of weeks/months. Part of this effort is to enable logical graph rewrites as you are suggesting here.


[MINOR] Use try with resource to close stream

Change Logs
use try with resource to close stream
Impact
If input streams are not properly closed after use, it can potentially affect the normal execution of commands or programs.
Risk level (write none, low medium or high below)
there is a low level
Documentation Update
Describe any necessary documentation update if there is any new feature, config, or user-facing change

The config description must be updated if new configs are added or the default value of the configs are changed
Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
ticket number here and follow the instruction to make
changes to the website.

Contributor's checklist

[ v] Read through contributor's guide
[ v] Change Logs and Impact were stated clearly
[ v] Adequate tests were added if applicable
[ v] CI passed

Hi, can you elaborate a little more what would happen if the inputstream is not closed properly? Can you write a test case to demonstrate the resolution of the issue.

Hi, can you elaborate a little more what would happen if the inputstream is not closed properly? Can you write a test case to demonstrate the resolution of the issue.

To demonstrate the issue of unclosed IO streams, I can write the following test program:
`import java.io.*;
public class UnclosedIOTest {
public static void main(String[] args) throws IOException {
BufferedReader reader = new BufferedReader(new InputStreamReader(System.in));
BufferedWriter writer = new BufferedWriter(new FileWriter("output.txt"));
    System.out.print("Please enter a line of text:");
    String line = reader.readLine();
    writer.write(line);
    System.out.println("Written to output.txt");
}

}
`
This program uses an unclosed BufferedReader and an unclosed BufferedWriter. When the program runs, the user will be prompted to enter a line of text, and the program will write this line of text to a file called output.txt. However, because the BufferedReader and BufferedWriter are not closed, it can lead to the following issues:
Resource leakage: When the program is run repeatedly, a new BufferedReader and BufferedWriter will be created each time, but the old IO streams are not closed, and they will continue to occupy system resources, which may eventually cause the system or program to crash.
Data loss: If an exception occurs while writing data and the BufferedWriter is not closed, the written data may be lost because they have not been flushed to the disk yet.
To solve these issues, you should add the following code at the end of the program to close the IO streams:
reader.close(); writer.close();
This will ensure that the program correctly releases the IO resources.

The CI is failing, can you check it.

The CI is failing, can you check it.

It's hard to find the problem,can you help me?

The CI is failing, can you check it.

yeah,found the problem.

The failure is known to be flaky, would merge it soon ~


RD2: Changes to RD applies to future Open Opportunities

As a user I want to make a change to the RD record and have all future Opportunities reflect the new value so that I can have a single RD and yet track actual expected revenue correctly.
Critical Changes
Changes
Issues Closed
New Metadata
Deleted Metadata

**lurch: attach W-037459

Tracking W-037459

**lurch: attach W-038156

Tracking W-038156

@heidmary , @Julian88Tex : WIs are ready for testing.

@RadSFDeveloper @force2b @heidmary Testing has been completed on both tickets for this PR:
https://foundation.lightning.force.com/lightning/r/agf__ADM_Work__c/a2x1E000001HpqxQAC/view
https://foundation.lightning.force.com/lightning/r/agf__ADM_Work__c/a2x1E000001HoVPQA0/view


Disabling logs of android-job library

I just wanted to know how to diable logging of jobs? I don't want these logs to appear on logcat of  users of my app. I mean the logs that show scheduling, rescheduling and sucess or failure of different jobs.
@vRallev

JobManager.instance().getConfig().setVerbose(false);

That's the trick :) Please close the issue if that solves it.

Thanks.
I am using version 1.0.13 of job-library (so as I can have periodic tasks with less than 15m intervals). Seems that getConfig() is not availbale in this version?

You should use the latest version, your jobs won't work correctly on Android 7.0 and 7.1. But I think on the old version you can call JobManager.instance().setVerbose(false);.

Thanks. That was it.


Matrix screensaver video

Hi! Can you upload one somewhere please? :D Very curious to see it moving! (if it does)

Sure, this clip has the hue animation turned on: https://youtu.be/gSZX4lkeEfc?si=v0LHiAucjCk0xI7P


issue with esrgan implementation

hi, i was making my own implementation of esrgan, except i made 2 changes, the number of rrdb blocks is 8 and i haven't included L1 loss in the perceptual loss function. The data is cell microscopy data and after 100 epochs i have been still getting output like the ones attatched in images( the generated is the 3rd image, ground truth is 4th, 1st and 2nd are bicubic and nearest neighbor). does my network need more epochs to train or is there something wrong.
P.S. i am asking this because these color losses in a normal srgan start to disappear after 10-20 epochs only.

Hey,
I am facing something similar too, did you find a solution to your problem?

hey @HarshPathakhp, I'm sorry it didn't work i had to switch my strategy

L1 loss should not deprecated in loss function


Get Envoy Mobile ready for C++20

Unfortunately, it's blocked by the fact that the Android NDK and XCode clang compilers are not C++20 ready.  There are some severe enough issues in compilation of C++20 features using Clang 16, that the minimum bar set for upgrade to C++20 for the NDK team (and Google's adoption of XCode for C++20) is Clang 17.
Once we're on an NDK and XCode version that supports Clang 17, we can switch Envoy Mobile to building with C++20.

see https://github.com/envoyproxy/envoy/issues/32955 for tracking ticket


Apply viewing hint to sequence as well as manifest

@escowles @jpstroop Since we're all gone for the night, can someone merge this in the morning? Paged viewing in UV doesn't work without it. =(


Add map type property (standard, satellite, hybrid) to MapView.

Here is an example project demonstrating this pull request: AKMapView

I suggest using enums instead of NSUInteger. Take a look at how the Image component RCTNetworkImageViewManager.m uses the UIViewContentMode enum with help from RCTConvert.h.

@paramaggarwal Thanks for pointing me in the right direction. I updated the PR to use an enum for the mapType property. I also updated my example project: AKMapView

@adamkrell - looks good aside from the one small style nit, can you fix that and squash into one commit?

@brentvatne Fixed coding convention issue and squashed commits.

Looks good to me!

@tadeuzagallo - assigned you to this as your name appears most frequently in related code, re-assign as you see fit of course :smile:

@tadeuzagallo I removed the unnecessary changes to RCTMap.

Looks good now, thanks! :smiley:
@facebook-github-bot import


Add deamon for Wifi onboarding via Bluetooth LE ('bluenetd')

To test this on Senic OS run following commands as root:
vim /etc/network/interfaces  # comment out wlan0 related lines
killall wpa_supplicant
NetworkManager
cd /srv/senic_hub
venv/bin/bluenetd -b hci0 start -d senic.local

Todos in Senic OS:

running these commands on startup
fix permission problems for senic user
remove wlan0 from /etc/network/interfaces
provide actual DNS name
remove wifi_scan process (?)

Known issue:

BLE service is not found on two different devices running Android 5.1 (but Nuimos are working, maybe a problem in how BlueZ advertises the services or a bug in Android)

Addressed all requested changes (indentation, renaming, code style). Renamed files and branded everything 'bluenet', too.


Buffer test cleanup and bug fix

The way we check buffers for correctness now is really annoying:

ASSERT_* does some crazy hackery where it doesn't end the test if it's called inside a function. So if you use it inside a for_each_index-ish lambda callback, one failing test generates thousands of errors. And we run fuzz tests in loops...
It's hard to see problems without context in the buffers.

One way to fix that would be to use the ASSERT_THAT matchers from gmock.h. This PR tries to do that in a few places, but hasn't eliminated all uses of for_each_index yet.
While attempting this PR, discovered a bug when fusing folded buffers.

 IMHO we're usually better off using CHECK or QCHECK.

use the ASSERT_THAT matchers

These are apparently the New Hotness because reasons, but can I say that I really dislike them because when there is a failure it can be hard to unwrap what's actually happening because the matchers get pretty convoluted.


Remove any dependency to Apache HTTP client

We are already using a plain HttpURLConnection, but the handling of POST request bodies was still done using Apache’s classes. This commit switches to plain built-in classes.
Note: Apache HTTP client will be removed in Android N, so we need to drop it to remain compatible.

LGTM :+1:


Added ability to validate YAMLs with multiple documents

Closing this PR as it had unintended circle-ci commits

Anyway I liked the idea! If you find time please recommit without circle-ci. Thanks!


Update import-physical-badging-data.md

Sample Data was not syntaxed correctly

@garajori PR merged. Thanks for updating.


feat: Stripe Coupon Admin

Description

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)

Type of change

Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that may cause existing functionality to not work as expected)
[x] Documentation update

Checklist

[x] My code is well-commented, linted and follows project conventions
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] Any dependent changes have been merged and published in downstream modules
[x] I have checked my code and corrected any misspellings
[x] I have updated the changelog

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 91.65%. Comparing base (fe1d748) to head (b5018dc).
Report is 1 commits behind head on dev.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##              dev      #53      +/-   ##
==========================================
+ Coverage   91.55%   91.65%   +0.10%
==========================================
  Files          57       59       +2
  Lines         971      983      +12
==========================================
+ Hits          889      901      +12
  Misses         82       82

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Gradle version 6

I’m thinking to upgrade Gradle version of this repository. From 4 to 6.
Good exercise for me to learn Gradle.

com.google.common.util.concurrent.ExecutionError: java.lang.NoClassDefFoundError: org/gradle/api/internal/java/JavaLibrary
suztomo@suxtomo24:~/gax-java$ ./gradlew assemble
Downloading https://services.gradle.org/distributions/gradle-6.0-bin.zip
..........................................................................................

Welcome to Gradle 6.0!

Here are the highlights of this release:
 - Substantial improvements in dependency management, including
   - Publishing Gradle Module Metadata in addition to pom.xml
   - Advanced control of transitive versions
   - Support for optional features and dependencies
   - Rules to tweak published metadata
 - Support for Java 13
 - Faster incremental Java and Groovy compilation
 - New Zinc compiler for Scala
 - VS2019 support
 - Support for Gradle Enterprise plugin 3.0

For more details see https://docs.gradle.org/6.0/release-notes.html

Starting a Gradle Daemon (subsequent builds will be faster)

FAILURE: Build failed with an exception.

* Where:
Build file '/usr/local/google/home/suztomo/gax-java/build.gradle' line: 96

* What went wrong:
A problem occurred evaluating root project 'gax-java'.
> com.google.common.util.concurrent.ExecutionError: java.lang.NoClassDefFoundError: org/gradle/api/internal/java/JavaLibrary

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.0/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 10s

Upgraded plugins versions and these errors are gone.
Next error is on apt (annotation processor)
suztomo@suxtomo24:~/gax-java$ ./gradlew clean

FAILURE: Build failed with an exception.

* Where:
Build file '/usr/local/google/home/suztomo/gax-java/gax/build.gradle' line: 21

* What went wrong:
A problem occurred evaluating project ':gax'.
> Could not find method apt() for arguments [com.google.auto.value:auto-value:1.4] on object of type org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler.

The line has
  apt libraries['maven.com_google_auto_value_auto_value']

where dependencies.property has maven.com_google_auto_value_auto_value=com.google.auto.value:auto-value:1.4
https://stackoverflow.com/questions/42441844/annotation-processor-in-intellij-and-gradle/54611475#54611475

assemble works but not build.
suztomo@suxtomo24:~/gax-java$ ./gradlew assemble

> Task :gax-grpc:compileJava
/usr/local/google/home/suztomo/gax-java/gax-grpc/src/main/java/com/google/longrunning/OperationsSettings.java:105: warning: [unchecked] toBuilder() in OperationsSettings overrides <B>toBuilder() in ClientSettings
  public Builder toBuilder() {
                 ^
  return type requires unchecked conversion from com.google.longrunning.OperationsSettings.Builder to B
  where B,SettingsT are type-variables:
    B extends com.google.api.gax.rpc.ClientSettings.Builder<SettingsT,B> declared in method <B>toBuilder()
    SettingsT extends ClientSettings<SettingsT> declared in class ClientSettings
/usr/local/google/home/suztomo/gax-java/gax-grpc/src/main/java/com/google/longrunning/stub/OperationsStubSettings.java:365: warning: [unchecked] build() in com.google.longrunning.stub.OperationsStubSettings.Builder overrides <B>build() in com.google.api.gax.rpc.StubSettings.Builder
    public OperationsStubSettings build() throws IOException {
                                  ^
  return type requires unchecked conversion from OperationsStubSettings to StubSettings<B>
  where B is a type-variable:
    B extends StubSettings<B> declared in method <B>build()
/usr/local/google/home/suztomo/gax-java/gax-grpc/src/main/java/com/google/api/gax/grpc/InstantiatingGrpcChannelProvider.java:267: warning: [unchecked] unchecked call to defaultServiceConfig(Map<String,?>) as a member of the raw type ManagedChannelBuilder
      builder.defaultServiceConfig(loadBalancingConfig);
                                  ^
  where T is a type-variable:
    T extends ManagedChannelBuilder<T> declared in class ManagedChannelBuilder
/usr/local/google/home/suztomo/gax-java/gax-grpc/src/main/java/com/google/api/gax/grpc/InstantiatingGrpcChannelProvider.java:297: warning: [unchecked] unchecked call to intercept(List<ClientInterceptor>) as a member of the raw type ManagedChannelBuilder
      builder.intercept(interceptorProvider.getInterceptors());
                       ^
  where T is a type-variable:
    T extends ManagedChannelBuilder<T> declared in class ManagedChannelBuilder
4 warnings

> Task :gax-httpjson:compileJava
/usr/local/google/home/suztomo/gax-java/gax-httpjson/src/main/java/com/google/api/gax/httpjson/ApiMethodDescriptor.java:53: warning: [unchecked] unchecked conversion
    return new AutoValue_ApiMethodDescriptor.Builder();
           ^
  required: com.google.api.gax.httpjson.ApiMethodDescriptor.Builder<RequestT,ResponseT>
  found:    com.google.api.gax.httpjson.AutoValue_ApiMethodDescriptor.Builder
  where RequestT,ResponseT are type-variables:
    RequestT extends Object declared in method <RequestT,ResponseT>newBuilder()
    ResponseT extends Object declared in method <RequestT,ResponseT>newBuilder()
/usr/local/google/home/suztomo/gax-java/gax-httpjson/src/main/java/com/google/api/gax/httpjson/ApiMessageHttpRequestFormatter.java:91: warning: [unchecked] unchecked cast
        for (Object val : (List<Object>) paramValue) {
                                         ^
  required: List<Object>
  found:    Object
2 warnings

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.0/userguide/command_line_interface.html#sec:command_line_warnings

BUILD SUCCESSFUL in 2s
9 actionable tasks: 9 executed

suztomo@suxtomo24:~/gax-java$ ./gradlew build
> Task :verifyGoogleJavaFormat FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':verifyGoogleJavaFormat'.
> Could not resolve all files for configuration ':googleJavaFormat1.6'.
   > Cannot resolve external dependency com.google.googlejavaformat:google-java-format:1.6 because no repositories are defined.
     Required by:
         project :

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Resuming this. Tried ./gradlew wrapper --gradle-version 5.0 and failed:
FAILURE: Build failed with an exception.

* Where:
Build file '/Users/suztomo/gax-java/build.gradle' line: 103

* What went wrong:
A problem occurred evaluating root project 'gax-java'.
> org.gradle.api.internal.java.JavaLibrary.<init>(Lorg/gradle/api/artifacts/PublishArtifact;Lorg/gradle/api/artifacts/DependencySet;)V

Execution failed for task ':gax:compileJava'.
> Cannot specify -processorpath or --processor-path via `CompileOptions.compilerArgs`. Use the `CompileOptions.annotationProcessorPath` property instead.

With https://github.com/googleapis/gax-java/pull/1002 CI failure, now I know that Gradle 5 requires Java 8 runtime.

Minimum java version to build and run gax-java is Java 7. We can't upgrade gradle to versions which require java8+ to run. Once (if?) gax-java minimum version is upgraded to Java 8, the gradle version and plugins will be updated as part of that process.
Closing this bug. Please feel free to reopen if you disagree with the rationale above.


Support read-only queries.

#52 will need read-only support first in order to also support best-effort queries.

All set with #58

Awesome, we can close this issue then @danielmai ?

Added in 65d45150cf338a2126960e71179d6c9c3c6c4d51


Add test case to verify non-exist spill file deletion won't fail query

@xiaoxmeng Looks good % CI failures.

Thanks for the quick review. Updated.


Fix CircleCI build

This is green, can I get a review ?

This was part of https://github.com/bpfkorea/agora/issues/269


Test kubos file-service with large file uploads

See if we can reproduce the failure and identify any improvements to the code.

Tracked elsewhere


GaloisLFSR: Note on taps === LSb-to-MSb polynomial

Also fixed a README link issue in CONTRIBUTING.md

Related Issue: https://github.com/chipsalliance/chisel3/issues/2483

Due to shifting towards LSb, the polynomials are currently implemented with a LSb to MSb notation
Most scrambling polynomials are notated MSb-to-LSb
This can lead to user trouble.
It's still confusing even with the note, but I hope it helps. (The notation for these polynomials is a mess everywhere)

I don't think anyone cares about this quirk in the notation for the FibonacciLFSR.
AFAIW, the GaloisLFSR is the only one used to implement specific scrambling polynomials.
A more proper fix requires left shifting since the Seq of Bools is MSb to LSb (need to shift towards MSb).
I triple-checked this and I'm ~95% sure I have MSb to LSb the right way around. I still appreciate someone quadruple-check ing me before merge.
Contributor Checklist

[ ] Did you add Scaladoc to every public function/method?
[ ] Did you add at least one test demonstrating the PR?
[ ] Did you delete any extraneous printlns/debugging code?
[ ] Did you specify the type of improvement?
[ ] Did you add appropriate documentation in docs/src?
[ ] Did you state the API impact?
[ ] Did you specify the code generation impact?
[ ] Did you request a desired merge strategy?
[ ] Did you add text to be included in the Release Notes for this change?

Type of Improvement

API Impact

Backend Code Generation Impact

Desired Merge Strategy

Release Notes

Reviewer Checklist (only modified by reviewer)

[ ] Did you add the appropriate labels?
[ ] Did you mark the proper milestone (Bug fix: 3.4.x, [small] API extension: 3.5.x, API modification or big change: 3.6.0)?
[ ] Did you review?
[ ] Did you check whether all relevant Contributor checkboxes have been checked?
[ ] Did you do one of the following when ready to merge:

[ ] Squash: You/ the contributor Enable auto-merge (squash), clean up the commit message, and label with Please Merge.
[ ] Merge: Ensure that contributor has cleaned up their commit history, then merge with Create a merge commit.

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

I'll ping @seldridge.
My understanding summarized: the shift for the multiplication of the Galois Polynomial is towards the msb when using MSb-to-LSb notation.

Yeah, I think that's a good practice to get into with PRs. I figured I'd fix that link since it's a small change, but I've now separated the two changes. That PR is now #2596
The main goal of this PR is to add some a note to help #2483 while I find time to work on a more permanent patch.


Organize imports breaks the app

Does this issue occur when all extensions are disabled?: Not sure

VS Code Version: 1.91.1 (Universal)
OS Version: Darwin arm64 23.5.0

Version: 1.91.1 (Universal)
Commit: f1e16e1e6214d7c44d078b1f0607b2388f29d729
Date: 2024-07-09T22:07:54.982Z
Electron: 29.4.0
ElectronBuildId: 9728852
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Darwin arm64 23.5.0

Steps to Reproduce:

create a Node app that uses env variables and external packages also using env variables
install dotenv npm package
in your app index file import dotenv/config and your external package(s) that need env variables too

import 'dotenv/config'
import { func-that-needs-env-vars } from '@org/external-using-env-vars'
import { func2 } from '@org/external-2'
import express, { type Express, type Request, type Response } from 'express'
import http from 'http'

Note: that importing dotenv has to be first, before importing externals
4. Organize imports using VS code feature
Note: that order was changed and import 'dotenv/config' is now after externals from @org scope
5. run your app
Solution:
import 'dotenv/config' or require('dotenv').config() has to be on first line

Can you use the typescript.preferences.autoImportFileExcludePatterns setting to deal with this?

You can place the dotenv import on is own separated from the other imports:
import 'dotenv/config'

import { func-that-needs-env-vars } from '@org/external-using-env-vars'
import { func2 } from '@org/external-2'
import express, { type Express, type Request, type Response } from 'express'
import http from 'http'

Organize will sort within these groups  but not move dotenv into the other imports


Gen 1: Fix move incompatibilities involving Gen 2 event Pokémon

Lovely Kiss+Double-Edge Snorlax, Rock Throw+Substitute Aerodactyl, Growth+Substitute eeveelutions, etc.

This was fixed for Gen 1 Tradebacks and more (critically) importantly on Gen 2 for the Gen 2 OU format on: https://github.com/Zarel/Pokemon-Showdown/commit/3bd4c0649e8239f0a33497d3c524935f8bac1770 and https://github.com/Zarel/Pokemon-Showdown/commit/5a7c3e103b5bbbade0118f75b01af2ba194490b9
(Basically it was sourcesBefore to 2 for those moves).


[Proposal] Support changing keyboardInputType

Can you add the ability to change the keyboard input type? e.g.  textCapitalization: TextCapitalization.sentences, and other.

Looks like a valid proposal to me, You are welcome to send a PR if you are interested if not I will definitely fix it.

This is available in searchfield: ^0.6.2 https://pub.dev/packages/searchfield/changelog
Closing as fixed.


file upload doesnt work

im going to upload file with useform
https://inertiajs.com/file-uploads
but when i select a file i have error in console
im useing in latest version

it have problem when i use
e.target.files[0]
i appreciate if help me

i use this and i got this errors
https://reactjs.org/docs/error-boundaries.html
Something went wrong.
InvalidStateError: An attempt was made to use an object that is not, or is no longer, usable
input
form
ErrorBoundary@http://<IP_ADDRESS>:5173/resources/js/Pages/Admin/Setting/Content/Menu/Create.jsx?t=1659492122945:21:5
Create@http://<IP_ADDRESS>:5173/resources/js/Pages/Admin/Setting/Content/Menu/Create.jsx?t=1659492122945:101:14
s@http://<IP_ADDRESS>:5173/node_modules/.vite/deps/@inertiajs_inertia-react.js?v=10d4c900:741:16


Articulate Markdown and Articulate Theme Picker DataTypes throw an Exception

After installation of Articulate first things were fine, but after pushing that installation to our git repository and retrieving it in a new repo copy, Articulate is broke in the sense that 2 Articulate DataTypes cannot be resolved and are leading to other errors. Other Articulate DataTypes work. Umbraco Backend is the same in both cases.
Could someone please point us in the right direction?
Errors from the Umbraco Backend: https://pastebin.com/YtTVWx70
Umbraco Version: 7.5.8

This is something related to your environment and how you are deploying, not Articulate.
You can see in the stack trace:
 System.InvalidOperationException: Could not find property editor with alias Articulate.MarkdownEditor

which means you haven't deployed the Articulate DLLs and/or the App_Plugins/Articulate folder to the destination since it cannot find this property editor

Thanks, the dll's were missing.


Add empty state to Dataplane policies tab

Description
Add an empty state to the Dataplane policies tab if there are no policies matching.

Also check column widths. Long matchers blow out column.


Fine-tuning CLIP for image object detection.

Thank you for publishing such great research and the implementation! This is more of a question rather than an issue per se.
I have used the image encoder of CLIP in the to encode video frames for video action classification. I used it as a frozen backbone and it outperformed all other backbones I was using (ViT being the second best).
Now, I would like to use it again as a backbone for image object detection. This time however, I would like to fine-tune it while training the rest of the model. The dataset I have contains around 200K images. I would like to ask if you think fine-tuning would be feasible in this case since the task I will be fine-tuning on will be quite different than the original task it was trained on.
I am supposing that a lower learning rate (than the one used for the rest of the model), a lower weight decay value and a late start of fine-tuning would be necessary in this case. Any other advice for fine-tuning in this case would be more than welcome :)

could you share the way you implement the clip image_encoder as backbone?


Compiler generates non compiling code (Java)

I tried it with the downloaded compiler and this colf file:
package asdf
type PrimArraysColfer struct {
id    []uint64
time    []uint64
valueInteger    []int32
valueInteger64    []int64
valueFloat    []float32
valueDouble    []float64
}

Number arrays are on the TODO list. The compiler's error reporting could use an upgrade though. ^_^

Floating point lists are done now @jschneider.


Create setupAndVerifyJDK.md

@Hilmerc We need similar PR for the exercise-solutions branch
Sorry for the delay in reviewing the PR.

Also, consider translating for the other branches i.e. maven-version and ant-version


Add VLAN app to tag or untag packets

Andy Wingo wrote this as part of the lwAFTR but I think it's a useful
component on its own so I'm submitting it for upstreaming.
Maybe this is moot if the lwAFTR is upstreamed but I think it's more
elegant to have this as another app anyway! :)

The lwaftr has basically been upstreamed - see https://github.com/SnabbCo/snabbswitch/pull/784 for details.
I'm happy to be the upstream for this PR, unless @eugeneia wants to be. @eugeneia , preferences/review/thoughts?

@kbara heh, src/apps/lwaftr/vlan.lua isn't there so it wasn't upstreamed enough ;)
Would you agree that it's better to put this as a separate app though? It's a fairly generic component and I think it's much cleaner if it's not inside the directory of a more specific application. I suppose lwaftr should start using this one as well instead of packing its own.

It's only in next, so we'll hopefully see it in the April release, which will be quite soon. :-)
I'm quite happy to have the vlan tagger/untagger as separate apps, but I'd like @eugeneia and/or @lukego to chime in and ack/nack it as well.

So I made something rather embarrassing and included some debug print statements that I had used before. Squashed that away :)

Is there any measurement of the performance impact of the tag/untag functionality?

I can write a selftest for that or at least run some tests.
In general, do we want performance tests as part of selftest() ?

@plajjan You could add a benchmark to program/snabbmark/, this is the place where we are currently collecting various micro benchmarks.
@kbara I would assume that this app is generally useful, so from my point of view it makes sense to have it as an independent app.
@plajjan Since this app is already in next in form of src/apps/lwaftr/vlan.lua I would like to wait for it to land on master (ETA: early next week), and then have the changes needed to move src/apps/lwaftr/vlan.lua to `src/apps/vlan/`` appended to this PR. Does that sound sensible?

@eugeneia sure, that makes sense. Since that is a completely different change from a git perspective I think we better discard this PR and open a new one.
@nnikolaev-virtualopensystems I wrote a quick perftest as a selftest, given @eugeneia feedback I guess it should go into snabbmark instead but anyway, here goes:
kll@lingloi320 ~/kod/snabbswitch/src $ make && sudo ./snsh -t apps.vlan.vlan
LUA       obj/apps/vlan/vlan_lua.o
LINK      snabb
BINARY    2,1M snabb
Effective rate - baseline: 65345535.0 Mpps
Effective rate - Tagger  : 40018680.0 Mpps
Effective rate - Untagger: 26598030.0 Mpps

This is on my laptop (Intel(R) Core(TM) i7-3687U CPU @ 2.10GHz but turboboost..). The perf drop is quite big but the relative difference seems smaller when used in a more realistic program. Like if pcapreader & repeater is used instead of Source I get:
kll@lingloi320 ~/kod/snabbswitch/src $ make && sudo ./snsh -t apps.vlan.vlan
LUA       obj/apps/vlan/vlan_lua.o
LINK      snabb
BINARY    2,1M snabb
Effective rate - baseline: 37955730.0 Mpps
Effective rate - Tagger  : 27742470.0 Mpps
Effective rate - Untagger: 20868690.0 Mpps

Anyway, since we'll be using the one from lwaftr I'll close this PR now.


Create missing intermediate pathname components for new folders

VSCode Version: 1.9.1
OS Version: MacOS 10.12.3

This is a small feature request that would be useful when creating a new folder from the Explorer tab.
Steps to Reproduce:

Go to the Explorer (View menu → Explorer)
Click on the New folder button
Type a name like folder/subfolder

Result: an error message like The name folder/subfolder is not valid is shown.
Expected result: the folder subfolder could be created inside the folder folder.
Notes:

What I am describing here would be the equivalent of the Unix mkdir -p command
SublimeText works this way when creating folders.

This issue has already been reported. Please use the search function next time before reporting an issue and/or this time if you are curious about the progress of the issue.

@bpasero I did it and couldn't find it unfortunately (and still can't).

https://github.com/Microsoft/vscode/issues/10967 https://github.com/Microsoft/vscode/issues/1169 https://github.com/Microsoft/vscode/issues/12893

Indeed, thanks. In the meantime I found this extension: https://github.com/dkundel/vscode-new-file


FAST API to Request Spotify Cluster

2OAuth with Spotify
Download selected playlist songs
Use clustering model
Response the result
Create playllist in spotify

Unfortunaltely Spotify deprecated the API Audio features on 27th November
https://developer.spotify.com/blog/2024-11-27-changes-to-the-web-api


chore: move ingress-nginx to galoy-deps

Moved over the ingress charts and config from galoy-infra, but in the current state getting hit by the error:
╷
│ Error: Failed to determine GroupVersionResource for manifest
│
│   with module.galoy_deps.kubernetes_manifest.issuer,
│   on galoy-deps/ingress.tf line 47, in resource "kubernetes_manifest" "issuer":
│   47: resource "kubernetes_manifest" "issuer" {
│
│ no matches for kind "ClusterIssuer" in group "cert-manager.io"
╵
make: *** [Makefile:18: deploy-services] Error 1

Moved over the ingress charts and config from galoy-infra, but in the current state getting hit by the error:
╷
│ Error: Failed to determine GroupVersionResource for manifest
│
│   with module.galoy_deps.kubernetes_manifest.issuer,
│   on galoy-deps/ingress.tf line 47, in resource "kubernetes_manifest" "issuer":
│   47: resource "kubernetes_manifest" "issuer" {
│
│ no matches for kind "ClusterIssuer" in group "cert-manager.io"
╵
make: *** [Makefile:18: deploy-services] Error 1

Right that's because the ingress chart uses a CRD. Because of the way the provider works, we cannot do the installation in one go, we need to first install the chart (which will install the CRD) and then the CR.

The problem still persists, but there are two kind of hacky solutions suggested here: https://stackoverflow.com/questions/69765121/how-to-avoid-clusterissuer-dependency-on-helm-cert-manager-crds-in-terraform-pla


Compile sdk with java target to 1.7

In continue to #3 issue: at the moment sdk available on maven central is working only at java 1.8+.
Is it possible to configure CI to build with java target 1.7?

Hi @Tapac, I'll update the build file to get it to target 1.7.


Not support doc format

Confirm this is an issue with the Python library and not an underlying OpenAI API

[x] This is an issue with the Python library

Describe the bug
OpenAI Docs:

Python library:

To Reproduce
Use Files API to Upload doc file，and use "assistants" for Assistants
Code snippets
No response
OS
Ubuntu
Python version
Python v3.10.12
Library version
openai v1.51.0

Thanks for the report, can you share an example snippet to reproduce the issue?

OK，I will share an example snippet later.

Thanks for the report, can you share an example snippet to reproduce the issue?

OK，I will share an example snippet later.

Thanks for the report, can you share an example snippet to reproduce the issue?

`
import openai,io
import requests
openai.api_key = "xxxxxxxxxxxxxxxxxxx"
class FileLike(io.BytesIO):
def init(self, _bytes, filename=None):
super().init(_bytes)
self.name = filename
url = "https://ccrb.s3.cn-northwest-1.amazonaws.com.cn/绳舞飞扬活力绽放.doc"
r = requests.get(url)
fileName = url.split("https://ccrb.s3.cn-northwest-1.amazonaws.com.cn/")[1]
bytes_io = io.BytesIO(r.content)
file_bytes = bytes_io.read()
res = openai.files.create(
file=FileLike(file_bytes, fileName), purpose="assistants"
)
if res.id and res.status == "processed":
file = openai.files.retrieve(res.id)
print(file)
`


Chore: Remove docs from repository

Description
Documentation has been moved to own repository: https://github.com/vite-pwa/docs
Linked Issues
None
Additional Context
None

Superseded by https://github.com/vite-pwa/vite-plugin-pwa/pull/791