HDFS-16778. Separate out the logger for which DN was picked by a DFSInputStream.

Just adds a new logger.

@omalley Why not change all the DFSClient.LOG in DFSInputStream to this new LOG?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
17m 57s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
41m 35s

trunk passed

+1 :green_heart:
compile
1m 11s

trunk passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
1m  0s

trunk passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 39s

trunk passed

+1 :green_heart:
mvnsite
1m  7s

trunk passed

+1 :green_heart:
javadoc
0m 57s

trunk passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 45s

trunk passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
2m 57s

trunk passed

+1 :green_heart:
shadedclient
25m 44s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 55s

the patch passed

+1 :green_heart:
compile
1m  0s

the patch passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
1m  0s

the patch passed

+1 :green_heart:
compile
0m 50s

the patch passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
0m 50s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 24s

the patch passed

+1 :green_heart:
mvnsite
0m 54s

the patch passed

+1 :green_heart:
javadoc
0m 37s

the patch passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 34s

the patch passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
2m 47s

the patch passed

+1 :green_heart:
shadedclient
25m 18s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
2m 25s

hadoop-hdfs-client in the patch passed.

+1 :green_heart:
asflicense
0m 40s

The patch does not generate ASF License warnings.

129m 15s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4911/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4911

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux e93103fc4b49 4.15.0-191-generic #202-Ubuntu SMP Thu Aug 4 01:49:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / b645f1ba38d21ab35ab12b77e20d9b2ab1338b0a

Default Java
Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4911/1/testReport/

Max. process+thread count
531 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs-client U: hadoop-hdfs-project/hadoop-hdfs-client

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4911/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.


Smal Typos/Extensions in Docu

Just tested this on the "DataView & Forms"-Example and everything went fine. Please accept PR, thx.

@4F2E4A2E This reminds me to this ancient pull request. :D Sorry... and merging now (better late than never) :P


Android 4.4.4 issue with dual sim

Expected behaviour
cards array should be listed.
Actual behaviour
cards array is null
I'm seeing this behaviour on

[ ] Android device

I am using

[ ] cordova
[ ] ionic

Hardware models
Example: Samsung Galaxy S6, iPhone 6s
Lenovo A6000
OS versions
Android 4.4.4
I've checked these

[ ] It happens on a fresh Cordova CLI project as well.
[ ] My JavaScript has no errors (window.onerror catches nothing).
[ ] I'm using the latest cordova library, Android SDK, Xcode, etc.

So how can we reproduce this?
Cordova, ionic

It is not a bug.
Check README: this feature is supported with

SubscriptionManager (since API level 22)

On 15 Dec 2016 08:50, "ramesh-sarvatra"<EMAIL_ADDRESS>wrote:

Expected behaviour
cards array should be listed.
Actual behaviour
cards array is null
I'm seeing this behaviour on

Android device

I am using

cordova
ionic

Hardware models
Example: Samsung Galaxy S6, iPhone 6s
Lenovo A6000
OS versions
Android 4.4.4
I've checked these

It happens on a fresh Cordova CLI project as well.
My JavaScript has no errors (window.onerror catches nothing).
I'm using the latest cordova library, Android SDK, Xcode, etc.

So how can we reproduce this?
Cordova, ionic
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pbakondy/cordova-plugin-sim/issues/47, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAej2aovcQSe7NIJrFwX9zLrRW0z8yIIks5rIPFhgaJpZM4LNzu_
.

HI pbakondy,
Currently plugin showing the single sim information on device running on less than lollipop versions.
Could please add cards array on devices running on less than lollipop versions regardless of both sim inserted or single sim inserted?

No I cannot because this older Android version does not support it.

Ok. Thanks!


Update CheckVariables.java

Fix an error message little bit

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Jenkins: ok to test


yahoo partner image fact page takeover

add the yahoo image on every fact page.
instead of printing the partner logo dynamically, just hardcode the yahoo partner image into the template.
put this behind a feature flag, so we can turn it on when the partnership launches, and then remove the code later

@angaither @sbsmith86 The logo will also need to be hyperlinked to something along the lines of search.yahoo.com [UTM parameter] -- final link coming soon.

@namimody is this link with the partner image linked the same as the ones in the google doc, or is this a new link that will be the same across all nodes?

@angaither new link that will be the same across all nodes!

Shoot @angaither totally my bad on this, apparently, "Powered By Yahoo" on 11 Facts is going to link to search.yahoo.com on desktop, and do.yahoo.com on mobile, both with specific UTM parameters (to come). cc @sbsmith86

Hey @sbsmith86! Links below:
Parameter for the Yahoo logo on mobile:
http://do.yahoo.com/?fr=do_dslogo&.tsrc=do-dslogo
Parameter for the Yahoo logo on desktop:
http://search.yahoo.com/?fr=do_dspc&.tsrc=do-dspc


Sample dashboards need correct cluster name

In v0.7 beta sample dashboards can be easily edited, but the samples have a hard-coded cluster name which has to be replaced prior to docker-compose build.
Maybe we can ask for the cluster name in install script.

The above commit should have fixed this.


We need a custom http agent!

https://github.com/joyent/node/issues/4769 has been a nightmare for PouchDB perf because it means connections constantly get closed if we don't immediately have content for them which causes entire 'buckets' of content to be synch'd to be abandoned and started over again. If the resolution in the bug actually works this will seriously juice our perf!
But here is an issue to really scare you - what happens if the pool contains more than one connection and its running over unpaired bluetooth or the multi-peer connectivity framework? Both only have a single socket. I'm not sure how we will run our content over that one socket but my guess is that it will look to us like a single TCP/IP connection. If that is the case then our custom http agent needs to have exactly one one member of its pool.
On the other hand if we are running over any normal TCP transport (e.g. Wi-Fi, Cell, etc.) then we want to use an unlimited number of sockets in the pool.
So we'll need to figure out (eventually) how to dynamically change which pool we are using depending on which transport we are going over. Oh, won't that be fun?

We have solved this problem by creating our own TCP mux layer on top of the P2P connection so Node can open and close connections to its heart's content and it won't affect the P2P connection.


[AWIBOF-7075] Remove debug event logs from TelemetryPublisher

Remove debug event logs from TelemetryPublisher because the event logs are recorded too many times.
Signed-off-by: mjlee34<EMAIL_ADDRESS>

Close this pull request because this should be mereged into release branch.


[Q] where to get front-end example for exceljs

where to get front-end example for exceljs?
Thanks!

希望能出一个官网吧


A lot of errors occur on my device when I build my project, but everything is OK on the simulator

I create en empty project,and install SDWebImage(4.0.0) with cocoapods. A lot of errors occur on my device when I build my project, but everything is OK on the simulator.What happened? The errors like this: Cannot define category for undefined class 'UIButton'、Cannot find interface declaration for 'UIButton'...
Platform Name          iOS
Platform Version        8.0
SDWebImage Version     4.0.0
Integration Method        cocoapods
Xcode Version          Xcode 8.1
Repro rate              all the time (100%)

I just rechecked, the CocoaPods installation works fine - closing. If your issue still persists, you should look into the CocoaPods project for similar problems


Webpack glslify

lgtm :D
This should allow for basic support in other loaders for now

@adnan-wahab Are the changes to the shader meant to be included as well?

I don't really see how this addresses the issue. While this now supports Webpack, we still rely on the glslify transform, which means we rely on glslify-loader. E.g. how does this address usage via AMD?
I thought we were moving away from relying on glslify in library code (and instead moving it into a bundler agnostic build step, like in the previous PR).

If someone is using another module loading paradigm such as AMD they will still be able to use the built version of famous without a problem.
This will at least fix support with webpack and I believe jspm. It is enough for us to support our community while we figure out the most graceful way to EOL glslify

@TheAlphaNerd I'm not sure I understand how this is going to support AMD without usage of the global build. The current solution would still require a preprocessing step for those people from my understanding.

People using amd are going to require a preprocessor either way was my
point.
On Jun 11, 2015 4:43 PM, "Alexander Gugel"<EMAIL_ADDRESS>wrote:

@TheAlphaNerd https://github.com/TheAlphaNerd I'm not sure I understand
how this is going to support AMD without usage of the global build. The
current solution would still require a preprocessing step for those people
from my understanding.
—
Reply to this email directly or view it on GitHub
https://github.com/Famous/engine/pull/270#issuecomment-111307715.

Hmmmm.... ok. I don't really see why we can't just put the shader in the repo to be honest (other than rather purist reasons), but maybe I'm missing something. Anyways. If that solves the issue...

@michaelobriena
yes the changes to the shader are required for this to work

@adnan-wahab Is it because glslify renames the uniforms for some reason? I had that issue, but thought I might be missing something. Still seems kind of a glslify bug to me. If that's the case, we should probably fix that in glslify...

+1 for putting it directly in the repo and dumping glslify
Not sure if that's even possible, but it would be great to use grunt/gulp + bower for build and dep management.  Right now I find it near impossible to incorporate that type of build because of the glslify.  You are left in a state where some dep's are managed through bower and others are through node :grimacing:.
I could be completely wrong, but I would love to be able to list famous as a bower dep and then use traditional gulp / grunt.

@jd-carroll We could still publish to bower with the GLSL code built already.  This would allow people to make changes to our shader code and use those changes without having to download a different tool to compile the shaders for them.

I think the bower + grunt/gulp use case is very important.  Without it, I
think adoption rates will be lower than what they otherwise could be.
On Sun, Jun 14, 2015 at 6:56 PM, michaelobriena<EMAIL_ADDRESS>wrote:

@jd-carroll https://github.com/jd-carroll We could still publish to
bower with the GLSL code built already. This would allow people to make
changes to our shader code and use those changes without having to download
a different tool to compile the shaders for them.
—
Reply to this email directly or view it on GitHub
https://github.com/Famous/engine/pull/270#issuecomment-111882524.

I very much disagree.
We can easily support bower simply by including the standalone in our
tagged version of the platforms
Aside from this the tooling /module loading pattern of the use is a moot
point.
If a develop has a preference, there is nothing stopping them from sticking
famous in their pipeline. Whether it be a script tag or via require (the
standalone will support amd)
If a develop has no preference or does not have experience they can use our
supported work flow with the famous cli and follow along our documentation
to get started.
If you consider that every in production app will have very different
pipeline needs, we cannot ever hope to offer example projects using every
potential tooling system.
What we cam do, and will, is make sure there is nothing in our build that
blocks our developers from using their tool chain of choice.
On Jun 14, 2015 7:47 PM, "Joseph Carroll"<EMAIL_ADDRESS>wrote:

I think the bower + grunt/gulp use case is very important. Without it, I
think adoption rates will be lower than what they otherwise could be.
On Sun, Jun 14, 2015 at 6:56 PM, michaelobriena<EMAIL_ADDRESS>wrote:

@jd-carroll https://github.com/jd-carroll We could still publish to
bower with the GLSL code built already. This would allow people to make
changes to our shader code and use those changes without having to
download
a different tool to compile the shaders for them.
—
Reply to this email directly or view it on GitHub
https://github.com/Famous/engine/pull/270#issuecomment-111882524.

—
Reply to this email directly or view it on GitHub
https://github.com/Famous/engine/pull/270#issuecomment-111905790.

@TheAlphaNerd I agree from a conceptual point of view, but I think the truth is that we can easily support a wider range of tool chains by simply checking in the shader code. This seems like a very acceptable cost considering the increase in usability and that our dependency on glslify has been a problem in the past. I think that's a much more flexible solution than forcing people to use the standalone version.

We can easily support bower simply by including the standalone in our tagged version of the platforms

If we do this, I see no reason why we shouldn't also include the bundled shader code.

@alexanderGugel while I agree with your points, I respectfully disagree in practice.
Our code base makes a few assumptions

Common JS module loading pattern
Browserify build step

This stack allows for us to do some magical things in development, like what we are doing with glslify. It will also support us being able to do something fancy for assertion like you are suggesting in #285
We need to make a higher level decision if we want to rely on AST transformation between development and production. If so, there is no need to check in the GL code. If people want to use our "development" code in production, the only thing stopping them from doing so is their technology stack. If someone chooses to use webpack, then they can either require in our standalone (which will just work), or they can shim the variety of AST manipulations we want to use.
There is no disadvantage to using the standalone build, especially as we can include a version that is unminified and includes source maps. There is nothing stopping them from using the development version either, as they can easily rebuild in-between steps.
The amount of build systems and tooling stacks has no shortage, webpack, JSPM, systemJS, bower, npm, commonJS, AMD, es6.... etc etc etc
We simply cannot support all the edge cases in our development branch, but we can very easily publish a version that is compatible.
If we decide that we need our development branch to be a baseline that works in all systems we are effectively giving up the ability to do AST transformations as part of our development process. Perhaps that is preferred... but I think it is super useful and we should be careful about throwing it away

Our code base makes a few assumptions

Common JS module loading pattern
Browserify build step

The browserify build step is what I'm worried about. One of the advantages of #285 IMO is that everything also "just works fine" without the transform.

We simply cannot support all the edge cases in our development branch, but we can very easily publish a version that is compatible.

I completely agree! Relying on glslify by contrast means the user needs to have Node installed when creating custom builds.
I think checking in the generated glslify is really not a big deal, especially if it increases usability in some cases. That being said I don't have an extremely strong opinion about that since - as you said - users can always still use the standalone build when in doubt. The only thing that I'm worried about is that we need to special case everything because of glslify (e.g. glslify-loader for Webpack), which is IMO not needed.

@alexanderGugel I think our main goal is to support multiple build tools and this does that.  I think moving away from a strict dependency on browserify is a good goal to have but having glslify is great for engine development (which is the point of this repo).
If you don't want our tooling, you can use other tools (because of this change) or just use the standalone as Myles mentioned. I don't think it should be the job of our engineers to maintain personal glsl transform tools just because we want to move off of glslify for no real benefit.

landed as e4e0f0f

As a note regarding gulp and browserify, I have a working famous-gulp-seed which with initial testing supports browserify and the glslify dependency.

Compatible with the famous-cli commands and structure using public also.
Allows for multiple bundle files (multiple entry points)

What I personally think would be a great add for the famous-cli is to allow for the passing of your own seed path on famous create by adding a prompt for a seed. The default would be the famous seed.  People with little tooling experience can use a third party seed. Just an idea.

@adnan-wahab Do you have a working webpack example? If so, I'm curious to learn from it. If not, I'll have one soon for everyone. (:


Make CSS global so that ra_table__ is not appended to table classes. …

…Fixes checkbox CSS bug.

This looks good and works correctly in my local.


Add RSS Stock Parts from Kerbal Stuff

This pull request was automatically generated by Kerbal Stuff on behalf of Yargnit, to add RSS Stock Parts to CKAN.
Please direct questions about this pull request to Yargnit.

#rebuild


Create directories needed by glide.

This avoids glide complaining about missing directories when a developers clones service-catalog and just types 'make'.
#59

Huh? I don't have those folders and I don't see any problems.

Our CI doesn't have these dirs and it seems to be ok too. @vin are you sure this is really an issue? What are you seeing?

Hm, ok. When I just clone service-catalog and try to follow the install instructions, I get this:
vineetk@instance-1:~/service-catalog$ make
glide install --strip-vendor
[WARN]  stat /home/vineetk/service-catalog/src: no such file or directory
[WARN]  stat /home/vineetk/service-catalog/vendor/src: no such file or directory
[ERROR] Could not find any of /home/vineetk/service-catalog//src, /home/vineetk/service-catalog//vendor/src.
[INFO]  As of Glide 0.5/Go 1.5, this is required.
[ERROR] Without src, cannot continue.
Makefile:111: recipe for target '.init' failed
make: *** [.init] Error 1
vineetk@instance-1:~/service-catalog$

Any idea what the difference may be?

ah, I think it might be because you didn't put the service-catalog dir in full go path .../github.com/kubernetes-incubator/service-catalog
Give that a try.
I think when doing native builds it requires that, but if you use Docker then it doesn't.
I'll update the docs once we figure out what's going on....

ah, I think it might be because you didn't put the service-catalog dir in full go path

That is exactly what's happening here. I moved my repo off my $GOPATH and tried a non-containerized build. I got the identical result to @vin's.
Going to close this.

@vin, the docs say this:
# If you have Go installed and want to build w/o Docker, first:
mkdir -p $GOPATH/src/github.com/kubernetes-incubator
cd $GOPATH/src/github.com/kubernetes-incubator

is that not sufficient or do we need to make this more clear in the docs?

OK, cool. I'm making progress after moving my working directory. FWIW I started from README.md, then linked to developer's guide which doesn't mention $GOPATH. It just has "Cloning the repo" instructions with no mention of putting it in a specific location.

@vin I'll update the cloning section of the devguide to be more clear - thanks!

oh wait, with the switch to pushing towards docker build I think this requirement is now gone.
@vin can you grab master and see if it still fails for you when you don't put it under the GOPATH?

You're right; I updated to HEAD and now that it uses docker by default it looks like it's working from ~/service-catalog.

cool thanks for checking


Update documentation_tips.md

The graphic doesn't appear in pandev but does in github

Status
Ready/In Progress/In Hold (Reason for hold)
Related Issues
fixes: link to the issue
Description
A few sentences describing the overall goals of the pull request's commits.
Screenshots
Paste here any images that will help the reviewer

@julieschwartz18 - Can you approve the graphic for me? Thanks


Amend jest snapshots to tie in nicely with Ava

Summary
I am currently working on implementation of jest snapshots into Ava (https://github.com/avajs/ava/pull/1113) and wanted to smooth a few rough edges when implementing with another runner.
In particular:

jest-snapshots relies on a context that has dontThrow function - that however depends too much on the implementation
message on failure contains information about where the failure occurred; that way, the first line of the message says expect(value).toMatchSnapshot() - which again displays an implementation detail that isn't necessary

I'm happy to change the solution but it would be great to address these issues.
Test plan
When integrated with Ava, we get this kind of output:

(Amazingly, when combined with nyc for test coverage, it works seamlessly without any additional work!)

Current coverage is 88.32% (diff: 100%)

Merging #2130 into master will not change coverage

@@             master      #2130   diff @@
==========================================
  Files            38         38
  Lines          1371       1371
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           1211       1211
  Misses          160        160
  Partials          0          0

Powered by Codecov. Last update 6ca7542...ae98ed5

Hey! Thanks for this. I'll be out on vacation next week but happy to look after then.

Thanks @cpojer, looking forward to yur feedback :) Happy Thanksgiving!

I'm not super excited about the dontThrow check but I'm also not feeling strongly about it so I went ahead and merged it.

Thank you @cpojer !

I'll publish a new version of Jest sometime this week once I get through all of these issues. Sorry for making you wait.


Add Fernando Vega to Contributors list

@fvegagiga, I'm quite elated about your PR. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a PR and learned that I merged it?


Enhance client creation with specific URL arguments

Problem
As a dev, I'd like to be able to create a client with specific URLs for consensus and mirror nodes. Reasons:

being able to connect to local nodes during development

Solution
Create a new factory method which accepts 2 URLs - consensusNodeUrl and mirrorNodeUrl.
Example usage:
Client.forNodes('http://localhost:5000', 'http://localhost:5001').setOperator(...);
Alternatives
No response

Not sure how helpful this is, but we use a bunch of mocking tests and this is how we create our server/client for that: https://github.com/hashgraph/hedera-sdk-js/blob/5092b57b5a88126f84f62679e49c92384917d048/test/unit/Mocker.js#L302
However, I understand that for devs simply providing the node IPs makes sense, but we cannot add this since it'd be visible to everyone and is likely to confuse users who are not devs. For now unfortunately you'd need to create a network object map.
Note: You can use Client.fromConfigFile() where you define everything once, that way you wouldn't need to define it in JS, Go, or Java.


@kanaabe => Responsive main layout footer

Closes https://github.com/artsy/force/issues/242
Main layout footer changes to mobile version at 600px, has anonymous and logged in states.

💯  so awesome! what does a signup/login look like with the mobile width? I'm assuming those will eventually have to be updated as well.

@kanaabe - not bad actually!  It is already responsive down to 400

Great, merging


[release-1.3] fix(stackdriver): pull mesh uid from config

Manual cherry-pick of #18655

@douglas-reid: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test lint_istio_release-1.3

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.

@douglas-reid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test lint_istio_release-1.3

integ-new-install-k8s-tests_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test integ-new-install-k8s-tests_istio_release-1.3

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.

@douglas-reid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test lint_istio_release-1.3

integ-new-install-k8s-tests_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test integ-new-install-k8s-tests_istio_release-1.3

pilot-multicluster-e2e_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test pilot-multicluster-e2e_istio_release-1.3

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.

@douglas-reid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test lint_istio_release-1.3

integ-new-install-k8s-tests_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test integ-new-install-k8s-tests_istio_release-1.3

pilot-multicluster-e2e_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test pilot-multicluster-e2e_istio_release-1.3

e2e-dashboard_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test e2e-dashboard_istio_release-1.3

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.

@douglas-reid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test lint_istio_release-1.3

integ-new-install-k8s-tests_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test integ-new-install-k8s-tests_istio_release-1.3

pilot-multicluster-e2e_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test pilot-multicluster-e2e_istio_release-1.3

e2e-dashboard_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test e2e-dashboard_istio_release-1.3

unit-tests_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test unit-tests_istio_release-1.3

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.

@douglas-reid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test lint_istio_release-1.3

integ-new-install-k8s-tests_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test integ-new-install-k8s-tests_istio_release-1.3

pilot-multicluster-e2e_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test pilot-multicluster-e2e_istio_release-1.3

e2e-dashboard_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test e2e-dashboard_istio_release-1.3

unit-tests_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test unit-tests_istio_release-1.3

codecov_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test codecov_istio_release-1.3

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.

@douglas-reid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test lint_istio_release-1.3

integ-new-install-k8s-tests_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test integ-new-install-k8s-tests_istio_release-1.3

pilot-multicluster-e2e_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test pilot-multicluster-e2e_istio_release-1.3

e2e-dashboard_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test e2e-dashboard_istio_release-1.3

unit-tests_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test unit-tests_istio_release-1.3

codecov_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test codecov_istio_release-1.3

racetest_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test racetest_istio_release-1.3

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.

@douglas-reid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-new-install-k8s-tests_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test integ-new-install-k8s-tests_istio_release-1.3

pilot-multicluster-e2e_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test pilot-multicluster-e2e_istio_release-1.3

e2e-dashboard_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test e2e-dashboard_istio_release-1.3

unit-tests_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test unit-tests_istio_release-1.3

codecov_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test codecov_istio_release-1.3

racetest_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test racetest_istio_release-1.3

lint_istio_release-1.3
122394f64d58361130bb95795ab4cd773cf8f9b3
link
/test lint_istio_release-1.3

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.

@douglas-reid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pilot-multicluster-e2e_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test pilot-multicluster-e2e_istio_release-1.3

e2e-dashboard_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test e2e-dashboard_istio_release-1.3

unit-tests_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test unit-tests_istio_release-1.3

codecov_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test codecov_istio_release-1.3

racetest_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test racetest_istio_release-1.3

lint_istio_release-1.3
122394f64d58361130bb95795ab4cd773cf8f9b3
link
/test lint_istio_release-1.3

integ-new-install-k8s-tests_istio_release-1.3
122394f64d58361130bb95795ab4cd773cf8f9b3
link
/test integ-new-install-k8s-tests_istio_release-1.3

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.

@douglas-reid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-dashboard_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test e2e-dashboard_istio_release-1.3

unit-tests_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test unit-tests_istio_release-1.3

codecov_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test codecov_istio_release-1.3

racetest_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test racetest_istio_release-1.3

lint_istio_release-1.3
122394f64d58361130bb95795ab4cd773cf8f9b3
link
/test lint_istio_release-1.3

integ-new-install-k8s-tests_istio_release-1.3
122394f64d58361130bb95795ab4cd773cf8f9b3
link
/test integ-new-install-k8s-tests_istio_release-1.3

pilot-multicluster-e2e_istio_release-1.3
122394f64d58361130bb95795ab4cd773cf8f9b3
link
/test pilot-multicluster-e2e_istio_release-1.3

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.

@douglas-reid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test unit-tests_istio_release-1.3

codecov_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test codecov_istio_release-1.3

racetest_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test racetest_istio_release-1.3

lint_istio_release-1.3
122394f64d58361130bb95795ab4cd773cf8f9b3
link
/test lint_istio_release-1.3

integ-new-install-k8s-tests_istio_release-1.3
122394f64d58361130bb95795ab4cd773cf8f9b3
link
/test integ-new-install-k8s-tests_istio_release-1.3

pilot-multicluster-e2e_istio_release-1.3
122394f64d58361130bb95795ab4cd773cf8f9b3
link
/test pilot-multicluster-e2e_istio_release-1.3

e2e-dashboard_istio_release-1.3
122394f64d58361130bb95795ab4cd773cf8f9b3
link
/test e2e-dashboard_istio_release-1.3

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.

@douglas-reid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

codecov_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test codecov_istio_release-1.3

racetest_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test racetest_istio_release-1.3

lint_istio_release-1.3
122394f64d58361130bb95795ab4cd773cf8f9b3
link
/test lint_istio_release-1.3

integ-new-install-k8s-tests_istio_release-1.3
122394f64d58361130bb95795ab4cd773cf8f9b3
link
/test integ-new-install-k8s-tests_istio_release-1.3

pilot-multicluster-e2e_istio_release-1.3
122394f64d58361130bb95795ab4cd773cf8f9b3
link
/test pilot-multicluster-e2e_istio_release-1.3

e2e-dashboard_istio_release-1.3
122394f64d58361130bb95795ab4cd773cf8f9b3
link
/test e2e-dashboard_istio_release-1.3

unit-tests_istio_release-1.3
122394f64d58361130bb95795ab4cd773cf8f9b3
link
/test unit-tests_istio_release-1.3

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.

@douglas-reid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

codecov_istio_release-1.3
caed32a1b8f70a3383dc7c1a85ec18e1e00773f2
link
/test codecov_istio_release-1.3

lint_istio_release-1.3
122394f64d58361130bb95795ab4cd773cf8f9b3
link
/test lint_istio_release-1.3

integ-new-install-k8s-tests_istio_release-1.3
122394f64d58361130bb95795ab4cd773cf8f9b3
link
/test integ-new-install-k8s-tests_istio_release-1.3

pilot-multicluster-e2e_istio_release-1.3
122394f64d58361130bb95795ab4cd773cf8f9b3
link
/test pilot-multicluster-e2e_istio_release-1.3

e2e-dashboard_istio_release-1.3
122394f64d58361130bb95795ab4cd773cf8f9b3
link
/test e2e-dashboard_istio_release-1.3

unit-tests_istio_release-1.3
122394f64d58361130bb95795ab4cd773cf8f9b3
link
/test unit-tests_istio_release-1.3

racetest_istio_release-1.3
122394f64d58361130bb95795ab4cd773cf8f9b3
link
/test racetest_istio_release-1.3

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.

@douglas-reid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_istio_release-1.3
122394f64d58361130bb95795ab4cd773cf8f9b3
link
/test lint_istio_release-1.3

integ-new-install-k8s-tests_istio_release-1.3
122394f64d58361130bb95795ab4cd773cf8f9b3
link
/test integ-new-install-k8s-tests_istio_release-1.3

pilot-multicluster-e2e_istio_release-1.3
122394f64d58361130bb95795ab4cd773cf8f9b3
link
/test pilot-multicluster-e2e_istio_release-1.3

e2e-dashboard_istio_release-1.3
122394f64d58361130bb95795ab4cd773cf8f9b3
link
/test e2e-dashboard_istio_release-1.3

unit-tests_istio_release-1.3
122394f64d58361130bb95795ab4cd773cf8f9b3
link
/test unit-tests_istio_release-1.3

racetest_istio_release-1.3
122394f64d58361130bb95795ab4cd773cf8f9b3
link
/test racetest_istio_release-1.3

codecov_istio_release-1.3
122394f64d58361130bb95795ab4cd773cf8f9b3
link
/test codecov_istio_release-1.3

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.

@douglas-reid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_istio_release-1.3
122394f64d58361130bb95795ab4cd773cf8f9b3
link
/test lint_istio_release-1.3

pilot-multicluster-e2e_istio_release-1.3
122394f64d58361130bb95795ab4cd773cf8f9b3
link
/test pilot-multicluster-e2e_istio_release-1.3

e2e-dashboard_istio_release-1.3
122394f64d58361130bb95795ab4cd773cf8f9b3
link
/test e2e-dashboard_istio_release-1.3

unit-tests_istio_release-1.3
122394f64d58361130bb95795ab4cd773cf8f9b3
link
/test unit-tests_istio_release-1.3

racetest_istio_release-1.3
122394f64d58361130bb95795ab4cd773cf8f9b3
link
/test racetest_istio_release-1.3

codecov_istio_release-1.3
122394f64d58361130bb95795ab4cd773cf8f9b3
link
/test codecov_istio_release-1.3

integ-new-install-k8s-tests_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test integ-new-install-k8s-tests_istio_release-1.3

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.

@douglas-reid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_istio_release-1.3
122394f64d58361130bb95795ab4cd773cf8f9b3
link
/test lint_istio_release-1.3

e2e-dashboard_istio_release-1.3
122394f64d58361130bb95795ab4cd773cf8f9b3
link
/test e2e-dashboard_istio_release-1.3

unit-tests_istio_release-1.3
122394f64d58361130bb95795ab4cd773cf8f9b3
link
/test unit-tests_istio_release-1.3

racetest_istio_release-1.3
122394f64d58361130bb95795ab4cd773cf8f9b3
link
/test racetest_istio_release-1.3

codecov_istio_release-1.3
122394f64d58361130bb95795ab4cd773cf8f9b3
link
/test codecov_istio_release-1.3

integ-new-install-k8s-tests_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test integ-new-install-k8s-tests_istio_release-1.3

pilot-multicluster-e2e_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test pilot-multicluster-e2e_istio_release-1.3

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.

@douglas-reid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.3
122394f64d58361130bb95795ab4cd773cf8f9b3
link
/test unit-tests_istio_release-1.3

racetest_istio_release-1.3
122394f64d58361130bb95795ab4cd773cf8f9b3
link
/test racetest_istio_release-1.3

codecov_istio_release-1.3
122394f64d58361130bb95795ab4cd773cf8f9b3
link
/test codecov_istio_release-1.3

integ-new-install-k8s-tests_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test integ-new-install-k8s-tests_istio_release-1.3

pilot-multicluster-e2e_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test pilot-multicluster-e2e_istio_release-1.3

e2e-dashboard_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test e2e-dashboard_istio_release-1.3

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.

@douglas-reid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

racetest_istio_release-1.3
122394f64d58361130bb95795ab4cd773cf8f9b3
link
/test racetest_istio_release-1.3

codecov_istio_release-1.3
122394f64d58361130bb95795ab4cd773cf8f9b3
link
/test codecov_istio_release-1.3

integ-new-install-k8s-tests_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test integ-new-install-k8s-tests_istio_release-1.3

pilot-multicluster-e2e_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test pilot-multicluster-e2e_istio_release-1.3

e2e-dashboard_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test e2e-dashboard_istio_release-1.3

unit-tests_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test unit-tests_istio_release-1.3

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.

@douglas-reid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-new-install-k8s-tests_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test integ-new-install-k8s-tests_istio_release-1.3

pilot-multicluster-e2e_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test pilot-multicluster-e2e_istio_release-1.3

e2e-dashboard_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test e2e-dashboard_istio_release-1.3

unit-tests_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test unit-tests_istio_release-1.3

integ-pilot-k8s-tests_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test integ-pilot-k8s-tests_istio_release-1.3

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.

@douglas-reid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-new-install-k8s-tests_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test integ-new-install-k8s-tests_istio_release-1.3

pilot-multicluster-e2e_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test pilot-multicluster-e2e_istio_release-1.3

e2e-dashboard_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test e2e-dashboard_istio_release-1.3

unit-tests_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test unit-tests_istio_release-1.3

integ-pilot-k8s-tests_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test integ-pilot-k8s-tests_istio_release-1.3

integ-mixer-k8s-tests_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test integ-mixer-k8s-tests_istio_release-1.3

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

/retest
Test failures unrelated to these changes.

@douglas-reid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pilot-multicluster-e2e_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test pilot-multicluster-e2e_istio_release-1.3

e2e-dashboard_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test e2e-dashboard_istio_release-1.3

unit-tests_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test unit-tests_istio_release-1.3

integ-pilot-k8s-tests_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test integ-pilot-k8s-tests_istio_release-1.3

integ-mixer-k8s-tests_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test integ-mixer-k8s-tests_istio_release-1.3

integ-new-install-k8s-tests_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test integ-new-install-k8s-tests_istio_release-1.3

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.

@douglas-reid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-dashboard_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test e2e-dashboard_istio_release-1.3

unit-tests_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test unit-tests_istio_release-1.3

integ-pilot-k8s-tests_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test integ-pilot-k8s-tests_istio_release-1.3

integ-mixer-k8s-tests_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test integ-mixer-k8s-tests_istio_release-1.3

integ-new-install-k8s-tests_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test integ-new-install-k8s-tests_istio_release-1.3

pilot-multicluster-e2e_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test pilot-multicluster-e2e_istio_release-1.3

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.

@douglas-reid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test unit-tests_istio_release-1.3

integ-pilot-k8s-tests_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test integ-pilot-k8s-tests_istio_release-1.3

integ-mixer-k8s-tests_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test integ-mixer-k8s-tests_istio_release-1.3

integ-new-install-k8s-tests_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test integ-new-install-k8s-tests_istio_release-1.3

pilot-multicluster-e2e_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test pilot-multicluster-e2e_istio_release-1.3

e2e-dashboard_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test e2e-dashboard_istio_release-1.3

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.

@douglas-reid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-new-install-k8s-tests_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test integ-new-install-k8s-tests_istio_release-1.3

pilot-multicluster-e2e_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test pilot-multicluster-e2e_istio_release-1.3

e2e-dashboard_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test e2e-dashboard_istio_release-1.3

integ-mixer-k8s-tests_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test integ-mixer-k8s-tests_istio_release-1.3

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

/test integ-new-install-k8s-tests_istio_release-1.3
/test pilot-multicluster-e2e_istio_release-1.3
/test e2e-dashboard_istio_release-1.3
/test integ-mixer-k8s-tests_istio_release-1.3

@douglas-reid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pilot-multicluster-e2e_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test pilot-multicluster-e2e_istio_release-1.3

e2e-dashboard_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test e2e-dashboard_istio_release-1.3

integ-mixer-k8s-tests_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test integ-mixer-k8s-tests_istio_release-1.3

integ-new-install-k8s-tests_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test integ-new-install-k8s-tests_istio_release-1.3

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.

@douglas-reid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-dashboard_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test e2e-dashboard_istio_release-1.3

integ-mixer-k8s-tests_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test integ-mixer-k8s-tests_istio_release-1.3

integ-new-install-k8s-tests_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test integ-new-install-k8s-tests_istio_release-1.3

pilot-multicluster-e2e_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test pilot-multicluster-e2e_istio_release-1.3

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.

@douglas-reid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test integ-mixer-k8s-tests_istio_release-1.3

integ-new-install-k8s-tests_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test integ-new-install-k8s-tests_istio_release-1.3

pilot-multicluster-e2e_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test pilot-multicluster-e2e_istio_release-1.3

e2e-dashboard_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test e2e-dashboard_istio_release-1.3

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

/test integ-new-install-k8s-tests_istio_release-1.3
/test pilot-multicluster-e2e_istio_release-1.3
/test e2e-dashboard_istio_release-1.3

@douglas-reid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pilot-multicluster-e2e_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test pilot-multicluster-e2e_istio_release-1.3

e2e-dashboard_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test e2e-dashboard_istio_release-1.3

integ-new-install-k8s-tests_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test integ-new-install-k8s-tests_istio_release-1.3

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.

@douglas-reid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pilot-multicluster-e2e_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test pilot-multicluster-e2e_istio_release-1.3

integ-new-install-k8s-tests_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test integ-new-install-k8s-tests_istio_release-1.3

e2e-dashboard_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test e2e-dashboard_istio_release-1.3

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.

@douglas-reid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-new-install-k8s-tests_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test integ-new-install-k8s-tests_istio_release-1.3

e2e-dashboard_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test e2e-dashboard_istio_release-1.3

pilot-multicluster-e2e_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test pilot-multicluster-e2e_istio_release-1.3

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.

it looks like those tests are maybe just broken on 1.3 ?

/test integ-new-install-k8s-tests_istio_release-1.3
/test pilot-multicluster-e2e_istio_release-1.3
/test e2e-dashboard_istio_release-1.3
retrying all flakes. any failures are unrelated to this PR.

@douglas-reid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-dashboard_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test e2e-dashboard_istio_release-1.3

pilot-multicluster-e2e_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test pilot-multicluster-e2e_istio_release-1.3

integ-new-install-k8s-tests_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test integ-new-install-k8s-tests_istio_release-1.3

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.

@douglas-reid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-dashboard_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test e2e-dashboard_istio_release-1.3

integ-new-install-k8s-tests_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test integ-new-install-k8s-tests_istio_release-1.3

pilot-multicluster-e2e_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test pilot-multicluster-e2e_istio_release-1.3

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.

@douglas-reid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-new-install-k8s-tests_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test integ-new-install-k8s-tests_istio_release-1.3

pilot-multicluster-e2e_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test pilot-multicluster-e2e_istio_release-1.3

e2e-dashboard_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test e2e-dashboard_istio_release-1.3

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.

Ping on review.

/test e2e-dashboard_istio_release-1.

/retest

@douglas-reid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pilot-multicluster-e2e_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test pilot-multicluster-e2e_istio_release-1.3

e2e-dashboard_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test e2e-dashboard_istio_release-1.3

integ-new-install-k8s-tests_istio_release-1.3
c2a6fa1c7efca010d01772f9ec1948428574f796
link
/test integ-new-install-k8s-tests_istio_release-1.3

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.


Fix physical back button behavior on Android

FYI: Tried with https://ionic-docs-5utg8ms4c-ionic1.vercel.app/docs/v5/developing/hardware-back-button but didn't seem to work for some reason.


finos#924: Fix accessibility issue with select fields in Typography Font Settings

Ensure all select fields in the Typography Font Settings page have proper labels to improve accessibility. This fixes issue #924.
The proposed solution is to add labelId and aria-describedby attributes to the select elements, referencing the corresponding labels and descriptions. This will ensure that screen readers can properly identify and describe the select fields.
Please review and merge this pull request to address the accessibility issue.

Linked wrong email - closing


Proposal: support multiple image types

Sometimes projects want to ship software in both image types supported by jpackage for a determined OS.
I found a way to implement it overriding the action() function.
https://github.com/AlchemistSimulator/Alchemist/blob/9d0ba2e8a8264cebf737126051e1615e4bcd1753/alchemist-full/build.gradle.kts#L46-L60
It looks kinda ugly, it could be avoided by supporting a list of types instead of one single type.

@Zimbrando
Your solution works really well, I did not think of extending it like that.
Thank you very much!


[GCD] Creating the training data pipeline

estimate 6
remaining 2020-10-10 6
remaining 2020-12-2 3

[x] Make a TF dataset object
[ ] Create the pipeline

done


[Feature Request]: Parallelism on using top agent from multi document agent while comparing multiple documents

Feature Description
Currently the same query passed to top agent extracts information from document1 (agent1) and then extracts from document 2 (agent2) sequentially and then at last comparison happens which is why it takes time to respond. Is there any feature to query each document in parallel and compare.
Reason
No response
Value of Feature
No response

I'm not sure what you would like here 🤔
An agent typically picks one tool at a time, and then calls it, reads the response, and decides what to do next. Its a pretty sequential task in general.
We do have a ParallelAgentRunner in our lower level agent API, but I noticed there's no example of using it. This will execute a DAG of tasks concurrently with async


swapping out the s3 bucket link for snark-keys

this change mirrors the changes merged in release 3.0.1: https://github.com/MinaProtocol/mina/pull/15824/files

!ci-build-me

!ci-build-me

!ci-build-me

Please consider the suggestions made here before merging


Perform null check before dereference

This code path gets when when we try to handleError while closing go cql connection closeWithError which internally calls HandleError.

@shubhamjadhav You have to merge the commit to rubrik-master not master.


[BUG] bootstrap.sh offline installation.

[Provide general introduction to the issue logging and why it is relevant to this repository.]
On the offline installation, the requirements.txt when offline download seems to not be downloading all the requirements dependencies, what creates some erros on the bootstrap script installation on offline_mode.
╔══════════════════════════════════════════════╗
║ Installing python needed dependencies via pip3...
╚══════════════════════════════════════════════╝
Defaulting to user installation because normal site-packages is not writeable
Looking in links: /home/bluebanquise/bluebanquise/offline_bootstrap/pip3/
Requirement already satisfied: pip in /usr/local/lib/python3.6/site-packages (from -r requirements.txt (line 1)) (21.3.1)
Processing ./offline_bootstrap/pip3/ansible-4.10.0.tar.gz
Preparing metadata (setup.py) ... done
Processing ./offline_bootstrap/pip3/netaddr-0.8.0-py2.py3-none-any.whl
Processing ./offline_bootstrap/pip3/ClusterShell-1.8.4.tar.gz
Preparing metadata (setup.py) ... done
Processing ./offline_bootstrap/pip3/jmespath-0.10.0-py2.py3-none-any.whl
Processing ./offline_bootstrap/pip3/ansible-core-2.11.12.tar.gz
Preparing metadata (setup.py) ... done
Processing ./offline_bootstrap/pip3/importlib_resources-5.4.0-py3-none-any.whl
Processing ./offline_bootstrap/pip3/PyYAML-6.0.tar.gz
Installing build dependencies ... error
ERROR: Command errored out with exit status 1:
command: /usr/bin/python3.6 /usr/local/lib/python3.6/site-packages/pip install --ignore-installed --no-user --prefix /tmp/pip-build-env-mcsz_02a/overlay --no-warn-script-location --no-binary :none: --only-binary :none: --no-index --find-links /home/bluebanquise/bluebanquise/offline_bootstrap/pip3/ -- setuptools wheel Cython
cwd: None
Complete output (3 lines):
Looking in links: /home/bluebanquise/bluebanquise/offline_bootstrap/pip3/
ERROR: Could not find a version that satisfies the requirement setuptools (from versions: none)
ERROR: No matching distribution found for setuptools
WARNING: Discarding file:///home/bluebanquise/bluebanquise/offline_bootstrap/pip3/PyYAML-6.0.tar.gz. Command errored out with exit status 1: /usr/bin/python3.6 /usr/local/lib/python3.6/site-packages/pip install --ignore-installed --no-user --prefix /tmp/pip-build-env-mcsz_02a/overlay --no-warn-script-location --no-binary :none: --only-binary :none: --no-index --find-links /home/bluebanquise/bluebanquise/offline_bootstrap/pip3/ -- setuptools wheel Cython Check the logs for full command output.
INFO: pip is looking at multiple versions of netaddr to determine which version is compatible with other requirements. This could take a while.
INFO: pip is looking at multiple versions of  to determine which version is compatible with other requirements. This could take a while.
INFO: pip is looking at multiple versions of ansible to determine which version is compatible with other requirements. This could take a while.
INFO: pip is looking at multiple versions of pip to determine which version is compatible with other requirements. This could take a while.
Processing ./offline_bootstrap/pip3/pip-21.3.1-py3-none-any.whl
ERROR: Could not find a version that satisfies the requirement PyYAML (from clustershell) (from versions: 6.0)
ERROR: No matching distribution found for PyYAML
[Provide more detailed introduction to the issue context.]
Os is RedHat 8.5 and it was installed as minimal install.

Dear @santos-lucas
Interesting, thanks a lot for catching this. I will setup a VM and investigate 🙂

Should be solved now :blush:
Closing.


Use UFCS in macros

Closes #3304

Pull Request Test Coverage Report for Build<PHONE_NUMBER>7
Details

3 of 4 (75.0%)  changed or added relevant lines in 3 files are covered.
2 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.01%) to 82.784%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

hashes/src/internal_macros.rs
1
2
50.0%

Files with Coverage Reduction
New Missed Lines
%

hashes/src/internal_macros.rs
1
61.54%

bitcoin/src/internal_macros.rs
1
73.4%

Totals

Change from base Build<PHONE_NUMBER>8:
0.01%

Covered Lines:
18941

Relevant Lines:
22880

💛  - Coveralls

Why is this marked as draft? I guess because it's incomplete?

@apoelstra taking this PR out of draft.
I couldn't find any other macros that required a trait to be in scope to use like in https://github.com/rust-bitcoin/rust-bitcoin/pull/3128#discussion_r1743138964, but there were some that I feel are cleaner with UFCS.

Nice!


Show total tiles

Sorry, I should done it before. Now I'm displaying of total tiles selected in the area as well.

Don't be sorry :), nice job.


Document the container/app lifecycle

Users want to know things like:

what signals are sent to the containers on kill.
how does handover between updates happen by default
what happens when a container crashes
what happens when a container hangs
is there an automatic roll back?

 Front conversations

A signal handling example (but need to check if still works with current setup because it's a few months old): https://github.com/resin-io-projects/resin-watchdog/blob/master/src/start.sh

Yeah I think that's gonna change in the next release, so probably won't work anymore :/


is there any listing of currently supported format?

the whole question is in title

Do you mean - which versions of barcodes we support? If so the whole answer is in the name - only QR codes 😛
If you mean what version and encoding schemes for QRs we support..we should support all of them. If that's not the case feel free to report an issue.
Closing this issue as I hope I've answered your question but if not please comment and I'll be happy to help.


Fix miss-use of a Secret vs ConfigMap in a configmap.md document.

Hello.
It looks like the word Secret is used instead of ConfigMap by mistake in a configmap.md documentation page.
These changes contain a possible fix.

I signed it

/lgtm
Nice catch.

/approve


Some bones missing from gltf exported cs2 weapon model

Describe the bug
VMDL_C Import

GLTF Import

Describe the bug
I extracted the "weapon_rif_ak47.vmdl_c" model, which I performed the "Decompile & Export" process using VRF, with the "GLTF" format. The model I created with GLTF format is missing some bones.

What game does this happen in
Counter-Strike 2
Reference file in a Source 2 game
VMDL_C.zip
GLTF.zip
Expected behavior
GLTF must have 42 bones
What version of VRF are you using? On what platform?
5.0.2236 / Windows 10 Pro

This happens because we filter out bones by ModelSkeletonBoneFlags.BoneUsedByVertexLod0, removing that exports them just fine.


feat(dataprocess): Add status aspect to allow for soft deletes

Adds status aspect to the dataProcessInstance so that we can perform soft deletion on data process instance runs.
This was tested locally with a manual data process run which was then soft deleted through the cli.
Checklist

[x] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[ ] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

Closing in favor of https://github.com/datahub-project/datahub/pull/10757


fix custom scene arguments from the editor

sequel of #7347
Play edited scene and Play custom scene didn't worked when main_run_args
hadn't $scene as argument.
Changes/Fixes the way how the editor handles scene paths when starting the
project/a scene
Play the project - no scene path
Play the edited scene - scene path of active scene in the editor
Play custom scene - scene path of custom scene
main_arg_runs is now empty by default and $scene won't be replaced
by the scene path anymore
Changed declaration if EditorRun::run, to remove a unused value

Does running a custom scene from the command line still work with this change?

yes godot myCustomscene.tscn still works.
The changes affect only how the editor constructs the command, not how godot process them.


Support socket manipulation through the server_conn hook.

The checks for self.[rfile|wfile] have been introduced to avoid the following exceptions:
Traceback (most recent call last):
  File "/tmp/mitmproxy/mitmproxy/proxy/server.py", line 119, in handle
    root_layer()
  File "/tmp/mitmproxy/mitmproxy/proxy/modes/transparent_proxy.py", line 25, in __call__
    self.disconnect()
  File "/tmp/mitmproxy/mitmproxy/protocol/base.py", line 162, in disconnect
    self.server_conn.finish()
  File "/tmp/mitmproxy/mitmproxy/models/connections.py", line 226, in finish
    tcp.TCPClient.finish(self)
  File "/tmp/mitmproxy/netlib/tcp.py", line 488, in finish
    self.wfile.flush()
AttributeError: 'NoneType' object has no attribute 'flush'

Traceback (most recent call last):
  File "/tmp/mitmproxy/mitmproxy/proxy/server.py", line 119, in handle
    root_layer()
  File "/tmp/mitmproxy/mitmproxy/proxy/modes/transparent_proxy.py", line 25, in __call__
    self.disconnect()
  File "/tmp/mitmproxy/mitmproxy/protocol/base.py", line 162, in disconnect
    self.server_conn.finish()
  File "/tmp/mitmproxy/mitmproxy/models/connections.py", line 226, in finish
    tcp.TCPClient.finish(self)
  File "/tmp/mitmproxy/netlib/tcp.py", line 494, in finish
    self.rfile.close()
AttributeError: 'NoneType' object has no attribute 'close'

These exceptions occur if the box, on which mitmproxy is running on, is unable to set up a connection to an external resource, and thereby violates disconnect's precondition.
https://github.com/mitmproxy/mitmproxy/blob/0dbb7033ee1a6e238752381ce99439ef7d38b208/mitmproxy/protocol/base.py#L148-L151

Would you guys be fine with the following?
diff --git a/netlib/tcp.py b/netlib/tcp.py
index eea1042..ba86113 100644
--- a/netlib/tcp.py
+++ b/netlib/tcp.py
@@ -727,9 +727,12 @@ class TCPClient(_Connection):
         self.rfile.set_descriptor(self.connection)
         self.wfile.set_descriptor(self.connection)

+    def _makesocket(self):
+        # some parties (cuckoo sandbox) need to hook this
+        return socket.socket(self.address.family, socket.SOCK_STREAM)
+
     def connect(self):
         try:
-            connection = socket.socket(self.address.family, socket.SOCK_STREAM)
+            connection = self._makesocket()

             if self.spoof_source_address:
                 try:

Fixed by #1583.


cf help [command] does not work for commands that use the command registry

cf help push, cf help api, etc. show:
cf: 'api' is not a registered command. See 'cf help'

I would expect the output to be the same as cf push --help or cf api --help, e.g.:
NAME:
   api - Set or view target api url

USAGE:
   CF_NAME api [URL]

OPTIONS:
   --unset                    Remove all api endpoint targeting
   --skip-ssl-validation      Please don't

@wendorf what version of the CLI?
I get the correct results with edge:
○ → cf -v
cf version 6.12.2-90b26dd-2015-07-21T04:53:35+00:00

 |1.9.3-p484| london in ~/Downloads
○ → cf help push
NAME:
   push - Push a new app or sync changes to an existing app

ALIAS:
   p

USAGE:
   Push a single app (with or without a manifest):
   cf push APP_NAME [-b BUILDPACK_NAME] [-c COMMAND] [-d DOMAIN] [-f MANIFEST_PATH]
   [-i NUM_INSTANCES] [-k DISK] [-m MEMORY] [-n HOST] [-p PATH] [-s STACK] [-t TIMEOUT]
   [--no-hostname] [--no-manifest] [--no-route] [--no-start]

   Push multiple apps with a manifest:
   cf push [-f MANIFEST_PATH]

OPTIONS:
   -b 			Custom buildpack by name (e.g. my-buildpack) or GIT URL (e.g. 'https://github.com/heroku/heroku-buildpack-play.git') or GIT BRANCH URL (e.g. 'https://github.com/heroku/heroku-buildpack-play.git#develop' for 'develop' branch). Use built-in buildpacks only by setting value to 'null' or 'default'
   -c 			Startup command, set to null to reset to default start command
   -d 			Domain (e.g. example.com)

This bug is only observable with commands implemented in our new structure (such as api, apps). However, the bug has just been fixed.
The fix will be in the next stable release.


Upload Imager support

You said you had it - is it in here?

It is uploaded.  There is still a bug, but it shouldn't be hit very often.


Rewrite MutableObjectModelBinder

A rewrite focused on simplifying extensibility points and reducing
allocations.
/cc @dougbu
Using 3000 requests to BigModelBinding scenario for comparison
Before

After

Knocks off about 128mb (16%) of allocated bytes from this scenario. There's really a mixed bag of improvements here, mostly it comes from eliminating async state machines and intermediate state.
This changeset is really focused on simplifying the code and making the extensibility points more useful. This is one of those joyous occasions where simplicity and perf are out on a dinner date :cupid:

:shipit: after you've added docs.

:watch: for doc comments and a few issues described above.

@dougbu - updated. Currently going through the experiment of removing the collection code.

354 additions, 802 deletions not shown because the diff is too large. Please use a local Git client to view these changes.

github says the diff on the tests is too high.

github says the diff on the tests is too high

Don't worry about it -- just the GitHub UI. The changes are visible in the commit(s) which is why I commented there in previous iteration.

:watch: just for remaining unit test fallout.

:shipit: w/ comment change discussed offline.

Will merge once dev is open for checkins


Fitting Empirical Models to Change over Time/Cycles

A common analysis for machine learning data is to fit an empirical model to how a property changes over cycles.

[ ] Linear models
[ ] Bilinear models

This is going to be part of moirae instead


Allow passing different session "states" per channel

When using different types of sessions, with different states, it's useful to be able to specify the state type of sessions inside a channel (instead of overwriting / extending the interface).
This change allows to pass the session state type in addition to the channel state:
const channel = createChannel<any, { flag: boolean }>();

Thanks so much for contributing! This will be included in the next release.


Check for existing connection to peer address before trying to start new connection

https://github.com/yzernik/squeaknode/pull/1007


Update Angular to Angular 4

Current version of AngularJS is 1.6.1
Should be updated to version  4 in order to use the latest available technology....

The code has been moved to react.js


New sample/sharepoint searchand optimizasion

Copilot will generate summary of the documents found in SharePoint Online for the specific topic. It will show the list of documents found in SharePoint Online and a summary of the content of the documents.

Thank you so much @ValerasNarbutas !


TBL - Dump Table Registry Data Command Can Hog CPU (GSFC DCR 23031)

The GSFC NICER FSW team discovered that it takes approximately 1 second to process the Dump Table Registry command when there are 250 RTS tables and that lower priority tasks generate various error events related to not getting an opportunity to run. Adding a platform configuration definition to insert task delays into the process loop will increase the time necessary for CFE_TBL to finish the command but will allow lower priority tasks to run while the command is being processed.
Also, creating some test code that puts performance markers around the file i/o calls within the command processor may identify where the bulk of the command process time is spent. It may be possible to reduce the command execution time by optimizing the command handler code if the bulk of the execution time is not being spent inside the file system.

Imported from trac issue 108.  Created by sstrege on 2015-08-28T16:09:54, last modified: 2019-03-01T15:27:58

Trac comment by glimes on 2016-10-18 15:07:03:
Remove my name from many tickets (where it was applied by default), so others can tell that there are tickets that need some attention.

The file writing should likely be moved to a low priority child task, same for any other potentially "large" file writes: CFE_SB_SendRtgInfo, CFE_SB_SendPipeInfo, CFE_SB_SendMapInfo

These all sound like great candidates for moving into the ES background job service.
Make a generic file writer job template based on the current perf data dump, then apply it for all these file dump commands.

Note - standby on this until #928 is implemented (for SB writes), since they are being refactored.

Removed dependency label, this can be resolved now.

Removed dependency label, this can be resolved now.


Add support for FreeBSD

Add support for FreeBSD. Tested on FreeBSD 12.1

@martijndegouw thanks for the PR! Can you u take a look at the failing spec tests and also add FreeBSD to the metadata.json?

@martijndegouw thanks for the updates. can you take a look at the failing tests?


Rebase up-to-date assemble on largeMonolithicJavaProject (parallel false) performance test on 4.8 RC 1

Context

See: https://github.com/gradle/gradle-private/issues/1285
Contributor Checklist

[ ] Review Contribution Guidelines
[ ] Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
[ ] Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team
[ ] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective
[ ] Provide unit tests (under <subproject>/src/test) to verify logic
[ ] Update User Guide, DSL Reference, and Javadoc for public-facing changes
[ ] Ensure that tests pass locally: ./gradlew <changed-subproject>:check

Gradle Core Team Checklist

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation
[ ] Recognize contributor in release notes

Never rebaseline on an rc/release, always use a nightly. rc/releases are slightly faster, making the test unfair.

No, we fixed the directory name, but there seems to be something else, yet to be identified.


Fix fuse-operands.mlir test after integration

https://github.com/iree-org/iree/pull/11763 disables fuse-operands.mlir to make integration progress forward.

@ftynse thanks for the fixes in https://github.com/iree-org/iree/pull/11750. I cherry-pick the fixes to the integration.
Only [mlir] verify against nullptr payload in transform dialect is not included. All the tests are passing except fuse-operands. Can one of you help fix the issue?

This failure does not look related to [mlir] verify against nullptr payload in transform dialect, the internal pattern implementing the fusion fails to apply. Verification doesn't change patterns.

This is actually due to https://github.com/llvm/llvm-project/commit/bcfd32adc4b658dc45aa8c338d5dd03837e2a0e4 that introduces a canonicalization breaking the precondition for https://github.com/iree-org/iree/blob/a81c3cf3f2f030a60254e66ba6ed711155ef9bf2/llvm-external-projects/iree-dialects/lib/Dialect/LinalgExt/Transforms/Fusion.cpp#L32-L33. IMO, this is yet another example for not running blanket canonicalization all over the place.

#11772 will add a proper error message here.  I don't know what's the intended behavior given that pattern and, therefore, how to reenable the test beyond matching this error.

I have a fix in #11714. Will re-activate the test in with that change.

Thanks for looking into it! I'll include the change in the integrate!


boost_sml: 0.1.0-2 in 'noetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository boost_sml to 0.1.0-2:

upstream repository: https://github.com/PickNikRobotics/boost_sml.git
release repository: https://github.com/PickNikRobotics/boost_sml-release.git
distro file: noetic/distribution.yaml
bloom version: 0.10.0
previous version for package: 0.1.0-1

boost_sml
* [feature] Generate SML diagrams using boost.Graph (#4 <https://github.com/PickNikRobotics/boost_sml/issues/4>)
* [feature] example source to enable catkin to build package that can be depended on (#2 <https://github.com/PickNikRobotics/boost_sml/issues/2>)
* [fix] undefined reference error (#6 <https://github.com/PickNikRobotics/boost_sml/issues/6>)
  * Change static constexpr into const to avoid compiler errors when building in debug mode doesn't inline variables.
* [fix] compilation errors when setting overriding CMAKE_CXX_STANDARD in catkin config. (#5 <https://github.com/PickNikRobotics/boost_sml/issues/5>)
* [maint] move all headers into one directory (#3 <https://github.com/PickNikRobotics/boost_sml/issues/3>)
* Contributors: JafarAbdi, Jere Liukkonen, Mark Moll, Tyler Weaver, picknik-jliukkonen

This just fixes a dependency issue for Noetic.


Pop up small window in non_web desktop or web apps

In web version, the login page works as the small popup window.
In mobile or desktop app, it opens a new whole browser screen. It would be better to open a small popup screen like the web version.

This needs to be addressed on the server side.

Closing the issue as this is a server side thing


Lights as led channels

allow leds to have lights as channels #419
add machine-wide brightness setting #417
fix #416 by using a led with the light as channel and a color correction profile

Coverage increased (+0.02%) to 92.09% when pulling ea2b5a04eb35aa2e5714edda8e3fb4224743014a on lights_as_led_channels into 39ce20d4e45d12acfb94b0f24d95e24f8976b504 on dev.

Coverage increased (+0.02%) to 92.09% when pulling ea2b5a04eb35aa2e5714edda8e3fb4224743014a on lights_as_led_channels into 39ce20d4e45d12acfb94b0f24d95e24f8976b504 on dev.

Coverage increased (+0.02%) to 92.09% when pulling 5dab529bbd7e3e38810be112386d79e5cb9aa8a0 on lights_as_led_channels into 39ce20d4e45d12acfb94b0f24d95e24f8976b504 on dev.


TypeError: res[0] is undefined with Dice So Nice

When I go to use Ethck's Downtime Tracker together with Dice So Nice (latest version running on 0.8.9 and the latest version of D&D5e), it throws this error for each instance, and the activity isn't performed. Disabling DSN fixes the issue. Reporting this both here and there.
Foundry VTT | Error thrown in hooked function lib-wrapper.js line 1 > eval:6:15
TypeError: res[0] is undefined
[Detected 3 packages: downtime-ethck, lib-wrapper, dice-so-nice]
    rollRollable https://assets.forge-vtt.com/bazaar/modules/downtime-ethck/0.6.1/training.js:783
    _call https://assets.forge-vtt.com/bazaar/modules/lib-wrapper/<IP_ADDRESS>/lib-wrapper.js line 1 > eval:4
    callAll https://vindictus.forge-vtt.com/scripts/foundry.js:153
    showMessage https://assets.forge-vtt.com/bazaar/modules/dice-so-nice/4.1.4/main.js:222
    promise callback* https://assets.forge-vtt.com/bazaar/modules/dice-so-nice/4.1.4/main.js:230
    _call https://assets.forge-vtt.com/bazaar/modules/lib-wrapper/<IP_ADDRESS>/lib-wrapper.js line 1 > eval:4
    callAll https://vindictus.forge-vtt.com/scripts/foundry.js:153
    callback https://vindictus.forge-vtt.com/scripts/foundry.js:8777
    documents https://vindictus.forge-vtt.com/scripts/foundry.js:8716
    _handleCreateDocuments https://vindictus.forge-vtt.com/scripts/foundry.js:8716
    _createDocuments https://vindictus.forge-vtt.com/scripts/foundry.js:8612
    create https://vindictus.forge-vtt.com/common/abstract/backend.mjs:96
    createDocuments https://vindictus.forge-vtt.com/common/abstract/document.mjs:332
    create https://vindictus.forge-vtt.com/common/abstract/document.mjs:431
    toMessage https://vindictus.forge-vtt.com/scripts/foundry.js:6128
    rollDC https://assets.forge-vtt.com/bazaar/modules/downtime-ethck/0.6.1/training.js:641
    rollRollable https://assets.forge-vtt.com/bazaar/modules/downtime-ethck/0.6.1/training.js:758
    rollRollable https://assets.forge-vtt.com/bazaar/modules/downtime-ethck/0.6.1/training.js:661
    rollRes https://assets.forge-vtt.com/bazaar/modules/downtime-ethck/0.6.1/training.js:436
    addTrainingTab https://assets.forge-vtt.com/bazaar/modules/downtime-ethck/0.6.1/training.js:435
    jQuery 2
        dispatch
        handle
lib-wrapper.js line 1 > eval:7:15
    _call https://assets.forge-vtt.com/bazaar/modules/lib-wrapper/<IP_ADDRESS>/lib-wrapper.js line 1 > eval:7
    callAll https://vindictus.forge-vtt.com/scripts/foundry.js:153
    showMessage https://assets.forge-vtt.com/bazaar/modules/dice-so-nice/4.1.4/main.js:222
    (Async: promise callback)
    <anonymous> https://assets.forge-vtt.com/bazaar/modules/dice-so-nice/4.1.4/main.js:230
    _call https://assets.forge-vtt.com/bazaar/modules/lib-wrapper/<IP_ADDRESS>/lib-wrapper.js line 1 > eval:4
    callAll https://vindictus.forge-vtt.com/scripts/foundry.js:153
    callback https://vindictus.forge-vtt.com/scripts/foundry.js:8777
    documents https://vindictus.forge-vtt.com/scripts/foundry.js:8716
    _handleCreateDocuments https://vindictus.forge-vtt.com/scripts/foundry.js:8716
    _createDocuments https://vindictus.forge-vtt.com/scripts/foundry.js:8612
    create https://vindictus.forge-vtt.com/common/abstract/backend.mjs:96
    createDocuments https://vindictus.forge-vtt.com/common/abstract/document.mjs:332
    create https://vindictus.forge-vtt.com/common/abstract/document.mjs:431
    toMessage https://vindictus.forge-vtt.com/scripts/foundry.js:6128
    rollDC https://assets.forge-vtt.com/bazaar/modules/downtime-ethck/0.6.1/training.js:641
    rollRollable https://assets.forge-vtt.com/bazaar/modules/downtime-ethck/0.6.1/training.js:758
    rollRollable https://assets.forge-vtt.com/bazaar/modules/downtime-ethck/0.6.1/training.js:661
    rollRes https://assets.forge-vtt.com/bazaar/modules/downtime-ethck/0.6.1/training.js:436
    addTrainingTab https://assets.forge-vtt.com/bazaar/modules/downtime-ethck/0.6.1/training.js:435
    jQuery 2

Thank you for the info! I can guarantee that the issue is on my end, so feel free to close the one on the DsN repo. I will have some cycles to look into this over the weekend and will hopefully fix it. I could have sworn I'd fixed all the bugs though :(

Closed on DsN repo as per request. I wish you luck with this. I am also using Better Rolls, if that helps, though... it doesn't matter if that module is on or not, so I doubt it helps at all.


python: ebpf: _terminate() blocking

I got this dump from a test deployment of a gProfiler 1.19.0, which became stuck.
Thread 16815 (idle): "ThreadPoolExecutor-0_3"
    _try_wait (subprocess.py:1901)
        Arguments:
            self: <Popen at 0x7f92f05ccd60>
            wait_flags: 0
    _wait (subprocess.py:1943)
        Arguments:
            self: <Popen at 0x7f92f05ccd60>
            timeout: None
    wait (subprocess.py:1209)
        Arguments:
            self: <Popen at 0x7f92f05ccd60>
            timeout: None
    _terminate (python_ebpf.py:254)
        Arguments:
            self: <PythonEbpfProfiler at 0x7f92f8b0b010>
        Locals:
            code: None
    _dump (python_ebpf.py:221)
        Arguments:
            self: <PythonEbpfProfiler at 0x7f92f8b0b010>
        Locals:
            process: <Popen at 0x7f92f05ccd60>
    snapshot (python_ebpf.py:227)
        Arguments:
            self: <PythonEbpfProfiler at 0x7f92f8b0b010>
    snapshot (python.py:403)
        Arguments:
            self: <PythonProfiler at 0x7f92f8b0add0>
    run (thread.py:58)
        Arguments:
            self: <_WorkItem at 0x7f92f028aa10>
    _worker (thread.py:83)
        Arguments:
            executor_reference: <weakref.ReferenceType at 0x7f92f8b97fb0>
            work_queue: <_queue.SimpleQueue at 0x7f92f8b1f830>
            initializer: None
            initargs: ()
        Locals:
            work_item: <_WorkItem at 0x7f92f028aa10>

gProfiler tried to stop PyPerf, it sent SIGTERM and PyPerf indeed exited with SIGTERM. However, gProfiler remains blocked in the wait function. Not sure if it's a bug in python stdlib/gprofiler/kernel lol. Why would wait block if PyPerf truly exited?

This is probably it: https://docs.python.org/3/library/subprocess.html#subprocess.Popen.wait

Reopening because I'm not sure it's fixed.


items is not defined - when passing an array of items to

🐛 Bug Report
items is not defined
To Reproduce
Unknown how exactly to reproduce
Expected behavior
<Transition /> recognizes valid items passed to it
Link to repro (highly encouraged)
Unknown how to reproduce
Environment

react-spring v9.0.0-808.17
react v16.12.0

Additional Info
2210 proves not to match perfectly to the actual file on the filesystem. The actual code on at the point of failure is:

Variables at time of failure:

@aleclarson any thoughts on this one? I'd love to include react-spring in our upcoming release. I'm hoping!

I won't be publishing another canary for a few weeks at least. Too busy atm.
You can use patch-package to temporarily fix the useTransition hook with a git patch. Just change the items and children references to props.items and props.children.

PS: You can become my patron to support my work.

@aleclarson I understand. Thanks for all your hard work and for the tip.
The values actually need to be _ref3.items and _ref3.children since props doesn't contain those values. Doing this may be the cause of the issues below though.
When I do make that change I just get piles of these warnings, and I believe infinitely looping items being inserted into the DOM, though I can't inspect because of the infinite loop.
Looking forward to trying the next release whenever it's available.

When I do make that change I just get piles of these warnings, and I believe infinitely looping items being inserted into the DOM, though I can't inspect because of the infinite loop.

What does your <Transition> usage look like?

That gets me  TypeError: transitions.map is not a function
I tried to implement hooks based on the from the example in the docs, but I don't know if maybe the API has changed?
const ListRenderer = props => {
  const initial = {
    opacity: 0,
    transform: 'translate3d(0,2rem,0)',
  };
  const fromProp = {
    opacity: 0,
    transform: 'translate3d(0,2rem,0)',
  };
  const leave = {
    opacity: 0,
    transform: 'translate3d(0,-2rem,0)',
  };
  const enter = {
    opacity: 1,
    transform: 'translate3d(0,0,0)',
  };

  const [items, set] = useState(props.items);
  const transitions = useTransition(items, item => item.key, {
    initial,
    from: fromProp,
    enter,
    leave,
    config: { duration: 5000 },
  });
  return transitions.map(({ item, animatedProps, key }) => (
    <animated.div key={key} style={animatedProps}>
      {item}
    </animated.div>
  ));
};

After inspecting I realized that transitions is now returning a function so I tried return transitions; instead of return transitions.map(...), and there's no error, elements are rendered, but sadly there's no animations, and no delay to indicate that React-Spring thinks it's processing animations. In some older versions items would be delayed from appearing/disappearing in accord with the chosen duration, but in this case the items are appear/disappear as soon as the props are updated.I set a duration of 5000 to make it easier to test, but I'm not sure that I've followed the v9 API correctly since I don't have a reference.

808.17 has the new useTransition API (see #809)
Also, make sure your enter.transform value keeps the rem unit in the middle, since that's what you're doing elsewhere.

Hey @aleclarson thanks for your speedy reply and for pointing me to the API notes!
I simplified my example and implemented the new API. Unfortunately I'm getting identical results, items display, but no delay or animation occurs. The new API is really sleek (nice work!) - so I don't think I've screwed anything up.  Is there anything I'm doing wrong here, or is this a bug?
const ListRenderer = props => {
  const initial = {
    opacity: 0,
  };
  const fromProp = {
    opacity: 0,
  };
  const leave = {
    opacity: 0,
  };
  const enter = {
    opacity: 1,
  };

  const [items, set] = useState(props.items);
  const transition = useTransition(items, {
    initial,
    from: fromProp,
    enter,
    leave,
    config: { duration: 10000 },
  });

  return transition((values, item) => (
    <animated.div style={values}>{item}</animated.div>
  ));
};

Is there anything I'm doing wrong here, or is this a bug?

Hard to say. Can you make a git repo with a lockfile and push it to Github?
This useTransition example works fine with 808.17:
https://codesandbox.io/s/react-spring-issue-927-bjrbv

Hey @aleclarson - between time constraints and proprietary code, I probably can, but not in a timely manner; it would have to be a repro, not the original code.
Is there any reason to think that maybe the issue comes from passing React components as children instead of just arrays of numbers?

Also, I left https://codesandbox.io/s/react-spring-issue-927-bjrbv running, not really intentionally, but I noticed it has broken down in that time.

Further inspection of the hooks attempt shows failure here:

Line 2173 is never reached because transitions is an empty array.
The actual line of failure is 2165 in<EMAIL_ADDRESS>The following line is never reached due to transitions always being an empty array.

Seems that useState returns an empty array for items if you pass it an array of React components. This is my first time trying to use useState for this purpose, so I assume this isn't unusual and that it's the issue here.
It works fine if I pass it simply objects to render a number, like in your example, but fails if I want to render React components as children because of useState. Is there any way to do this? The same general concept worked very nicely in 8.x using the render-props API.

Managed to get it working with hooks. #922 remains a showstopper unfortunately.

To clarify why this issue is not closed, although we got it working with the hook API, we didn't get it working with the class-based version.

This will be fixed in the next version. 👍


No longer throwing when refreshing a token fails

Some auth flows use refresh tokens that do expire so we shouldn't be propagating a exception when refreshing fails and authFlow.authenticate should be trusted to handle it.

+1


Creating URL link for Tag-generator

Overview
Creating URL link for tag generator
Action Items

[ ] Create the function that will enable tag generator to store selected strings in the URL that can then be copied and sent to administrator of Github repository for the projects.

Resources/Instructions
https://github.com/pbeshai/use-query-params#examples

@nrrao is going to fix the API call.


Rebase master onto release branch

to: @jacknagz @ryandeivert
cc: @airbnb/streamalert-maintainers
closes #610
Background
The release-2.0.0 is currently 21 commits behind (3 commits ahead) of master. This rebases master onto the release branch so we're up to date.

Coverage increased (+0.1%) to 95.531% when pulling 6464dc8d07728e128352d30543c75893cf785bfd on release-sync-master into 304ceb2ab347332b23f30208254fb91ee7e133c4 on release-2.0.0.