feat: filter contract logs for events

Description of changes
Avoid No Matching event by only calling parseLog on the logs that correspond to the current contract called.
Notes:
I'm not sure if this is the best solution for the problem, ideally we should return the logs unparsed but that can be found in the transaction itself

Just stumbled across this as having the same error. Nice one.

For anyone else arriving here, this error was introduced in the most recent relase (0.4.4), so if you fix to version 0.4.3 you're OK.

Maybe we should pass the filtering function as argument to useContractFunction
useContractFunction(..., filteringFunction?: (e:any) => boolean)

So that developers can have more control and as default it can be left filtering address of contract

More than a filtering function I would say it's a parse function, where manually they read the logs and parse the event with the corresponding contract Abi, this could be an empty function to get the raw logs


VoiceOver support

Hi, it would be great to add support for VoiceOver.
Currently VoiceOver reads all the text in an ActiveLabel, but urls, mentions and hashtags are skipped from VoiceOver focus.
A solution would be to perform a whole text reading, then VoiceOver focuses on every actionable elements (urls, mentions and hashtags).

Hi, any updates?

This sounds like a nice feature, however, I don't have the skill to add/fix this. If there is any PR I can merge for the next release.


[AzureMonitorExporter] refactor OfflineStorageTests to use mock file storage

Refactor the OfflineStorageTests to not rely on FileStorage.
Currently, these tests take longer to run than all other tests combined.
(15 tests x 10 sec wait each = 150 sec = 2.5 minutes)
This change replaces the FileStorage with an in-memory mock storage and eliminates the Task.Delay
(2.6 seconds)

@vishweshbankwar, we may want to hold off on this change until after your changes to the PersistantStorage package
However, taking this change now would massively improve the time to run tests locally.

API change check for Azure.Monitor.OpenTelemetry.Exporter
API changes are not detected in this pull request for Azure.Monitor.OpenTelemetry.Exporter

This approach looks good to me, we need to validate transmitter._storage.GetBlob().Lease(1000).Delete() is needed.


Allow file upload of native single images

Waiting for this https://github.com/encord-team/cord-backend/pull/962 to roll out before merging.


22w07a stuff

Biome tag stuff + TicksInWrongChunkFix datafix + lots of bits and pieces, mostly just lambda parameters

Some conflicts here, sorry about that 👍


First release version

First release version of PaladinsLive. A simple multiplatform Paladins game tracker.
Features:

User search
Favorites
User live match statistics
User match history

Looks like live match data and match history is not properly received in datahandler class.
Clicking on any element in the searchResults will add them to favorites (unintended when clicking Live or History)


[ci] Workaround JDK 18 spotbugs issue.

Change-Id: I4c15161fdfb91fc164af05137ef69fbc2acadd62
Description
Brief description of what this PR is about

If this change is a backward incompatible change, why must this change be made?
Interesting edge cases to note here

Codecov Report

Merging #1880 (d044d81) into master (bb5073f) will decrease coverage by 2.09%.
The diff coverage is 66.45%.

:exclamation: Current head d044d81 differs from pull request most recent head 5ef86e9. Consider uploading reports for the commit 5ef86e9 to get more accurate results

@@             Coverage Diff              @@
##             master    #1880      +/-   ##
============================================
- Coverage     72.08%   69.99%   -2.10%
- Complexity     5126     5585     +459
============================================
  Files           473      530      +57
  Lines         21970    24624    +2654
  Branches       2351     2679     +328
============================================
+ Hits          15838    17236    +1398
- Misses         4925     6073    +1148
- Partials       1207     1315     +108

Impacted Files
Coverage Δ

api/src/main/java/ai/djl/modality/cv/Image.java
69.23% <ø> (-4.11%)
:arrow_down:

...rc/main/java/ai/djl/modality/cv/MultiBoxPrior.java
76.00% <ø> (ø)

...rc/main/java/ai/djl/modality/cv/output/Joints.java
71.42% <ø> (ø)

.../main/java/ai/djl/modality/cv/output/Landmark.java
100.00% <ø> (ø)

...main/java/ai/djl/modality/cv/output/Rectangle.java
72.41% <0.00%> (ø)

...i/djl/modality/cv/translator/BigGANTranslator.java
21.42% <0.00%> (-5.24%)
:arrow_down:

...odality/cv/translator/BigGANTranslatorFactory.java
33.33% <0.00%> (+8.33%)
:arrow_up:

...nslator/InstanceSegmentationTranslatorFactory.java
14.28% <0.00%> (-3.90%)
:arrow_down:

.../cv/translator/SemanticSegmentationTranslator.java
0.00% <0.00%> (ø)

.../cv/translator/StyleTransferTranslatorFactory.java
40.00% <ø> (ø)

... and 428 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Updated the counters config.

Updated counters config to resolve issue #126.

Merging into dev.

:+1:


Use pyspcwebgw for SPC component

Description:
Fixes SPC alarm system support that has been broken for a number of releases. Major parts of the code has been moved to an API specific PyPi package (pyspcwebgw).
Related issue (if applicable): fixes #13306
Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass

If the code communicates with devices, web services, or third-party tools:

[x] New dependencies have been added to the REQUIREMENTS variable ([example][ex-requir]).
[x] New dependencies are only imported inside functions that use them ([example][ex-import]).
[x] New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.
[x] Tests have been added to verify that the new code works.

Fix the conflict and we can merge.

@MartinHjelmare conflicts fixed, but don't know what's up with the cla-bot?

I have a problem.
I have updated to 0.79.0
When I run the SPC component the History graph from sensors and switches do not work.
If I remove SPC from the components the History graph works again.
The history graph become emty with no updates.


update asyncpg example

Why was the connection pool code removed?

@nszceta because it doesn't make sense to open a connection pool for a single connection.

If you can keep the same connection pool open and use that (which is possible by attaching it to the request.app attribute), then it would make sense to use it.

@r0fls what are your thoughts regarding https://github.com/channelcat/sanic/issues/540 ?


Tensorflow finding only 9gb of free memory but 11gb total for gtx 1080 ti GPU

We found on both Windows 10 and Linux machines that Tensorflow will only find 9gb of the 11gb available for GTX 1080 ti GPUs from both EVGA and MSI.  Having trouble finding a fix - does anyone know why it is doing this and how to fix it so it can get access to all the memory?

I'm getting the same issue when investigating in CUDA directly, so it's not a Tensorflow issue.


Coudnt connect to internet issue

Hey.iam testing out this in a lan enviroment.after like 5 or 6 attempts it displays "we coudnt connect to indtagram make sure you are connected to internet"
Any fix for it

I also have this problem. I created a site on the internet for testing purposes. Everything is working normally but after a few days I get this problem. I can't find where the problem is. I installed the tool on Ubuntu Server 20.04 LTS. If anyone can help, I will ask another question. I really need help.

+++  I have same problem, help pls

or give  link on post


Work with FOREX but volume error with US500

Hello, thank you for the library.
I tried the lib with EURUSD which worked fine.
However I ran into this weird volume error with US500.
My code:
symbol = "US500"
volume = 0.1 # order size
price = api.quote()
price = np.round(price['US500']['bid'] + 0.002, 1)
id = api.buyLimit(symbol, volume, price)
And I received this as error.
ERROR:root:Order volume 10000.00 is bigger than maxVolume=100.00.
Which is not the volume I entered clearly.
Please help.
Thank you very much.

Hello, thank you for the library.
I tried the lib with EURUSD which worked fine.
However I ran into this weird volume error with US500.
My code: symbol = "US500" volume = 0.1 # order size price = api.quote() price = np.round(price['US500']['bid'] + 0.002, 1)
id = api.buyLimit(symbol, volume, price)
And I received this as error.
ERROR:root:Order volume 10000.00 is bigger than maxVolume=100.00.
Which is not the volume I entered clearly.
Please help.
Thank you very much.

digit point contract size 0.001

HI, This error is because of it multiplying the volume with 10000 for forex calculation. Changing it in the main library fix.py I was able to solve the issue.

HI, This error is because of it multiplying the volume with 10000 for forex calculation. Changing it in the main library fix.py I was able to solve the issue.

As this project was focused on Forex, it presents these issues. However, if necessary, feel free to submit a pull request for changes. We appreciate your contribution.


unknown characters exception

at the moment unknown characters (like # -) cause an exception that does not get catched
either catch it or dont throw it
in wildcards it should all characters

fixed


5 -  As a player, when not being in a game, I want to be able to get a visual overview of the  leaderboard showing the best players and their stats. Also I want to see the stats about my own  games

[x] The leaderboard can not be accessed while the player is in-game
[x] The leaderboard keeps track of the ELO of all players
[x] The leaderboard shows the top 5 players in order
[x] A player can search for other players to get an overview of their stats
[x] A player can click on another player to inspect their profile

92c927dcee0f966531c192ea4c9ee6a9443eed90


Filter empty string in comment

The comment parser sometimes include empty string as a command line argument, which breaks python's argparser in request_pr_exp.py.
This PR removes empty strings from the command parsed from the comment.

/gcbrun exp -f    -n dg

Report looks good:
https://llm-exp.oss-fuzz.com/Result-reports/ofg-pr/2024-07-11-466-dg-comparison/index.html

TBR.


Translation the newly added message keys

See 5d98b7d for the set of new keys to be translated (some of these (login-*) are actually not new, but we didn't have them in our message files).
Note that, since https://github.com/ufal/clarin-dspace/issues/662 was added in 2017.04, the JS messages are now all stored in a dedicated JS file, analogous to the XML file.
The keys that I've now added (both XML and JS) are precisely the ones that the cs message files contain which the sl message files lacked, as identified with python utilities/project_helpers/scripts/check-message-translations.py cs sl (see my https://github.com/ufal/clarin-dspace/wiki/Language-localisation for rough documentation).

This has been translated and is mounted on CLARIN.SI repo.


Baseline MPC algorithm code is mising

Dear Jie Feng, i am thankful to you for providing the code required for the implementation of related paper.  However upon downloading the repository, i could not find the code for recreation of Baseline MPC algorithm. If you may provide this code as well, it will help me to conduct my research. I will cite your paper in my publication. Thanks for consideration & time.

Thank you for the comment. Our method is a model-free method, as a result, a comparison with MPC is not specifically of interest. Unfortunately, I do not have access to the MPC code now.


Connection failed: Invalid connector type: l2cap

Hello Ken,
What are the other CONNECTION_TYPE values other than "rfcomm"  for connect() function?
From the documentation (https://kenjdavidson.com/react-native-bluetooth-classic/react-native/rn-bluetooth-device/)
its only specified about rfcomm. It would really help what are the values to be given for OBEX and L2CAP. if I give "obex" or "obex", then i get this error - Connection failed: Invalid connector type: l2cap or Connection failed: Invalid connector type: l2cap  respectively

Have you read the documentation?
There are no other types provided by default, only RFCOMM.  I redesigned the library to make it extendable.  You can write your own:

DeviceAcceptor
DeviceConnector
DeviceConnection

and provide them to the Bluetooth module so that you can do anything you want, without having to re-write or modify the actual library itself.
There are examples of doing so with the ByteArrayDeviceConnectionImpl.


Configuration using environment variables doesn't allow setting namespace

Describe the bug
How do we set the namespace when configuring using environment variables?
I'm looking at this portion: https://github.com/MrZoidberg/VaultSharp.Extensions.Configuration/blob/master/Source/VaultSharp.Extensions.Configuration/VaultConfigurationExtensions.cs#L66, and it doesn't look like namespace is set from environment variables?

@oyetteramirez What's your use case for namespaces in environment variables?


chore: bump to v0.12.2

cc @QuadnucYard PTAL ♥

Better examples:
#{
  let x = 1
/* Block comment
      that
          spans
 multiple
     lines
  */
}

#{
  let x = 1   /* Attached block comment
      that
          spans
 multiple
     lines
  */
}

will be formatted to
#{
  let x = 1
  /* Block comment
       that
           spans
  multiple
      lines
   */
}

#{
  let x = 1 /* Attached block comment
                 that
                     spans
            multiple
                lines
             */
}


Allow flexible folder names and trimming test words from image names

These changes will be introduced soon in the main library, but we need them already.
Original pull request here: https://github.com/uber/ios-snapshot-test-case/pull/14

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.alexis.santos.perez seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Transmite Eddystone URI and UID data simultaneously

Hi, I'm playing with Eddystone examples for nRF 8001 and I saw that in the current code you can transmit only one type of payload. How would I accomplish transmitting them "simultaneously"(change the advertising payload at each publish)?

Hi @danielcbit,
I think you can try modifying the Eddystone beacon code to call toggle between the following

UID: https://github.com/sandeepmistry/arduino-BLEPeripheral/blob/master/EddystoneBeacon.cpp#L48-L64
URL: https://github.com/sandeepmistry/arduino-BLEPeripheral/blob/master/EddystoneBeacon.cpp#L73

after calling begin.
Since the advertising interval is 100ms, you'll have to toggle at a less frequent interval than this.
I'm closing this for now, feel free to continue the discussion though. Pull request welcome for the new example along with setUid API to make things cleaner.

Hi @sandeepmistry. I would have to toggle between those in the loop method, right?

I would recommend it, two options for delaying are using:

delay(ms)
checking the value of mills() and comparing differences.

Only mils() actually, since delay() stops the code execution so it is not a good idea.
Nice, I'll work on these patchs. I will add support for ESP8266 as well, I have a patch already. This is my current platform.

@danielcbit sounds good, looking forward to seeing your patches.


[IJ Plugin] Schedule the GraphQL configuration reload early

Between the moment a project is opened and when its GraphQL configuration is gathered and contributed to the GraphQL plugin, the default behavior (use all schemas found in the project) was used, which may be confusing (cf #6219).
Instead, contribute an empty configuration immediately.
Caveat: until the configuration is gathered - which may happen late, or even never due to an issue with the Gradle conf for instance - all schema references in operations will be unresolved. But I think this is OK since the configuration contribution can be disabled completely in the settings, in which case the default behavior will be used again.

🛠 Docs Preview Building...

Configuration
{
  "repoOverrides": {
    "apollographql/apollo-kotlin@main": {
      "remote": {
        "owner": "apollographql",
        "repo": "apollo-kotlin",
        "branch": "ij-plugin-schedule-conf-reload-early"
      }
    }
  }
}

f4df00c5f2300404be05f756c308ba8198541252


distance for crosslinks

Great work !  I have a question that what is the distance for a crosslinking input like following:
5 A 5 A 0.1
Will it be 25 Ang ? How to define the distance for such a crosslinking data due to different crosslinking reagent?

hello, alphalink2 is currently trained with 25 angstrom data. So that line indicates a residue pair with 25 angstrom between residue 5 of chain A and residue 5 of chain A with a false discovery rate of 0.1 (10%). Currently, the distance cannot be changed, but it is not a distance restraint in the traditional sense- it is the maximum crosslinker distance used in training the network.
Others have already used this with different crosslinkers, as AL2 weighs both experimental and MSA evidence, and indication of proximity is often enough to drive the prediction to the correct state.
disclaimer: I am not the AL2 developer, i was involved in developing AL1.

I have been using AL2 for bs3 and dsso with ok results (the lower restraint density makes things harder). I also would say that 35 is not a generally agreed cutoff for bs3 CA-CA, groups work with anything between 22 to 35 depending how much backbone flexibility is thought to play a role...
I don't know about the parser specification for cutoff, though i know the cutoff in the colab is about plotting crosslinks on structures only.

The cutoff is just for the calculation of the crosslink satisfaction. It's by default 25 A because that's what the network was trained on. We also have another network which was trained on photoAA crosslinks (10 A).

The cutoff is just for the calculation of the crosslink satisfaction. It's by default 25 A because that's what the network was trained on. We also have another network which was trained on photoAA crosslinks (10 A).

Yes! I've checked with different cutoff, 25 A, 35 A, 45 A. The resulted structure is simillar while output satisfaction ratio gradually increases.
Thanks!


How to use it between scenes?

I was prefeb one scene.  and I want use socket other scene.
Than how to use it??  I was try add prefeb to other scene. but that is make other socket.

I have the same question.

@kys9261 @hackiey http://docs.unity3d.com/ScriptReference/Object.DontDestroyOnLoad.html
That should stop the GameObject from being destroyed when a new scene is loaded.


Missing downward arrow on the Action.ShowCard as shown in documentation

Missing downward arrow on the Action.ShowCard as shown in the adaptive cards document
Screenshots

Version
1.2 and above
Describe the bug
Document showing different card and same is not working
Steps to reproduce
In the Adaptive card designer add Action.ShowCard
Cannot see the downward arrow.
Expected behavior

Styling is controlled by the host app that is displaying your card. For example, you can change the host app at the top of our designer to see what it will look like on Outlook (which does show the arrow):

@dclaux / @matthidinger perhaps we should add the host config we use (in Schema Explorer / Samples) as an option in the designer?

@golddove technically it is already in the designer, it's the Outlook one. The problem is setting expectations: if we defaulted to Outlook (or introduced a "Default") developers would still find discrepancies between the designer and the host they target.

@naveenkumarreddym
Please check out the Outlook option in "Select host app" dropdown in designer. Feel free to re-open this issue if you have further questions.


Enable the transactional outbox pattern but no message delivered to the message broker

In what area(s)?

/area runtime

What version of Dapr?

1.14.2

Expected Behavior

I am using postgresql as a state store component and rabbitmq as a message broker, when i saved the state keys by state store transaction, the messages should be delivered to the message broker
Actual Behavior
Keys were successfully saved to postgresql, but no message delivered to message broker

Steps to Reproduce the Problem

pubsub.yaml

apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
  name: app1-pub-sub-outbox
  namespace: tenent1
spec:
  type: pubsub.rabbitmq
  version: v1
  metadata:
  - name: connectionString
    value: "amqp://root:root@<IP_ADDRESS>:5672/dapr_test_vhost"
  - name: protocol
    value: "amqp"
  - name: hostname
    value: "<IP_ADDRESS>"
  - name: username
    value: "root"
  - name: password
    value: "root"
  - name: durable
    value: "true"
  - name: deletedWhenUnused
    value: "false"
  - name: autoAck
    value: "false"
  - name: reconnectWait
    value: "0"
  - name: enableDeadLetter
    value: "false"
  - name: concurrency
    value: parallel
  - name: consumerID
    value: "{namespace}"
scopes:
- refactor-test-app1
- refactor-test-order
- refactor-test-stock

subscription.yaml

apiVersion: dapr.io/v2alpha1
kind: Subscription
metadata:
  name: app1-pub-sub-outbox
  namespace: tenent1
spec:
  topic: dapr_app1_topic_outbox
  routes:
    default: /test_consume_msg
  pubsubname: app1-pub-sub-outbox
scopes:
- refactor-test-app1
- refactor-test-order

statestore.yaml

apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
  name: statestore-outbox
  namespace: tenent1
spec:
  type: state.postgresql
  version: v2
  metadata:
  - name: connectionString
    value: "host=<IP_ADDRESS> user=postgres password=123456 port=5432 database=rocketbird-refactor"
  - name: tablePrefix
    value: "dapr.dapr_"
  - name: metadataTableName
    value: "dapr.dapr_metadata"
  - name: outboxPublishPubsub # Required
    value: "app1-pub-sub-outbox"
  - name: outboxPublishTopic # Required
    value: "dapr_app1_topic_outbox"

use python sdk to save state

DAPR_STATESTORE_NAME_OUTBOX = 'statestore-outbox'
with DaprClient() as d:
    result = d.execute_state_transaction(store_name=DAPR_STATESTORE_NAME_OUTBOX, operations=[
        TransactionalStateOperation(
            operation_type=TransactionOperationType.upsert,
            key="outbox-key1" + uuid.uuid4().hex,
            data=val1),
        TransactionalStateOperation(key="outbox-err" + uuid.uuid4().hex, data='no-err'),
        TransactionalStateOperation(key="outbox-key2" + uuid.uuid4().hex, data=val2)
    ])

consumer message code

@app.post("/test_consume_msg")
def test_consume_msg(request: Request, event_data: dict = Body(...)):
    print(event_data)
    print(request.headers.items())

test and see what happened
I ran the save state script in step 4, then i can see datas were stored in postgresql table as bellow,

here I see some records start with "outbox-", I think these keys were created by Dapr, does it mean my state configuration  works. but i found no consume logs at /test_consume_msg endpoint, and i found no message delivered to message topic at rabbitmq UI,

can any one help me with this problem, maybe it is not a bug, caused by my understanding
Release Note

RELEASE NOTE:

Can you paste debug level logs from both the publisher and subscriber Dapr processes?

publisher-daprd-logs.txt
subscriber-daprd-logs.txt
@yaron2 here are the logs, thanks


Snakemake on Windows requires snakemake-minimal

Thanks to @annefou for the hint that solved it.
I don't know how WSL vs native anaconda affects things, etc.  Or if
this is even the right answer... please discuss.

are you sure that Windows users really need to install snakemake-minimal? I haven't observed this in a workshop for windows users, and the official installation instructions don't mention it (https://snakemake.readthedocs.io/en/stable/getting_started/installation.html)

I'm not sure at all... I just know that Anne gave the suggestion is
zulip and it seemed to work.  Someone should investigate.
The direct problem was that the pygraphviz dependency wasn't available
for install via conda, but snakemake-minimal worked.  Could it be a
native vs WSL issue?  I think some people installed via pip and it
worked.

I am unsure whether merge or not?

On Fri, May 31, 2019 at 01:59:54AM -0700, Radovan Bast wrote:

I am unsure whether merge or not?

Let's wait and see if someone understands what is going on, in the
mean time the open request provides hints for others and documentation
on a problem.

Snakemake depends on pygraphviz which is not available for windows in "standard" conda channels this is why we only install snakemake-minimal on windows.
There is one version for windows at https://anaconda.org/marufr/pygraphviz (I have never tried it).

I was also faced with installation issues of snakemake on python 3.7 namely this: https://bitbucket.org/snakemake/snakemake/issues/934/installation-failed-in-python-37
Was solved by following this comment https://github.com/pytries/datrie/issues/52#issuecomment-464977050

My understanding is that this PR needs to be amended?

I don't know... there were multiple issues, one about datrie, maybe one about this which is a bit questionable.  Really, I opened it because with git-pr it was easier to make a bad PR than a vague issue.  I know long-running open PRs aren't good, but this could be seen as an issue noting something until later...
I still don't know what the "right" solution is for sure, beyond Anne's knowledge.

The Datrie one is out of scope of this PR AFAICS. I am happy to merge if it makes things better, also OK to park.

@annefou what do you recommend we do with this PR :-) if follow-up actions are needed, can you please summarize what they are?

I would definitely recommend to merge this PR. We alwasy use snakemake-minimal on Windows as for instance pygraphviz  is not available for windows in standard conda channels.

Here is what you get if you try to install snakemake on windows:
PackagesNotFoundError: The following packages are not available from current channels:

snakemake -> imagemagick[version='>=7.0']
snakemake -> pygraphviz

i think we can merge this PR.
One alternative would be to recommend snakemake-minimal for all platforms, for simplicity's sake, but then osx/linux users would miss out on the feature to generate DAG images (i think that's what pygraphviz contributes)

creating DAGs is still in the material. We could remove it and then recommend snakemake-minimal for all platforms. Advantage would be that it's simpler to recommend only one conda package, and possibly we would avoid some installation issues even on macs and linuxes, but drawback that participants (not on Win) can't create DAGs.
I guess this connects with how much snakemake we want to teach. I enjoy teaching snakemake and my feeling is that many participants have really found it useful. Of course it's not the right tool for everyone, but the same is true for e.g. pytest and jupyter. We teach one tool in a given category, and point out that there are other tools out there that might fit other use cases better (other testing frameworks, other notebooks (e.g. for R), other workflow frameworks).
So my opinion is that we should not cut down snakemake to only bare minimum, and that we should keep an exercise on it, but that the lesson should still not be dominated by snakemake.
This might be easier to achieve if we follow Richards good suggestion to split into project organization and workflow parts

so my suggestion for now is that we merge this PR as-is. The installation instructions (after merging) say that snakemake-minimal and snakemake  are two possible packages, but the former is required on Windows. So people running into issues on mac or linux will likely think of trying snakemake-minimal

OK. Merging.
The DAG is nice to see and I agree it's nice to keep if it does not complicate installation too much.
Snakemake is a really nice tool and I am not trying to remove it. We need to offer good alternatives for the R community also and we know about this. Indeed the same can be said about pytest and that is one of the next things on my list to open up towards other communities and user profiles.


Release 130

@sebastianmontero There isn't such a catalog of banks at this moment. Users type a back name & address for each entry.

Yes, I was just wondering if at some point you considered  having a bank catalog, and if so why you decided against it?

Yes, I was just wondering if at some point you considered having a bank catalog, and if so why you decided against it?

@sebastianmontero Yes! We did at some point as we can reuse this information for other projects (and have information of all banks that participate), but we decided to not create a new storage map for banks as it was going to be more calls for the front end team. Also the plan is latter migrate that to a storage map when we implement a cache layer this information could be query easily


Fixed MERGE_ALL commit from repeating actions

Fixes #26118
Committing an UNDO action will run the action. This is fine if it's set to not merge or only merge the ends, but with MERGE_ALL it meant that the action could be merged into previous actions, then the operations from ALL the merged actions would be run, instead of from the most recent action.
This pull request fixes this by keeping a record (merge_total) of the amount of operations that are in the current action that the new action is being merged into. Then, when the action is committed. This variable is used to skip over operations until we get to the ones that only the newest action added.

I've added Unit Tests that prove the bug has been fixed and test one or two other parts of UndoRedo for good measure.

Thanks!


can't DM in web talk

Whenever I try to send a DM in web talk, the username bar goes red and it won't let me send the message. This happens both when I type ~master-morzod/inbox manually, and when I click on the name from an earlier message. I can send DMs from CLI talk without issue.
@Fang- maybe you know what this is about.

Can't reproduce, I can send DMs to ~rovnys-ricfer/inbox, ~rovnys-ricfer and rovnys-ricfer just fine. Clicking ship-names also works.
Not sure what you're hitting here. You can try pointing your browser's debugger at this function and seeing if it's doing anything weird, but I'm not sure why that would be out of the ordinary.

Oh I see, the ship name parsing is out of date. This still contains old syllables. It was failing on the mor part of ~master-morzod. brb fixing now.

See also urbit/womb#3. I had to use the browser console to claim ~master-morzod because of that ;)


Done the changes according to issue number pranjay-poddar #1560

Title and Issue number
Image is Uploaded to Travel Website Template  and the isssue no is #1560
Close #1560

Checklist:

[X] I have mentioned the issue number in my Pull Request.
[] I have commented my code, particularly in hard-to-understand areas
[] I have created a helpful and easy to understand README.md

Images are not required directly as it will increase the repo size rather links can be added to cloud images


removing babel branch

I never really liked babel, I just implemented the branch because sy needed it. I'll remove it, I don't want to work on things I'll never use. I'll use ES6 when it will be implemented in node and/or in browsers.

Done.


Landing Page UI improved

Old:

New:

@Its-Aman-Yadav please merge this PR under the GSSOC 24 and assign me under this, for any changes feel free to contact


matrix-conduit: 0.5.0 -> 0.6.0

Description of changes

New version of Conduit was released, including support for space hierarchies, threads, edit history, and many other improvements.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[X] Fits CONTRIBUTING.md.

conduit[607632]: Hello, Timo here, Thanks for updating your Conduit. Starting now, you will receive notifications in this room for important Conduit news, like when a new release comes out or a new security issue was discovered. This works by sending a simple GET request to conduit.rs once per hour. You can opt out of this by setting allow_check_for_updates = false in your config. Have a nice day!

Do we want that by default? I don't think so, since this is basically telemetry.

I think update checks should be disabled by default, not necessarily because of telemetry, but more because we as a distribution already take care of the updates.


rootless: create user conf files when they don't exist

If the configuration files for the user don't exist, create them automatically.
Different policies are used for the creation of these files:

storage.conf: use the default configuration known to libpod at the time these files are created.  This will prevent that users will keep using their configuration if we decide to change any default value in future.
libpod.conf: same policy as storage.conf.
registries.conf: when the file is not found, the global configuration is used.
policy.json: same policy as registries.conf.
mounts.conf: it is created as an empty file.

My concern about this is that the users will not get advantage of any changes to these files, if they never modified them, themselves.
Can we generate a symbolic link and then when the user modifies them we will know.  We could document that.  I think only storage.conf is necessary to be different?

the only file that could take advantage of that is registries.conf, all other ones must be customized for each user.  Should we treat registries.conf differently than other files?

Ok, I am wondering if we need a podman reset command or something like that.  We currently have issues with random content in the users homedir, that is somewhat difficult for the user to know how to cleanup.
If we go with this change, we should probably add info rot podman info to show that its registries.conf is different then the hosts registries.conf.   Or just drop registries.conf from this patch altogether and document if the  user wants to use something different. I don't see this happening often.

ok I've dropped the patch for copying registries.conf.  If the file is not found now in the user configuration, the global configuration is used

Do you need to worry about /etc/containers/policy.json?

Changes LGTM, but would like other head nods on this.

Changes LGTM, but would like other head nods on this.

and I'd definitely like to know what @mheon thinks about this PR before it is merged

LGTM - I think this will help a lot with ensuring rootless files always go in the same place.

can we cover this at a scrum before merging?

/approve cancel

can we cover this at a scrum before merging?

sure.  Is there anything in particular that must be covered?

mostly that @mheon is working on a PR that will be complimentary to this and we should make sure things are coordinated on how they work. no major objections at all.

Sorry, I am late to the game. Two things came to my mind while reading the code:

Currently, we are ignoring errors when creating those files. I don't understand why they're being ignored but I likely miss some background story. Can you elaborate on that?

Another issue relates to update scenarios. Not having those config files might be intended by some users who want to rely on Podman's defaults. When creating the config files, Podman will continue loading the defaults from this specific version of Podman.

The issue with relying on the defaults is when they change - almost all of
them changing will result in breaking changes that lose all the user's
rootless containers.
On Thu, Nov 15, 2018, 07:46 Valentin Rothberg<EMAIL_ADDRESS>wrote:

Sorry, I am late to the game. Two things came to my mind while reading the
code:

Currently, we are ignoring errors when creating those files. I don't
understand why they're being ignored but I likely miss some background
story. Can you elaborate on that?
Another issue relates to update scenarios. Not having those config
files might be intended by some users who want to rely on Podman's
defaults. When creating the config files, Podman will continue loading the
defaults from this specific version of Podman.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/containers/libpod/pull/1806#issuecomment-439028379,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHYHCJdow99nRW43Qow5IP9y1SoRvpFLks5uvWIWgaJpZM4YbN4H
.

The issue with relying on the defaults is when they change - almost all of
them changing will result in breaking changes that lose all the user's
rootless containers.

Thanks, @mheon. Makes sense. Better safe than sorry :+1:

Right I believe we should only change the config files that "rootless" podman overrides from the user installed version.
This is why I don't want @giuseppe creating a registries.conf or policy.json, we should continue to use the system defaults unless the user creates them.
BTW I don't think we should ignore the errors when creating these files.

BTW I don't think we should ignore the errors when creating these files.

I've changed it to not ignore errors when creating these files

tests are happy again

/lgtm


IP_AUTODETECTION_METHOD setting is unsuccessful

@sunboy1 is this an operator managed cluster? For operator installs of Calico, to change the IP auto detection config you'll need to update the Installation custom resource: https://docs.projectcalico.org/reference/installation/api#operator.tigera.io/v1.NodeAddressAutodetection

thanks


update jdk version to 1.8

update to avoid grammar errors

Codecov Report

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

@@             Coverage Diff              @@
##             master    #2080      +/-   ##
============================================
- Coverage     83.07%   83.05%   -0.03%
+ Complexity     6582     6578       -4
============================================
  Files           139      139
  Lines         24036    24036
  Branches       5614     5614
============================================
- Hits          19969    19964       -5
- Misses         2539     2543       +4
- Partials       1528     1529       +1

Impacted Files
Coverage Δ
Complexity Δ

...com/alibaba/fastjson/parser/JSONReaderScanner.java
72.61% <0%> (-1.28%)
44% <0%> (-1%)

...main/java/com/alibaba/fastjson/util/TypeUtils.java
82.67% <0%> (-0.15%)
509% <0%> (-1%)

...ava/com/alibaba/fastjson/parser/JSONLexerBase.java
71.85% <0%> (-0.04%)
788% <0%> (-1%)

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 bdf617d...6ddd847. Read the comment docs.

Need to support JDK 1.5/1.6/1.7


"error trying to start process"

Hi
I've installed from the package manager and Rhino 8, I didn't see it on the Rhino 7 package manager.  When dropping the component onto the canvas I see this error.  I'm running on Windows 11.

Thanks @rdthree
This was due to Rhino 8's change to dotnet core. Fixed via https://github.com/camnewnham/HotLoader/commit/4c68c6b2291e5faf7c09c98274f45bc31c5fe0a3

Thanks! At this point should I wait for an updated version on the package
manager?
On Tue, Nov 14, 2023, 6:00 PM camnewnham @.***> wrote:

Closed #2 https://github.com/camnewnham/HotLoader/issues/2 as completed.
—
Reply to this email directly, view it on GitHub
https://github.com/camnewnham/HotLoader/issues/2#event-10961031214, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAI4RZHTXLS6G4EE7J4PPRLYEPZYNAVCNFSM6AAAAAA7LN43LCVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJQHE3DCMBTGEZDCNA
.
You are receiving this because you were mentioned.Message ID:
@.***>

It's updated now, so yes you can update via the package manager :)
Cheers
On Wed, 15 Nov 2023 at 10:19, rdthree @.***> wrote:

Thanks! At this point should I wait for an updated version on the package
manager?
On Tue, Nov 14, 2023, 6:00 PM camnewnham @.***> wrote:

Closed #2 https://github.com/camnewnham/HotLoader/issues/2 as
completed.
—
Reply to this email directly, view it on GitHub
https://github.com/camnewnham/HotLoader/issues/2#event-10961031214,
or
unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AAI4RZHTXLS6G4EE7J4PPRLYEPZYNAVCNFSM6AAAAAA7LN43LCVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJQHE3DCMBTGEZDCNA>

.
You are receiving this because you were mentioned.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/camnewnham/HotLoader/issues/2#issuecomment-1811546601,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AETCYCHGNBB2U4ZZI77TVBLYEP4BJAVCNFSM6AAAAAA7LN43LCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJRGU2DMNRQGE
.
You are receiving this because you modified the open/close state.Message
ID: @.***>


wrong representation of found pods by kubernetes replica sets

Rancher Versions:
Server: 1.3.1
kubernetes (if applicable):1.5.1   latest update that was available
OS and where are the hosts located? (cloud, bare metal, etc):
AWS
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)
3 nodes HA, external DB
Environment Type: (Cattle/Kubernetes/Swarm/Mesos)
Kubernetes
Steps to Reproduce:
shut down and delete all worker nodes in environment. then create new hosts and attach to environment.
Results:
plenty of pods, old and new, displayed in "deployment" / "replica sets" ,  but dashboard says "3/0 up" or similar.

some kind of UI bug where dashboard representation is wrong. happened after i closed all spotinst worker nodes with running pods, and started new servers (old servers were DELETED, and new CREATED, not same hosts).  probably also Kubernetes bug, where it thinks it has so many live pods  (ALL those pods and containers are shown as ALIVE and ready in Rancher -  but are all nonexistent containers!)

P.S. one thing to learn from this:  never turn off all your worker minions on kubernetes :)
P.S.2. It was kinda disaster recovery test, to know if masters will reschedule the correct pods after new worker nodes come back and cluster can be recovered.  well the test failed i guess? :)

etcd docker volume still present on recycled hosts. See here https://docs.rancher.com/rancher/v1.5/en/kubernetes/deleting/#cleaing-up-persistent-data


bazel_4 incorrect arch set for aarch64-darwin

Describe the bug
When using a .bazelversion file with the current bazel_4, you get a message like:
bazel build //...
ERROR: The project you're trying to build requires Bazel 4.2.1 (specified in /local/project/path/.bazelversion), but it wasn't found in /nix/store/lh5cn9cmqvj6iry3i4k02vi5vyvcy58w-bazel-4.2.2/bin.

Bazel binaries for all official releases can be downloaded from here:
  https://github.com/bazelbuild/bazel/releases

Please put the downloaded Bazel binary into this location:
  /nix/store/lh5cn9cmqvj6iry3i4k02vi5vyvcy58w-bazel-4.2.2/bin/bazel-4.2.1-darwin-arm64

a quick ls in that store path shows that the bin is suffixed with aarch64 instead of arm64
 /bin/ls -l /nix/store/lh5cn9cmqvj6iry3i4k02vi5vyvcy58w-bazel-4.2.2/bin/
total 62776
-r-xr-xr-x  1 root  nixbld      8734 Dec 31  1969 bazel
-r-xr-xr-x  1 root  nixbld  32123374 Dec 31  1969 bazel-4.2.2-darwin-aarch64
-r-xr-xr-x  1 root  nixbld       240 Dec 31  1969 bazel-execlog

Steps To Reproduce
Steps to reproduce the behavior:

Add a .bazelversion file to an existing bazel project
Attempt to use bazel_4

Expected behavior
Build should work and continue forward without error
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Once I remove the .bazelversion file, it works fine.
Notify maintainers

@NixOS/bazel
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
- system: `"aarch64-darwin"`
 - host os: `Darwin 21.2.0, macOS 12.1`
 - multi-user?: `yes`
 - sandbox: `no`
 - version: `nix-env (Nix) 2.5.1`
 - nixpkgs: `/nix/store/2l43ycb2hl1pv05bifdvjf352x0g6sg8-lgfhg4n6445yizgf0xjirb4bc4j86fr9-source`

This appears to still be an issue. Symlinking sudo ln -s bazel-4.2.2-darwin-aarch64 bazel-4.2.2-darwin-arm64 in the /nix/store/1mr7dcx24li4fa9a5dhnylz8bcf2p0i9-bazel-4.2.2/bin directory makes it work. But how should this be fixed in future?

I believe if this line was changed from stdenv.hostPlatform.parsed.cpu.name to stdenv.hostPlatform.darwinArch that would fix it.
I don't have a super deep understanding of nix, but it looks like that would work regardless of the actual host system based on these attributes.

This is also an issue with bazel_5 since it uses the same logic for determining the arch name https://github.com/NixOS/nixpkgs/blob/nixos-unstable/pkgs/development/tools/build-managers/bazel/bazel_5/default.nix#L129

should probably be resolved by https://github.com/NixOS/nixpkgs/pull/180251


Automator: update proxy@master in istio/istio@master

Generated by Automator - 2024-04-27T14:40:30+00:00

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry_istio
36f55016f97329baab2df69fb32adf6241ddd01c
link
true
/test integ-telemetry

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry_istio
36f55016f97329baab2df69fb32adf6241ddd01c
link
true
/test integ-telemetry

integ-telemetry-discovery_istio
36f55016f97329baab2df69fb32adf6241ddd01c
link
true
/test integ-telemetry-discovery

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry_istio
36f55016f97329baab2df69fb32adf6241ddd01c
link
true
/test integ-telemetry

integ-telemetry-discovery_istio
36f55016f97329baab2df69fb32adf6241ddd01c
link
true
/test integ-telemetry-discovery

integ-telemetry-istiodremote_istio
36f55016f97329baab2df69fb32adf6241ddd01c
link
true
/test integ-telemetry-istiodremote

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry_istio
36f55016f97329baab2df69fb32adf6241ddd01c
link
true
/test integ-telemetry

integ-telemetry-discovery_istio
36f55016f97329baab2df69fb32adf6241ddd01c
link
true
/test integ-telemetry-discovery

integ-telemetry-istiodremote_istio
36f55016f97329baab2df69fb32adf6241ddd01c
link
true
/test integ-telemetry-istiodremote

integ-telemetry-mc_istio
36f55016f97329baab2df69fb32adf6241ddd01c
link
true
/test integ-telemetry-mc

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry_istio
36f55016f97329baab2df69fb32adf6241ddd01c
link
true
/test integ-telemetry

integ-telemetry-discovery_istio
36f55016f97329baab2df69fb32adf6241ddd01c
link
true
/test integ-telemetry-discovery

integ-telemetry-mc_istio
36f55016f97329baab2df69fb32adf6241ddd01c
link
true
/test integ-telemetry-mc

integ-telemetry-istiodremote_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry-istiodremote

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry_istio
36f55016f97329baab2df69fb32adf6241ddd01c
link
true
/test integ-telemetry

integ-telemetry-mc_istio
36f55016f97329baab2df69fb32adf6241ddd01c
link
true
/test integ-telemetry-mc

integ-telemetry-istiodremote_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry-istiodremote

integ-telemetry-discovery_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry-discovery

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-mc_istio
36f55016f97329baab2df69fb32adf6241ddd01c
link
true
/test integ-telemetry-mc

integ-telemetry-istiodremote_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry-istiodremote

integ-telemetry-discovery_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry-discovery

integ-telemetry_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-istiodremote_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry-istiodremote

integ-telemetry-discovery_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry-discovery

integ-telemetry_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry

integ-telemetry-mc_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry-mc

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

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-discovery_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry-discovery

integ-telemetry_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry

integ-telemetry-mc_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry-mc

integ-telemetry-istiodremote_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry-istiodremote

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-discovery_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry-discovery

integ-telemetry-mc_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry-mc

integ-telemetry-istiodremote_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry-istiodremote

integ-telemetry_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-mc_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry-mc

integ-telemetry-istiodremote_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry-istiodremote

integ-telemetry_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry

integ-telemetry-discovery_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry-discovery

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-istiodremote_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry-istiodremote

integ-telemetry_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry

integ-telemetry-discovery_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry-discovery

integ-telemetry-mc_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry-mc

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

there's no related changes around this in upstream, seems like a network/dns issue.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry

integ-telemetry-discovery_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry-discovery

integ-telemetry-mc_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry-mc

integ-telemetry-istiodremote_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry-istiodremote

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-discovery_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry-discovery

integ-telemetry-mc_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry-mc

integ-telemetry-istiodremote_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry-istiodremote

integ-telemetry_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-mc_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry-mc

integ-telemetry-istiodremote_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry-istiodremote

integ-telemetry_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry

integ-telemetry-discovery_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry-discovery

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-istiodremote_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry-istiodremote

integ-telemetry_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry

integ-telemetry-discovery_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry-discovery

integ-telemetry-mc_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry-mc

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry

integ-telemetry-discovery_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry-discovery

integ-telemetry-mc_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry-mc

integ-telemetry-istiodremote_istio
9a0d242ade27bda2cb74632323a820263ddf8022
link
true
/test integ-telemetry-istiodremote

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry

integ-telemetry-mc_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry-mc

integ-telemetry-istiodremote_istio
9a0d242ade27bda2cb74632323a820263ddf8022
link
true
/test integ-telemetry-istiodremote

integ-telemetry-discovery_istio
9a0d242ade27bda2cb74632323a820263ddf8022
link
true
/test integ-telemetry-discovery

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-mc_istio
7ae5f6c61fb21721f7b702682d7d1a3f23a92c18
link
true
/test integ-telemetry-mc

integ-telemetry-istiodremote_istio
9a0d242ade27bda2cb74632323a820263ddf8022
link
true
/test integ-telemetry-istiodremote

integ-telemetry-discovery_istio
9a0d242ade27bda2cb74632323a820263ddf8022
link
true
/test integ-telemetry-discovery

integ-telemetry_istio
9a0d242ade27bda2cb74632323a820263ddf8022
link
true
/test integ-telemetry

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-istiodremote_istio
9a0d242ade27bda2cb74632323a820263ddf8022
link
true
/test integ-telemetry-istiodremote

integ-telemetry-discovery_istio
9a0d242ade27bda2cb74632323a820263ddf8022
link
true
/test integ-telemetry-discovery

integ-telemetry_istio
9a0d242ade27bda2cb74632323a820263ddf8022
link
true
/test integ-telemetry

integ-telemetry-mc_istio
9a0d242ade27bda2cb74632323a820263ddf8022
link
true
/test integ-telemetry-mc

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-discovery_istio
9a0d242ade27bda2cb74632323a820263ddf8022
link
true
/test integ-telemetry-discovery

integ-telemetry_istio
9a0d242ade27bda2cb74632323a820263ddf8022
link
true
/test integ-telemetry

integ-telemetry-mc_istio
9a0d242ade27bda2cb74632323a820263ddf8022
link
true
/test integ-telemetry-mc

integ-telemetry-istiodremote_istio
e5d11941f2c0546574767bd04e6bddcaf1bfbb61
link
true
/test integ-telemetry-istiodremote

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-discovery_istio
9a0d242ade27bda2cb74632323a820263ddf8022
link
true
/test integ-telemetry-discovery

integ-telemetry-mc_istio
9a0d242ade27bda2cb74632323a820263ddf8022
link
true
/test integ-telemetry-mc

integ-telemetry-istiodremote_istio
e5d11941f2c0546574767bd04e6bddcaf1bfbb61
link
true
/test integ-telemetry-istiodremote

integ-telemetry_istio
e5d11941f2c0546574767bd04e6bddcaf1bfbb61
link
true
/test integ-telemetry

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-mc_istio
9a0d242ade27bda2cb74632323a820263ddf8022
link
true
/test integ-telemetry-mc

integ-telemetry-istiodremote_istio
e5d11941f2c0546574767bd04e6bddcaf1bfbb61
link
true
/test integ-telemetry-istiodremote

integ-telemetry_istio
e5d11941f2c0546574767bd04e6bddcaf1bfbb61
link
true
/test integ-telemetry

integ-telemetry-discovery_istio
e5d11941f2c0546574767bd04e6bddcaf1bfbb61
link
true
/test integ-telemetry-discovery

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-istiodremote_istio
e5d11941f2c0546574767bd04e6bddcaf1bfbb61
link
true
/test integ-telemetry-istiodremote

integ-telemetry_istio
e5d11941f2c0546574767bd04e6bddcaf1bfbb61
link
true
/test integ-telemetry

integ-telemetry-discovery_istio
e5d11941f2c0546574767bd04e6bddcaf1bfbb61
link
true
/test integ-telemetry-discovery

integ-telemetry-mc_istio
e5d11941f2c0546574767bd04e6bddcaf1bfbb61
link
true
/test integ-telemetry-mc

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-istiodremote_istio
e5d11941f2c0546574767bd04e6bddcaf1bfbb61
link
true
/test integ-telemetry-istiodremote

integ-telemetry_istio
e5d11941f2c0546574767bd04e6bddcaf1bfbb61
link
true
/test integ-telemetry

integ-telemetry-discovery_istio
e5d11941f2c0546574767bd04e6bddcaf1bfbb61
link
true
/test integ-telemetry-discovery

integ-telemetry-mc_istio
e5d11941f2c0546574767bd04e6bddcaf1bfbb61
link
true
/test integ-telemetry-mc

integ-security-multicluster_istio
e5d11941f2c0546574767bd04e6bddcaf1bfbb61
link
true
/test integ-security-multicluster

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry_istio
e5d11941f2c0546574767bd04e6bddcaf1bfbb61
link
true
/test integ-telemetry

integ-telemetry-discovery_istio
e5d11941f2c0546574767bd04e6bddcaf1bfbb61
link
true
/test integ-telemetry-discovery

integ-telemetry-mc_istio
e5d11941f2c0546574767bd04e6bddcaf1bfbb61
link
true
/test integ-telemetry-mc

integ-security-multicluster_istio
e5d11941f2c0546574767bd04e6bddcaf1bfbb61
link
true
/test integ-security-multicluster

integ-telemetry-istiodremote_istio
f599a2033ea5d431ec18ad8a2e33c876e0ae0d3c
link
true
/test integ-telemetry-istiodremote

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-discovery_istio
e5d11941f2c0546574767bd04e6bddcaf1bfbb61
link
true
/test integ-telemetry-discovery

integ-telemetry-mc_istio
e5d11941f2c0546574767bd04e6bddcaf1bfbb61
link
true
/test integ-telemetry-mc

integ-security-multicluster_istio
e5d11941f2c0546574767bd04e6bddcaf1bfbb61
link
true
/test integ-security-multicluster

integ-telemetry-istiodremote_istio
f599a2033ea5d431ec18ad8a2e33c876e0ae0d3c
link
true
/test integ-telemetry-istiodremote

integ-telemetry_istio
f599a2033ea5d431ec18ad8a2e33c876e0ae0d3c
link
true
/test integ-telemetry

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-multicluster_istio
e5d11941f2c0546574767bd04e6bddcaf1bfbb61
link
true
/test integ-security-multicluster

integ-telemetry-istiodremote_istio
f599a2033ea5d431ec18ad8a2e33c876e0ae0d3c
link
true
/test integ-telemetry-istiodremote

integ-telemetry_istio
f599a2033ea5d431ec18ad8a2e33c876e0ae0d3c
link
true
/test integ-telemetry

integ-telemetry-discovery_istio
f599a2033ea5d431ec18ad8a2e33c876e0ae0d3c
link
true
/test integ-telemetry-discovery

integ-telemetry-mc_istio
f599a2033ea5d431ec18ad8a2e33c876e0ae0d3c
link
true
/test integ-telemetry-mc

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.

I also looked at this failure to see if I could find anything, and didn't. It does seem suspicious that the failures relate to Zipkin, which had some changes a while ago, but I couldn't find anything related. @kyessenov

this is more like a c-ares issue in envoy.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-istiodremote_istio
f599a2033ea5d431ec18ad8a2e33c876e0ae0d3c
link
true
/test integ-telemetry-istiodremote

integ-telemetry_istio
f599a2033ea5d431ec18ad8a2e33c876e0ae0d3c
link
true
/test integ-telemetry

integ-telemetry-discovery_istio
f599a2033ea5d431ec18ad8a2e33c876e0ae0d3c
link
true
/test integ-telemetry-discovery

integ-telemetry-mc_istio
f599a2033ea5d431ec18ad8a2e33c876e0ae0d3c
link
true
/test integ-telemetry-mc

integ-ambient_istio
8cf06f4e361f465d7729cc56274c05e7ede584c4
link
true
/test integ-ambient

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry_istio
f599a2033ea5d431ec18ad8a2e33c876e0ae0d3c
link
true
/test integ-telemetry

integ-telemetry-discovery_istio
f599a2033ea5d431ec18ad8a2e33c876e0ae0d3c
link
true
/test integ-telemetry-discovery

integ-telemetry-mc_istio
f599a2033ea5d431ec18ad8a2e33c876e0ae0d3c
link
true
/test integ-telemetry-mc

integ-ambient_istio
8cf06f4e361f465d7729cc56274c05e7ede584c4
link
true
/test integ-ambient

integ-telemetry-istiodremote_istio
8cf06f4e361f465d7729cc56274c05e7ede584c4
link
true
/test integ-telemetry-istiodremote

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry_istio
f599a2033ea5d431ec18ad8a2e33c876e0ae0d3c
link
true
/test integ-telemetry

integ-telemetry-mc_istio
f599a2033ea5d431ec18ad8a2e33c876e0ae0d3c
link
true
/test integ-telemetry-mc

integ-ambient_istio
8cf06f4e361f465d7729cc56274c05e7ede584c4
link
true
/test integ-ambient

integ-telemetry-istiodremote_istio
8cf06f4e361f465d7729cc56274c05e7ede584c4
link
true
/test integ-telemetry-istiodremote

integ-telemetry-discovery_istio
8cf06f4e361f465d7729cc56274c05e7ede584c4
link
true
/test integ-telemetry-discovery

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-mc_istio
f599a2033ea5d431ec18ad8a2e33c876e0ae0d3c
link
true
/test integ-telemetry-mc

integ-ambient_istio
8cf06f4e361f465d7729cc56274c05e7ede584c4
link
true
/test integ-ambient

integ-telemetry-istiodremote_istio
8cf06f4e361f465d7729cc56274c05e7ede584c4
link
true
/test integ-telemetry-istiodremote

integ-telemetry-discovery_istio
8cf06f4e361f465d7729cc56274c05e7ede584c4
link
true
/test integ-telemetry-discovery

integ-telemetry_istio
8cf06f4e361f465d7729cc56274c05e7ede584c4
link
true
/test integ-telemetry

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio
8cf06f4e361f465d7729cc56274c05e7ede584c4
link
true
/test integ-ambient

integ-telemetry-istiodremote_istio
8cf06f4e361f465d7729cc56274c05e7ede584c4
link
true
/test integ-telemetry-istiodremote

integ-telemetry-discovery_istio
8cf06f4e361f465d7729cc56274c05e7ede584c4
link
true
/test integ-telemetry-discovery

integ-telemetry_istio
8cf06f4e361f465d7729cc56274c05e7ede584c4
link
true
/test integ-telemetry

integ-telemetry-mc_istio
8cf06f4e361f465d7729cc56274c05e7ede584c4
link
true
/test integ-telemetry-mc

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

this is more like a c-ares issue in envoy.

https://github.com/envoyproxy/envoy/pull/33880

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-discovery_istio
8cf06f4e361f465d7729cc56274c05e7ede584c4
link
true
/test integ-telemetry-discovery

integ-telemetry_istio
8cf06f4e361f465d7729cc56274c05e7ede584c4
link
true
/test integ-telemetry

integ-telemetry-mc_istio
8cf06f4e361f465d7729cc56274c05e7ede584c4
link
true
/test integ-telemetry-mc

integ-ambient_istio
26101e7a1dda8ee49f39f4b79f7c98f110c6b377
link
true
/test integ-ambient

integ-telemetry-istiodremote_istio
26101e7a1dda8ee49f39f4b79f7c98f110c6b377
link
true
/test integ-telemetry-istiodremote

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-discovery_istio
8cf06f4e361f465d7729cc56274c05e7ede584c4
link
true
/test integ-telemetry-discovery

integ-telemetry-mc_istio
8cf06f4e361f465d7729cc56274c05e7ede584c4
link
true
/test integ-telemetry-mc

integ-ambient_istio
26101e7a1dda8ee49f39f4b79f7c98f110c6b377
link
true
/test integ-ambient

integ-telemetry-istiodremote_istio
26101e7a1dda8ee49f39f4b79f7c98f110c6b377
link
true
/test integ-telemetry-istiodremote

integ-telemetry_istio
26101e7a1dda8ee49f39f4b79f7c98f110c6b377
link
true
/test integ-telemetry

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-mc_istio
8cf06f4e361f465d7729cc56274c05e7ede584c4
link
true
/test integ-telemetry-mc

integ-ambient_istio
26101e7a1dda8ee49f39f4b79f7c98f110c6b377
link
true
/test integ-ambient

integ-telemetry-istiodremote_istio
26101e7a1dda8ee49f39f4b79f7c98f110c6b377
link
true
/test integ-telemetry-istiodremote

integ-telemetry_istio
26101e7a1dda8ee49f39f4b79f7c98f110c6b377
link
true
/test integ-telemetry

integ-telemetry-discovery_istio
26101e7a1dda8ee49f39f4b79f7c98f110c6b377
link
true
/test integ-telemetry-discovery

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio
26101e7a1dda8ee49f39f4b79f7c98f110c6b377
link
true
/test integ-ambient

integ-telemetry-istiodremote_istio
26101e7a1dda8ee49f39f4b79f7c98f110c6b377
link
true
/test integ-telemetry-istiodremote

integ-telemetry_istio
26101e7a1dda8ee49f39f4b79f7c98f110c6b377
link
true
/test integ-telemetry

integ-telemetry-discovery_istio
26101e7a1dda8ee49f39f4b79f7c98f110c6b377
link
true
/test integ-telemetry-discovery

integ-telemetry-mc_istio
26101e7a1dda8ee49f39f4b79f7c98f110c6b377
link
true
/test integ-telemetry-mc

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-istiodremote_istio
26101e7a1dda8ee49f39f4b79f7c98f110c6b377
link
true
/test integ-telemetry-istiodremote

integ-telemetry_istio
26101e7a1dda8ee49f39f4b79f7c98f110c6b377
link
true
/test integ-telemetry

integ-telemetry-mc_istio
26101e7a1dda8ee49f39f4b79f7c98f110c6b377
link
true
/test integ-telemetry-mc

integ-ambient_istio
213458dfd3791cbf5504dbec80a75f8f560cb988
link
true
/test integ-ambient

integ-telemetry-discovery_istio
213458dfd3791cbf5504dbec80a75f8f560cb988
link
true
/test integ-telemetry-discovery

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-istiodremote_istio
26101e7a1dda8ee49f39f4b79f7c98f110c6b377
link
true
/test integ-telemetry-istiodremote

integ-telemetry-mc_istio
26101e7a1dda8ee49f39f4b79f7c98f110c6b377
link
true
/test integ-telemetry-mc

integ-ambient_istio
213458dfd3791cbf5504dbec80a75f8f560cb988
link
true
/test integ-ambient

integ-telemetry-discovery_istio
213458dfd3791cbf5504dbec80a75f8f560cb988
link
true
/test integ-telemetry-discovery

integ-telemetry_istio
213458dfd3791cbf5504dbec80a75f8f560cb988
link
true
/test integ-telemetry

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-mc_istio
26101e7a1dda8ee49f39f4b79f7c98f110c6b377
link
true
/test integ-telemetry-mc

integ-ambient_istio
213458dfd3791cbf5504dbec80a75f8f560cb988
link
true
/test integ-ambient

integ-telemetry-discovery_istio
213458dfd3791cbf5504dbec80a75f8f560cb988
link
true
/test integ-telemetry-discovery

integ-telemetry_istio
213458dfd3791cbf5504dbec80a75f8f560cb988
link
true
/test integ-telemetry

integ-telemetry-istiodremote_istio
213458dfd3791cbf5504dbec80a75f8f560cb988
link
true
/test integ-telemetry-istiodremote

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio
213458dfd3791cbf5504dbec80a75f8f560cb988
link
true
/test integ-ambient

integ-telemetry-discovery_istio
213458dfd3791cbf5504dbec80a75f8f560cb988
link
true
/test integ-telemetry-discovery

integ-telemetry_istio
213458dfd3791cbf5504dbec80a75f8f560cb988
link
true
/test integ-telemetry

integ-telemetry-istiodremote_istio
213458dfd3791cbf5504dbec80a75f8f560cb988
link
true
/test integ-telemetry-istiodremote

integ-telemetry-mc_istio
213458dfd3791cbf5504dbec80a75f8f560cb988
link
true
/test integ-telemetry-mc

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio
213458dfd3791cbf5504dbec80a75f8f560cb988
link
true
/test integ-ambient

integ-telemetry-discovery_istio
213458dfd3791cbf5504dbec80a75f8f560cb988
link
true
/test integ-telemetry-discovery

integ-telemetry_istio
213458dfd3791cbf5504dbec80a75f8f560cb988
link
true
/test integ-telemetry

integ-telemetry-istiodremote_istio
213458dfd3791cbf5504dbec80a75f8f560cb988
link
true
/test integ-telemetry-istiodremote

integ-telemetry-mc_istio
213458dfd3791cbf5504dbec80a75f8f560cb988
link
true
/test integ-telemetry-mc

integ-security-multicluster_istio
213458dfd3791cbf5504dbec80a75f8f560cb988
link
true
/test integ-security-multicluster

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.


Update Keycloak docs

Fixes | Closes | Resolves #999

Please remove anything marked as optional that you don't need to fill in. Choose one of the keywords preceding to refer to the issue this PR solves, followed by the issue number (e.g Fixes # 666). If there is no issue, remove the line. Remove this note after reading.

Changes:

Update docs based on new default groups available

Types of changes
What types of changes does your code introduce?
Put an x in the boxes that apply

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds a feature)
[ ] Breaking change (fix or feature that would cause existing features to not work as expected)
[x] Documentation Update
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build related changes
[ ] Other (please describe):

Testing
Requires testing

[ ] Yes
[ ] No

In case you checked yes, did you write tests?

[ ] Yes
[ ] No

Further comments (optional)
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered and more.

Hey @trallard, thanks for the thorough review. I committed all but one of your suggestions. I will be making updates here based on some of the recent keycloak group changes (#1112). I'd be happy to have you look it over again shortly :)

This keycloak group structure is finalized so should be ready for the keycloak docs.


error constructing ArbComplex

Hi Devs,
I'm attempting to make some ArbComplex variables. This is what I'm trying, but I can't seem to create one. I had expected the below to create an ArbComplex of 1+i.
I must be doing something wrong?
Cheers,
James
julia> using ArbNumerics

julia> ArbComplex(1.0)
1.0 + 0im

julia> ArbComplex(1.0 + im)
ERROR: MethodError: no method matching ArbComplex{128}(::Complex{Float64})
Closest candidates are:
  ArbComplex{128}(::T<:Number) where T<:Number at boot.jl:741
  ArbComplex{128}() where P at /Users/james/.julia/packages/ArbNumerics/mzdxG/src/libarb/ArbComplex.jl:23
  ArbComplex{128}(::ArbComplex{P}) where P at /Users/james/.julia/packages/ArbNumerics/mzdxG/src/libarb/ArbComplex.jl:32
  ...
Stacktrace:
 [1] ArbComplex(::Complex{Float64}) at /Users/james/.julia/packages/ArbNumerics/mzdxG/src/values/constructors.jl:15
 [2] top-level scope at none:0

[7e558dbc] ArbNumerics v0.2.6
Version 1.1.2-pre.0 (2019-05-17)  release-1.1/2aee2debbb

I get it:
julia> ArbComplex(1.0, 1)
1.0 + 1.0im

also, for that specific value
julia> one(ArbComplex)
1.0 + 0im

This is related:
Julia> (1 + im) / ArbComplex(1, 1)
ERROR: MethodError: no method matching ArbComplex{152}(::Complex{Int64})

but this is fixed by
ArbComplex{P}(x::T) where {P, T<:Number} = ArbComplex{P}(real(x), imag(x))

Is not the right way to do it?

What version of Julia are you using?

julia> versioninfo()
Julia Version 1.2.0
Commit c6da87ff4b (2019-08-20 00:03 UTC)
Platform Info:
  OS: Windows (x86_64-w64-mingw32)
  CPU: Intel(R) Xeon(R) E-2176M  CPU @ 2.70GHz
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-6.0.1 (ORCJIT, skylake)

julia> using ArbNumerics

julia>  (1 + im) / ArbComplex(1, 1)
1.0 + 0im

julia> versioninfo()
Julia Version 1.1.2-pre.0
Commit 2aee2debbb (2019-05-17 16:48 UTC)
Platform Info:
  OS: macOS (x86_64-apple-darwin18.5.0)
  CPU: Intel(R) Core(TM) i7-5557U CPU @ 3.10GHz
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-6.0.1 (ORCJIT, broadwell)
Environment:
  JULIA_NUM_THREADS = 4

On Mon, 9 Sep 2019 at 19:58, Jeffrey Sarnoff<EMAIL_ADDRESS>wrote:

What version of Julia are you using?
julia> versioninfo()
Julia Version 1.2.0
Commit c6da87ff4b (2019-08-20 00:03 UTC)
Platform Info:
OS: Windows (x86_64-w64-mingw32)
CPU: Intel(R) Xeon(R) E-2176M  CPU @ 2.70GHz
WORD_SIZE: 64
LIBM: libopenlibm
LLVM: libLLVM-6.0.1 (ORCJIT, skylake)
julia> using ArbNumerics
julia>  (1 + im) / ArbComplex(1, 1)
1.0 + 0im
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/JeffreySarnoff/ArbNumerics.jl/issues/21?email_source=notifications&email_token=ADWNA6UY4OFNITDVA73Z5SDQI2MGDA5CNFSM4IUUKGG2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6IVSHA#issuecomment-529619228,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADWNA6UJKSB5D3JKE7ZVZ7DQI2MGDANCNFSM4IUUKGGQ
.

More good things occur without our effort in v1.2

many lower-level corner case gotchas have been  resolved
many of my benchmarks run 5%-10% faster

I use v1.2 and v1.3-x.
Some more good things happen in 1.3-x (more of each above + the advent of easy multithreading).

I get a lot of ERROR: Unsatisfiable requirements detected for package FOO errors for v1.2 - I don't have the bandwidth to think about it. I was just hoping that eventually I'll just try and it will work

reasonable


[WIP] use behavior api in p2p/eth/les/exchange

extracted from #966
What was wrong?
This is a WIP that applies the behavior API introduced in #1142 to the appropriate p2p/eth/les and request/response APIs.
How was it fixed?
To-Do

[ ] Clean up commit history

[ ] Add entry to the release notes

Cute Animal Picture

replaced by #1199 and #1156  and #1150


Failed: build_docker_http2

Bottom of the log:
Entering 'third_party/protobuf'
Submodule 'third_party/protobuf' (https://github.com/google/protobuf.git) registered for path 'third_party/protobuf'
Cloning into '/var/local/git/grpc/third_party/protobuf'...
Submodule path 'third_party/protobuf': checked out 'd7e943b8d2bc444a8c770644e73d090b486f8b37'
Entering 'third_party/protoc-gen-validate'
Submodule 'third_party/protoc-gen-validate' (https://github.com/envoyproxy/protoc-gen-validate.git) registered for path 'third_party/protoc-gen-validate'
Cloning into '/var/local/git/grpc/third_party/protoc-gen-validate'...
Submodule path 'third_party/protoc-gen-validate': checked out '872b28c457822ed9c2a5405da3c33f386ac0e86f'
Entering 'third_party/re2'
Submodule 'third_party/re2' (https://github.com/google/re2.git) registered for path 'third_party/re2'
Cloning into '/var/local/git/grpc/third_party/re2'...
Submodule path 'third_party/re2': checked out 'aecba11114cf1fac5497aeb844b6966106de3eb6'
Entering 'third_party/udpa'
Submodule 'third_party/udpa' (https://github.com/cncf/udpa.git) registered for path 'third_party/udpa'
Cloning into '/var/local/git/grpc/third_party/udpa'...
Submodule path 'third_party/udpa': checked out 'cc1b757b3eddccaaaf0743cbb107742bb7e3ee4f'
Entering 'third_party/zlib'
Submodule 'third_party/zlib' (https://github.com/madler/zlib) registered for path 'third_party/zlib'
Cloning into '/var/local/git/grpc/third_party/zlib'...
Submodule path 'third_party/zlib': checked out 'cacf7f1d4e3d44d871b605da3b647f07d718623f'
go: cannot find main module, but found .git/config in /var/local/git/grpc
	to create a module there, run:
	cd ../.. && go mod init

Seen in: https://github.com/grpc/grpc/pull/25672

Duplicate of #25660.


config: skip some rocksdb config

What have you changed?
This pr skip some config, these config on the rocksdb config struct are not support dynamic change because these config neither real rocksdb config (can not recognize by rocksdb) or not support dynamic change by rocksdb. This pr also rename dynamic-config to enable-dynamic-config
What is the type of the changes?

Bugfix (a change which fixes an issue)
Engineering (engineering change which doesn't change any feature or fix any issue)

How is the PR tested?
No
Does this PR affect documentation (docs) or should it be mentioned in the release notes?
No
Does this PR affect tidb-ansible?
No

/run-all-tests


Power BI File Fails to connect to Pricing API

The Linked Power BI template does not work, the included URL's within the BI template, fail (error 400)
Error:
DataSource.Error: Web.Contents failed to get contents from 'https://prices.azure.com/api/retail/prices?currencyCode='GBP'&$filter=
(indexof(location, ' ') ne -1 or location eq 'Global' or location eq '')%20%0Aand%20indexof(serviceName,%20'Virtual%20Machines')%20ne%20-1%20%0Aand%20indexof(productName,%20'%20Series')%20ne%20-1%0Aand%20indexof(productName,%20'%20Dedicated')%20eq%20-1%0Aand%20priceType%20eq%20'Consumption'%20%0Aand%20indexof(skuName,%20'Spot')%20eq%20-1%20%0Aand%20indexof(meterName,'Expired')%20eq%20-1%20%0Aand%20indexof(meterName,'Low%20Priority')%20eq%20-1%20%0Aand%20indexof(meterName,%20'Promo')%20eq%20-1' (400): Bad Request
https://raw.githubusercontent.com/microsoft/CloudAdoptionFramework/master/strategy/azure-virtual-machine-cost-estimator.pbix

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

ID: 42f8649e-4a66-2667-b4c7-88698cf5183f
Version Independent ID: ce9e86a7-423d-7177-685d-ed9f426940b5
Content: Create a business case - Cloud Adoption Framework
Content Source: docs/strategy/cloud-migration-business-case.md
Service: cloud-adoption-framework
Sub-service: strategy
GitHub Login: @WendyRing
Microsoft Alias: wering

@adamswbrown - apologies for the delayed response and thanks very much for this contribution.
We're not able to repro the 400 error nor the ones reported since you opened this issue. I've also reported this to the author of the template in the event that it's been updated/resolved since then, or if these are known issues that have a workaround, or should be documented. We'll update this issue if/when we get updates from the author, and please also feel free to update with any additional repro info you might have or status updates..
#please-close


Fix unsound Clone and undefined behavior in self-referential Buf variants

TemplateBuf and ByteTemplate are implemented as self-referential structs, but their current implementation is unsound and contains undefined behavior.
According to my analysis the following issues exists:

The derived Clone implementations by the compiler are unsound, as they copy the static reference by value, causing all kinds of memory issues (panics due to memory issues caused my investigation.)
As field order of structs determines the drop order, the underlying String  or Vec<u8> will be dropped before the reference, this UB according to my understanding, as there will be dangling reference.
String and Vec<u8> are implemented using core::ptr::Unique. As such all references to such a type, are invalidated, if such a type is moved. See Self-referential types for fun and profit by @hniksic for details

This PR tries to address these issues.

I've included a small test to reproduce the first issue.
The fixes for the first two points are rather self-explanatory.
For the last issue I've implemented the aliasable::String and aliasable::Bytes types instead of pulling in an extra dependency like the aliasable crate.
I've checked my changes, by running the tests with miri. It passes but requires tree-borrows (MIRIFLAGS="-Zmiri-tree-borrows").

String and Vec<u8> are implemented using core::ptr::Unique. As such all references to such a type, are invalidated, if such a type is moved. See Self-referential types for fun and profit by @hniksic for details

What about references to the data that are stored inside a union? miri doesn't complain anymore when I do that, but I'm not sure if it's truly sound >.<

I've opened #30 with a different approach to solving the aliasing problem. Rather than swapping Vec with a custom implementation, that approach wraps the Template that holds the references in MaybeUninit. More details available at that PR.
The main motivation for the alternative approach is that it's less extra unsafe code compared to aliasable::Byte/String. It also doesn't need extra miri flags to pass the tests.

Merging without the last commit.
Thanks again! This was a really important fix 😬

I've opened #30 with a different approach to solving the aliasing problem. Rather than swapping Vec with a custom implementation, that approach wraps the Template that holds the references in MaybeUninit. More details available at that PR.
The main motivation for the alternative approach is that it's less extra unsafe code compared to aliasable::Byte/String. It also doesn't need extra miri flags to pass the tests.

I'm not familiar enough with aliasing guarantees/details around MaybeUnit to judge this approach.
Thank you for your quick action and your work in general too!


Providing candidate fq files as input

Hi,
When starting genotyping from stage 1 or stage2, the program is looking for the candidate fq files by trying to infer the name from the output directory and prefix. It would be useful to be able to specify where these candidate fq files are as an input argument instead, so that the outputs could be saved in different directories (e.g. for when testing different cov/frac options).
I think there is currently no such input option? Apologies if I've missed it.
Cheers,
Loukas

Could you please try the "--noExtraction" option? Then it should directly use the candidate fq files in other directories.

Thank you very much for the rapid response!
I used the --noExtraction option and specified candidate reads fq files with -1 and -2 and it works fine indeed.
Cheers,
Loukas


Fixed navbar font

Fixes #52

@ishitakapoor26 Please do check and merge!

Good job. Keep Contributing!


Implement cli_runner fixture for test_cli.py

This makes it even easier to write CLI tests. 😂
Currently:
result = runner.invoke(main, ['--verbose', template])

With this PR:
result = cli_runner('--verbose', template)

Current coverage is 100% (diff: 100%)

Merging #790 into master will not change coverage

@@           master   #790   diff @@
====================================
  Files          15     15
  Lines         601    601
  Methods         0      0
  Messages        0      0
  Branches        0      0
====================================
  Hits          601    601
  Misses          0      0
  Partials        0      0

Powered by Codecov. Last update 0301bf6...9de7f66

👌

Thanks man! 🙇


sync all change from upstream for code freeze rhoai-2.8

sync all change from upstream for code freeze rhoai-2.8
Related-JIRA:
https://issues.redhat.com/browse/RHOAIENG-1848

Merging to get the code-freeze ready.