Should Spectrum support environments running Java 6?

The test runner itself (everything in src/main/java) only uses features that are backward-compatible with Java 6. The idea was to keep Spectrum available as an option in scenarios where Java 8 isn't allowed and/or feasible (like testing Android apps and in many enterprise environments that aren't "ready" for Java 8 yet).
The specs themselves can be written in Java 6, but of course lambdas aren't available so they don't look as pretty:
describe("specs using Java 6", new Block() {
  @Override
  public void run() throws Throwable {

    it("can use anonymous objects", new Block() {
        @Override
        public void run() throws Throwable {
            assertEquals(1, foo);
        }
    });
  }
});

I see a few choices:

Officially support Java 6 using anonymous objects (as above). While we don't have a Java 6 automated build to verify it (yet), I believe this will work just fine in the current state. This would mean keeping the production code in Java 6 mode.
Officially support Java 6 using Retrolambda. This would allow us to use some of the Java 8 language features (but not APIs), while compiling to bytecode that runs on older JVMs.
Forget compatibility with anything less than Java 8. This will make our development lives easier, but may eliminate the tool from consideration for some users.

Thoughts? Ideas?

Java 8 was released two years ago, so it's certainly reasonable to go with
option 3. Not just because options 1 and 2 represent additional work, but
because they clutter the design of the code.
Android is about to get lambda support in the upcoming release. Anyone
starting a new project will use Java 8. Anyone stuck on older versions of
Java, likely because they don't have tests in the first place, is probably
not going to adopt Spectrum anyway.
The test runner itself (everything in src/main/java) only uses features
that are backward-compatible with Java 6. The idea was to keep Spectrum
available as an option in scenarios where Java 8 isn't allowed and/or
feasible (like testing Android apps and in many enterprise environments
that aren't "ready" for Java 8 yet).
The specs themselves can be written in Java 6, but of course lambdas aren't
available so they don't look as pretty:
describe("specs using Java 6", new Block() {
@Override
public void run() throws Throwable {
it("can use anonymous objects", new Block() {
    @Override
    public void run() throws Throwable {
        assertEquals(1, foo);
    }
});

}
});
I see a few choices:

Officially support Java 6 using anonymous objects (as above). While
we don't have a Java 6 automated build to verify it (yet), I believe this
will work just fine in the current state. This would mean keeping the
production code in Java 6 mode.

Officially support Java 6 using Retrolambda
https://github.com/orfjackal/retrolambda. This would allow us to use
some of the Java 8 language features (but not APIs), while compiling to
bytecode that runs on older JVMs.

Forget compatibility with anything less than Java 8. This will make our
development lives easier, but may eliminate the tool from consideration for
some users.

Thoughts? Ideas?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/greghaskins/spectrum/issues/27

@rkawala good point about Android. You're referring to Android N right? It looks like after that is released, life gets a lot easier for Android devs.
I'm not sure what to do about web devs stuck on older Java versions. For one, I don't think an old Java version implies teams don't write tests. I have been on several teams stuck on old JVM versions like WAS for whatever reason, but we still test-drove our code. A lot of bigger companies are very slow to adopt newer versions of the JVM. It's hard to find stats online, but at least a couple different places [1] [2] show a sizeable group of developers not yet on Java 8.
I know many library projects (e.g. Commons, Spring, Guava, etc.) maintain backward-compatibility for just that reason, and they certainly write lots of unit tests. Requiring sourceCompatibility = 1.8 with Spectrum would mean library authors using it would also have to require Java 8 (at least to run their own test suite). This article about Spring compatibility was interesting.
That said, there might still be enough reasons to drop pre-1.8 support:

Spectrum tests really should be written with lambdas. If you can't use them, it pretty much defeats the point of the library.
We could use streams and other good bits from the latest Java 8 standard library, not to mention lambdas on the production side of the library.
More simplicity in building and supporting the library, since there are fewer possible edge cases that could crop up across JVM versions. No need to maintain a separate suite of Java-6-compatible tests for Spectrum or anything like that.
There's a precedent in many cases where tests can run newer/different Java versions, even if production code has to be Java 6. Heck, even the Spring Framework build.gradle uses this technique.

I guess after that wandering line of thought, I'm leaning towards supporting only Java 8 (and newer). Anyone have a strong opinion in support of backwards compatibility?
Spectrum will probably have one more mid-size internal refactor before 1.0, so it would be good to have this settled in the next week or so. Dropping Java 6 support would be a semver major change, although we're still in 0.x.y "initial development" mode at the moment.

I know you asked for strong opinion in support of backwards compatibility, but this is so true we need to repeat it:

Spectrum tests really should be written with lambdas. If you can't use them, it pretty much defeats the point of the library.

If something is not easy to do, people just do not use it. If there was no Java 8, would you write spectrum? I don't think so - JUnit will be much less verbose, even if it does not let you document your tests like spectrum's BDD style does.

Good points, all.
It sounds like it's settled: Spectrum will require Java 8 to run tests. Our implementation will assume that minimum, both for syntax and the standard library.
Users may use Spectrum to test production code that is pre-1.8, of course, but their test scope would require a Java 8 compiler and JVM.


Got ErrorException after installation and login

Hi,
After installation, I tried to login by admin account.
But it threw Error Exception like as below
ErrorException
Undefined property: stdClass::$Tables_in_softcrm

Can you give me any hint for resolve it ?
Regards

Hello @datvoquoc
You got this error because you have another name of database than 'softcrm'. I have marked this issue as "Need to be fixed".
Actually, I have fixed this issue, and you can pull changes from master branch.
Thank you for support.

Hi @KamilGrzechulski
Thanks for your fast responding.
I tried and it has been fixed.
Regards.


test which python versions we can support

e.g., due to https://github.com/numba/llvmlite/issues/531 there seems to be an issue in 3.9

3.6 dropped due to numpy 1.20, 3.9 not possible due to numba


Only zero values on ESP32 Wroom

Hi,
with ESP32 Wroom Dev Board I get only 0 values for all PM sizes every second.
 See output example:
117:50:38.875 -> 203
17:50:39.466 -> 77
17:50:39.504 -> 0
17:50:39.537 -> 50
17:50:39.605 -> 0
17:50:39.639 -> 0
17:50:39.712 -> 0
17:50:39.748 -> 0
17:50:39.783 -> 205
17:50:40.290 -> 77
17:50:40.358 -> 0
17:50:40.396 -> 50
17:50:40.429 -> 0
17:50:40.497 -> 0
17:50:40.534 -> 0
17:50:40.602 -> 0
17:50:40.635 -> 205
17:50:41.230 -> 77
17:50:41.264 -> 0
17:50:41.297 -> 32
17:50:41.367 -> 0
17:50:41.401 -> 0
17:50:41.469 -> 0
17:50:41.503 -> 0
17:50:41.571 -> 183
Thank you for your help!

Hi and sorry, here it is:

// lib for using hardwareserials with ESP32
#include <HardwareSerial.h>
HardwareSerial Ser1_33_32_PMS7003(1);
// PMS OPC
#include "PMS.h"
PMS pms(Ser1_33_32_PMS7003);
PMS::DATA data;
void setup() {
/***************************************************
SERIAL PORTS CONFIGURATION - BEGIN
****************************************************/
Serial.begin(9600);
// let serial console settle
delay(10);
Ser1_33_32_PMS7003.begin(9600, SERIAL_8N1, 33, 32);
delay(10);
/***************************************************
SERIAL PORTS CONFIGURATION - END
****************************************************/
} // setup end
void loop() {
// next for lines: just checking if serial data is coming from sensor
//if (Ser1_33_32_PMS7003.read() > 0) {
//delay(50);
//Serial.println(Ser1_33_32_PMS7003.read());
//}
// the active example function
if (pms.read(data))
{
Serial.print("PM 1.0 (ug/m3): ");
Serial.println(data.PM_AE_UG_1_0);
Serial.print("PM 2.5 (ug/m3): ");
Serial.println(data.PM_AE_UG_2_5);

Serial.print("PM 10.0 (ug/m3): ");
Serial.println(data.PM_AE_UG_10_0);

}}

Serial.println(Ser1_33_32_PMS7003.read());
I don't get it, what you want to achieve with this code.
It is totally wrong. read() just returns boolean.
You did not give any output log with above code, so I don't know what is printed out now.
It is worked with ESP32 for sure, so check wiring again and your configuration (pins).
Just use attached examples and connect properly without changing in the code.
If everything work, then start modify your code 😃
Sorry, I don't' have PMS on my desk anymore.

Thank you for your response.
The lib works like it should on my ESP32! The sensor just needed several minutes to start showing the bigger values!
With the Serialprintln I wanted to pass the pmsSerial input to serial like this:
if (pmsSerial.available()) {
Serial.write(pmsSerial.read());
}
Anyway, it works now, thank you!


Is this still working in Unified Interface?

I can't seem to find the session with the URL of the web resource in Unified Interface form.

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

ID: 2682c773-2fd4-872e-a557-12403a4a7099
Version Independent ID: f51f3347-736f-67e5-8bf4-9eebb44256ad
Content: Streamline JavaScript web resource development using Fiddler AutoResponder (Developer Guide for Dynamics 365 Customer Engagement (on-premises))
Content Source: ce/customerengagement/on-premises/developer/streamline-javascript-development-fiddler-autoresponder.md
Service: crm-online
GitHub Login: @susikka
Microsoft Alias: susikka

Hi, whats the status on this issue? I'm experiencing the same thing. This has changed as I was able to use this functionality in UUI before. Additionally I see that on some entities it still works. For me the campaign entity does not work but the account entity does. hard for me to see why..

@LinnZawWin @elca-lpr Thanks for creating this issue. We will look into it and update the doc soon.

@susikka will there be any update?

Assigning this to @phecke

@LinnZawWin Thanks for your feedback. We are closing this issue because we are either unable to find relevant information or reproduce this. If you're still experiencing the issue described here, please reopen or create a new issue.


Add RelationshipDirection.UNDIRECTED support to ElasticSearchGraphService

The com.linkedin.metadata.graph.GraphService API contains two methods findRelatedEntities and removeEdgesFromNode that allow to set a RelationshipDirection via RelationshipFilter. The current ElasticSearch implementation supports directions INCOMING and OUTGOING, but UNDIRECTED is not supported.
Implement UNDIRECTED or clearly document this is not implemented and throw a respective exception.
There are tests in #3011 that test the undirected relationships case.

@EnricoMi, I agree- we should articulate it is not supported at the moment.

Hi @EnricoMi!
We are now managing feature requests through our new portal to improve visibility & prioritize work into our public roadmap. If this request is still relevant, please create a new issue so we can gauge current interest from the Community & prioritize work accordingly.
We'll close out this issue in the meantime. Feel free to reach out to me on DataHub Slack with any questions!


Apply stricter linting

Already fixed most of these errors on DT, but will run tests again as more errors may have popped up in the interim.

@andy-ms,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


xeval/evaluator: add math function

Hi,
This PR add math function abs_int to expression evaluator.
PTAL @XuHuaiyu @AndreMouche @lishihai9017 @andelf

PTAL @XuHuaiyu @AndreMouche @lishihai9017 @andelf

The impl of abs_int will be raised as a new PR, so that it would be a independent  PR for the demonstration in document.

LGTM


[ASK] Are all the tdlib methods for Android not available, just td_json_xxx?

I tried building tdlib using the examples in examples/android
command I ran:
docker build --build-arg TDLIB_INTERFACE=JSON --output tdlib .
after I tried on Android Flutter but td_execute wasn't there
how to make all these function methods available?

https://core.telegram.org/tdlib/docs/td__json__client_8h.html

td_execute is called td_execute on Android instead of _td_execute now. You need to modify the wrapper to use the same function names for all operating systems.

Thank you very much,


API additions: rotatedPoint, scaledPoint, dilatedPoint, translatedPoint

It's a concept worth calling out that rotations, dilations, translations, and scaling can be applied to points, as well as pictures.  (In fact, viewing a picture as Point -> Color, the transformations on pictures should satisfy: pic = transform(pic) ∘ transformPoint
Therefore, we'd like to add these four functions to the Prelude.

Note that this duplicates vectorSum, rotatedVector, and scaledVector.  I'm not proposing that we remove the latter quite yet, since there are also other vector functions, such as vectorLength, vectorDirection, and dotProduct, which don't have replacements in this framework.  So we'll just have some duplication.  The names aren't stealing valuable real estate, so that's okay.

@alphalambda FYI


VMS: modernise rand_pool_acquire_entropy

Stop redefining structures that are already defined in system
headers.  This also means we can stop setting the pointer size
globally, because the system structures will have the correct pointer
sizes either way.  The only exception is passing the right pointer
size to a function.
Stop trying to twist things around with rand(), that's the job of the
DRBG that we feed.
Stop assuming the location of the JPI$_FINALEXC item, look it up
instead.
Signal an exception if the sys$getjpiw call fails (it means the item
list isn't set up right, so works as an assertion, but using VMS
methodology).
Add more items that could serve as entropy source.

Note: together with #6150, the entropy factor will be made larger (i.e. the VMS entropy gatherer will become much more pessimistic about the quality of the entropy sources)

I currently get a mysterious crash on IA64...  need to resolve that before approval

Some of output sizes are 8. Does it imply corresponding alignment? If so, it might be the reason. I mean if it's supposed to be aligned, then there are some that won't be. Because number of prior 4-byte sized elements is not even.

Ooooh, I think you're on to something.  The data_buffer pointer you're thinking about points at an array of 32-bit integers, and if the 8-byte element happen to be an odd element, it will be positioned across a 64-bit boundary.
I think that the easiest is to make the array a GENERIC_64 array instead of a uint32_t one.  GENERIC_64 is a union of a 64-bit integer, 2 32-bit integers and 4 16-bit integers, and since we allocate the space for potential 64-bit numbers at every item anyway, we might as well...

Or hmmm...  GENERIC_64 turns out to be a bad idea, that will leave some holes in the array that we send to the pool.  Better then to treat all 8-byte elements separately...

That did change something...  now it crashes elsewhere...

Away a few hours, I'll get back to this tonight

This is now crash free on VMS.

I'm confused. At one point you said that alignment insurance [for data_buffer_64bit] is required, but provide none. This doesn't actually contradict assertion that it's crash-free, because compiler is likely to align it, it's custom. Do you want to leave it for somebody else to keep an eye on too? Or maybe alignment is not an issue after all. You can verify this by initializing total_elems_64bit with 1 (and expanding data_buffer_64bit by 1).

I totally spaced on what you might mean with "insurance", sorry.  What do you have in mind?
The experiment with initializing total_elems_64bit to 1 resulted in a %SYSTEM-F-BADPARAM, bad parameter value on Alpha, but error free on IA64.  This kinda sorta indicates that you're right about alignment not being an actual issue.  I'll investigate (gotta rebuild in debug mode)...

"insurance"

https://github.com/openssl/openssl/pull/6151#discussion_r185495817

%SYSTEM-F-BADPARAM ... you're right about alignment not being an actual issue.

Contrary, this is indication that alignment is an issue. Because failure on one system is sufficient to classify it as problem.

Re insurance, I separated the buffers in two, one for 64-bit data and one for 32-bit.  Are you telling me that the compiler won't ensure that an individual array - actually any variable - starts at an aligned address?

%SYSTEM-F-BADPARAM ... you're right about alignment not being an actual issue.

Contrary, this is indication that alignment is an issue. Because failure on one system is sufficient to classify it as problem.

What I didn't say was that there is no error on IA64...  that did take me by surprise.  But I may have failed something, so I'm rebuilding from scratch with total_elems_64bit initialized to 1.  But do note that I said "kinda sorta".
(wanna know the infuriating thing?  On alpha, when I build in debug mode and run it under the debugger, that error doesn't show up)

Re insurance, I separated the buffers in two, one for 64-bit data and one for 32-bit.

And problem there was that amount of preceding 32-bit values could be uneven, so that few 64-bit ones were guaranteed to be misaligned.

Are you telling me that the compiler won't ensure that an individual array - actually any variable - starts at an aligned address?

Compiler is obliged to align at natural type boundary. I mean 32-bit variables/arrays shall be aligned at 32-bit boundaries, 64-bit - at 64-bit. 32-bit variables can be aligned at 64-bit boundaries, and as already said, 64-bit compilers customarily align all stack objects at 64-bit boundaries. However, they don't have to, hence you can't make assumption that they actually do. Keyword here is that both arrays are declared uint32_t, even data_buffer_64bit, hence compiler may align the latter at 32 bits. So that if alignment for 64-bit values is issue, then you better arrange it in a way that makes compiler always align data_buffer_64bit at 64-bit boundary.

Ah!  I misremembered that as only applying within structures...
It just dawned on me, btw, that there's really no need for two different data buffers, as long as we start with the 64-bit values.

Merged.  Thanks for the detailed review!
463e6ef500ead3fefccc470ce2f82429bb060e70 VMS: modernise rand_pool_acquire_entropy, step 2
ce147f7333fa56ab87a0878b34649991a5dae8f5 VMS: modernise rand_pool_acquire_entropy, step 1


Update to genienlp 0.3.0

genienlp 0.2.0 will try to install an incompatible version of
the transformers library

Pull Request Test Coverage Report for Build 2564

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 69.097%

Totals

Change from base Build 2561:
0%

Covered Lines:
7857

Relevant Lines:
10702

💛  - Coveralls


[compositor-client]: Enable mouse cursor for RPI.

Blackduck scan failure details
Summary: 0 violations, 0 files pending approval, 1 file pending identification.

Protex Server Path: /home/blackduck/github/ThunderClientLibraries/147/rdkcentral/ThunderClientLibraries

Commit: 591b75c3e5b28a02396d9290d4623fd7bdb23d38

Report detail: gist

Blackduck scan failure details
Summary: 0 violations, 0 files pending approval, 1 file pending identification.

Protex Server Path: /home/blackduck/github/ThunderClientLibraries/147/rdkcentral/ThunderClientLibraries

Commit: dfd3dc7ad157c05ee2afb472990b00bffb00cfdc

Report detail: gist

I thought indeed it might be related with the license text, but it seems the first commit was good, as it was only complaining that there is "code-match" https://gist.github.com/3ad5da20df2b362d7030cbd0050f00df

Seems indeed you are right and this is a false positive. Let me ask someone more knowledgeable on this.

Hi @mhughesacn
It looks like Black Duck reports a code match for a file, but seen the content of the file, it is just a cursor image, this might be a false positive. What should we do?


router: add two header formatter operators

This commit updates the router's header formatter to support
the RESPONSE_FLAGS and RESPONSE_CODE_DETAILS operators.
Signed-off-by: Spencer Lewis<EMAIL_ADDRESS>Risk Level: low
Testing: small updates to existing unit tests
Docs Changes: updated http conn man custom request/response headers doc
Release Notes: updated current version history

Thanks please merge maser.
/wait


improve nydus snapshotter container image

A few improvements for the nydus-snapshotter image.

support customized containerd root path
use shared daemon mode
handle base image CA issue
do not install recommended packages
clean up apt cache

Signed-off-by: Peng Tao<EMAIL_ADDRESS>

Codecov Report

Merging #15 (bbf4ff1) into main (21cb822) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #15   +/-   ##
=======================================
  Coverage   34.56%   34.56%
=======================================
  Files          18       18
  Lines        1270     1270
=======================================
  Hits          439      439
  Misses        760      760
  Partials       71       71

Continue to review full report at Codecov.

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


fix ts tabindex to use number

I did not change flow typings as requested, only ts ones

Thanks


drupal self-update is not work out-of-box

http://take.ms/vaVNf

Use sudo drupal self-update.
Also, the most recent version of cli has the most recent Drupal Console installed (1.0.0-alpha).
Run dsh update images


Add pshah123's list of lists

Add pshah123's list of lists, which contained some lists which were not in other lists of lists.

How did I miss that one? Thanks @ajburley!


update Caliptra.md

Changing SoC 'debug state' to 'insecure state'
I'm not entirely sure if Caliptra and the SoC really need to be synchronized regarding the debug state across all lifecycle stages. For example, if we're in a product manufacturing stage and if there is an environment that ensures secure manufacturing (though defining this itself is also challenging), wouldn't it still be possible to consider the SoC to be in a secure state even if it's in a debug state (e.g., JTAG opened)? Additionally, during manufacturing, the SoC state could transition from debug state to non-debug state. However, should the state of Caliptra and the SoC be synchronized at every moment throughout this process? I feel 'insecure state' might be more appropriate than 'debug state.' Is there a specific reason why it must be the debug state? I'd like to hear your thoughts on this.

Changing Caliptra 'unsecured state' to 'insecure state'
In the Caliptra.md, states are defined as Secure/Insecure. Except for this one statement, the term 'insecure' is used consistently throughout

#252

@Bryankel, @andreslagarcavilla
Can you review this PR and provide your opinion? I'm not sure why, but I'm unable to assign reviewers myself.

On the question you asked on point number 1, if debug path to SoC is open, our stance is that no production secrets (assets) should exist. Even though everyone intends to do right thing, side channel paths have exposed secrets before. So if SoC is in debug state, Caliptra should also have that debug mode information to clear the secrets.
Also we don't want to change the architectural nomenclatures in the spec without prior discussions as it will have confusion for underlying development work since all of us have been aligned on what these names mean. We understand that each company has a different naming convention but we request you to adhere to the existing nomenclature.

On the question you asked on point number 1, if debug path to SoC is open, our stance is that no production secrets (assets) should exist. Even though everyone intends to do right thing, side channel paths have exposed secrets before. So if SoC is in debug state, Caliptra should also have that debug mode information to clear the secrets.
Also we don't want to change the architectural nomenclatures in the spec without prior discussions as it will have confusion for underlying development work since all of us have been aligned on what these names mean. We understand that each company has a different naming convention but we request you to adhere to the existing nomenclature.

Thanks for your feedback.
I agree with the concerns raised in point number 1. However, I’d like to better understand the specific paths that could lead to a secret being exposed. Is the concern focused on scenarios where the protection mechanisms for Caliptra assets are not properly implemented? Or are there potential paths for exposure even when the protection is functioning as intended? For example, even if the SoC’s JTAG is open in the Caliptra DebugLocked state, it’s hard to imagine how an attacker could gain a meaningful advantage. (even though I do understand the intention behind the concern, I didn't fully understand the path we're concerning)
And how should the scope of the SoC debug state be defined? Since debug capabilities differ across vendors, it may be difficult to define this in a generic way. However, this opens the door for subjective interpretations as well. Would it be sufficient to recognize the debug state simply as the SoC JTAG being enabled? If we can clearly identify the paths through which secrets might be exposed, it could help define the scope of what should be included in the debug state.
Regarding on point number 2, it's not a big deal, but the spec has definitions of 'insecure' and all the statements are using 'insecure', but only one statement is using 'unsecured'.
https://github.com/chipsalliance/Caliptra/blob/main/doc/caliptra_1x/Caliptra.md#caliptra-security-states


ModuleNotFoundError: No module named 'preprocess.third_party.Track-Anything.app'

Hi, I'll try to do "lab4d".
But I have an issue.
python scripts/run_preprocess.py cat-pikachu-0 quad "0"
Traceback (most recent call last):
File "C:\Users\lab4d\scripts\run_preprocess.py", line 25, in
track_anything_module = importlib.import_module(
File "C:\Users\AppData\Local\Programs\Python\Python39\lib\importlib_init_.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 984, in _find_and_load_unlocked
ModuleNotFoundError: No module named 'preprocess.third_party.Track-Anything.app'
When I try this, There is ERROR.
Could you tell me about it?
Thank you.

python scripts/run_preprocess.py cat-pikachu-0 cat quad "0"
Traceback (most recent call last):
File "C:\Users\lab4d\scripts\run_preprocess.py", line 25, in
track_anything_module = importlib.import_module(
File "C:\Users\AppData\Local\Programs\Python\Python39\lib\importlib_init_.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 986, in _find_and_load_unlocked
File "", line 680, in _load_unlocked
File "", line 850, in exec_module
File "", line 228, in _call_with_frames_removed
File "C:\Users\lab4d\preprocess\third_party\Track-Anything\app.py", line 10, in
from track_anything import TrackingAnything
ModuleNotFoundError: No module named 'track_anything'

hi, have you solved this?


Need for Tutorial

Hello Team,
I loved the design layouts posted by your team.It would appreciate if you could include the steps to run the code in Android Studio SDK !
Thanks,
Irene

I agree, Please provide a simple tutorial or documenation for the methods used

You gave me a reason to use the ADT again~


Fix minor visual flaw in samsung_swoop.svg

The Samsung with blue "swoop" ellipse icon that was recently merged has a minor visual flaw. It was made to fit into 1KB by merging the swoop with the text, but the text's exact size and position meant that it extended past the edge of the ellipse ever so slightly, and with the new approach, that part now renders in blue, as it represents an area of odd crossings. This PR tweaks the arcs for the swoop ever so slightly so that the text is definitely within the swoop, and has pretty close to identical (minimal) spacing between the edge of the letter and edge of the swoop in both the top-left and bottom-right.
The file is still 935 bytes long.

You two are GENIUSES!


Add events and actions

Deprecate "action":"play" and replace it with a more expressive and powerful set of properties such as:

events
params (these will be addressed in a later issue; so just a placeholder here)
actions

Actions need the ability to modify elements so there needs to be a way to reference elements via a property like "name".  This "name" property can also be added to pages so that actions can perform segues to specific pages; as opposed to the current sequential segues using the swipe gesture.

Example:  Display a text element that changes the text when tapped.
	"pages": [ 		{ 			"elements": [ 				{ 					"text": "tap me", 					"pos": ["50%", "33%"], 					"w":"90%", 					"h":"10%", 					"bc":"#fdd", 					"events": { 						"tap": { 							"actions": [ 								{ 									"update": {"text":"text1 tapped"} 								}, 							] 						} 					} 				} 			] 		},

Example: Tap on element updates another element:
		{
			"elements": [
				{
					"text": "tap me",
					"pos": ["50%", "33%"],
					"w":"90%",
					"h":"10%",
					"bc":"#fdd",
					"events": {
						"tap": {
							"actions": [
								{
									"update": {"name":"other", "text":"tapped"}
								},
							]
						}
					}
				},
				{
					"name":"other",
					"text": "hello",
					"pos": ["50%", "66%"],
					"w":"90%",
					"h":"10%",
					"bc":"#fdd",
				}
			]
		},

Example: Tap on element changes text, after a delay change text again.  This is the basis for implementing a button un Swipe!
			"elements": [
				{
					"text": "tap me",
					"pos": ["50%", "33%"],
					"w":"90%",
					"h":"10%",
					"bc":"#fdd",
					"events": {
						"tap": {
							"actions": [
								{
									"update": {"text":"tapped"}
								},
								{
									"timer": {
										"duration":0.5,
										"events": {
											"tick": {
												"actions": [
													{
														"update": {"text":"tick"}
													}
												]
											}
										}
									}
								}
							]
						}
					}
				}
			]

Example:  Tap on page updates element
		{
			"//": "Tap on page, updates element",
			"elements": [
			  {
				  "name": "text1",
				  "text": "tap anywhere",
					"pos": ["50%", "33%"],
					"w":"90%",
					"h":"10%",
					"bc":"#fdd",
			  }
			],
			"events": {
				"tap": {
					"actions": [
						{
							"update": {"name":"text1", "text":"main tapped"}
						}
					]
				}
			}
		},

Note that when an element does not handle an event, the event propagates up the parent chain.  In the example above, a tap on the element is handled by the page.

That's great to have the more expressive and powerful events and actions. I have two questions:

How do you differentiate name property and id property, which is existing one?
I think a timer can be just an action with delay. Looks good for you too?

"actions": [
    {
        "update": {"text":"tapped"}
    },
    {
        "update": {"text":"tick"}, "delay":0.5
    }
]

The timer is intended to allow for multiple actions to be done on "tick"

@Pstoppani thanks for the answer. Does the timer keep working until the next page is displayed? Or will we support another event to stop the timer?

@yoichitgy A repeating timer will continue until the next page is displayed.  For now, there is no other way to stop a repeating timer any other way, but we could add an "action" to do that or some other attribute.

@yoichitgy Regarding the 'id' vs 'name' question, I think 'id' has a special meaning which is a bit confusing as it means something like "template named X at this element nesting level".  While 'name' is a name that can be referenced from anywhere.  So, my thinking is that 'id' should be renamed.  I don't have any thoughts on that right now other than the long descriptive name above!

@Pstoppani: Talking about the timer, it's enough, for me too, just to stop when the next page is displayed. We can add the stop "action" later if needed as you said.
The timer looks a nice feature for me too.

Pull request https://github.com/swipe-org/swipe/pull/39 implements the the 'events', 'actions', 'update' and 'id' features.


Increase granularity of the current process when creating meetings, and ensure all possible fails are catch.

This has to be done in order to prevent more failures and unblock admins.
The goal here is to catch any possible error every time a flow is run, a table is patched, or any data is processed. We need enough granularity to be able to include breakpoints and monitor points on the process, so if it fails, we will know exactly which step failed and why.

I discovered that we could use custom components with behavior properties as a workaround for not having functions in PowerApps.
The behavior property needs to be invoked from the OnReset property of the component, so we can put custom code on it from the Canvas App, and when we want to run that code, we just need to Reset() the component.
Example: Reset(InputChecks);
I'm not super happy with this workaround, and I'm not happy that I'm calling functions with the Reset() property, but this definitely helps with the overloading of the Buttons, and makes working with the app smoother.

After playing around with the approached I mention in the last comment, I have come up with the following list of things we can do:

Split the create and update logic into two different buttons. (When we work on this other issue https://github.com/Azure/azure-sdk-tools/issues/3676, we could also split the view into three different ones: one to schedule a new meeting, another one to see the details, and another one to edit the meeting).

A disadvantage of doing this is repeating blocks of code, for example, the input checks.

 This has to be done in every single app.

After splitting the logic intro different buttons and views, we could create a shared custom component as a workaround for not having user defined functions. However, this is very hacky, and we will need to agree if it is worth it to include and how we can document this hacky workaround so other people can understand why we are doing it this way. @praveenkuttappan is taking a look at this to see if there are other ways to have or emulate user defined functions.


Feature: styles fixes

What have been done here:

New global font-family;
Patient summary page styles fixing;
Plugin pages styles fixing;
List table and paginator styles fixing;
Settings modal window - add close button;
Add table sorting at client side;
Remove footer;
Change Search icon;
Fix pages list/forms headings

@fzaninotto Francois, could you please review this PR?

@fzaninotto
Francois, I fixed all notes to this PR. Can it be approved?


[BUG] Picamera2.global_camera_info returns no "Num" on devices with a single camera

On devices with multiple cameras, such as Pi5, Picamera2.global_camera_info() returns a dict which includes a "Num" element with values 0, 1.
On devices with a single camera only, such as Pi Zero, "Num" is not included in the returned dict.
It would have been convenient to initialize "Num" with 0 also in these cases because also there it is possible to instantiate a camera with cam=Picamera2(0)

Hi, thanks for the report. I think the problem is actually that Pi Zeros are still running Bullseye which has not received the update to return the correct camera "Num". (Pi 4s and 5s get Bookwork, which has this change.) Would you be on a position to try out the 0_3_12_next branch in this repo? That's basically the Bullseye version with a few more recent patches.
Slightly longer term I believe the plan is to release a version of Bookworm for earlier Pis, so all this trouble will go away, but I'll have to check how that's progressing.

Hi, thanks for the reply. Actually, I came across the issue only on Bullseye systems.
I am working on a webserver, controlling Pi cameras (https://github.com/signag/raspi-cam-srv), which also supports Pi 5 with two cameras. It was straightforward to work around the missing "Num" for the Pi Zero and Pi Zero 2 systems.
Therefore, I did not try the suggested branch.
On the Pi 5, the "Num" value returned seems to be independent from the socket to which a camera is connected.
If only one camera is connected, it returns "Num" 0 in either socket. What are the rules if two cameras are connected? Is it possible to somehow know from the "Num" value which socket the camera is in?
I have seen (see https://github.com/signag/raspi-cam-srv/blob/main/docs/Information.md) that the "Location" parameter does not seem to distinguish the socket.

The problem users have had is that when the system boots, the order in which cameras are discovered is not fixed. So sometimes "cam0" can appear first, sometimes "cam1" can appear first, and this determines which libcamera regards as camera 0 or 1.
However, the camera 'Id' that you get does indicate which connector the camera is attached to. There should be a number after i2c@ which should identify it - the numbers will be different between Pi 5s and non-Pi 5s, but the same principle should hold, I believe. Using that you should be able work out the correct camera number to open. (On Bullseye images, where there's no "Num" field, I think you can just use the index of the camera in the list.)


Firefox: the form submission does not post selected options

(on Linux at least).
Options are selected using attr("selected", "selected) in tokenAdd, but on some browsers what gets really submitted are the options whose native DOM property selected = true.
I will try to propose a patch in my branch.

Please check 1494b5b6048cd20351582b1a9adf81498fe9a067

Hi thanks for your correction but it not work for me. The option element is remplaced by "true" value

Hmm let me check. It worked for me in Cr and Ff. I will provide my test files later today.
Thanks

Please check my test file here: https://github.com/gabrielzerbib/Tokenize/tree/master/test
I think it works.

I have do a little change for this issue, I have tested it on FF linux it's work perfectly.
P.S. your last message don't refere to this issue...

I think it was simply because the programmatic selection of an option must be made with .prop("selected", true) instead of attr( ).

According jQuery forum prop() doesn't work with selected attribute, I don't now why ! jQuery problem I think !


ansi chars in kosmos not ok

the ansi characters are not ok
when showing an object in shell should nicely show the colors

There's a problem with development_types branch, installation is broken (i cannot just checkout to it and start kosmos, it gives more errors, and @rkhamis mentioned that there're more changes to base classes).
on development, there's no problem with something like:

Need to know which branch and steps you made to get such output (also the terminal emulator used would help too).


Add bower_components assets from outside source folder?

Really love middleman and have some sites build in it ; only I have a really terrible time the last day with it. For the issue you want to add a bower_component asset from your asset pipeline manifest stylesheets.css for example.
It is not possible anyway to include any asset from outside source folder /bower_components like

I could copy the resources to the source/assets/stylesheets folder but that is not a working solution.
How could this be resolved?
Version 4 is not using sprockets anymore:
https://forum.middlemanapp.com/t/bower-and-stylus-unusable-with-version-4/2084

So Im using 4 so re-adding the sprockets like:
Gemfile:
source 'https://rubygems.org'

gem 'middleman', '>= 4.0.0'
gem 'middleman-livereload'
gem 'middleman-sprockets', '~> 4.0.0.rc'```

Then config.rb ( only top initialisation) :

activate :directory_indexes
activate :asset_hash
activate :sprockets
sprockets.append_path File.join(root, 'vendor')
set :css_dir,                     'assets/stylesheets'
set :js_dir,                      'assets/javascripts'
set :font_dir,                    'assets/fonts'
set :images_dir,                  'assets/images'

Then inside /site/source/assets/stylesheets/main.scss doing sometthing like:

@import "vendor/bootstrap/dist/css/bootstrap.css"
or
@import "bootstrap/dist/css/bootstrap.css"

Still fails no, bootstrap included.

How should this work? Anyone can please share some light in this?

I think that comes down to how sass works, since the stylesheet you're trying to import ends with .css sass leaves the import alone to act like a "vanilla" css import. If you're looking to include the contents of that file, you should be able to use a sprockets require:
In assets/stylesheets/main.css.scss
//= require 'bootstrap/dist/css/bootstrap.css'

No this is not working not with sass not .scss which is quite frustrating.
Such a simple case that worked before in 3 why is this such a pain in version 4?

Ok, I think I'll need some more info and hopefully we can get to the bottom of it. So, for what I do know (please correct me if I'm wrong):

using Middleman 4.x & Middleman::Sprockets 4.0.0.rc.x
activating sprockets & appending your bower path (vendor)
trying it import css out of the bower path into a file in source (source/assets/stylesheets/main.scss)

First step, you'll need to change main.scss to main.css.scss since implied extensions were removed in middleman 4.0.
After that, can you explain more about what's not working:

what behavior are you expecting to see?
what behavior are you seeing -- error messages, file not having expected content, etc

A public repo / gist with a minimal reproduction case would be super helpful, but I know those can be a pain sometimes. cheers

When using bootstrap and bower you should be including
"bootstrap-sass-official" : "",

This way you can import Bootstrap the correct way
// Bootstrap
//----------------------------------------------------------------------------//
@import "bootstrap-sass-official/assets/stylesheets/_bootstrap";

@stevenosloan using @import I believe does not use sprockets, but the included SASS gem? Is that correct?
The sprockets method would be
#=

But then you have the issue that variables are not carried as globals

@iwarner yeah, IIRC sprockets it just passes off some path stuff to the sass importer (if you're using sprockets). So I think using the bootstrap-sass is probably the way to go -- forgot about that, last I used boostrap it was less only (it's been a while ¯_(ツ)_/¯ )

I put together a quick project just to show how Bootstrap can be configured in MM4, completed with Glyphicon support: https://github.com/vvasabi/middleman4-bootstrap. Aside from the need to manually include and activate the middleman-sprockets extension, I didn’t find adding Bootstrap to be too different in MM4 than in 3. Hope that helps.

Thanks for pitching in, everyone.


ci: run a full lightwalletd sync from a close-to-tip zebrad

Motivation
On every PR push, if the zebrad state format hasn’t changed, we want to run a full lightwalletd sync from a close-to-tip zebrad, as a test. This test should take 30 minutes
Designs

Lightwalletd updates from zebrad in less than half an hour, so that part of the test can be  run on every PR change
This approach would use already generated disks from previous stateful disk generations job https://github.com/ZcashFoundation/zebra/blob/main/.github/workflows/test.yml#L213
A lightwalletd-test.yml might be appropriate from this point on and move specific lightwalletd tests here.

Related Work
https://github.com/ZcashFoundation/zebra/issues/3922

Is this the same as #3511?

@teor2345 I added #3511 as a dependency. Considering the test must be created (#3511) and then added to the CI (#3926)

This is a high priority, because it is on the critical path, and blocking other lightwalletd integration tests.


Add support for downloading with aria2 if it's already installed

By default, xcodes will use a URLSession to download the specified version. If aria2 (available in Homebrew with brew install aria2) is installed, either at /usr/local/bin/aria2c or at the path specified by the --aria2 flag, then it will be used instead. aria2 will use up to 16 connections to download Xcode 3-5x faster (based on a couple tests on my residential internet). If you have aria2 installed and would prefer to not use it, you can use the --no-aria2 flag.
aria2 downloads should retry up to 3 times if it fails in the middle, just like URLSession. Errors that cause aria2c to exit with a non-zero status code will show an appropriate error message.
In order to support both aria2 and URLSession, I had to change the download URLs. The previous URL prefix still works, but I was having issues with it when using aria2 for downloads. This new URL prefix matches whats shown in a browser at developer.apple.com/download/more, and works with both URLSession and aria2.
Closes #93
Testing
Download a bunch of xcodes while you're on this branch 😄
First, clone this repo if necessary and check out the PR branch:
git clone https://github.com/RobotsAndPencils/xcodes.git
cd xcodes
git checkout -b interstateone-aria2 master
git pull https://github.com/interstateone/xcodes.git aria2

You can test this new behaviour with your own account using a command like:
swift run xcodes install 12.1 gm seed # or some other version that you don't have already

You should try installing both with and without aria2, so:

without aria2c
with aria2c
with aria2c and --no-aria2 flag to use URLSession

You can see if aria2c is being used during install by opening Activity Monitor and filtering for aria2c in the top right.

Nice. It'd be nice to make aria2 a dependency in the Homebrew formula so that it'd be using it by default.

@thii That’s a good idea, I hadn’t thought of that! I’m leaning towards making it optional in the formula, at least to begin with, so that this is an incremental change.
 I think this might have been because of the versions of some formulas that I already had installed, and so not everyone will have this experience, but I’d like to see how it works for more people first.)

If we do want to make aria2 the default download option in the future I'd like to look into statically linking libaria2 instead of relying on the separate executable. I don't know if this would actually work yet, though 😄

I just noticed the installation slowness too. Let's keep it optional for now.

I tried adding depends_on to the formula, but it seems to only work when building from source, not when installing the bottle. I think it's okay if users have to brew install robotsandpencils/made/xcodes aria2 instead though.


Enabling Envoy gRPC Access Log Service (ALS)

This PR dependent on https://github.com/istio/api/pull/911. Similar to file access log, this extends pilot to enable envoy gRPC access log service which forwards access log to a central log inventory or APM system, for instance, Apache SkyWalking.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: hanahmily
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: greghanson
If they are not already assigned, you can assign the PR to them by writing /assign @greghanson in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

install/OWNERS
pilot/pkg/networking/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

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

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

/ok-to-test

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-unit-tests

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

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-unit-tests

prow/istio-presubmit.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-presubmit

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.

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-unit-tests

prow/istio-presubmit.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-presubmit

prow/release-test.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test release-test

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

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-unit-tests

prow/istio-presubmit.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-presubmit

prow/release-test.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test release-test

prow/e2e-mixer-no_auth.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test e2e-mixer-no_auth

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.

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-unit-tests

prow/istio-presubmit.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-presubmit

prow/release-test.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test release-test

prow/e2e-mixer-no_auth.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test e2e-mixer-no_auth

prow/e2e-dashboard.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test e2e-dashboard

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.

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-unit-tests

prow/istio-presubmit.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-presubmit

prow/release-test.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test release-test

prow/e2e-mixer-no_auth.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test e2e-mixer-no_auth

prow/e2e-dashboard.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

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.

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-unit-tests

prow/istio-presubmit.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-presubmit

prow/release-test.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test release-test

prow/e2e-mixer-no_auth.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test e2e-mixer-no_auth

prow/e2e-dashboard.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e-simpleTests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test e2e-simpleTests

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.

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-unit-tests

prow/istio-presubmit.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-presubmit

prow/release-test.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test release-test

prow/e2e-mixer-no_auth.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test e2e-mixer-no_auth

prow/e2e-dashboard.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e-simpleTests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test e2e-simpleTests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-pilot-e2e-envoyv2-v1alpha3

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.

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-unit-tests

prow/istio-presubmit.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-presubmit

prow/release-test.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test release-test

prow/e2e-mixer-no_auth.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test e2e-mixer-no_auth

prow/e2e-dashboard.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e-simpleTests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test e2e-simpleTests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-bookInfoTests-trustdomain.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test e2e-bookInfoTests-trustdomain

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.

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-unit-tests

prow/istio-presubmit.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-presubmit

prow/release-test.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test release-test

prow/e2e-mixer-no_auth.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test e2e-mixer-no_auth

prow/e2e-dashboard.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e-simpleTests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test e2e-simpleTests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-bookInfoTests-trustdomain.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test e2e-bookInfoTests-trustdomain

prow/e2e_pilotv2_auth_sds.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio_auth_sds_e2e

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.

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-unit-tests

prow/istio-presubmit.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-presubmit

prow/release-test.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test release-test

prow/e2e-mixer-no_auth.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test e2e-mixer-no_auth

prow/e2e-dashboard.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e-simpleTests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test e2e-simpleTests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-bookInfoTests-trustdomain.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test e2e-bookInfoTests-trustdomain

prow/e2e_pilotv2_auth_sds.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio_auth_sds_e2e

prow/istio-pilot-multicluster-e2e.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-pilot-multicluster-e2e

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.

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-unit-tests

prow/istio-presubmit.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-presubmit

prow/release-test.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test release-test

prow/e2e-mixer-no_auth.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test e2e-mixer-no_auth

prow/e2e-dashboard.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e-simpleTests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test e2e-simpleTests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-bookInfoTests-trustdomain.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test e2e-bookInfoTests-trustdomain

prow/e2e_pilotv2_auth_sds.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio_auth_sds_e2e

prow/istio-pilot-multicluster-e2e.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-pilot-multicluster-e2e

prow/istio-integ-local-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-integ-local-tests

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

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-unit-tests

prow/istio-presubmit.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-presubmit

prow/release-test.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test release-test

prow/e2e-mixer-no_auth.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test e2e-mixer-no_auth

prow/e2e-dashboard.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e-simpleTests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test e2e-simpleTests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-bookInfoTests-trustdomain.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test e2e-bookInfoTests-trustdomain

prow/e2e_pilotv2_auth_sds.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio_auth_sds_e2e

prow/istio-pilot-multicluster-e2e.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-pilot-multicluster-e2e

prow/istio-integ-local-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-integ-k8s-tests

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

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: hanahmily
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: howardjohn
If they are not already assigned, you can assign the PR to them by writing /assign @howardjohn in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

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

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/e2e-bookInfoTests-trustdomain.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test e2e-bookInfoTests-trustdomain

prow/e2e_pilotv2_auth_sds.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio_auth_sds_e2e

prow/istio-pilot-multicluster-e2e.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-pilot-multicluster-e2e

prow/istio-integ-local-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-integ-k8s-tests

prow/integ-pilot-k8s-presubmit-tests.sh
788d6d45cbbdaa16c78150dfdc696253b458ca2f
link
/test integ-pilot-k8s-presubmit-tests-master

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.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: hanahmily, rshriram
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [rshriram]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

New changes are detected. LGTM label has been removed.

/lgtm

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: hanahmily, rshriram
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [rshriram]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

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

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-integ-k8s-tests

prow/e2e-simpleTests.sh
4dfb1a415a2e40bef16f57a47ff5f05c62af94a1
link
/test e2e-simpleTests-master

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.

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

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-integ-k8s-tests

prow/e2e-simpleTests.sh
4dfb1a415a2e40bef16f57a47ff5f05c62af94a1
link
/test e2e-simpleTests-master

prow/integ-pilot-k8s-presubmit-tests.sh
4dfb1a415a2e40bef16f57a47ff5f05c62af94a1
link
/test integ-pilot-k8s-presubmit-tests-master

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 e2e-simpleTests-master

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

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-integ-k8s-tests

prow/integ-pilot-k8s-presubmit-tests.sh
4dfb1a415a2e40bef16f57a47ff5f05c62af94a1
link
/test integ-pilot-k8s-presubmit-tests-master

prow/e2e-simpleTests.sh
4dfb1a415a2e40bef16f57a47ff5f05c62af94a1
link
/test e2e-simpleTests-master

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 e2e-simpleTests-master

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

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-integ-k8s-tests

prow/integ-pilot-k8s-presubmit-tests.sh
4dfb1a415a2e40bef16f57a47ff5f05c62af94a1
link
/test integ-pilot-k8s-presubmit-tests-master

prow/e2e-simpleTests.sh
4dfb1a415a2e40bef16f57a47ff5f05c62af94a1
link
/test e2e-simpleTests-master

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

@hanahmily needs rebase

New changes are detected. LGTM label has been removed.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: hanahmily, rshriram
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

install/OWNERS [rshriram]
pilot/pkg/networking/OWNERS [rshriram]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

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

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-integ-k8s-tests

prow/integ-pilot-k8s-presubmit-tests.sh
4dfb1a415a2e40bef16f57a47ff5f05c62af94a1
link
/test integ-pilot-k8s-presubmit-tests-master

prow/e2e-simpleTests.sh
4dfb1a415a2e40bef16f57a47ff5f05c62af94a1
link
/test e2e-simpleTests-master

prow/istio-unit-tests.sh
877b3bbb6ebdff463ddfb79b6418421a5bbc6ce7
link
/test istio-unit-tests-master

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.

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

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-integ-k8s-tests

prow/integ-pilot-k8s-presubmit-tests.sh
4dfb1a415a2e40bef16f57a47ff5f05c62af94a1
link
/test integ-pilot-k8s-presubmit-tests-master

prow/e2e-simpleTests.sh
4dfb1a415a2e40bef16f57a47ff5f05c62af94a1
link
/test e2e-simpleTests-master

prow/istio-unit-tests.sh
877b3bbb6ebdff463ddfb79b6418421a5bbc6ce7
link
/test istio-unit-tests-master

prow/istio-presubmit.sh
877b3bbb6ebdff463ddfb79b6418421a5bbc6ce7
link
/test istio-presubmit-master

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.

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

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-integ-k8s-tests

prow/integ-pilot-k8s-presubmit-tests.sh
4dfb1a415a2e40bef16f57a47ff5f05c62af94a1
link
/test integ-pilot-k8s-presubmit-tests-master

prow/e2e-simpleTests.sh
4dfb1a415a2e40bef16f57a47ff5f05c62af94a1
link
/test e2e-simpleTests-master

prow/istio-unit-tests.sh
877b3bbb6ebdff463ddfb79b6418421a5bbc6ce7
link
/test istio-unit-tests-master

prow/istio-presubmit.sh
877b3bbb6ebdff463ddfb79b6418421a5bbc6ce7
link
/test istio-presubmit-master

prow/integ-telemetry-local-presubmit-tests.sh
877b3bbb6ebdff463ddfb79b6418421a5bbc6ce7
link
/test integ-telemetry-local-presubmit-tests-master

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.

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

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-integ-k8s-tests

prow/integ-pilot-k8s-presubmit-tests.sh
4dfb1a415a2e40bef16f57a47ff5f05c62af94a1
link
/test integ-pilot-k8s-presubmit-tests-master

prow/e2e-simpleTests.sh
4dfb1a415a2e40bef16f57a47ff5f05c62af94a1
link
/test e2e-simpleTests-master

prow/istio-unit-tests.sh
877b3bbb6ebdff463ddfb79b6418421a5bbc6ce7
link
/test istio-unit-tests-master

prow/istio-presubmit.sh
877b3bbb6ebdff463ddfb79b6418421a5bbc6ce7
link
/test istio-presubmit-master

prow/integ-telemetry-local-presubmit-tests.sh
877b3bbb6ebdff463ddfb79b6418421a5bbc6ce7
link
/test integ-telemetry-local-presubmit-tests-master

prow/integ-security-local-presubmit-tests.sh
877b3bbb6ebdff463ddfb79b6418421a5bbc6ce7
link
/test integ-security-local-presubmit-tests-master

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.

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

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-integ-k8s-tests

prow/integ-pilot-k8s-presubmit-tests.sh
4dfb1a415a2e40bef16f57a47ff5f05c62af94a1
link
/test integ-pilot-k8s-presubmit-tests-master

prow/e2e-simpleTests.sh
4dfb1a415a2e40bef16f57a47ff5f05c62af94a1
link
/test e2e-simpleTests-master

prow/istio-unit-tests.sh
877b3bbb6ebdff463ddfb79b6418421a5bbc6ce7
link
/test istio-unit-tests-master

prow/istio-presubmit.sh
877b3bbb6ebdff463ddfb79b6418421a5bbc6ce7
link
/test istio-presubmit-master

prow/integ-telemetry-local-presubmit-tests.sh
877b3bbb6ebdff463ddfb79b6418421a5bbc6ce7
link
/test integ-telemetry-local-presubmit-tests-master

prow/integ-security-local-presubmit-tests.sh
877b3bbb6ebdff463ddfb79b6418421a5bbc6ce7
link
/test integ-security-local-presubmit-tests-master

prow/integ-pilot-local-presubmit-tests.sh
877b3bbb6ebdff463ddfb79b6418421a5bbc6ce7
link
/test integ-pilot-local-presubmit-tests-master

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.

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

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-integ-k8s-tests

prow/integ-pilot-k8s-presubmit-tests.sh
4dfb1a415a2e40bef16f57a47ff5f05c62af94a1
link
/test integ-pilot-k8s-presubmit-tests-master

prow/e2e-simpleTests.sh
4dfb1a415a2e40bef16f57a47ff5f05c62af94a1
link
/test e2e-simpleTests-master

prow/istio-unit-tests.sh
877b3bbb6ebdff463ddfb79b6418421a5bbc6ce7
link
/test istio-unit-tests-master

prow/istio-presubmit.sh
877b3bbb6ebdff463ddfb79b6418421a5bbc6ce7
link
/test istio-presubmit-master

prow/integ-telemetry-local-presubmit-tests.sh
877b3bbb6ebdff463ddfb79b6418421a5bbc6ce7
link
/test integ-telemetry-local-presubmit-tests-master

prow/integ-security-local-presubmit-tests.sh
877b3bbb6ebdff463ddfb79b6418421a5bbc6ce7
link
/test integ-security-local-presubmit-tests-master

prow/integ-pilot-local-presubmit-tests.sh
877b3bbb6ebdff463ddfb79b6418421a5bbc6ce7
link
/test integ-pilot-local-presubmit-tests-master

prow/integ-mixer-local-presubmit-tests.sh
877b3bbb6ebdff463ddfb79b6418421a5bbc6ce7
link
/test integ-mixer-local-presubmit-tests-master

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.

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

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-integ-k8s-tests

prow/integ-pilot-k8s-presubmit-tests.sh
4dfb1a415a2e40bef16f57a47ff5f05c62af94a1
link
/test integ-pilot-k8s-presubmit-tests-master

prow/e2e-simpleTests.sh
4dfb1a415a2e40bef16f57a47ff5f05c62af94a1
link
/test e2e-simpleTests-master

prow/istio-unit-tests.sh
877b3bbb6ebdff463ddfb79b6418421a5bbc6ce7
link
/test istio-unit-tests-master

prow/istio-presubmit.sh
877b3bbb6ebdff463ddfb79b6418421a5bbc6ce7
link
/test istio-presubmit-master

prow/integ-telemetry-local-presubmit-tests.sh
877b3bbb6ebdff463ddfb79b6418421a5bbc6ce7
link
/test integ-telemetry-local-presubmit-tests-master

prow/integ-security-local-presubmit-tests.sh
877b3bbb6ebdff463ddfb79b6418421a5bbc6ce7
link
/test integ-security-local-presubmit-tests-master

prow/integ-pilot-local-presubmit-tests.sh
877b3bbb6ebdff463ddfb79b6418421a5bbc6ce7
link
/test integ-pilot-local-presubmit-tests-master

prow/integ-mixer-local-presubmit-tests.sh
877b3bbb6ebdff463ddfb79b6418421a5bbc6ce7
link
/test integ-mixer-local-presubmit-tests-master

prow/integ-istioctl-local-presubmit-tests.sh
877b3bbb6ebdff463ddfb79b6418421a5bbc6ce7
link
/test integ-istioctl-local-presubmit-tests-master

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.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: hanahmily, rshriram
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [rshriram]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/lgtm

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: hanahmily, rshriram
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [rshriram]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

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

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-integ-k8s-tests

prow/integ-pilot-k8s-presubmit-tests.sh
4dfb1a415a2e40bef16f57a47ff5f05c62af94a1
link
/test integ-pilot-k8s-presubmit-tests-master

prow/e2e-simpleTests.sh
4dfb1a415a2e40bef16f57a47ff5f05c62af94a1
link
/test e2e-simpleTests-master

prow/istio-unit-tests.sh
ce40981baa5d4cf6a7bb841773e90b2885533a53
link
/test istio-unit-tests-master

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.

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

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-integ-k8s-tests

prow/integ-pilot-k8s-presubmit-tests.sh
4dfb1a415a2e40bef16f57a47ff5f05c62af94a1
link
/test integ-pilot-k8s-presubmit-tests-master

prow/e2e-simpleTests.sh
4dfb1a415a2e40bef16f57a47ff5f05c62af94a1
link
/test e2e-simpleTests-master

prow/istio-unit-tests.sh
ce40981baa5d4cf6a7bb841773e90b2885533a53
link
/test istio-unit-tests-master

prow/integ-framework-local-presubmit-tests.sh
ce40981baa5d4cf6a7bb841773e90b2885533a53
link
/test integ-framework-local-presubmit-tests-master

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 istio-unit-tests-master

/test integ-pilot-k8s-presubmit-tests-master

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

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-integ-k8s-tests

prow/integ-pilot-k8s-presubmit-tests.sh
4dfb1a415a2e40bef16f57a47ff5f05c62af94a1
link
/test integ-pilot-k8s-presubmit-tests-master

prow/istio-unit-tests.sh
ce40981baa5d4cf6a7bb841773e90b2885533a53
link
/test istio-unit-tests-master

prow/integ-framework-local-presubmit-tests.sh
ce40981baa5d4cf6a7bb841773e90b2885533a53
link
/test integ-framework-local-presubmit-tests-master

prow/e2e-simpleTests.sh
ce40981baa5d4cf6a7bb841773e90b2885533a53
link
/test e2e-simpleTests-master

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.

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

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-integ-k8s-tests

prow/integ-pilot-k8s-presubmit-tests.sh
4dfb1a415a2e40bef16f57a47ff5f05c62af94a1
link
/test integ-pilot-k8s-presubmit-tests-master

prow/istio-unit-tests.sh
ce40981baa5d4cf6a7bb841773e90b2885533a53
link
/test istio-unit-tests-master

prow/integ-framework-local-presubmit-tests.sh
ce40981baa5d4cf6a7bb841773e90b2885533a53
link
/test integ-framework-local-presubmit-tests-master

prow/e2e-simpleTests.sh
ce40981baa5d4cf6a7bb841773e90b2885533a53
link
/test e2e-simpleTests-master

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
ce40981baa5d4cf6a7bb841773e90b2885533a53
link
/test istio-pilot-e2e-envoyv2-v1alpha3-master

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.

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

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-integ-k8s-tests

prow/istio-unit-tests.sh
ce40981baa5d4cf6a7bb841773e90b2885533a53
link
/test istio-unit-tests-master

prow/integ-framework-local-presubmit-tests.sh
ce40981baa5d4cf6a7bb841773e90b2885533a53
link
/test integ-framework-local-presubmit-tests-master

prow/e2e-simpleTests.sh
ce40981baa5d4cf6a7bb841773e90b2885533a53
link
/test e2e-simpleTests-master

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
ce40981baa5d4cf6a7bb841773e90b2885533a53
link
/test istio-pilot-e2e-envoyv2-v1alpha3-master

prow/e2e_pilotv2_auth_sds.sh
ce40981baa5d4cf6a7bb841773e90b2885533a53
link
/test istio_auth_sds_e2e-master

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.

New changes are detected. LGTM label has been removed.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: hanahmily, rshriram
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: geeknoid
If they are not already assigned, you can assign the PR to them by writing /assign @geeknoid in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [rshriram]
pkg/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

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

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-integ-k8s-tests

prow/e2e-simpleTests.sh
ce40981baa5d4cf6a7bb841773e90b2885533a53
link
/test e2e-simpleTests-master

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
ce40981baa5d4cf6a7bb841773e90b2885533a53
link
/test istio-pilot-e2e-envoyv2-v1alpha3-master

prow/e2e_pilotv2_auth_sds.sh
ce40981baa5d4cf6a7bb841773e90b2885533a53
link
/test istio_auth_sds_e2e-master

prow/istio-unit-tests.sh
594fb6ac3adaf33cc914d923193e7eb3cd0d347b
link
/test istio-unit-tests-master

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.

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

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-integ-k8s-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
ce40981baa5d4cf6a7bb841773e90b2885533a53
link
/test istio-pilot-e2e-envoyv2-v1alpha3-master

prow/e2e_pilotv2_auth_sds.sh
ce40981baa5d4cf6a7bb841773e90b2885533a53
link
/test istio_auth_sds_e2e-master

prow/istio-unit-tests.sh
594fb6ac3adaf33cc914d923193e7eb3cd0d347b
link
/test istio-unit-tests-master

prow/e2e-simpleTests.sh
594fb6ac3adaf33cc914d923193e7eb3cd0d347b
link
/test e2e-simpleTests-master

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.

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

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
b0e59d87d86f727f5fb578b02b4c032973bc9542
link
/test istio-integ-k8s-tests

prow/e2e-simpleTests.sh
31ec765ed6e8174b9aaab5496d87f06b379502c7
link
/test e2e-simpleTests-master

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 e2e-simpleTests-master

/lgtm

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: hanahmily, rshriram
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: geeknoid
If they are not already assigned, you can assign the PR to them by writing /assign @geeknoid in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [rshriram]
pkg/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

All CLAs are signed, manually approving.


Steering override (Like other OP cars)

Please try this and give some feedback, given I think OP way you can override anytime is FAR better than AP this is definitely how I prefer it work.. But the difference w/ AP will seem abnormal at first to anyone who is used to AP.. I think they'll quickly like it better.

I run this pull request on my car. Its a step in the right direction IMHO, but not ready for prime time. I had multiple event of engage-disengage-engage-disengage at 0.5 sec intervals, like "fighting" the system. Its not really fighting as the EPAS is super easy on the user and the user always have the last word, but it was kind of not working well in some conditions. Also, for lane changes I fell like its much better with signals disabling temporarily. I mean, its not smooth for passenger compared of what's in the current branch.
One idea I had is trying to smooth out re-engagement but temporarily reducing Kp/Ki gains for a second after re-engaging. Something like that would helps.

Making a new request, closing this one.


$ thyme dep prompting to install watch even though it is already installed

I have watch installed and enabled privileges for iTerm and Terminal. Still getting the following on running thyme dep
Ankits-MacBook-Pro:bin ankit$ thyme dep

You will need the OSX 'watch' command. With Homebrew installed, in your command line enter "brew install watch". You will also need to enable privileges for "Terminal" in System Preferences > Security & Privacy > Privacy > Accessibility.
See https://support.apple.com/en-us/HT202802 for details.

Ankits-MacBook-Pro:bin ankit$ brew install watch
Warning: watch-3.3.11 already installed

You don't need watch installed.
https://github.com/sourcegraph/thyme/commit/734a92b6cfb18c959936cdef8790bbb7920f89f6


Create get-in-touch.svelte component

This component will have a title,

get in touch!

and a paragraph...

Have any questions for us?  Want to work with us?  Just want to say hi? Whatever it is, feel free to contact us!  Send us an email by filling out the form below, and we’ll have a representative get back to you as soon as possible. Don’t worry, we’re friendly! 😊

Additionally, the component will manage a simple form with fields for name, email, topic, and message.

Here is the code of the contact form from the previous website: https://github.com/CSUF-ACM/acmwebsite/blob/master/src/components/ContactForm/index.js. Here, the form data is being sent to an endpoint (https://script.google.com/macros/s/AKfycbwIQ-9G6HEg3ap_yyjPqR3ka2Q1c5KgSsSfO-kn/exec) that is either still functional or not functional anymore. This fact should be verified before this task is begun.

Resolved by #66 🎉


Installation error with Hatchling v1.22

The latest update of Hatchling causes the following installation error:
Processing /home/runner/work/pytest-cmake/pytest-cmake
  Installing build dependencies: started
  Installing build dependencies: finished with status 'done'
  Getting requirements to build wheel: started
  Getting requirements to build wheel: finished with status 'error'
  error: subprocess-exited-with-error

  × Getting requirements to build wheel did not run successfully.
  │ exit code: 1
  ╰─> [32 lines of output]
      Traceback (most recent call last):
        File "/opt/hostedtoolcache/Python/3.11.8/x64/lib/python3.11/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in <module>
          main()
        File "/opt/hostedtoolcache/Python/3.11.8/x64/lib/python3.11/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main
          json_out['return_val'] = hook(**hook_input['kwargs'])
                                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "/opt/hostedtoolcache/Python/3.11.8/x64/lib/python3.11/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 1[18](https://github.com/buddly27/pytest-cmake/actions/runs/8317355309/job/22758020884#step:7:19), in get_requires_for_build_wheel
          return hook(config_settings)
                 ^^^^^^^^^^^^^^^^^^^^^
        File "/tmp/pip-build-env-bb2wsyur/overlay/lib/python3.11/site-packages/hatchling/build.py", line 44, in get_requires_for_build_wheel
          return builder.config.dependencies
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "/tmp/pip-build-env-bb2wsyur/overlay/lib/python3.11/site-packages/hatchling/builders/config.py", line 656, in dependencies
          for dependency in self.dynamic_dependencies:
                            ^^^^^^^^^^^^^^^^^^^^^^^^^
        File "/opt/hostedtoolcache/Python/3.11.8/x64/lib/python3.11/functools.py", line 1001, in __get__
          val = self.func(instance)
                ^^^^^^^^^^^^^^^^^^^
        File "/tmp/pip-build-env-bb2wsyur/overlay/lib/python3.11/site-packages/hatchling/builders/config.py", line 671, in dynamic_dependencies
          build_hook = build_hook_cls(
                       ^^^^^^^^^^^^^^^
        File "/tmp/pip-build-env-bb2wsyur/overlay/lib/python3.11/site-packages/hatchling/builders/hooks/custom.py", line 35, in __new__
          hook_class = load_plugin_from_script(path, build_script, BuildHookInterface, 'build_hook')
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "/tmp/pip-build-env-bb2wsyur/overlay/lib/python3.11/site-packages/hatchling/plugin/utils.py", line 18, in load_plugin_from_script
          spec.loader.exec_module(module)  # type: ignore
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "<frozen importlib._bootstrap_external>", line 940, in exec_module
        File "<frozen importlib._bootstrap>", line [24](https://github.com/buddly27/pytest-cmake/actions/runs/8317355309/job/22758020884#step:7:25)1, in _call_with_frames_removed
        File "/home/runner/work/pytest-cmake/pytest-cmake/build_config.py", line 2, in <module>
          import pytest
      ModuleNotFoundError: No module named 'pytest'
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.

It seems to be because of the dynamic pytest dependency, which might need to be handled differently:
https://github.com/pypa/hatch/pull/1314

Fixed via 6aca5ca


Issue 4174 - Template interface functions not allowed, making operator overloads difficult

Issue 4174 - Template interface functions not allowed, making operator overloads difficult
The lifting restriction banning final and static members in interfaces should also apply to template functions.
http://d.puremagic.com/issues/show_bug.cgi?id=4174

Please also add an associated pull request to the language specification.
At the bottom of:
http://www.d-programming-language.org/template.html#Constraint

Shouldn't the test case be a complete one based on the previous xfail test, plus override, checking template specializations and whatever.

If you've got more test cases you'd like in here I'd be happy to add them to the pull request.  Given that this patch loosens a restriction, I'm not particularly concerned.


[Feature] Cloud Rule pages (such as Manager Correlation) should describe how to use the rules, not just how to code one.

Is your feature request related to a problem? Please describe.
ManagerCorrelation rules are immensely valuable, however the Rule page only shows how to write a rule.
it does not have reference to how to tie it to the managerCorrelationRule field on a source
it does not show what has to be done within the tenant to utilize the rule
Describe the solution you'd like. A clear and concise description of what to do and where to do it, end to end, to utilize a cloud rule for its intended purpose

Hi Stephen, I am closing this issue as we have plans to improve the documentation around rules, but this particular issue is something that is difficult to track and understand when it is "complete". In the meantime, if you have a solid implementation of manager correlation that you could share publicly, I think we would like to be able to add that to the documentation.


chore(ci): validate lockfile

npm ci installs based on package-lock.json only, which can become out-of-date (somehow) with respect to a package.json.  If npm ls after an npm ci fails with a non-zero exit code, this is why.

Current dependencies on/for this PR:

main

PR #950

PR #951   👈

This stack of pull requests is managed by Graphite.

I've consolidated the lockfile validation into the lint job, and split up the steps:

lint sources
lint deps
lint lockfile (this change)


Add python-dev and python3-dev to prerequisites

Remedies a problem found by @hsaliak.

Updated; please rereview and merge.


added upgradation command for mesheryctl using brew

Signed-off-by: ashiscs<EMAIL_ADDRESS>

@leecalcote is this okay?


fix leaderboard monthly and aggregate display table

fix for leaderboard monthly filter not working
aggregate table rather than result per row

This change is

Current Version


Wrong flag "supportsIePointer" on Chrome

https://github.com/noraesae/perfect-scrollbar/blob/master/src/js/lib/helper.js#L82
In chrome the flag is true
console.log(window.navigator.msMaxTouchPoints)
//undefined
console.log(window.navigator.msMaxTouchPoints !== null)
//true

Fixed in a81208a2ea72b4d903d852d1aecc40252a42c5b0. Thanks!