Backporting - PR #103 from master - Adding feature for topic regex patterns and also decorate events

Merging changes made in master and other non conflicting useful ones to api-v1 branch which uses kafka 0.9.

Wasn't right, will recreate.


Why are you eliminating the influence of positional information on modalities using RoPE?

In your implementation, you're removing the positional information for modalities within Transfusion using the derive_rotary_positions_from_modality_positions function.
In the Transfusion paper, information about positional encoding is only briefly mentioned in footnote 4 on page 5. However, basic models like VisionTransformer typically apply positional information to patched images.
Is this implementation of modality intended to be a generalized set for continuous data, leaving the adaptation for specific data types such as images or audio to us as users?

oh, or maybe you are working with raw data reshaped into tokens?

@lucidrains
Thank you for your reply!!!
I'm currently working on implementing adaptation for motion data. So, without questioning previous research, I assumed that positional embeddings should be applied to motion data in Transfusion as well. Although not within the scope of my research, I had similar assumptions for images, audio, and video data.
If I understand correctly, you're suggesting that, regardless of the Transfusion research, models can implicitly learn positional information during the training process as a general principle.
This is a very interesting topic.
Considering image understanding learning, for example, I agree that the model could potentially grasp the positional relationships between patches from vast amounts of training data, even without explicitly providing PE (Positional Encoding).
I think the crucial point is the difference in results on benchmarks. Even if a model can solve benchmark tasks to some extent without PE, people definitely choose to provide PE if it clearly improves accuracy.
I don't know of any specific papers supporting this, though.
I know that this doesn't provide a definitive answer to whether PE is truly necessary or not.
It's a complex topic that likely requires further research and discussion...

@shin-wn if your autoencoder has a few convolutions in there, the network learns the absolute positions from the padding
https://arxiv.org/abs/2102.10882 and plenty of other papers

@shin-wn but again, i could think about automatic injection of axial positional embeddings based on the shape of the modality. maybe give me until end of the week
how many dimensions is your motion data?

@lucidrains Thank you for sharing your knowledge and the paper!
Regarding motion data: it has a shape of (num_frames, 263), where each frame is treated as one token on transformer-based diffusion model. So I have num_frames tokens, each with 263 dimensions.

@shin-wn hey Shinichi, sorry for the delay
will get this wrapped up by wednesday

@shin-wn hey Shinichi, made a first pass through the logic this morning
you can try it out on the latest version with this flag turned on, and setting modality_num_dim with the appropriate number of dimensions (for your motion case, it will be 1 for time)

@lucidrains
wow...
Thank you so much!!!
You've made it possible to set any Positional Encoding for various modalities while still applying only Rotary Embedding to text. This is greatly appreciated!!!

@shin-wn you got it! let me know if you run into any 🐛, and hopefully by week's end things are solid

was actually reading https://arxiv.org/abs/2406.10322 and hoping to apply that here, but was uncertain how to keep two continuous modalities from interacting in the same batch. absolute axial positions it is

I am implementing  diffusion model based transfusion, not your flow matching implementation.
It will take some time for me to produce results that are free of implementation misses with my implementation skills...


fixing the stargate key-value scenarios

Fixing of the Stargate Docs API key-value scenario. Multiple things are done here:

rw_key is set to uniformly go up to keycount only. This means that we read up to the elements inserted with seq_key.
However, since ramp-up cycles were in default scenario lower that keycount, I actually made those two equal, so default scenario writes 10M in he rampup and then read those 10M in the main.
added delete table in schema, to clear-up any possible documents before the test (if exists)
accept 404 on read, because you could say keycount=100 rumpup-cycles=80. This would mean write 80 docs, but target 100 in reads, meaning 20% misses; so we can design tests to have some percentage of the misses as well
made read and write rating to 5 each, as in the original key-value cql scenario
named steps in default scenario for easier metrics correlation

@EricBorczuk Any chance you can fix other Stargate key-value activities following these changes?
@dougwettlaufer FYI

@ivansenic yes, will handle the other cases - thanks for doing this!

@ivansenic This PR is still in draft stage. Are you ready for it to be merged?

@jshook yep ready for merging..


APPSRE-8660 adjust schema for more self-service

We need to accommodate for 2 token:

the bootstrapAPIToken is used to generate new API tokens for HS
the automationAPIToken is used by app-interface automations to interact with dynatrace API

Note, that none of the tokens is required. I.e., a dynatrace environment is not necessarily tied to a HS region and/or app-interface automation.
Further, we remove the region enum, as onboarding a new region requires a change to the schema which is not self-servicable.

Changing the scope of this change:

remove enum for better self-service
add description to bootstrapToken field

Our current automation does not use dynatrace-environment-1 to get the token - it is setup directly through openshiftResources. Once we enhance our automation, we might also change the token structure here at a later point.


Add Create: Steam 'n' Rails

Suggested by Nettle.

Should be a fine enough addition, I shall test it.


Malicious IPA stalls with non-relaxed DP parameters

Here is a draft run that reproduces the issue. It seems similar to stalls we're observing in aggregation where validate_record requires all futures to be spawned in order to make progress. Instead we're getting one future at a time and we stall.
Non relaxed DP generates more records, making it more likely to hit the stall issue. @danielmasny is currently looking for a place inside DP generation where it could be happening

I believe this is a duplicate of #1300.


Packages for openSUSE or RPMs in general

As asked in #28793 I am opening this new thread here.
CC @athomas
I am an openSUSE Community member in this post and not speaking for SUSE, please keep that in mind.

Currently if you are using software in some kind we have the concept of packages. On my local openSUSE Tumbleweed system I would expect be able to install any application via:
zypper in some-awesome-dart-software

This is currently not possible because the whole ecosystem for dart is not packaged on openSUSE. We have some great tooling for Python PyPi Packages and the packaging of rubygems is nearly fully automated as well. Go is also basically solved and C/C++ packaging is solved longer then I am currently old.
If using and IDE or advanced editor of any kind it will look in $PATH most probably for the dart sdk. To add any program to $PATH normally as a linux distro user I would expect my package manager to have it available for me. This means that we need packages in the different distros submitted. Additionally this would mean we could profit from security backports for stable release distros (like openSUSE Leap).

Currently I see the following on the TODO list of anyone working on this:

Write documentation for who to build the required parts from source
Package all dependencies so dart can be built to an RPM
Write a specfile for a single distro.
From personal experience I do not recommend writing a cross distro specfile since this is getting very very complicated very fast
Optional: Submit the specfile and the sources to a distribution like openSUSE Tumbleweed.

For testing the full thing I would recommend the openSUSE Build Service since it is able to build RPMs, DEBs and more in a single project. As an example I will link in the following the development project for the openSUSE Build Service CLI which builds for a ton of distros at the same time: https://build.opensuse.org/package/show/openSUSE:Tools/osc
If there are more questions to what I am suggesting I am more then happy to answer them. I have decided to start working on this since for me it is currently impossible to develop a flutter android application on my machine (my system is snap free).

Last but not least: If anyone working at Google is interested that Dart is officially supported on SUSE Linux Enterprise I can try to get the right people in touch with each other but I am not the right person to drive such an effort. I am suggesting this because recently openSUSE Leap 15.3 and SLE got binary identical. This means anyone who runs openSUSE Leap 15.3 can get a subscription and convert his system with a few steps into SLE. If dart packages would be a SUSE supported thing this could increase the adoption of Dart possibly.

@SchoolGuy We already have https://build.opensuse.org/project/show/devel:languages:dart for this. So let's coordinate our efforts.

@jubalh Okay this was not there last time I checked. :) Indeed this is good. Since I see that this is empty where can I help and how?

Okay this was not there last time I checked.

I requested in months ago but admins needed several pings until it was finally created.

Since I see that this is empty

It is empty because I waited for python2 issue to be resolved which was only the case yesterday ;)
So now we will follow their build instructions and create a package for dart.

Very cool, let me know if you need any support from the Dart side. The python3 migration has just landed, there may still be problems in some scripts (especially when deviating from the "happy path", e.g. in exception handlers and when the default locale is something other than UTF-8).

@athomas I only had limited time today so I only took a quick look at the build instructions in the wiki. In our build environment we won't have access to the internet. So we need to get all compressed files in advance. It seems like some scripts except to have a working internet connection or am I mistaken?

I will also make myself familiar with the build tomorrow.
@jubalh would you like to have a call on meet.opensuse.org tomorrow? Or what day and time would suit you?

There's quite a few things that will attempt to make network connections if you follow the developer instructions. In particular depot_tools needs a network connection to provision various build tools and gclient sync is needed to fetch sources and tooling outside the Dart SDK repo. After a gclient sync it should be possible to build offline. However, we share a lot of infrastructure with chromium via depot_tools, so perhaps some of these issues are already solved for the chromium package.
One thing that might be tricky here is that you need a Dart SDK to build a Dart SDK (normally, this is the checked-in Dart SDK provisioned by gclient sync).

@athomas If my eyes don't betray me we are not using gsync for building Chromium? - https://build.opensuse.org/package/view_file/network:chromium/chromium/chromium.spec?expand=1

@SchoolGuy The magic might be happening in this line:
Source0:        https://commondatastorage.googleapis.com/chromium-browser-official/%{name}-%{version}.tar.xz

Looks like a source tarball probably generated from a checkout after running gclient sync somewhere else.

Yes but that doesn't explain how the third party stuff is pulled in correctly without a gclient...
I will hang around here so we can brainstorm. - https://meet.opensuse.org/dart

Sorry, I'm about to leave so I won't be able to join your meeting.
But, I think the rough process is probably:

chromium infra checks out their git repo.
chromium infra runs gclient sync.
chromium infra runs a script to package the resulting folder structure with all pulled in stuff into a src tarball.
chromium infra uploads the src tarball.
open suse infra fetches that (it's the result of a gclient sync so it doesn't have to run it)
open suse infra provides all the tooling needed to build from the src tarball (so it doesn't need depot tools because it provides ninja/gn/etc).

Okay then another time. I will have a look if I can get things running. But yes I agree that would be also the best option for dart I guess. In theory we could run the gsync locally because everything is a source. Let's see.

We could strip vendored third party stuff and replace it with the normal versions of our packages in a later step. I think we should try to reduce vendoring as much as possibel

Checking out the sources via fetch: 10:20:12 - 10:25:47
Building dart: 10:23:06 - 10:33:32
Build was successful. I think we should have a Constraints file (like Chromium has in the OBS) in regard to CPU cores. My 16 threads were maxed out during the build. RAM was constantly under 8 GiB including my host system. Thus memory should be fine.

https://github.com/dart-lang/sdk/blob/master/tools/create_tarball.py has
partial support for creating a source tarball, but hasn't been updated for
changes in the SDK. So the resulting tarball contains way too much and
probably a lot more than just sources. Locally I was able to quickly reduce
the size by half, but I suspect it still contains way too much. If we get
this in shape we could produce the tarballs on our infra and upload them
together with other release artifacts.
On Sat, 17 Apr 2021, 10:36 Enno G., @.***> wrote:

Checking out the sources via fetch: 10:20:12 - 10:25:47
Building dart: 10:23:06 - 10:33:32
Build was successful. I think we should have a Constraints file (like
Chromium has in the OBS) in regard to CPU cores. My 16 threads were maxed
out during the build. RAM was constantly under 8 GiB including my host
system. Thus memory should be fine.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dart-lang/sdk/issues/45724#issuecomment-821789895,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEYRJB54LMJZRQBVHMQDKUDTJFCA3ANCNFSM43BAADIQ
.

Re: diskspace: a src tarball will be a lot smaller than 14 GiB. We should end up with less than 1 GiB (with some optimizations the tarball has 800MiB locally, but it can be optimized further). A lot of the size comes from the GIT history, the various SDKs like the Android SDK and some of those will not be relevant for building these packages.

@athomas I was not referring to the diskspace for the source tarball but rather the size during build. If I understood the constraints file from Chromium, this is exactly what it is for...

Here's my little process of reducing size. Could someone please enlighten me if it's possible to reduce it even more?
Delete all the .git directories. Interestingly, the .git folder for the root repo cannot be deleted, otherwise the tool will have trouble generating ninja files, which leaves me about 1GB of unremovable space.
ninja -C out/ReleaseX64 create_sdk
ninja: Entering directory `out/ReleaseX64'
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
ninja: error: manifest 'build.ninja' still dirty after 100 tries

BUILD FAILED

For third_party, only the following are required to build:
third_party
├── boringssl
├── devtools
├── icu
├── pkg
├── requirejs
├── root_certificates
├── tcmalloc
└── zlib

Delete buildtools/linux-x64/rust. clang must be kept. Is it possible to use the clang provided by the distribution, or is it possible but not recommended?
build/linux/**-sysroot: are they used during the build? Or are they for creating the source tarball? The build tool gets angry at me if I don't have them, but I'm not sure if they are used.
I tried to symlink both the buildtools/linux-x64/clang and tools/sdks/dart-sdk to my own copies, but it seems that the build tool does some version checking which prohibits me from doing so:
ERROR at //build/config/compiler/BUILD.gn:363:30: Could not read file.
    cipd_version = read_file(toolchain_stamp_file, "json")
                             ^-------------------
I resolved this to "/whatever/sdk/buildtools/linux-x64/clang/.versions/clang.cipd_version".
See //build/config/BUILDCONFIG.gn:233:3: which caused the file to be included.
  "//build/config/compiler:compiler",
  ^---------------------------------
Command failed: /whatever/sdk/buildtools/gn gen out/ReleaseX64 --args=target_os="linux" host_cpu="x64" target_cpu="x64" dart_target_arch="x64" dart_use_compressed_pointers=false dart_use_crashpad=false dart_snapshot_kind="app-jit" dart_use_fallback_root_certificates=true bssl_use_clang_integrated_as=true dart_use_tcmalloc=true dart_use_mallinfo2=false is_debug=false is_release=true is_product=false dart_debug=false dart_runtime_mode="develop" exclude_kernel_service=false is_clang=true dart_vm_code_coverage=false is_asan=false is_lsan=false is_msan=false is_tsan=false is_ubsan=false is_qemu=false dart_platform_sdk=false dart_stripped_binary="exe.stripped/dart" dart_precompiled_runtime_stripped_binary="exe.stripped/dart_precompiled_runtime_product" gen_snapshot_stripped_binary="exe.stripped/gen_snapshot_product" dart_use_debian_sysroot=true use_goma=false goma_dir="None" verify_sdk_hash=true
ninja -C out/ReleaseX64 create_sdk
ninja: Entering directory `out/ReleaseX64'
[0/1] Regenerating ninja files
ERROR at //build/config/compiler/BUILD.gn:363:30: Could not read file.
    cipd_version = read_file(toolchain_stamp_file, "json")
                             ^-------------------
I resolved this to "/whatever/sdk/buildtools/linux-x64/clang/.versions/clang.cipd_version".
See //build/config/BUILDCONFIG.gn:233:3: which caused the file to be included.
  "//build/config/compiler:compiler",
  ^---------------------------------
FAILED: build.ninja
../../buildtools/gn --root=../.. -q --regeneration gen .
ninja: error: rebuilding 'build.ninja': subcommand failed
BUILD FAILED

Hi I'm new to OpenSUSE and I aslo would like to have dart installed

Hello good people. Is there any update on this?

Is there any update on this?

Not on the opensuse side.

I've installed homebrew, and then dart using brew and flutter using fvm. Not the ideal, but works fine, and then I changed the path in Intellij settings and everything worked


Store Attestations into an AttestationPool

What is wrong?
Much like we introduce a block pool in #465, we will need a local pool of the Attestations we have seen from other validators.
How can it be fixed

Extend the p2p layer to accept gossiped Attestations.
Store the Attestations in some kind of in-memory cache, the pool.
Remove attestations from the pool once they have been included on chain -- this should happen after the state transition but before the (post-block) fork choice!
[optimization] index the attestations by validator index
[optimization...?] persist attestations to disk (into the ChainDB).

(2) is required to resolve this issue.
(3) can happen after (2) is in place and integrated into the node software
(1) can happen after (2) and (3). (4) and (5) are some optimizations to think about, possibly after we have completed (1-3).

Remove attestations from the pool once they have been included on chain -- this should happen after the state transition but before the (post-block) fork choice!

Curious about why "before post-block fork choice"

@NIC619 i think i misspoke -- the intention was to be careful to not exclude any attestations from the fork choice but i don't think what i wrote makes sense...
what we want: we have some attestations in the pool, we get a valid block and produce a new state. the attestations now on-chain should be removed from the pool; we should now run the fork choice using the on-chain attestations, along with this latest state of the attestation pool

Thanks @ralexstokes ! This makes total sense to me.


Add  kubelet-preferred-address-types=InternalIP in metrics-server

What this PR does / why we need it:
Fix issue that metric-server can't scrape metrics of node in Alicloud.
Which issue(s) this PR fixes:
Fixes # https://github.com/gardener/gardener-extension-provider-alicloud/issues/39
Special notes for your reviewer:
It is not possibe to implement a webhook to change the deployment of metrics-server. Because the deployment is managed by gardener resource manager.
Release note:

Metrics-server can scrape node's metrics now.

Why do we do this in g/g globally? I guess it’s rather something specific to Alicloud.
Option 1. Alicloud provider extension webhook changes the metrics server deployment, the resource manager will reconcile it back. As the result, the pod will be destroyed and started again and agiain.
Option 2. Alicloud provider extension webhook changes the secret managedresource-shoot-core. It is not easy to change it because the key of the data is not intuitive and it is not maintainable.

The currently one always works on  all hyperscalers.

Option 1. Alicloud provider extension webhook changes the metrics server deployment, the resource manager will reconcile it back. As the result, the pod will be destroyed and started again and agiain.

That's wrong, see https://github.com/gardener/gardener/blob/master/docs/extensions/shoot-webhooks.md. If you have a webhook on the metrics-server Deployment then it will not be reconciled back. It will always be injected.

The currently one always works on all hyperscalers.

I'm fine changing it in general here in g/g, however, we need some confidence.

That's wrong, see https://github.com/gardener/gardener/blob/master/docs/extensions/shoot-webhooks.md. If you have a webhook on the metrics-server Deployment then it will not be reconciled back. It will always be injected.

OK. I made a mistake :)

I am not sure, if this is still something the committer wants to have added globally, we will try it out. But maybe he is already convinced to implement this as a provider extension webhook?

@jia-jerry can you outline your plans? :)

@jia-jerry can you outline your plans? :)

I will change it in the extension. Let's keep the defaut setting of the metrics server. Will close it. Thank you.

FYI: https://github.com/gardener/gardener/pull/2468


How to turn a connecting line from curved to straight?

The connecting lines between nodes are curved.
How do I set them to a 90 degree right angle?
Is this configurable?

Yes, chart.linkGroupArc is responsible for that
https://github.com/bumbeishvili/org-chart/blob/c8ebb0490ecfcf1424c16a8528a4a835d3efde53/src/d3-org-chart.js#L96
This is how it's invoked
https://github.com/bumbeishvili/org-chart/blob/c8ebb0490ecfcf1424c16a8528a4a835d3efde53/src/d3-org-chart.js#L776
I think you can play with linkHorizontal here.
https://observablehq.com/@d3/collapsible-tree

I'm really sorry, but I've tried various things,
I don't know how to do it.
This is my situation.
Without using npm.
I downloaded and use .js myself.
js file list

d3.js
https://d3js.org/d3.v7.min.js
d3-org-chart.js
https://cdn.jsdelivr.net/npm/d3-org-chart@2
d3-flextree.js
<EMAIL_ADDRESS>
therefore
https://realtimehtml.com/
Could you tell me as an example on this site?

I changed it as above, but it doesn't seem to apply.
Is there anything else I should apply?

We have 2 kinds of different connections, I thought you were referring to similar connections

looks like you just want to change the link curvature in  here (this is v3 org chart version)
https://github.com/bumbeishvili/org-chart/blob/279153efe64de34f011db458f7f2655884a2fef0/src/d3-org-chart.js#L218C57-L218C126
Here is how modified version will look when pasted at https://realtimehtml.com

Here is the code


Fix error checking for pod name & NS

Previously it would just check if POD_NAME or POD_NAMESPACE was set, which
could lead to very bizarre failure modes.

This change is

Coverage remained the same at 44.342% when pulling ad583c3acbeb64fbfa9e89a15b04459bc61b34e0 on claytononeill:fix-env-var-error-checks into d416d029ecc3caa8eea3a0f368ba5f2399bf9071 on kubernetes:master.

/lgtm

@claytononeill thanks!


Remove statics required for task until spawning

This allows embedding tasks in other types without them needing to be
static until spawn is called.

I don't think this is sound. It would allow you to allocate a task, spawn it, then deallocate it, leaving dangling pointers in the executor and wakers. The 'static bounds prevent that.
What issue are you trying to solve?

I don't think this is sound. It would allow you to allocate a task, spawn it, then deallocate it, leaving dangling pointers in the executor and wakers. The 'static bounds prevent that.

I was afraid you were going to say that :) I have pushed a change which puts back the 'static for the spawning, but removes 'static bound for the Future, which would help a long way. Not sure how that would also be unsound?

What issue are you trying to solve?

I'm basically trying to avoid using the embassy::task macro, because it simplifies spawning the Actor tasks. In my case, I know the actors are static when spawning, so keeping spawn() 'static would be fine. Example here: https://github.com/lulf/embassy/blob/embassy-taskwork/embassy-std-examples/src/bin/tick.rs#L64

@Dirbaio Ok, I think I understand the issue you're hinting at better: the Task F: Future must be static, otherwise it means the held Future could be deallocated while being executed.
I have found a way to work around this without trouble, I thought initially this had worse implications than it actually had. Closing this issue, but feel free to reopen if I'm wrong.


authz: remove alpha RBAC CRD

The API will also be removed in https://github.com/istio/api/pull/1427.
#23668

@yangminzhu: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
6b1e091986aa2dd61336d8f302f9b2413155a2d6
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yangminzhu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
6b1e091986aa2dd61336d8f302f9b2413155a2d6
link
/test gencheck_istio

integ-galley-k8s-tests_istio
6b1e091986aa2dd61336d8f302f9b2413155a2d6
link
/test integ-galley-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yangminzhu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
6b1e091986aa2dd61336d8f302f9b2413155a2d6
link
/test gencheck_istio

integ-galley-k8s-tests_istio
6b1e091986aa2dd61336d8f302f9b2413155a2d6
link
/test integ-galley-k8s-tests_istio

release-test_istio
6b1e091986aa2dd61336d8f302f9b2413155a2d6
link
/test release-test_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yangminzhu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
6b1e091986aa2dd61336d8f302f9b2413155a2d6
link
/test gencheck_istio

integ-galley-k8s-tests_istio
6b1e091986aa2dd61336d8f302f9b2413155a2d6
link
/test integ-galley-k8s-tests_istio

release-test_istio
6b1e091986aa2dd61336d8f302f9b2413155a2d6
link
/test release-test_istio

integ-local-tests_istio
6b1e091986aa2dd61336d8f302f9b2413155a2d6
link
/test integ-local-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yangminzhu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-galley-k8s-tests_istio
6b1e091986aa2dd61336d8f302f9b2413155a2d6
link
/test integ-galley-k8s-tests_istio

release-test_istio
6b1e091986aa2dd61336d8f302f9b2413155a2d6
link
/test release-test_istio

integ-local-tests_istio
6b1e091986aa2dd61336d8f302f9b2413155a2d6
link
/test integ-local-tests_istio

gencheck_istio
34fe67319ca37c478cae89a3ccd855ad813dc241
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yangminzhu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
6b1e091986aa2dd61336d8f302f9b2413155a2d6
link
/test release-test_istio

integ-local-tests_istio
6b1e091986aa2dd61336d8f302f9b2413155a2d6
link
/test integ-local-tests_istio

gencheck_istio
34fe67319ca37c478cae89a3ccd855ad813dc241
link
/test gencheck_istio

integ-galley-k8s-tests_istio
34fe67319ca37c478cae89a3ccd855ad813dc241
link
/test integ-galley-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yangminzhu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-galley-k8s-tests_istio
34fe67319ca37c478cae89a3ccd855ad813dc241
link
/test integ-galley-k8s-tests_istio

gencheck_istio
cbffbaf8bac1142dbb5ad4bb538e81622a38774b
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yangminzhu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
cbffbaf8bac1142dbb5ad4bb538e81622a38774b
link
/test gencheck_istio

integ-galley-k8s-tests_istio
cbffbaf8bac1142dbb5ad4bb538e81622a38774b
link
/test integ-galley-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yangminzhu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-galley-k8s-tests_istio
cbffbaf8bac1142dbb5ad4bb538e81622a38774b
link
/test integ-galley-k8s-tests_istio

gencheck_istio
6f418b3a736bc86aae34a30e053df6d083af8538
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yangminzhu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
6f418b3a736bc86aae34a30e053df6d083af8538
link
/test gencheck_istio

integ-galley-k8s-tests_istio
6f418b3a736bc86aae34a30e053df6d083af8538
link
/test integ-galley-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yangminzhu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
6f418b3a736bc86aae34a30e053df6d083af8538
link
/test gencheck_istio

integ-galley-k8s-tests_istio
6f418b3a736bc86aae34a30e053df6d083af8538
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
6f418b3a736bc86aae34a30e053df6d083af8538
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yangminzhu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-galley-k8s-tests_istio
6f418b3a736bc86aae34a30e053df6d083af8538
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
6f418b3a736bc86aae34a30e053df6d083af8538
link
/test integ-pilot-k8s-tests_istio

gencheck_istio
214c1b3259aab168b8eba49f33530fce32af6068
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yangminzhu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
6f418b3a736bc86aae34a30e053df6d083af8538
link
/test integ-pilot-k8s-tests_istio

gencheck_istio
214c1b3259aab168b8eba49f33530fce32af6068
link
/test gencheck_istio

integ-galley-k8s-tests_istio
214c1b3259aab168b8eba49f33530fce32af6068
link
/test integ-galley-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yangminzhu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
214c1b3259aab168b8eba49f33530fce32af6068
link
/test gencheck_istio

integ-galley-k8s-tests_istio
214c1b3259aab168b8eba49f33530fce32af6068
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
214c1b3259aab168b8eba49f33530fce32af6068
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yangminzhu: PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@yangminzhu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
214c1b3259aab168b8eba49f33530fce32af6068
link
/test gencheck_istio

integ-galley-k8s-tests_istio
214c1b3259aab168b8eba49f33530fce32af6068
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
214c1b3259aab168b8eba49f33530fce32af6068
link
/test integ-pilot-k8s-tests_istio

integ-multicluster-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-multicluster-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yangminzhu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
214c1b3259aab168b8eba49f33530fce32af6068
link
/test gencheck_istio

integ-galley-k8s-tests_istio
214c1b3259aab168b8eba49f33530fce32af6068
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
214c1b3259aab168b8eba49f33530fce32af6068
link
/test integ-pilot-k8s-tests_istio

integ-multicluster-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yangminzhu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
214c1b3259aab168b8eba49f33530fce32af6068
link
/test gencheck_istio

integ-galley-k8s-tests_istio
214c1b3259aab168b8eba49f33530fce32af6068
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
214c1b3259aab168b8eba49f33530fce32af6068
link
/test integ-pilot-k8s-tests_istio

integ-multicluster-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test unit-tests_istio

integ-security-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-security-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yangminzhu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
214c1b3259aab168b8eba49f33530fce32af6068
link
/test gencheck_istio

integ-galley-k8s-tests_istio
214c1b3259aab168b8eba49f33530fce32af6068
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
214c1b3259aab168b8eba49f33530fce32af6068
link
/test integ-pilot-k8s-tests_istio

integ-multicluster-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test unit-tests_istio

integ-security-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-security-k8s-tests_istio

release-test_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test release-test_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yangminzhu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
214c1b3259aab168b8eba49f33530fce32af6068
link
/test gencheck_istio

integ-galley-k8s-tests_istio
214c1b3259aab168b8eba49f33530fce32af6068
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
214c1b3259aab168b8eba49f33530fce32af6068
link
/test integ-pilot-k8s-tests_istio

integ-multicluster-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test unit-tests_istio

integ-security-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-security-k8s-tests_istio

release-test_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test release-test_istio

integ-mixer-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-mixer-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yangminzhu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-galley-k8s-tests_istio
214c1b3259aab168b8eba49f33530fce32af6068
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
214c1b3259aab168b8eba49f33530fce32af6068
link
/test integ-pilot-k8s-tests_istio

integ-multicluster-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test unit-tests_istio

integ-security-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-security-k8s-tests_istio

release-test_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test release-test_istio

integ-mixer-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-mixer-k8s-tests_istio

gencheck_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yangminzhu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-galley-k8s-tests_istio
214c1b3259aab168b8eba49f33530fce32af6068
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
214c1b3259aab168b8eba49f33530fce32af6068
link
/test integ-pilot-k8s-tests_istio

integ-multicluster-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test unit-tests_istio

integ-security-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-security-k8s-tests_istio

release-test_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test release-test_istio

integ-mixer-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-mixer-k8s-tests_istio

gencheck_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test gencheck_istio

integ-telemetry-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yangminzhu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-galley-k8s-tests_istio
214c1b3259aab168b8eba49f33530fce32af6068
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
214c1b3259aab168b8eba49f33530fce32af6068
link
/test integ-pilot-k8s-tests_istio

integ-multicluster-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test unit-tests_istio

integ-security-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-security-k8s-tests_istio

release-test_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test release-test_istio

integ-mixer-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-mixer-k8s-tests_istio

gencheck_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test gencheck_istio

integ-telemetry-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-telemetry-k8s-tests_istio

integ-operator-controller-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-operator-controller-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yangminzhu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-galley-k8s-tests_istio
214c1b3259aab168b8eba49f33530fce32af6068
link
/test integ-galley-k8s-tests_istio

integ-multicluster-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test unit-tests_istio

integ-security-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-security-k8s-tests_istio

release-test_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test release-test_istio

integ-mixer-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-mixer-k8s-tests_istio

gencheck_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test gencheck_istio

integ-telemetry-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-telemetry-k8s-tests_istio

integ-operator-controller-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-operator-controller-tests_istio

integ-pilot-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yangminzhu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test unit-tests_istio

integ-security-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-security-k8s-tests_istio

release-test_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test release-test_istio

integ-mixer-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-mixer-k8s-tests_istio

gencheck_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test gencheck_istio

integ-telemetry-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-telemetry-k8s-tests_istio

integ-operator-controller-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-operator-controller-tests_istio

integ-pilot-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-pilot-k8s-tests_istio

integ-galley-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-galley-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yangminzhu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test unit-tests_istio

integ-security-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-security-k8s-tests_istio

release-test_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test release-test_istio

integ-mixer-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-mixer-k8s-tests_istio

gencheck_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test gencheck_istio

integ-telemetry-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-telemetry-k8s-tests_istio

integ-operator-controller-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-operator-controller-tests_istio

integ-pilot-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-pilot-k8s-tests_istio

integ-galley-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-galley-k8s-tests_istio

lint_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yangminzhu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test unit-tests_istio

integ-security-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-security-k8s-tests_istio

release-test_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test release-test_istio

integ-mixer-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-mixer-k8s-tests_istio

gencheck_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test gencheck_istio

integ-telemetry-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-telemetry-k8s-tests_istio

integ-operator-controller-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-operator-controller-tests_istio

integ-pilot-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-pilot-k8s-tests_istio

integ-galley-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-galley-k8s-tests_istio

lint_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test lint_istio

integ-distroless-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-distroless-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yangminzhu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test unit-tests_istio

integ-security-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-security-k8s-tests_istio

release-test_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test release-test_istio

integ-mixer-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-mixer-k8s-tests_istio

gencheck_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test gencheck_istio

integ-telemetry-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-telemetry-k8s-tests_istio

integ-operator-controller-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-operator-controller-tests_istio

integ-pilot-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-pilot-k8s-tests_istio

integ-galley-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-galley-k8s-tests_istio

lint_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test lint_istio

integ-distroless-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-distroless-k8s-tests_istio

integ-local-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-local-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yangminzhu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test unit-tests_istio

integ-security-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-security-k8s-tests_istio

release-test_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test release-test_istio

integ-mixer-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-mixer-k8s-tests_istio

integ-telemetry-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-telemetry-k8s-tests_istio

integ-operator-controller-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-operator-controller-tests_istio

integ-pilot-k8s-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-pilot-k8s-tests_istio

integ-local-tests_istio
4aa0098e41a04dc4089088c2ef423986ab863b4f
link
/test integ-local-tests_istio

integ-galley-k8s-tests_istio
821c1c6bc818af88ac321e061f5837f0d63e9847
link
/test integ-galley-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio/wg-docs-maintainers @istio/wg-policies-and-telemetry-maintainers @istio/wg-user-experience-maintainers could you take a look? thanks.


fix: if ca is not enabled, do not pass the cacert curl flag

Small bug fix were we should not add cacert flag in the situation where ca is disabled.
This should be the last small fix that we can commit without causing breaking changes. I will then close PR #289

In my mind, the internal tls must always have the CA flag. There's no reason to ever have an internal address provided by an external entity that I can see.

In my mind, the internal tls must always have the CA flag. There's no reason to ever have an internal address provided by an external entity that I can see.

That is correct, but it will be an issue on the external ca which will not always be the case that an external ca exists.

Not that important right now. I think we are in the process or will solve this where it will not be a concern.


Update info.json

Debugging job 506

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

jobs/506/info.json
:white_check_mark:Succeeded

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


use angle brackets instead of curly brackets

fixed one code example for better readability
thx.

Docs Build status updates of commit 7aed6b6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/legacy-protocols/how-to-authenticate-an-imap-pop-smtp-application-by-using-oauth.md
:white_check_mark:Succeeded
View

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


Get all sqlite DBs off NFS

Context
Jupyter uses a couple of sqlite DBs:

nbsignatures.db for managing trusted notebooks
(NEW!) file_id_manager.db, for handling file ids for real time collaboration.

By default, these end up on the jupyter data path (not runtime path), as they (maybe? someone should verify) need to persist between sessions.
However, that menas they end up in ~/.local/share/jupyter, which is on NFS.
NFS and sqlite kinda hate each other, and generally using them together causes problems that are hard to debug yet inevitable. So we should find a way to get these off NFS.
This was triggered by https://github.com/2i2c-org/infrastructure/issues/2244.
Proposal

Figure out if we need nbsignatures.db to persist across sessions at all in our context (hosted jupyterhub). If we don't, let's put it in /tmp or somewhere else. If we do, let's document this.
Figure out if we can turn off the fileid sqlite db unless it is absolutely required for RTC. And even in that case, it can not exist on NFS - it uses WAL, which is not supported. So I guess we should just turn this off.

Updates and actions
No response

https://github.com/jupyter-server/jupyter_server_fileid/issues/60 reported upstream

I'm unsure if there is an action point on us regarding this to track here, I'm pre-emptively closing this rather than keeping it around pending that.

[x] We have avoided the issue
[x] We have provided sufficient comments in our basehub config about how its being avoided

The remaining action point if any as I see it, is to follow https://github.com/jupyter-server/jupyter_server_fileid/issues/60 for updates that makes us think if we want to do something else.

I was looking at the logs from the UToronto incident, and see similar messages posted for nbsignatures.db too:
[I 2023-02-22 14:27:39.397 SingleUserLabApp contentsmanager:138] Saving Untitled1.ipynb
[E 2023-02-22 14:27:39.407 SingleUserLabApp filemanager:449] Error while saving file: Untitled1.ipynb unable to open database file
    Traceback (most recent call last):
      File "/opt/conda/lib/python3.10/site-packages/jupyter_server/services/contents/filemanager.py", line 434, in save
        self.check_and_sign(nb, path)
      File "/opt/conda/lib/python3.10/site-packages/jupyter_server/services/contents/manager.py", line 651, in check_and_sign
        self.notary.sign(nb)
      File "/opt/conda/lib/python3.10/site-packages/nbformat/sign.py", line 453, in sign
        self.store.store_signature(signature, self.algorithm)
      File "/opt/conda/lib/python3.10/site-packages/nbformat/sign.py", line 193, in store_signature
        if not self.check_signature(digest, algorithm):
      File "/opt/conda/lib/python3.10/site-packages/nbformat/sign.py", line 228, in check_signature
        self.db.execute(
    sqlite3.OperationalError: unable to open database file
[E 2023-02-22 14:27:39.408 SingleUserLabApp contentsmanager:178] Error while saving file: Untitled1.ipynb HTTP 500: Internal Server Error (Unexpected error while saving file: Untitled1.ipynb unable to open database file)
    Traceback (most recent call last):
      File "/opt/conda/lib/python3.10/site-packages/jupyter_server/services/contents/filemanager.py", line 434, in save
        self.check_and_sign(nb, path)
      File "/opt/conda/lib/python3.10/site-packages/jupyter_server/services/contents/manager.py", line 651, in check_and_sign
        self.notary.sign(nb)
      File "/opt/conda/lib/python3.10/site-packages/nbformat/sign.py", line 453, in sign
        self.store.store_signature(signature, self.algorithm)
      File "/opt/conda/lib/python3.10/site-packages/nbformat/sign.py", line 193, in store_signature
        if not self.check_signature(digest, algorithm):
      File "/opt/conda/lib/python3.10/site-packages/nbformat/sign.py", line 228, in check_signature
        self.db.execute(
    sqlite3.OperationalError: unable to open database file

    The above exception was the direct cause of the following exception:

    Traceback (most recent call last):
      File "/opt/conda/lib/python3.10/site-packages/jupytext/contentsmanager.py", line 175, in save
        return write_pair(path, jupytext_formats, save_one_file)
      File "/opt/conda/lib/python3.10/site-packages/jupytext/pairs.py", line 38, in write_pair
        value = write_one_file(alt_path, fmt)
      File "/opt/conda/lib/python3.10/site-packages/jupytext/contentsmanager.py", line 142, in save_one_file
        return self.super.save(
      File "/opt/conda/lib/python3.10/site-packages/jupyter_server/services/contents/largefilemanager.py", line 59, in save
        return super().save(model, path)
      File "/opt/conda/lib/python3.10/site-packages/jupyter_server/services/contents/filemanager.py", line 450, in save
        raise web.HTTPError(500, f"Unexpected error while saving file: {path} {e}") from e
    tornado.web.HTTPError: HTTP 500: Internal Server Error (Unexpected error while saving file: Untitled1.ipynb unable to open database file)
[W 2023-02-22 14:27:39.408 SingleUserLabApp web:1796] 500 POST /user/7c76d04b-2a80-4db1-b985-a2d2fa2f708c/api/contents (<IP_ADDRESS>): Unexpected error while saving file: Untitled1.ipynb HTTP 500: Internal Server Error (Unexpected error while saving file: Untitled1.ipynb unable to open database file)
[W 2023-02-22 14:27:39.408 SingleUserLabApp handlers:649] wrote error: 'Unexpected error while saving file: Untitled1.ipynb HTTP 500: Internal Server Error (Unexpected error while saving file: Untitled1.ipynb unable to open database file)'

(that is my user logs).


DocsArchive-<IP_ADDRESS>Auto archive content

Auto archive content from https://github.com/OPS-E2E-PPE/docs-archive-test-source

Docs Build status updates of commit 37aa912:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Archive_master_2019-10-14-06-07-23 has been deleted or has been force pushed: fatal: Couldn't find remote ref Archive_master_2019-10-14-06-07-23

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


Update roleManagementAlertOperations properties

ARM API Information (Control Plane)
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo.  If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[x ] Other, please clarify
I recently added this new api version (https://github.com/Azure/azure-rest-api-specs/pull/19296), and it has not yet been released to customers. We recently found a discrepancy between the properties in this API and our corresponding graph API which we need to align with, so we want to correct that in the same api version. The API has not been released to customers, so there should not be customer impact.

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review.  Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.

Hi @juliawelborn, one or multiple breaking change(s) is detected in your PR. Please check out the breaking change(s), and provide business justification in the PR comment and @ PR assignee why you must have these change(s), and how external customer impact can be mitigated. Please ensure to follow breaking change policy to request breaking change review and approval before proceeding swagger PR review. Action: To initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki. If you want to know the production traffic statistic, please see ARM Traffic statistic. If you think it is false positive breaking change, please provide the reasons in the PR comment, report to Swagger Tooling Team via https://aka.ms/swaggerfeedback. Note: To avoid breaking change, you can refer to Shift Left Solution for detecting breaking change in early phase at your service code repository.

Hi @ruowan. There is no customer impact to this breaking change because this API version has not been released to customers. The changes are necessary to align with our service's corresponding Graph APIs, which is important to reduce customer confusion. I have created a breaking change request describing the scenario as well (Scenario 17191878: Microsoft.Authorization 2022-08-01-preview API version breaking change request)


fix(driver): fix build on RHEL 9.3 kernels

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area API-version

/area build

/area CI

/area driver-kmod

/area driver-bpf

/area driver-modern-bpf

/area libscap-engine-bpf

/area libscap-engine-gvisor

/area libscap-engine-kmod

/area libscap-engine-modern-bpf

/area libscap-engine-nodriver

/area libscap-engine-noop

/area libscap-engine-source-plugin

/area libscap-engine-savefile

/area libscap-engine-udig

/area libscap

/area libpman

/area libsinsp

/area tests

/area proposals

Does this PR require a change in the driver versions?

/version driver-API-version-major

/version driver-API-version-minor

/version driver-API-version-patch

/version driver-SCHEMA-version-major

/version driver-SCHEMA-version-minor

/version driver-SCHEMA-version-patch

What this PR does / why we need it:
On recent RHEL9 kernels (namely starting with 5.14.0-327.el9) the kmod driver will fail to build with the following error:
./main.c: In function 'scap_init':
./main.c:2896:30: error: assignment to 'char * (*)(const struct device *, umode_t *)' {aka 'char * (*)(const struct device *, short unsigned int *)'} from incompatible pointer type 'char * (*)(struct device *, umode_t *)' {aka 'char * (*)(struct device *, short unsigned int *)'} [-Werror=incompatible-pointer-types]
         g_ppm_class->devnode = ppm_devnode;
                              ^
cc1: all warnings being treated as errors

Notice how Red Hat backported that change from kernel 6.2 into what looks like 5.14 for RHEL9.3.
See for instance:
$ head -2 */usr/src/kernels/5.14.0-283.el9.x86_64/Makefile.rhelver
RHEL_MAJOR = 9
RHEL_MINOR = 2

vs
$ head -2 */usr/src/kernels/5.14.0-327.el9.x86_64/Makefile.rhelver
RHEL_MAJOR = 9
RHEL_MINOR = 3

Which issue(s) this PR fixes:
Special notes for your reviewer:
This is a followup on https://github.com/falcosecurity/libs/pull/919
Does this PR introduce a user-facing change?:

NONE

Thanks for this fix!

Notice how Red Hat backported that change from kernel 6.2 into what looks like 5.14 for RHEL9.3.

BUT WHY?? :rofl:

/milestone next-driver

The change: https://github.com/torvalds/linux/commit/ff62b8e6588fb07bedda7423622c140c4edd66a7

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, iurly
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

driver/OWNERS [Andreagit97]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: a9050fe709a6ccf424fe29b8fc6d1519bb274e86

/milestone 5.1.0+driver


Selecting keyword from collection is collapsing collection

Afer #25, collections are displayed as collapsed, which is correct. Unfortunately, after selecting keyword from expanded collection, collection gets collapsed. I do not know if it is still fixable in css, or it should be some js functionality.

Fixed by new frontend version


RFP - hdrmerge

Checklist

[x] The package I am requesting does not already exist on https://chocolatey.org/packages;
[x] There is no open issue for this package;
[x] The issue title starts 'RFP - ';
[x] The download URL is public and not locked behind a paywall / login;

Package Details
Software project URL : http://jcelaya.github.io/hdrmerge/
Direct download URL for the software / installer :
https://github.com/jcelaya/hdrmerge/releases/download/v0.5.0/hdrmerge-setup-0.5.0.exe
https://github.com/jcelaya/hdrmerge/releases/download/v0.5.0/hdrmerge-setup64-0.5.0.exe
Software summary / short description:

HDRMerge combines two or more raw images into a single raw with an extended dynamic range. It can import any raw image supported by LibRaw, and outputs a DNG 1.4 image with floating point data. The output raw is built from the less noisy pixels of the input, so that shadows maintain as much detail as possible. This tool also offers a GUI to remove ghosts from the resulting image.

ref: https://github.com/jcelaya/hdrmerge/issues/166

Status: Review
https://chocolatey.org/packages/hdrmerge

Status: Published
https://chocolatey.org/packages/hdrmerge
Can be closed.


StorageExceptions may be suppressed

          Should we add a `TODO` here to not forget about the issue off suppressed `StorageException`?

Originally posted by @sschuberth in https://github.com/eclipse-apoapsis/ort-server/pull/1303#discussion_r1818647624

Closing as #1303 was not merged.


feat: pre-calculate prev and next trip_stop pk_id in vehicle_events

Our view for OPMI RT data uses lag and lead functions to calculate prev trip_stop information on the fly.
To increase performance, the previous and next stop for each vehicle_event RT record will be pre-computed and saved in the vehicle_events database table.
Asana Task: https://app.asana.com/0/1204817744674813/1204881066211313

LGTM 🍰


Swift3 Xcode 8 Beta 3

Fixed compatibility with Swift 3 (Xcode 8 beta 3).
Added compatibility with Swift 3 for tvOS project.
Closes #87.

Wrong branch, resubmitting...


SSH_DOMAIN	 parameter support

guys, need the SSH_DOMAIN as a supported parameter.  I am re-using a separate ingress, thus the domain is different for web/ssh requests in GCE :P
https://gogs.io/docs/advanced/configuration_cheat_sheet

This PR will be obsoleted by https://github.com/kubernetes/charts/pull/2704

Closed in favor of #2704.


AllocatorCreateInfo taking ownership of device and instance

Currently in AllocatorCreateInfo we're required to pass in an owned device and instance. These objects are huge - each with a size of a few kilobytes. If we want to retain the device and instance objects outside the allocator, they needs to be cloned at least twice.
This PR changes this so that AllocatorCreateInfo will only take a reference of the device and instance objects, saving two unnecessary clones.

The erupt library has the same issue, and suggest to solve it by storing the loaders with all the fnptrs in an Rc/Arc. That way, you don't need annoying lifetimes everywhere.


add icon in csv spec to conform to build pipelines

icon is copied from client-op csv which passes the pipeline

Testing
w/o fix
> ./bin/operator-sdk-1.34.1 bundle validate -b podman --select-optional name=operatorhubv2 quay.io/rhn_support_lgangava/code:csi-op-bundle --verbose
DEBU[0000] Debug logging is set
INFO[0000] Unpacking image layers
DEBU[0000] Pulling and unpacking container image         bundle-dir=/tmp/bundle-1486430938 container-tool=podman
INFO[0000] running /usr/bin/podman pull quay.io/rhn_support_lgangava/code:csi-op-bundle
INFO[0002] running podman create
DEBU[0002] [podman create quay.io/rhn_support_lgangava/code:csi-op-bundle ]
[...]
ERRO[0004] Error: Value : (cephcsi-operator.v4.17.0) csv.Spec.Icon elements should contain both data and mediatype

w/ fix
> ./bin/operator-sdk-1.34.1 bundle validate -b podman --select-optional name=operatorhubv2 quay.io/rhn_support_lgangava/code:csi-bundle --verbose
DEBU[0000] Debug logging is set
INFO[0000] Unpacking image layers
DEBU[0000] Pulling and unpacking container image         bundle-dir=/tmp/bundle-410842000 container-tool=podman
INFO[0000] running /usr/bin/podman pull quay.io/rhn_support_lgangava/code:csi-bundle
[...]
INFO[0011] All validation tests have completed successfully

/cherrypick release-4.17


docs(README): correct spelling

Signed-off-by: kanav<EMAIL_ADDRESS>Issue #
Changed Accord Protocol to Accord Project
Changes

-

Flags

Related Issues

Issue #
Pull Request #187

Coverage remained the same at 88.594% when pulling 6b3fae69d79fe96e80979a720126dcaa191d7906 on kanav-raina:master into dbaebb40a759b091e490919be720a051cff000c1 on accordproject:master.

Keeping PRs like this closed unless they are handled in a more comprehensive approach. Open an issue in techdocs which tracks all the READMEs that are correct, all those that are incorrect, and then open a PR linking to that issue for all the ones which are incorrect and we can fix all of this all at once instead of having scattered PRs.


fix: improve mxText type

Add missing protected properties
TSDoc fixes
validation by checking:
https://github.com/jgraph/mxgraph/blob/v4.2.2/javascript/src/js/shape/mxText.js
cc @csouchet @aibcmars

Detected while implementing https://github.com/process-analytics/bpmn-visualization-js/pull/1163


[BUG] Files created in readonly - Callback already called + write error on next write.

Please keep in mind that I am trying this on an older Node Webkit  0.12.0 on Windows XP, 7, 8, 10.
Seems I have to use this version for windows XP support but its node version is higher than the required one for this module.
write error Objecterror: Errorcode: "EPERM"errno: -4048message: "EPERM: operation not permitted, open 'E:\TEST\gfdsgasd\TEST.txt'"path: "E:\TEST\gfdsgasd\TEST.txt"

My zip file contains a text file that is it.
The odd thing is when I goto the file on disk it is there but empty (probably from a previous attempt)
I deleted everything and ran again and it worked which indicates it can't overwrite existing files or directories.
DOH Its creating the file in read only mode. When I zipped the file it was not read only so the permission is being incorrectly set on here.
Ah here is a fix
Line 67-71 of extract-zip/index.js
// if no mode then use the default.
if (mode === 0) {
  if (isDir) mode = 0555
  else mode = 0666 //mode = 0444 read only
}

Maybe there should have a way to specify the default mode if none is set?
Although if I am extracting a file from a ZIP I would kind of expect it to default to writable at least for my user and createWriteStream + other file write methods default to 0666 so I think that should be the default.
What are your thoughts on this?
Sample code
extractZip(path, { dir: 'E:\\TEST' }, function(err) {
    console.log('extracted', err);
});

I think a defaultMode option would be fine, it should be a 1 line addition to the code, and a mention in the readme

Is there an example of how to do this from the api?

I've tried:
await extract(${options.tempDirectory}/${options.appName}.zip, { dir: appath, defaultDirMode:0o777,defaultFileMode:0o777 })
and still not able to extract the zip to overwrite an existing directory because .plist in read-only.

it has been 8 years, this still exists.
all the files are written in read-only mode.
npx extract-zip test.zip dist

@liesauer There is more than one way to extract a zip.
https://www.npmjs.com/package/decompress
https://www.npmjs.com/search?q=zip
You could use a tmp folder and move files after the fact.
But it looks like a default mode was added if needed
defaultDirMode
defaultFileMode
https://github.com/maxogden/extract-zip/blob/master/index.js#L136

I think this is just a ressource leak. Closing the filestream should propably fix it. Alternatively autoClose could be used


AMBARI-24641. Stackadvisor error while trying to add atlas service. E…

…rror - "if mountPoints[mountPoint] < reqiuredDiskSpace: KeyError: None" (amagyar)
What changes were proposed in this pull request?
When ambari agent starts it reports mount points including remote ones by default. However in ambari-server the default value of "agent.check.remote.mounts" is False which will make the agent not to report remote mount points anymore. This patch modifies the default value in the agent to match the default value in the server.
How was this patch tested?

manually on a repro cluster

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/3960/
Test FAILed.
Test FAILured.

retest this please

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/3962/
Test FAILed.
Test FAILured.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/3964/
Test PASSed.


Create symlinks before building antmicro yosys plugins

Having symlinks for the purpose of building the packages should be
enough and will not require us to maintain the patch.

I added a commit that reenables antmicro-yosys-plugins/-complete. Let's see if they will be successfully built.

LGTM


Also merge event descriptions

Thanks for your work @LukasForst, it gave me nice inspiration and I'm using it for a personal project. :)
It seemed quite obvious me to the DESCRIPTION of events should be included as well in the merged calendar.
Yet I soon realized it wasn't the case in camerge (yet).
I assume that this is the place where the field filtering happens.
Was there any reason why the DESCRIPTION was not included?

hi! I think the answer to this question is the line above the one you linked 😄:
# TODO: maybe investigate what is really needed and what is not

feel free to submit PR! I wanted to work more on this project a bit more, but sadly I don't have enough time right now.
One thing to think of when implementing it - when anonymisation is enabled with busy_place_holder=True, one should probably anonymise the description as well (so not set it or not copy it).


Fix a few minor deprecations

Just a few minor things the deprecation cop alerted me to, this is an awesome package BTW! I'm glad it's finally working :smile:

Thank you very much!

I'm glad it's finally working :smile:

Me too. There are still a couple of serious bugs caused by the webview tag again but hopefully they will be fixed faster than the big one before.
Back to working on features ...

Sounds good to me! I wanted to ask you something, actually. Are you familiar with the new service provider API? I was thinking about playing with it a little, and I was going to use web-browser as a guinea pig. Would you be open to a PR that adds a service dependency to this package if I can come up with something really cool?

Would you be open to a PR that adds a service dependency to this package

Yes!
I assume you mean that web-browser would be a service that other packages would use.  I've got a lot of ideas for things that need to call the browser.  For example, a context help that would bring up the actual help web pages for selected words.

Actually I meant web-browser would depend on a service I provide from quantum-shell. You see, I've realized the the command line is a very comfortable and familiar interface for a lot of the hackers who are hacking on the hackable text editor :grin: and it just so happens that my package is a command line interface that runs in atom, much like thedaniel/terminal-panel. However, my focus has been more on builtins and I quickly realized that an atom builtin that sends commands directly to atom would be awesome.  I've got it mostly working and it should be available in the next release. But after I got that working, I realized that it would be really awesome if individual packages could accept command-line input from quantum-shell (instead of the traditional key-bindings). Basically, when all is said and done, my package quantum-shell would provide a service that your package web-browser would subscribe to. I'd write the code for your package that turns web-browser into a command line tool. Meaning a user could pull up quantum-shell type something like:
web-browser open atom.io

and your package would handle the rest. Please keep in mind though, that this is all still contained entirely inside my head, and it would probably be a week or two before I had anything worth looking at.

The end result of your idea is the same as mine.   Your example web-browser open atom.io would do what I was talking about.  It would be an external package talking to mine to bring up a page.  This would work with either package being the service and the other one the client.
Having said that, I would welcome a PR for my package to register as a client.  Maybe I could learn from your work and also provide my package as a service.
We just have to make sure we don't end up with each package registering with the other in an infinite loop.  (grin)

We just have to make sure we don't end up with each package registering with the other in an infinite loop. (grin)

Indeed :grin:, however it the interest of openness, I should tell you that I have less-than-technical reasons for wanting quantum-shell to be the service provider. I would like to eventually create a many-to-one relationship with as many different packages as possible. If this happened, in my readme, I would point to web-browser as the canonical "how-to-turn-my-package-into-a-command-line-tool" example, in the hopes that other package authors would be inspired to subscribe to this hypothetical service. Plus, I wouldn't mind piggybacking all of the exposure web-browser has been receiving recently...isn't it always better to "stand on the shoulder of giants"? :smile:

in the hopes that other package authors would be inspired to subscribe to this hypothetical service.

It occurred to me that you aren't dependent on the other package authors.  If it is easy to register and provide a service as I think, you could do PRs for a lot of other packages.  I don't see why any would reject your PR as it adds another feature.
It will be really easy in my package.  One simple call with a URL argument will open any page.  This assumes that the service API is easy to use.
I haven't looked at the service API.  Will it automatically install your package when I register for your service?  If so you'll get a lot of installs from that.

It will be really easy in my package.

yes, that's why I was hoping you'd be okay with it. I don't have any experience with the services API, and the simpler the implementation, the more I can focus on learning what is needed to make something like this work.

Will it automatically install your package when I register for your service?

I am unsure, but I certainly hope so!


Unable to load charts

wagalytics.bundle.js:273 Uncaught (in promise) TypeError: Cannot read property 'length' of undefined     at wagalytics.bundle.js:273
'wagalytics.bundle.js:352 Uncaught (in promise) TypeError: Cannot read property 'length' of undefined
at createTable (wagalytics.bundle.js:352)
at wagalytics.bundle.js:320
'wagalytics.bundle.js:205 Uncaught (in promise) TypeError: Cannot read property 'map' of undefined
at wagalytics.bundle.js:205
Hello , im facing with these errors in my console , and it does not seem to be able to load the charts , there are no errors within my terminal

I'm having a very similar issue in issue #65


Training Setting

Hi ! Thanks for sharing the trained model, I wonder how to reproduce this result.
For example, for ADE dataset, this training set is the same as Pytorch-Encoding repo??
What is the learning rate and crop size, batch size

Please see GluonCV for training detail


Could not compile doctopt_macros

When I include this crate's latest version and compile with stable 1.1.0, I get the error:
// Could not compile docopt_macros.
// \src/macro.rs:4:1: 4:52 error: unstable feature
// C:\Users\CVO.cargo\registry\src\github.com-1ecc6299db9ec823\doco
// \src/macro.rs:4 #![feature(plugin_registrar, quote, rustc_private
//                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
// note: this feature may not be used in the stable release channel
// error: aborting due to previous error
Any idea when it will compile with stable?
Thanks,
Ivo

When I include this crate's latest version and compile with stable 1.1.0, I get the error:

docopt! is a compiler plugin and compiler plugins do not work on stable Rust. You must use a nightly compiler.

Any idea when it will compile with stable?

No. Not any time soon. If you want to use stable, then you can only use the docopt crate.


add additional checks for lib validations

added lint chekc in the release arduino-library-deploy:v2.2.9


Lambda - using gateway 301 error

i had added follow sameple code, zip and upload to aws lambda
but its not work for me...
Any suggestion please?

import (
	"fmt"
	"log"
	"net/http"
	"os"

	"github.com/apex/gateway"
)

func main() {
	http.HandleFunc("/", hello)
	log.Fatal(gateway.ListenAndServe(":3000", nil))
}

func hello(w http.ResponseWriter, r *http.Request) {
	// example retrieving values from the api gateway proxy request context.
	requestContext, ok := gateway.RequestContext(r.Context())
	if !ok || requestContext.Authorizer["sub"] == nil {
		fmt.Fprint(w, "Hello World from Go")
		return
	}

	userID := requestContext.Authorizer["sub"].(string)
	fmt.Fprintf(w, "Hello %s from Go", userID)
}

This is almost certainly a problem with mux. Try to pass your handler directly to gateway and see if that works. Mux has issues with slashes that seem to conflict with API gateway. You can also play with a default route in API gateway to see if that helps.

@felix0324324 did you find a solution ?

@felix0324324 did you find a solution ?

Same issue...


RenameVariables adding extra underscore

Using robotidy 4.11.0, RenameVariable with default settings foollowing happens with variables in Variables section:
*** Variables ***
-${random_seed} =    ${None}
+${RANDOM_SEED}_ =    ${NONE}

so the underscore after variable and before equal sign should not be there.
Also, maybe the ${None} should not be updated?
Other minor corner case might be numeric (true/false) values where I would like to retain the original value:
${0b1011} {0o10} ${0xFF} ${True}

Thanks - I will check it out. We're due to release so it may be already fixed.
I can add ${None} to ignroed by default. There is ignore_case paramater that allows to ignore (do not update) case of selected variables. By default its ${\n} only. I may add ${True} and ${False} (it looks better than ${TRUE} etc) but for other names I will leave it to the user. Hovewer for numeric values I need to think about some generic way of ignoring them

I can confirm it's a bug - ${return} =  will be converted correctly for other sections but does not work for ```*** Variables ***``. I will fix it & add more tests


show rsvp history in track volunteers

#829
Did:

greyed out when a participant has unrsvped
added a hover to show the rsvp history

Test:

create an event
change user to student (ayisie) and rsvp
unrsvp
go to events list, click on the event, click track volunteers, hover on the date and time under rsvp and you should see the rsvp history

In the case where a user has unrsvpd from an event they are still in the event participant table after the event has occurred, the are just grayed out. If they did not participate in the event they should either be removed or we need to indicate/tell whoever is looking at the table why they are grayed out.
Also, when you go to add a user as a participant on the "Track Volunteers" page on an event they have rsvpd for that has happened this error is thrown:

still working on fixing this!

I am not sure if that is intended, but I can see the rsvp history even when hovering over the student's name, not only the date and time. That is a little distracting because both name and date/time are underlined, which makes me think that they would contain different information once hovering over the two options separately. I would prefer not to have the rsvp history when hovering over the student's name

This issue is on Hold because we are woking on CELTS Spreadsheet.

Refer to the last four comments to continue with issue!


Remove engine dependency of LifecycleChannel

Sends lifecycle messages through a BasicMessageChannel instead of using FlutterTizenEngine::SendPlatformMessage.
I implemented StringCodec from scratch because there was no equivalent of the framework's StringCodec in cpp_client_wrapper. StandardCodecSerializer already has support for the string data type but its serialization format is slightly different from StringCodec's.
@flutter-tizen/maintainers How do you feel about this change? I can discard this change if it doesn't make very much sense.

First of all, Thank you for your efforts to improve code. :clap:  (I should do too... but it's not easy... :smile: )
In my case, I am not sure which one is better, so I referred to other implementation...but I still don't know. :cry:
I'm really curious what other people think regarding this.

There are a few more "Channel" implementations that depend on FlutterTizenEngine, and I'm planning to refactor them as well after this change.

It looks similar to the Android implementation and In my view, this is

@bbrto21 Why do you think so? I'm just curious... I want to know even a small or minor part.

It looks similar to the Android implementation and In my view, this is

@bbrto21 Why do you think so? I'm just curious... I want to know even a small or minor part.

I've just seen these
https://github.com/flutter/engine/blob/6a87e0b558e45ae0e7d3369757512bb3c7c151fa/shell/platform/android/io/flutter/plugin/common/StringCodec.java#L17
https://github.com/flutter/engine/blob/6a87e0b558e45ae0e7d3369757512bb3c7c151fa/shell/platform/android/io/flutter/embedding/engine/systemchannels/LifecycleChannel.java#L20

@bbrto21 FYI, it's also consistent with the Dart side definition of the lifecycle channel.
https://github.com/flutter/flutter/blob/2.2.1/packages/flutter/lib/src/services/system_channels.dart#L210-L223


Hi you, Ask about the server and the client.

You can create server and client individual, to run server then connect to client when server run?
Communication between server and client is separate not same project.
Thank you!

Yes you can run the server and client as separate instances - but with Mirror they're still in the same project.

Yes you can run the server and client as separate instances - but with Mirror they're still in the same project.

I very like video of you, hope you have more game RPG basic, ideas and meaning like simple RPG role playing.
I have subscribed to your channel.
Thank very much.


Create a visual design for the MVP footer

Wonil-Suh1 created the following on Jul 10:

As a user, I need a consolidated view of all the extra resources available on IBM.com.
Acceptance criteria

[x] Design completed
[x] Design shared with IDL for IDL feedback
[x] Design reviewed and approved by dev team
[x] Design approved by DGC design leadership (Charlie Douglas, Wonil Suh, Elliott Trice)

Original issue: https://github.ibm.com/webstandards/digital-design/issues/1208

On Jul 12, Wonil-Suh1 commented:
Initial explorations posted on Wake.
And the sketch file posted here.
@Benjamin-Hansen1 @james-dow @spbokma @chsanche @larahanlon @Olivia-Flory Please comment / criticize!

On Jul 12, larahanlon commented:
@Wonil-Suh1 they all look so good! I left some comments, hope it helps.

On Jul 17, Wonil-Suh1 commented:
Posted on Wake, received feedbacks. Here are some of the feedback items:

The social icons are visually conflicting with the IBM logo
Preference for the stacked version

On Jul 17, Olivia-Flory commented:
@Wonil-Suh1 Does the collapsed version need to have the locale selector? It does in the v18 alt version, but not in the pop up version.
https://www.ibm.com/standards/web/v18/design/footers/
PS.

you still have two Facebook logos in there, you said one would be YouTube?
missing "Privacy" from Option 3

On Jul 17, Wonil-Suh1 commented:
Based on comments, narrowed the number of options to three.
Option 1

Option 2

Option 3

Collapsed version

The Sketch file has more examples.
Next steps
Get final agreement from IDL / Carbon
Get final approval from Elliott

On Jul 18, Wonil-Suh1 commented:
The latest Sketch file is here

On Jul 19, Wonil-Suh1 commented:
One more update to address the local selector button affordance issue:
Lighter border + new icon (proposed to IDL)

On Jul 19, Wonil-Suh1 commented:
Specs

@Jeff-Chew @Kenny-Lam @james-dow @vladislav-saling

On Jul 22, Wonil-Suh1 commented:
Final specs for the full version:

Final specs for minimal version:

On Jul 23, Wonil-Suh1 commented:
And the final Sketch file is here.


SnoopWPF on "Disabled" control state?

I use 2.10 version.
How can I snoop on "Disabled" control state?

I don't get your question.
Could you explain what you mean a bit more?

Normally, When I press Ctrl+Shift and drag mouse over to the control. red border will appear at the control, right?

But,
I have Buttons, TextBoxes that set IsEnabled property value to False. In this case "CREATE" Button.
When I do the same steps as above. Red border does not appear on those controls.
What is your recommendation?
Sorry, for my English.