Port to spago (CI)

Here is my attempt to continue with the work done here https://github.com/exercism/purescript/pull/127 in replacing bower/pulp with spago. I focused on getting CI setup to build and test the exercises (just practice exercises for now). The approach is more or less similar to what was being done for bower. Spago uses two files packages.dhall (defines package-set) and spago.dhall (project dependencies).

All exercises should use the same package set so that we can share a .spago and output directory.
We gain some additional flexibility in that spago.dhall can vary per exercise. This is nice because we can whittle down the exercise dependencies to the bare minimum and we save students some diskspace. Also spago has started warning about unused dependencies... a topic for when we tackle porting the exercises to 0.14.x.

Please have a look (the last commit contains the interesting bits) and see if you think this approach is worth pursuing. If so I can continue to update the docs and add the finishing touches.
NOTE: Without sharing the output and .spago directories the CI run takes around 7 minutes...
@connorads @aimorris

Here is an example of a CI run: https://github.com/emiel/purescript/runs/2442322095?check_suite_focus=true

@emiel Thank you 💙
@ErikSchierboom will take a look at this later in the week when he's back working. Before then hopefully some @exercism/purescript people can take a look! :)

The travis is failing because it's still using the old configlet

The travis is failing because it's still using the old configlet

Thanks for having a look @SleeplessByte. It is my understanding Excercism is migrating completely to GitHub CI and thus that is where my focus is now. I'd rather tackle configlet in another PR because I guess there is more work to do there. ;)

Totally. It was mostly informational and why I approved.

I concur

Closing in favor of https://github.com/exercism/purescript/pull/185


Not shown in official website

what's the problem on it, the official website doesn't shown and how can i contribute more to this python nepal open source community. Any ideas

Thanks @Aju100 Updated and merged.


SemVer changes

We are currently following SemVer by using japicmp.
Propose changing our guarantees to the following
We follow SemVer as closely as we can.

patch releases are binary and source compatible [1]
minor releases are source compatible [2] [3]
major release will struggle to only contain breaking changes that are previously deprecated

1: Except in the case of an urgent security concern.
2: Except that we allow new interface methods with default implementations.
3: Except that we allow removal of superclass declaration where the superclass is to be considered a helper class and users are expected to either rely on the actual class, a different superclass in the hierarchy or an interface.
Reasoning
The main reason to use SemVer is to maintain a consistency between releases for our users and especially for users who release their own tools built with RDF4J. SemVer is also useful for aligning our release process with the expectations of the Eclipse Foundation.
Binary compatibility is useful because it means that a user can change out a JAR file without recompiling other jar files that depend on it. Consider a fictional end user who has bought Product X which uses RDF4J 4.0.1 as one of many libraries. We discover and fix a data corruption issue and release a fix with 4.0.2. The end user can then swap out all the existing RDF4J JARs with the new ones without waiting for a new build of Product X.
Backwards compatibility can sometimes be cumbersome and costly, restricting innovation. SemVer details what should or shouldn't be considered a breaking change striking a good balance between compatibility and innovation. A few of the SemVer rules implemented in japicmp are still sometimes overly restrictive.
All new interface methods are considered a major change, even if they have a default implementation. We have fairly frequently broken with this restriction in order to add new interface methods for more specific use cases, for instance adding a removeAll(...) method with a default implementation that instead calls remove(...) from within a loop. Or adding two methods where one signals that the other is implemented, for instance supportsBulkAdd() and bulkAdd(...).
Our codebase relies on many shared classes with sensible implementations of interfaces. In most cases these classes exist for our own sanity in order to reduce duplicate code. Naturally we want our users to take advantage of these shared classes too and we take care to ensure backwards compatibility.
SemVer considers it a major change when a class stops extending a superclass because a user could have relied on that superclass in their code. An example BaseSheep sheep = new NorwegianSpottedMountainSheep(); vs Sheep sheep = new NorwegianSpottedMountainSheep();. From our own codebase EmptyIteration could be a decent example.
EmptyIteration extends AbstractCloseableIteration which implements CloseableIteration and some code for making sure that the iteration is only closed once. EmptyIteration is a final class, so users aren't allowed to extend it with their own code. It makes sense for EmptyIteration to implement CloseableIteration directly since there isn't any need for the code from AbstractCloseableIteration that makes sure that the iteration is only closed once. A question then is if users have relied on EmptyIteration viewed as AbstractCloseableIteration or if they call any of the inherited methods?
public final class EmptyIteration<E, X extends Exception> extends AbstractCloseableIteration<E, X> {

	public EmptyIteration() {
	}

	@Override
	public boolean hasNext() {
		return false;
	}

	@Override
	public E next() {
		throw new NoSuchElementException();
	}

	@Override
	public void remove() {
		throw new IllegalStateException("Empty iterator does not contain any elements");
	}
}

AbstractCloseableIteration exposes two methods that are not declared in the CloseableIteration interface. We can copy those methods into EmptyIteration which ensures source compatibility when EmptyIteration is viewed as an EmptyIteration.
public final class EmptyIteration<E, X extends Exception> implements CloseableIteration<E, X> {

	public EmptyIteration() {
	}

	@Override
	public boolean hasNext() {
		return false;
	}

	@Override
	public E next() {
		throw new NoSuchElementException();
	}

	@Override
	public void remove() {
		throw new IllegalStateException("Empty iterator does not contain any elements");
	}

	public boolean isClosed() {
		return true;
	}

	public  void close() throws X {
	}

	protected void handleClose() throws X {
	}
}

We would need to consider this on a case by case basis. For EmptyIteration it could very well make sense for a users to rely on AbstractCloseableIteration so that all iterations can be tracked in a list to make sure that they all have been correctly closed. Then again we could assume that users would implement their own wrappers if they want this sort of functionality since we could very well create new iteration classes that don't extend AbstractCloseableIteration which they then wouldn't be able to track.
Tasks

[ ] Update pom.xml
[ ] Update website
[ ] Consider publishing a news item

We follow SemVer as closely as we can.
* patch releases are binary and source compatible [1]

* minor releases are source compatible [2] [3]

* major release will struggle to only contain breaking changes that are previously deprecated

1: Except in the case of an urgent security concern.

Good call out. Somewhat on the fence if/when a concern is serious enough to do this, but it's not likely to happen often anyway.

2: Except that we allow new interface methods with default implementations.

We may want to explain a little why, generally speaking, this is not source compatible, to illustrate that these are rare cases and when handled with care, it won't be a problem. There's a good discussion here: https://stackoverflow.com/questions/31188231/do-java-8-default-methods-break-source-compatibility

3: Except that we allow removal of superclass declaration where the superclass is to be considered a helper class and users are expected to either rely on the actual class, a different superclass in the hierarchy or an interface.

I find this one hard to justify. I understand what you're trying to say, but taking a cynical view it sounds a little too much like: "We have this specific thing we want to fix in a minor release and we need to twist our definitions of compatibility to make that possible".
Perhaps we should at the very least pledge that we would only make such changes in rare circumstances, favoring marking things deprecated / internaluseonly before addressing in a major release, and that if we do this we will always ensure that the LSP is observed in these cases (use of the helper class can be safely swapped to use of the subclass, without changing behavior).


make it so that imported events retain UID and duplicate IDs will fail gracefully

see #583 and #492
I modified this for my own purposes and I stopped at "it works for my use case and doesn't make any tests fail". I don't think I missed anything important but I don't mind spending some more time on it if needed. I think not importing defaults is pretty reasonable default behavior --  I personally would not expect an import to create duplicate events if the event IDs are the same.  Thoughts?

I don't have time to get familiar with that part of the codebase and review but I agree with your description of the desired behavior. Basically I think this should try to reproduce what the Google Calendar web interface does when given repeated imports of the same thing, which to my knowledge is as you describe.

I have tested this PR and can confirm it works as expected, thanks!

Here's more feedback:
In its current state this PR does not allow importing updated events (ie. SEQUENCE got incremented).
Ideally gcalcli would fetch the existing event (same UID) and update it if SEQUENCE has been incremented and ignore events who have not changed (same UID and same SEQUENCE)

Updating events would be a much welcome behavior! It would be even better than a graceful fail.
May I suggest using service.events().import(**kwargs) instead of service.events().insert(**kwargs), when 'iCalUID' in event is True?
I did some tests from the google developers API page, the behavior of import seems correct.
I can create an other pull request but I wanted to have your thoughts first!

Hello from 2024! This change no longer merges cleanly, but I put together an updated PR #712 based on cryhot's change that should fix these issues. Would anyone be able to give that version a try and make sure it's not horribly broken so I can finally merge a fix for this? =)


Support script expressions

The current JsonPath spec allows script expressions aka functions, are there any plans to support it?
$.books.size()
$.somestring.split(".")[0]

Which JsonPath spec? Can you provide a sample json and the expected result of your example?

http://goessner.net/articles/JsonPath/
"Script expression evaluated by the underlying script engine"
For example the jayway implementation allows some functions, min, max, etc.
https://github.com/json-path/JsonPath#functions
Ideally this would need to be an addition to the antlr grammar to allow pluggable functions that could be defined in the JsonSurfer instance

{
"items": [1,2,3,-1]
}
$.items.size() // 4
$.items.min() // -1
$.items.toString() // "[1,2,3,-1]"

I think it would not be too difficult if the "functions" apply only to leaf level(as the last node), then the implementation should be similar to JsonPath filter. Any pull requests for this feature are welcome. I'd love to help, if you have any further question.

Alternatively, you can use stream API of Java8 to achieve above "functions". Please refer to https://github.com/jsurfer/JsonSurfer#stream-support

Examples added in document:
https://github.com/jsurfer/JsonSurfer#java-8-streams-api-support


Test 'Can create a registry with multiple controllers' is skipped.

This feature is supported by the node. https://github.com/docknetwork/dock-substrate/blob/42ecfdf2d0efd358857aa720a09194bc8b90379d/runtime/src/revoke.rs#L902

Test now passes, perhaps was a previous implementation bug or polkadot issue when first implementing.

Test is flaky, fails 50% of the time with badproof error. Still needs more investigation


[BUG] GUI doesn't appear during "Select the Windows 10 Edition to Optimize"

Bug description
After I launch Start-Optimize.ps1 in (Administrator) PowerShell, with the following command: "powershell -ep bypass -file C:\Users[My Username\Downloads\Optimize-Offline-<IP_ADDRESS>\Start-Optimize.ps1", the script copies the .esd file, then at the top of the window it says "Select the Windows 10 Edition to Optimize", but no GUI appears.
Screenshots

Please complete the following information:

Image Name: Windows.iso
Image Build: 20H2 (I'm not sure what the exact build is)
Host Environment: Windows 10 Pro

I encounter the same problem with the <IP_ADDRESS>, have you found a solution ?


Track dependencies when using qAddDependentFile

Do I also need to need the files or is calling doesFileExist enough to track the dependency?

doesFileExist tracks that the file exists or not. need tracks the modification time too and asserts that it must exist. My guess is you want need here?

need uses the plain Shake file rules, wouldn't GetModificationTime be a better fit here?

@pepeiborra What is your exact suggestion?

use_ GetModificationTime instead of doesFileExist

Yes, you're right. A GetModificationTime would be better.

Is this what you have in mind?

Is this what you have in mind?

Yes, this is exactly what I had in mind

How would a test work?

Check that a program using qAddDependentFile to e.g. inject code, gets recompiled after changing the indirect dep?

a very simple way to check that it gets recompiled might be to just delete the file that you are adding via qAddDependentFile and see that you get a diagnostic afterwards.

I added a test now.


Could not create an instance of type com.linkedin.gradle.python.PythonExtension_Decorated.

When I run the example of PyGradle, I came across this exception.
my environments:
win7 64-bit
jdk1.8.0_51
gradle-3.1
thanks

This is a duplicate of issue #68
Closing this one.
Please follow up for resolution on #68.

@zvezdan this are different issues.
@cay914 can you please run gradle wrapper --gradle-version 3.0 --stacktrace?

file.txt
OK. Here is the exception file log. @ethankhall

I have had the same thing on my machine at work, and I attempted the same exact process on a linux vm and I did not have any issues, just tried it on my machine here at my home and produced the same error as on my windows machine at work, so it looks like the issue could be os dependent.

@scuba10steve did you see it on Windows then?

@ethankhall Yes, but not on a linux based machine, more specifically it was a VirtualBox VM running Xubuntu 16.04.

Awesome thanks, I'll take a look at whats going on.

Same here..
Gradle 3.2.1
Groovy:       2.4.7
Ant:          Apache Ant(TM) version 1.9.6 compiled on June 29 2015
JVM:          1.8.0_111 (Oracle Corporation 25.111-b14)
OS:           Windows 10 10.0 amd64

Same error using both the Windows cmd and the git bash (cygwin):
* What went wrong:
An exception occurred applying plugin request [id: 'com.linkedin.python-cli', version: '0.3.36']
> Failed to apply plugin [class 'com.linkedin.gradle.python.plugin.PythonPlugin']
   > Could not create an instance of type com.linkedin.gradle.python.PythonExtension_Decorated.

Thanks!

same here..
Gradle 4.7
Groovy:2.4.15
JVM:          1.8.0_172(build 1.8.0_172-b11)
OS:           Windows 7 64bit

example-project>gradle wrapper --gradle-version 3.0 --stacktrace

FAILURE: Build failed with an exception.

* Where:
Build file 'D:\2.ws\pycharm\example-project\build.gradle' line: 2

* What went wrong:
An exception occurred applying plugin request [id: 'com.linkedin.python-sdist', version: '0.3.9']
> Failed to apply plugin [class 'com.linkedin.gradle.python.plugin.PythonPlugin']
   > Could not create an instance of type com.linkedin.gradle.python.PythonExtension_Decorated.
      > Unable to find or execute python

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

* Exception is:
org.gradle.api.plugins.InvalidPluginException: An exception occurred applying plugin request [id: 'com.linkedin.python-sdist', version: '0.3.9']

Is this resolved, I have the same issue on windows.

Same issue. Python is in my path variable for boot the use and the system. I'd be glad if there was a way to set it manually.


Added MATTERMOST_TOKEN for handling MFA token

See https://github.com/loafoe/mattermost-client/pull/35.

@jwernicke MFA is pretty interactive, but this change might be useful for when we actually get token based bot accounts in MM, so merged.

What I do is log in manually as the bot, pull the token from cookies, then set it in my run script. I think the token stays valid until MM restarts.

What I do is log in manually as the bot, pull the token from cookies, then set it in my run script. I think the token stays valid until MM restarts.


Feature request: supporting DragonflyBSD?

Hi olevole!
How feasible would it be to support CBSD on DragonflyBSD? I would really like to see CBSD on DF.
PS: Also I just wanted to say a very big thank you for all your hard work and a big well done to you all.

Hi, thank you for feedback.
I've already tried to get CBSD on DragonFly, I also was interested. Unfortunately, the implementation of jail on DF is outdated. Everything you need to get CBSD on DF - is support jail.conf(5) configuration and libjail.so. I believe that for DF hackers it should be a trivial work, because in fact, jail did not develop more than 10+ years. Changing parameters from command line to jail.conf (with degradation of functional in the form of loss of ability to have jail on two interfaces) - that's all change for the period ;-)

Close issue  until better times because at the moment it does not have a possible solution


⚠ Bofrost.at has degraded performance

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

HTTP code: 200
Response time: 2368 ms

Resolved: Bofrost.at performance has improved in 00bfd61 after 9 minutes.


Does custom repo work?

Hi,
I tried to use a custom repo as was added in #12
however this is my build output in the action:
Status: Downloaded newer image for frealmyr/marlin-build:latest

Override Detected
Switching git repository to: https://github.com/tinuva/B1-SE-SKR2

Cloning into 'B1-SE-SKR2'...
/home/platformio/build-marlin.sh: line 34: cd: Marlin/: No such file or directory
fatal: not a git repository (or any of the parent directories): .git

You are using git tag from docker image:

cp: cannot create regular file '/home/platformio/Marlin/Marlin/Configuration_adv.h': No such file or directory
cp: cannot create regular file '/home/platformio/Marlin/Marlin/Configuration.h': No such file or directory
sed: can't read /home/platformio/Marlin/platformio.ini: No such file or directory

I do have a Marlin folder inside my repo but I suspect its where the script expect it to be. Eg. its probably at B1-SE-SKR2/Marlin instead of Marin.
Am I doing something wrong or is this not fully tested?

I was wondering if it would work better with
git init .
git remote add origin <repository-url>
git pull origin master

Ok testing the git command myself, it needs to be this in the script:
git clone $USE_REPO Marlin
at line https://github.com/frealmyr/marlin-build/blob/master/build-marlin.sh#L8


setup file trigger before start

Taking over #17523
We have been using galley with filesystem backend in the VM infrastructure for a while.
Fsnotify support is required to kick off the config reload routines, when config files
on the disk change. Currently, the fs backend requires explicit triggers for file system changes
by asking the user to issue a SIGUSR1. This PR chains fsnotify triggers to this path [triggering
a SIGUSR1 when the backing files change].

Hi @vikaschoudhary16. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

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.

/ok-to-test

/ok-to-test

please sign google cla

and per @sushicw we need tests

I've gotten a bit more context on the history behind this since my look at the last version of this PR. Apparently the previous behavior (notifying on file changes) was brittle and difficult to debug, prompting the move to explicit signalling.
You should gate this change behind an opt-in flag,  so we can support this use case but the auto fsnotify is off by default.

@rshriram CLA is signed but you should comment @googlebot I consent. because the first commit has you as author. https://github.com/istio/istio/pull/17588#issuecomment-537836543
Unit tests are updated.

@vikaschoudhary16: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

unit-tests_istio
c590adf2f1c94b81b9f8ef19fbcf74d0baaa2ad9
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

unit-tests_istio
c590adf2f1c94b81b9f8ef19fbcf74d0baaa2ad9
link
/test unit-tests_istio

lint_istio
c590adf2f1c94b81b9f8ef19fbcf74d0baaa2ad9
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

unit-tests_istio
c590adf2f1c94b81b9f8ef19fbcf74d0baaa2ad9
link
/test unit-tests_istio

lint_istio
c590adf2f1c94b81b9f8ef19fbcf74d0baaa2ad9
link
/test lint_istio

racetest_istio
c590adf2f1c94b81b9f8ef19fbcf74d0baaa2ad9
link
/test racetest_istio

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

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

Test name
Commit
Details
Rerun command

unit-tests_istio
c590adf2f1c94b81b9f8ef19fbcf74d0baaa2ad9
link
/test unit-tests_istio

lint_istio
c590adf2f1c94b81b9f8ef19fbcf74d0baaa2ad9
link
/test lint_istio

racetest_istio
c590adf2f1c94b81b9f8ef19fbcf74d0baaa2ad9
link
/test racetest_istio

codecov_istio
c590adf2f1c94b81b9f8ef19fbcf74d0baaa2ad9
link
/test codecov_istio

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

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

Test name
Commit
Details
Rerun command

unit-tests_istio
c590adf2f1c94b81b9f8ef19fbcf74d0baaa2ad9
link
/test unit-tests_istio

lint_istio
c590adf2f1c94b81b9f8ef19fbcf74d0baaa2ad9
link
/test lint_istio

racetest_istio
c590adf2f1c94b81b9f8ef19fbcf74d0baaa2ad9
link
/test racetest_istio

codecov_istio
c590adf2f1c94b81b9f8ef19fbcf74d0baaa2ad9
link
/test codecov_istio

integ-mixer-k8s-tests_istio
c590adf2f1c94b81b9f8ef19fbcf74d0baaa2ad9
link
/test integ-mixer-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

unit-tests_istio
c590adf2f1c94b81b9f8ef19fbcf74d0baaa2ad9
link
/test unit-tests_istio

racetest_istio
c590adf2f1c94b81b9f8ef19fbcf74d0baaa2ad9
link
/test racetest_istio

codecov_istio
c590adf2f1c94b81b9f8ef19fbcf74d0baaa2ad9
link
/test codecov_istio

integ-mixer-k8s-tests_istio
c590adf2f1c94b81b9f8ef19fbcf74d0baaa2ad9
link
/test integ-mixer-k8s-tests_istio

lint_istio
e65a979c0f6f1728d92d9ced79ed2b400123d051
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio
c590adf2f1c94b81b9f8ef19fbcf74d0baaa2ad9
link
/test integ-mixer-k8s-tests_istio

lint_istio
a6624c9ec27035d87a6118b73a5144de2029703a
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
a6624c9ec27035d87a6118b73a5144de2029703a
link
/test lint_istio

gencheck_istio
b5e8c72c285766babd120b4936c154c0cc8c1930
link
/test gencheck_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
a6624c9ec27035d87a6118b73a5144de2029703a
link
/test lint_istio

gencheck_istio
b5e8c72c285766babd120b4936c154c0cc8c1930
link
/test gencheck_istio

racetest_istio
b5e8c72c285766babd120b4936c154c0cc8c1930
link
/test racetest_istio

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

@googlebot I consent

ping @sushicw @ozevren @rshriram

@rshriram @sushicw @ozevren updated. PTAL!

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

Test name
Commit
Details
Rerun command

racetest_istio
b5e8c72c285766babd120b4936c154c0cc8c1930
link
/test racetest_istio

lint_istio
47a8d9cbab4a1d10eb096a89c78787da39cc4a24
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

racetest_istio
b5e8c72c285766babd120b4936c154c0cc8c1930
link
/test racetest_istio

lint_istio
47a8d9cbab4a1d10eb096a89c78787da39cc4a24
link
/test lint_istio

unit-tests_istio
47a8d9cbab4a1d10eb096a89c78787da39cc4a24
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

racetest_istio
b5e8c72c285766babd120b4936c154c0cc8c1930
link
/test racetest_istio

unit-tests_istio
47a8d9cbab4a1d10eb096a89c78787da39cc4a24
link
/test unit-tests_istio

lint_istio
dbb972b09afe571df36fd0e73c4024335621b5bf
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

racetest_istio
b5e8c72c285766babd120b4936c154c0cc8c1930
link
/test racetest_istio

lint_istio
dbb972b09afe571df36fd0e73c4024335621b5bf
link
/test lint_istio

unit-tests_istio
dbb972b09afe571df36fd0e73c4024335621b5bf
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

racetest_istio
b5e8c72c285766babd120b4936c154c0cc8c1930
link
/test racetest_istio

lint_istio
e38453149593b647b0e44a998273001bc135fe3a
link
/test lint_istio

unit-tests_istio
e38453149593b647b0e44a998273001bc135fe3a
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

racetest_istio
b5e8c72c285766babd120b4936c154c0cc8c1930
link
/test racetest_istio

lint_istio
e38453149593b647b0e44a998273001bc135fe3a
link
/test lint_istio

unit-tests_istio
e38453149593b647b0e44a998273001bc135fe3a
link
/test unit-tests_istio

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

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

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

Test name
Commit
Details
Rerun command

racetest_istio
b5e8c72c285766babd120b4936c154c0cc8c1930
link
/test racetest_istio

unit-tests_istio
e38453149593b647b0e44a998273001bc135fe3a
link
/test unit-tests_istio

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

lint_istio
b707ba4ac58198b7d1b72af6251f46d0e79e7ca1
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

racetest_istio
b5e8c72c285766babd120b4936c154c0cc8c1930
link
/test racetest_istio

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

lint_istio
b707ba4ac58198b7d1b72af6251f46d0e79e7ca1
link
/test lint_istio

unit-tests_istio
b707ba4ac58198b7d1b72af6251f46d0e79e7ca1
link
/test unit-tests_istio

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

This is failing the lint

galley/pkg/server/components/processing2_test.go:90:56: TestProcessing2_StartErrors$6 - result 0 (istio.io/istio/galley/pkg/config/event.Source) is always nil (unparam)
_ = func(_ string, _ schema.KubeResources, _ bool) (event.Source, error) { return nil, e }

@howardjohn https://github.com/golangci/golangci-lint/issues/367
unparam in the ci needs to be updated i guess

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

Test name
Commit
Details
Rerun command

racetest_istio
b5e8c72c285766babd120b4936c154c0cc8c1930
link
/test racetest_istio

lint_istio
b707ba4ac58198b7d1b72af6251f46d0e79e7ca1
link
/test lint_istio

unit-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

racetest_istio
b5e8c72c285766babd120b4936c154c0cc8c1930
link
/test racetest_istio

lint_istio
b707ba4ac58198b7d1b72af6251f46d0e79e7ca1
link
/test lint_istio

unit-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test unit-tests_istio

pilot-multicluster-e2e_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test pilot-multicluster-e2e_istio

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

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

Test name
Commit
Details
Rerun command

racetest_istio
b5e8c72c285766babd120b4936c154c0cc8c1930
link
/test racetest_istio

lint_istio
b707ba4ac58198b7d1b72af6251f46d0e79e7ca1
link
/test lint_istio

unit-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test unit-tests_istio

pilot-multicluster-e2e_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test pilot-multicluster-e2e_istio

release-test_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test release-test_istio

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

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

Test name
Commit
Details
Rerun command

racetest_istio
b5e8c72c285766babd120b4936c154c0cc8c1930
link
/test racetest_istio

lint_istio
b707ba4ac58198b7d1b72af6251f46d0e79e7ca1
link
/test lint_istio

unit-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test unit-tests_istio

pilot-multicluster-e2e_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test pilot-multicluster-e2e_istio

release-test_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test release-test_istio

integ-telemetry-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-telemetry-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

racetest_istio
b5e8c72c285766babd120b4936c154c0cc8c1930
link
/test racetest_istio

lint_istio
b707ba4ac58198b7d1b72af6251f46d0e79e7ca1
link
/test lint_istio

unit-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test unit-tests_istio

pilot-multicluster-e2e_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test pilot-multicluster-e2e_istio

release-test_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test release-test_istio

integ-telemetry-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-telemetry-k8s-tests_istio

integ-galley-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-galley-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

racetest_istio
b5e8c72c285766babd120b4936c154c0cc8c1930
link
/test racetest_istio

lint_istio
b707ba4ac58198b7d1b72af6251f46d0e79e7ca1
link
/test lint_istio

unit-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test unit-tests_istio

pilot-multicluster-e2e_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test pilot-multicluster-e2e_istio

release-test_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test release-test_istio

integ-telemetry-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-telemetry-k8s-tests_istio

integ-galley-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-pilot-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

racetest_istio
b5e8c72c285766babd120b4936c154c0cc8c1930
link
/test racetest_istio

lint_istio
b707ba4ac58198b7d1b72af6251f46d0e79e7ca1
link
/test lint_istio

unit-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test unit-tests_istio

pilot-multicluster-e2e_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test pilot-multicluster-e2e_istio

release-test_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test release-test_istio

integ-telemetry-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-telemetry-k8s-tests_istio

integ-galley-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-pilot-k8s-tests_istio

integ-framework-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-framework-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

racetest_istio
b5e8c72c285766babd120b4936c154c0cc8c1930
link
/test racetest_istio

lint_istio
b707ba4ac58198b7d1b72af6251f46d0e79e7ca1
link
/test lint_istio

unit-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test unit-tests_istio

pilot-multicluster-e2e_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test pilot-multicluster-e2e_istio

release-test_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test release-test_istio

integ-telemetry-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-telemetry-k8s-tests_istio

integ-galley-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-pilot-k8s-tests_istio

integ-framework-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-framework-k8s-tests_istio

integ-istioctl-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-istioctl-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

racetest_istio
b5e8c72c285766babd120b4936c154c0cc8c1930
link
/test racetest_istio

lint_istio
b707ba4ac58198b7d1b72af6251f46d0e79e7ca1
link
/test lint_istio

unit-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test unit-tests_istio

pilot-multicluster-e2e_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test pilot-multicluster-e2e_istio

release-test_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test release-test_istio

integ-telemetry-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-telemetry-k8s-tests_istio

integ-galley-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-pilot-k8s-tests_istio

integ-framework-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-framework-k8s-tests_istio

integ-istioctl-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-istioctl-k8s-tests_istio

integ-security-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-security-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

racetest_istio
b5e8c72c285766babd120b4936c154c0cc8c1930
link
/test racetest_istio

lint_istio
b707ba4ac58198b7d1b72af6251f46d0e79e7ca1
link
/test lint_istio

unit-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test unit-tests_istio

pilot-multicluster-e2e_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test pilot-multicluster-e2e_istio

release-test_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test release-test_istio

integ-telemetry-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-telemetry-k8s-tests_istio

integ-galley-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-pilot-k8s-tests_istio

integ-framework-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-framework-k8s-tests_istio

integ-istioctl-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-istioctl-k8s-tests_istio

integ-security-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-security-k8s-tests_istio

integ-new-install-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-new-install-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

racetest_istio
b5e8c72c285766babd120b4936c154c0cc8c1930
link
/test racetest_istio

lint_istio
b707ba4ac58198b7d1b72af6251f46d0e79e7ca1
link
/test lint_istio

unit-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test unit-tests_istio

pilot-multicluster-e2e_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test pilot-multicluster-e2e_istio

release-test_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test release-test_istio

integ-telemetry-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-telemetry-k8s-tests_istio

integ-galley-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-pilot-k8s-tests_istio

integ-framework-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-framework-k8s-tests_istio

integ-istioctl-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-istioctl-k8s-tests_istio

integ-security-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-security-k8s-tests_istio

integ-new-install-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-new-install-k8s-tests_istio

e2e-simpleTests-distroless_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test e2e-simpleTests-distroless_istio

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

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

Test name
Commit
Details
Rerun command

racetest_istio
b5e8c72c285766babd120b4936c154c0cc8c1930
link
/test racetest_istio

lint_istio
b707ba4ac58198b7d1b72af6251f46d0e79e7ca1
link
/test lint_istio

unit-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test unit-tests_istio

pilot-multicluster-e2e_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test pilot-multicluster-e2e_istio

release-test_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test release-test_istio

integ-telemetry-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-telemetry-k8s-tests_istio

integ-galley-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-pilot-k8s-tests_istio

integ-framework-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-framework-k8s-tests_istio

integ-istioctl-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-istioctl-k8s-tests_istio

integ-security-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-security-k8s-tests_istio

integ-new-install-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-new-install-k8s-tests_istio

e2e-simpleTests-distroless_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test e2e-simpleTests-distroless_istio

pilot-e2e-envoyv2-v1alpha3_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test pilot-e2e-envoyv2-v1alpha3_istio

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

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

Test name
Commit
Details
Rerun command

racetest_istio
b5e8c72c285766babd120b4936c154c0cc8c1930
link
/test racetest_istio

lint_istio
b707ba4ac58198b7d1b72af6251f46d0e79e7ca1
link
/test lint_istio

unit-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test unit-tests_istio

pilot-multicluster-e2e_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test pilot-multicluster-e2e_istio

release-test_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test release-test_istio

integ-telemetry-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-telemetry-k8s-tests_istio

integ-galley-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-pilot-k8s-tests_istio

integ-framework-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-framework-k8s-tests_istio

integ-istioctl-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-istioctl-k8s-tests_istio

integ-security-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-security-k8s-tests_istio

integ-new-install-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-new-install-k8s-tests_istio

e2e-simpleTests-distroless_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test e2e-simpleTests-distroless_istio

pilot-e2e-envoyv2-v1alpha3_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test pilot-e2e-envoyv2-v1alpha3_istio

e2e-simpleTests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test e2e-simpleTests_istio

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

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

Test name
Commit
Details
Rerun command

racetest_istio
b5e8c72c285766babd120b4936c154c0cc8c1930
link
/test racetest_istio

lint_istio
b707ba4ac58198b7d1b72af6251f46d0e79e7ca1
link
/test lint_istio

unit-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test unit-tests_istio

pilot-multicluster-e2e_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test pilot-multicluster-e2e_istio

release-test_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test release-test_istio

integ-telemetry-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-telemetry-k8s-tests_istio

integ-galley-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-pilot-k8s-tests_istio

integ-framework-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-framework-k8s-tests_istio

integ-istioctl-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-istioctl-k8s-tests_istio

integ-security-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-security-k8s-tests_istio

integ-new-install-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-new-install-k8s-tests_istio

e2e-simpleTests-distroless_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test e2e-simpleTests-distroless_istio

pilot-e2e-envoyv2-v1alpha3_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test pilot-e2e-envoyv2-v1alpha3_istio

e2e-simpleTests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test e2e-simpleTests_istio

integ-mixer-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-mixer-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

racetest_istio
b5e8c72c285766babd120b4936c154c0cc8c1930
link
/test racetest_istio

lint_istio
b707ba4ac58198b7d1b72af6251f46d0e79e7ca1
link
/test lint_istio

unit-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test unit-tests_istio

pilot-multicluster-e2e_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test pilot-multicluster-e2e_istio

release-test_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test release-test_istio

integ-telemetry-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-telemetry-k8s-tests_istio

integ-galley-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-pilot-k8s-tests_istio

integ-framework-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-framework-k8s-tests_istio

integ-istioctl-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-istioctl-k8s-tests_istio

integ-security-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-security-k8s-tests_istio

integ-new-install-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-new-install-k8s-tests_istio

e2e-simpleTests-distroless_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test e2e-simpleTests-distroless_istio

pilot-e2e-envoyv2-v1alpha3_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test pilot-e2e-envoyv2-v1alpha3_istio

e2e-simpleTests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test e2e-simpleTests_istio

integ-mixer-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-mixer-k8s-tests_istio

e2e-mixer-no_auth_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test e2e-mixer-no_auth_istio

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

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

Test name
Commit
Details
Rerun command

racetest_istio
b5e8c72c285766babd120b4936c154c0cc8c1930
link
/test racetest_istio

lint_istio
b707ba4ac58198b7d1b72af6251f46d0e79e7ca1
link
/test lint_istio

unit-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test unit-tests_istio

pilot-multicluster-e2e_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test pilot-multicluster-e2e_istio

release-test_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test release-test_istio

integ-telemetry-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-telemetry-k8s-tests_istio

integ-galley-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-pilot-k8s-tests_istio

integ-framework-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-framework-k8s-tests_istio

integ-istioctl-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-istioctl-k8s-tests_istio

integ-security-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-security-k8s-tests_istio

integ-new-install-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-new-install-k8s-tests_istio

e2e-simpleTests-distroless_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test e2e-simpleTests-distroless_istio

pilot-e2e-envoyv2-v1alpha3_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test pilot-e2e-envoyv2-v1alpha3_istio

e2e-simpleTests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test e2e-simpleTests_istio

integ-mixer-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-mixer-k8s-tests_istio

e2e-mixer-no_auth_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test e2e-mixer-no_auth_istio

integ-istioio-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-istioio-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

racetest_istio
b5e8c72c285766babd120b4936c154c0cc8c1930
link
/test racetest_istio

lint_istio
b707ba4ac58198b7d1b72af6251f46d0e79e7ca1
link
/test lint_istio

unit-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test unit-tests_istio

pilot-multicluster-e2e_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test pilot-multicluster-e2e_istio

release-test_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test release-test_istio

integ-telemetry-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-telemetry-k8s-tests_istio

integ-galley-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-pilot-k8s-tests_istio

integ-framework-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-framework-k8s-tests_istio

integ-istioctl-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-istioctl-k8s-tests_istio

integ-security-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-security-k8s-tests_istio

integ-new-install-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-new-install-k8s-tests_istio

e2e-simpleTests-distroless_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test e2e-simpleTests-distroless_istio

pilot-e2e-envoyv2-v1alpha3_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test pilot-e2e-envoyv2-v1alpha3_istio

e2e-simpleTests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test e2e-simpleTests_istio

integ-mixer-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-mixer-k8s-tests_istio

e2e-mixer-no_auth_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test e2e-mixer-no_auth_istio

integ-istioio-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-istioio-k8s-tests_istio

e2e-dashboard_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test e2e-dashboard_istio

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

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

Test name
Commit
Details
Rerun command

racetest_istio
b5e8c72c285766babd120b4936c154c0cc8c1930
link
/test racetest_istio

lint_istio
b707ba4ac58198b7d1b72af6251f46d0e79e7ca1
link
/test lint_istio

unit-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test unit-tests_istio

pilot-multicluster-e2e_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test pilot-multicluster-e2e_istio

release-test_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test release-test_istio

integ-telemetry-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-telemetry-k8s-tests_istio

integ-galley-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-pilot-k8s-tests_istio

integ-framework-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-framework-k8s-tests_istio

integ-istioctl-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-istioctl-k8s-tests_istio

integ-security-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-security-k8s-tests_istio

integ-new-install-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-new-install-k8s-tests_istio

e2e-simpleTests-distroless_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test e2e-simpleTests-distroless_istio

pilot-e2e-envoyv2-v1alpha3_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test pilot-e2e-envoyv2-v1alpha3_istio

e2e-simpleTests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test e2e-simpleTests_istio

integ-mixer-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-mixer-k8s-tests_istio

e2e-mixer-no_auth_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test e2e-mixer-no_auth_istio

integ-istioio-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-istioio-k8s-tests_istio

e2e-dashboard_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test e2e-dashboard_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

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

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

Test name
Commit
Details
Rerun command

racetest_istio
b5e8c72c285766babd120b4936c154c0cc8c1930
link
/test racetest_istio

lint_istio
b707ba4ac58198b7d1b72af6251f46d0e79e7ca1
link
/test lint_istio

unit-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test unit-tests_istio

pilot-multicluster-e2e_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test pilot-multicluster-e2e_istio

release-test_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test release-test_istio

integ-telemetry-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-telemetry-k8s-tests_istio

integ-galley-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-pilot-k8s-tests_istio

integ-framework-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-framework-k8s-tests_istio

integ-istioctl-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-istioctl-k8s-tests_istio

integ-security-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-security-k8s-tests_istio

integ-new-install-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-new-install-k8s-tests_istio

e2e-simpleTests-distroless_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test e2e-simpleTests-distroless_istio

pilot-e2e-envoyv2-v1alpha3_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test pilot-e2e-envoyv2-v1alpha3_istio

e2e-simpleTests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test e2e-simpleTests_istio

integ-mixer-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-mixer-k8s-tests_istio

e2e-mixer-no_auth_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test e2e-mixer-no_auth_istio

integ-istioio-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-istioio-k8s-tests_istio

e2e-dashboard_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test e2e-dashboard_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

e2e-simpleTestsMinProfile_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test e2e-simpleTestsMinProfile_istio

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

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

Test name
Commit
Details
Rerun command

racetest_istio
b5e8c72c285766babd120b4936c154c0cc8c1930
link
/test racetest_istio

lint_istio
b707ba4ac58198b7d1b72af6251f46d0e79e7ca1
link
/test lint_istio

unit-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test unit-tests_istio

pilot-multicluster-e2e_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test pilot-multicluster-e2e_istio

release-test_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test release-test_istio

integ-telemetry-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-telemetry-k8s-tests_istio

integ-galley-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-pilot-k8s-tests_istio

integ-framework-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-framework-k8s-tests_istio

integ-istioctl-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-istioctl-k8s-tests_istio

integ-security-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-security-k8s-tests_istio

integ-new-install-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-new-install-k8s-tests_istio

e2e-simpleTests-distroless_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test e2e-simpleTests-distroless_istio

pilot-e2e-envoyv2-v1alpha3_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test pilot-e2e-envoyv2-v1alpha3_istio

e2e-simpleTests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test e2e-simpleTests_istio

integ-mixer-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-mixer-k8s-tests_istio

e2e-mixer-no_auth_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test e2e-mixer-no_auth_istio

integ-istioio-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-istioio-k8s-tests_istio

e2e-dashboard_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test e2e-dashboard_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

e2e-simpleTestsMinProfile_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test e2e-simpleTestsMinProfile_istio

e2e-simpleTests-cni_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test e2e-simpleTests-cni_istio

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

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

Test name
Commit
Details
Rerun command

racetest_istio
b5e8c72c285766babd120b4936c154c0cc8c1930
link
/test racetest_istio

unit-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test unit-tests_istio

pilot-multicluster-e2e_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test pilot-multicluster-e2e_istio

release-test_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test release-test_istio

integ-telemetry-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-telemetry-k8s-tests_istio

integ-galley-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-pilot-k8s-tests_istio

integ-framework-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-framework-k8s-tests_istio

integ-istioctl-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-istioctl-k8s-tests_istio

integ-security-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-security-k8s-tests_istio

integ-new-install-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-new-install-k8s-tests_istio

e2e-simpleTests-distroless_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test e2e-simpleTests-distroless_istio

pilot-e2e-envoyv2-v1alpha3_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test pilot-e2e-envoyv2-v1alpha3_istio

e2e-simpleTests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test e2e-simpleTests_istio

integ-mixer-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-mixer-k8s-tests_istio

e2e-mixer-no_auth_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test e2e-mixer-no_auth_istio

integ-istioio-k8s-tests_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test integ-istioio-k8s-tests_istio

e2e-dashboard_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test e2e-dashboard_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

e2e-simpleTestsMinProfile_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test e2e-simpleTestsMinProfile_istio

e2e-simpleTests-cni_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test e2e-simpleTests-cni_istio

lint_istio
376fa25c6f9e3a5e914ea6bf109c5e0c9fda1da9
link
/test lint_istio

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


Try FFmpeg-Input with bitstream filters to fix various H264/HEVC standards

0.2.1

Backport to 0.4.x if works.


Have you ever seen any gone_remotes?

I haven't seen yet. I don't have a test case for it.
yes: 👍
no: 👎

I did. Would be nice if git trim would remove none existing remotes as well.

@schrieveslaach Thank you for responding to the survey! I initially doubted gone_remote's existence. Would you let me know your workflow? Also, I want to hear about what do you mean by 'none existing remotes'?
(I have so many questions)
Do you use a triangular workflow (upstream, origin(a fork of upstream), local fork)?
I assume that your branch (I'll call it 'A') is both on the upstream and fork. It is pushed to the fork, and fetched from the upstream.
Also since it is classified as 'gone', it is not fully merged into the base branch, isn't it?
But it is 'gone_remotes', the branch on the upstream is removed but it is still on the fork, is it right?

Sometimes at work we create personal forks of our products and we give them to our teammates so that they can test something. When I receive such a fork, I add it with git remote add and I do the stuff my teammates asked for. When I'm done we with it, the creator of the fork deletes it and I forget about it.
Today, when I used git trim, I noticed that I do have a remote that did not exists anymore. Unfortunately, git trim failed and I had to run git remote remove.
So there is no special workflow, just temporarily sharing code.

Oh thank you for sharing the story. That's what I meant for 'triangular workflow'. I haven't thought about deleting the forked repository though. I'll have a look into it. Thanks.

The fail might be caused by the git itself. git fetch --all --prune fails for the case.

You are welcome.

gone remote is changed to semantics while renaming it to stray remote. I'll close this survey.


Add mapping files for each famility.

Part to device, package and speed grade mapping

Device to fabric mapping

Part resources for the fuzzers

Signed-off-by: Daniel Schultz<EMAIL_ADDRESS>This PR is needed for https://github.com/SymbiFlow/prjxray/pull/1539

These need to land into the prjxray repository and then they will then be exported into the database in the same way the settings.sh.

So the suggestion here is to commit these on the prjxray side, and the standard CI process will propagate them to prjxray-db.  That make sense?

These need to land into the prjxray repository and then they will then be exported into the database in the same way the settings.sh.

So the suggestion here is to commit these on the prjxray side, and the standard CI process will propagate them to prjxray-db.  That make sense?

@litghost @mithro  - yes, sounds good to me. I would place them all in settings//. The CI scripts should still only push the parts and devices, right?

@litghost @mithro  - yes, sounds good to me. I would place them all in settings//. The CI scripts should still only push the parts and devices, right?

@litghost @mithro - yes, sounds good to me. I would place them all in settings//. The CI scripts should still only push the parts and devices, right?

That isn't quiet right.  You should commit the device.yaml and parts.yaml in prjxray/database/<family>, and put the resources.yaml in the prjxray/settings.

@litghost @mithro - yes, sounds good to me. I would place them all in settings//. The CI scripts should still only push the parts and devices, right?

That isn't quiet right.  You should commit the device.yaml and parts.yaml in prjxray/database/<family>, and put the resources.yaml in the prjxray/settings.


Add a global reseed button

Should change just the seeds on all effects. For quick remixes.

Don't like this, cause I want to see the output and manually pick a good new seed.


[QUERY] How to authenticate to management.azure.com with DefaultAzureCredential()

Query/Question
What's the best way to authenticate to the azure management api? I'm trying to add custom domains via code.
Before it worked well with
AzureServiceTokenProvider azureTokenProvider = new AzureServiceTokenProvider();
 string token = await azureTokenProvider.GetAccessTokenAsync("https://management.azure.com", tenantId);

But now, I'm migrating to the new API and I'm getting "The access token is invalid." error message.
var credential = new DefaultAzureCredential();

var token = credential.GetToken(
           new Azure.Core.TokenRequestContext(
                    new[] { $"https://management.azure.com/.default" }));

Also tried with the tenantId instead of .default, but it returns
Unable to get access token.  'AADSTS500011: The resource principal named https://management.azure.com/tenantId was not found in the tenant named...
Edit: I should also mention that I am authenticating to KeyVault with no problem using DefaultAzureCredential() and SecretClient()
Any advice?
Environment:

Name and version of the Library package used: [Azure.Identity 1.2.0-preview.3]
Hosting platform or OS and .NET runtime version: Linux App Service, .Net Core 3.1
IDE and version: Visual Studio 2019

Thanks!

@schaabs can you take a look? Is this supported by DefaultAzureCredential?

@mariojsnunes  Thank you for reaching out with this question. We are currenlty working on new versions of our management libraries which will work directly with the TokenCredential abstraction and the implementations in the Azure.Identity library. In the meantime @jongio has also provided some samples which demonstrate using the DefaultAzureCredential with our older libraries. For instance here is a sample which wraps the DefaultAzureCredential in the ITokenProvider interface so it can be used in all the contexts you were using AzureServiceTokenProvider before.

@mariojsnunes - Are you wanting to use Azure.Identity with management plane libs or do you want to use on its own? What do you mean by add custom domains?
Here's the repo with all the samples that adapt the Resource Management SDKs with the new Azure.Identity https://github.com/jongio/azidext

I have many tests here https://github.com/jongio/azidext/tree/master/net/Azure.Identity.Extensions.Tests/Mgmt
I'm using the same scope that you ref above.
Can you share the API that you are calling with that token?

I was trying to call the API for updating the custom domains of an Azure App Service.
This is the code I tried and couldn't put it to work:
var credential = new DefaultAzureCredential();

var token = credential.GetToken(
    new Azure.Core.TokenRequestContext(
        new[] { $"https://management.azure.com/{tenantId}" }));

using (HttpClient client = new HttpClient())
{
    client.DefaultRequestHeaders.Add("Authorization", "Bearer " + token);
    var baseUrl = new Uri($"https://management.azure.com/");
    var requestURl = baseUrl + $"subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/sites/{siteName}/hostNameBindings/{hostName}?api-version=2019-08-01";

    client.GetAsync(requestURl)
}

My guess is that I needed to use a client like on your samples:
var client = new ResourceManagementClient(new AzureIdentityCredentialAdapter());
But I didn't find the one to use, and thought wasn't implemented yet, so I tried calling the rest API manually.

Yes, try to do with the AzureIdentityCredentialAdapter and LMK if it works.  If not, let's pair on it when you have some time.

@mariojsnunes - Did you get this working?


Discourage controller specs in README

Per issue #1838.

LGTM. @xaviershay your feedback has been addressed so I'm going to merge.

thanks, sorry I missed the update!


Autofocus doesn't work

Hi,
i have a textarea which will be rendered, if some state is true. This input should get the focus automatically. So i use the autoFocus attribute. Unfortunatelly the component doesn't get the focus. When i use react, it works.
Tested with:

preact: 8.3.1
preact-compat: 3.18.4

@dkirchhof According to the HTML spec setting the autofocus attribute will focus the form-control as soon as the page is loaded. In your case it seems like the page is already loaded when setting the autofocus attribute, resulting in having no effect.
If you want to focus elements after the page is loaded you can use the native focus() method.
class Foo extends Component {
  constructor(props) {
    super(props);
    this.ref = createRef();
    this.onClick = this.onClick.bind(this);
  }

  onClick() {
    if (this.ref.current) {
      this.ref.current.focus();
    }
  }

  render() {
    return (
      <div>
        <input ref={this.ref} />
		<button onClick={this.onClick}>Set focus on input</button>
      </div>
    );
  }
}

Well, i was just wondering, why it works in react and doesn't in preact. So i have to refactor my code or will keep react.


Subdomain Detection is not Working on Localhost

🚀 Feature Proposal
The subdomain detection only works on public domains. In a development area is often localhost the domain. Then the subdomain detection is not working.
Motivation
The detection should also work on localhost development.
Example
The regex detection is based on the full URL. However, this is slightly unnecessary, since it is about your domain recognition. So you can take protocols or paths out of the detection.
The window.location object provides a property for this, which only outputs the hostname.
We assume that public domains always have at least one dot in them. The remaining characters are "word characters".
Everything that is before the Publik domain and has at least 2 and up to 5 characters (word characters) is the subdomain.
For the development area there is the or option "localhost" to the Publik Domain in the RegEx.
const language = window.location.hostname.match(/^(\w{2,5})\.((\w+\.\w{2,})|localhost)/i)

The regex option "g" (global) can be removed - on the kind of regex is has no impact.

Sorry, but why should the subdomain detection make sense on localhost?

For tests on localhost ... e.g. ReactCreateApp in default working on http://localhost:3000
http://fr.localhost:3000 is working fine. The current detection is not finding any subdomain so the default language is displayed .. first gues: The whole translation is not working.

Would you like to send a Pull Request to address this?

v6.1.5


Plotscripts

TODO: check plots scripts still works with new name

This one is almost ready.
Some modif of the README wrt paper figures number.

check glob command in each ntoebook

glob command has been check.
Now that we have zenodo link, I'll try to create the download script for the plots.


Comments on posts implementation

Main story: #272

@egnaf please correct link to main story from #271 to #272

ok


[Relay] Recursive destructor call replaced with non-recursive for Call nodes.

Recursive destructor call replaced with non-recursive (based on ExpandDataflow) for Call nodes. This prevents OutOfStack
exception during unwinding a chain of destructors for large-sized subtrees based on smart-pointers.

Mine is:

ulimit -s
8192

And it fails with around 200'000 stack frames in case of the unit test for
me.
--
Dmitriy Smirnov
On Wed, 14 Apr 2021 at 21:22, Robert Kimball @.***>
wrote:

@.**** commented on this pull request.
In tests/cpp/relay_dismantler_test.cc
https://github.com/apache/tvm/pull/7832#discussion_r613561822:

+#include <tvm/runtime/packed_func.h>
+#include <tvm/runtime/registry.h>
+#include <tvm/te/operation.h>
+#include <tvm/topi/broadcast.h>
+#include <tvm/topi/generic/injective.h>

+using namespace tvm;
+using namespace tvm::relay;
+
+TEST(Relay, OutOfStack) {

auto foo = [] {
auto add_op = relay::Op::Get("add");
auto c_data = tvm::runtime::NDArray::Empty({1, 2, 3}, {kDLFloat, 32, 1}, {kDLCPU, 0});
auto c1 = relay::Constant(c_data);
Call y1 = relay::Call(add_op, {c1, c1});
for (int i = 0; i < 16'384; i++) {

I was using ubuntu 20.04. I do have 64G RAM but I don't think that changes
the stack size. When I type ulimit -s to print the stack size I see
8182K. What do you see?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/apache/tvm/pull/7832#discussion_r613561822, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AGADO35QEDRNXHYLCK4YAJDTIX2RNANCNFSM42ZXVWQA
.

I mistyped my stack size. Mine is the same as yours. I tried 1e5 and it worked but failed at 1e6. Since it does not take long to run even 1e6 you can just set it there and it should fail in most places. 16384 is just too small

Thanks @d-smirnov @rkimball @yzhliu


Suggestion: Export to Markdown

It would be amazing if this repo would also support exporting to Markdown so that PR comments and GitHub issue can be created from the reports.

@mowies Added a patch to add --markdown, hopefully that is what you were looking for

Amazing! I just checked out the PR!
One thing maybe to add: For bigger test suites, the report gets super long for me. Is it somehow possible to provide an option to pass in my own custom markdown template? I would like to put in a more condensed template where every test is just a single line or even a table with just test name and a checkmark or a cross.

There is now a --template parameter as well:
go test -json | ./go-test-report --markdown --template short_report.md.template

go-test-report
Total: 17
✓ TestGenerateReport
✓ TestGroupOutputFlag
✓ TestGroupOutputFlagIfMissingValue
✓ TestGroupSizeFlag
✓ TestGroupSizeFlagIfMissingValue
✓ TestParseSizeFlagIfHeightValueIsNotInteger
✓ TestParseSizeFlagIfMalformedSize
✓ TestParseSizeFlagIfValueIsNotInteger
✓ TestParseSizeFlagIfWidthValueIsNotInteger
✓ TestReadTestDataFromStdIn
✓ TestSameTestName
✓ TestSizeFlag
✓ TestSizeFlagIfMissingValue
✓ TestSizeFlagWithFullDimensions
✓ TestTitleFlag
✓ TestTitleFlagIfMissingValue
✓ TestVersionCommand
✓ Passed: 17 | ‐ Skipped: 0 | ✗ Failed: 0

Awesome! This is exactly what I needed

was this deprecated by something else? Why didn't this ever get merged?

https://github.com/vakenbolt/go-test-report/pull/39#issuecomment-997683958

There have been no new go-test-report releases in 2022, or in 2023.

So forking is the right answer then, I suppose, unless you are aware of another ready made solution that exports to markdown?

Plenty of tools write markdown, but not exactly similar for go test no.

#60


Merge from 0.22

Getting a jump start on porting #5385. Merges 0.22.10.

Well, I was suprised that WS Client compiled without changes.  It's because it didn't even try.

This evolved into several merges from 0.22, but we're seeing much improved ClientTimeoutSuite performance as a result.  In my opinion, this is the final blocker to an 0.23.9 release, which will also ship the Ember HTTP/2 work.


Speed up GPU tests by avoiding device reset

At the moment, all of our GPU tests store a device executor that gets destroyed after each test, which in turn executes cuda/hipDeviceReset. This causes each of our tests to take at least 800ms on NVIDIA GPUs (less on AMD GPUs), independent of the actual kernel runtime. I think this is not necessary and can be fixed by instantiating a second device executor in a global variable (other, cleaner solutions welcome!)
Somewhat related to #461
Before:
151: [==========] Running 24 tests from 1 test case.
151: [----------] Global test environment set-up.
151: [----------] 24 tests from Dense
151: [ RUN      ] Dense.SingleVectorHipScaleIsEquivalentToRef
151: [       OK ] Dense.SingleVectorHipScaleIsEquivalentToRef (1012 ms)
...
151: [ RUN      ] Dense.CalculateTotalColsIsEquivalentToRef
151: [       OK ] Dense.CalculateTotalColsIsEquivalentToRef (864 ms)
151: [----------] 24 tests from Dense (22293 ms total)

After:
151: [==========] Running 24 tests from 1 test case.
151: [----------] Global test environment set-up.
151: [----------] 24 tests from Dense
151: [ RUN      ] Dense.SingleVectorHipScaleIsEquivalentToRef
151: [       OK ] Dense.SingleVectorHipScaleIsEquivalentToRef (95 ms)
...
151: [ RUN      ] Dense.CalculateTotalColsIsEquivalentToRef
151: [       OK ] Dense.CalculateTotalColsIsEquivalentToRef (20 ms)
151: [----------] 24 tests from Dense (1783 ms total)

What about creating a cuda/test/utils.hpp header (which includes core/test/utils.hpp), and do the creation of the executor there? That would at least hide the not so pleasant code inside a header and would allow us to improve / remove that in one line instead of in every test-file.
This would obviously require us changing all includes of core/test/utils.hpp to cuda/test/utils.hpp, but that is easy to automate (only needs to be done once).

@thoasm Good idea, I followed your suggestion and only had to patch a small compilation issue with assert and the comma operator in constexpr contexts for HIP.

Does return GKO_ASSERT(...), value; -> GKO_ASSERT(...); return value;  not work?
Or it can not be constexpr?

In C++11, constexpr functions are only allowed to consist of a single return statement, so that unfortunately doesn't work. The expected behavior for NDEBUG would be that assert is replaced by something like void(0), but this weird combination of includes seems to let some asserts vanish. I did not investigate this further yet, since the workaround works.


Outdated

We are in the process of updating these posters.

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

ID: 4dd609f7-fa8a-a9ce-fe89-96b7c368ba1d
Version Independent ID: 6e372641-cb87-b500-5d10-20d68385aa1b
Content: Deploy Windows 10 - architectural posters
Content Source: windows/deployment/windows-10-architecture-posters.md
Product: w10
Technology: windows
GitHub Login: @greg-lindsay
Microsoft Alias: greg-lindsay

Closing the comment.


enable text input and buttons on hotspot

I have hotspot that are html boxes. One box has a text input and a button. I need to let the user to input data, but the keyboard controls the navigation.
Can you explain, if it this is posibble, and how?
thnaks

Temporaly, I download the full version and edit the functions onDocumentKeyUp and onDocumentKeyPress to achieve my goal, but may be this is a feature request to keep in mind.

Add an event listeners for keydown, keyup, and blur to your boxes and set them to function(e) {e.stopPropagation()}. This will prevent any key presses made in the boxes from reaching Pannellum's event listeners.
I also added a disableKeyboardCtrl option two weeks ago in 499fff145dfd04162a8fab33913494206b4ce3e4 that disables the keyboard event listeners.


ENS Domain name resolution initial integration

The beginnings of the Names module and the initial resolution services provided via ENS. Needs some help in terms of wiring the thing into the main embark module.

closing this and the other PR, until they are ready for review

we need to initialize the module, and add the config part


Feature request: Add custom relays

I like to add another relay – maybe even my own.

Included with https://github.com/KoalaSat/nostros/releases/tag/v<IP_ADDRESS>-alpha


How long it takes to test an image

I use the gradio_pose2image.py default configuration, passing a test image into the ui with no results, and setting those parameters?

I was able to generate one image, it took 35 minutes, very long. My GPU is NVIDIA Geforce GTX 2060.

我能够生成一张图像，花了 35 分钟，非常长。我的 GPU 是 NVIDIA Geforce GTX 2060。
感谢您的回答，有没有更快的模型来生成可控图像？

I was able to generate one image, it took 35 minutes, very long. My GPU is NVIDIA Geforce GTX 2060.

Thanks for your answer, is there a faster model to generate controllable images

I was able to generate one image, it took 35 minutes, very long. My GPU is NVIDIA Geforce GTX 2060.

Thanks for your answer, is there a faster model to generate controllable images

Hi, you should try using this, I was able to generate an image in 10 seconds
https://huggingface.co/docs/diffusers/api/pipelines/controlnet
There is also a webui, but I did not try this
https://github.com/Mikubill/sd-webui-controlnet


fix bazel-mappings and runfiles

This also changes the server to serve from $RUNFILES/__main__.
dev_server rules also now only need to provide the ddc_bundle_rule in data, and that will provide all the dart files for source maps via runfiles.
cc @nshahan

Do you have a web app example that works with these changes? When I try to load my demo in a browser I am getting a naming conflict with the moduleName again.
In ddc_bundle.dart_library.js accessing the library fails:
The libraries map contains a key "captains_log" but it is trying to be accessed with "/captains_log"

@nshahan I didn't port the fix for that into this cl. This cl does fix sourcemaps though, as well as clean up the dev_server rules.


Fix up .gitattributes

Contains some text mappings for binary files, should probably clean :-)

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/11540563-fix-up-gitattributes?utm_campaign=plugin&utm_content=tracker%2F15383776&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F15383776&utm_medium=issues&utm_source=github).

Fixed this in #85 and #87 without ever noticing this issue (:
This probably needs to be closed.

Looks clean to me. Thanks rzats


Provide Amazon Aurora database support for our products

Description:
We need to provide Amazon Aurora support for our products in future releases with relevant DB scripts.
Suggested Labels:
database
Suggested Assignees:
Sanjeewa Malalgoda
Affected Product Version:
Future

We have no plans to support this for now hence closing the issue.


lots of ECONNRESET issues

Looking at the logs it seems that in april this would happen at a maximum a few times a day (and on average maybe once every few days)
"An error happened while processing the polled messages":
Error: read ECONNRESET
at exports._errnoException (util.js:1050:11)
at TLSWrap.onread (net.js:581:26)
However recently it has become near constant.  Upon connect it can almost certainly occur (sometimes during the login itself).  Reconnecting right away using the new token also fails falling back to user/pass.
Using a proxy through the same server the web client does not exhibit similar behavior (all poll requests are successful).

Same thing for me. All bots became almost unusable :(

So after trying to solve these ECONNRESET issues I decided to switch to Microsoft Bot API and it works without a single error. Couldn't be happier with it, and it's all free too. If you only need Skype, you won't need to switch to Azure, just remove Web Chat and and Skype channel.
Create your bot here:
https://dev.botframework.com/bots/new
All I needed to do is save address of each channel (used typicode/lowdb for this task):
https://docs.microsoft.com/en-us/azure/bot-service/nodejs/bot-builder-nodejs-proactive-messages

Unfortunately bots can't work with existing users or share a user account (for example to only handle certain messages directly).  For others though it may be a good fit.  I am guessing the issue came about when they did the revision for read receipts.     Unfortunately, I have yet to find a full solution to this bug.

Alright so after updating everything fully clearing all state data (this seemed to cause an issue) I was able to avoid this problem and get good connections again.   May want to use PR #112 to assist with running latest version of libs.

Sadly this issue still persists.   Will have to try proxying some connections to detect the difference.  Not as bad as before but still get a few a day.


Cannot find module './common/html2canvas'

Running snowpack dev with jsPDF installed gives the following error.
Error: Cannot find module ''./common/html2canvas.esm-04ad8f17.js'' from '/home/diblaze/git/x/x/x/x/x/node_modules/jspdf/dist'
  code: 'MODULE_NOT_FOUND'

html2canvas, dompurify and canvg is installed.
Is this related to snowpack way of building the project?

I'm not very familiar with snowpack but it seems like it's doing something different than Webpack, Rollup, or Parcel. I also wonder why it tries to load './common/html2canvas.esm-04ad8f17.js' and not just 'html2canvas'. Could you provide a complete sample project to reproduce the problem?

I have similar issue, when trying to use snowpack in project with jspdf:
UnhandledPromiseRejectionWarning: Error: Cannot find module ''./common/html2canvas.esm-e1665ffd.js'' from '/Users/jakubwolny/projects/x/node_modules/jspdf/dist'
UnhandledPromiseRejectionWarning: Error: Cannot find module ''./common/purify.es-f9b8952a.js'' from '/Users/jakubwolny/projects/x/node_modules/jspdf/dist'

let me try to setup a sample repo

This issue seems to have been resolved in a recent version of snowpack. Please update to snowpack >=3.8.2.


Provide cloud name values for all supported clouds in the docs

Provide example value of the environment() function (specifically the name property) for all supported clouds.

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

ID: 0b99c507-4598-544c-aa4c-3b22d2315d3c
Version Independent ID: adadc545-61bb-7423-4a8d-779edf43691e
Content: Bicep functions - deployment - Azure Resource Manager
Content Source: articles/azure-resource-manager/bicep/bicep-functions-deployment.md
Service: azure-resource-manager
Sub-service: bicep
GitHub Login: @mumian
Microsoft Alias: jgao

@stan-sz Thanks for your comment. We will review the issue and get back to you shortly.

@stan-sz You can retrieve cloud names values by using command Get-AzEnvironment.

@mumian Can you please look into this issue and check if this can be added to the document?

@stan-sz - thanks for this feedback. I'll add some information about the commands for seeing environment names.

The update will get published later today.
#please-close


Fixes to streamed output in native notebooks

For #13611

Codecov Report

Merging #14158 into main will decrease coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main   #14158      +/-   ##
==========================================
- Coverage   59.94%   59.92%   -0.03%
==========================================
  Files         705      705
  Lines       39101    39101
  Branches     5667     5667
==========================================
- Hits        23440    23431       -9
- Misses      14429    14435       +6
- Partials     1232     1235       +3

Impacted Files
Coverage Δ

...very/locators/services/virtualenvwrapperLocator.ts
76.92% <0.00%> (-15.39%)
:arrow_down:

src/client/common/utils/platform.ts
60.00% <0.00%> (-12.00%)
:arrow_down:

.../pythonEnvironments/common/externalDependencies.ts
66.66% <0.00%> (-4.77%)
:arrow_down:

src/client/linters/pydocstyle.ts
86.66% <0.00%> (-2.23%)
:arrow_down:

src/client/datascience/debugLocationTracker.ts
76.56% <0.00%> (-1.57%)
:arrow_down:

src/client/common/process/proc.ts
14.49% <0.00%> (-0.73%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 218dd8d...19c43b2. Read the comment docs.


Publish hfhchan kvariants wrapper on crates.io

Publish the rust wrapper around the file kvariant.txt file coming from https://github.com/hfhchan/irg.

[x] Notify the author (@hfhchan) by e-mail
[ ] Find a proper name for this Library
[ ] Create a CI to publish this new crate on crates.io

Please go ahead, it's licensed under MIT
My only request is that someone keeps it updated via a GitHub Action or some sort of CI.

Please also add a message directing people to submit changes to the dictionary to upstream.


fix typo change to Laravel 7+

update comment as mentioned by @iMokhles here https://github.com/Laravel-Backpack/CRUD/issues/3255#issuecomment-711159261

A new inspection was created.

The inspection completed: No new issues

Thanks again @mahasadhu !


Looks great
/lgtm deps


Address TSLint issues

Our starter code has a lot of "problems" according to TSLint (e.g., we use double quotes when apparently we should be using single quotes). It would be good to get our TSLint issues down to zero (or have reasonable arguments for anything we don't "fix") before we give the code to the students. Then we can expect them to use TSLint and have a small number of issues.

Turns out that IntelliJ has a "Fix TSLint Problems" button that can automate a lot of this, which is nifty. It's especially nice for fixing all the double quote -> single quote conversions, which would have been super tedious otherwise.

This seems to be working just fine in VS Code. Not sure when that was fixed...


Haxchi for 5.5.2

This fixes https://github.com/Plailect/Guide_WiiU/issues/79
Enjoy! This should be enough for now.

Everything should be good now.

Apparently http://sleepii.ovh is a website containing rebranded-code. It's up to you whether or not to include it in the guide.

Closing this for now. Will continue working on this tomorrow.


Update Autoware User Interface to the latest UI

Autoware UI is updated to a more modern look and for sometime the only problematic UI we have is Scenario Simulator UI which still uses the old UI as shown below:
I am expecting Scenario Simulator UI to be updated to the Autoware UI as soon as possible.
If it's possible for @KhalilSelyan to update please let him know.
Autoware UI - Scenario Simulator UI

@KhalilSelyan we have discussed with Mitsudome san and he recommended you to create a PR at scenario simulator and update.  If you have any issues please consult with Berkay.

https://autowarefoundation.github.io/autoware-documentation/main/tutorials/scenario-simulation/planning-simulation/scenario-test-simulation/
🔽
https://github.com/tier4/scenario_simulator_v2/blob/1d219827a28b82a5d0359c0918862e6b0a7c4d2a/test_runner/scenario_test_runner/launch/scenario_test_runner.launch.py#L235-L236
🔽
https://github.com/tier4/scenario_simulator_v2/blob/1d219827a28b82a5d0359c0918862e6b0a7c4d2a/simulation/traffic_simulator/config/scenario_simulator_v2.rviz
This .rviz file needs to be updated.

Yes. it needs to be updated.