Include Phil's VIMS Titan occultations in OPUS

See BYBTW meeting 4/16/2020
MRS: Table from Phil showing VIMS Titan occultations.  Can we generate similar information so that OPUS easily shows which raw VIMS and UVIS observations are occs?

For now, Mitch will look at putting any documentation on the main website.
BYBTW 3/11/2021

Eventually we will want to add the Titan occultations as a composite data product in OPUS, where the downloadable products are the individual raw files. This means we need a new OPUS ID, preview image, metadata, etc. This goes with #307.


Sample rate gets rounded to thousands

I'm trying to recognize an audio file with a sample rate of 22050 hz. I pass the correct value of the corresponding parameter: --rate 22050 but get an error which says that the sample rate is configured to 22000 hz which is not true.
#! /bin/bash

source "./sh/env.sh"
cat $1 | \
    python3 -m recognize_stream --host stt.tinkoff.ru --port 443 \
    --rate 22050 --num_channels 2 --encoding MPEG_AUDIO \
    --chunk_size 8192 --api_key $STT_TEST_API_KEY --secret_key $STT_TEST_SECRET_KEY

Audio header reports sample rate of 22050 hz, but recognition_config.sample_rate_herts = 22000

The same problem appears with the 44100 hz. Seems like the sample rate get rounded to thousands somewhere while being passed to the API.

Hi. This seems to be related to the fact that internally we resample audio from its original samplerate to the samplerate supported by acoustic model. Resampler that we use only supports handful of samplerate conversion modes, all of which assume that we can round samplerate to thousands, because there is actually almost no difference between 22050 or 22000 samplerate or between 44100 and 44000 from resampling standpoint. The error was caused by an incorrect samplerate check before resampling would occur (we forgot to account for rounding). The error is fixed now, I'll be updating our backend in a few hours. Thanks for reporting this!

Sorry for the delay. Finally, I've updated our backend, now samplerates 44100, 22050 and similar should work.

Should we close this issue?


make subject status dropdown multi-select

Issues
Closes #57

@samussiah Looks good! And added lot's of nice stuff in addition as always! Nice work. One thing that's confusing me right now though is that when I select Completed and Enrolled I only get the subjects from Completed. Am I doing something wrong or is that a webcharts problem? Didn't seem like the multi-select functionality itself got messed with, just those appearance tweaks

nice catch @pburnsdata , fix is in


bone missing

Describe the bug
missed some bone when generate UMA race asset using my fbx,as if uma ignore some bone by some reason,but i'm not sure!
Environment (please complete the following information):

Unity Version:2018.2.14
UMA Version:2.7.0
Platform Build (if not editor):

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

Hi, can you give us some screenshots of your model skeleton before and after in UMA?

Hi, can you give us some screenshots of your model skeleton before and after in UMA?

thank you for reply!
the following is 3dMax screenshot:

the following is unity screenshot,and the bone named Bip01 Head is missing:

Sorry it took me a while to reply.  What does the UMA bone hierachy look like?  Does it generate but missing the head bone? or not generate at all?
You're using UMA 2.7 but on Unity 2018.2? I'm surprised that even worked.

Sorry it took me a while to reply. What does the UMA bone hierachy look like? Does it generate but missing the head bone? or not generate at all?
You're using UMA 2.7 but on Unity 2018.2? I'm surprised that even worked.

I finaly soveled that issue，that missing bone was not attached to any vertex，it seemed that UMA thinks that bone is useless and ignore it. is this a bug?
and by the way, should I update my UMA to 2.8.0?

Not a bug - only bones that are used are brought into the model. We are considering ways to improve this functionality in R3.


[BUG] .NET SDK 6.0.1017 missing on Azure DevOps Hosted VS2017 Agents

Describe the bug
Running a unit test code that targets Microsoft.ServiceFabric.Actors Version="6.0.1017" results in an error on a hosted VS2017 agent.
The error:
Unhandled exception. Unhandled exception. System.IO.FileNotFoundException: Could not load file or assembly 'C:\Program Files\Microsoft Service Fabric\bin\Fabric\Fabric.Code\NS_9\Microsoft.ServiceFabric.Data.Impl.dll'. The system cannot find the path specified.
File name: 'C:\Program Files\Microsoft Service Fabric\bin\Fabric\Fabric.Code\NS_9\Microsoft.ServiceFabric.Data.Impl.dll'
   at System.Runtime.Loader.AssemblyLoadContext.LoadFromPath(IntPtr ptrNativeAssemblyLoadContext, String ilPath, String niPath, ObjectHandleOnStack retAssembly)
   at System.Runtime.Loader.AssemblyLoadContext.LoadFromAssemblyPath(String assemblyPath)
   at System.Reflection.Assembly.LoadFrom(String assemblyFile)
   at Microsoft.ServiceFabric.Data.ReliableStateManager..ctor(StatefulServiceContext serviceContext, ReliableStateManagerConfiguration configuration)

This is caused by a mismatch between the Nuget package version and the SDK on the build agent.
Area/Component:
programming modes in combination with Azure DevOps
To Reproduce
Steps to reproduce the behavior:

Install older SDK version to reproduce the error.
Install the latest version to resolve it.

Expected behavior
Azure DevOps agents should be equipped with the latest SDK, so we can run unit tests.
Observed  behavior:
Azure DevOps agent doesn't have the latest SDK
Service Fabric Runtime Version:
Windows 9.0.1017.9590
Windows .NET SDK 6.0.1017
If this is a regression, which version did it regress from?
We've seen this issue before.

Assignees: /cc @microsoft/service-fabric-triage

It's been fixed.


Fix inserting documents without id field

@boba-and-beer i think this breaks if '_id' is there for first document but missing for the rest?

Interesting edge- I will write a test case.


feedback changes

Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after):
Fix #
https://github.com/hlxsites/tlcgrp/pull/78
Test URLs:

Before: https://main----.hlx.page/
After: https://----.hlx.page/

closed


Update pydantic version

This addresses https://github.com/blueinkhq/blueink-client-python/pull/16

Closing as a duplicate of https://github.com/blueinkhq/blueink-client-python/issues/26, which has additional details


Add license for voornamen.json

Hi,
I am interested in using this file to detect personal information in order to help people protect their identity online. Is there a chance you would be willing to add a license for it? This is a non-profit project.
Thanks

Hello,
I've added a license. Good luck!

Thanks!


Update unstable nightly portable-simd imports

Import SimdOrd, SimdPartialEq from std::simd::cmp
Import SimdInt, SimdUint from std::simd::num
The most recent portable-simd subtree sync moved some traits out of the top level modules.

Thanks!


Updated manifest sample with personal tab url

Category

[x] Content fix
[ ] New article

What's in this Pull Request?
SPFx 1.10 now supports personal tabs. Updating the teams manifest sample with the url to use in case of an SPFx based personal tab.

thx @vman, great and valuable add-on for the docs.


[Feature] Captcha

Support to decentralized captchas, for preventing SPAM on apps, like Freenet does

That sounds like it'd be a cool application to make on top of Dat.


[NUCLEO_F031K6] Add HSI calibration default value

Fix issue with MBED_A9 and EXAMPLE_1 tests.
Sorry for all the other commits, I am not able to remove them. Even with a rebase.

I'll do squash manually ;)

ok thanks a lot  :-)

Done, commit 105bb7bc5520e1fc6146f is on master


DAT-17457

fix: .github/workflows/run-tests.yml: run snowflake tests only if PR is merged to master
Impact

[ ] Bug fix (non-breaking change which fixes expected existing functionality)
[ ] Enhancement/New feature (adds functionality without impacting existing logic)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description

Things to be aware of

Things to worry about

Additional Context

This is going to fail on PR builds. The Snowflake tests also need to be disabled on PR runs.

added a condition to Skip integration test if testSystem is 'snowflake'  if: ${{ matrix.testSystem != 'snowflake' }}


Fixed ES6 modules imports

The change fixes ES6 module imports and fixes issue #310.
All tests are green!

Thanks @JoeLanglois! Could you rebase with master? Then I'll merge this in :)

I'll sound like a total noob but I really have no idea what you mean by that.
You wish for me to git rebase my fork's master branch to your repo's master branch?

Basically just pull down master into yours, then push back up :) It's out of sync with master at the moment.


Remove legacy XDS_AUTH and PILOT_ENABLE_XDS_IDENTITY_CHECK feature flags

@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

integ-security_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
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 can we please leave this flag? This is needed for deployments that run Envoy before Istiod for mTLS handling and communicates with Istiod on plain text. Alternatively people have to rely on XDS_AUTH_PLAINTEXT setting to false.

Not sure I understand why these would be disabled? Isn't there an
authenticator for that mode already?
On Thu, Apr 27, 2023 at 2:09 AM Rama Chavali @.***>
wrote:

@howardjohn https://github.com/howardjohn can we please leave this
flag? This is needed for deployments that run Envoy before Istiod for mTLS
handling and communicates with Istiod on plain text. Alternatively people
have to rely on XDS_AUTH_PLAINTEXT setting to false.
—
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/44586#issuecomment-1525209068, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXONWFCMXDTYTYD4WC3XDIZS5ANCNFSM6AAAAAAXM6QWOA
.
You are receiving this because you were mentioned.Message ID:
@.***>

No. There is no authenticator for that mode, except for xfcc - that is not fully tested in cases.

No. There is no authenticator for that mode, except for xfcc - that is not fully tested in cases.

Sorry I don't understand what you are doing today. No auth at all in Istiod?
If so, where is the XFCC not sufficient? I thought you added it specifically for this purpose?

Never mind test env ( I was lazy and not updating credentials).
I think it is ok to remove it - but we should make sure XFCC is usable and
enabled by default ( once CIDR for envoy-in-front-of-istiod is set or we
have a
similar setting to check the identity of the envoy using mTLS or JWT).
The auth does need a serious revamp, including the non-mTLS port ( it would
be great to stop calling them 'plain text' - ztunnel or
network security do encrypt ).
The use case I have in mind and would like to get working ( not on this PR)
is an app like proxyless gRPC or something that is using
XDS for whatever purpose, making a call to istiod:15010 and having ztunnel
take care of encryption and authn. No need to have an agent
or deal with special craziness to connect to istiod.
On Thu, Apr 27, 2023 at 8:49 AM John Howard @.***>
wrote:

@.**** commented on this pull request.
In pilot/pkg/features/pilot.go
https://github.com/istio/istio/pull/44586#discussion_r1179375245:

@@ -427,15 +427,6 @@ var (
EnableUnsafeAdminEndpoints = env.Register("UNSAFE_ENABLE_ADMIN_ENDPOINTS", false,
"If this is set to true, dangerous admin endpoints will be exposed on the debug interface. Not recommended for production.").Get()

XDSAuth = env.Register("XDS_AUTH", true,

This doesn't impact the plaintext port afaik, that one is still open. But
like you said we need to improve that.
So I am not sure why this would be used for test env - that might mean I
am misunderstanding its usage?
—
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/44586#discussion_r1179375245, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAUR2W56WK6QUJWHWO4RGDXDKIR3ANCNFSM6AAAAAAXM6QWOA
.
You are receiving this because your review was requested.Message ID:
@.***>

XFCC is on if you set a trusted GW CIDR today. Just need to see why that isn't meeting @ramaraochavali's use case I think.
ztunnel case is interesting...

Sorry - I didn't ask a question about release note, I think I know the
answer. Just to clarify it in the text for the users, in particular normal
users.
"If you upgrade from version 1.xx, no change"
If you are on an older version and have invalid credentials - any upgrade
would fail anyways, but there was a way to set the flag ( which would be a
horrible idea,
better to rollback and fix the credentials )
On Thu, Apr 27, 2023 at 8:48 AM John Howard @.***>
wrote:

@.**** commented on this pull request.
In releasenotes/notes/drop-legacy-xds-auth.yaml
https://github.com/istio/istio/pull/44586#discussion_r1179373647:

@@ -0,0 +1,6 @@
+apiVersion: release-notes/v2
+kind: feature
+area: traffic-management
+releaseNotes:
+- |

Removed the XDS_AUTH and PILOT_ENABLE_XDS_IDENTITY_CHECK feature flags.

It just means:

If you are super advanced user setting these, you are broken and
need to find alternatives/ask us to add the flag back/etc
Normal users - should be no change really. Only if you are on a
super old version AND are connecting with invalid credentials would you be
broken; no standard user should be doing this

—
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/44586#discussion_r1179373647, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAUR2WTAEQXNB6KQFBJLCLXDKINZANCNFSM6AAAAAAXM6QWOA
.
You are receiving this because your review was requested.Message ID:
@.***>

To enforce xfcc we have the following challenges (Solvable) but my point is we may run in to others

XDS_AUTH_PLAINTEXT - Needs to be set to true. Otherwise XFCC is not enforced. This is an obscure flag which no one knows about unless you look at the code
For Envoy running before Istiod when it directly connects to local cluster (local istiod) instead of connecting to any istiod , the xfcc header is not set as it does go via regular route and http connection manager. So local istiod's envoy's xfcc authentication fails. We need to find a way to do this.

So I think xfcc authenticator in general needs to be production ready and handle these better. Also the gateway CIDR part that @costinm mentioned is an important one.

On Thu, Apr 27, 2023 at 9:57 PM Rama Chavali @.***>
wrote:

To enforce xfcc we have the following challenges (Solvable) but my point
is we may run in to others

XDS_AUTH_PLAINTEXT - Needs to be set to true. Otherwise XFCC is not
enforced. This is an obscure flag which no one knows about unless you look
at the code

I think this is a separate issue / path - I do agree, and for the 'safe'
istio I think we have auth by default on 15010 if the network is secure or
Istiod is behind
ztunnel ( or turn it off otherwise ). I don't know if we can turn it on by
default in regular Istio - but we should make it more visible, as well as
the obscure flag to
turn it off completely.

But in the new ambient world - I would avoid calling it 'plaintext', and we
will need John's MDS PR, XFCC.
CIDR or NetworkPolicy can be used to make sure the workload in front is the
waypoint for Istiod.
Istiod also has a database of IP->identity now (for ambient), so if ztunnel
is used ( or ztunnel equivalent is part of the native network) it can get
the peer identity from the authenticated IP.

For Envoy running before Istiod when it directly connects to local
cluster (local istiod) instead of connecting to any istiod , the xfcc
header is not set as it does go via regular route and http connection
manager. So local istiod's envoy's xfcc authentication fails. We need to
find a way to do this.

So I think xfcc authenticator in general needs to be production ready and
handle these better. Also the gateway CIDR part that @costinm
https://github.com/costinm mentioned is an important one.

Not sure what production ready means here - more testing ? We certainly
need more options for auth, docs for CIDR or NetworkPolicy, etc.
But for this PR purpose - besides making sure it only applies to 15012, is
there any other concern ? Are you having the gateway connect to the TLS
port with
auth off ? Trying to understand all cases, I would like for 'safe' to have
better defaults, including for a proper waypoint in front of Istiod.
BTW - not sure if you are familiar with Google IAP or similar 'auth
gateways', but if Istiod trusts the waypoint ( NetworkPolicy, CIDR or mTLS
validating
the waypoint identity - or a JWT in the headers, as IAP is using), we don't
really need XFCC parsing, passing the identity as a simple and clean header
may work better. XFCC is useful if we need the original cert - but it's
mostly useless, we still need to trust the waypoint.
Message ID: @.***>

XDS_AUTH_PLAINTEXT - Needs to be set to true. Otherwise XFCC is not enforced. This is an obscure flag which no one knows about unless you look at the code

Aren't you currently doing no auth (xds_auth=false)?

For Envoy running before Istiod when it directly connects to local cluster (local istiod) instead of connecting to any istiod , the xfcc header is not set as it does go via regular route and http connection manager. So local istiod's envoy's xfcc authentication fails. We need to find a way to do this.

You could have the local envoy just have a static XFCC possibly. Or use JWT. A bit hacky

Aren't you currently doing no auth (xds_auth=false)?

Yes we are. Because we are not able to validate xfcc yet. That is the reason I am requesting to wait on this removal for a bit :-)

/retest

@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

integ-security_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
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.

Hmm the test also depends on this. But for bad reasons. Need to fix it.

You could have the local envoy just have a static XFCC possibly. Or use JWT. A bit hacky

Yes. We can do that. Let me try that. Can we please hold on to this till we try that?

@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

integ-security_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-security

bookinfo-build_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test bookinfo-build

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.

@ramaraochavali did you get a chance to look into this

Yeah no problem
On Fri, Aug 11, 2023 at 7:04 AM Rama Chavali @.***>
wrote:

Ah. Sorry. It slipped out of my mind. Can I get back to you by Monday?
—
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/44586#issuecomment-1674848264, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXLHD6KNM66PQGOHKWTXUY3VDANCNFSM6AAAAAAXM6QWOA
.
You are receiving this because you were mentioned.Message ID:
@.***>

I am not able to fully verify XFCC as it needed some more changes from our side. Let us remove these flags and if we run in to issue - I will open another PR

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

integ-security_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-security

bookinfo-build_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test bookinfo-build

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

integ-basic-arm64_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
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

integ-security_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-security

bookinfo-build_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test bookinfo-build

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

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

unit-tests_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
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

integ-security_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-security

bookinfo-build_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test bookinfo-build

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

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

unit-tests_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test unit-tests

release-test_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
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

integ-security_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-security

bookinfo-build_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test bookinfo-build

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

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

unit-tests_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test unit-tests

release-test_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test release-test

integ-distroless_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
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

integ-security_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-security

bookinfo-build_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test bookinfo-build

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

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

unit-tests_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test unit-tests

release-test_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test release-test

integ-distroless_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-distroless

integ-cni_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
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

integ-security_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-security

bookinfo-build_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test bookinfo-build

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

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

unit-tests_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test unit-tests

release-test_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test release-test

integ-distroless_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-distroless

integ-cni_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-cni

integ-telemetry_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-telemetry

integ-telemetry-istiodremote_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
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

integ-security_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-security

bookinfo-build_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test bookinfo-build

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

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

unit-tests_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test unit-tests

release-test_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test release-test

integ-distroless_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-distroless

integ-cni_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-cni

integ-telemetry_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-telemetry

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

integ-ipv6_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
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

integ-security_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-security

bookinfo-build_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test bookinfo-build

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

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

unit-tests_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test unit-tests

release-test_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test release-test

integ-distroless_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-distroless

integ-cni_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-cni

integ-telemetry_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-telemetry

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

integ-ipv6_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-ipv6

integ-security-multicluster_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
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

integ-security_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-security

bookinfo-build_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test bookinfo-build

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

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

unit-tests_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test unit-tests

release-test_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test release-test

integ-distroless_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-distroless

integ-cni_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-cni

integ-telemetry_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-telemetry

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

integ-ipv6_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-ipv6

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

integ-ds_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
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

integ-security_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-security

bookinfo-build_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test bookinfo-build

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

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

unit-tests_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test unit-tests

release-test_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test release-test

integ-distroless_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-distroless

integ-cni_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-cni

integ-telemetry_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-telemetry

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

integ-ipv6_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-ipv6

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

integ-ds_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-ds

integ-telemetry-mc_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
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

integ-security_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-security

bookinfo-build_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test bookinfo-build

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

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

unit-tests_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test unit-tests

release-test_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test release-test

integ-distroless_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-distroless

integ-cni_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-cni

integ-telemetry_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-telemetry

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

integ-ipv6_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-ipv6

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

integ-ds_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-ds

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

integ-security-istiodremote_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
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

integ-security_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-security

bookinfo-build_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test bookinfo-build

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

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

unit-tests_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test unit-tests

release-test_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test release-test

integ-distroless_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-distroless

integ-cni_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-cni

integ-telemetry_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-telemetry

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

integ-ipv6_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-ipv6

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

integ-ds_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-ds

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

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

integ-operator-controller_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
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

integ-security_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-security

bookinfo-build_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test bookinfo-build

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

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

unit-tests_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test unit-tests

release-test_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test release-test

integ-distroless_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-distroless

integ-cni_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-cni

integ-telemetry_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-telemetry

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

integ-ipv6_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-ipv6

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

integ-ds_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-ds

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

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

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

analyze-tests_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
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

integ-security_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-security

bookinfo-build_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test bookinfo-build

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

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

unit-tests_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test unit-tests

release-test_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test release-test

integ-distroless_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-distroless

integ-cni_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-cni

integ-telemetry_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-telemetry

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

integ-ipv6_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-ipv6

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

integ-ds_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-ds

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

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

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

analyze-tests_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test analyze-tests

integ-pilot-multicluster_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
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

bookinfo-build_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test bookinfo-build

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

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

unit-tests_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test unit-tests

release-test_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test release-test

integ-distroless_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-distroless

integ-cni_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-cni

integ-telemetry_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-telemetry

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

integ-ipv6_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-ipv6

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

integ-ds_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-ds

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

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

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

analyze-tests_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test analyze-tests

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

integ-security_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
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

bookinfo-build_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test bookinfo-build

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

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

unit-tests_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test unit-tests

release-test_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test release-test

integ-distroless_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-distroless

integ-cni_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-cni

integ-telemetry_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-telemetry

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

integ-ipv6_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-ipv6

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

integ-ds_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-ds

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

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

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

analyze-tests_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test analyze-tests

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

integ-security_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-security

integ-pilot_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
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

bookinfo-build_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test bookinfo-build

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

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

unit-tests_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test unit-tests

release-test_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test release-test

integ-distroless_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-distroless

integ-cni_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-cni

integ-telemetry_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-telemetry

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

integ-ipv6_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-ipv6

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

integ-ds_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-ds

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

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

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

analyze-tests_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test analyze-tests

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

integ-security_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-security

integ-pilot_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-pilot

lint_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
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

bookinfo-build_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test bookinfo-build

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

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

unit-tests_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test unit-tests

release-test_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test release-test

integ-distroless_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-distroless

integ-cni_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-cni

integ-telemetry_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-telemetry

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

integ-ipv6_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-ipv6

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

integ-ds_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-ds

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

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

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

analyze-tests_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test analyze-tests

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

integ-security_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-security

integ-pilot_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-pilot

lint_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test lint

integ-ambient_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
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

bookinfo-build_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test bookinfo-build

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

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

unit-tests_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test unit-tests

release-test_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test release-test

integ-distroless_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-distroless

integ-cni_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-cni

integ-telemetry_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-telemetry

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

integ-ipv6_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-ipv6

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

integ-ds_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-ds

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

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

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

analyze-tests_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test analyze-tests

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

integ-security_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-security

integ-pilot_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-pilot

lint_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test lint

integ-ambient_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-ambient

integ-helm_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
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

bookinfo-build_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test bookinfo-build

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

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

unit-tests_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test unit-tests

release-test_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test release-test

integ-distroless_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-distroless

integ-cni_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-cni

integ-telemetry_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-telemetry

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

integ-ipv6_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-ipv6

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

integ-ds_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-ds

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

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

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

analyze-tests_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test analyze-tests

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

integ-security_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-security

integ-pilot_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-pilot

lint_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test lint

integ-ambient_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-ambient

integ-helm_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-helm

integ-pilot-istiodremote_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
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

bookinfo-build_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test bookinfo-build

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

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

unit-tests_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test unit-tests

release-test_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test release-test

integ-distroless_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-distroless

integ-cni_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-cni

integ-telemetry_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-telemetry

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

integ-ipv6_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-ipv6

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

integ-ds_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-ds

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

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

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

analyze-tests_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test analyze-tests

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

integ-security_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-security

integ-pilot_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-pilot

lint_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test lint

integ-ambient_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-ambient

integ-helm_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-helm

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

release-notes_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test release-notes

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

bookinfo-build_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test bookinfo-build

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

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

unit-tests_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test unit-tests

release-test_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test release-test

integ-distroless_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-distroless

integ-cni_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-cni

integ-telemetry_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-telemetry

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

integ-ipv6_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-ipv6

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

integ-ds_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-ds

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

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

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

analyze-tests_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test analyze-tests

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

integ-security_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-security

integ-pilot_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-pilot

lint_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test lint

integ-ambient_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-ambient

integ-helm_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-helm

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

release-notes_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test release-notes

integ-pilot-istiodremote-mc_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
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

bookinfo-build_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test bookinfo-build

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

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

unit-tests_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test unit-tests

release-test_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test release-test

integ-distroless_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-distroless

integ-cni_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-cni

integ-telemetry_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-telemetry

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

integ-ipv6_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-ipv6

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

integ-ds_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-ds

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

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

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

analyze-tests_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test analyze-tests

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

integ-security_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-security

integ-pilot_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-pilot

lint_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test lint

integ-ambient_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-ambient

integ-helm_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test integ-helm

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

release-notes_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test release-notes

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

gencheck_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
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

bookinfo-build_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test bookinfo-build

integ-security_istio
7cc0b6616cea4476f96cba95557c8aec0fb62fe2
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

bookinfo-build_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test bookinfo-build

integ-security_istio
ec099af8987c19d1d89bd9aa5bb4d9c805967225
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

bookinfo-build_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test bookinfo-build

integ-security_istio
ec099af8987c19d1d89bd9aa5bb4d9c805967225
link
true
/test integ-security

unit-tests-arm64_istio
48d5afa734f8a805265342ddaea8331b848b1712
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

bookinfo-build_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test bookinfo-build

integ-security_istio
ec099af8987c19d1d89bd9aa5bb4d9c805967225
link
true
/test integ-security

unit-tests-arm64_istio
48d5afa734f8a805265342ddaea8331b848b1712
link
true
/test unit-tests-arm64

unit-tests_istio
48d5afa734f8a805265342ddaea8331b848b1712
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

bookinfo-build_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test bookinfo-build

unit-tests-arm64_istio
48d5afa734f8a805265342ddaea8331b848b1712
link
true
/test unit-tests-arm64

unit-tests_istio
48d5afa734f8a805265342ddaea8331b848b1712
link
true
/test unit-tests

integ-security_istio
48d5afa734f8a805265342ddaea8331b848b1712
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

bookinfo-build_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test bookinfo-build

integ-security_istio
6b2d66fbcf32bf9151d768fbde82a578b66d38e3
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

bookinfo-build_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test bookinfo-build

integ-security_istio
b3520bf964975cbd56026ddc7ab84985f4989946
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.

/test integ-security

@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

bookinfo-build_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test bookinfo-build

integ-security_istio
b3520bf964975cbd56026ddc7ab84985f4989946
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

bookinfo-build_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test bookinfo-build

integ-security_istio
b3520bf964975cbd56026ddc7ab84985f4989946
link
true
/test integ-security

integ-ds_istio
b3520bf964975cbd56026ddc7ab84985f4989946
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

bookinfo-build_istio
b6e884239f878a3dfb4e743b60ef110f829cbc81
link
true
/test bookinfo-build

integ-ds_istio
b3520bf964975cbd56026ddc7ab84985f4989946
link
true
/test integ-ds

integ-security_istio
b3520bf964975cbd56026ddc7ab84985f4989946
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.


Speed of machines

Now the machines of AR is a bit slow，do you want to give sth. make them faster？

The alpha builds have different teirs of motors and coils which you should be able to use to speed up most machines.

Yes I know。


Recovering EasyRSA?

If we lose EasyRSA the deployment is degraded since you cannot add more units.
Adding a new EasyRSA unit with juju add-unit easyrsa gets etcd in a bad state:
etcd/0*     active    idle   1        <IP_ADDRESS>  2379/tcp  Errored with 0 known peers

And on the etcd logs we get:
018-04-27 11:52:37 INFO juju-log certificates:1: Invoking reactive handler: reactive/etcd.py:63:check_cluster_health
2018-04-27 11:52:38 WARNING juju-log certificates:1: Notice:  Unit failed cluster-health check
2018-04-27 11:52:38 INFO juju-log certificates:1: b'failed to check the health of member 1de2133320b227fd on https://<IP_ADDRESS>:2379: Get https://<IP_ADDRESS>:2379/health: remote error: tls: bad certificate\
nmember 1de2133320b227fd is unreachable: [https://<IP_ADDRESS>:2379] are all unreachable\nfailed to check the health of member 58177fbfad385493 on https://<IP_ADDRESS>:2379: Get https://<IP_ADDRESS>:2379/heal
th: remote error: tls: bad certificate\nmember 58177fbfad385493 is unreachable: [https://<IP_ADDRESS>:2379] are all unreachable\nfailed to check the health of member c6602f1c727f3723 on https://<IP_ADDRESS>:2379
: Get https://<IP_ADDRESS>:2379/health: remote error: tls: bad certificate\nmember c6602f1c727f3723 is unreachable: [https://<IP_ADDRESS>:2379] are all unreachable\ncluster is unhealthy\n'
2018-04-27 11:52:38 DEBUG certificates-relation-changed client: etcd cluster is unavailable or misconfigured
2018-04-27 11:52:38 INFO juju-log certificates:1: Invoking reactive handler: reactive/tls_client.py:15:store_ca
2018-04-27 11:52:39 INFO juju-log certificates:1: Writing CA certificate to /var/snap/etcd/common/ca.crt
2018-04-27 11:52:39 INFO juju-log certificates:1: Writing CA certificate to /usr/local/share/ca-certificates/etcd.crt
2018-04-27 11:52:39 DEBUG certificates-relation-changed Updating certificates in /etc/ssl/certs...
2018-04-27 11:52:40 DEBUG certificates-relation-changed 0 added, 0 removed; done.
2018-04-27 11:52:40 DEBUG certificates-relation-changed Running hooks in /etc/ca-certificates/update.d...
2018-04-27 11:52:40 DEBUG certificates-relation-changed done.

Here is an idea we also employ on the kubernetes-masters and that seems to be halfway implemented on the easyrsa. We could store in the leader any certificates/configurations we need to revive a lost easyrsa charm. This makes sense because we have to solve HA (more like recovery not HA) on a single place, the juju controller. easyrsa charm seems to be setting storing some certificates on the leader context but it does not seem to recover them at any point https://github.com/juju-solutions/layer-easyrsa/blob/master/reactive/easyrsa.py#L179 . It could be as easy as storing the certificates issued and recalling them (https://github.com/juju-solutions/layer-easyrsa/blob/master/reactive/easyrsa.py#L288).

Related issue: https://github.com/juju-solutions/layer-easyrsa/issues/9

Does anyone know of any progress on this? I'm in the process of spooling a node in my cluster which holds easyrsa, I have no idea how to proceed. Hasn't this come up yet with customers of Canonical icw CDK?

This was fixed. See https://bugs.launchpad.net/charm-easyrsa/+bug/1835258.
If you lose or remove your easyrsa unit, you can add a new one and it will recover the CA cert/key from leadership data (stored on the Juju controller).


Pubchem compound id duplicated/wrong

Hello,
Description of the issue:
m01778c and m02646c share the same pubchem.compound ID.
Expected feature/value/output:
m01778c should be 5461071 and m02646c should be 445639.
Current feature/value/output:
"m01778c"	"m01778"	"elaid"	"C00712"	"HMDB00573"	"CHEBI:27997"	"445639"	"LMFA01030073"	""	"HC00830"	"elaid"	"MNXM11476;MNXM306;MNXM92305"	"m01778c"
"m02646c"	"m02646"	"ocdcea"	"C00712"	"HMDB00207"	"CHEBI:16196"	"445639"	"LMFA01030002"	""	"HC00510"	"ocdcea"	"MNXM306"	"m02646c"
Reproducing these results:
NA
I hereby confirm that I have:

[X] Tested my code on my own computer for running the model
[X] Done this analysis in the master branch of the repository
[X] Checked that a similar issue does not exist already

@jorgemlferreira the correction of PubChem ids can be made to the metabolite annotation file.


pre-commit: PR118197

Link: https://github.com/llvm/llvm-project/pull/118197
Requested by: @dtcxzyw

/add-label reviewed
/close


Analyzer crashing in QSPI mode with valueError

Hello!
So I've been playing around with a capture that includes some QSPI traffic (from a Micron M5QU128), and am running into a error whenever I try to instantiate the SPI Flash analyzer over the Simple Parallel analyzer:
SPI Flash error - ValueError('byte must be in range(0, 256)')
  File "/home/<path>/.config/Logic/Marketplace/33/SPIFlashAnalyzer.py", line 184, in decode
    self._miso_data.extend(fake_frame.data["miso"])

I haven't seen any values in the output of the parallel analyzer that are greater than a single byte (and have tried both with and without the CS line included). I've tried both the version that is downloadable through Logic (as seen above) and from getting a local clone of the repository, with the same results.
I'm glad to help debug this/submit a pull request, since I haven't managed to create a minimal test file (and can't share this one, sorry.) If you have any suggestions for where to start poking at this, I would greatly appreciate them.
Thanks!

Sage

Hi Sage, what are you parallel analyzer settings? I don't think I documented it well.
Printing fake_frame.data["miso"] and then tracing back where the bad value comes from would be my next step.

The parallel analyzer settings are:
    D0--D3: DQ0--DQ3 (MOSI, MISO, WP#, HOLD#)
    D4--D14: not set
    D15: S# (CS)
    Clock: CLK
    Edge: Rising edge
    (Not shown in table/terminal, but that doesn't change anything)

From poking it a little bit, it does end up with a (fake) frame with {'mosi': [15467], 'miso': [768]}, which is indeed above the size for a byte.
I'm reasonably sure that the reason for this happening is that the chip is already using Quad-SPI commands, so the analyzer doesn't see a known command to enter QSPI mode and thus doesn't properly deal with data on all four lines.
These values in particular are coming from lines 137 and 138 https://github.com/adafruit/Logic2-SPIFlash/blob/c8b3dbdb902be6f7c0613ee388c567a9bd5b5a26/SPIFlashAnalyzer.py#L137-L138 which properly mask off the initial data. When the fake frame is created on line 146,  self._clock_count = 7, self._mosi_out = 0b11110001101011 / 0x3c6b, and self._miso_in = 0b1100000000 / 0x300. From doing a bit more poking, this is due to the previous transaction being only 54 clock cycles, which wouldn't make sense if it were just normal SPI but since it is using fast quad-output reads (command 0x6b), the timings are different (8 cycles for the command, 24 cycles for the address, 4 dummy cycles, and then 7 bytes @ 2 cycles each = 54).
So, this is actually two separate but related bugs:

The analyzer doesn't (properly) handle captures where QSPI mode is already active (and thus doesn't have an enter command) or when quad-output/etc commands are used in 'normal' SPI mode
self._mosi_out/self._miso_in aren't zeroed when a new transaction occurs

The second issue is pretty simple to fix. My thoughts on the first issue would be to extend the set of CONTINUE_COMMANDS and data commands to handle more commands from more chips. Depending on how much use this extension ends up getting, it might be worth parameterize this by chip manufacturer but that is more of a stretch goal.

Now that I've written out that slight novel on figuring out the issue, I would be glad to help fix these and put in a pull request. The first one seems reasonably simple to implement by just increasing the known commands, and the second one could be handled by zero'ing self._mosi_out/self._miso_in when a new transaction occurs around here https://github.com/adafruit/Logic2-SPIFlash/blob/main/SPIFlashAnalyzer.py#L117-L122
Do these changes seem reasonable to you? I'm glad to implement them and give you a pull request.

Ya, they seem totally reasonable. I'm happy to review and merge changes in.
It feels like we may want a setting that says "I'm already in a QSPI mode" if your data doesn't have any commands in it at all (just continuations.)

Here is a .sal for a file which gives this error and is fixed by #3. Also attached is datasheet.
Note there is an additional fix needed for continuous decoding to work (in particular - the comparison at https://github.com/Wmyers559/Logic2-SPIFlash/blob/fix_qspi_crash/SPIFlashAnalyzer.py#L174 needs to be against 0xa5, technically the datasheet just says high/low nibbles will be complements, may be safer to just check high nibble only for 0xa and ignore low nibble in case other manufactures do this different).
spi qspi demo.zip
Infineon-S25FL128S_S25FL256S_128_Mb_(16_MB)256_Mb(32_MB)_3.0V_SPI_Flash_Memory-DataSheet-v18_00-EN.pdf

Here is my changes for reference too - https://github.com/colinoflynn/Logic2-SPIFlash/tree/qspi_updates_continous (I've merged in the PR to my repo)

Thanks for the comment @colinoflynn. I've merged #3 and I think this is fixed by it. (I haven't been using this decoder recently.)


Updating websites to use new SDK version

Updating the SDK version for websites
Description

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

add to S169


update for missing a couple possibly unsafe xml parser

Fixes #901

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

Sorry no, I do not believe this deserves a CVE. See my previous comments.


1707 new trs domains

Context
We need to create domain names for TRS apps:
Configure non-production environments: dev, test, pre-prod
Follow naming in teaching-record-system/terraform/domains/environment_domains/config at main · DFE-Digital/teaching-record-system
Changes proposed in this pull request

Domain authorise-access-to-a-teaching-record.education.gov.uk and mapped to [trs-production-authz.teacherservices.cloud]
Domain teaching-record-system.education.gov.uk and mapped to trs-production-ui.teacherservices.cloud
Create frontdoors for each hosted zone

Checklist

[ ] Attach to Trello card
[x] Rebased master
[x] Cleaned commit history
[x] Tested by running locally

 New TRS domains


Allow RRsets return size (top) to be configurable

Added the ability to modify the maximum number of record sets returned per page. Azure allows returning up to 1000 records per page. The default has been set to 100, which is the value set by Azure if not specified.

Does the azure client paginate automatically and this is just setting the page size or is it hard limiting the number of records returned and thus stuff is missing?
Haven't used Azure with large zones (or a lot of zones) so not sure myself. Azure docs make me think it's just limiting, but I suppose the python client lib could be paginating automatically.

Does the azure client paginate automatically and this is just setting the page size

Correct, It's just setting the page size. Larger zones take quite a while to compare due to their upper limit of just 1000 records returned per page. https://learn.microsoft.com/en-us/python/api/azure-mgmt-privatedns/azure.mgmt.privatedns.operations.recordsetsoperations?view=azure-python#azure-mgmt-privatedns-operations-recordsetsoperations-list


River only imports ~500k wikipedia documents into index.

This weekend I tried importing wikipedia into an ES index using the river. Only about 500K documents were imported. Because I am running on a managed ES cluster (QBox) I couldn't check the server logs to see why the import stopped.
But, since the readme.md indicates that rivers were deprecated and to look at stream2es instead, I decided to try that. When importing wikipedia using stream2es it also stopped at about 500k documents. This time I was able to see the logs and opened an issue with the stream2es project
stream2es indexing of wikipedia fails at about 540K docs with IOException: unexpected end of stream
(see this issue for the stack trace)
The comment on that issue indicates that it might be a problem with the WikiXMLSAXParser class which stream2es depends on and is maintained in this project. This would explain why both using the river and stream2es failed at about the same place in the import process. Perhaps the wikipedia dump file format changed in a way that broke this parser?
At the end of the day I would love to get wikipedia imported for a project I am working on whether or not I use the river or stream2es. Has anyone gotten wikipedia to import recently? Any tips on how to get this to work?

Might be better to download first locally the Wikipedia dump instead of streaming it ?
I guess it could be caused by a Network issue?

Does the river plugin support downloading a local copy? Is there a parameter that I need to set when I start the river?

This should work:
{
    "type" : "wikipedia",
    "wikipedia" : {
        "url" : "file:/path/to/dump"
    }
}

Thanks, since I am using a managed ES cluster (QBox) I dont have access to the filesystem of the node so I couldn't try this for the river. But was able to try using stream2es since that is running on another machine that I manage. Since it looks like the two projects share the core bz2 streaming code and SAX parser I thought I'd add the results to this issue as well
Per the recommendation from @dadoonet, I downloaded the dump locally and ran stream2es using the local dump file. This time it did not fail at ~500k documents. It is still running and chugging along at about 13.5MM documents so far so I assume this should finish. @drewr mentioned I should expect 15MM or so documents when it is done indexing
So, it would appear that streaming the dump file from the server causes the issue. It is a nice feature to be able to process the file directly over the network stream rather than having to have the extra step (and disk space) of downloading an 11GB+ dump file first, but at least this gives me a workaround to keep developing.
Thanks for the help!

This project has been stopped since elasticsearch 2.0.


Our .bat wrapper scripts don't always keep the exit code (ERRORLEVEL) intact

Right now c "leave 1" will set ERRORLEVEL to 1 (as it should). But svn st -q | c "leave 1" leaves the ERRORLEVEL at 0.  However, adding exit /b %errorlevel% to the end of "c.bat" restores the errorlevel as it should be (to 1) in either case.
So, we need to add this to all our .bat wrappers.

I suppose further testing is needed to see if the same holds true on Linux or OSX...

Appears to work fine on OSX (and therefore probably Linux as well).


Compiling bug

mike@DESKTOP-IU99086:~/sappworks/rustorm$ cargo build
   Compiling rustorm v0.10.7 (/home/mike/sappworks/rustorm)
error[E0599]: no method named `safe_name` found for type `dao::TableName` in the current scope
  --> src/table.rs:29:19
   |
29 |         self.name.safe_name()
   |                   ^^^^^^^^^

error[E0599]: no method named `safe_complete_name` found for type `dao::TableName` in the current scope
  --> src/table.rs:33:19
   |
33 |         self.name.safe_complete_name()
   |                   ^^^^^^^^^^^^^^^^^^
   |
   = help: did you mean `complete_name`?

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0599`.
error: Could not compile `rustorm`.

To learn more, run the command again with --verbose.
mike@DESKTOP-IU99086:~/sappworks/rustorm$ rustc -V
rustc 1.30.0-nightly (63d51e89a 2018-09-28)

fix bug. ref #4


Core.JavaScript embedder on O365-D

Hi guys,
small thing I noticed by running [Core.JavaScript.Embedder] (https://github.com/OfficeDev/PnP/tree/dev/Samples/Core.JavaScript/Core.JavaScript.Embedder) on 365 Dedicated tenant; referencing V15 assemblies.
Line 49 in Program.cs
foreach (var link in
 links.Where(l => l.Title.Equals("MyTestCustomAction", StringComparison.OrdinalIgnoreCase)))

returns exception "Specified method is not supported"
Less fancy but works instead
foreach (var link in  links)
{
   if (link.Title == "MyTestCustomAction")
  //

Massimo

Believe this is fixed, thanks for catching that. Please let us know if you still see problems.


Empty string passed Check validation.

Hi! Thanks for this project. I'm using it to validate json files and an empty string passes validation and I think it should not.

Hi,
Thanks for your feedback.
See, empty values are valid as in {"k":""}.
Also, empty keys are valid like this: {"":"v"}.
See JSON Lint as reference.
Regards,
Marcelo.

Thanks you for your quick response. I know that empty strings are valid but, what I was trying to say is that, if you pass an empty string to validate ( i.e. check('') ) it returns true and it should return false, just like JSON Lint does if you simply click on the [Validate JSON] button without any text in the textarea.
Best regards.

Oh, Now I got it.
It is simple to implement.
Meanwhile, you can check just not empty strings, right? :-)
I'll share it in next update.
Best.

Done!
Sorry for the delay.


Text overlaping on presets.large

Describe the bug
Text overlaps on presets.large, similar to #3: https://github.com/GeopJr/GeopJr/blob/main/sponsors.svg
It was generated using GitHub actions on the latest tag using this config and this action workflow
Reproduction
The above mentioned workflow, config and github login should reproduce it
System Info
(This is from action runner)

  System:
    OS: Linux 5.15 Ubuntu 22.04.2 LTS 22.04.2 LTS (Jammy Jellyfish)
    CPU: (2) x64 Intel(R) Xeon(R) Platinum 8272CL CPU @ 2.60GHz
    Memory: 5.86 GB / 6.78 GB
    Container: Yes
    Shell: 5.1.16 - /bin/bash
  Binaries:
    Node: 18.15.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 9.5.0 - /usr/local/bin/npm
  Browsers:
    Chrome: 111.0.5563.146
    Chromium: 111.0.5547.0
    Firefox: 111.0.1

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

I am not sure how we could properly fix it. Currently we limit the length of the name by string length but we probably need to introduce some library to measure their visual width instead.

I don't think measuring its width would work either since there are multiple fonts. I did some attempts with clip paths and nested svgs:
<!-- the maths is a bit weird, svg x + text x should be equal to the original x (same for y) -->
<!-- 70 is the width and height of the avatar -->
<svg width="70" height="70" x="282.5" y="83" xmlns="http://www.w3.org/2000/svg">
      <text x="70" y="70" text-anchor="middle" class="sponsorkit-name" fill="currentColor">Andreas Maerten</text>
</svg>

That looks a bit bad, but if we increase the x so its a bit more centered and the width since it fits:
<svg width="70" height="70" y="83" xmlns="http://www.w3.org/2000/svg" x="315">
      <text y="70" text-anchor="middle" class="sponsorkit-name" fill="currentColor" x="52.5">Andreas Maerten</text>
</svg>

:/ The half-missing word doesn't look that good either. Using foreignobject for text wrapping would also break the svg outside of browsers.
For my original issue, I'll just decrease the preset maxLength, so feel free to close!


Generating .json parameter file does not supply all params when you select all

Does this occur consistently?
Repro steps:

rightclick the selected file you wish to generate a param file for
select Generate Parameter File
select JSON
Select All

receive an empty json file
{
  "$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#",
  "contentVersion": "<IP_ADDRESS>",
  "parameters": {}
}

works fine if i select bicepparamfile
using './main.bicep'

param enivironmentName = 'dev'
param solutionName = 'toyhr${uniqueString(resourceGroup().id)}'
param appServicePlanInstanceCount = 1
param appServicePlanSku = {
  name: 'F1'
  tier: 'Free'
}
param location = 'westus3'

Action: command/bicep.generateParams
Error type: Error
Error Message: Generating parameters failed: Please select the output format and which parameters to include
Output
Version: 0.23.1
OS: win32
OS Release: 10.0.22000
Product: Visual Studio Code
Product Version: 1.84.2
Language: en

Call Stack
GenerateParamsCommand.execute extension.js:2:2854203
extension.js:2:2856542extension.js:2:2856542

Can you include the bicep file you are using to generate the parameters off of so that we have a full reproduction of the issue? @polatengin can you take a look?

hi @jimmyboy10101,
Error message says Please select the output format and which parameters to include
The generator will fail and print the exact same message if the output-format or include-params options doesn't have a selection registered.
By any chance you hit escape, or your VS Code setup cancels the command from proceeding, so those options have no value, and you receive this error?


Apache2 License

Would you please also license this as Apache License v2?
http://www.apache.org/licenses/LICENSE-2.0.html
It's simply a translation of the MIT license from English into Legalese. A bit of a step backwards, unfortunately, but one that is easier to deal with in certain situations.

IANAL, but I'm using MIT licensed stuff from https://github.com/dominictarr/JSON.sh ... I don't know what limitation  this places on my derivative work.  If you know the legality of this, that would be great; I'm willing to license it in whatever way I'm legally permitted to.

I forked JSON.sh and added the Apache License 2. We'll see if the author accepts my pull requests.

It got merged.
https://github.com/dominictarr/JSON.sh/commit/a615139d9315eaa82e828480aa5eedb1a2eff0a9

Sw33t ... would you mind sending me a pull request?


No way to add tags

I don't see a way to add tags. It would be most helpful to be able to add tags when saving a web clipping.

The extension has no access to your Obsidian vault so it can't suggest existing tags like you would do on the desktop app (if that's what you're referring to); however you can manually write tags obviously, like so:
Note title
A brief note taken from my web browser.
#Tag1 #Tag2

Of course. Yes, I was hoping there was a way to get the existing tags. Oh well. Thought I would ask. Thanks for responding.
David
http://www.linkedin.com/in/dmonder
“There is no knowing that does not begin with knowing God.” ― John Calvin
On Aug 8, 2023, 5:29 AM -0400, Marco Vavassori @.***>, wrote:

The extension has no access to your Obsidian vault so it can't suggest existing tags like you would do on the desktop app (if that's what you're referring to); however you can manually write tags obviously, like so:
Note title
A brief note taken from my web browser.
#Tag1 #Tag2
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


Add MultipartBackend interface to support overriding the multipart upload behaviour

This PR adds support for implementation the optional MultipartBackend interface to avoid the in-memory multipart uploader and instead use a custom one.
I have to admit I accidentally opened this PR and the Copy PR on this repo instead of our fork but I thought it might be a good addition anyway.

Codecov Report

Merging #83 (737ad23) into master (42c772b) will decrease coverage by 0.14%.
The diff coverage is 62.33%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@            Coverage Diff             @@
##           master      #83      +/-   ##
==========================================
- Coverage   65.93%   65.79%   -0.14%
==========================================
  Files          28       28
  Lines        2677     2681       +4
==========================================
- Hits         1765     1764       -1
- Misses        647      649       +2
- Partials      265      268       +3

Files Changed
Coverage Δ

backend.go
91.30% <ø> (ø)

gofakes3.go
65.15% <46.66%> (+0.35%)
:arrow_up:

uploader.go
84.61% <66.12%> (-3.91%)
:arrow_down:

Looks great! Thank you!


⚠ Bofrost.fr has degraded performance

In 9404ea9, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1110 ms

Resolved: Bofrost.fr performance has improved in 466ea17 after 6 minutes.