Added test_packs_pack

Tests almost all actions on packs page, except for:

st2 run packs.install register=all repo_url=https://github.com/StackStorm/st2incubator.git - installing all packs as part of sanity seems too much
st2 run packs.restart_component servicename=st2sensorcontainer - I didn't find the way to reliably test that this action does something
st2 action list --pack=docker, st2 sensor list --pack=docker, st2 trigger list --pack=docker - since they are not parts of packs pack

+1


Dortania is not affiliated with Acidanthera

Dortania is not affiliated with Acidanthera and our guides are not officially related to OpenCore in any way. Our guides are a community effort and are not the same as, and should be used in tandem with, the official OpenCore documentation. Please update your repo to reflect this.

Thanks for the info. You learn something new every day.
I’ll update it when I can (probably today or tomorrow maybe). If you would like it updated sooner, I would be more than happy to merge it in a pull request.


[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew typecheck with your changes locally?
[x] Have you successfully run brew tests with your changes locally?

Fix a typo in pr-upload affecting Internet Archive. Not sure how this typo slipped in. Sigh

Review period will end on 2021-02-25 at 23:08:51 UTC.

Review period skipped due to critical label.

CI / test everything (macOS) (pull_request)
  brew audit --skip-style
audit for lg-onscreen-control: failed
 - cannot use the sha256 for an empty string: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
 - Cask should have a description. Please add a `desc` stanza.

https://github.com/Homebrew/brew/pull/10697/checks?check_run_id=1974574815#step:12:8
😕

https://github.com/Homebrew/homebrew-cask-drivers/pull/2056


adding aqara button support

first attempt at a hubitat Device Driver.

updated the code to support release, single, double, triple and quadruple presses.

I like how this button works now.  There is only one event for a push & release.  I simulate the release in two ways.  Momentary mode runs a function in a setable number of seconds, and then sets button 0 for release.  Toggle will switch between button 0 and button 1 being pressed simulating On/Off.

Looks good to me! The use of button 0 is interesting, though I will have to do some testing with my "original" Xioami button driver to see if button 0 can be used by Hubitat's apps (Rule Machine, Button Controller, etc.) Otherwise it will be useful for people using WebCoRE ported to Hubitat (when it's fully ready.)
I'm merging it, and can announce it after (probably tomorrow - I'm heading out now).
Thanks for putting it together.

I was able to use button 0 with rule machine

That's good news


clicking on the repo  on the front page takes one to the external site

I guess whether this is a bug, improvement, or WONTFIX depends on whether one thinks of sourcebot as merely a "fancy bookmarking" system, and the end user really wants to navigate to the code hosting site, or whether one thinks of sourcebot as "references as a service" and thus clicks should mostly navigate to other sourcebot URLs unless otherwise designated

Navigate to https://demo.sourcebot.dev/
Observe the commaai/openpilot in the (ahem) horizontal scroll list
Click on it, expecting to be taken to https://demo.sourcebot.dev/search?query=repo%3Acommaai%2Fopenpilot
😢  Instead observe that one is taken to https://github.com/commaai/openpilot

I'm in the "sourcebot should aim to be a fully self sufficient tool aiming to reference to itself as much as possible" camp.
With this, I feel that when clicking on the repo carousel, this should take the user to the as of yet not implemented file browser for a repo.
For now it is fine.

Agreed with @KonradStanski - once we have a file explorer, we can link to it from other points in the app. #94


Fixed cddl spec for tx-submission protocol

We should use tx rather than txId in the cddl.  It only works
because we use int for both.

@bolt12 I changed this PR considerably, so please review it again.
We should use this idea in other mini-protocols / specs as well.  The only question is if we should modify data structure in ouroboros-network-protocols:test or provide different data structures just for ouroboros-network-protocols:cddl?

I created the issue: input-output-hk/ouroboros-network#4595


NullTypeGradError: tensor.grad encountered a NaN. This variable is Null because the grad method for input 0 (Reshape{2}.0) of the UndefinedGrad op is mathematically undefined.

Same problem. Fixed after I downgrade Theano from 1.0 to 0.9.0


DialogContextError in botbuilder-dialogs

Github issues should be used for bugs and feature requests. Use Stack Overflow for general "how-to" questions.
Versions
package version of the SDK: ^4.7.0
node.js version: v12.13.1
browser version: Chrome 87
os: Windows 10
bot written in Typescript 3.9.7
Describe the bug
The user is stuck in a weird dialog state and cannot interact with the bot anymore, receiving only the "Sorry, it looks like something went wrong." error message. The implemented interruption logic (CancelDialog) is not working either. User's last successful conversation with the bot ended the current dialog, so the user is not stuck in a previous conversation.
Here are some useful stack traces from the logs:

And the actual stringified error here:

Analyzing the stack trace, here's the error that's being thrown in the /botbuilder-dialogs/lib/dialogContext.js:
throw new dialogContextError_1.DialogContextError(DialogContext.continueDialog(): Can't continue dialog. A dialog with an id of '${instance.id}' wasn't found., this);
Here is the code for the dialogBot.ts where the error is being thrown (in turn method) and mainDialog.ts where a dialog is started based on the detected skill of the bot.
https://github.com/StefaniaMan314/botbuilder
To Reproduce
Every time the user tries to start a new conversation with the bot a DialogContextError is being thrown and the dialog cannot be started.
Expected behavior
The dialog to start is found in the dialog context or in its parent dialog context.
Screenshots
Here's a screenshot of the user's conversations and the bot's responses:

Additional context
The odd thing is that this is happening only for a few users (3) across the org (from a total of ~5000 users). This is an unprecedented issue.
Here are several ways we tried to solve this, but none of them worked:

Clearing state DB entries for this user
Uninstalling and installing back the bot in Teams
Clearing Teams cache on the user's machine

Any help is greatly appreciated. Thank you!

@StefaniaMan314 Can you please include the code for the dialogs in question? Can you also please include the code where you instantiate the dialogs and add them to the dialog stacks?
You may also want to attempt updating your version of the SDK, especially if you're set up with a development environment. We follow semver, so there shouldn't be any breaking changes.

@StefaniaMan314 Can you please include the code for the dialogs in question? Can you also please include the code where you instantiate the dialogs and add them to the dialog stacks?
You may also want to attempt updating your version of the SDK, especially if you're set up with a development environment. We follow semver, so there shouldn't be any breaking changes.

@mdrichardson I added two files in the description of the bug. Thanks!

@mdrichardson I added two files in the description of the bug. Thanks!

@StefaniaMan314 Based on the error message and stack trace, I believe the issue is related to this line. Can you verify that all of the dialogs that can possibly be called by that line are added here and that they all have unique ids?
If so, please send the log output around those stack traces; it looks like you have decent logging set up that may help track this down. Also, if you can include the code for the compiled MainDialog.js, we can verify which line it's breaking on.

@StefaniaMan314 Based on the error message and stack trace, I believe the issue is related to this line. Can you verify that all of the dialogs that can possibly be called by that line are added here and that they all have unique ids?
If so, please send the log output around those stack traces; it looks like you have decent logging set up that may help track this down. Also, if you can include the code for the compiled MainDialog.js, we can verify which line it's breaking on.

@mdrichardson Hi, I checked the exact line you mentioned to see if the dialogs are added correctly (they are) and they do have unique ids as you can see here:

The thing is that the flow does not reach that line for the user. The DialogContext error is thrown here https://github.com/StefaniaMan314/botbuilder/blob/7bb952398e8cad0b56a9413e519668f37c6163c3/dialogBot.ts#L117 inside dialogBot.ts, before the execution reaches onEvent in mainDialog.ts.
Here are some logs from user's last interaction with the bot: https://github.com/StefaniaMan314/botbuilder/blob/main/botErrorLog.txt
And here is the compiled MainDialog.js file: https://github.com/StefaniaMan314/botbuilder/blob/main/mainDialog.js
Let me know your thoughts, thanks!

@mdrichardson Hi, I checked the exact line you mentioned to see if the dialogs are added correctly (they are) and they do have unique ids as you can see here:

The thing is that the flow does not reach that line for the user. The DialogContext error is thrown here https://github.com/StefaniaMan314/botbuilder/blob/7bb952398e8cad0b56a9413e519668f37c6163c3/dialogBot.ts#L117 inside dialogBot.ts, before the execution reaches onEvent in mainDialog.ts.
Here are some logs from user's last interaction with the bot: https://github.com/StefaniaMan314/botbuilder/blob/main/botErrorLog.txt
And here is the compiled MainDialog.js file: https://github.com/StefaniaMan314/botbuilder/blob/main/mainDialog.js
Let me know your thoughts, thanks!

@StefaniaMan314 I'm still digging through this, but are you sure the error is thrown on that line and in dialogBot? I'm not seeing that in any of your stack traces.

@StefaniaMan314 I'm still digging through this, but are you sure the error is thrown on that line and in dialogBot? I'm not seeing that in any of your stack traces.

@mdrichardson Oh, my bad! I got the wrong line. The error's thrown at this line https://github.com/StefaniaMan314/botbuilder/blob/7bb952398e8cad0b56a9413e519668f37c6163c3/dialogBot.ts#L144 and you can see this in the logs as well: https://github.com/StefaniaMan314/botbuilder/blob/a35baabc4ecbb6b44801362644950240943caf9f/botErrorLog.txt#L199. Sorry for the confusion!

@mdrichardson Oh, my bad! I got the wrong line. The error's thrown at this line https://github.com/StefaniaMan314/botbuilder/blob/7bb952398e8cad0b56a9413e519668f37c6163c3/dialogBot.ts#L144 and you can see this in the logs as well: https://github.com/StefaniaMan314/botbuilder/blob/a35baabc4ecbb6b44801362644950240943caf9f/botErrorLog.txt#L199. Sorry for the confusion!

I think the issue is that you're calling dc.continueDialog() inside the dialog that you'd like to continue. Generally, the dc you label here is labeled innerDc. This is because it uses MainDialog's inner dialog context. As you can see in the error log line, MainDialog doesn't have any dialogs in its dialogStack.
It's a little difficult to pinpoint, for sure, what's going on because I don't have all the code to debug and your dialog routing is a little unconventional.
As for fixed, I'd recommend:

Implementing a dialogStack check, similar to what you have here or just ending the MainDialog. If there's others on the stack, they should continue.
Update to the latest SDK release and refactor your code to handle dialogs to be more in line with how Core Bot does it.
Use botframework-solutions as little as possible. It's really more of a separate package and can be difficult to implement with Botbuilder docs and Samples.

I also notice that in dialogBot, you only save conversationState once, when a proactive message is sent. It should really be saved after every turn to ensure a user maintains the correct position in your dialog flow.

I think the issue is that you're calling dc.continueDialog() inside the dialog that you'd like to continue. Generally, the dc you label here is labeled innerDc. This is because it uses MainDialog's inner dialog context. As you can see in the error log line, MainDialog doesn't have any dialogs in its dialogStack.
It's a little difficult to pinpoint, for sure, what's going on because I don't have all the code to debug and your dialog routing is a little unconventional.
As for fixed, I'd recommend:

Implementing a dialogStack check, similar to what you have here or just ending the MainDialog. If there's others on the stack, they should continue.
Update to the latest SDK release and refactor your code to handle dialogs to be more in line with how Core Bot does it.
Use botframework-solutions as little as possible. It's really more of a separate package and can be difficult to implement with Botbuilder docs and Samples.

I also notice that in dialogBot, you only save conversationState once, when a proactive message is sent. It should really be saved after every turn to ensure a user maintains the correct position in your dialog flow.

I'll go ahead and implement the dialogStack check you mentioned, sounds like a really good idea. Concerning the SDK version, we're using ^4.7.0, which means it takes the latest version, right?
Thanks for looking into this and for your suggestions!

I'll go ahead and implement the dialogStack check you mentioned, sounds like a really good idea. Concerning the SDK version, we're using ^4.7.0, which means it takes the latest version, right?
Thanks for looking into this and for your suggestions!

Concerning the SDK version, we're using ^4.7.0, which means it takes the latest version, right?

Yes. We follow semver, so there shouldn't be breaking changes between minor version changes (4.7 -> 4.11); breaking changes should only occur for major version changes (3.x -> 4.x).
Let me know how it goes with the dialogStack check. If you're able to share your full code, I may be able to help you debug, too.

Concerning the SDK version, we're using ^4.7.0, which means it takes the latest version, right?

Yes. We follow semver, so there shouldn't be breaking changes between minor version changes (4.7 -> 4.11); breaking changes should only occur for major version changes (3.x -> 4.x).
Let me know how it goes with the dialogStack check. If you're able to share your full code, I may be able to help you debug, too.

Hi @mdrichardson, I looked into how I could implement the dialogStack check and I'm kind of confused. You mentioned that the issue might be calling dc.continueDialog(), but this in inside onEvent  function, which gets called only if the user performs an action on the displayed AC. Since no AC is displayed and the user only gets the "Sorry, it looks like something went wrong." message, the code never reaches this step. So it won't help checking the dialogStack here. Instead, I added a couple of checks in the route() and in the onInterruptDialog() methods. However, I'm not sure if this is going to help either. Let me know if you have any other suggestions where we can add those checks.
The only time we're directly checking for the dialogStack inside the activeDialog is in dialogBot.ts, inside sendProactiveTimeoutMessage method, which assures that the conversation is ended if the user is inactive, so he doesn't get stuck in a dialog. Should we implement something more like this? If so, where should we add this check?
As for the full code, I'm not able to share it here since the company does not allow it. dialogBot.ts and mainDialog.ts are most probably the files where the error happens, so I'm hoping they'll be enough to track it down. Thanks!

Hi @mdrichardson, I looked into how I could implement the dialogStack check and I'm kind of confused. You mentioned that the issue might be calling dc.continueDialog(), but this in inside onEvent  function, which gets called only if the user performs an action on the displayed AC. Since no AC is displayed and the user only gets the "Sorry, it looks like something went wrong." message, the code never reaches this step. So it won't help checking the dialogStack here. Instead, I added a couple of checks in the route() and in the onInterruptDialog() methods. However, I'm not sure if this is going to help either. Let me know if you have any other suggestions where we can add those checks.
The only time we're directly checking for the dialogStack inside the activeDialog is in dialogBot.ts, inside sendProactiveTimeoutMessage method, which assures that the conversation is ended if the user is inactive, so he doesn't get stuck in a dialog. Should we implement something more like this? If so, where should we add this check?
As for the full code, I'm not able to share it here since the company does not allow it. dialogBot.ts and mainDialog.ts are most probably the files where the error happens, so I'm hoping they'll be enough to track it down. Thanks!

According to your stack trace, there's definitely errors occurring in the onEvent block:

Without being able to debug your full code and reproduce the results, I'm afraid that there isn't much more help that I can provide. I'd recommend adding a significant amount of additional logging so that you can see the entire flow that that the user takes, if you can't reproduce it locally and follow it around with breakpoints, step in, step over, etc. I can say that this is not an issue that I've seen before, so it's very unlikely a bug in the SDK.
What exactly is going on in the onEvent code? I see that you're checking for a tokenResponse event. Are you doing SSO with a skill? Maybe you can describe the flow of the user's interaction and that might help me pinpoint some issues?

According to your stack trace, there's definitely errors occurring in the onEvent block:

Without being able to debug your full code and reproduce the results, I'm afraid that there isn't much more help that I can provide. I'd recommend adding a significant amount of additional logging so that you can see the entire flow that that the user takes, if you can't reproduce it locally and follow it around with breakpoints, step in, step over, etc. I can say that this is not an issue that I've seen before, so it's very unlikely a bug in the SDK.
What exactly is going on in the onEvent code? I see that you're checking for a tokenResponse event. Are you doing SSO with a skill? Maybe you can describe the flow of the user's interaction and that might help me pinpoint some issues?

onEvent is triggered when the user performs an action submitted from an AC (for example clicking a button). The main thing that's happening here is that dc.continueDialog() is being called, and if the status of the dialog turn result is complete, it calls the complete() method that clears the skill status.
You can ignore the TokenResponseEventName check, as I debugged the code and it never passes this condition . It must be a reminiscent code from an older version of the project.
I will add more logs across the project to identify bot state elements such as the conversationId that could help me track the user's interaction in our state database and understand what's happening. Thanks!

onEvent is triggered when the user performs an action submitted from an AC (for example clicking a button). The main thing that's happening here is that dc.continueDialog() is being called, and if the status of the dialog turn result is complete, it calls the complete() method that clears the skill status.
You can ignore the TokenResponseEventName check, as I debugged the code and it never passes this condition . It must be a reminiscent code from an older version of the project.
I will add more logs across the project to identify bot state elements such as the conversationId that could help me track the user's interaction in our state database and understand what's happening. Thanks!

Hey @mdrichardson, we're recently facing this issue for more users. We found this article about resetting the conversation. Do you think implementing something like this will solve our problem?

Hey @mdrichardson, we're recently facing this issue for more users. We found this article about resetting the conversation. Do you think implementing something like this will solve our problem?

That might alleviate the current symptom, but given that more users are experiencing this, there's an issue with the code that will likely continue.

That might alleviate the current symptom, but given that more users are experiencing this, there's an issue with the code that will likely continue.

We found a way to clear the conversationId in our botstate db. The issue was solved for the users, we can close this, thanks!

I encountered an error while attempting to fetch the 'intro-dialog' from my JSON configuration file. To address this issue, I am planning to submit a detailed problem report on Git, seeking assistance in resolving the problem.
below my config.json:

error:


⚠NOTE⚠ Removal of -openssl3 postfix and update to MUSL v1.2.5

Hello all,
I'm going to remove the -openssl3 tag on the next update.
Mainly because I only build openssl3 images for a while now, and the postfix doesn't add any extra use.
Also MUSL will be updated to v1.2.5.
And an extra library is added on request, libxml2.
Cheers!

Closing as this is done long time ago.


Q about unit fixed effect

Hi, Kyunghoon, THANKS for your great work. I have a Q on unit FE: in rdid, not need unit FE?

Hello Wenli,
Thanks for your interest and for reaching out to me.
If you're asking about the need to include unit dummy variables for the typical DID specification, then no, you don't need to manually include unit fixed effects (dummy variables) as long as the treatment dummy and post-treatment dummy are correctly specified for rdid.
However, if you're asking about controlling for time-invariant unobserved heterogeneity, typically addressed by adding "fixed effects," we don't have an automated option for that yet.

Thanks for your reply. In your simdata, treatment variable = post* unit？ I try to get a TWFE DID result， how to do？
---- Replied Message ----
@.>Date10/12/2024 09:34 @.> @.>,
@.>SubjectRe: [KyunghoonBan/rdid] Q about unit fixed effect (Issue #1)
Hello Wenli,
Thanks for your interest and for reaching out to me.
If you're asking about the need to include unit dummy variables for the typical DID specification, then no, you don't need to manually include unit fixed effects (dummy variables) as long as the treatment dummy and post-treatment dummy are correctly specified for rdid.
However, if you're asking about controlling for time-invariant unobserved heterogeneity, typically addressed by adding "fixed effects," we don't have an automated option for that yet.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Hello Wenli,
First of all, the naïve $2\times 2$ DID results can be obtained by running the following regression:
$Y_{it} = \alpha_0 + \beta D_{i} + \gamma \mathrm{pos}_{t} + \delta D_{i}  \mathrm{pos}_{t} + \varepsilon_{it},$
where $\widehat{\delta}$ is the ATT estimate. Note that the variable $D_{i}  \mathrm{pos}_{t}$ is equal to 1 if the observation is both in the post-treatment periods and in the treated group, which is occasionally referred to as the "treatment variable."
To get the TWFE DID result, which is slightly more efficient as we exploit the panel structure, you need to run the following regression:
$Y_{it} = \alpha_1 + \delta  D_{i}  \mathrm{pos}_{t} + \mu_t + \lambda_i + e_{it},$
where $\widehat{\delta}$ is the ATT estimate, and $\mu_t$ and $\lambda_i$ are the time and unit dummy variables (or the "fixed-effects"), respectively.
Please feel free to estimate each model by running the following code in Stata:
use sim_rdid, clear

gen pos_D = pos*D
reg Y D pos pos_D

gen ind = mod(_n - 1, 100) + 1
gen t_100 = t + 100
reg Y pos*D i.ind i.t_100

Note that the dataset sim_rdid.dta currently does not include the individual index, so we need to create ind manually for the TWFE exercise.
Also, note that the estimate $\widehat{\delta}=15.77938$ is included in the estimated RDID bounds, $[9.5525, 19.0281]$.


LEGO: Pull request from lego/hb_04604851-bac4-4681-9f74-73de611d6e48_20211121043418978 to main

LEGO: Pull request from lego/hb_04604851-bac4-4681-9f74-73de611d6e48_20211121043418978 to main with localized lcls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.003%) to 41.596%

Files with Coverage Reduction
New Missed Lines
%

extensions/notebook/src/book/bookTrustManager.ts
2
96.43%

Totals

Change from base Build<PHONE_NUMBER>:
-0.003%

Covered Lines:
27080

Relevant Lines:
59040

💛  - Coveralls


tooling: Update envoy.docs.sphinx_runner

Quieten docs build
Run sphinx multi core

Signed-off-by: Ryan Northey<EMAIL_ADDRESS>Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

/docs

i will need to land this one as the website needs to be updated at the same time - https://github.com/envoyproxy/envoy-website/pull/257

/lgtm deps


[QUESTION] Is it possible to get caller when entering a method?

I'm currently trying to get the text displayed in an app.
So I hooked TextGenerator.PopulateWithErrors. In this way I can get the text I want but....
When a sentence is "abcdefg", I got 7 separate method onEnter callback:
a
ab
abc
abcd
abcde
abcdef
abcdefg

The displayed characters are increased one at each time.
So I'm wondering how to get the original string "abcdefg" at once.
I think get the caller of TextGenerator.PopulateWithErrors may help.
By the way, I'm wondering how to monitor nested calls in a method. So I can know where these text really from?

Unfortunately, you can't obtain the caller Il2CppMethod. This information is stripped in release builds.
However, there are two solutions.
The first one consists in tracing the classes/methods you suspect are calling TextGenerator.PopulateWithErrors (use the full or detailed tracing). You will be able to see nested method calls.
The second one consists in using a disassembler (I use ghidra). You must analyze the il2cpp library with it first, then you dump the application, and finally you have to load the method names. After that, you can inspect the "call tree" the disassembler populates for you; otherwise you can get a backtrace:
Interceptor.attach(TextGenerator.methods.PopulateWithErrors.virtualAddress, {
    onEnter() {
        const backtrace = Thread.backtrace(this.context, Backtracer.ACCURATE).map(DebugSymbol.fromAddress).join("\n");
        console.log(backtrace + "\n");
    }
});


Minimize unsafe usage and rework line wrapping

Builds on #27 to minimize unsafe usage (see discussion in #29 for more context).
This has only a minor performance cost, and on certain sizes, a small boost:
 name                    master.bcmp ns/iter    branch.bcmp ns/iter     diff ns/iter  diff %
 encode_100b             94 (1063 MB/s)          87 (1149 MB/s)                    -7  -7.45%
 encode_100b_reuse_buf   72 (1388 MB/s)          67 (1492 MB/s)                    -5  -6.94%
 encode_10mib            8,894,048 (1178 MB/s)   9,030,736 (1161 MB/s)        136,688   1.54%
 encode_10mib_reuse_buf  5,685,071 (1844 MB/s)   5,991,851 (1750 MB/s)        306,780   5.40%
 encode_30mib            27,063,216 (1162 MB/s)  27,540,693 (1142 MB/s)       477,477   1.76%
 encode_30mib_reuse_buf  17,055,237 (1844 MB/s)  18,557,631 (1695 MB/s)     1,502,394   8.81%
 encode_3b               34 (88 MB/s)            38 (78 MB/s)                       4  11.76%
 encode_3b_reuse_buf     14 (214 MB/s)           17 (176 MB/s)                      3  21.43%
 encode_3kib             1,711 (1795 MB/s)       1,634 (1880 MB/s)                -77  -4.50%
 encode_3kib_reuse_buf   1,691 (1816 MB/s)       1,611 (1906 MB/s)                -80  -4.73%
 encode_3mib             2,436,637 (1291 MB/s)   2,518,086 (1249 MB/s)         81,449   3.34%
 encode_3mib_reuse_buf   1,692,495 (1858 MB/s)   1,704,400 (1845 MB/s)         11,905   0.70%
 encode_500b             313 (1597 MB/s)         294 (1700 MB/s)                  -19  -6.07%
 encode_500b_reuse_buf   292 (1712 MB/s)         274 (1824 MB/s)                  -18  -6.16%
 encode_50b              62 (806 MB/s)           61 (819 MB/s)                     -1  -1.61%
 encode_50b_reuse_buf    42 (1190 MB/s)          41 (1219 MB/s)                    -1  -2.38%

Also, mime (which line wraps) is now only somewhat slower instead of much slower:
test encode_3kib_reuse_buf      ... bench:       1,612 ns/iter (+/- 12) = 1905 MB/s
test encode_3kib_reuse_buf_mime ... bench:       2,017 ns/iter (+/- 4) = 1523 MB/s
test encode_500b_reuse_buf      ... bench:         278 ns/iter (+/- 1) = 1798 MB/s
test encode_500b_reuse_buf_mime ... bench:         378 ns/iter (+/- 2) = 1322 MB/s

@alicemaz I think this is good to go; would you like more time to review or should I merge?

looks good to me


Saving problems.

I want to save my document, and nothing happens. Atom says, it's already saved (the little blue circle doesn't shown.) But if i check my file in cli with vim, i see the file wasn't saved.

Can you reproduce this in safe mode (atom --safe)? What OS are you running?

thanks, trying. Running on mac os x Yosemite

Did you manage to reproduce this in safe mode?

Gonna close this out - feel free to comment / reopen if you can reproduce this in safe mode with the latest version of Atom.


Add prerender-macro Bun plugin

I think this is awesome!

Thanks @tomByrer, in Brisa's framework you can try it with a JSX property: https://brisa.build/api-reference/extended-props/renderOn#renderonbuild-or-runtime


Update dependencies

Java gRPC and Maven plugin
Node test dependencies

Also:

Remove unused import in test code.
Remove a redundant vulnerability scan suppression.

@denyeart Since Andy is out this week, please could you give this one your blessing?


Broadcast an Event on every step

At the moment we don't know when a migration starts/finishes and the access to the database is not locked by mongock, so an insertion at application startup can produce errors for not yet initialised collections (e.g. multi-document transaction exception)
Is there an event publisher or is planned to be?
Eg.
| MongockStartingEvent
|_ MongockStartedEvent
|   |_ MongockChahgeLogStartingEvent
|   |_ MongockChahgeLogStartedEvent
|   |  |_ MongockChahgeSetStartingEvent
|   |  |_ MongockChahgeSetFinishedEvent
|   |_ MongockChahgeLogFinishedEven
|_ MongockFinishedEvent

Hello @marchrius ,
I am glad you ask that because we have planned to add this feature. When I say "plan" I mean we have decided to add it, however there are some other priorities first and I cannot tell you when exactly this will be available, but after transactions, recovery, undo and some other, this is next, so my expectation is beginning of august.
Thanks


[Feature Request] Apply edit dialog using keyboard (e.g. Ctrl+Enter)

[x] I agree to follow the Code of Conduct that this project adheres to.
[x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Is your feature request related to a problem? Please describe.
I'm always frustrated when I have to use mouse to click Apply on the edit dialog. Escape closes the edit dialog. There should be a way to confirm (=Apply) dialog with keyboard as well.
Describe the solution you'd like
I suggest Ctrl+Enter to confirm the dialog.
Describe alternatives you've considered
More like a workaround, currently you have to Tab-Tab-Tab-Tab-Enter to confirm dialog.
Additional context
No additional context.

Good idea! We'll add this in the next release.

@alderg should I open new issue?

If it works in the online version and fails in a desktop build, please open the issue on the desktop project.

Ctrl+Enter works for me in Chrome 100.0.4896.60 on macOS 12.3.1 (21E258).


Explore potential use of OAuth 2 / OIDC to connect consumer to company

What if, for example, the AA had an app with signon from company (eg FB, Google, etc) and used that to prove to company the consumer was identical to their customer on-file?  Also, this app could be used to provide, secure and monitor communications and sending data from AA to consumer (eg for sending a copy of data about customer requested under CCPA from company).

possibly OpenID Connect claims? https://openid.net/specs/openid-connect-core-1_0.html#Claims


WIP: TLS changes

Just for testing

/test all

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

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

Test name
Commit
Details
Rerun command

release-notes_istio
4ed901e5074965efc0d7f283741e5bb676ec931e
link
/test release-notes_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

release-notes_istio
4ed901e5074965efc0d7f283741e5bb676ec931e
link
/test release-notes_istio

gencheck_istio
4ed901e5074965efc0d7f283741e5bb676ec931e
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.

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

Test name
Commit
Details
Rerun command

release-notes_istio
4ed901e5074965efc0d7f283741e5bb676ec931e
link
/test release-notes_istio

gencheck_istio
4ed901e5074965efc0d7f283741e5bb676ec931e
link
/test gencheck_istio

lint_istio
4ed901e5074965efc0d7f283741e5bb676ec931e
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.

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

Test name
Commit
Details
Rerun command

release-notes_istio
4ed901e5074965efc0d7f283741e5bb676ec931e
link
/test release-notes_istio

gencheck_istio
4ed901e5074965efc0d7f283741e5bb676ec931e
link
/test gencheck_istio

lint_istio
4ed901e5074965efc0d7f283741e5bb676ec931e
link
/test lint_istio

unit-tests_istio
4ed901e5074965efc0d7f283741e5bb676ec931e
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.

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

Test name
Commit
Details
Rerun command

release-notes_istio
4ed901e5074965efc0d7f283741e5bb676ec931e
link
/test release-notes_istio

gencheck_istio
4ed901e5074965efc0d7f283741e5bb676ec931e
link
/test gencheck_istio

lint_istio
4ed901e5074965efc0d7f283741e5bb676ec931e
link
/test lint_istio

unit-tests_istio
4ed901e5074965efc0d7f283741e5bb676ec931e
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
4ed901e5074965efc0d7f283741e5bb676ec931e
link
/test integ-ipv6-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.

/test all

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

Test name
Commit
Details
Rerun command

gencheck_istio
4ed901e5074965efc0d7f283741e5bb676ec931e
link
/test gencheck_istio

lint_istio
4ed901e5074965efc0d7f283741e5bb676ec931e
link
/test lint_istio

unit-tests_istio
4ed901e5074965efc0d7f283741e5bb676ec931e
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
4ed901e5074965efc0d7f283741e5bb676ec931e
link
/test integ-ipv6-k8s-tests_istio

release-notes_istio
1d3f50e1a79d2fabbdadce7c540f914e7d17ba1c
link
/test release-notes_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

gencheck_istio
4ed901e5074965efc0d7f283741e5bb676ec931e
link
/test gencheck_istio

lint_istio
4ed901e5074965efc0d7f283741e5bb676ec931e
link
/test lint_istio

unit-tests_istio
4ed901e5074965efc0d7f283741e5bb676ec931e
link
/test unit-tests_istio

integ-ipv6-k8s-tests_istio
4ed901e5074965efc0d7f283741e5bb676ec931e
link
/test integ-ipv6-k8s-tests_istio

release-notes_istio
1d3f50e1a79d2fabbdadce7c540f914e7d17ba1c
link
/test release-notes_istio

analyze-tests_istio
1d3f50e1a79d2fabbdadce7c540f914e7d17ba1c
link
/test analyze-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

gencheck_istio
4ed901e5074965efc0d7f283741e5bb676ec931e
link
/test gencheck_istio

lint_istio
4ed901e5074965efc0d7f283741e5bb676ec931e
link
/test lint_istio

integ-ipv6-k8s-tests_istio
4ed901e5074965efc0d7f283741e5bb676ec931e
link
/test integ-ipv6-k8s-tests_istio

release-notes_istio
1d3f50e1a79d2fabbdadce7c540f914e7d17ba1c
link
/test release-notes_istio

analyze-tests_istio
1d3f50e1a79d2fabbdadce7c540f914e7d17ba1c
link
/test analyze-tests_istio

unit-tests_istio
1d3f50e1a79d2fabbdadce7c540f914e7d17ba1c
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.

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

Test name
Commit
Details
Rerun command

gencheck_istio
4ed901e5074965efc0d7f283741e5bb676ec931e
link
/test gencheck_istio

integ-ipv6-k8s-tests_istio
4ed901e5074965efc0d7f283741e5bb676ec931e
link
/test integ-ipv6-k8s-tests_istio

release-notes_istio
1d3f50e1a79d2fabbdadce7c540f914e7d17ba1c
link
/test release-notes_istio

analyze-tests_istio
1d3f50e1a79d2fabbdadce7c540f914e7d17ba1c
link
/test analyze-tests_istio

unit-tests_istio
1d3f50e1a79d2fabbdadce7c540f914e7d17ba1c
link
/test unit-tests_istio

lint_istio
1d3f50e1a79d2fabbdadce7c540f914e7d17ba1c
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.

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

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio
4ed901e5074965efc0d7f283741e5bb676ec931e
link
/test integ-ipv6-k8s-tests_istio

release-notes_istio
1d3f50e1a79d2fabbdadce7c540f914e7d17ba1c
link
/test release-notes_istio

analyze-tests_istio
1d3f50e1a79d2fabbdadce7c540f914e7d17ba1c
link
/test analyze-tests_istio

unit-tests_istio
1d3f50e1a79d2fabbdadce7c540f914e7d17ba1c
link
/test unit-tests_istio

lint_istio
1d3f50e1a79d2fabbdadce7c540f914e7d17ba1c
link
/test lint_istio

gencheck_istio
1d3f50e1a79d2fabbdadce7c540f914e7d17ba1c
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.

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

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio
4ed901e5074965efc0d7f283741e5bb676ec931e
link
/test integ-ipv6-k8s-tests_istio

release-notes_istio
1d3f50e1a79d2fabbdadce7c540f914e7d17ba1c
link
/test release-notes_istio

analyze-tests_istio
1d3f50e1a79d2fabbdadce7c540f914e7d17ba1c
link
/test analyze-tests_istio

unit-tests_istio
1d3f50e1a79d2fabbdadce7c540f914e7d17ba1c
link
/test unit-tests_istio

lint_istio
1d3f50e1a79d2fabbdadce7c540f914e7d17ba1c
link
/test lint_istio

gencheck_istio
1d3f50e1a79d2fabbdadce7c540f914e7d17ba1c
link
/test gencheck_istio

integ-pilot-multicluster-tests_istio
1d3f50e1a79d2fabbdadce7c540f914e7d17ba1c
link
/test integ-pilot-multicluster-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.

/test all

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
1d3f50e1a79d2fabbdadce7c540f914e7d17ba1c
link
/test analyze-tests_istio

unit-tests_istio
1d3f50e1a79d2fabbdadce7c540f914e7d17ba1c
link
/test unit-tests_istio

gencheck_istio
1d3f50e1a79d2fabbdadce7c540f914e7d17ba1c
link
/test gencheck_istio

integ-pilot-multicluster-tests_istio
1d3f50e1a79d2fabbdadce7c540f914e7d17ba1c
link
/test integ-pilot-multicluster-tests_istio

lint_istio
002cf104c3548f63f3c3477171daa06c84491d6e
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.

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

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
1d3f50e1a79d2fabbdadce7c540f914e7d17ba1c
link
/test integ-pilot-multicluster-tests_istio

lint_istio
002cf104c3548f63f3c3477171daa06c84491d6e
link
/test lint_istio

unit-tests_istio
002cf104c3548f63f3c3477171daa06c84491d6e
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.

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

Test name
Commit
Details
Rerun command

lint_istio
002cf104c3548f63f3c3477171daa06c84491d6e
link
/test lint_istio

unit-tests_istio
002cf104c3548f63f3c3477171daa06c84491d6e
link
/test unit-tests_istio

integ-security-k8s-tests_istio
002cf104c3548f63f3c3477171daa06c84491d6e
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.

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

Test name
Commit
Details
Rerun command

lint_istio
002cf104c3548f63f3c3477171daa06c84491d6e
link
/test lint_istio

unit-tests_istio
002cf104c3548f63f3c3477171daa06c84491d6e
link
/test unit-tests_istio

integ-security-k8s-tests_istio
002cf104c3548f63f3c3477171daa06c84491d6e
link
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
002cf104c3548f63f3c3477171daa06c84491d6e
link
/test integ-security-multicluster-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.

/test all

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

Test name
Commit
Details
Rerun command

unit-tests_istio
002cf104c3548f63f3c3477171daa06c84491d6e
link
/test unit-tests_istio

integ-security-k8s-tests_istio
002cf104c3548f63f3c3477171daa06c84491d6e
link
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
002cf104c3548f63f3c3477171daa06c84491d6e
link
/test integ-security-multicluster-tests_istio

lint_istio
22db71bb4fd2978563e5a1642b7b9b29d92e23dc
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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
002cf104c3548f63f3c3477171daa06c84491d6e
link
/test unit-tests_istio

integ-security-k8s-tests_istio
002cf104c3548f63f3c3477171daa06c84491d6e
link
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
002cf104c3548f63f3c3477171daa06c84491d6e
link
/test integ-security-multicluster-tests_istio

lint_istio
22db71bb4fd2978563e5a1642b7b9b29d92e23dc
link
/test lint_istio

gencheck_istio
22db71bb4fd2978563e5a1642b7b9b29d92e23dc
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.

/test all

@howardjohn: 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.

/test all

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

Test name
Commit
Details
Rerun command

lint_istio
6914b1b3e1e5dbfec0569857a47eb28746faf7c0
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.

/test all

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

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
e2e13148772c0702e0094c65528d48114501da95
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

/test all

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

Test name
Commit
Details
Rerun command

unit-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test unit-tests_istio

analyze-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test analyze-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

unit-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test unit-tests_istio

analyze-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test analyze-tests_istio

release-test_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test unit-tests_istio

analyze-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test analyze-tests_istio

release-test_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test release-test_istio

integ-distroless-k8s-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
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

unit-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test unit-tests_istio

analyze-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test analyze-tests_istio

release-test_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test release-test_istio

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

integ-security-k8s-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test unit-tests_istio

analyze-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test analyze-tests_istio

release-test_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test release-test_istio

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

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

integ-ipv6-k8s-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-ipv6-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

unit-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test unit-tests_istio

analyze-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test analyze-tests_istio

release-test_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test release-test_istio

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

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

integ-ipv6-k8s-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-ipv6-k8s-tests_istio

lint_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test unit-tests_istio

analyze-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test analyze-tests_istio

release-test_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test release-test_istio

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

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

integ-ipv6-k8s-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-ipv6-k8s-tests_istio

lint_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test lint_istio

integ-pilot-k8s-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test unit-tests_istio

analyze-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test analyze-tests_istio

release-test_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test release-test_istio

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

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

integ-ipv6-k8s-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-ipv6-k8s-tests_istio

lint_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test lint_istio

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

integ-telemetry-mc-k8s-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-telemetry-mc-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

unit-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test unit-tests_istio

analyze-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test analyze-tests_istio

release-test_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test release-test_istio

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

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

integ-ipv6-k8s-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-ipv6-k8s-tests_istio

lint_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test lint_istio

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

integ-telemetry-mc-k8s-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-telemetry-mc-k8s-tests_istio

integ-pilot-multicluster-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-pilot-multicluster-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

unit-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test unit-tests_istio

analyze-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test analyze-tests_istio

release-test_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test release-test_istio

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

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

integ-ipv6-k8s-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-ipv6-k8s-tests_istio

lint_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test lint_istio

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

integ-telemetry-mc-k8s-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-telemetry-mc-k8s-tests_istio

integ-pilot-multicluster-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-pilot-multicluster-tests_istio

gencheck_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test unit-tests_istio

analyze-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test analyze-tests_istio

release-test_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test release-test_istio

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

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

integ-ipv6-k8s-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-ipv6-k8s-tests_istio

lint_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test lint_istio

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

integ-telemetry-mc-k8s-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-telemetry-mc-k8s-tests_istio

integ-pilot-multicluster-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-pilot-multicluster-tests_istio

gencheck_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test gencheck_istio

integ-telemetry-k8s-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test unit-tests_istio

analyze-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test analyze-tests_istio

release-test_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test release-test_istio

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

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

integ-ipv6-k8s-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-ipv6-k8s-tests_istio

lint_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test lint_istio

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

integ-telemetry-mc-k8s-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-telemetry-mc-k8s-tests_istio

integ-pilot-multicluster-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-pilot-multicluster-tests_istio

gencheck_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test gencheck_istio

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

integ-operator-controller-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-operator-controller-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

unit-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test unit-tests_istio

analyze-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test analyze-tests_istio

release-test_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test release-test_istio

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

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

integ-ipv6-k8s-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-ipv6-k8s-tests_istio

lint_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test lint_istio

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

integ-telemetry-mc-k8s-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-telemetry-mc-k8s-tests_istio

integ-pilot-multicluster-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-pilot-multicluster-tests_istio

gencheck_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test gencheck_istio

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

integ-operator-controller-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-operator-controller-tests_istio

integ-multicluster-k8s-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
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

unit-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test unit-tests_istio

analyze-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test analyze-tests_istio

release-test_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test release-test_istio

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

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

integ-ipv6-k8s-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-ipv6-k8s-tests_istio

lint_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test lint_istio

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

integ-telemetry-mc-k8s-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-telemetry-mc-k8s-tests_istio

integ-pilot-multicluster-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-pilot-multicluster-tests_istio

gencheck_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test gencheck_istio

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

integ-operator-controller-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-operator-controller-tests_istio

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

integ-helm-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-helm-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

unit-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test unit-tests_istio

analyze-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test analyze-tests_istio

release-test_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test release-test_istio

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

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

integ-ipv6-k8s-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-ipv6-k8s-tests_istio

lint_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test lint_istio

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

integ-telemetry-mc-k8s-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-telemetry-mc-k8s-tests_istio

integ-pilot-multicluster-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-pilot-multicluster-tests_istio

gencheck_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test gencheck_istio

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

integ-operator-controller-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-operator-controller-tests_istio

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

integ-helm-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-helm-tests_istio

integ-security-multicluster-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-security-multicluster-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.

/test all

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

Test name
Commit
Details
Rerun command

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

integ-ipv6-k8s-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-ipv6-k8s-tests_istio

lint_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test lint_istio

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

integ-pilot-multicluster-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-pilot-multicluster-tests_istio

gencheck_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test gencheck_istio

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

integ-operator-controller-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-operator-controller-tests_istio

integ-helm-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-helm-tests_istio

integ-security-multicluster-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-security-multicluster-tests_istio

analyze-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test analyze-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-security-k8s-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-security-k8s-tests_istio

integ-ipv6-k8s-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-ipv6-k8s-tests_istio

lint_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test lint_istio

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

integ-pilot-multicluster-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-pilot-multicluster-tests_istio

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

integ-operator-controller-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-operator-controller-tests_istio

integ-helm-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-helm-tests_istio

integ-security-multicluster-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-security-multicluster-tests_istio

analyze-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test analyze-tests_istio

gencheck_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
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.

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

Test name
Commit
Details
Rerun command

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

integ-ipv6-k8s-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-ipv6-k8s-tests_istio

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

integ-pilot-multicluster-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-pilot-multicluster-tests_istio

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

integ-operator-controller-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-operator-controller-tests_istio

integ-helm-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-helm-tests_istio

integ-security-multicluster-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-security-multicluster-tests_istio

analyze-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test analyze-tests_istio

gencheck_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test gencheck_istio

lint_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
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.

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

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-ipv6-k8s-tests_istio

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

integ-pilot-multicluster-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-pilot-multicluster-tests_istio

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

integ-operator-controller-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-operator-controller-tests_istio

integ-helm-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-helm-tests_istio

integ-security-multicluster-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-security-multicluster-tests_istio

analyze-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test analyze-tests_istio

gencheck_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test gencheck_istio

lint_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test lint_istio

integ-security-k8s-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
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.

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

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-ipv6-k8s-tests_istio

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

integ-pilot-multicluster-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-pilot-multicluster-tests_istio

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

integ-operator-controller-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-operator-controller-tests_istio

integ-security-multicluster-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-security-multicluster-tests_istio

analyze-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test analyze-tests_istio

gencheck_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test gencheck_istio

lint_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test lint_istio

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

integ-helm-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-helm-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-ipv6-k8s-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-ipv6-k8s-tests_istio

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

integ-pilot-multicluster-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-operator-controller-tests_istio

integ-security-multicluster-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-security-multicluster-tests_istio

analyze-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test analyze-tests_istio

gencheck_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test gencheck_istio

lint_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test lint_istio

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

integ-helm-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-helm-tests_istio

integ-telemetry-k8s-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
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.

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

Test name
Commit
Details
Rerun command

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

integ-pilot-multicluster-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-operator-controller-tests_istio

integ-security-multicluster-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-security-multicluster-tests_istio

analyze-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test analyze-tests_istio

gencheck_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test gencheck_istio

lint_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test lint_istio

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

integ-helm-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-helm-tests_istio

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

integ-ipv6-k8s-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-ipv6-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-pilot-multicluster-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-operator-controller-tests_istio

integ-security-multicluster-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-security-multicluster-tests_istio

analyze-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test analyze-tests_istio

gencheck_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test gencheck_istio

lint_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test lint_istio

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

integ-helm-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-helm-tests_istio

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

integ-ipv6-k8s-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
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.

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

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-operator-controller-tests_istio

analyze-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test analyze-tests_istio

gencheck_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test gencheck_istio

lint_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test lint_istio

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

integ-helm-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-helm-tests_istio

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

integ-ipv6-k8s-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-ipv6-k8s-tests_istio

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

integ-security-multicluster-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-security-multicluster-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.

/test all

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

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-operator-controller-tests_istio

analyze-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test analyze-tests_istio

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

integ-helm-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-helm-tests_istio

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

integ-ipv6-k8s-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-ipv6-k8s-tests_istio

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

integ-security-multicluster-tests_istio
ee37f0e1b2202e18a0f965e5e083ca53404f1526
link
/test integ-security-multicluster-tests_istio

lint_istio
2ac5426e7dd85681b218a7d2e120e60bef19240e
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.

/test all

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

Test name
Commit
Details
Rerun command

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

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

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

lint_istio
87e10967c1dbe98dff3083fa052d2941276bb8ee
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.

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

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio
5fa5b7bed4fea8799905c893c214c21e011106eb
link
/test integ-security-multicluster-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

Overall looks good. Just minor comments.

Any thoughts/plan for more testing? Since the changes are non trivial and bugs may come from TLS/HTTP/Sniffing combination corner case. Also we don't have a feature flag. (understandably hard to do so though).

This is actually probably one of the most thoroughly tested parts of our xds generation. We have very complete integration tests and unit tests - you can see the tests actually already caught all the issues this is fixing and the PR just updated them to not longer he skipped.

Question, if I have a port declared port, do they include these non Istio ALPN as well? It's will be easier to follow then, since we are making pass through filter chain match the same as explicit port.

Yes, with this PR the passthrough and explicit port will generated identical filter chain match. Prior to this PR it was different which is what led to some of the issues this is fixing

is ListenerProtocolAuto is needed on outbound listener only, for http sniffing? and here the PR is changing inbound, that's why we don't need to handle?

A filter chain is either http or tcp - it cannot be "auto". An auto listener consists of http and tcp filter chains. Therefore, the plugins only need to handle tcp or http filter chain, as there is no concept of "auto filter chain".
Possibly as a follow-up pr we should change the type so that Auto is not even a valid option?

@yangminzhu @incfly @ramaraochavali I believe I have addressed all comments, please let me know if I missed any. Thanks!


Hitting rate limits when --builder-per-project is enabled.

acorn version v0.6.0-12-g5e4b75d0+5e4b75d0
Steps to reproduce the problem:
acorn install --builder-per-project=true.
Created multiple projects and deployed apps in these projects.
When there are enough number of projects (about 100)  created and apps deployed in them , we are not able to deploy apps anymore because of hitting rate limits when building images.
  ✗  ERROR:  failed to solve: nginx: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/nginx/manifests/sha256:aa0afebbb3cfa473099a62c4b32e9b3fb73ed23f2a75a65ce1d4b4f55a5c2ef2: 429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit

acorn install --builder-per-project=true
Created multiple projects and deployed apps in these projects.
Eventually I started  hitting the rate limit issue.
Followed the steps mentioned - https://docs.acorn.io/next/faq#i-am-hitting-rate-limits-from-dockerhub - to add my docker credentials.
Even after this , I continue to see the rate limit issues when trying to deploy apps from Acornfile.
I am able to add the same docker credentials at the project level and see it being used when  deploying apps from Acornfile in that project.

Able to follow the steps mentioned in the docs to configure  docker credentials which will then be used for acorn run, build and pull commands.


platformio: Add udev rules to package output

Motivation for this change
The udev rules shipped with platformio are not part of the package output. This is a follow up to #91679 (I'll close the PR when this gets merged)
Things done
Put the udev rules into $out/lib/udev/rules.d/99-platformio-udev.rules. This also adds a patch to change the default warning when the rules are not found to a more NixOS specific message.
Some things feel weird for me:
1.) Is calling fetchFromGitHub in multiple places with the same arguments considered good style? I could not think of a better way to do this.
2.) Is patching a appropriate way to inform about the usage of the udev rules?

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@f4814 great stuff, thanks!


Export callable into function with single error return value

I noticed that exporting a callable into a func() error type field throws a panic at runtime instead of returning the error.
As far as I can see, this is because the following code only checks if the target function has two return values or none. Is there a specific reason not to check for a single error return value?
https://github.com/dop251/goja/blob/261677941f3cd8b7f091620b63627a29de9e46be/runtime.go#L2157-L2163
Thank you for the library, I really enjoy working with it! :pray:

Yes, the reason is to distinguish between when function returns an error and when it throws it. For that, the first return value of the Go function (if present) always corresponds to the return value of the ES function and the second return value (if present and is error) corresponds to the thrown exception.
If you're not using the return value, you can export to func() (Value, error) and ignore the Value.

Yeah, that's what I ended up doing.
Alright, got it! Thanks for the clarification. :+1:


Failing to extract the xml test results

Once in a while I see this error when the cli is trying to open the .zip and extract the test results from XML.
This happens on our VSTS test runs, I don't have access to this machine.
{"nunit_xml_zip":"https://testcloud-artifacts.s3-eu-west-1.amazonaws.com/23d33e49-eaab-4515-b625-247f7b4b3801/d50797b5-8804-4760-84cf-0082eee4a753?response-cache-control=max-age%3D315576000\u0026AWSAccessKeyId=AKIAI4UZT4FCOF2OTJYQ\u0026Signature=xsWgky41d1mJO5fh0FbCWbFeMZc%3D\u0026Expires=1735689600"}}}
2018-06-07T19:35:38.3878910Z
2018-06-07T19:35:38.3915040Z
2018-06-07T19:35:38.3923710Z
2018-06-07T19:35:38.3941430Z Downloaded artifacts to /Users/vsts/agent/2.134.2/work/r1/a/testresults/nunit_xml_zip.zip
2018-06-07T19:35:38.3965610Z Error: XML merging has ended with an error
2018-06-07T19:35:38.3974990Z
2018-06-07T19:35:38.3992620Z Further error details: For help, please send both the reported error above and the following environment information to us by going to https://appcenter.ms/apps and starting a new conversation (using the icon in the bottom right corner of the screen)
2018-06-07T19:35:38.4001980Z
2018-06-07T19:35:38.4019700Z     Environment: darwin
2018-06-07T19:35:38.4041110Z     App Upload Id: xtc-Xamarin-Forms/XamControl
2018-06-07T19:35:38.4062100Z     Timestamp:<PHONE_NUMBER>254
2018-06-07T19:35:38.4079190Z     Operation: RunManifestTestsCommand
2018-06-07T19:35:38.4095970Z     Exit Code: 3

https://devdiv.visualstudio.com/DevDiv/_release?releaseId=111040&_a=release-logs
check iOS10 logs

Thanks @rmarinho for flagging this out! We're taking a look at this. FYI @glennwester

Hi @rmarinho this issue should have been fixed with the PR #457, merged and released in the new CLI v1.1.0 version today. Could you install the new CLI version, and check if this issue is resolved? Thanks.

Hey @rmarinho ! This issue should have been fixed with the PR #457. Do try it out, and let us know if you have any other questions. I'll be closing this ticket for now.
Amanda


do the messages need to be more structured

like marked up as an https://datatracker.ietf.org/doc/html/rfc5322

cc @mitchelljkotler,

not at this time.


CollectorRegistry undefined order of unlocking

The CollectorRegistry uses theading.Lock for mutexing purposes. It does not have a defined order of unlocks.
In our use-case sometimes three or more actions happen almost simultaneously and sometime this would case them to appear in the wrong order.
The easiest solution in my opinion would be to use threading.Semaphore instead.

Can you please explain more about your issue?

Sure, our use-case might a bit of a stretch for a pull-based problem. I wrote a simple exporter using this library to expose the metrics of our CI (buildbot). While one already exists https://github.com/claws/buildbot-prometheu it is not very useful for us.
What we need is the state of the build: running, pending, success, failed, etc.
These events come asynchronously via buildbot's master Message Queue.
What would quite often happen is that there would three state changes very close of one another say pending -> running -> success within a couple ms.
The pending would acquire the lock for the CollectorRegistry as would the other two. Then since the order of unlocking is not defined for Locks the events would end up in the opposite order there fore it would appear as pending -> success -> running and the build would appear to hand on running even when it was not until it was run again.
This could be solved by using a Semaphore instead which has defined order of unlocking in the order of acquiring them.
I understand this situation is more suitable for an event based push system, but for now it is working for us as is with using a Semaphore on top of CollectorRegistry

What is the performance cost of this change?

I was unable to find a resource on the exact performance difference of Lock and Semaphore in Python.
However the difference should not be that noticeable since a lock is a special case (unary) semaphore. The only difference is that lock only holds boolean value whether it is open or not whereas a semaphore has a counter that increments and decrements.  The counter then decides which thread should go into the critical section next.


[5.5] Add a from test helper method

This adds a method called from which can be chained when testing HTTP requests. It's a friendly wrapper that sets the incorrectly spelt Referer header. This makes it helpful to test things like validation exceptions that should redirect to the previous page. It's a little more explicit then checking that it redirects to the root URL which it would by default.
$response = $this->from('/register')
    ->post('/register', $invalidAttributes);

$response->assertRedirect('/register');

Seems legit #21448


get_agent_secrets doesn't work if agent version == 'latest'

when we call db.get_agent_secrets we have to provide actual agent version instead of string "latest"

I think it's only the data_source == "local_files" branch in get_agent_entry. Does that match what you're seeing? We can add an extra lookup on that side of the conditions.

Yes, I noticed it in local_files mode


feat: enhance profile with member status (#416)

cloes #416

Club Member Status:

ECF Membership Status:


[Feature Request] concat shape support for ViT

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Concat is currently falling back to CPU and is killing e2e perf.
See: https://tenstorrent.sharepoint.com/:x:/r/sites/Jasmina/_layouts/15/Doc.aspx?sourcedoc={4D45EB45-E309-4B38-883D-CEC7D4CD93FB}&file=ops_perf_results_vit_E2E__2024_04_04_21_25_15.xls&action=default&mobileredirect=true
Describe the solution you'd like
Concat Support for this configuration per ViT.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

@mbahnasTT

checked with @mbahnasTT's unit test. I added it here on my own branch:
https://github.com/tenstorrent-metal/tt-metal/commit/3cd19c6049ff65391540be0d53527fc412bb3e5b
TTNN for some reason is forcing a fallback if it's not tilized, in my commit I hacked ttnn to let this through, and it works on device. @arakhmati @eyonland will need to see why @mbahnasTT 's cases are fallback since it does work on device.

workaround with ttnn.experimental works

concat issue solved.


python311Packages.bleak-esphome: init at 0.2.0

Bleak backend of ESPHome
https://github.com/bluetooth-devices/bleak-esphome
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 274081 run on x86_64-linux 1

4 packages built:

python310Packages.bleak-esphome
python310Packages.bleak-esphome.dist
python311Packages.bleak-esphome
python311Packages.bleak-esphome.dist


infinite email loop

Hi,
I have a mail alias from<EMAIL_ADDRESS>to<EMAIL_ADDRESS><EMAIL_ADDRESS>is the mailbox of one of my customers)
but the email box at<EMAIL_ADDRESS>is configured with a autoresponder and send back a message to<EMAIL_ADDRESS>It will result in a infinite message loop.
Is there any way to be protected from such case ?
Have a good day.

This seems to be a general postfix question and perhaps better ask this somewhere else?
Perhaps there is a clue in here:
https://unix.stackexchange.com/questions/174003/rewriting-from-header-when-forwarding-email-using-postfix
Seems to me there should be no mail-loop since the auto-reply should go to the original reponder (but better test that assumption)

I agree, this is a pure postfix question. I would try upstream or https://stackexchange.com. I'll leave the question open in case someone has an answer though!

Hi, I've posted the question to: https://stackoverflow.com/questions/60337284/infinite-email-loop-with-alias-when-auto-responder-is-activated-on-destination-e

StackOverflow is for programming questions, you might get better results at https://serverfault.com/questions (though they dislike cross-posting).

@erik-wramner also posted on serverfault :) thx