[Improvement][json] optimize performance of json_extract by reusing json path object

Proposed changes
Issue Number: close #xxx
Reuse json path object for const path in json_extract function
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 47.69 seconds
stream load tsv:          534 seconds loaded<PHONE_NUMBER>9 Bytes, about 133 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          65 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          29.4 seconds inserted 10000000 Rows, about 340K ops/s
storage size:<PHONE_NUMBER>3 Bytes

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 47.46 seconds
stream load tsv:          535 seconds loaded<PHONE_NUMBER>9 Bytes, about 133 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          64 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          32 seconds loaded 861443392 Bytes, about 25 MB/s
insert into select:          29.2 seconds inserted 10000000 Rows, about 342K ops/s
storage size:<PHONE_NUMBER>6 Bytes

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 46.7 seconds
stream load tsv:          535 seconds loaded<PHONE_NUMBER>9 Bytes, about 133 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          64 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          28.8 seconds inserted 10000000 Rows, about 347K ops/s
storage size:<PHONE_NUMBER>2 Bytes

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 46.95 seconds
stream load tsv:          533 seconds loaded<PHONE_NUMBER>9 Bytes, about 133 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          64 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          32 seconds loaded 861443392 Bytes, about 25 MB/s
insert into select:          29.7 seconds inserted 10000000 Rows, about 336K ops/s
storage size:<PHONE_NUMBER>3 Bytes


Finaly hunter was mentioned at CppCon :-)

Look at this talk on youtube.
http://www.youtube.com/watch?v=30r_SsOjg2E&t=49m30s
Ruslan, you have to give your own talk about hunter on the next CppCon. The conan boys already had two full talks. ;-)

https://youtu.be/30r_SsOjg2E?t=49m56s

>20 supported packages

I think one zero is missing here :) I see 267 packages at this moment:

https://docs.hunter.sh/en/latest/packages/all.html

Not all of them are "real" (there are "mocking system" like pkg.coregraphics or components like pkg.opencv-extra which can't be used without main pkg.opencv) but still.

Thanks for posting the link @Knitschi.  (No pressure @ruslo 😏.)  Does anyone know of other suitable conferences?  I think a public high level narrative like this would be an incredible way of introducing an end-to-end view of Hunter to more C++ devs and (especially) organizations.  It would also be a great opportunity to get some Hunter users communicating face-to-face in the same room.  Perhaps this type of networking could open doors to some forms of corporate sponsorship (so @ruslo can pay rent).  The measurable growing user base is likely to make upstream adoption much more likely, which seems to be an important long term goal.  If one or two highly visible projects adopt optional Hunter CMake mods (OpenCV, etc), I think more will follow.

Closing inactive discussion.


Add TransformUp implementations

Current coverage is 55.01% (diff: 19.35%)

Merging #23 into master will decrease coverage by 1.01%

@@             master        #23   diff @@
==========================================
  Files            25         25
  Lines          1153       1176    +23
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            646        647     +1
- Misses          448        470    +22
  Partials         59         59

Powered by Codecov. Last update 39f6a24...688e95d


More examples Please

It would be awesome if the APP SDK OpenCL samples were ported to HIP.
This would provide a lot more guidance than the current handful of samples in the repo.

Hi,
We have some here. Do you have something specific in mind?

Thanks. So, in a nutshell here is how my OpenCL app is currently designed:
(I make heavy use of OpenCL events, and OpenCL images)

chunk of data is read from disk and copied asynchronously to a device buffer using map/unmap functions
once on the card, a cl_event triggers a series of kernels to process the data
the last kernel triggers a map of the data buffer back to the host space
once mapped, data is processed on host

So, I am looking for an example that shows how to do this in HIP:

asynch copy from host to device and device to host
use of HIP events
use of HIP equivalent of OpenCL buffer and image

Did you also check out https://github.com/ROCm-Developer-Tools/HIP-Examples ?

Thanks.  Didn't see anything that matches my requirements. I suppose I could re-implement in CUDA,
then port to HIP ?  :)

But then, what's the point ?

HIP targets existing CUDA-software, so indeed no point. Except when there are CUDA-features that would improve performance, and have no equivalent in OpenCL - see discussion #19

I think the best way to approach this is to simply find CUDA samples, and then convert to HIP.
But, of course, if AMD maintained an up to date repository of samples in HIP that showed which features are supported, that would be nice.


Add drop shadow to separate bar button and body text

A possible way to implement the issue mentioned in #2196

Mind posting a screenshot?
Sent with GitHawk

Aw, sorry to add it, here's how it looks:

And here's another one:

Maybe reducing the shadowRadius to 2.0 which is 3.0 by default and changing the color to darkGray does the trick?

Ya lets give that a spin
Sent with GitHawk


Run gofmt

Periodic go-fmt-ing.

Codecov Report

Merging #1024 into master will increase coverage by 0.05%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1024      +/-   ##
==========================================
+ Coverage    54.8%   54.85%   +0.05%
==========================================
  Files          41       41
  Lines        9856     9856
==========================================
+ Hits         5402     5407       +5
+ Misses       3431     3427       -4
+ Partials     1023     1022       -1

Impacted Files
Coverage Δ

acceptfunc.go
46.66% <ø> (ø)
:arrow_up:

server.go
67.95% <0%> (+0.27%)
:arrow_up:

msg.go
77.5% <0%> (+0.66%)
:arrow_up:

Continue to review full report at Codecov.

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


Implemented OnCustomCommand

This fixes #122.

I must admit I haven't got a chance (or time) to test this in detail. But I assume, since you put the work into it, that you had. That's why I'll just merge, release and hope for no issues ;)

Thanks!

@PeterKottas Cool, yes I did test it. Here is an example of how to call it:
PS > dotnet ServiceName.dll action:custom-command command:200

Cool, I am not using this myself, but happy to have it here in case somebody needs to implement this behavior. Going over a few PRs. Need to fix some issues, once that's done, I'll release. Hopefully in like an hour.

Ok 2.0.11 is out. Could you pls pull it down and just double check if everything works as expected? No rush

Looks good. Thanks for releasing so quickly!


Code?

Hi,
I was wondering where I could find your code. Many thanks!

submitted.

Cool! Thanks!


cmd/gc: assigned but not used checking is not strict enough

The following program, http://play.golang.org/p/92JZyQQ-Gr, fails because an err value is shadowed.
This error cropped up a few times in the standard library (and more times in user code).
@robpike thinks the compiler should catch this.
Discussion: https://groups.google.com/forum/#!topic/golang-nuts/MdDLbvOjb4o

See also related issue #10989.

Note that the spec doesn't require the compiler to do any flow analysis for the "defined but not used" error of function-local variables. See #10989 for a discussion.

Duplicate of #10989.


Fixed access violation issue happening on tensorflow native, due susp…

…ection that we pass managed memory pointer to tensorflow native and that gets messed up some time by GC.

Still doesn't work. Something exception thrown:

@tompetk Please try the v0.20 version.


integration cannot be loaded

Version of the custom_component
0.3.2
2024.12.1 Docker
Configuration
GUI
Describe the bug
custom integration cannot be loaded
Debug log

Setup failed for custom integration 'solarweb': Requirements for solarweb not found: ['fronius-solarweb>=0.3.0'].

Unable to install package fronius-solarweb>=0.3.0: × No solution found when resolving dependencies: ╰─▶ Because fronius-solarweb>=0.3.0 depends on pydantic>=2,<3.0 and pydantic==1.10.19, we can conclude that fronius-solarweb>=0.3.0 cannot be used. And because only the following versions of fronius-solarweb are available: fronius-solarweb<=0.3.0 fronius-solarweb==0.3.1 fronius-solarweb==0.3.2 fronius-solarweb==0.3.3 and you require fronius-solarweb>=0.3.0, we can conclude that your requirements are unsatisfiable.

I can confirm
the same error messages in log
when trying to add integration:

Maybe:
[Changes]
(https://github.com/drc38/Fronius_solarweb/releases/0.3.2)
!! Only install if you are running HA >2025.01 !!


[Add TLS config...] Impossible to restart the container after

I am playing with the TLS enforcing and it always work on the first restart.
After that I have my openldap container exiting:
Add TLS config...
*** /container/run/startup/slapd failed with status 13

The only solution I have found so far was to restore a previous database.
I have set shortname for my cert and I have verified  config.ldif, this has nothing to do with https://github.com/osixia/docker-openldap/issues/74
Docker version 17.03.1-ce, build c6d412e
osixia/docker-openldap 1.1.8

I have also tried to fix with copy-services and it also produce an error :
To see how this files are processed and environment variables values,
run this container with '--loglevel debug'
*** Running /container/run/startup/:ssl-tools...
*** Running /container/run/startup/slapd...
*** An error occurred. Aborting.
*** Shutting down /container/run/startup/slapd (PID 11)...
*** Init system aborted.
*** Killing all processes...

Is there a way to recover my data?
I haven't found the bug, am I the only one to have this?

I have the same issue using osixia/openldap:1.2.4 and a fresh container


ID22 Energy System Impacts

General
Please read to end of this to make sure all changes are adopted.
SP 30-10-24 -no changes needed.
DB 1/Nov/24: Somewhat disagree with SP.  I have reviewed and changes are needed, see subsequent columns.
Other Author Team Actions
Land: Should be merged with Modelling energy demand in built environment and Core Climate Services
DB 1/Nov/24: Disagree with further mergers (Land comments refer to previous versions – suggest ignore).
Experiments
DB 1/Nov/24: Define new experiment group “impact_climserv_core”.  To contain: hist-aer, hist-GHG, hist-nat, Initialised prediction (2025-2036), land-hist, newGeoMIP, esm-hist, historical, Overshoot scenario, High scenario, Low overshoot scenario, Low scenario, Medium scenario, Very low scenario.
DB 1/Nov/24: New “impact_climserv_core_expt” experiment list means removing the following experiments as they have less relevance to I&A studies: 1pctCO2-bgc, 1pctCO2-rad, abrupt-0p5CO2, abrupt-127k, abrupt-2xCO2, amip-p4k, amip-piForcing, esm-flat10-cdr, esm-flat10-zec, SSPX-SLCF, hist-piAer, hist-piSLCF, piClim-aer, piClim-histaer, piClim-histall, piClim-X.
Variables
DB 1/Nov/24: Need to remove cowclip_wind_wave_variables.  These are a legacy of earlier versions of this opportunity (pre-mergers).  Please remove.
Time Slices
DB 5/Nov/24: All experiments listed in “impact_climserv_core_expt” requested to provide data throughout entire simulation.  Historic experiments (hist* and esm-hist) can use hist72 timeslice.  Future scenarios to prioritize data output period to 2100, but extensions beyond this are welcomed where possible (as a lower priority but particularly to 2150 for hydropower applications).

CP 5/Dec/24 I made the requested changes except for the removal of unrequired experiments


quarantine administrator is not listed in the article

quarantine admin is not listed nor is the details on what it allows when granted.

@scottsa-msft - May we know which Microsoft document link you used in reference to this issue?
Please share it with us so we can investigate further. Thank you.

This is the URL that is missing any reference to the new quarantine admin role
https://docs.microsoft.com/en-us/azure/active-directory/users-groups-roles/directory-assign-admin-roles#available-roles
Scott Sanders | Office 365 Service Delivery Manager
scottsa<EMAIL_ADDRESS>'<PHONE_NUMBER> È<PHONE_NUMBER>  7 O365 Support 1-800-936-3100
<EMAIL_ADDRESS>From: Joyce Y<EMAIL_ADDRESS>Sent: Sunday, December 8, 2019 8:51 AM
To: MicrosoftDocs/OfficeDocs-O365ITPro<EMAIL_ADDRESS>Cc: Scott Sanders (OFFICE365<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/OfficeDocs-O365ITPro] quarantine administrator is not listed in the article (#857)
@scottsa-msfthttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fscottsa-msft&data=02|01|Scott.Sanders%40microsoft.com|f0dfb1925d56444f840108d77be5b326|72f988bf86f141af91ab2d7cd011db47|1|0|637114098803730788&sdata=IqxG%2BLfll4Rip7nPzUfRorJMHNdElsNKqFYWQvfYFPs%3D&reserved=0 - May we know which Microsoft document link you used in reference to this issue?
Please share it with us so we can investigate further. Thank you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FOfficeDocs-O365ITPro%2Fissues%2F857%3Femail_source%3Dnotifications%26email_token%3DAKSAOCJYHUW62SRXLNZQKQLQXT3VLA5CNFSM4JW6WLI2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGG7DSI%23issuecomment-562950601&data=02|01|Scott.Sanders%40microsoft.com|f0dfb1925d56444f840108d77be5b326|72f988bf86f141af91ab2d7cd011db47|1|0|637114098803730788&sdata=KYsaLefHI7iX0B3oOdjlZzSvX0jfeI5p%2BQCGy3kS4Go%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAKSAOCL47D5LCSUPGSGZ2ZTQXT3VLANCNFSM4JW6WLIQ&data=02|01|Scott.Sanders%40microsoft.com|f0dfb1925d56444f840108d77be5b326|72f988bf86f141af91ab2d7cd011db47|1|0|637114098803740746&sdata=088UXkzEnj5Is1tAJ%2BlS4IIWicnxhSaaZlKVPsCvpfM%3D&reserved=0.

@scottsa-msft - Thank you for sharing the doc link. This repository is intended for feedback on docs specific to Office 365 ITPro topics and the link you shared is for the Azure repo.  Please submit your feedback and open a new issue by clicking on the Feedback section on the specific Microsoft doc (https://docs.microsoft.com/en-us/azure/active-directory/users-groups-roles/directory-assign-admin-roles#available-roles) which is found at the bottom of the page.


Reference error: Collide not defined

I'm getting the error  "collide not defined".
i'm using grunt to compile my app. i tried to add it to the shim but no luck.
anybody please help.
Thank you

https://github.com/kevincobain2000/ionic-tinder-ui/blob/master/www/index.html#L37


Add support for windows XP

Implemented in 561230020fd04387985e9011401cd0235ce28cc9. Some things may not work, additional testing required.


DNM: this PR is only to test the CI

test this please

One clean test, lets try again.

test this please

test this please

test this please

test this please

This should be all the changes needed to allow for multiple tests to run at once and avoid libvirt collisions.


macOS Sierra: Error loading library

After having updated to macOS Sierra, Radiant Player can't load my library.

+1 same issue

Might be a duplicate of #600 .. Not too sure

Enabling the use of Safari cookies mentioned in #600 fixed the issue for me. The exact comment is https://github.com/radiant-player/radiant-player-mac/issues/600#issuecomment-247295337

Yup, enabling Safari's cookies worked for me too. Thanks!

Please note that while the comment @xrubioj linked to has a working download, there is a v2 of it with more fixes down below at https://github.com/radiant-player/radiant-player-mac/issues/600#issuecomment-247714939

A PR will be submitted today didn't have time the last few days but it will be PR'ed today sorry about the wait.

PR has been submitted once @jacobwgillespie or someone from the Radiant Player Team hops on and merges the changes a new version will be out :)

@mordocai You're right, I saw the big chunk of code in this comment and I missed the download link. ;)

This should be resolved by v1.11.0.

Yay! It's working for me. Set the cookie store back to application internal one and works perfectly. Thanks!


TextEditorEdit does not handle and convert \r and \r\n as the documentation states

VSCode Version: 1.13.1
OS Version: macOS Sierra

Summary of issue:
I am trying to use TextEditorEdit replace to replace random text with text including newlines. The newline characters are literally inserted instead of converting to line breaks.
From the docs it specifically says if I pass in \n or \r\n they will be normalized:
	export interface TextEditorEdit {
		/**
		 * Replace a certain text region with a new value.
		 * You can use \r\n or \n in `value` and they will be normalized to the current [document](#TextDocument).
		 *
		 * @param location The range this operation should remove.
		 * @param value The new text this operation should insert after removing `location`.
		 */
		replace(location: Position | Range | Selection, value: string): void;

Steps to Reproduce:
Using this function, I pass in a valid range and the text is abc\nabc\nabc
    static async replace(range: vscode.Range, text: string): Promise<boolean> {
    return vscode.window.activeTextEditor!.edit(editBuilder => {
      editBuilder.replace(new vscode.Selection(range.end, range.start), text);
    });
  }

I end up with abc\nabc\abc\n in the editor instead of this:
abc
abc
abc

@xconverge Can you share the code with us that computes the value of text?

I can in a bit, what does text have to include other than \n? The string I referenced abc\nabc\nabc is not enough info?

Ideally you have a repo or another form of source that you could share with me

So, the snippet below inserts three lines for me

  let disposable = vscode.commands.registerCommand('extension.sayHello', async () => {

        if (!vscode.window.activeTextEditor) {
            return;
        }

        vscode.window.activeTextEditor.edit(builder => {
            let text = 'abc\nabc\nabc';
            builder.replace(vscode.window.activeTextEditor.selection, text);
        });
    });

@jrieken Thanks for the responses. I am going to close this for now. I have expanded on your example a bit to be closer to my actual source code, and it still works correctly. I think that I am most likely doing something wrong, now that I see that this example works I will close it for now. Sorry for the noise!
 vscode.commands.registerCommand('extension.sayHello', async () => {

    if (!vscode.window.activeTextEditor) {
      return;
    }

    vscode.window.activeTextEditor.edit(builder => {
      const regex = new RegExp(",","g");
      const originalContent = "abc,abc,abc";
      const newContent = originalContent.replace(regex, "\n");
      const range = vscode.window.activeTextEditor!.selection;
      builder.replace(new vscode.Selection(range.end, range.start), newContent);
    });
  });

Yep this was totally my fault, sorry for not doing my due diligence and wasting your time, bummer!
https://github.com/VSCodeVim/Vim/pull/1868/commits/efcd4eaf4f49c39b7bf8ef2d8d891d4586d30879


The aarch64 version test case fails

The aarch64 version test case fails, need to determine whether it is aarch64

Unfortunately, we cannot accept the PR as you did not sign the CLA.


directly call UnityEngine elements?

Is there a way to directly call Unity Engine elements, similar to Tencent PuErTS?
For example
var u = UnityEngine;
var Vector3 = UnityEngine.Vector3;
u.gameObject.transform.position = new Vector3(1,0,0);

etc

cool figured this out! also there is a meta file missing from your unity jint, so i ended up uninstalling that and just using unity nuget to get regular jint
	public void EvalThis(string eval) {
		engine = new Engine();
		engine.Execute(eval);
	}

	public void UpdateEditor(){
		EvalThis(input.text);
	}

seems kind of hacky so do let me know if there is a better way of doing this... but do u know of a way to access the UnityEngine things without having to manually write functions to expose each one


Depth 0

added a test to mm_is_valid_day that checks for depths <= 0, which would break
or seriously confuse a model
fixed a bug where a single day of data passed to a b_Kl or b_Kb model would
cause Stan to fail because the log(discharge) values were being formatted
improperly for Stan.

Travis error is an issue with installing rstan
Error in .shlib_internal(args) :
  C++14 standard requested but CXX14 is not defined
* removing ‘/usr/local/lib/R/site-library/rstan’


ci/ui: test the new elemental ui extension updated to work with rancher 2.9

1.3.1-rc7is ready to test and it should be visible only in Rancher 2.9

The basic test has been updated here https://github.com/rancher/elemental/pull/1482
Green test with rancher 2.9 => https://github.com/rancher/elemental/actions/runs/9851758204

This morning, we pushed operator 1.5.3 to the marketplace https://github.com/rancher/charts/pull/4200
Waiting the sync to be able to use automated tests, I'm doing some manuals tests.
The stack is:

rancher 2.9-head
operator 1.5.3 from the marketplace (branch dev-2.9 of rancher-chart)
elemental ui extension 1.3.1-rc7

All good regarding the installation but regarding the UI extension, we can install older version and that's an issue because they are not compatible with rancher 2.9 => https://github.com/rancher/dashboard/issues/11416

[ ] Create machine registration
[ ] Build ISO using OS version 2.0.4
[ ] Boot 3 nodes and create a cluster:

k3s 1.30.2 ✅
rke2 1.30.2 :✅

[ ] Reset the nodes by deleting the cluster

Blocked by https://github.com/rancher/elemental-ui/issues/202
But all good for rancher 2.9.0-alpha7 validation.


Bug in handling preprocessing directives

I just copy-pasted your code from https://github.com/Norconex/collector-http/issues/41 :+1:

Unfortunately, the preprocessor interprets the  #set in the comment, and raises:

com.norconex.commons.lang.config.ConfigurationException: Cannot load config file as a string: /home/gmuller/Downloads/norconex-collector-http-2.5.0/tests/test1/test.xml
at com.norconex.commons.lang.config.ConfigurationLoader.loadString(ConfigurationLoader.java:234)
at com.norconex.commons.lang.config.ConfigurationLoader.loadXML(ConfigurationLoader.java:181)
at com.norconex.collector.core.CollectorConfigLoader.loadCollectorConfig(CollectorConfigLoader.java:73)
at com.norconex.collector.core.AbstractCollectorLauncher.launch(AbstractCollectorLauncher.java:76)
at com.norconex.collector.http.HttpCollector.main(HttpCollector.java:75)
Caused by: org.apache.velocity.exception.ParseErrorException: Encountered ".." at /home/gmuller/Downloads/norconex-collector-http-2.5.0/tests/test1/test.xml[line 3, column 45]
Was expecting one of:
 ...
 ...
"{" ...
    at org.apache.velocity.runtime.RuntimeInstance.evaluate(RuntimeInstance.java:1301)
    at org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:272)
    at com.norconex.commons.lang.config.ConfigurationLoader.loadString(ConfigurationLoader.java:230)
    ... 4 more

The ticket you reference has an old config and some references in it are no longer valid.   You should start with the sample configurations provided with the version you downloaded.
Please confirm if you run into issues using current configuration samples and documentation.

Hi,
Thanks for the quick answer, I know the config in the referred ticket is quite old, but the "problem" is still here in the last version of the software :)
Indeed, if you add the following comment in any file, it will not run:
<!-- You can define variables with the #set(...) directive to simplify your
     config maintenance (using Apache Velocity syntax) -->

I see... this is a problem in the comment in the ticket you reference only.  I verified all XML examples shipping with the product and on site documentation and that #set() in comment does not exist.  I updated the ticket you referenced to eliminate this.


Support a build that only builds nuget packages

i.e. doesn't do any sort of compilation, just creation of NuGet packages, and then the standard publishing cycle.

This has been completed, and is being used in the build of Cake.Wyam.Recipe.


Changed JSONField in migration file

In Django version 1.9, It has JSON field built-in. So we can use JSON field package from Django.

After upgrade to version 0.4.5, Auditlog used JSONField from Django built-in function.
So no longer need this PR.


chore: remove redundant lemma LinearMap.IsSymmetric.eigenspace_invariant_of_commute

I noticed that #15012 seemed to prove a few results with unnecessarily strong assumptions (mostly, working over ℝ or ℂ when any commutative ring would suffice). I don't have time to generalise it all but I thought I'd highlight this observation with this small PR.

This is amazing, Oliver. Jireh just suggested that I remove that lemma and make this fix using generalized eigenspaces. Thanks!

Also, thanks for the suggestion about the commutative rings. We are finishing up a PR for finite tuples and will fold in the weakened assumptions throughout with that PR.

Great news! Thanks so much @JonBannon 🎉

Thanks! I think we'll just fold these suggestions (and the generalization to CommRing) into #16569, and thereby avoid the merge conflict. I'm closing this for that reason.


Support user action to delete builds in database

Currently, we have auto-deletion in TRSS. For example, a build will be removed if # of Builds to Keep is reached. We need also to support user action to delete builds. In Build Monitoring List, if a user decides to delete a Build URL, we should also ask if he/she wants to delete the data in database. If so, the build data will be removed from database.

This is a good idea, especially since currently it is way to easy and commonplace for the build team to trigger the build pipelines, often with no testing enabled, which is not nearly so interesting for us to keep AND means that we flush out pipelines that launched tests far more quickly than necessary.


add extra material

[ ] I have read freeCodeCamp's contribution guidelines.
[ ] My pull request has a descriptive title (not a vague title like Update index.md)
[ ] My pull request targets the master branch of freeCodeCamp.
[ ] None of my changes are plagiarized from another source without proper attribution.
[ ] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

@wwewsm, sorry for the delay. Unfortunately this is traditional Chinese, and we would like to keep the Guide in Simplified Chinese for the time being.
Please feel free to open another PR in the future!


UAA startup issue

We're having an issue with the uaa.yml ops file. When we deploy bosh-deployment (bb2e14e6fd1e17053fbbaac4fd92435cedc3ccc7) using UAA 71.0 on stemcell 250.21, the UAA starts up, becomes responsive on :8443, but monit never realizes this. It keeps repeatedly trying to hit http://:8443/healthz, but gets a 400, because the endpoint requires TLS. This seems to be due to the uaa.yml ops file setting the UAA's http port to -1, disabling non-tls traffic inbound.
Not sure if this is a uaa issue, a bosh issue, or a stemcell issue. When i try to make monit use https or configure any ssl options for the protocol check, i get syntax issues around https or ssl. If we override the ops file to specify a non-tls port, the release configures the health check on :8080 which is then open, and everything works. I'd rather not have to enable insecure http just to have our UAA start up.
I'm also not sure what caused this to occur, since nothing seems to have changed in the release related to this behavior, or in bosh-deployment. When we first encountered this, we went from UAA 60.2 to UAA 71.0,  trusty 3586.91 stemcell  to xenial 250.21, and bosh-deployment ba03a10581182bbf29efa586040f16064ab92f7d to bb2e14e6fd1e17053fbbaac4fd92435cedc3ccc7.

Downgrading to uaa 64.0 and removing my ops file to re-enable the http-specific port was successful. The health check is still set up for :8443, but somehow works from monit's perspective.
When I curled :8443 using http rather than https, I get this output which somehow isn't a curl failure, despite not having the right protocol, or any http response:
# curl localhost:8443/healthz -vvv -f
*   Trying <IP_ADDRESS>...
* Connected to localhost (<IP_ADDRESS>) port 8443 (#0)
> GET /healthz HTTP/1.1
> Host: localhost:8443
> User-Agent: curl/7.47.0
> Accept: */*
>
* Connection #0 to host localhost left intact
P

@geofffranks there are currently issues with all UAA releases after and including v68. Bosh-deployment will be updated to use the latest when we have heard the issue is fixed. Thanks!


SaveFilePanel crashes the plugin in a Mac App Store build

Sorry to bother you again, Gökhan.
The following code crashes the plugin on a macOS build for the Mac App Store (i.e. built with Mac App Store Validation enabled in Unity, then codesigned and packaged, then installed from the package):
Debug.Log("before StandaloneFileBrowser.SaveFilePanel");
string path = SFB.StandaloneFileBrowser.SaveFilePanel("Export", "", "something", "pdf");
Debug.Log("path: " + path);

The crash results in the following in Unity's Player.log file:
before StandaloneFileBrowser.SaveFilePanel

(Filename: /Users/builduser/buildslave/unity/build/artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51)

2018-11-15 15:22:36.282 Our Application[17987:3915399] init
2018-11-15 15:22:36.390 Our Application[17987:3915399] *** Assertion failure in -[NSVBSavePanel viewWillInvalidate:], /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppKit/AppKit-1671/Nav.subproj/OpenAndSavePanelRemote/NSVBOpenAndSavePanels.m:374
2018-11-15 15:22:36.391 Our Application[17987:3915399] -[NSVBSavePanel init] caught non-fatal NSObjectNotAvailableException 'service com.apple.appkit.xpc.openAndSavePanelService failed to init an instance of NSSavePanelService on behalf of <NSRemoteView: 0x600003308460> due to {
    callStackSymbols = (
	0   CoreFoundation                      0x00007fff4663943d __exceptionPreprocess + 256
	1   libobjc.A.dylib                     0x00007fff72546720 objc_exception_throw + 48
	2   CoreFoundation                      0x00007fff4663926f +[NSException raise:format:] + 201
	3   com.apple.appkit.xpc.openAndSavePanelService 0x000000010258b204 com.apple.appkit.xpc.openAndSavePanelService + 8708
	4   AppKit                              0x00007fff43c5d10b -[NSViewController _loadViewIfRequired] + 75
	5   AppKit                              0x00007fff43c5d076 -[NSViewController view] + 30
	6   ViewBridge                          0x00007fff6f644ac3 -[NSViewServiceMarshal _bootstrap:replyData:] + 2899
	7   ViewBridge                          0x00007fff6f646047 -[NSViewServiceMarshal bootstrap:withReply:] + 167
	8   CoreFoundation                      0x00007fff4658ef8c __invoking___ + 140
	9   CoreFoundation                      0x00007fff4658ee5f -[NSInvocation invoke] + 311
	10  CoreFoundation                      0x00007fff465f053d -[NSInvocation invokeWithTarget:] + 56
	11  ViewBridge                          0x00007fff6f68baaf -[NSVB_ViewServiceImplicitAnimationDecodingProxy forwardInvocation:] + 85
	12  CoreFoundation                      0x00007fff465d880e ___forwarding___ + 780
	13  CoreFoundation                      0x00007fff465d8478 _CF_forwarding_prep_0 + 120
	14  CoreFoundation                      0x00007fff4658ef8c __invoking___ + 140
	15  CoreFoundation                      0x00007fff4658ee5f -[NSInvocation invoke] + 311
	16  CoreFoundation                      0x00007fff465f053d -[NSInvocation invokeWithTarget:] + 56
	17  ViewBridge                          0x00007fff6f653973 -[NSVB_QueueingProxy forwardInvocation:] + 324
	18  CoreFoundation                      0x00007fff465d880e ___forwarding___ + 780
	19  CoreFoundation                      0x00007fff465d8478 _CF_forwarding_prep_0 + 120
	20  CoreFoundation                      0x00007fff4658ef8c __invoking___ + 140
	21  CoreFoundation                      0x00007fff4658ee5f -[NSInvocation invoke] + 311
	22  CoreFoundation                      0x00007fff465f053d -[NSInvocation invokeWithTarget:] + 56
	23  CoreFoundation                      0x00007fff465d880e ___forwarding___ + 780
	24  CoreFoundation                      0x00007fff465d8478 _CF_forwarding_prep_0 + 120
	25  CoreFoundation                      0x00007fff4658ef8c __invoking___ + 140
	26  CoreFoundation                      0x00007fff4658ee5f -[NSInvocation invoke] + 311
	27  ViewBridge                          0x00007fff6f6206cd __deferNSXPCInvocationOntoMainThread_block_invoke + 237
	28  ViewBridge                          0x00007fff6f615af3 __wrapBlockWithVoucher_block_invoke + 37
	29  ViewBridge                          0x00007fff6f6158a4 __deferBlockOntoMainThread_block_invoke_2 + 553
	30  CoreFoundation                      0x00007fff465bcca7 __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 12
	31  CoreFoundation                      0x00007fff4657fced __CFRunLoopDoBlocks + 395
	32  CoreFoundation                      0x00007fff4657fa49 __CFRunLoopRun + 2834
	33  CoreFoundation                      0x00007fff4657ece4 CFRunLoopRunSpecific + 463
	34  HIToolbox                           0x00007fff45818895 RunCurrentEventLoopInMode + 293
	35  HIToolbox                           0x00007fff458185cb ReceiveNextEventCommon + 618
	36  HIToolbox                           0x00007fff45818348 _BlockUntilNextEventMatchingListInModeWithFilter + 64
	37  AppKit                              0x00007fff43ad595b _DPSNextEvent + 997
	38  AppKit                              0x00007fff43ad46fa -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1362
	39  ViewBridge                          0x00007fff6f61e226 -[NSViewServiceApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 92
	40  AppKit                              0x00007fff43ace75d -[NSApplication run] + 699
	41  AppKit                              0x00007fff43abde97 NSApplicationMain + 780
	42  libxpc.dylib                        0x00007fff7384af1f _xpc_objc_main + 612
	43  libxpc.dylib                        0x00007fff7384a9e5 _xpc_copy_xpcservice_dictionary + 0
	44  ViewBridge                          0x00007fff6f60fa76 xpc_connection_handler + 0
	45  ViewBridge                          0x00007fff6f618a03 NSViewServiceApplicationMain + 2877
	46  com.apple.appkit.xpc.openAndSavePanelService 0x00000001025904ea main + 208
	47  libdyld.dylib                       0x00007fff73614085 start + 1
);
    name = NSInternalInconsistencyException;
    reason = "+[NSOpenAndSavePanelService loadViewToService:isOpenPanel:appCentric:] : failed entitlements check";
    userInfo = "<null>";
}' with backtrace (
	0   CoreFoundation                      0x00007fff4663943d __exceptionPreprocess + 256
	1   libobjc.A.dylib                     0x00007fff72546720 objc_exception_throw + 48
	2   ViewBridge                          0x00007fff6f671b00 -[NSRemoteView _advanceToConfigPhaseLegacy] + 1593
	3   ViewBridge                          0x00007fff6f672845 -[NSRemoteView _viewServiceMarshalProxy:withDetailedErrorHandler:] + 217
	4   ViewBridge                          0x00007fff6f672c1a -[NSRemoteView _viewServiceMarshalProxy:withErrorHandler:] + 73
	5   ViewBridge                          0x00007fff6f6613c0 -[NSRemoteView _bridge] + 393
	6   ViewBridge                          0x00007fff6f661211 -[NSRemoteView bridge] + 30
	7   AppKit                              0x00007fff43e2c5fa -[NSVBSavePanel init] + 290
	8   AppKit                              0x00007fff43e2c119 +[NSSavePanel _crunchyRawUnbonedPanel] + 75
	9   StandaloneFileBrowser               0x000000010e3429f8 -[StandaloneFileBrowser createSavePanel:directory:defaultName:filters:] + 167
	10  StandaloneFileBrowser               0x000000010e342848 -[StandaloneFileBrowser dialogSaveFilePanel:directory:defaultName:filters:] + 19
	11  StandaloneFileBrowser               0x000000010e341ed9 DialogSaveFilePanel + 224
	12  ???                                 0x0000000110e56063 0x0 +<PHONE_NUMBER>
)
path:

The crucial part seems to be "service com.apple.appkit.xpc.openAndSavePanelService failed to init an instance of NSSavePanelService".
The error affects only the plugin (the app itself does not crash), which returns an empty path without opening the save file dialog at all. This does not happen on a standalone macOS build from Unity (i.e. not prepared for the store), which is very strange. StandaloneFileBrowser.OpenFilePanel seems to work regardless of SaveFilePanel not working. Could this be a permissions issue that doesn't happen for non-store builds?
It happens on both a recent iMac with Mojave (the error above is from that) and a very old MacBook Pro from 2010 with High Sierra 10.13.6. We are using the current unitypackage from your repository's "Package" folder.
Any ideas? :)
Cheers!
Daniel Lobo

I'm not sure but it's probably because of apple's app sandbox. I think you have to specify file-access permissions in the entitlement key. Documentation is here.

You were spot-on, thank you very much. :)
Turns out that OpenFilePanel was working because we already had the com.apple.security.files.user-selected.read-only persmission, since by following Unity's instructions we copied the entitlements file created by Xcode for a default project.
Adding com.apple.security.files.user-selected.read-write worked perfectly.
For reference, if anyone stumbles upon this thread, the correct entitlements file for us became this:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>com.apple.security.app-sandbox</key>
	<true/>
	<key>com.apple.security.files.user-selected.read-only</key>
	<true/>
	<key>com.apple.security.files.user-selected.read-write</key>
	<true/>
</dict>
</plist>

Thanks again! Your help is much appreciated. ;)
Daniel


open-vm-tools: 10.3.0 -> 10.3.5

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/open-vm-tools/versions.
meta.description for open-vm-tools is: '"Set of tools for VMWare guests to improve host-guest interaction"'.
Release on GitHub
Compare changes on GitHub

Checks done (click to expand)

built on NixOS
/nix/store/awkcx8mcnlni4w6vpr2fz2wa05whkvb4-open-vm-tools-10.3.5/bin/vmware-user passed the binary check.
/nix/store/awkcx8mcnlni4w6vpr2fz2wa05whkvb4-open-vm-tools-10.3.5/bin/vmware-hgfsclient passed the binary check.
Warning: no invocation of /nix/store/awkcx8mcnlni4w6vpr2fz2wa05whkvb4-open-vm-tools-10.3.5/bin/vmware-checkvm had a zero exit code or showed the expected version
/nix/store/awkcx8mcnlni4w6vpr2fz2wa05whkvb4-open-vm-tools-10.3.5/bin/vmware-rpctool passed the binary check.
/nix/store/awkcx8mcnlni4w6vpr2fz2wa05whkvb4-open-vm-tools-10.3.5/bin/vmware-namespace-cmd passed the binary check.
/nix/store/awkcx8mcnlni4w6vpr2fz2wa05whkvb4-open-vm-tools-10.3.5/bin/vmware-guestproxycerttool passed the binary check.
/nix/store/awkcx8mcnlni4w6vpr2fz2wa05whkvb4-open-vm-tools-10.3.5/bin/vmtoolsd passed the binary check.
Warning: no invocation of /nix/store/awkcx8mcnlni4w6vpr2fz2wa05whkvb4-open-vm-tools-10.3.5/bin/vmware-toolbox-cmd had a zero exit code or showed the expected version
/nix/store/awkcx8mcnlni4w6vpr2fz2wa05whkvb4-open-vm-tools-10.3.5/bin/vmware-user-suid-wrapper passed the binary check.
Warning: no invocation of /nix/store/awkcx8mcnlni4w6vpr2fz2wa05whkvb4-open-vm-tools-10.3.5/bin/vmware-vmblock-fuse had a zero exit code or showed the expected version
/nix/store/awkcx8mcnlni4w6vpr2fz2wa05whkvb4-open-vm-tools-10.3.5/bin/vmhgfs-fuse passed the binary check.
/nix/store/awkcx8mcnlni4w6vpr2fz2wa05whkvb4-open-vm-tools-10.3.5/bin/vmware-xferlogs passed the binary check.
Warning: no invocation of /nix/store/awkcx8mcnlni4w6vpr2fz2wa05whkvb4-open-vm-tools-10.3.5/bin/mount.vmhgfs had a zero exit code or showed the expected version
9 of 13 passed binary check by having a zero exit code.
0 of 13 passed binary check by having the new version present in output.
found 10.3.5 with grep in /nix/store/awkcx8mcnlni4w6vpr2fz2wa05whkvb4-open-vm-tools-10.3.5
directory tree listing: https://gist.github.com/a289395fe6645eaafdea197a7e3f110f
du listing: https://gist.github.com/92f6adcac175d5bb8fa879e90ef2bf86

Rebuild report (click to expand)

4 total rebuild path(s)
2 package rebuild(s)
2 x86_64-linux rebuild(s)
2 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
0 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
open-vm-tools
open-vm-tools-headless

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/awkcx8mcnlni4w6vpr2fz2wa05whkvb4-open-vm-tools-10.3.5 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A open-vm-tools https://github.com/r-ryantm/nixpkgs/archive/b747257ca28508f93c6dd7b1546bec32a6f93938.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/awkcx8mcnlni4w6vpr2fz2wa05whkvb4-open-vm-tools-10.3.5
ls -la /nix/store/awkcx8mcnlni4w6vpr2fz2wa05whkvb4-open-vm-tools-10.3.5/bin

cc @joamaki for testing.

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: open-vm-tools
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: open-vm-tools
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: open-vm-tools
Partial log (click to expand)
/nix/store/awkcx8mcnlni4w6vpr2fz2wa05whkvb4-open-vm-tools-10.3.5/etc/vmware-tools/resume-vm-default: interpreter directive changed from "/bin/sh" to "/nix/store/r47p5pzx52m3n34vdgqpk5rvqgm0m24m-bash-4.4-p23/bin/sh"
/nix/store/awkcx8mcnlni4w6vpr2fz2wa05whkvb4-open-vm-tools-10.3.5/etc/vmware-tools/poweroff-vm-default: interpreter directive changed from "/bin/sh" to "/nix/store/r47p5pzx52m3n34vdgqpk5rvqgm0m24m-bash-4.4-p23/bin/sh"
checking for references to /build in /nix/store/awkcx8mcnlni4w6vpr2fz2wa05whkvb4-open-vm-tools-10.3.5...
moving /nix/store/awkcx8mcnlni4w6vpr2fz2wa05whkvb4-open-vm-tools-10.3.5/sbin/* to /nix/store/awkcx8mcnlni4w6vpr2fz2wa05whkvb4-open-vm-tools-10.3.5/bin
shrinking RPATHs of ELF executables and libraries in /nix/store/abwyvb0ahxkrbqxlq5vhr67wjpkalr3k-open-vm-tools-10.3.5-dev
strip is /nix/store/vcc4svb8gy29g4pam2zja6llkbcwsyiq-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/abwyvb0ahxkrbqxlq5vhr67wjpkalr3k-open-vm-tools-10.3.5-dev/lib
patching script interpreter paths in /nix/store/abwyvb0ahxkrbqxlq5vhr67wjpkalr3k-open-vm-tools-10.3.5-dev
checking for references to /build in /nix/store/abwyvb0ahxkrbqxlq5vhr67wjpkalr3k-open-vm-tools-10.3.5-dev...
/nix/store/awkcx8mcnlni4w6vpr2fz2wa05whkvb4-open-vm-tools-10.3.5

Release notes:
https://github.com/vmware/open-vm-tools/blob/stable-10.3.5/ReleaseNotes.md


operator: add support for fine-grained handling of AddonComponents

Another approach, this time with a dynamic list of AddonComponents, read directly from the charts. @ostromart let me know what you think
[x] Installation

I updated the PR. I'm keeping the changes that move the manifests around out of here, for reviewer's sanity. I will follow up with another PR for that

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

Test name
Commit
Details
Rerun command

lint_istio
27a7d1e9f79a044cf1a998ddab912523cb29e361
link
/test lint_istio

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

Looks like directory names and chart names have to match, so I'll add a second commit with the manifests moved around

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

Test name
Commit
Details
Rerun command

lint_istio
27a7d1e9f79a044cf1a998ddab912523cb29e361
link
/test lint_istio

gencheck_istio
7523448edd1d9f034fe1b026fc1cf6b4df718801
link
/test gencheck_istio

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

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

Test name
Commit
Details
Rerun command

release-test_istio
03b8dd864d77c397b98a6e4053a7655f5a64fcff
link
/test release-test_istio

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

The new structure approach LGTM.  A bit concerned on in place upgrade impact for these components, how would that work when names have changed?

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

Test name
Commit
Details
Rerun command

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

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

The new structure approach LGTM. A bit concerned on in place upgrade impact for these components, how would that work when names have changed?

Hey Lin, I think we're good on the upgrade case, because the underlying Kubernetes resources don't change their names, just the helm charts - and as we're not using helm directly, those names aren't exposed to the user afaik. @ostromart do you have more info on this?

/retest

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

Test name
Commit
Details
Rerun command

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

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

/retest

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

Test name
Commit
Details
Rerun command

gencheck_istio
19edeeba9a72739dc6efba9cc52e62cff78a313d
link
/test gencheck_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
19edeeba9a72739dc6efba9cc52e62cff78a313d
link
/test gencheck_istio

unit-tests_istio
19edeeba9a72739dc6efba9cc52e62cff78a313d
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
42f7928c7f0d07a13a097e82937abf259c09bc55
link
/test integ-security-k8s-tests_istio

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

@dgn: PR needs rebase.

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

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
42f7928c7f0d07a13a097e82937abf259c09bc55
link
/test integ-security-k8s-tests_istio

unit-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
42f7928c7f0d07a13a097e82937abf259c09bc55
link
/test integ-security-k8s-tests_istio

unit-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test unit-tests_istio

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

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

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
42f7928c7f0d07a13a097e82937abf259c09bc55
link
/test integ-security-k8s-tests_istio

unit-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test unit-tests_istio

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

integ-telemetry-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-telemetry-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
42f7928c7f0d07a13a097e82937abf259c09bc55
link
/test integ-security-k8s-tests_istio

unit-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test unit-tests_istio

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

integ-telemetry-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-telemetry-k8s-tests_istio

integ-security-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-security-local-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
42f7928c7f0d07a13a097e82937abf259c09bc55
link
/test integ-security-k8s-tests_istio

unit-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test unit-tests_istio

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

integ-telemetry-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-telemetry-k8s-tests_istio

integ-security-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-security-local-tests_istio

integ-galley-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-galley-local-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
42f7928c7f0d07a13a097e82937abf259c09bc55
link
/test integ-security-k8s-tests_istio

unit-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test unit-tests_istio

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

integ-telemetry-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-telemetry-k8s-tests_istio

integ-security-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-security-local-tests_istio

integ-galley-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-galley-local-tests_istio

integ-pilot-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-pilot-local-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
42f7928c7f0d07a13a097e82937abf259c09bc55
link
/test integ-security-k8s-tests_istio

unit-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test unit-tests_istio

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

integ-telemetry-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-telemetry-k8s-tests_istio

integ-security-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-security-local-tests_istio

integ-galley-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-galley-local-tests_istio

integ-pilot-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-pilot-local-tests_istio

integ-conformance-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-conformance-local-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
42f7928c7f0d07a13a097e82937abf259c09bc55
link
/test integ-security-k8s-tests_istio

unit-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test unit-tests_istio

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

integ-telemetry-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-telemetry-k8s-tests_istio

integ-security-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-security-local-tests_istio

integ-galley-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-galley-local-tests_istio

integ-pilot-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-pilot-local-tests_istio

integ-conformance-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-conformance-local-tests_istio

release-test_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test release-test_istio

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

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
42f7928c7f0d07a13a097e82937abf259c09bc55
link
/test integ-security-k8s-tests_istio

unit-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test unit-tests_istio

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

integ-telemetry-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-telemetry-k8s-tests_istio

integ-security-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-security-local-tests_istio

integ-galley-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-galley-local-tests_istio

integ-pilot-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-pilot-local-tests_istio

integ-conformance-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-conformance-local-tests_istio

release-test_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test release-test_istio

pilot-e2e-envoyv2-v1alpha3_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test pilot-e2e-envoyv2-v1alpha3_istio

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

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
42f7928c7f0d07a13a097e82937abf259c09bc55
link
/test integ-security-k8s-tests_istio

unit-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test unit-tests_istio

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

integ-telemetry-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-telemetry-k8s-tests_istio

integ-security-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-security-local-tests_istio

integ-galley-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-galley-local-tests_istio

integ-pilot-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-pilot-local-tests_istio

integ-conformance-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-conformance-local-tests_istio

release-test_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test release-test_istio

pilot-e2e-envoyv2-v1alpha3_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test pilot-e2e-envoyv2-v1alpha3_istio

e2e-mixer-no_auth_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test e2e-mixer-no_auth_istio

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

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
42f7928c7f0d07a13a097e82937abf259c09bc55
link
/test integ-security-k8s-tests_istio

unit-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test unit-tests_istio

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

integ-telemetry-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-telemetry-k8s-tests_istio

integ-security-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-security-local-tests_istio

integ-galley-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-galley-local-tests_istio

integ-pilot-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-pilot-local-tests_istio

integ-conformance-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-conformance-local-tests_istio

release-test_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test release-test_istio

pilot-e2e-envoyv2-v1alpha3_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test pilot-e2e-envoyv2-v1alpha3_istio

e2e-mixer-no_auth_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test e2e-mixer-no_auth_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

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

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
42f7928c7f0d07a13a097e82937abf259c09bc55
link
/test integ-security-k8s-tests_istio

unit-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test unit-tests_istio

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

integ-telemetry-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-telemetry-k8s-tests_istio

integ-security-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-security-local-tests_istio

integ-galley-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-galley-local-tests_istio

integ-pilot-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-pilot-local-tests_istio

integ-conformance-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-conformance-local-tests_istio

release-test_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test release-test_istio

pilot-e2e-envoyv2-v1alpha3_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test pilot-e2e-envoyv2-v1alpha3_istio

e2e-mixer-no_auth_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test e2e-mixer-no_auth_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

gencheck_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test gencheck_istio

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

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

Test name
Commit
Details
Rerun command

unit-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test unit-tests_istio

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

integ-telemetry-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-telemetry-k8s-tests_istio

integ-security-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-security-local-tests_istio

integ-galley-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-galley-local-tests_istio

integ-pilot-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-pilot-local-tests_istio

integ-conformance-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-conformance-local-tests_istio

release-test_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test release-test_istio

pilot-e2e-envoyv2-v1alpha3_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test pilot-e2e-envoyv2-v1alpha3_istio

e2e-mixer-no_auth_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test e2e-mixer-no_auth_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

gencheck_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test gencheck_istio

integ-security-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-security-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

unit-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test unit-tests_istio

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

integ-telemetry-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-telemetry-k8s-tests_istio

integ-security-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-security-local-tests_istio

integ-galley-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-galley-local-tests_istio

integ-pilot-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-pilot-local-tests_istio

integ-conformance-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-conformance-local-tests_istio

release-test_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test release-test_istio

pilot-e2e-envoyv2-v1alpha3_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test pilot-e2e-envoyv2-v1alpha3_istio

e2e-mixer-no_auth_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test e2e-mixer-no_auth_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

gencheck_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test gencheck_istio

integ-security-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-pilot-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

unit-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test unit-tests_istio

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

integ-telemetry-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-telemetry-k8s-tests_istio

integ-security-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-security-local-tests_istio

integ-galley-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-galley-local-tests_istio

integ-pilot-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-pilot-local-tests_istio

integ-conformance-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-conformance-local-tests_istio

release-test_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test release-test_istio

pilot-e2e-envoyv2-v1alpha3_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test pilot-e2e-envoyv2-v1alpha3_istio

e2e-mixer-no_auth_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test e2e-mixer-no_auth_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

gencheck_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test gencheck_istio

integ-security-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-pilot-k8s-tests_istio

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

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

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

Test name
Commit
Details
Rerun command

unit-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test unit-tests_istio

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

integ-telemetry-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-telemetry-k8s-tests_istio

integ-security-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-security-local-tests_istio

integ-galley-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-galley-local-tests_istio

integ-pilot-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-pilot-local-tests_istio

integ-conformance-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-conformance-local-tests_istio

release-test_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test release-test_istio

pilot-e2e-envoyv2-v1alpha3_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test pilot-e2e-envoyv2-v1alpha3_istio

e2e-mixer-no_auth_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test e2e-mixer-no_auth_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

gencheck_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test gencheck_istio

integ-security-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-pilot-k8s-tests_istio

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

integ-conformance-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-conformance-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

unit-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test unit-tests_istio

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

integ-telemetry-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-telemetry-k8s-tests_istio

integ-security-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-security-local-tests_istio

integ-galley-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-galley-local-tests_istio

integ-pilot-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-pilot-local-tests_istio

integ-conformance-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-conformance-local-tests_istio

release-test_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test release-test_istio

pilot-e2e-envoyv2-v1alpha3_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test pilot-e2e-envoyv2-v1alpha3_istio

e2e-mixer-no_auth_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test e2e-mixer-no_auth_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

gencheck_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test gencheck_istio

integ-security-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-pilot-k8s-tests_istio

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

integ-conformance-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-conformance-k8s-tests_istio

integ-istioio-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-istioio-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

unit-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test unit-tests_istio

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

integ-telemetry-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-telemetry-k8s-tests_istio

integ-security-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-security-local-tests_istio

integ-galley-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-galley-local-tests_istio

integ-pilot-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-pilot-local-tests_istio

integ-conformance-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-conformance-local-tests_istio

release-test_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test release-test_istio

pilot-e2e-envoyv2-v1alpha3_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test pilot-e2e-envoyv2-v1alpha3_istio

e2e-mixer-no_auth_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test e2e-mixer-no_auth_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

gencheck_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test gencheck_istio

integ-security-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-pilot-k8s-tests_istio

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

integ-conformance-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-conformance-k8s-tests_istio

integ-istioio-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-istioio-k8s-tests_istio

integ-distroless-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-distroless-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

unit-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test unit-tests_istio

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

integ-telemetry-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-telemetry-k8s-tests_istio

integ-security-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-security-local-tests_istio

integ-galley-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-galley-local-tests_istio

integ-pilot-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-pilot-local-tests_istio

integ-conformance-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-conformance-local-tests_istio

release-test_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test release-test_istio

pilot-e2e-envoyv2-v1alpha3_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test pilot-e2e-envoyv2-v1alpha3_istio

e2e-mixer-no_auth_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test e2e-mixer-no_auth_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

gencheck_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test gencheck_istio

integ-security-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-pilot-k8s-tests_istio

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

integ-conformance-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-conformance-k8s-tests_istio

integ-istioio-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-istioio-k8s-tests_istio

integ-distroless-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-distroless-k8s-tests_istio

e2e-dashboard_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test e2e-dashboard_istio

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

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

Test name
Commit
Details
Rerun command

unit-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test unit-tests_istio

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

integ-telemetry-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-telemetry-k8s-tests_istio

integ-security-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-security-local-tests_istio

integ-galley-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-galley-local-tests_istio

integ-pilot-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-pilot-local-tests_istio

integ-conformance-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-conformance-local-tests_istio

release-test_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test release-test_istio

pilot-e2e-envoyv2-v1alpha3_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test pilot-e2e-envoyv2-v1alpha3_istio

e2e-mixer-no_auth_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test e2e-mixer-no_auth_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

gencheck_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test gencheck_istio

integ-security-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-pilot-k8s-tests_istio

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

integ-conformance-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-conformance-k8s-tests_istio

integ-istioio-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-istioio-k8s-tests_istio

integ-distroless-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-distroless-k8s-tests_istio

e2e-dashboard_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test e2e-dashboard_istio

pilot-multicluster-e2e_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test pilot-multicluster-e2e_istio

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

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

Test name
Commit
Details
Rerun command

unit-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test unit-tests_istio

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

integ-telemetry-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-telemetry-k8s-tests_istio

integ-security-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-security-local-tests_istio

integ-galley-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-galley-local-tests_istio

integ-pilot-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-pilot-local-tests_istio

integ-conformance-local-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-conformance-local-tests_istio

release-test_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test release-test_istio

pilot-e2e-envoyv2-v1alpha3_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test pilot-e2e-envoyv2-v1alpha3_istio

e2e-mixer-no_auth_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test e2e-mixer-no_auth_istio

e2e-bookInfoTests-envoyv2-v1alpha3_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test e2e-bookInfoTests-envoyv2-v1alpha3_istio

gencheck_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test gencheck_istio

integ-security-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-pilot-k8s-tests_istio

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

integ-conformance-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-conformance-k8s-tests_istio

integ-istioio-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-istioio-k8s-tests_istio

integ-distroless-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-distroless-k8s-tests_istio

e2e-dashboard_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test e2e-dashboard_istio

pilot-multicluster-e2e_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test pilot-multicluster-e2e_istio

lint_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test integ-security-k8s-tests_istio

pilot-multicluster-e2e_istio
a6bf5fe53b15ccbcb4a4f7faca5b57d012546036
link
/test pilot-multicluster-e2e_istio

lint_istio
78bc7f21ef33111dd9b9c7827cad47c09ef446b1
link
/test lint_istio

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

@dgn: PR needs rebase.

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

As this is becoming a burden to maintain and very hard to review, I'm splitting it into a bunch of small PRs. I will link them here.


Broken Games by Shangri-la Frontier

Song Name
Broken Games
Artist Name
Shangri-la Frontier
Source
Youtube
Youtube Link
https://www.youtube.com/watch?v=GasIaj6iNOU
Direct File Link
No response
Song ID
1124343
Start Offset [ms]
0
Extra
Created from Auto Nong.
Created for level: 100836920

reject
duplicate request, no worries, the song has already been accepted


[BEAM-4707] Add timestamp field to Nexmark tables and use explicit mode in table name

Follow this checklist to help us incorporate your contribution quickly and easily:

[X] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[X] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.
Post-Commit Tests Status (on master branch)

Lang
SDK
Apex
Dataflow
Flink
Gearpump
Samza
Spark

Go

---
---
---
---
---
---

Java

Python

---

---
---
---
---

Thanks again Lukasz. I did the fixes, PTAL.

LGTM. Merging.

Thanks!


Problem with Inertia forms

There is a problem using Inertia forms inside a modal.
When some field does not pass the validation of the request in the backend (with a Form Request, for example), the modal reloads completely and does not save the content of the fields. The form.errors object is also empty. Using preserveState does not work either.
Steps to reproduce it:

Have a form inside a modal:

<script setup>
    import ModalMomentum from<EMAIL_ADDRESS>    import { useForm } from '@inertiajs/vue3';

    const form = useForm({
        name: null,
    });

    const store = () => {
        form.post(route('test.store'), {
            preserveState: true,
        })
    }
</script>

<template>
    <ModalMomentum>
        <form @submit.prevent="store">
            <input id="name" type="text" v-model="form.name">
            <p v-if="form.errors">
                {{ form.errors.name }}
            </p>
            <button type="submit">Save</button>
        </form>
    </ModalMomentum>
</template>

Have a validation rule:

<?php

use Illuminate\Foundation\Http\FormRequest;

class StoreRequest extends FormRequest
{
    public function authorize()
    {
        return true;
    }

    public function rules()
    {
        return [
            'name' => 'required|string|max:1',
        ];
    }

}

Enter a value that breaks validation (in this case, a string longer than 1 character).

package.json:
    "devDependencies": {
        "vue": "^3.3",
    },
    "dependencies": {
        "@inertiajs/vue3": "^1.0.9",
        "momentum-modal": "^0.2.0",
    }

I'm not sure if this will help you, but I've experienced similar weirdness like this before, and what would end up resolving things is to completely wipe out the node_modules directory and package-lock.json and perform a fresh npm i.
What I do is add a "flush" script in my package.json:
"scripts": {
      "dev": "vite",
      "build": "vite build",
      "flush": "rm -rf node_modules package-lock.json && npm i && npm run dev"
},

And then whenever I want to "reboot" things as mentioned above, I simply run npm run flush for convenience.
The other thing to verify that you are using the correct axios version (should be 1.2.0). I've been down this road a couple of times in projects wondering why the inertia forms aren't submitting/validating correctly, and the above "clean re-install" would resolve it.

Seeing the same issue with the modal completely reloaded (errors flash but barely get a chance to see them before it reloads). Inertia and React here.


Use derived ProxyConfig for tracing tls settings

Follow up to https://github.com/istio/istio/pull/23220
This should be using .ProxyConfig which is Istiod's internal
representation of the proxy config and takes annotation overrides into
account, rather than .Values which may or may not be accurate

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

Test name
Commit
Details
Rerun command

integ-local-tests_istio
5337fd4ce9d56a0a9011ac6f1005868f30d3e147
link
/test integ-local-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-local-tests_istio
5337fd4ce9d56a0a9011ac6f1005868f30d3e147
link
/test integ-local-tests_istio

integ-distroless-k8s-tests_istio
5337fd4ce9d56a0a9011ac6f1005868f30d3e147
link
/test integ-distroless-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-local-tests_istio
5337fd4ce9d56a0a9011ac6f1005868f30d3e147
link
/test integ-local-tests_istio

integ-distroless-k8s-tests_istio
5337fd4ce9d56a0a9011ac6f1005868f30d3e147
link
/test integ-distroless-k8s-tests_istio

integ-multicluster-k8s-tests_istio
5337fd4ce9d56a0a9011ac6f1005868f30d3e147
link
/test integ-multicluster-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-local-tests_istio
5337fd4ce9d56a0a9011ac6f1005868f30d3e147
link
/test integ-local-tests_istio

integ-distroless-k8s-tests_istio
5337fd4ce9d56a0a9011ac6f1005868f30d3e147
link
/test integ-distroless-k8s-tests_istio

integ-multicluster-k8s-tests_istio
5337fd4ce9d56a0a9011ac6f1005868f30d3e147
link
/test integ-multicluster-k8s-tests_istio

integ-mixer-k8s-tests_istio
5337fd4ce9d56a0a9011ac6f1005868f30d3e147
link
/test integ-mixer-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
fe04325ac89699ae87b7ce6e9e08ad7d7dd92989
link
/test integ-multicluster-k8s-tests_istio

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

/retest

In response to a cherrypick label: #23406 failed to apply on top of branch "release-1.6":
error: Failed to merge in the changes.
Using index info to reconstruct a base tree...
M	manifests/charts/istio-control/istio-discovery/files/gen-istio.yaml
M	manifests/charts/istio-control/istio-discovery/files/injection-template.yaml
Falling back to patching base and 3-way merge...
Auto-merging manifests/charts/istio-control/istio-discovery/files/injection-template.yaml
Auto-merging manifests/charts/istio-control/istio-discovery/files/gen-istio.yaml
CONFLICT (content): Merge conflict in manifests/charts/istio-control/istio-discovery/files/gen-istio.yaml
Patch failed at 0001 Use derived ProxyConfig for tracing tls settings


feat: add gRPC 1.58.0, datadog_trace 0.91.0, xdebug 3.3.0alpha2 releases

update gRPC with release 1.58.0
update datadog_trace with release 0.91.0
update xdebug with release 3.3.0alpha2

:tada: This PR is included in version 1.194.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Added functionality for c++

I have done the necessary stuff for it, but I am unable to test it, because the code written in readme and the files here aren't the same, the code over there is camel cased and code in the repo is under snake casing.
I am unable to figure out how to test it, so please test it and lemme know if something's wrong. #5

Ok I will test. But I am not sure what you mean by "code written in readme and the files here aren't the same".

I have fixed the issues, by names aren't same I mean that,
on readme it's written
from testcase_maker.generator import TestcaseGenerator
from testcase_maker.values import ValueGroup, NamedValue, RandomInt, LoopValue, ValueRef

so basically I had to import TestcaseGenerator and ValueGroup, NamedValue, RandomInt, LoopValue, ValueRef from values.
So TestcaseGenerator is over there as it should be but under values we have  ValueGroup, NamedValue, RandomInt, LoopValue, ValueRef  under camel casing which is value_group, named_value, random_int, loop_value and value_ref
I think that was the reason for my inability to test.


www.adminer.org not available

Issue Type

Bug Report / Support Request

Your Environment
Vagrant 1.9.1
VirtualBox 5.0.26r108824
ansible <IP_ADDRESS>

Your OS

macOS (10.11.6)

Summary

When I'm trying to do provision for drupal-vm I'm getting a timeout error for adminer role, because www.adminer.org doesn't work

I noticed you're running Vagrant 1.9.1 and VirtualBox 5.0.26; both of those versions had some known issues with Drupal VM. Can you upgrade both and try provisioning again?

It also looks like the site is a bit slower to respond than normal... I need to file an upstream bug about this; we can increase the timeout so it works more consistently.


fix(fees): moved fees to correct part of quote response

version bumped fiatconnect-types to keep in sync with spec change

@jophish idk, it was optional so maybe providers just didn't see it..?


Events created with "khal new" are one hour off when shown in EGroupware or Android

I'm running into issues with Khal from Git (latest snapshot, f53b9c3), our EGroupware 1.8.005 server, and DST settings.
When creating an event with khal new which happens during DST, the time shown in the EGroupware calendar is always an hour later than what I've entered: e.g. khal new 25.10. 8:00 10:00 results in an EGroupware entry that starts at 9:00 and ends at 11:00.
In contrast, when creating an event which happens post-DST, the time shown in EGroupware is an hour earlier than what I entered: khal new 30.10. 8:00 10:00 results in an EGroupware entry starting at 7:00 and ending at 9:00.
Here is a Gist with a number of iCalendar files that exhibit this behavior:

khal--during-dst.ics and khal--post-dst.ics were created using khal and exhibit the behavior described above.
khal--during-dst--changed-in-eg.ics and khal--post-dst--changed-in-eg.ics refer to the same events as the two previous files, but the times were manually corrected in EGroupware.
eg--during-dst.ics and eg--post-dst.ics are events created from within EGroupware.
khal.conf is my khal configuration. The timezones are set explicitly in order to eliminate tzlocal as the potential error source, otherwise nothing out of the ordinary here.

Interestingly, all times are displayed correctly in khal itself—even after I've manually corrected them in EGroupware. I'm not sure whether this is an issue with khal or with our EGroupware server.
In any case, thanks for a cool program. :)

I'll close this now for lack of activity, if anyone has this bug again, please reopen or file a new one.


Multisig. Create multisig flow. There is broken state with signatory selection

Description
If user add a signatory before choose his account - it will broke the selection
Example:
https://github.com/user-attachments/assets/7ad47f0e-7b5f-4624-afbe-ecbdfb141ba5
Steps to Reproduce

Go to multisig creation flow
Enter on page with Step 2
Add signatory befor entering something in first row
Try to fill all fields

Expected Behavior
User can fill fields in any order
Actual Behavior
Account picker broke the flow, can't fill signatory fields
Environment
https://github.com/novasamatech/nova-spektr/commit/c66c6920ba3846ec1f433b7eab5b1dfe55014a4a

Status verification: ✅


Take .fits input files

Just in case you, like me, have fits files from SITELLE, there should be an alternate way to read in files that are not in .hdf5 formats. After talking to crhea93, he said this can be done in LuciBase.py function read_in_cube(). I will try modifying this so depending on the input, the file can be read in using h5py.File() OR fits.open().

Added a try clause to handle this :D


Was created Hero article card UI componnets

Added 2 new components Hero and article card components

Need to add responses for article card component

Should be a grid with 4 cards on a large screen
And when screen is smaller it should wrap to a new line by component


Add sns blueprint

Added SNS blueprint.
Added SQS blueprint.

Closing in favor of a different branch.


Fix/update to node 20.0.0

:tada: This PR is included in version 1.1.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket: