Fix link to 'map_blocks' function in array api docs

This is a doc-only update. I use the map_blocks function a lot and finally got annoyed enough of the autosummary link at the top of the page not mapping to the function that I fixed it. I also fixed the PerformanceWarning link. However, there are other functions/methods that aren't linked to, but I had trouble figuring out the proper solution. I'll create a separate issue for those in a bit.

[ ] Tests added / passed
[ ] Passes flake8 dask

Thanks @djhoese. Didn't realize that you hadn't submitted a PR before here. Welcome 😄

@stuarteberg might appreciate this. 😉

@jakirkham I have, just not merged yet due to the side effects they make cause (dask.config stuff). Thanks for the merge.


build failure after sbt import

building with 2.11.8 and kafka 0.9
Error:scalac: missing or invalid dependency detected while loading class file 'KafkaUnavailableException.class'.
Could not access type RuntimeException in package scala.package,
because it (or its dependencies) are missing. Check your build definition for
missing or conflicting dependencies. (Re-run with -Ylog-classpath to see the problematic classpath.)
A full rebuild may help if 'KafkaUnavailableException.class' was compiled against an incompatible version of scala.package.

Could this be related to #10 ?

I suspected it was related, however I changed my version from 2.11.8 to 2.11.7 and I still saw the build failure.

v0.5.0 uses Scala 2.11.8 - have you tried to build against 0.4.3-kafka09 using Scala 2.11.7? Please let me know. Also, if you could paste your dependencies declaration that could be helpful.

After some hair-pulling, I finally stepped back and did a sanity check by running sbt compile from a terminal, which succeeded.  There seems to be some issue with IntelliJ and this setup.
dependencies used in project:
"io.spray"            %%  "spray-can"     % sprayV,
"io.spray"            %%  "spray-routing" % sprayV,
"io.spray"            %%  "spray-testkit" % sprayV  % "test",
"com.typesafe.akka"   %%  "akka-actor"    % akkaV,
"com.typesafe.akka"   %%  "akka-testkit"  % akkaV   % "test",
"org.specs2"          %%  "specs2-core"   % "2.3.11" % "test",
"io.spray"            %%  "spray-json"    % "1.3.2",
"com.typesafe.slick"  %%  "slick"          % "3.0.0",
"org.postgresql"      % "postgresql"       % "9.3-1100-jdbc4",
"org.apache.kafka" %% "kafka" % "<IP_ADDRESS>",
"io.confluent"        % "kafka-avro-serializer" % "2.0.0",
"com.julianpeeters"   %% "avrohugger-core" % "0.9.3",
"joda-time"           % "joda-time"        % "2.9.3",
"org.joda"            % "joda-convert"     % "1.2",
"org.scalatest"       % "scalatest_2.11" % "2.2.1" % "test",
"org.mockito"         % "mockito-core" % "1.9.5" % "test",
"net.manub" %% "scalatest-embedded-kafka" % "0.5.0" % "test"

This is strange. Although I'm more inclined to say that it could be a problem with the way IntelliJ interprets SBT dependencies.

I agree.
I moved stuff around and tried different things and IntelliJ still interprets it as a build failure, but using sbt build is a workaround for the moment.

I can keep this issue open for a while, in case anybody else experiences the same problem.

👍
I'll update this thread if we are able to find a solution/cause

Update:  this is definitely a IntelliJ project file issue.  Other team members were able to check the same code and build successfully.
I was able to resolve the error by re-creating the project file and manually setting the Module sources folders.

Awesome, thanks for your feedback.


Expo Updates not checking updates neither is it downloading update

Build/Submit details page URL
https://expo.dev/accounts/infinitypaul/projects/flickwheel/builds/37a39816-757e-41ef-b4b6-9544725fab38
Summary
I'm trying to use expo update to update the JS Layer of my app. I'm currently using EAS build and I'm trying to use Expo Updates to check for updates, after pushing the update to the preview channel branch.
On opening the build on my device. I don't seem to be getting the update. I believe the checkForUpdateAsync is not working.
Please help!
Managed or bare?
Managed
Environment
expo-env-info 1.0.3 environment info:
System:
OS: macOS 12.3.1
Shell: 5.8 - /bin/zsh
Binaries:
Node: 14.18.1 - /usr/local/bin/node
Yarn: 1.22.18 - ~/.yarn/bin/yarn
npm: 6.14.15 - /usr/local/bin/npm
Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman
Managers:
CocoaPods: 1.11.2 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.4, iOS 15.5, macOS 12.3, tvOS 15.4, watchOS 8.5
Android SDK:
API Levels: 27, 28, 29, 30, 31, 32
Build Tools: 29.0.2, 30.0.2, 31.0.0, 32.0.0, 32.0.0, 32.1.0, 33.0.0
System Images: android-27 | Google APIs Intel x86 Atom, android-28 | Google APIs Intel x86 Atom, android-29 | Google APIs Intel x86 Atom, android-29 | Google Play Intel x86 Atom, android-30 | Google APIs Intel x86 Atom, android-30 | Google Play Intel x86 Atom
IDEs:
Android Studio: 2020.3 AI-203.7717.56.2031.7784292
Xcode: 13.4/13F17a - /usr/bin/xcodebuild
npmPackages:
expo: ^45.0.0 => 45.0.4
react: 17.0.2 => 17.0.2
react-dom: 17.0.2 => 17.0.2
react-native: 0.68.2 => 0.68.2
react-native-web: 0.17.7 => 0.17.7
npmGlobalPackages:
eas-cli: 0.52.0
expo-cli: 5.4.4
Expo Workflow: managed
Error output
No response
Reproducible demo or steps to reproduce from a blank project
NA

You are using releaseChannel that specifies channel for classic build service, but you are publishing using EAS Update.
If you want to use EAS Update you need to specify channel in eas.json instead


"ESP-{BOARDID}" Wi-Fi Network Broadcast Continues After Setup

I mentioned this issue in https://github.com/mdhiggins/ESP8266-HTTP-IR-Blaster/issues/306 but since it's unrelated I've opened a new issues. Now, I think I've figured out why this was happening and how to solve/avoid it.
I'm not sure exactly why this occurred on my board, but I think this is because of WiFi mode persistence settings in WiFiManger. Seems like possibly WIFI_AP_STA got set on my board somehow and then persisted after setupWifi.
As a solution, adding WiFi.mode(WIFI_STA); after // if you get here you have connected to the WiFi seems to solve this issue for me. OR, adding WiFi.mode(WIFI_STA); before the WiFiManager wifiManager; may be a better solution so that STA mode gets persisted by WiFiManager on its own.
So, I'm not sure if this was really caused by ESP8266-HTTP-IR-Blaster in the first place, but thought you may want to know how to easily avoid it for any other users. A lot is going on in WiFiManger and ESP8266-HTTP-IR-Blaster and I'm not certain there would be no other consequences to adding this line. Or, there may be a better place to add this line or a better way to solve this altogether.

I'll add that line and test it out, I suspect it will probably be ok and resolve the issue

Adding in both locations may be a better solution. I'm feeling about done with fiddling with this for now, but I just saw a case where my specified wifi_config_name continued to be broadcast after Wi-Fi was connected when I only had WiFi.mode(WIFI_STA); before the WiFiManager wifiManager;.

Want to drop a pull request for your changes and I'll take a look?

Will do. I'll come back to this after a break. Think I'll do a bit more investigating first.
When logging WiFi.getMode() I was seeing that WIFI_AP_STA was still being preserved by WiFiManager after setting WiFi.mode(WIFI_STA); after // if you get here you have connected to the WiFi.
That made it seem like there should be a better place to put WiFi.mode(WIFI_STA); so that WiFiManager would preserve it properly on its own. But, putting it before WiFiManager wifiManager; didn't seem to work like I thought it would.

Seems like putting WiFi.mode(WIFI_STA); before WiFiManager wifiManager; is the way to go. The STA mode variable does get preserved properly by WiFiManager that way.
wifi_config_name continuing to be broadcast after Wi-Fi was connected was a false positive, it just continues to stay visible to my computer for a bit (but cannot be connected to) and then goes away properly.

Merged, gonna close this for now thanks for checking this out


Error with group-level analysis on HPC using singularity image of MRIQC 0.10.0

Hi,
I'm running mriqc version 0.10.0 on an HPC cluster with a BIDS dataset including both structural and functional runs. The subject-level analysis ran successfully, and I am trying to run the group level, but am getting an error message and I'm not seeing any other posts related to this error. Any insights would be appreciated!
Here is the input:
singularity exec /beegfs/work/public/singularity/mriqc-0.10.0.img mriqc /beegfs/work/hartley/projects/MBMFDev/data/BIDS_MBMF/ /beegfs/work/hartley/projects/MBMFDev/data/mriqc/out/ group
Here is the output error:
Traceback (most recent call last):   File "/usr/local/miniconda/bin/mriqc", line 11, in <module>     load_entry_point('mriqc==0.10.0', 'console_scripts', 'mriqc')()   File "/usr/local/miniconda/lib/python3.6/site-packages/mriqc/bin/mriqc_run.py", line 381, in main     out_file=out_html)   File "/usr/local/miniconda/lib/python3.6/site-packages/mriqc/reports/group.py", line 168, in gen_html     'boxplots.js'))).read(),   File "/usr/local/miniconda/lib/python3.6/encodings/ascii.py", line 26, in decode     return codecs.ascii_decode(input, self.errors)[0] UnicodeDecodeError: 'ascii' codec can't decode byte 0xef in position 7465: ordinal not in range(128)

Both solutions may work for other users having the same issues. Bottom line is that we changed the underlying nipype version from v. 0.10.0 to 0.10.1 and this decoding error is one of the bugfixes.
Therefore, a clean install of anaconda would upgrade the version of niworkflows (and in fact update nipype).
Updating the singularity image implicitly updates niworkflows.
Finally, the suggestion of @kevmanderson of unsetting $PYTHONPATH is particularly relevant with singularity. With a singularity image of mriqc-0.10.1 working with a python environment with an outdated niworkflows would lead to this problem if $PYTHONPATH is set.
Thanks very much for posting this issue, and glad the latest release worked well.

@oesteban thank you for clarifying! I'm new to to docker and singularity, so this helps me understand the issue better.


Nathan Individual Test Plan

Score _/5 (Graded by: Brian Zhang)
Github Page Link - Notes
AP Test
AP Test 1 (45/50) - Corrections
AP Test 1 (46/50) - Corrections
Week Plan - AP Plan
Create Task
Create Task Content - Github Page
Video - https://user-images.githubusercontent.com/89236893/165161541-2d438b39-f5c8-4d1d-a18d-171aaaac3187.mp4

[x] Start review ticket with study plan and study reflection for week, due EOD Monday 4/18
[x] Finals-Quiz1 score/50 and corrections
[x] Finals-Quiz2 score/50 and corrections
[x] Create Task code/runtime and 1 min video are reviewed by another person, you may request Teacher review as time permits
[x] Review ticket with Crossover Score on Monday 4/25 in class

Reflection:
I think my plan for study went well, as my score this time around the MCQ was a lot better than my previous tests, and I ended up performing better on problems I reviewed. However, I do believe I need review on topic we haven't covered in a while, because some topics ended up confusing me a lot, resulting in a lower score than I expected.

Score 5/5 Grader: Brian Zhang

[ ] Study plan Here
[ ] Study reflection for week: Listed at the bottom of this issue
[ ] Finals-Quiz1 score/50 and corrections: Link
[ ] Finals-Quiz2 score/50 and corrections: Link
[ ] Create Task code/runtime and 1 min video: Video


How do I use this with Scrivener?

No idea how to use this with Scrivener, saw it on the forums.
How do I use it?

All that I have is at https://retorque.re/zotero-better-bibtex/cayw/. For more you'd have to ask on the zotero forums I'm afraid. I provide the infrastructure to make the integration but not the integration itself.


add a warning header comment indicating that files are generated

First off, thanks for a very useful tool!
For many code generators it is customary to add a header comment that indicates that the file is a generated one and, hence, shouldn't be edited. This can be very valuable information in a large code base.
For example, the following header could be added to every generated file.
// Code generated by quicktype; DO NOT EDIT.

If adding it as default behavior feels too disruptive, maybe it would be possible to opt-in on it with a --add-generated-warning command-line flag or similar?

Sure, we would accept a PR that adds this.


kclient: refactor for easier usage

This is just refactoring. Mostly, its to make it easier to use for tests when we want either direct reads (Get and List w/o informer) or to just generate a writer-only client w/o and informer.
Tests are updated to use these.

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
099817a30085eac38e5351c835c6f6b058a3b14e
link
true
/test lint

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
099817a30085eac38e5351c835c6f6b058a3b14e
link
true
/test lint

gencheck_istio
099817a30085eac38e5351c835c6f6b058a3b14e
link
true
/test gencheck

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
099817a30085eac38e5351c835c6f6b058a3b14e
link
true
/test lint

gencheck_istio
099817a30085eac38e5351c835c6f6b058a3b14e
link
true
/test gencheck

unit-tests-arm64_istio
099817a30085eac38e5351c835c6f6b058a3b14e
link
true
/test unit-tests-arm64

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
099817a30085eac38e5351c835c6f6b058a3b14e
link
true
/test lint

gencheck_istio
099817a30085eac38e5351c835c6f6b058a3b14e
link
true
/test gencheck

unit-tests-arm64_istio
099817a30085eac38e5351c835c6f6b058a3b14e
link
true
/test unit-tests-arm64

unit-tests_istio
099817a30085eac38e5351c835c6f6b058a3b14e
link
true
/test unit-tests

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
099817a30085eac38e5351c835c6f6b058a3b14e
link
true
/test lint

gencheck_istio
099817a30085eac38e5351c835c6f6b058a3b14e
link
true
/test gencheck

unit-tests_istio
099817a30085eac38e5351c835c6f6b058a3b14e
link
true
/test unit-tests

unit-tests-arm64_istio
b98fcc9fd426a5677db8148ac00dfe6f1a70e2d0
link
true
/test unit-tests-arm64

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
099817a30085eac38e5351c835c6f6b058a3b14e
link
true
/test gencheck

unit-tests_istio
099817a30085eac38e5351c835c6f6b058a3b14e
link
true
/test unit-tests

unit-tests-arm64_istio
b98fcc9fd426a5677db8148ac00dfe6f1a70e2d0
link
true
/test unit-tests-arm64

lint_istio
b98fcc9fd426a5677db8148ac00dfe6f1a70e2d0
link
true
/test lint

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
099817a30085eac38e5351c835c6f6b058a3b14e
link
true
/test gencheck

unit-tests-arm64_istio
b98fcc9fd426a5677db8148ac00dfe6f1a70e2d0
link
true
/test unit-tests-arm64

lint_istio
b98fcc9fd426a5677db8148ac00dfe6f1a70e2d0
link
true
/test lint

unit-tests_istio
b98fcc9fd426a5677db8148ac00dfe6f1a70e2d0
link
true
/test unit-tests

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
b98fcc9fd426a5677db8148ac00dfe6f1a70e2d0
link
true
/test unit-tests-arm64

lint_istio
b98fcc9fd426a5677db8148ac00dfe6f1a70e2d0
link
true
/test lint

unit-tests_istio
b98fcc9fd426a5677db8148ac00dfe6f1a70e2d0
link
true
/test unit-tests

gencheck_istio
b98fcc9fd426a5677db8148ac00dfe6f1a70e2d0
link
true
/test gencheck

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
b98fcc9fd426a5677db8148ac00dfe6f1a70e2d0
link
true
/test lint

unit-tests_istio
b98fcc9fd426a5677db8148ac00dfe6f1a70e2d0
link
true
/test unit-tests

gencheck_istio
b98fcc9fd426a5677db8148ac00dfe6f1a70e2d0
link
true
/test gencheck

unit-tests-arm64_istio
2add1e349aa0113c6d20bfc43d86d125980cb55e
link
true
/test unit-tests-arm64

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
b98fcc9fd426a5677db8148ac00dfe6f1a70e2d0
link
true
/test unit-tests

unit-tests-arm64_istio
2add1e349aa0113c6d20bfc43d86d125980cb55e
link
true
/test unit-tests-arm64

gencheck_istio
2add1e349aa0113c6d20bfc43d86d125980cb55e
link
true
/test gencheck

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
2add1e349aa0113c6d20bfc43d86d125980cb55e
link
true
/test unit-tests-arm64

gencheck_istio
2add1e349aa0113c6d20bfc43d86d125980cb55e
link
true
/test gencheck

unit-tests_istio
2add1e349aa0113c6d20bfc43d86d125980cb55e
link
true
/test unit-tests

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
2add1e349aa0113c6d20bfc43d86d125980cb55e
link
true
/test gencheck

unit-tests_istio
2add1e349aa0113c6d20bfc43d86d125980cb55e
link
true
/test unit-tests

unit-tests-arm64_istio
b97b4ccb69ebbd2201773f4ba7e509d270dcc6ce
link
true
/test unit-tests-arm64

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
b97b4ccb69ebbd2201773f4ba7e509d270dcc6ce
link
true
/test unit-tests-arm64

unit-tests_istio
b97b4ccb69ebbd2201773f4ba7e509d270dcc6ce
link
true
/test unit-tests

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.

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
ea971b76e08a4363d7b58175375056d271568617
link
true
/test unit-tests

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.

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
ea971b76e08a4363d7b58175375056d271568617
link
true
/test unit-tests

unit-tests-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests-arm64

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
ea971b76e08a4363d7b58175375056d271568617
link
true
/test unit-tests

unit-tests-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests-arm64

analyze-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test analyze-tests

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests-arm64

analyze-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test analyze-tests

unit-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests-arm64

analyze-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test analyze-tests

unit-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests

integ-basic-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-basic-arm64

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests-arm64

analyze-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test analyze-tests

unit-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests

integ-basic-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-basic-arm64

release-test_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test release-test

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests-arm64

analyze-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test analyze-tests

unit-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests

integ-basic-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-basic-arm64

release-test_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test release-test

integ-ipv6_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-ipv6

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests-arm64

analyze-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test analyze-tests

unit-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests

integ-basic-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-basic-arm64

release-test_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test release-test

integ-ipv6_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-ipv6

integ-helm_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-helm

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests-arm64

analyze-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test analyze-tests

unit-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests

integ-basic-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-basic-arm64

release-test_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test release-test

integ-ipv6_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-ipv6

integ-helm_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-helm

integ-distroless_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-distroless

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests-arm64

analyze-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test analyze-tests

unit-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests

integ-basic-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-basic-arm64

release-test_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test release-test

integ-ipv6_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-ipv6

integ-helm_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-helm

integ-distroless_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-distroless

integ-pilot_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-pilot

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests-arm64

analyze-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test analyze-tests

unit-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests

integ-basic-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-basic-arm64

release-test_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test release-test

integ-ipv6_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-ipv6

integ-helm_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-helm

integ-distroless_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-distroless

integ-pilot_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-pilot

integ-cni_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-cni

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests-arm64

analyze-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test analyze-tests

unit-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests

integ-basic-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-basic-arm64

release-test_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test release-test

integ-ipv6_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-ipv6

integ-helm_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-helm

integ-distroless_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-distroless

integ-pilot_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-pilot

integ-cni_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-cni

integ-security_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-security

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests-arm64

analyze-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test analyze-tests

unit-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests

integ-basic-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-basic-arm64

release-test_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test release-test

integ-ipv6_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-ipv6

integ-helm_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-helm

integ-distroless_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-distroless

integ-pilot_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-pilot

integ-cni_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-cni

integ-security_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-security

integ-telemetry-istiodremote_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-telemetry-istiodremote

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests-arm64

analyze-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test analyze-tests

unit-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests

integ-basic-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-basic-arm64

release-test_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test release-test

integ-ipv6_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-ipv6

integ-helm_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-helm

integ-distroless_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-distroless

integ-pilot_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-pilot

integ-cni_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-cni

integ-security_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-security

integ-telemetry-istiodremote_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-telemetry-istiodremote

integ-ds_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-ds

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests-arm64

analyze-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test analyze-tests

unit-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests

integ-basic-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-basic-arm64

release-test_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test release-test

integ-ipv6_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-ipv6

integ-helm_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-helm

integ-distroless_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-distroless

integ-pilot_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-pilot

integ-cni_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-cni

integ-security_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-security

integ-telemetry-istiodremote_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-telemetry-istiodremote

integ-ds_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-ds

integ-telemetry_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-telemetry

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests-arm64

analyze-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test analyze-tests

unit-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests

integ-basic-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-basic-arm64

release-test_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test release-test

integ-ipv6_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-ipv6

integ-helm_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-helm

integ-distroless_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-distroless

integ-pilot_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-pilot

integ-cni_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-cni

integ-security_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-security

integ-telemetry-istiodremote_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-telemetry-istiodremote

integ-ds_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-ds

integ-telemetry_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-telemetry

gencheck_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test gencheck

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests-arm64

analyze-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test analyze-tests

unit-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests

integ-basic-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-basic-arm64

release-test_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test release-test

integ-ipv6_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-ipv6

integ-helm_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-helm

integ-distroless_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-distroless

integ-pilot_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-pilot

integ-cni_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-cni

integ-security_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-security

integ-telemetry-istiodremote_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-telemetry-istiodremote

integ-ds_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-ds

integ-telemetry_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-telemetry

gencheck_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test gencheck

integ-ambient_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-ambient

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests-arm64

analyze-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test analyze-tests

unit-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests

integ-basic-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-basic-arm64

release-test_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test release-test

integ-ipv6_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-ipv6

integ-helm_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-helm

integ-distroless_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-distroless

integ-pilot_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-pilot

integ-cni_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-cni

integ-security_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-security

integ-telemetry-istiodremote_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-telemetry-istiodremote

integ-ds_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-ds

integ-telemetry_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-telemetry

gencheck_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test gencheck

integ-ambient_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-ambient

integ-pilot-istiodremote_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-pilot-istiodremote

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests-arm64

analyze-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test analyze-tests

unit-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests

integ-basic-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-basic-arm64

release-test_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test release-test

integ-ipv6_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-ipv6

integ-helm_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-helm

integ-distroless_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-distroless

integ-pilot_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-pilot

integ-cni_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-cni

integ-security_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-security

integ-telemetry-istiodremote_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-telemetry-istiodremote

integ-ds_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-ds

integ-telemetry_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-telemetry

gencheck_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test gencheck

integ-ambient_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-ambient

integ-pilot-istiodremote_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-pilot-istiodremote

lint_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test lint

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests-arm64

analyze-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test analyze-tests

unit-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests

integ-basic-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-basic-arm64

release-test_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test release-test

integ-ipv6_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-ipv6

integ-helm_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-helm

integ-distroless_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-distroless

integ-pilot_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-pilot

integ-cni_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-cni

integ-security_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-security

integ-telemetry-istiodremote_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-telemetry-istiodremote

integ-ds_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-ds

integ-telemetry_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-telemetry

gencheck_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test gencheck

integ-ambient_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-ambient

integ-pilot-istiodremote_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-pilot-istiodremote

lint_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test lint

integ-operator-controller_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-operator-controller

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests-arm64

analyze-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test analyze-tests

unit-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests

integ-basic-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-basic-arm64

release-test_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test release-test

integ-ipv6_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-ipv6

integ-helm_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-helm

integ-distroless_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-distroless

integ-pilot_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-pilot

integ-cni_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-cni

integ-security_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-security

integ-telemetry-istiodremote_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-telemetry-istiodremote

integ-ds_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-ds

integ-telemetry_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-telemetry

gencheck_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test gencheck

integ-ambient_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-ambient

integ-pilot-istiodremote_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-pilot-istiodremote

lint_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test lint

integ-operator-controller_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-operator-controller

integ-pilot-multicluster_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-pilot-multicluster

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests-arm64

analyze-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test analyze-tests

unit-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests

integ-basic-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-basic-arm64

release-test_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test release-test

integ-ipv6_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-ipv6

integ-helm_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-helm

integ-distroless_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-distroless

integ-pilot_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-pilot

integ-cni_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-cni

integ-security_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-security

integ-telemetry-istiodremote_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-telemetry-istiodremote

integ-ds_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-ds

integ-telemetry_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-telemetry

gencheck_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test gencheck

integ-ambient_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-ambient

integ-pilot-istiodremote_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-pilot-istiodremote

lint_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test lint

integ-operator-controller_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-operator-controller

integ-pilot-multicluster_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-pilot-multicluster

integ-telemetry-mc_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-telemetry-mc

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests-arm64

analyze-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test analyze-tests

unit-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests

integ-basic-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-basic-arm64

release-test_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test release-test

integ-ipv6_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-ipv6

integ-helm_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-helm

integ-distroless_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-distroless

integ-pilot_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-pilot

integ-cni_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-cni

integ-security_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-security

integ-telemetry-istiodremote_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-telemetry-istiodremote

integ-ds_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-ds

integ-telemetry_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-telemetry

gencheck_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test gencheck

integ-ambient_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-ambient

integ-pilot-istiodremote_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-pilot-istiodremote

lint_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test lint

integ-operator-controller_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-operator-controller

integ-pilot-multicluster_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-pilot-multicluster

integ-telemetry-mc_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-telemetry-mc

integ-pilot-istiodremote-mc_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-pilot-istiodremote-mc

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests-arm64

analyze-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test analyze-tests

unit-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests

integ-basic-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-basic-arm64

release-test_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test release-test

integ-ipv6_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-ipv6

integ-helm_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-helm

integ-distroless_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-distroless

integ-pilot_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-pilot

integ-cni_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-cni

integ-security_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-security

integ-telemetry-istiodremote_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-telemetry-istiodremote

integ-ds_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-ds

integ-telemetry_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-telemetry

gencheck_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test gencheck

integ-ambient_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-ambient

integ-pilot-istiodremote_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-pilot-istiodremote

lint_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test lint

integ-operator-controller_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-operator-controller

integ-pilot-multicluster_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-pilot-multicluster

integ-telemetry-mc_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-telemetry-mc

integ-pilot-istiodremote-mc_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-pilot-istiodremote-mc

integ-security-istiodremote_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-security-istiodremote

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests-arm64

analyze-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test analyze-tests

unit-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test unit-tests

integ-basic-arm64_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-basic-arm64

release-test_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test release-test

integ-ipv6_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-ipv6

integ-helm_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-helm

integ-distroless_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-distroless

integ-pilot_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-pilot

integ-cni_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-cni

integ-security_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-security

integ-telemetry-istiodremote_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-telemetry-istiodremote

integ-ds_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-ds

integ-telemetry_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-telemetry

gencheck_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test gencheck

integ-ambient_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-ambient

integ-pilot-istiodremote_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-pilot-istiodremote

lint_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test lint

integ-operator-controller_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-operator-controller

integ-pilot-multicluster_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-pilot-multicluster

integ-telemetry-mc_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-telemetry-mc

integ-pilot-istiodremote-mc_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-pilot-istiodremote-mc

integ-security-istiodremote_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-security-istiodremote

integ-security-multicluster_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-security-multicluster

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

analyze-tests_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test analyze-tests

release-test_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test release-test

integ-ipv6_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-ipv6

integ-helm_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-helm

integ-distroless_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-distroless

integ-pilot_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-pilot

integ-cni_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-cni

integ-security_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-security

integ-telemetry-istiodremote_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-telemetry-istiodremote

integ-ds_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-ds

integ-telemetry_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-telemetry

integ-pilot-istiodremote_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-pilot-istiodremote

integ-operator-controller_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-operator-controller

integ-pilot-multicluster_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-pilot-multicluster

integ-telemetry-mc_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-telemetry-mc

integ-pilot-istiodremote-mc_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-pilot-istiodremote-mc

integ-security-istiodremote_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-security-istiodremote

integ-security-multicluster_istio
a05a6a427585b0564ca120003d49caac85571f6d
link
true
/test integ-security-multicluster

unit-tests_istio
a77dd7a9d907ec5000cce0bc9878fb8e9eefd8e4
link
true
/test unit-tests

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
a77dd7a9d907ec5000cce0bc9878fb8e9eefd8e4
link
true
/test unit-tests

integ-security-multicluster_istio
a77dd7a9d907ec5000cce0bc9878fb8e9eefd8e4
link
true
/test integ-security-multicluster

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.

/retest


Add SwiftPM support

Hi Tim, I hope you're well. This is a useful little library! It would be nice to be able to use it with SPM so I added a swift package description. I had to move the source files around a bit to make it work, and I made sure the test project has the updated paths.
Best,
Jonas

Rad, thanks!


Publish Tekton Dashboard as GitHub Actions Environment

Right now we create a environment from our Pulumi created EKS cluster address which has minimal use right now. It would be much more aligned with the project's goals to have the Tekton Dashboard available which could be also linked inside the GitHub Actions log.

Fixed by https://github.com/jonashackt/pulumi-eks-tekton/pull/19


Full exit nft missing tx details

Description
FullExitNft transaction only generate one owner account related and one nft related tx detail, missing creator account related tx detail which is needed by circuit, see https://github.com/bnb-chain/zkbnb-crypto/issues/28
Rationale
FullExitNft missing txDetails
Changes
Notable changes:
add a TxDetail for creatorAccount

This is already merged in https://github.com/bnb-chain/zkbnb/pull/244


Cow: Watch bandiztechnoz.com

Cow requests the watch of the watch_keyword bandiztechnoz\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

bandiztechnoz\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by double-beep in Charcoal HQ


split results

Congratulations on another excellent piece of work. I would like to get random seeds or txts of your triple dataset split in order to follow your work. Looking forward to your reply.
Best wishes!

thanks for focusing our benchmarks, three split-files have upload in /data

Thank you very much.


Remove Global Scroll on Document Edit Page

What would you like to be added:
On the document edit page, the global scroll should not be visible. Currently, due to unknown margins outside the document, the global scroll is visible.
Why is this needed:
To provide a cleaner look and better user experience on the document edit page.
Additional Information:

I'd like to work on this issue, can I take it on?

@bishoe01
Sure. If you have any questions, feel free to ask.

@bishoe01
This is more detail description about this issue.
https://github.com/user-attachments/assets/cbc39586-1b87-4f07-9805-37375cbb51e6
As you can see, an unintended space appears at the bottom of the screen, causing a global scroll to occur.
You can check this CodePair document here.
If you have any questions, please leave a comment on this GitHub Issue.


--max-quality ignored when used without -f

Example:
$ youtube-dl -F https://www.youtube.com/watch\?v\=lYePxF7CJ6I
[youtube] lYePxF7CJ6I: Downloading webpage
[youtube] lYePxF7CJ6I: Extracting video information
[youtube] lYePxF7CJ6I: Downloading DASH manifest
[info] Available formats for lYePxF7CJ6I:
format code  extension  resolution note
171          webm       audio only DASH audio  126k , audio@128k (44100Hz), 5.42MiB
140          m4a        audio only DASH audio  129k , m4a_dash container, aac  @128k (44100Hz), 6.14MiB
141          m4a        audio only DASH audio  255k , m4a_dash container, aac  @256k (44100Hz), 12.19MiB
160          mp4        256x144    DASH video  120k , 15fps, video only, 4.61MiB
278          webm       256x144    DASH video  134k , webm container, VP9, 15fps, video only, 3.03MiB
133          mp4        426x240    DASH video  274k , 30fps, video only, 9.92MiB
242          webm       426x240    DASH video  289k , 30fps, video only, 5.67MiB
243          webm       640x360    DASH video  485k , 30fps, video only, 10.02MiB
134          mp4        640x360    DASH video  603k , 30fps, video only, 11.21MiB
244          webm       854x480    DASH video  851k , 30fps, video only, 16.15MiB
135          mp4        854x480    DASH video 1109k , 30fps, video only, 20.30MiB
302          webm       1280x720   DASH video 2678k , VP9, 60fps, video only, 41.82MiB
298          mp4        1280x720   DASH video 3310k , h264, 60fps, video only, 61.45MiB
303          webm       1920x1080  DASH video 4966k , VP9, 60fps, video only, 79.56MiB
299          mp4        1920x1080  DASH video 5523k , h264, 60fps, video only, 107.74MiB
17           3gp        176x144
36           3gp        320x240
5            flv        400x240
43           webm       640x360
18           mp4        640x360
22           mp4        1280x720   (best)

$ youtube-dl --max-quality 99 https://www.youtube.com/watch\?v\=lYePxF7CJ6I
[youtube] lYePxF7CJ6I: Downloading webpage
[youtube] lYePxF7CJ6I: Extracting video information
[youtube] lYePxF7CJ6I: Downloading DASH manifest
[download] Destination: LGR - Operation Frog - C64 Game Review-lYePxF7CJ6I.f299.mp4
[download] 100% of 107.74MiB in 01:15
[download] Destination: LGR - Operation Frog - C64 Game Review-lYePxF7CJ6I.f141.m4a
[download] 100% of 12.19MiB in 00:11
[ffmpeg] Merging formats into "LGR - Operation Frog - C64 Game Review-lYePxF7CJ6I.mp4"

Despite asking for a max-quality of 99 (ie everything that isn't DASH), I still get the 299 and 141 qualities.
This is regardless of the video or the argument passed to --max-quality:
$ youtube-dl --max-quality 199 https://www.youtube.com/watch\?v\=g1zerc7crGM
[youtube] g1zerc7crGM: Downloading webpage
[youtube] g1zerc7crGM: Extracting video information
[youtube] g1zerc7crGM: Downloading DASH manifest
[download] Destination: LGR - SimCity BuildIt Review-g1zerc7crGM.f299.mp4
[download] 100% of 155.75MiB in 01:51
[download] Destination: LGR - SimCity BuildIt Review-g1zerc7crGM.f141.m4a
[download] 100% of 11.06MiB in 00:15
[ffmpeg] Merging formats into "LGR - SimCity BuildIt Review-g1zerc7crGM.mp4"
Deleting original file LGR - SimCity BuildIt Review-g1zerc7crGM.f299.mp4 (pass -k to keep)
Deleting original file LGR - SimCity BuildIt Review-g1zerc7crGM.f141.m4a (pass -k to keep)

Using -f best seems to make --max-quality actually be taken into account:
$ youtube-dl --max-quality 43 -f best https://www.youtube.com/watch\?v\=lYePxF7CJ6I
[youtube] lYePxF7CJ6I: Downloading webpage
[youtube] lYePxF7CJ6I: Extracting video information
[youtube] lYePxF7CJ6I: Downloading DASH manifest
[download] Destination: LGR - Operation Frog - C64 Game Review-lYePxF7CJ6I.webm

All that being said, I realize that --max-quality is pretty much made obsolete by the new capabilities of -f. However, the option is still mentioned in the docs and help text, and simply gets ignored when used on its own, which is confusing.
The most simple way to solve this, I think, would be to simply remove the option, or mark it as deprecated. Maybe emit a warning or error when it's used, and ask the user to use -f instead.

We've removed the option, you'll have to use -f best[<somefilter>] in the next version.
Thanks for the report.


Document building with west by default

This PR intends to make west build a first-class citizen in our documentation. This involves rewriting parts of the zephyr app extension so that we make use of modern CMake features and we do not rely on environment variables anymore, cleaning up the documentation that still refers to cmake as an executable directly and finally turn on the option to make west always present in build instructions.
See commit messages for additional details.

@dbkinder @mbolivar I addressed the doc comments. I will next take a look at the code itself.

@nashif @carlescufi : Something went bad with CODEOWNERS(!?) this should have added several reviewers who are missing.

For native_posix, as it was before, https://builds.zephyrproject.org/zephyrproject-rtos/zephyr/16839/docs/boards/posix/native_posix/doc/index.html#compiling , if you ran the build commands you ended up in the build/ folder, so the following commands from the "Running" section could be run directly. Here at least the text indicates that the resulting executable is placed in the build folder, but if you go for example to https://builds.zephyrproject.org/zephyrproject-rtos/zephyr/16839/docs/guides/coverage.html#coverage-posix , or https://builds.zephyrproject.org/zephyrproject-rtos/zephyr/16839/docs/boards/posix/nrf52_bsim/doc/index.html#building-and-running , you now have a set of commands which miss a cd build in between

My oversight, thanks for spotting this. Will fix.

@aescolar @mbolivar thanks for the review. I've addressed your comments.


Keep original isClientTheLeader value on page refresh

Details
Login - 'Another login page is open' briefly displayed when refresh the page
A bug was caused by this PR #40997. On page refresh, the app was cleaning its own clientID from the list of active clients. And while the page is still visible Onyx reports change and triggers re-render. Since clientID is already removed from the list, isClientTheLeader returns false.
Fixed Issues

$ https://github.com/Expensify/App/issues/42062
PROPOSAL: https://github.com/Expensify/App/issues/42062#issuecomment-2108068691
Tests

[ ] Open sign-in page
[ ] Hit Refresh page
[ ] Title "Get started below." should not change to "Another login page is open."

Offline tests

QA Steps

[ ] Open sign-in page
[ ] Hit Refresh page
[ ] Title "Get started below." should not change to "Another login page is open."

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos
MacOS: Chrome / Safari
https://github.com/Expensify/App/assets/1768919/e88da317-efb3-406a-87fb-c387da21d3d1

is this PR requires me as c+ @tgolen : )

Yes, would you please do the checklist for this PR and test it?

@ishpaul777 that's correct behavior since once the tab is active, client becomes the leader

you may see the bug in related bug https://github.com/Expensify/App/issues/42062
The issue is the when there is only one tab active (hence already leading client) and user refreshs the page, the cleanup process is removing current client ID and it mistakingly becomes not the leading one. This leads to showing the "Another login page is open." title on sign up page for a second before the page is refreshed.

We don’t have such scenarios for native devices. Also, the code is mocked
for that platforms. It only affects web browsers.
On Tue, May 14, 2024 at 00:09 Ishpaul Singh @.***>
wrote:

also @Skakruk https://github.com/Skakruk Can you please add demo videos
for Andriod chrome and Ios safari
—
Reply to this email directly, view it on GitHub
https://github.com/Expensify/App/pull/42095#issuecomment-2108804110, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AANP3V3NOKLP2DCIK6VAKGLZCETZJAVCNFSM6AAAAABHUWNPV6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBYHAYDIMJRGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

@ishpaul777 I've uploaded screen records for iOS Safari and Android Chrome devices

You completed 56 out of 57 checklist items with 1 unfinished items

@ishpaul777 did you want to check off that last item?

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Cherry-picked to staging by https://github.com/mountiny in version: 1.4.73-7 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to production by https://github.com/Beamanator in version: 1.4.73-7 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Fix timeval redefinition

Hello @polyfractal and thanks very much for your work!
I was getting redefinition errors when attempting to build on Arch, with packages:

arm-none-eabi-gcc
arm-none-eabi-gdb
arm-none-eabi-newlib
arm-none-eabi-binutils

Specifically, struct timeval was redefined. It sounded identical to this reported issue. I tried following the instructions in sockets.h and that seemed to work nicely, so I submit the changes for your approval.
Could it cause problems on Ubuntu, as you seem not to have encountered this issue? Reject away if so!

Awesome, thanks for these!  I'll try it out on Ubuntu today and see if it causes problems... I'm guessing it'll be fine, perhaps Ubuntu is just more lenient or something?
What version of arm-non-eabi-gcc were you using?  On my machine it installed 4.9.3 20150529

Hrm, Arch gave me 6.3.0. I guess it's the whole rolling release thing.

Sorry for the delay, just got a chance to try this out.  Seems that newer versions are just pickier... this compiles fine on 4.9.3.  Merging, thanks!


HCE Support

Does this plugin has HCE support..like to emulate any custom string entered as nfc tag.

dup of #118


TLS and Basic auth vars for capm3 v0.4.1 release

What this PR does / why we need it:
Add missing TLS and Basic auth related vars which are required for the clusterctl deployment.

/assign @maelk

/lgtm

/test-integration


Call to undefined method

I tried following the first tutorial (Hello World) in php.
I copy pasted the code and I get the following error in the console:
 [*] Waiting for messages. To exit press CTRL+C PHP Fatal error:  Uncaught Error: Call to undefined method PhpAmqpLib\Channel\AM QPChannel::is_consuming()
I've searched everywhere, no one seems to get this error.How can I solve this?
Thanks.

Thank you for your time.
Team RabbitMQ uses GitHub issues for specific actionable items engineers can work on. GitHub issues are not used for questions, investigations, root cause analysis, discussions of potential issues, etc (as defined by this team).
We get at least a dozen of questions through various venues every single day, often light on details.
At that rate GitHub issues can very quickly turn into a something impossible to navigate and make sense of even for our team. Because GitHub is a tool our team uses heavily nearly every day, the signal/noise ratio of issues is something we care about a lot.
Please post this to rabbitmq-users.
Thank you.

You may be using an older version of the client (or a newer one, @lukebakken has done some releases recent but I believe the tutorials are up-to-date). Or you might have missed the dependency installation step with Composer.
See rabbitmq/rabbitmq-tutorials for an executable version.

https://github.com/rabbitmq/rabbitmq-tutorials/pull/227 upgraded the tutorials to use the latest API.


Device requirements

https://github.com/mogenson/fitbit-heart-rate-service/blob/4b98a5b7c893b164f6854f4fa349b3ef19ec5f02/README.md?plain=1#L13
Is there anything special about the Sense or Versa 3 that allows this? Could this method be used on other Fitbit models (like Versa 2 or Charge series, etc)?

This setup should work on any Fitbit device that https://studio.fitbit.com supports. This project is currently configured to target Fitbit OS 5.0 (which only run on Sense and Versa 3 watches). I don't own any other Fitbit products, so I can't test them to be sure. Feel free to build the watch app for another device and try it out. You'll probably also need to adjust the graphics and layout for a different size display.

Thanks for the quick response. I took a look at Fitbit Studio and now it's clear why this is the case. Fitbit SDK 5/6 supports Sense and Versa 3 while SDK 4.3 supports older models (Versa/Lite/2 and Ionic). It looks like the Charge series is SOL. I'll try to take a look at this for Versa 2 later.


zsh escapes space after singleton completions

On unique completion possibilities, a trailing space is added. This has the nice effect of adding a space on the command line, but is not an ideal way to do so. zsh, for instance, is smart enough to notice that trailing space, and keeps escaping it automatically (so instead of '--help', zsh completes it as '--help\ ' which is incorrect).
IMHO, this is better handled by removing the '-o nospace' in:
complete -o nospace -o default -F _python_argcomplete "t"

...and removing these lines:
in init.py:
 If there's only one completion, and it's not open-quoted and doesn't end with a continuation char, add a space
 continuation_chars = '=/:'
if len(completions) == 1 and completions[0][-1] not in continuation_chars:
    if cword_prequote == '' and not completions[0].endswith(' '):
        completions[0] += ' '

Is there any reason not to do so that I'm not seeing?

Does it make sense to have "singleton completions that may be partial"? In the case of a directory name followed by a slash, should you not also return the contents of that directory? For example, if you return dir/ and expect the user could use something in that directory, why not also return dir/subdir/, dir/file, etc?

Yes, it does. Try completing a path of several directories in bash. Even if there is a unique completion, each <TAB> will yield just one directory completion at a time. That's an intentional UX design, and I'd like to conform to it.

More generally, we can't reasonably return all completions in a tree hierarchy.

What I had assumed was happening is that when a directory would be returned as the only match, it also returned the contents of that directory, eg dir/ and dir/subdir (but not dir/subdir/file or any deeper in the hierarchy), which would cause dir/ to be filled in as the common prefix. However you are correct - even when show-all-if-ambiguous is turned on, bash will not display the contents of a directory until tab is pushed a second time.


report exact alternate alleles

Report exact alternate bases for A,C, G, T, rather than summing the frequency of all alts.
And suggest degenerate bases for those primers

This is done now, as in v0.4.0 plotly is used which includes exact alternates as a hovertip.
although I have not implemented degenerate primers suggestion yet


Update Acquia Solr Search module

Summary

Updates to the 3.x branch of solr search module.
Adds exclude config settings to ecms_basic_page feature to resolve search config rollbacks.
Removes old database search config (this won't impact live sites since we aren't touching the active config).
Removes patch from content_moderation_notifications module that was committed to latest release.
Metadata

Question
Answer

Did you use a meaningful pull request title?
yes

Did you apply meaningful labels to the pull request?
yes

Did you perform a self review first?
yes

Documentation reflects changes?
no

CHANGELOG reflects changes?
yes

Unit/Functional tests reflect changes?
no

Did you perform browser testing?
yes

Risk level
Medium

Relevant links
https://thinkoomph.jira.com/browse/RIGA-36

Me too! Thanks!


Access log include double quote at the user-agent field

Hi
I use some tool to do penetration test and see if modsecurity v3 will block the request successful.
In some testing case, user-agent includes double-quote in it, ie:
int2.diamond.trendmicro.com <IP_ADDRESS> - - [24/May/2017:07:38:35 +0000] "POST /api/v1/logs/ HTTP/1.1" 403 0- "'""<PHONE_NUMBER>1.000000 - /var/log/modsec/20170524/20170524-0738/20170524-073835-14956115151.000000 0 9454.000000 md5:d87287f684b5e55193b7402d421835bd
Modsecurity blocked the request succesfully, however, it will output the origin user-agent string into the access log too.
It cause our log parser (fluentd + elastisearch) failed in this case, and we don't have good solution for it.
I would like to support libmodsecurity can convert the double-quote as \x22 , so does other character between 0x7F-0x1F. I see this idea in nginx's access log.
https://serverfault.com/questions/584881/parseable-nginx-accesslog-files-with-delimiters
Thanks!

Hi @Pjack, Is this the nginx log or the audit log? For the auditlogs you can use straight the JSON. If that is on nginx logs, we may have a bug.

Hi @zimmerle ,
It is the index of audit log, sorry that I did not use precise wording.
The log is generated by  std::string Transaction::toOldAuditLogFormatIndex
https://github.com/SpiderLabs/ModSecurity/blob/v3/master/src/transaction.cc#L1318
We hopes to parse it into Elasticsearch server.
Thanks!

@Pjack  Can you confirm if the issue also happens if you enable JSON audit logs? (SecAuditLogFormat)

Hi @victorhora ,
SecAuditLogFormat is invalid in v3.
Here is my settings,
SecAuditEngine RelevantOnly
SecAuditLogType Parallel
SecAuditEngine RelevantOnly
SecAuditLogParts ABIJDEFHZ
SecAuditLog /var/log/modsec/audit.log
SecAuditLogStorageDir /var/log/modsec
SecAuditLogRelevantStatus "^(?:5|4(?!04))"
Transaction::toOldAuditLogFormatIndex  is only invoked under parallel mode.
https://github.com/SpiderLabs/ModSecurity/blob/v3/master/src/audit_log/writer/parallel.cc#L153

Ah right you're using v3 @Pjack ! My bad :)
Well, afaik, the only way I can think of now to avoid plain double quotes for going to the logs would be using the sanitize directives but I'm not sure if it would work well for you and these aren't currently implemented on v3 so this might be needed to be implemented as a new feature altogether. Unless I'm missing something and someone else comes up with a better idea :)

Hi @victorhora ,
Sorry that I don't know what is sanitize directive that I can't answer you.
I just know how nginx handle this situation, FYI.
https://serverfault.com/questions/584881/parseable-nginx-accesslog-files-with-delimiters
Thanks for your response and please consider to implement it in near future.

Support for AuditLogFormat was added as of https://github.com/SpiderLabs/ModSecurity/commit/63bef3d142b2ae25ed42d344c40729fb5f3d552e. Enabling JSON audit logging should solve this issue.


"Go to Definition" not working for packages installed by setup.py

Environment data

VS Code version: 1.59.1
OS and version: Win10
Python version (& distribution if applicable, e.g. Anaconda): Pythn 3.8.11 via Anaconda3
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda activate base
Value of the python.languageServer setting: Pylance

Expected behaviour
"Go to Definition" work for all packages what method was used to install (conda, setup.py, cmake, ...) .
Actual behaviour
As far as I can tell, Go to Definition is not working for all packages installed by "python setup.py install".
When I check, the installed package exists in site-packages, and I can run it without any problem.
By the way, Go to Definition didn't work even if I installed it with pip install git+https://***.git, so it might be a problem with the setup.py setting.
For example,
https://github.com/tnakaicode/pyticra.git
Logs
No output and Errors for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

Can you ellaborate? Is this a package you've installed, then use and then try to go-to-definition? Or is it something you're working on (so is the workspace root), and are also installing using this method?
If the former, do you see imports resolving?
If the latter, can you use editable installs so that there's no question as to what file "is" the library?

Do you mind also providing trace logs, per: https://github.com/microsoft/pylance-release/blob/main/TROUBLESHOOTING.md#filing-an-issue ?

I'm former.
After installing the package (the install was successful), I import it in another VSCode Workspace and try to run "Go to Definition", but I get "No Definition found".
There is no import error at runtime, and no warning from Pylance.
I can't understand what meaning "If the latter, can you use editable installs so that there's no question as to what file "is" the library?"
If I import in the Workspace of VSCode used to installation the package, the "Go to Definition" works and you can jump to the corresponding part in the "Workspace".
However, it is not possible to jump to the Install destination (under site-package).
By the way, I have confirmed that the target package is under site-package.
See https://github.com/microsoft/pylance-release/blob/main/TROUBLESHOOTING.md#filing-an-issue and set "python.analysis.logLevel": " Trace" and checked the Python Language Server, there is no log or error.
I got only the message "No Definition found".


⚠ Bofrost.at has degraded performance

In 70d0270, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1622 ms

Resolved: Bofrost.at performance has improved in 3203cce after 13 minutes.


DM precheck failed to check GTID when stop and then start from checkpoint with same task config

What did you do?
below is the steps I summarized from a user feedback, I hasn't reproduce it locally, but from the code seems it will fail

start a dm incr task with explicit GTID
run for a while, then purge some binlogs, and run another while
stop task, and checkpoint is kept
start again with same config, this time we will start from checkpoint actually
precheck "meta_position" failed with "ERROR 1236 (HY000): The slave is connecting using CHANGE MASTER TO MASTER_AUTO_POSITION = 1, but the master has purged binary logs containing GTIDs that the slave requires."

in precheck, we are always uses the position in task config, but since we are recover from checkpoint, we should uses the position in checkpoint instead as that's checkpoint position is the real position we will use, and might also need to consider this issue https://github.com/pingcap/dm/issues/1418
https://github.com/pingcap/tiflow/blob/9062d7c0cac6839d157379c38785f55fe2c3275a/dm/pkg/checker/binlog.go#L356-L368
What did you expect to see?
No response
What did you see instead?
No response
Versions of the cluster
dm version 7.5.3, upstream unknown right now,
current status of DM cluster (execute query-status <task-name> in dmctl)
(paste current status of DM cluster here)

/assign

My attempts to reproduce, but without expected errors:

Start a mysql docker instance with --log-bin=mysql-bin --binlog-format=ROW --server-id=1 --gtid_mode=ON --enforce-gtid-consistency=true;
Insert data into mysql, and start a mode=full dm task to initialize, then stop the full task;

show master status: xxx:1-11
show binary logs: mysql-bin.000001 to mysql-bin.000003

Start a mode=incremental dm task (config gtid xxx:1-11);
Insert data into mysql (saved to mysql-bin.000003)

show master status: xxx:1-13
show binary logs: mysql-bin.000001 to mysql-bin.000003

flush logs and purge binary logs to 'mysql-bin.000004'

show master status: xxx:1-13
show binary logs: mysql-bin.000004

Insert data into mysql (saved to mysql-bin.000004)

show master status: xxx:1-14
show binary logs: mysql-bin.000004

Stop incremental dm task
Start incremental dm task (same config gtid xxx:1-11), while checkpoint is xxx:1-14. Prechecker check based on 1-11 and found 12-14 is missing. However 12-13 is purged and we get error:

ERROR 1236 (HY000): Cannot replicate because the source purged required binary logs. Replicate the missing transactions from elsewhere, or provision a new replica from backup. Consider increasing the source's binary log expiration period. The GTID set sent by the replica is 'faa40251-8a9e-11ef-a97a-0242ac110002:1-11', and the missing transactions are 'faa40251-8a9e-11ef-a97a-0242ac110002:12-13'
This is different to the error mentioned above: "ERROR 1236 (HY000): The slave is connecting using CHANGE MASTER TO MASTER_AUTO_POSITION = 1, but the master has purged binary logs containing GTIDs that the slave requires."

> dmctl start-task precheck/incr-task.yaml
{
    "result": false,
    "msg": "",
    "sources": [
    ],
    "checkResult": "[code=26005:class=dm-master:scope=internal:level=medium], Message: fail to check synchronization configuration with type: check was failed, please see detail
        detail: {
                "results": [
                        {
                                "id": 2,
                                "name": "meta position check",
                                "desc": "check whether meta position is valid for db",
                                "state": "fail",
                                "errors": [
                                        {
                                                "severity": "fail",
                                                "short_error": "ERROR 1236 (HY000): Cannot replicate because the source purged required binary logs. Replicate the missing transactions from elsewhere, or provision a new replica from backup. Consider increasing the source's binary log expiration period. The GTID set sent by the replica is 'faa40251-8a9e-11ef-a97a-0242ac110002:1-11', and the missing transactions are 'faa40251-8a9e-11ef-a97a-0242ac110002:12-13'"
                                        }
                                ],
                                "instruction": "you should make sure your meta's binlog position is valid and not purged, and the user has REPLICATION SLAVE privilege",
                                "extra": "address of db instance - <IP_ADDRESS>:3308"
                        }
                ],
                "summary": {
                        "passed": false,
                        "total": 11,
                        "successful": 10,
                        "failed": 1,
                        "warning": 0
                }
        }"
}