Question re removing / filtering fields

My app uses redux-form to handle the state of multiple forms at once in a dashboard; each form has its name passed in at render time.  We also dynamically add and remove fields.  It's a fairly complex setup.
Desired behavior
I would like to implement behavior such that when fields with certain characteristics are added to the form, it automatically 1) adds additional fields with pre-filled values to the form, and 2) removes other fields, matching certain conditions, if those are present.  Contrived example: when a field animal_type: dog is added, we remove any cat-related fields currently in the form and add some dog-specific fields.
Approaches considered
We've considered a few.  One involves using reducer.plugin() to plug in a reducer that will perform all these additional state changes when needed.  The apparent blocker here is that we seemingly need to know the name of the form prior to runtime in order to use plugin(), and as mentioned above, we generate the form names on render.
Another approach would be to use a custom action for adding field values which would also dispatch the appropriate arrayPush and arrayRemove actions when the conditions are met.  The blocker here is that arrayRemove requires the index of the fields we wish to remove.  We can find the fields we want to remove in the form state, but when removing more than one field, the indexes will change.  We can start with the latest index number and work back, but this feels hacky.  It seems like what we want here is something like arrayFilter.
Is there a recommended way of accomplishing this? Anyone doing something similar? Happy to provide more details!

This was meant for redux-form.

Just for comparison sake:

adds additional fields with pre-filled values to the form

// in an onClick handler, or wherever else:
dispatch(actions.change('animals', animals => [
  ...animals,
  { animal_type: 'dog', name: 'New doggo 1' },
  { animal_type: 'dog', name: 'New doggo 2' },
  { animal_type: 'dog', name: 'New pupper 3' }
]));

removes other fields, matching certain conditions, if those are present.

// in an onClick handler, or wherever else:
dispatch(actions.filter('animals', ({ animal_type }) => animal_type !== 'cat'));

And this works 100% as you would expect with dynamic fields 🐶

Hey, thanks for the comp! 😺  react-redux-form was actually my initial choice for what we're doing, but I went with redux-form for various reasons.  Could be worth revisiting.


Possible mechanisms for temporary access

There exists the need in the community to easily share private ARCs without the need to sign up. The prime use case here is that potential reviewers of a paper need to have access to an associated ARC, but do not have (or not want) an nfdi4plants account.
My first idea would be a mechanism that creates a temporary user that has read-only access to the selected ARC.
Gitlab seems to provide a Guest role, so maybe that is the way to go? https://docs.gitlab.com/ee/administration/guest_users.html
Thoughts @muehlhaus @j-bauer ?

cc @HLWeil

It seems, that the Guest users are only available in the GitLab ultimate (paid) tier. But there is something similar called External users. But I don't know if the user creation can somehow be automated with Keycloak.  @j-bauer can you maybe have a look?

related to #23

Unfortunately, paper peer-review is typically anonymous. So I doubt they'd like to login with personal credentials.


avoid Calls inside While/Cond

The first commit here was an attempt at fixing #1267, which didn't really work but is probably still a good cleanup to apply.
The other commits represent a temporary workaround for the facts that

when the PRNG hash function loops are unrolled, XLA:CPU compile time is too slow
when the PRNG hash function loops are rolled, the XLA:GPU execution time is too slow

It seems that avoiding the Call inside While wasn't enough to fix the performance regression in #1267, but unrolling the loops in the PRNG hash function (i.e. undoing #1175) seems to fix it (see #1267 for some numbers).

Here's a colab where I tested the roll/unroll behavior of 2815c55 on CPU/GPU (switching the backend and restarting the runtime in the interim).
 I think that may just be noise).


Scintilla control for Eto.Forms

Hi,
I have been drafting an Eto.Forms implementation of the Scintilla.NET wrapper. The process looks quite good on my opinion with the possibility to use the control as with WinForms. I don't have any experience with macOS nor any idea of how to implement the control to the macOS. The source code here doesn't compile on Mac - it seems to have been partially implemented though - can someone point me to the right direction with the macOS version so I could make the library support all three operating systems? I would only need a decent start / demo project to go further from there. Thanks 🙂

I think you meant to post this to the Eto.Toolkit repo, where there is already an implementation of a CodeEditor control based on Scintilla for WPF and Mac platforms.

I did - thank you, too many tabs open while searching for solution.


Missing feature from planning list

Describe the bug
I have an epic with several features associated with it. All but one feature is displaying in the plan features pane. I've confirmed the feature is properly associated with the parent, in the backlog iteration, is not closed, has its own children configured correctly. All other features seem to be displaying.
Browser
Choose a browser
[ ] IE11
[x ] Chrome
[ ] FireFox
[ ] Safari
Version
[ x] VSTS
[ ] TFS 2017 Update 2/3
[ ] TFS 2018
Screenshots

Thanks @GreenDavidA  for reporting the issue. Is the feature in same Area Path and Project as other features?
Also how many total features you see in the Planning Pane, I believe we show only first 200 unplanned items in the planning pane.

They are all in the same project and area path. It may be close to 200 features. What is the sort order? This feature was newer than others, but I moved towards of the top of the backlog.

Can we setup a quick Skype meeting to go over the details and do some live debugging? Please send an email to<EMAIL_ADDRESS>if you are available.

Was this ever resolved. I am having exactly the same problem. Thanks

I am still looking for a repro ... will you have time for a skype call?

Yea sure – can you do it now?
Best regards,
Dr Arji Bhogal
Engineering Manager
[w2logo]
Clarence House, Clarence Place, Newport, NP19 7AA
Tel:+44 (0)330 088 9542
Skype For Business<EMAIL_ADDRESS>Web: www.w2globaldata.comhttp://www.w2globaldata.com/
Technical Support: support<EMAIL_ADDRESS>Subscribe to our newsletterhttps://w2globaldata.us12.list-manage.com/subscribe?u=4d6f5011ee8abd9b9c4da1f63&id=9d4b1c48de
<EMAIL_ADDRESS>The information contained in this electronic message is confidential. It is intended solely for the use of to whom it is addressed and others authorised to receive it. If the reader of this message is not the intended recipient you are hereby notified that any use, copying, dissemination or disclosure of this information is strictly prohibited and are asked to delete it immediately and notify the sender. If you require any further details please call +44 (0)330 088 9542
From: NAVNEET GUPTA<EMAIL_ADDRESS>Sent: 03 August 2018 07:54
To: Microsoft/featuretimeline<EMAIL_ADDRESS>Cc: Arji Bhogal<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [Microsoft/featuretimeline] Missing feature from planning list (#21)
I am still looking for a repro ... will you have time for a skype call?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Ffeaturetimeline%2Fissues%2F21%23issuecomment-410162503&data=02|01|arji.bhogal%40w2globaldata.com|d14e8df910ff41aacaa008d5f90de07b|fb467507ea414c558d90608578f8f97b|0|0|636688760372866373&sdata=%2BWF5RyyLPByntxPuAN3eu0Yu4hmfOMwwJ3UBGwqTFEE%3D&reserved=0, or mute the threadhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAmyPKVXoz8BYQgXDlmdFzK7ISGuqll7jks5uM_N_gaJpZM4VU03_&data=02|01|arji.bhogal%40w2globaldata.com|d14e8df910ff41aacaa008d5f90de07b|fb467507ea414c558d90608578f8f97b|0|0|636688760372876386&sdata=Rc%2B8konsUULXESwExX35TWkHWiM6veoxr1CCCd1SEok%3D&reserved=0.

I don't know if you were able to get the Skype call from the other user or if you still need assistance. Do you need anything further from me?

I think I might have figured out why I couldn't get it to appear. After looking at the code, it appears that the plan list filters out active features, and I'm pretty sure that the feature that was missing was active at the time. I'll keep an eye on this to see if I observe it happening again.

Thanks David, Sorry I haven't responded until now. The feature that was missing for us, was below the top 100 threshold and did not appear. Re-ordering the features so the inflight ones were at the top sorted the issue out. Active features have always appeared for us.

I have increased the limit to 300, hopefully that will be useful in future. Please reopen the issue if you see any problems.


WIP - MINIFICPP-1253 - Do not apply backpressure on self-loops

WORK IN PROGRESS not ment to be merged

Thank you for submitting a contribution to Apache NiFi - MiNiFi C++.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[ ] Does your PR title start with MINIFICPP-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[ ] Has your PR been rebased against the latest commit within the target branch (typically master)?

[ ] Is your initial contribution a single, squashed commit?

For code changes:

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file?
[ ] If applicable, have you updated the NOTICE file?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

closed in favor of proper solution


Task one completed

Don't push the env folder to github. Check the following for more: https://stackoverflow.com/questions/51863155/do-we-need-to-upload-virtual-env-on-github-too


Ankimote fails if Google Analytics cannot be reached

I get the following error when I connect (though it still connects fine) and it errors whenever I try use the remote, then does nothing.
Anki encountered a problem. Please follow the troubleshooting steps.
Add-ons possibly involved: Ankimote
Debug Info:
Anki 23.12.1 (1a1d4d54)  (ao)
Python 3.9.15 Qt 6.6.1 PyQt 6.6.1
Platform: Windows-10-10.0.22631

Traceback (most recent call last):
  File "urllib3.connection", line 203, in _new_conn
  File "urllib3.util.connection", line 60, in create_connection
  File "socket", line 954, in getaddrinfo
socket.gaierror: [Errno 11004] getaddrinfo failed

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "urllib3.connectionpool", line 790, in urlopen
  File "urllib3.connectionpool", line 496, in _make_request
  File "urllib3.connection", line 395, in request
  File "http.client", line 1280, in endheaders
  File "http.client", line 1040, in _send_output
  File "http.client", line 980, in send
  File "urllib3.connection", line 243, in connect
  File "urllib3.connection", line 210, in _new_conn
urllib3.exceptions.NameResolutionError: <urllib3.connection.HTTPConnection object at 0x0000011663099100>: Failed to resolve 'www.google-analytics.com' ([Errno 11004] getaddrinfo failed)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "requests.adapters", line 486, in send
  File "urllib3.connectionpool", line 844, in urlopen
  File "urllib3.util.retry", line 515, in increment
urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='www.google-analytics.com', port=80): Max retries exceeded with url: /collect (Caused by NameResolutionError("<urllib3.connection.HTTPConnection object at 0x0000011663099100>: Failed to resolve 'www.google-analytics.com' ([Errno 11004] getaddrinfo failed)"))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:\Users\Lily\AppData\Roaming\Anki2\addons21\ankimote\__init__.py", line 266, in handleMessage
    requests.post("http://www.google-analytics.com/collect", data=payloadAnsCard)
  File "requests.api", line 115, in post
  File "requests.api", line 59, in request
  File "requests.sessions", line 589, in request
  File "requests.sessions", line 703, in send
  File "requests.adapters", line 519, in send
requests.exceptions.ConnectionError: HTTPConnectionPool(host='www.google-analytics.com', port=80): Max retries exceeded with url: /collect (Caused by NameResolutionError("<urllib3.connection.HTTPConnection object at 0x0000011663099100>: Failed to resolve 'www.google-analytics.com' ([Errno 11004] getaddrinfo failed)"))

===Add-ons (active)===
(add-on provided name [Add-on folder, installed at, version, is config changed])
Additional Card Fields Fork for 21 ['744725736', 2022-10-23T11:10, 'None', '']
AnkiConnect ['2055492159', 2024-02-27T04:37, 'None', '']
AnkiWebView Inspector ['31746032', 2023-06-27T20:26, 'None', '']
Ankimote ['ankimote', 0, 'None', '']
CrowdAnki JSON exportimport Edit history Collaborate on deck creation ['1788670778', 2023-10-30T18:57, 'None', '']
FSRS4Anki Helper ['759844606', 2024-04-16T05:00, 'None', mod]
ImageResizer ['1214357311', 2023-12-03T01:58, 'None', '']
More Overview Stats 21 ['738807903', 2021-07-30T20:13, 'None', '']
Review Heatmap ['1771074083', 2022-06-30T02:43, 'None', '']

===IDs of active AnkiWeb add-ons===
1214357311<PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER> 31746032 738807903 744725736 759844606

===Add-ons (inactive)===
(add-on provided name [Add-on folder, installed at, version, is config changed])

The addon errors and doesn't function if it cannot reach www.google-analytics.com, which I have blocked.
I forked this repo to remove the tracking for anyone else with this issue: https://github.com/iamasink/ankimote.
It'd be nice to see an opt out and for it to fail silently, though!

The addon errors and doesn't function if it cannot reach www.google-analytics.com, which I have blocked. I forked this repo to remove the tracking for anyone else with this issue: https://github.com/iamasink/ankimote. It'd be nice to see an opt out and for it to fail silently, though!

Thankyou!!! work perfectly!


Repatch default params in manager.py

Repatch commit 7e00e93f2c8a5, modified for production use by not
setting the default values for terms, setup and training.

Yep


Test go 1.15 in CI

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.

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

Test name
Commit
Details
Rerun command

lint_istio
50662df15cf8a69e679d3c73cf8cc28928acadbe
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
50662df15cf8a69e679d3c73cf8cc28928acadbe
link
/test lint_istio

release-notes_istio
50662df15cf8a69e679d3c73cf8cc28928acadbe
link
/test release-notes_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
50662df15cf8a69e679d3c73cf8cc28928acadbe
link
/test lint_istio

release-notes_istio
d6a97c1c598c46bc6340f634889dc7dfc813d754
link
/test release-notes_istio

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
d6a97c1c598c46bc6340f634889dc7dfc813d754
link
/test release-notes_istio

lint_istio
d6a97c1c598c46bc6340f634889dc7dfc813d754
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
d6a97c1c598c46bc6340f634889dc7dfc813d754
link
/test lint_istio

release-notes_istio
299cfe074ee3c4ad55a6ea8365a2cf04afc84fde
link
/test release-notes_istio

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

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

Test name
Commit
Details
Rerun command

release-notes_istio
299cfe074ee3c4ad55a6ea8365a2cf04afc84fde
link
/test release-notes_istio

lint_istio
299cfe074ee3c4ad55a6ea8365a2cf04afc84fde
link
/test lint_istio

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

/test benchmark_istio

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

Test name
Commit
Details
Rerun command

release-notes_istio
299cfe074ee3c4ad55a6ea8365a2cf04afc84fde
link
/test release-notes_istio

lint_istio
3b1a4afdb1639555fe9efb2e54bab4e3254aaceb
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
3b1a4afdb1639555fe9efb2e54bab4e3254aaceb
link
/test lint_istio

release-notes_istio
3b1a4afdb1639555fe9efb2e54bab4e3254aaceb
link
/test release-notes_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
3b1a4afdb1639555fe9efb2e54bab4e3254aaceb
link
/test lint_istio

release-notes_istio
3b1a4afdb1639555fe9efb2e54bab4e3254aaceb
link
/test release-notes_istio

integ-pilot-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-pilot-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
3b1a4afdb1639555fe9efb2e54bab4e3254aaceb
link
/test lint_istio

release-notes_istio
3b1a4afdb1639555fe9efb2e54bab4e3254aaceb
link
/test release-notes_istio

integ-pilot-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-telemetry-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
3b1a4afdb1639555fe9efb2e54bab4e3254aaceb
link
/test lint_istio

release-notes_istio
3b1a4afdb1639555fe9efb2e54bab4e3254aaceb
link
/test release-notes_istio

integ-pilot-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-security-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
3b1a4afdb1639555fe9efb2e54bab4e3254aaceb
link
/test lint_istio

release-notes_istio
3b1a4afdb1639555fe9efb2e54bab4e3254aaceb
link
/test release-notes_istio

integ-pilot-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-security-k8s-tests_istio

integ-distroless-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-distroless-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
3b1a4afdb1639555fe9efb2e54bab4e3254aaceb
link
/test lint_istio

release-notes_istio
3b1a4afdb1639555fe9efb2e54bab4e3254aaceb
link
/test release-notes_istio

integ-pilot-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-security-k8s-tests_istio

integ-distroless-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-distroless-k8s-tests_istio

analyze-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test analyze-tests_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
3b1a4afdb1639555fe9efb2e54bab4e3254aaceb
link
/test lint_istio

release-notes_istio
3b1a4afdb1639555fe9efb2e54bab4e3254aaceb
link
/test release-notes_istio

integ-pilot-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-security-k8s-tests_istio

integ-distroless-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-distroless-k8s-tests_istio

analyze-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test analyze-tests_istio

integ-ipv6-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-ipv6-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
3b1a4afdb1639555fe9efb2e54bab4e3254aaceb
link
/test lint_istio

release-notes_istio
3b1a4afdb1639555fe9efb2e54bab4e3254aaceb
link
/test release-notes_istio

integ-pilot-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-security-k8s-tests_istio

integ-distroless-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-distroless-k8s-tests_istio

analyze-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test analyze-tests_istio

integ-ipv6-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-ipv6-k8s-tests_istio

gencheck_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test gencheck_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
3b1a4afdb1639555fe9efb2e54bab4e3254aaceb
link
/test lint_istio

integ-pilot-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-security-k8s-tests_istio

integ-distroless-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-distroless-k8s-tests_istio

analyze-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test analyze-tests_istio

integ-ipv6-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-ipv6-k8s-tests_istio

gencheck_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test gencheck_istio

release-notes_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test release-notes_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
3b1a4afdb1639555fe9efb2e54bab4e3254aaceb
link
/test lint_istio

integ-pilot-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-security-k8s-tests_istio

integ-distroless-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-distroless-k8s-tests_istio

analyze-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test analyze-tests_istio

integ-ipv6-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-ipv6-k8s-tests_istio

gencheck_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test gencheck_istio

release-notes_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test release-notes_istio

integ-operator-controller-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-operator-controller-tests_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
3b1a4afdb1639555fe9efb2e54bab4e3254aaceb
link
/test lint_istio

integ-pilot-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-security-k8s-tests_istio

integ-distroless-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-distroless-k8s-tests_istio

analyze-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test analyze-tests_istio

integ-ipv6-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-ipv6-k8s-tests_istio

gencheck_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test gencheck_istio

release-notes_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test release-notes_istio

integ-operator-controller-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-operator-controller-tests_istio

integ-multicluster-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-multicluster-k8s-tests_istio

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

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

Test name
Commit
Details
Rerun command

lint_istio
3b1a4afdb1639555fe9efb2e54bab4e3254aaceb
link
/test lint_istio

integ-pilot-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-security-k8s-tests_istio

integ-distroless-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-distroless-k8s-tests_istio

analyze-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test analyze-tests_istio

integ-ipv6-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-ipv6-k8s-tests_istio

gencheck_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test gencheck_istio

release-notes_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test release-notes_istio

integ-operator-controller-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-operator-controller-tests_istio

integ-multicluster-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-multicluster-k8s-tests_istio

release-test_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test release-test_istio

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

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

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-security-k8s-tests_istio

integ-distroless-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-distroless-k8s-tests_istio

analyze-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test analyze-tests_istio

integ-ipv6-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-ipv6-k8s-tests_istio

gencheck_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test gencheck_istio

release-notes_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test release-notes_istio

integ-operator-controller-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-operator-controller-tests_istio

integ-multicluster-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-multicluster-k8s-tests_istio

release-test_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test release-test_istio

lint_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-pilot-k8s-tests_istio

integ-security-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-security-k8s-tests_istio

integ-distroless-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-distroless-k8s-tests_istio

analyze-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test analyze-tests_istio

integ-ipv6-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-ipv6-k8s-tests_istio

gencheck_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test gencheck_istio

release-notes_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test release-notes_istio

integ-operator-controller-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-operator-controller-tests_istio

integ-multicluster-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-multicluster-k8s-tests_istio

release-test_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test release-test_istio

lint_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test lint_istio

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

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

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

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-pilot-k8s-tests_istio

integ-security-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-security-k8s-tests_istio

analyze-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test analyze-tests_istio

integ-ipv6-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-ipv6-k8s-tests_istio

gencheck_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test gencheck_istio

release-notes_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test release-notes_istio

integ-operator-controller-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-operator-controller-tests_istio

integ-multicluster-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-multicluster-k8s-tests_istio

release-test_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test release-test_istio

lint_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test lint_istio

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

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

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

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

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-pilot-k8s-tests_istio

integ-security-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-security-k8s-tests_istio

analyze-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test analyze-tests_istio

gencheck_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test gencheck_istio

release-notes_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test release-notes_istio

integ-operator-controller-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-operator-controller-tests_istio

integ-multicluster-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-multicluster-k8s-tests_istio

release-test_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test release-test_istio

lint_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test lint_istio

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

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

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

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

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

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-pilot-k8s-tests_istio

integ-security-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-security-k8s-tests_istio

analyze-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test analyze-tests_istio

gencheck_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test gencheck_istio

release-notes_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test release-notes_istio

integ-operator-controller-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-operator-controller-tests_istio

integ-multicluster-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-multicluster-k8s-tests_istio

release-test_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test release-test_istio

lint_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test lint_istio

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

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

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

unit-tests_istio
b39a96dce62cd267a064f81a0c8c054123fedaa5
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-pilot-k8s-tests_istio

integ-security-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-security-k8s-tests_istio

analyze-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test analyze-tests_istio

gencheck_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test gencheck_istio

release-notes_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test release-notes_istio

integ-operator-controller-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-operator-controller-tests_istio

integ-multicluster-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-multicluster-k8s-tests_istio

release-test_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test release-test_istio

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

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

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

unit-tests_istio
b39a96dce62cd267a064f81a0c8c054123fedaa5
link
/test unit-tests_istio

lint_istio
b39a96dce62cd267a064f81a0c8c054123fedaa5
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-pilot-k8s-tests_istio

integ-security-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-security-k8s-tests_istio

analyze-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test analyze-tests_istio

gencheck_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test gencheck_istio

release-notes_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test release-notes_istio

integ-multicluster-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-multicluster-k8s-tests_istio

release-test_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test release-test_istio

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

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

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

unit-tests_istio
b39a96dce62cd267a064f81a0c8c054123fedaa5
link
/test unit-tests_istio

lint_istio
b39a96dce62cd267a064f81a0c8c054123fedaa5
link
/test lint_istio

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

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

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-security-k8s-tests_istio

analyze-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test analyze-tests_istio

gencheck_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test gencheck_istio

release-notes_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test release-notes_istio

integ-multicluster-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-multicluster-k8s-tests_istio

release-test_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test release-test_istio

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

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

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

unit-tests_istio
b39a96dce62cd267a064f81a0c8c054123fedaa5
link
/test unit-tests_istio

lint_istio
b39a96dce62cd267a064f81a0c8c054123fedaa5
link
/test lint_istio

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

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

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

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-security-k8s-tests_istio

analyze-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test analyze-tests_istio

gencheck_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test gencheck_istio

integ-multicluster-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-multicluster-k8s-tests_istio

release-test_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test release-test_istio

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

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

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

unit-tests_istio
b39a96dce62cd267a064f81a0c8c054123fedaa5
link
/test unit-tests_istio

lint_istio
b39a96dce62cd267a064f81a0c8c054123fedaa5
link
/test lint_istio

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

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

release-notes_istio
b39a96dce62cd267a064f81a0c8c054123fedaa5
link
/test release-notes_istio

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

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test analyze-tests_istio

gencheck_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test gencheck_istio

integ-multicluster-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-multicluster-k8s-tests_istio

release-test_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test release-test_istio

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

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

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

unit-tests_istio
b39a96dce62cd267a064f81a0c8c054123fedaa5
link
/test unit-tests_istio

lint_istio
b39a96dce62cd267a064f81a0c8c054123fedaa5
link
/test lint_istio

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

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

release-notes_istio
b39a96dce62cd267a064f81a0c8c054123fedaa5
link
/test release-notes_istio

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

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

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test analyze-tests_istio

gencheck_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test gencheck_istio

integ-multicluster-k8s-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test integ-multicluster-k8s-tests_istio

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

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

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

unit-tests_istio
b39a96dce62cd267a064f81a0c8c054123fedaa5
link
/test unit-tests_istio

lint_istio
b39a96dce62cd267a064f81a0c8c054123fedaa5
link
/test lint_istio

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

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

release-notes_istio
b39a96dce62cd267a064f81a0c8c054123fedaa5
link
/test release-notes_istio

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

release-test_istio
b39a96dce62cd267a064f81a0c8c054123fedaa5
link
/test release-test_istio

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

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test analyze-tests_istio

gencheck_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test gencheck_istio

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

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

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

unit-tests_istio
b39a96dce62cd267a064f81a0c8c054123fedaa5
link
/test unit-tests_istio

lint_istio
b39a96dce62cd267a064f81a0c8c054123fedaa5
link
/test lint_istio

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

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

release-notes_istio
b39a96dce62cd267a064f81a0c8c054123fedaa5
link
/test release-notes_istio

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

release-test_istio
b39a96dce62cd267a064f81a0c8c054123fedaa5
link
/test release-test_istio

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

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

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test analyze-tests_istio

gencheck_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test gencheck_istio

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

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

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

unit-tests_istio
b39a96dce62cd267a064f81a0c8c054123fedaa5
link
/test unit-tests_istio

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

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

release-notes_istio
b39a96dce62cd267a064f81a0c8c054123fedaa5
link
/test release-notes_istio

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

release-test_istio
b39a96dce62cd267a064f81a0c8c054123fedaa5
link
/test release-test_istio

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

lint_istio
da83009be571d7f745cae475500d9bed8683425f
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test analyze-tests_istio

gencheck_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test gencheck_istio

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

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

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

unit-tests_istio
b39a96dce62cd267a064f81a0c8c054123fedaa5
link
/test unit-tests_istio

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

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

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

release-test_istio
b39a96dce62cd267a064f81a0c8c054123fedaa5
link
/test release-test_istio

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

lint_istio
da83009be571d7f745cae475500d9bed8683425f
link
/test lint_istio

release-notes_istio
da83009be571d7f745cae475500d9bed8683425f
link
/test release-notes_istio

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

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

Test name
Commit
Details
Rerun command

analyze-tests_istio
41532f0990005280493bea40969cbef57ab4b1d5
link
/test analyze-tests_istio

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

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

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

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

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

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

release-test_istio
b39a96dce62cd267a064f81a0c8c054123fedaa5
link
/test release-test_istio

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

lint_istio
da83009be571d7f745cae475500d9bed8683425f
link
/test lint_istio

release-notes_istio
da83009be571d7f745cae475500d9bed8683425f
link
/test release-notes_istio

unit-tests_istio
da83009be571d7f745cae475500d9bed8683425f
link
/test unit-tests_istio

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

Unit test fails as expected until https://github.com/istio/istio/pull/26387

/test benchmark_istio

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

Test name
Commit
Details
Rerun command

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

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

release-test_istio
b39a96dce62cd267a064f81a0c8c054123fedaa5
link
/test release-test_istio

lint_istio
da83009be571d7f745cae475500d9bed8683425f
link
/test lint_istio

release-notes_istio
da83009be571d7f745cae475500d9bed8683425f
link
/test release-notes_istio

unit-tests_istio
da83009be571d7f745cae475500d9bed8683425f
link
/test unit-tests_istio

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

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

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

Test name
Commit
Details
Rerun command

lint_istio
da83009be571d7f745cae475500d9bed8683425f
link
/test lint_istio

release-notes_istio
da83009be571d7f745cae475500d9bed8683425f
link
/test release-notes_istio

unit-tests_istio
da83009be571d7f745cae475500d9bed8683425f
link
/test unit-tests_istio

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

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

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

/test unit-tests_istio

/retest

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

Test name
Commit
Details
Rerun command

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

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

lint_istio
da83009be571d7f745cae475500d9bed8683425f
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

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

lint_istio
da83009be571d7f745cae475500d9bed8683425f
link
/test lint_istio

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

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

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

Test name
Commit
Details
Rerun command

lint_istio
da83009be571d7f745cae475500d9bed8683425f
link
/test lint_istio

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

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

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

/retest

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

Test name
Commit
Details
Rerun command

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

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

lint_istio
da83009be571d7f745cae475500d9bed8683425f
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

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

lint_istio
da83009be571d7f745cae475500d9bed8683425f
link
/test lint_istio

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

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

/retest

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

Test name
Commit
Details
Rerun command

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

lint_istio
da83009be571d7f745cae475500d9bed8683425f
link
/test lint_istio

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

This updated in CI


Link to all rustdocs

Content request
In https://docs.substrate.io/rustdocs/, we should have a third entry

other notable rust-docs in the substrate ecosystem

which points to https://paritytech.github.io/
Are you willing to help with this request?
No.

We instead have moved to only have master referenced, and remove this page, and update the look&feel of https://paritytech.github.io/ and expand what is shown there when referencing anything not rustdoc related


verify_authenticity_token has not been defined

Pre-check

Do not use the issues tracker for help or support, try Stack Overflow.
For bugs, do a quick search and make sure the bug has not yet been reported
If you found a security bug, do not report it through GitHub. Please send an e-mail to<EMAIL_ADDRESS>instead.
Finally, be nice and have fun!

Environment

Ruby [version]
Rails [version]
Devise [version]

Current behavior
Include code samples, errors, steps to reproduce the error and stack traces if appropriate.
Will be even more helpful if you provide a sample application or a test case that reproduces the error.
Expected behavior

Please provide more info if you're still having issues.


[Chip][New feature] Allow setting margin

Hey guys,
After searching the web and looking at the source code I can't find how to set the default margin of Chips. When I watch I can see that the value can't be overwritten with css (except by passing a style object).
This could be cool that we could OR by setting it in the muiTheme.
Thank you for reading me.

@gop-aroy CSS styling will be possible for the next branch. I don't envisage us adding this to the theme. Thanks for the suggestion though.

Nice, thank you. Can't wait for it :)


[Spark-21807][SQL]The getAliasedConstraints function  in LogicalPlan will take a long time when number of expressions is greater than 100

What changes were proposed in this pull request?
The getAliasedConstraints  fuction in LogicalPlan.scala will clone the expression set when an element added,
and it will take a long time. This PR add a function to add multiple elements at once to reduce the clone time.
Before modified, the cost of getAliasedConstraints is:
100 expressions:  41 seconds
150 expressions:  466 seconds
After modified, the cost of getAliasedConstraints is:
100 expressions:  1.8 seconds
150 expressions:  6.5 seconds
The test is like this:
test("getAliasedConstraints") {
val expressionNum = 150
val aggExpression = (1 to expressionNum).map(i => Alias(Count(Literal(1)), s"cnt$i")())
val aggPlan = Aggregate(Nil, aggExpression, LocalRelation())
val beginTime = System.currentTimeMillis()
val expressions = aggPlan.validConstraints
println(s"validConstraints cost: ${System.currentTimeMillis() - beginTime}ms")
// The size of Aliased expression is n * (n - 1) / 2 + n
assert( expressions.size === expressionNum * (expressionNum - 1) / 2 + expressionNum)

}
(Please fill in changes proposed in this fix)
How was this patch tested?
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)
Run new added test.
Please review http://spark.apache.org/contributing.html before opening a pull request.

Can one of the admins verify this patch?

We can edit the PR title and description to show the changes clearly.

ok to test

Test build #81035 has started for PR 19022 at commit 57e8a3d.

Test build #81035 has finished for PR 19022 at commit 57e8a3d.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81035/
Test FAILed.

add to whitelist

Test build #81039 has started for PR 19022 at commit 57e8a3d.

Test build #81039 has finished for PR 19022 at commit 57e8a3d.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81039/
Test FAILed.

Merged build finished. Test FAILed.

Test build #81057 has started for PR 19022 at commit 0762840.

Test build #81057 has finished for PR 19022 at commit 0762840.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81057/
Test PASSed.

LGTM

Thanks! Merging to master.
You can fix this in your future PRs.


feat: Analyzing Reddit Comments Sentiment using MistralAI and LangGraph

Cookbook Pull Request
Description
Added a new cookbook that utilizes MistralAI's large LLM with LangGraph to perform sentiment analysis on Reddit comments.
...
Type of Change
What type of PR is it?

[X] New Cookbook

[X] Notebook File

[X] Does it work on google colab?

[X] Markdown File

[ ] Cookbook Update

[ ] Code Refactoring
[ ] Bug Fix

[ ] README.md Update

[ ] Other (please describe):

Cookbook Checklist:

[X] My code is easy to read and well structured.
[X] I've tagged the versions of any dependency required.
[X] I have performed a self-review of my own code.
[X] I have commented my code, particularly in hard-to-understand areas.
[X] My changes generate no new warnings or errors.

[ ] My changes do not concern the cookbooks.

README.md Checklist

[X] I've added my cookbook to the table.

[ ] My changes do not concern the README file.

Additional Context
Add any other context or screenshots about the feature request here.
TL;DR
Added a new cookbook for analyzing Reddit comments' sentiment using MistralAI and LangGraph.
...

@sophiamyang hopefully i followed everything correctly, happy to tweak based on feedback.
Thanks!


[Docs] Navigation Menu Lists

Current State
The current <ul> and <li> table of contents sidebar is having some trouble.
Screenshot

Contributor Guides and Handbook

📚 Instructions for contributing to documentation

Meshery documentation site and source

🛠 Meshery Build & Release Strategy
🎨 Wireframes and designs for Meshery UI in Figma (open invite)
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

Assign it to me I want to work on it

Thanks, @manzil-infinity180

@manzil-infinity180 any luck so far?

Is this really an issue? I cannot reproduce this. The HTML markup looks fine as well. It looks fine in Firefox 119.0.1:

This issue has been open for some time with no recent activity, unassigning to open it up for new contributors to give it a go.

I tested the sidebar on the firefox 121.0.1, chrome 120.0 and opera 120.0 browsers and I failed to reproduce the error as did @dmarcoux. @leecalcote could you verify whether the problem still occurs?

Thanks for asking... actually, we just got done (yesterday) revamping this behavior, which is much improved, @charleac.
Here's what we really need now: dynamically built menus (not statically built from _data/toc.yml). The queries needed to build a dynamic menu are essentially the same queries found in pages/index.md. These would go into include/sidebar.html, replacing the _data/toc.yaml source. // @iArchitSharma and @vishalvivekm are to have opened an issue on this...

I'm closing this issue as the original item is fixed.


./gradlew :shared:runDebugExecutableMacosArm64 failed on MacOS, finished with non-zero exit value 133

Describe the bug
building chat example successed with :desktopApp:run, but fail with :shared:runDebugExecutableMacosArm64
I haven't modified any code yet
Affected platforms

Other(MacosArm64)

Versions

Kotlin version*: 1.9.20
Compose Multiplatform version*: 1.5.10
OS version(s)* (required for Desktop and iOS issues): Macos 14.1.1 (23B2082)
OS architecture (x86 or arm64): Arm64
JDK (for desktop issues): 17.0.9

To Reproduce

Run ./gradlew :shared:runDebugExecutableMacosArm64

bl@192 chat % ./gradlew :shared:runDebugExecutableMacosArm64

> Configure project :shared
w: The Default Kotlin Hierarchy Template was not applied to 'project ':shared'':
Explicit .dependsOn() edges were configured for the following source sets:
[iosArm64Main, iosMain, iosSimulatorArm64Main, iosX64Main, macosArm64Main, macosMain, macosX64Main]

Consider removing dependsOn-calls or disabling the default template by adding
    'kotlin.mpp.applyDefaultHierarchyTemplate=false'
to your gradle.properties

Learn more about hierarchy templates: https://kotl.in/hierarchy-template

> Task :shared:runDebugExecutableMacosArm64 FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':shared:runDebugExecutableMacosArm64'.
> Process 'command '/Volumes/nvmessd/download/compose-multiplatform-master/examples/chat/shared/build/bin/macosArm64/debugExecutable/shared.kexe'' finished with non-zero exit value 133

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.

Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

For more on this, please refer to https://docs.gradle.org/8.2.1/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.

BUILD FAILED in 840ms
5 actionable tasks: 2 executed, 3 up-to-date

run shared.kexe directly
bl@192 ~ % '/Volumes/nvmessd/download/compose-multiplatform-master/examples/chat/shared/build/bin/macosArm64/debugExecutable/shared.kexe'
zsh: trace trap

Thank you for your bug report! I have reproduced it and is lokking into it.

It is the same bug as -- #3900. It crashes on execution the following function:
@Composable
internal actual fun rememberTextFieldOverscrollEffect(): OverscrollEffect? = null

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


Documentation could be more clear about path based table use (i.e. non hive)

It would appear that many (though not all) delta functions will work on a path based delta table (i.e. non hive) like:
delta.`/path/to/table`
It would be good to have this be a bit more clear in the documentation on the website regarding:

This pattern in general
What works
What does not work

Thanks @mikenac - as we update the Delta documentation, we will work to fix this.  The new docs should be showing up on the delta.io website in the next few weeks.  Much appreciated!


Support for imagePullSecrets

Ideally we can pass in an imagePullSecrets to the job to allow for images from custom docker repositories.

Hi @KnechtionsCoding  , can you please elaborate on how can we pass imagePullSecret to the job without modifying the code?


Minor Bug in date picker's month numbers

I started using this library yesterday and I noticed today that the date picker mismatched the months. I assume that it started counting January as the Oth month because it returns 21st September 2016 as 21/08/2016.

That's covered on the FAQ section of the readme.


add streaming distribution config filter and set-attributes action

Codecov Report

Merging #12 into master will decrease coverage by 0.01%.
The diff coverage is 82.35%.

@@            Coverage Diff             @@
##           master      #12      +/-   ##
==========================================
- Coverage   90.37%   90.36%   -0.02%
==========================================
  Files         294      294
  Lines       32989    33057      +68
==========================================
+ Hits        29815    29873      +58
- Misses       3174     3184      +10

Impacted Files
Coverage Δ

c7n/resources/cloudfront.py
84.35% <82.35%> (-0.53%)
:arrow_down:

c7n/resources/s3.py
84.93% <0.00%> (+0.13%)
:arrow_up:

Continue to review full report at Codecov.

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


Suggestion to make it static

Shouldn't mapper be static as in AutoMapper? I think it would be much easier to use as static.

It would be easier to use indeed, but since a mapper carries its configuration and its mappings it would be like a singleton pattern usage and I don't like it very much due to side effects / testability and so on..

Answers given, closing this one.


pass variable file name into module

I'm trying to pass a variable file name into the module and the build keeps failing.
  {% for image in site.static_files %}     {% if image.path contains 'img/photos' %}     {% assign passingname = '/img/photos/' | append: image.basename | append: image.extname %}

                                                  {% cloudinary passingname  %}

                                     {{ image.basename | replace: "-", " " }}

          {% endif %}         {% endfor %}
I've also tried
{% cloudinary /img/photos/{{image.basename}}{{image.extname}} %}
and
{% cloudinary /img/photos/[image.basename][image.extname] %}
but in both of those cases, the module just created a url with the variable names instead of the variable's contents.
Am I just doing the liquid syntax incorrectly or is this not doable with the gem?
Thanks!

I don't think it's currently possible to use variables.
I'll try to find if there's a way to do that, thanks for asking.

It's possible to pass variable with a string, instead of the path string directly? Thanks and very good job!

I think recent documentation update answers this:
https://github.com/nhoizey/jekyll-cloudinary#liquid-tag-values