--jpeg-ext generates long file names

** Before submitting a bug report, please ensure you are running the most recent version of osxphotos and that the bug is reproducible on the latest version **

osxphotos version
You have the latest version of osxphotos: 0.65.0

Describe the bug
When exporting with the following options
osxphotos export
--update
--cleanup
--ramdb
--jpeg-ext jpeg
--filename '{created.date}_{created.hour}.{created.min}.{created.sec}'
--directory '{edited?{edited_version?Collection,Originals},Collection}/{created.year}/{created.mm}'
--touch-file
--sidecar XMP
--keyword-template '{favorite?Favorite,}'
--keyword-template '{photo.hidden?Private,}'
--library '/Users/username/Pictures/Photos Library.photoslibrary'
/targetdir
I get an error
Error exporting photo (DD440259-2C03-4618-B132-A900056D4947: IMG_1087.JPG) as 2022-10-13_11.14.26.jpeg: [Errno 63] File name too long: '//Collection/2022/10/2022-10-13_11.14.26 (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).jpeg'
The following checks were made:

There is no file starting with 2022-10-13_11.14.26 in the target directory
if the option --jpeg-ext jpeg is removed the export concludes with no error, in this case the file is exported with extension JPG

To Reproduce
Not sure probably is something with my Library - if helpful I could run some specific tests
Expected behavior
file is exported as "2022-10-13_11.14.26.jpeg"
Screenshots
Desktop (please complete the following information):

OS: [e.g. which version of macOS] Sonoma 14.1.2
osxphotos version (osxphotos --version)
You have the latest version of osxphotos: 0.65.0

Additional context

I am not sure but possibly the picture is "special" as it comes from a DSLR Camera and maybe had also a Raw file that I later deleted. In case it helps.

While @RhetTbull comes back to you on this topic.
What if you just run a simple test and try with --name IMG_1087 into an empty /test_target_dir just to make sure it's specific to this pic and rule out other causes.

@finestream does this happen with all images or only this one? Are the other images being exported correctly?

Also, as @oPromessa recommended above, it would be good to export just this one photo using the --name option both with and without the --jpeg-ext option to see if there's any difference.

While @RhetTbull comes back to you on this topic.
What if you just run a simple test with all your parameters and try with --name IMG_1087 into an empty /test_target_dir just to make sure it's specific to this pic and rule out other causes.

Exporting only this picture to an empty folder works properly.
Running the same command with a new directory target works properly
I also fully deleted the previous export and re-run it and works properly.

I am assuming something went corrupted on my export tree and given I can't reproduce any longer I would suggest closing the issue.
For the record @RhetTbull it happened for 8 images, all from the same camera and shooting session. Other pictures from the same session were working properly.
Thank you very much for the quick reaction time and halp!

I've just looked at the code that increments the filename and I cannot find anything obvious that would cause this. One more test to run is to run your same command again but this time add --debug between osxphotos and export: osxphotos --debug export [...rest of your options].  This will cause osxphotos to crash when it encounters the error instead of continuing on. When it crashes it will write a crash log osxphotos_crash.log when you can then post here or send to me. This will contain useful info on exactly where the error is happening.

Also after a re-running the comment and performing an --update, it still worked as expected. Thank you.

@finestream OK, I will close the issue. Glad it's working. If it happens again feel free to re-open. Is the target directory on a network drive by chance? It could be a network error caused the code which checks to see if a file is already in the export folder to fail.


Update azure-cli-reference-for-storage.md

To add the information which protocol is used to make the request to Azure Storage from AZCLI
++AZ CLI makes a request over HTTP/HTTPS to Azure Storage. By default, every resource in Azure Storage is secured, and every request to a secure resource must be authorized.

@Ramyaharinarthini, Thank you for your informative tip.  I've added a link to Authorize access to data in Azure Storage in the See also section via PR 3607


New element: PhotoElement

Element for display photo

https://github.com/mocircle/cidrawing/commit/b60479209975a3cad50b3a83736fc284ea958a9b


BUG: Issues in navbar light/dark mode

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?

navbar is not sticky.

In light mode, when scrolling, the navbar is becoming like dark mode which should not happen.

Toggle button is also not functioning properly.

in light mode, a moon icon should be present to indicate "change to dark theme" but it is only a sun icon. Toggling of the icons is not happening.
I want to fix all these issues, @anuragverma108  @huamanraj  @RitiChandak Please assign to me under GSSoC'24.
Thank you.

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

I want to contribute on this issue. Can you assign it to me ??

@anuragverma108 @huamanraj @RitiChandak please look into this issue, as this has not been assigned yet, but a PR has been made.

@Madhuri36
Assigned!
Make sure to attach before & after screenshots in your PR.

@Gaurav-Kushwaha-1225
Issues are assigned on a first-come, first-served basis. If a contributor doesn't contribute within 1 week, it will be reassigned to the next person who requested it. You can wait or find another bug/feature to contribute to. Thank you!


Contributing

I have a set of patches that I'd like to see in the 7.x branch of the package. What is the process for getting new code into a specific branch? Is it ported from 7.x to master or does it go from master to 7.x?

Hi @geoffmore , sorry for a delayed response. The workflow being used is to work inside master, and then backport into 7.x and 6.x branches (there's a Make target for that). Note that the esapi package is an exception, since the API is generated from the specification, not written manually.


Enhance OpenEBS logger to collect systemd (kubelet) logs on the nodes

What this PR does / why we need it:

Currently, the stern based debug job only collects the (specified) pod logs. However, the host's systemd logs (kubelet) are necessary to complete the debug picture. This PR provides a way to achieve the same.

How does this change address the issue

The debug job uses a nodelogger daemonset (DS) which is based on Heptio's sonobuoy-systemd-logs container to collect the node logs. This is launched from within the openebs/logger pod after collection of pods logs.

The sonobuoy-systemd-logs container chroots into the node directory and performs the journalctl commands to get these logs.

Which issue this PR fixes

Partially-fixes https://github.com/openebs/openebs/issues/1224

What side effects does this change have?

None on OpenEBS itself. However, the nodelogger runs privileged containers which is a necessary requirement to get the logs. This daemonset is killed immediately after the logs are obtained.

Special notes for your reviewer:
The following considerations were made while making the changes in this PR:
1. The nodelogger has to be a once-run daemonset

There is a need to continue on the existing debugjob philosophy where the job runs for a definite period (mostly on-demand by user) collects the required logs and exits.

However, the node logs need a daemonset to be run to capture it on all nodes, i.e., a once-run DS. In other words a job that runs on all the nodes.

However this is till an open requirement in kubernetes (https://github.com/kubernetes/kubernetes/issues/36601). Daemonsets currently run forever. As a result, the logger script has been enhanced to look for completion of the log collection and kill/delete the DS once done
Note: Keeping it running will cause overwrite of the existing logs. Also users wont prefer to run this
as this solution is not meant to be a constant log capture mechanism like fluentd (which is also typically  DS)

2. Create an RBAC policy (separate sa, clusterrole, clusterrolebinding) for the debugjob

Based on the precondition that the nodelogger has to be run from within the debugjob (Running
it outside would mean creating some kind of wrapper scripts with logic to track launch and completion of both the job and ds)

Running the DS from within the logger pod (debugjob) needs RBAC (daemonsets.extensions "sono" is forbidden: User "system:serviceaccount:default:default" cannot get daemonsets.extensions in the namespace "default").

Didn't want to escalate the permissions for the default service account used by the debugjob, so created a new sa. On similar lines, this sa too was not bound to the cluster-admin role to ensure best-practices. A dedicated cluster-role for the debugjob has been created with custom-permissions (including pods/exec as we are using kubectl exec commands in the logger to get status of node-log collection) which can be edited based on logging activity requirements.

Signed-off-by: ksatchit<EMAIL_ADDRESS>

Sample Node logs where application was launched. Note that the logdump in its original form is not very readable and needs to be processed. Will be including this as a TODO/add in future enhancements.

 karthik@MayaHost02:~$ cat systemd_logs | grep "kubelet.service" | sed 's|.*"MESSAGE" :||g' | sed 's|.$||' > systemd.log

 "E0321 07:09:19.376093     801 kuberuntime_logs.go:201] Failed with err write tcp <IP_ADDRESS>:10250-><IP_ADDRESS>:34608: write: connection reset by peer when writing log for log file \"/var/log/pods/8cc50428-2b3f-11e8-9309-000c298ff5fc/maya-apiserver_0.log\": &{timestamp:{sec:63657193159 nsec:375270081 loc:<nil>} stream:stderr log:[73 48 51 50 49 32 48 49 58 51 57 58 49 57 46 51 55 53 49 56 55 32 32 32 32 32 32 32 53 32 117 116 105 108 46 103 111 58 49 50 48 53 93 32 87 105 108 108 32 117 115 101 32 101 110 118 32 118 97 114 32 39 68 69 70 65 85 76 84 95 79 82 67 72 69 83 84 82 65 84 79 82 95 78 65 77 69 58 32 39 10]}"
 "I0321 07:09:19.380074     801 logs.go:41] http: multiple response.WriteHeader calls"
 "E0321 07:09:19.380514     801 kuberuntime_logs.go:201] Failed with err write tcp <IP_ADDRESS>:10250-><IP_ADDRESS>:35506: write: connection reset by peer when writing log for log file \"/var/log/pods/8cc50428-2b3f-11e8-9309-000c298ff5fc/maya-apiserver_0.log\": &{timestamp:{sec:63657193159 nsec:375270081 loc:<nil>} stream:stderr log:[73 48 51 50 49 32 48 49 58 51 57 58 49 57 46 51 55 53 49 56 55 32 32 32 32 32 32 32 53 32 117 116 105 108 46 103 111 58 49 50 48 53 93 32 87 105 108 108 32 117 115 101 32 101 110 118 32 118 97 114 32 39 68 69 70 65 85 76 84 95 79 82 67 72 69 83 84 82 65 84 79 82 95 78 65 77 69 58 32 39 10]}"
 "I0321 07:09:19.381271     801 logs.go:41] http: multiple response.WriteHeader calls"
 "E0321 07:09:19.384229     801 kuberuntime_logs.go:201] Failed with err write tcp <IP_ADDRESS>:10250-><IP_ADDRESS>:33786: write: broken pipe when writing log for log file \"/var/log/pods/8cc50428-2b3f-11e8-9309-000c298ff5fc/maya-apiserver_0.log\": &{timestamp:{sec:63657193159 nsec:379882441 loc:<nil>} stream:stderr log:[73 48 51 50 49 32 48 49 58 51 57 58 49 57 46 51 55 55 56 49 55 32 32 32 32 32 32 32 53 32 117 116 105 108 46 103 111 58 49 50 48 53 93 32 87 105 108 108 32 117 115 101 32 101 110 118 32 118 97 114 32 39 68 69 70 65 85 76 84 95 79 82 67 72 69 83 84 82 65 84 79 82 95 73 78 95 67 76 85 83 84 69 82 58 32 39 10]}"
 "I0321 07:09:19.384990     801 logs.go:41] http: multiple response.WriteHeader calls"
 "E0321 07:09:19.688534     801 helpers.go:468] PercpuUsage had 0 cpus, but the actual number is 1; ignoring extra CPUs"
 "I0321 07:09:19.870925     801 reconciler.go:212] operationExecutor.VerifyControllerAttachedVolume started for volume \"openebs\" (UniqueName: \"kubernetes.io/host-path/ac89b8dd-2ca8-11e8-9309-000c298ff5fc-openebs\") pod \"pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc-rep-6c878b99f7-7bnn5\" (UID: \"ac89b8dd-2ca8-11e8-9309-000c298ff5fc\")"
 "I0321 07:09:19.871873     801 reconciler.go:212] operationExecutor.VerifyControllerAttachedVolume started for volume \"default-token-92p66\" (UniqueName: \"kubernetes.io/secret/ac89b8dd-2ca8-11e8-9309-000c298ff5fc-default-token-92p66\") pod \"pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc-rep-6c878b99f7-7bnn5\" (UID: \"ac89b8dd-2ca8-11e8-9309-000c298ff5fc\")"
 "I0321 07:09:20.377038     801 reconciler.go:212] operationExecutor.VerifyControllerAttachedVolume started for volume \"pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc\" (UniqueName: \"kubernetes.io/iscsi/<IP_ADDRESS>:3260:iqn.2016-09.com.openebs.jiva:pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc:0\") pod \"percona-5b9df94795-hfzh6\" (UID: \"ac4a8c61-2ca8-11e8-9309-000c298ff5fc\")"
 "I0321 07:09:20.377121     801 reconciler.go:212] operationExecutor.VerifyControllerAttachedVolume started for volume \"default-token-92p66\" (UniqueName: \"kubernetes.io/secret/ac4a8c61-2ca8-11e8-9309-000c298ff5fc-default-token-92p66\") pod \"percona-5b9df94795-hfzh6\" (UID: \"ac4a8c61-2ca8-11e8-9309-000c298ff5fc\")"
 "E0321 07:09:20.377298     801 nestedpendingoperations.go:264] Operation for \"\\\"kubernetes.io/iscsi/<IP_ADDRESS>:3260:iqn.2016-09.com.openebs.jiva:pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc:0\\\"\" failed. No retries permitted until 2018-03-21 07:09:20.877263406 +0530 IST (durationBeforeRetry 500ms). Error: Volume has not been added to the list of VolumesInUse in the node's volume status for volume \"pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc\" (UniqueName: \"kubernetes.io/iscsi/<IP_ADDRESS>:3260:iqn.2016-09.com.openebs.jiva:pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc:0\") pod \"percona-5b9df94795-hfzh6\" (UID: \"ac4a8c61-2ca8-11e8-9309-000c298ff5fc\")"
 "W0321 07:09:20.523359     801 raw.go:87] Error while processing event (\"/run/lxcfs/controllers/cpu,cpuacct/system.slice/run-rdb1aa3f2696f455eb85dbd276a914d29.scope\": 0x40000100 == IN_CREATE|IN_ISDIR): inotify_add_watch /run/lxcfs/controllers/cpu,cpuacct/system.slice/run-rdb1aa3f2696f455eb85dbd276a914d29.scope: no such file or directory"
 "W0321 07:09:20.523804     801 raw.go:87] Error while processing event (\"/run/lxcfs/controllers/blkio/system.slice/run-rdb1aa3f2696f455eb85dbd276a914d29.scope\": 0x40000100 == IN_CREATE|IN_ISDIR): inotify_add_watch /run/lxcfs/controllers/blkio/system.slice/run-rdb1aa3f2696f455eb85dbd276a914d29.scope: no such file or directory"
 "W0321 07:09:20.524155     801 raw.go:87] Error while processing event (\"/run/lxcfs/controllers/memory/system.slice/run-rdb1aa3f2696f455eb85dbd276a914d29.scope\": 0x40000100 == IN_CREATE|IN_ISDIR): inotify_add_watch /run/lxcfs/controllers/memory/system.slice/run-rdb1aa3f2696f455eb85dbd276a914d29.scope: no such file or directory"
 "I0321 07:09:21.015255     801 reconciler.go:212] operationExecutor.VerifyControllerAttachedVolume started for volume \"pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc\" (UniqueName: \"kubernetes.io/iscsi/<IP_ADDRESS>:3260:iqn.2016-09.com.openebs.jiva:pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc:0\") pod \"percona-5b9df94795-hfzh6\" (UID: \"ac4a8c61-2ca8-11e8-9309-000c298ff5fc\")"
 "E0321 07:09:21.015508     801 nestedpendingoperations.go:264] Operation for \"\\\"kubernetes.io/iscsi/<IP_ADDRESS>:3260:iqn.2016-09.com.openebs.jiva:pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc:0\\\"\" failed. No retries permitted until 2018-03-21 07:09:22.015457086 +0530 IST (durationBeforeRetry 1s). Error: Volume has not been added to the list of VolumesInUse in the node's volume status for volume \"pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc\" (UniqueName: \"kubernetes.io/iscsi/<IP_ADDRESS>:3260:iqn.2016-09.com.openebs.jiva:pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc:0\") pod \"percona-5b9df94795-hfzh6\" (UID: \"ac4a8c61-2ca8-11e8-9309-000c298ff5fc\")"
 "I0321 07:09:22.041676     801 reconciler.go:212] operationExecutor.VerifyControllerAttachedVolume started for volume \"pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc\" (UniqueName: \"kubernetes.io/iscsi/<IP_ADDRESS>:3260:iqn.2016-09.com.openebs.jiva:pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc:0\") pod \"percona-5b9df94795-hfzh6\" (UID: \"ac4a8c61-2ca8-11e8-9309-000c298ff5fc\")"
 "E0321 07:09:22.042690     801 nestedpendingoperations.go:264] Operation for \"\\\"kubernetes.io/iscsi/<IP_ADDRESS>:3260:iqn.2016-09.com.openebs.jiva:pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc:0\\\"\" failed. No retries permitted until 2018-03-21 07:09:24.042642426 +0530 IST (durationBeforeRetry 2s). Error: Volume has not been added to the list of VolumesInUse in the node's volume status for volume \"pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc\" (UniqueName: \"kubernetes.io/iscsi/<IP_ADDRESS>:3260:iqn.2016-09.com.openebs.jiva:pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc:0\") pod \"percona-5b9df94795-hfzh6\" (UID: \"ac4a8c61-2ca8-11e8-9309-000c298ff5fc\")"
 "I0321 07:09:24.049349     801 reconciler.go:212] operationExecutor.VerifyControllerAttachedVolume started for volume \"pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc\" (UniqueName: \"kubernetes.io/iscsi/<IP_ADDRESS>:3260:iqn.2016-09.com.openebs.jiva:pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc:0\") pod \"percona-5b9df94795-hfzh6\" (UID: \"ac4a8c61-2ca8-11e8-9309-000c298ff5fc\")"
 "E0321 07:09:24.050483     801 nestedpendingoperations.go:264] Operation for \"\\\"kubernetes.io/iscsi/<IP_ADDRESS>:3260:iqn.2016-09.com.openebs.jiva:pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc:0\\\"\" failed. No retries permitted until 2018-03-21 07:09:28.050434751 +0530 IST (durationBeforeRetry 4s). Error: Volume has not been added to the list of VolumesInUse in the node's volume status for volume \"pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc\" (UniqueName: \"kubernetes.io/iscsi/<IP_ADDRESS>:3260:iqn.2016-09.com.openebs.jiva:pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc:0\") pod \"percona-5b9df94795-hfzh6\" (UID: \"ac4a8c61-2ca8-11e8-9309-000c298ff5fc\")"
 "I0321 07:09:28.066329     801 reconciler.go:212] operationExecutor.VerifyControllerAttachedVolume started for volume \"pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc\" (UniqueName: \"kubernetes.io/iscsi/<IP_ADDRESS>:3260:iqn.2016-09.com.openebs.jiva:pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc:0\") pod \"percona-5b9df94795-hfzh6\" (UID: \"ac4a8c61-2ca8-11e8-9309-000c298ff5fc\")"
 "I0321 07:09:28.078918     801 operation_generator.go:684] Controller attach succeeded for volume \"pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc\" (UniqueName: \"kubernetes.io/iscsi/<IP_ADDRESS>:3260:iqn.2016-09.com.openebs.jiva:pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc:0\") pod \"percona-5b9df94795-hfzh6\" (UID: \"ac4a8c61-2ca8-11e8-9309-000c298ff5fc\") device path: \"\""
 "I0321 07:09:28.167319     801 operation_generator.go:416] MountVolume.WaitForAttach entering for volume \"pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc\" (UniqueName: \"kubernetes.io/iscsi/<IP_ADDRESS>:3260:iqn.2016-09.com.openebs.jiva:pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc:0\") pod \"percona-5b9df94795-hfzh6\" (UID: \"ac4a8c61-2ca8-11e8-9309-000c298ff5fc\") DevicePath \"\""
 "E0321 07:09:28.178725     801 iscsi_util.go:233] iscsi: failed to rescan session with error: iscsiadm: No session found."
 " (exit status 21)"
 "E0321 07:09:28.201901     801 iscsi_util.go:293] iscsi: failed to get any path for iscsi disk, last err seen:"
 "iscsi: failed to sendtargets to portal <IP_ADDRESS>:3260 output: , err signal: broken pipe"
 "E0321 07:09:28.202766     801 nestedpendingoperations.go:264] Operation for \"\\\"kubernetes.io/iscsi/<IP_ADDRESS>:3260:iqn.2016-09.com.openebs.jiva:pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc:0\\\"\" failed. No retries permitted until 2018-03-21 07:09:28.702723788 +0530 IST (durationBeforeRetry 500ms). Error: MountVolume.WaitForAttach failed for volume \"pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc\" (UniqueName: \"kubernetes.io/iscsi/<IP_ADDRESS>:3260:iqn.2016-09.com.openebs.jiva:pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc:0\") pod \"percona-5b9df94795-hfzh6\" (UID: \"ac4a8c61-2ca8-11e8-9309-000c298ff5fc\") : failed to get any path for iscsi disk, last err seen:"
 "iscsi: failed to sendtargets to portal <IP_ADDRESS>:3260 output: , err signal: broken pipe"
 "I0321 07:09:28.768836     801 operation_generator.go:416] MountVolume.WaitForAttach entering for volume \"pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc\" (UniqueName: \"kubernetes.io/iscsi/<IP_ADDRESS>:3260:iqn.2016-09.com.openebs.jiva:pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc:0\") pod \"percona-5b9df94795-hfzh6\" (UID: \"ac4a8c61-2ca8-11e8-9309-000c298ff5fc\") DevicePath \"\""
 "E0321 07:09:28.781590     801 iscsi_util.go:233] iscsi: failed to rescan session with error: iscsiadm: No session found."
 " (exit status 21)"
 "E0321 07:09:28.805885     801 iscsi_util.go:293] iscsi: failed to get any path for iscsi disk, last err seen:"
 "iscsi: failed to sendtargets to portal <IP_ADDRESS>:3260 output: , err signal: broken pipe"
 "E0321 07:09:28.806761     801 nestedpendingoperations.go:264] Operation for \"\\\"kubernetes.io/iscsi/<IP_ADDRESS>:3260:iqn.2016-09.com.openebs.jiva:pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc:0\\\"\" failed. No retries permitted until 2018-03-21 07:09:29.80672158 +0530 IST (durationBeforeRetry 1s). Error: MountVolume.WaitForAttach failed for volume \"pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc\" (UniqueName: \"kubernetes.io/iscsi/<IP_ADDRESS>:3260:iqn.2016-09.com.openebs.jiva:pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc:0\") pod \"percona-5b9df94795-hfzh6\" (UID: \"ac4a8c61-2ca8-11e8-9309-000c298ff5fc\") : failed to get any path for iscsi disk, last err seen:"
 "iscsi: failed to sendtargets to portal <IP_ADDRESS>:3260 output: , err signal: broken pipe"
 "I0321 07:09:29.872694     801 operation_generator.go:416] MountVolume.WaitForAttach entering for volume \"pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc\" (UniqueName: \"kubernetes.io/iscsi/<IP_ADDRESS>:3260:iqn.2016-09.com.openebs.jiva:pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc:0\") pod \"percona-5b9df94795-hfzh6\" (UID: \"ac4a8c61-2ca8-11e8-9309-000c298ff5fc\") DevicePath \"\""
 "E0321 07:09:29.890247     801 iscsi_util.go:233] iscsi: failed to rescan session with error: iscsiadm: No session found."
 " (exit status 21)"
 "E0321 07:09:29.912325     801 iscsi_util.go:293] iscsi: failed to get any path for iscsi disk, last err seen:"
 "iscsi: failed to sendtargets to portal <IP_ADDRESS>:3260 output: , err signal: broken pipe"
 "E0321 07:09:29.913143     801 nestedpendingoperations.go:264] Operation for \"\\\"kubernetes.io/iscsi/<IP_ADDRESS>:3260:iqn.2016-09.com.openebs.jiva:pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc:0\\\"\" failed. No retries permitted until 2018-03-21 07:09:31.913040011 +0530 IST (durationBeforeRetry 2s). Error: MountVolume.WaitForAttach failed for volume \"pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc\" (UniqueName: \"kubernetes.io/iscsi/<IP_ADDRESS>:3260:iqn.2016-09.com.openebs.jiva:pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc:0\") pod \"percona-5b9df94795-hfzh6\" (UID: \"ac4a8c61-2ca8-11e8-9309-000c298ff5fc\") : failed to get any path for iscsi disk, last err seen:"
 "iscsi: failed to sendtargets to portal <IP_ADDRESS>:3260 output: , err signal: broken pipe"
 "I0321 07:09:31.979862     801 operation_generator.go:416] MountVolume.WaitForAttach entering for volume \"pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc\" (UniqueName: \"kubernetes.io/iscsi/<IP_ADDRESS>:3260:iqn.2016-09.com.openebs.jiva:pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc:0\") pod \"percona-5b9df94795-hfzh6\" (UID: \"ac4a8c61-2ca8-11e8-9309-000c298ff5fc\") DevicePath \"\""
 "E0321 07:09:31.996493     801 iscsi_util.go:233] iscsi: failed to rescan session with error: iscsiadm: No session found."
 " (exit status 21)"
 "E0321 07:09:32.036525     801 iscsi_util.go:293] iscsi: failed to get any path for iscsi disk, last err seen:"
 "iscsi: failed to sendtargets to portal <IP_ADDRESS>:3260 output: , err signal: broken pipe"
 "E0321 07:09:32.037390     801 nestedpendingoperations.go:264] Operation for \"\\\"kubernetes.io/iscsi/<IP_ADDRESS>:3260:iqn.2016-09.com.openebs.jiva:pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc:0\\\"\" failed. No retries permitted until 2018-03-21 07:09:36.037350686 +0530 IST (durationBeforeRetry 4s). Error: MountVolume.WaitForAttach failed for volume \"pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc\" (UniqueName: \"kubernetes.io/iscsi/<IP_ADDRESS>:3260:iqn.2016-09.com.openebs.jiva:pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc:0\") pod \"percona-5b9df94795-hfzh6\" (UID: \"ac4a8c61-2ca8-11e8-9309-000c298ff5fc\") : failed to get any path for iscsi disk, last err seen:"
 "iscsi: failed to sendtargets to portal <IP_ADDRESS>:3260 output: , err signal: broken pipe"
 "I0321 07:09:36.095095     801 operation_generator.go:416] MountVolume.WaitForAttach entering for volume \"pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc\" (UniqueName: \"kubernetes.io/iscsi/<IP_ADDRESS>:3260:iqn.2016-09.com.openebs.jiva:pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc:0\") pod \"percona-5b9df94795-hfzh6\" (UID: \"ac4a8c61-2ca8-11e8-9309-000c298ff5fc\") DevicePath \"\""
 "E0321 07:09:36.105536     801 iscsi_util.go:233] iscsi: failed to rescan session with error: iscsiadm: No session found."
 " (exit status 21)"
 "I0321 07:09:38.788539     801 mount_linux.go:379] `fsck` error fsck from util-linux 2.27.1"
 "fsck.ext2: Bad magic number in super-block while trying to open /dev/sdb"
 "/dev/sdb:"
 "The superblock could not be read or does not describe a valid ext2/ext3/ext4"
 "filesystem.  If the device is valid and it really contains an ext2/ext3/ext4"
 "filesystem (and not swap or ufs or something else), then the superblock"
 "is corrupt, and you might try running e2fsck with an alternate superblock:"
 "    e2fsck -b 8193 <device>"
 " or"
 "    e2fsck -b 32768 <device>"
 "E0321 07:09:38.823961     801 mount_linux.go:140] Mount failed: exit status 32"
 "Mounting command: systemd-run"
 "Mounting arguments: --description=Kubernetes transient mount for /var/lib/kubelet/plugins/kubernetes.io/iscsi/iface-default/<IP_ADDRESS>:3260-iqn.2016-09.com.openebs.jiva:pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc-lun-0 --scope -- mount -t ext4 -o defaults /dev/disk/by-path/ip-<IP_ADDRESS>:3260-iscsi-iqn.2016-09.com.openebs.jiva:pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc-lun-0 /var/lib/kubelet/plugins/kubernetes.io/iscsi/iface-default/<IP_ADDRESS>:3260-iqn.2016-09.com.openebs.jiva:pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc-lun-0"
 "Output: Running scope as unit run-rbb12416a626848a8ace18c0845ebd966.scope."
 "mount: wrong fs type, bad option, bad superblock on /dev/sdb,"
 "       missing codepage or helper program, or other error"
 "       In some cases useful info is found in syslog - try"
 "       dmesg | tail or so."
 "I0321 07:09:38.864194     801 mount_linux.go:404] Disk \"/dev/disk/by-path/ip-<IP_ADDRESS>:3260-iscsi-iqn.2016-09.com.openebs.jiva:pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc-lun-0\" appears to be unformatted, attempting to format as type: \"ext4\" with options: [-F /dev/disk/by-path/ip-<IP_ADDRESS>:3260-iscsi-iqn.2016-09.com.openebs.jiva:pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc-lun-0]"
 "W0321 07:09:41.983214     801 conversion.go:110] Could not get instant cpu stats: different number of cpus"
 "I0321 07:09:47.803328     801 mount_linux.go:408] Disk successfully formatted (mkfs): ext4 - /dev/disk/by-path/ip-<IP_ADDRESS>:3260-iscsi-iqn.2016-09.com.openebs.jiva:pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc-lun-0 /var/lib/kubelet/plugins/kubernetes.io/iscsi/iface-default/<IP_ADDRESS>:3260-iqn.2016-09.com.openebs.jiva:pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc-lun-0"
 "I0321 07:09:47.874440     801 operation_generator.go:425] MountVolume.WaitForAttach succeeded for volume \"pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc\" (UniqueName: \"kubernetes.io/iscsi/<IP_ADDRESS>:3260:iqn.2016-09.com.openebs.jiva:pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc:0\") pod \"percona-5b9df94795-hfzh6\" (UID: \"ac4a8c61-2ca8-11e8-9309-000c298ff5fc\")"
 "I0321 07:09:47.874862     801 operation_generator.go:446] MountVolume.MountDevice succeeded for volume \"pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc\" (UniqueName: \"kubernetes.io/iscsi/<IP_ADDRESS>:3260:iqn.2016-09.com.openebs.jiva:pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc:0\") pod \"percona-5b9df94795-hfzh6\" (UID: \"ac4a8c61-2ca8-11e8-9309-000c298ff5fc\") device mount path \"/var/lib/kubelet/plugins/kubernetes.io/iscsi/iface-default/<IP_ADDRESS>:3260-iqn.2016-09.com.openebs.jiva:pvc-ac4615b9-2ca8-11e8-9309-000c298ff5fc-lun-0\""
 "W0321 07:09:47.954311     801 container.go:354] Failed to create summary reader for \"/system.slice/run-r4669be51900d4e95bc4cb516fc232511.scope\": none of the resources are being tracked."
 "E0321 07:09:47.954823     801 helpers.go:468] PercpuUsage had 0 cpus, but the actual number is 1; ignoring extra CPUs"
 "I0321 07:11:47.550433     801 reconciler.go:212] operationExecutor.VerifyControllerAttachedVolume started for volume \"root\" (UniqueName: \"kubernetes.io/host-path/049f7fa4-2ca9-11e8-9309-000c298ff5fc-root\") pod \"sono-q69f7\" (UID: \"049f7fa4-2ca9-11e8-9309-000c298ff5fc\")"
 "I0321 07:11:47.551227     801 reconciler.go:212] operationExecutor.VerifyControllerAttachedVolume started for volume \"default-token-92p66\" (UniqueName: \"kubernetes.io/secret/049f7fa4-2ca9-11e8-9309-000c298ff5fc-default-token-92p66\") pod \"sono-q69f7\" (UID: \"049f7fa4-2ca9-11e8-9309-000c298ff5fc\")"
 "I0321 07:11:47.551529     801 reconciler.go:212] operationExecutor.VerifyControllerAttachedVolume started for volume \"results\" (UniqueName: \"kubernetes.io/host-path/049f7fa4-2ca9-11e8-9309-000c298ff5fc-results\") pod \"sono-q69f7\" (UID: \"049f7fa4-2ca9-11e8-9309-000c298ff5fc\")"


Estimated release date

Hi, thanks for your great work! Do you have an estimate of the release date for the code?

Thanks for your interest. The code has been released.


ES module

Hello,
When using this package with Astro, I am getting this message:
vanilla-hcaptcha doesn't appear to be written in CJS, but also doesn't appear to be a valid ES module (i.e. it doesn't have "type": "module" or an .mjs extension for the entry point). Please contact the package author to fix.

Hi. This is built as an IIFE. You should be able to do the following:
<script src="[vanilla-hcaptcha](https://cdn.jsdelivr.net/npm/vanilla-hcaptcha)"></script>

or if you installed via npm/yarn:
<script src="vanilla-hcaptcha"></script>

If this does not help, please provide a snippet to reproduce the error.

Closing this.


Track appname in MongoClient

It'll be useful for the Atlas folks to see how many people are connecting to Atlas Clusters via our dask-mongo connector. To do that we need to include the appname when creating the client.
I believe it would look something like
app_info = f"dask-mongo/{dask_mongo.__version__}

with pymongo.MongoClient(**connection_kwargs, appname=app_info) as mongo_client:
       #do things

We should include this in write_mongo, fetch_mongo, and read_mongo in https://github.com/coiled/dask-mongo/blob/main/dask_mongo/core.py
For reference, read appname in https://pymongo.readthedocs.io/en/stable/api/pymongo/mongo_client.html
cc: @jrbourbeau @rrpelgrim

Sounds reasonable to me. Are there restrictions on what characters can be in appname? Is app_info = f"dask-mongo/{dask_mongo.__version__}" a valid name?

It looks like appname takes strings, according to the docs.

appname: (string or None) The name of the application that created this MongoClient instance. The server will log this value upon establishing each connection. It is also recorded in the slow query log and profile collections.

Are there restrictions on what characters can be in appname?

No restrictions,  f"dask-mongo/{dask_mongo.__version__}" makes sense to me.

Thanks for clarifying @ShaneHarvey. Are you able to confirm if the appname added in https://github.com/coiled/dask-mongo/pull/19 is showing up on the mongo side?

You can verify by inspecting the server logs. The server will log the appname on each new connection like this:
{"t":{"$date":"2022-05-24T18:57:35.254-07:00"},"s":"I",  "c":"NETWORK",  "id":22943,   "ctx":"listener","msg":"Connection accepted","attr":{"remote":"<IP_ADDRESS>:49719","uuid":"6182ae63-66e5-40c6-8284-511b3363fd94","connectionId":27,"connectionCount":6}}
{"t":{"$date":"2022-05-24T18:57:35.255-07:00"},"s":"I",  "c":"NETWORK",  "id":51800,   "ctx":"conn27","msg":"client metadata","attr":{"remote":"<IP_ADDRESS>:49719","client":"conn27","doc":{"driver":{"name":"PyMongo","version":"4.2.0.dev1"},"os":{"type":"Darwin","name":"Darwin","architecture":"x86_64","version":"10.16"},"platform":"CPython 3.7.9.final.0","application":{"name":"dask-mongo/1.1.1"}}}}

Thanks @baf509 I was able to test it locally by printing the mongo_client.server_info().
{"t":{"$date":"2022-05-25T12:08:24.475-04:00"},"s":"I",  "c":"COMMAND",  "id":51803,   "ctx":"conn11","msg":"Slow query","attr":{"type":"command","ns":"test-db.test-collection",
"appName":"dask-mongo/2021.7.3","command":{"insert":"test-collection","ordered":true,"lsid":{"id":{"$uuid":"667d444d-3034-445d-bbf4-f812a75b6c56"}},"$db":"test-db"},"ninserted":2,"keysInserted":2,"numYields":0,"reslen":45,"locks":{"ParallelBatchWriterMode":{"acquireCount":{"r":4}},"ReplicationStateTransition":{"acquireCount":{"w":4}},"Global":{"acquireCount":{"r":1,"w":3}},"Database":{"acquireCount":{"r":1,"w":3}},"Collection":{"acquireCount":{"r":1,"w":3}},"Mutex":
{"acquireCount":{"r":5}}},"flowControl":{"acquireCount":3,"timeAcquiringMicros":10},"storage":{},"remote":"<IP_ADDRESS>:53735","protocol":"op_msg","durationMillis":252}}

I will go ahead and do a release, pypi should be fast, we will have to wait a bit for conda-forge until the bots pick it up.
@jrbourbeau Do I have a green light to release?

@baf509 The new release of dask-mongo that includes the tracking of the appname is up on PyPI and should be in conda-forge in 1h or so, we've just merged the conda-forge feedstock PR.

That's great, thanks @ncclementi!


[Brick] Improve list and tree selection performance

Tree and List are being completely rebuild when selection changes, instead we should just update related items

it is instant now


Refactoring - remove duplicated code in DMNKogito

Hi,
While I was working on some stuff I found out that this class could have been refactored since two methods contains the same code.
Hope this helps

I will abandon this PR since this class is already refactored in another open pr https://github.com/kiegroup/kogito-runtimes/pull/395


remove smoke tests temporarily since we haven't got a fix for the cer…

remove smoke tests temporarily since we haven't got a fix for the certificate issue yet. Brief detail about the issue -
Since the last few days we have been getting this error while trying to run the smoke tests. This is primarily down to the apt-get update failing to update the certs. Tried multiple options however but seems to fail every time. Also updated the dockerfile from bullseye to bookworm but still the same issue. So disabling the smoke tests till we get around this issue. Hopefully Google will update the certs post which it starts running again as earlier -
Example -
https://app.circleci.com/pipelines/github/ministryofjustice/send-legal-mail-to-prisons/1992/workflows/df2d6d09-6383-4ff9-8259-a2cb3deda3b8/jobs/9233

Have you tried updating the executor for the smoke tests. It's using an old version: https://github.com/ministryofjustice/send-legal-mail-to-prisons/blob/2b2f1836322523a840df9e190313b2957a214122/.circleci/config.yml#L32
Newer versions here: https://hub.docker.com/r/cypress/included. E.g. could match it to what's in package.json.
Vaguely recall this was what #390 was about...


Multi tag field

Supported on PHP 7.
Fixed parameter to fit the parent method.
Fixed database install and update.

Merged as cf6cdc5


Wrong groups detection by import/order

I have the next config
"import/order": ["error", {
      "groups": [["external", "builtin"], "internal", "sibling", "parent", "index"],
      "newlines-between": "always",
      "pathGroups": [
        {
          "pattern": "constants/**",
          "group": "internal",
          "position": "before"
        },
        {
          "pattern": "actions/ui/actionTypes",
          "group": "internal",
          "position": "after"
        },
        {
          "pattern": "utils",
          "group": "internal",
          "position": "after"
        },
        {
          "pattern": "utils/**",
          "group": "internal",
          "position": "after"
        },
        {
          "pattern": "api/**",
          "group": "internal",
          "position": "after"
        },
        {
          "pattern": "api",
          "group": "internal",
          "position": "after"
        },
        {
          "pattern": "components/**",
          "group": "internal",
          "position": "after"
        },
        {
          "pattern": "layouts/**",
          "group": "internal",
          "position": "after"
        },
        {
          "pattern": "reducers/**",
          "group": "internal",
          "position": "after"
        },
        {
          "pattern": "routes/**",
          "group": "internal",
          "position": "after"
        },
        {
          "pattern": "selectors/**",
          "group": "internal",
          "position": "after"
        },
        {
          "pattern": "services/**",
          "group": "internal",
          "position": "after"
        },
        {
          "pattern": "actions/**",
          "group": "internal",
          "position": "after"
        },
        {
          "pattern": "shared/**",
          "group": "internal",
          "position": "after"
        },
        {
          "pattern": "static/**",
          "group": "internal",
          "position": "after"
        },
        {
          "pattern": "styles/**",
          "group": "internal",
          "position": "after"
        },
        {
          "pattern": "_history",
          "group": "internal",
          "position": "after"
        },
        {
          "pattern": "index",
          "group": "internal",
          "position": "after"
        },
        {
          "pattern": "store",
          "group": "internal",
          "position": "after"
        },
        {
          "pattern": "toast",
          "group": "internal",
          "position": "after"
        },
        {
          "pattern": "pages/**",
          "group": "internal",
          "position": "after"
        },
        {
          "pattern": "*.scss",
          "patternOptions": { "matchBase": true },
          "group": "index",
          "position": "after"
        }
      ],
      "pathGroupsExcludedImportTypes": []
    }],

Src folder has the next structure

.eslintrc placed in root of the project
The first moment is that the order plugin treats utils.js as an external. Tried to manage it by adding pathGroup for every folder/file in src (like in provided above config). But still got a problem with recognizing utils group. It says that it should be blank line between imports from constants/freezedEntities and utils, but both of them described as "group": "internal". Is it a bug or I've missed something?
file in src/Components/*/filename.js
import React from 'react'

import { CARDS } from 'constants/cards'
import { EMPTY_OBJECT } from 'constants/freezedEntities' // Error: There should be at least one empty line between import groups
import { getColors, formatNumber } from 'utils'

import CardChart from './apps/CardChart'

import style from './style.scss'

        {
          "pattern": "constants/**",
          "group": "internal",
          "position": "before" <<< BEFORE
        },
        {
          "pattern": "utils",
          "group": "internal",
          "position": "after" <<< AFTER
        },

Try making those match. You are missing a small detail in the docs. You're not assigning it to the group "internal" there, but rather, you're saying this should come before internal or this should come after internal. I'm not an expert on this project - but the way I view it, that would mean you're creating two "virtual groups" for lack of better words, and it expects empty lines between groups.

That seems like a reasonable answer, thanks.
Happy to reopen if needed.


Use the minus sign

The JavaScript language is camelCase (toString, toLowerCase, etc), and this: "-" is a minus sign. I don't know why people do var myModule = require("my-module");. It's just silly. Don't put minus signs in filesystem paths or package names.

Camelcase are not allowed anymore
forbidden New packages must have all-lowercase names

The minus sign it's now being used instead.

@michaeljota Thanks for this suggestion. Although I think that rule is silly/terrible, I don't think it matters enough to bikeshed it, so I have updated this repo to v3.0.0 with lower-kebab-case filenames.


fpgainfo: for N501x add show board info read from BMC

Signed-off-by: Roger Christensen<EMAIL_ADDRESS>

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 10 (0.0%)  changed or added relevant lines in 1 file are covered.
7 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.05%) to 65.871%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

libraries/libboard/board_n5010/board_n5010.c
0
10
0.0%

Files with Coverage Reduction
New Missed Lines
%

libraries/plugins/xfpga/open.c
1
74.68%

libraries/plugins/xfpga/mmio.c
6
82.87%

Totals

Change from base Build<PHONE_NUMBER>:
-0.05%

Covered Lines:
13140

Relevant Lines:
19948

💛  - Coveralls


Production site gives 404 when opened from nested URL

Open production website from any url that is not the base one will give a 404.
Probably related to the vite transition, the js is loaded from the wrong url, so it is not found.

Fixed this error, but on further research I have noticed that the routing on the client is wrong, will also fix that


MIDI heartbeat and sequencer timing sync problems

Both MIDI heartbeat and sequencer step execution need to run in synchronization but at different frequencies. i.e. The MIDI timer needs to run faster. Therefore they are triggered by seperate timers. However there are drift issues with the synchronization if we simply set the timer frequency manually. A better solution is needed:

master/slave sync No good, the slave timer must run at the same freq as the master.
Input compare. Only works with own duty? Maybe a 2nd channel could run a faster duty cycle and could trigger a second timer?
repetition counter. MIDI timer could wait n repetitions before triggering the sequencer timer?

Solution was to have one timer in SequenceManager. The ISR would count 0->12. Every count would send a MIDI clock message, but only when reaching 12 would the Pattern cursor be incremented.
e0813dfe3eba70da7c41fa62eb7fcb1d4a5ce861


Move the Read The Docs black bar back under menu list

@bkabili @CobyKabili Ben had moved the black bar I'm showing in the attached picture out from under the menu list, but on smaller screens is blocks out the links for the bottom of the lists as they expand.
Can we move this back inline with the menu?

@AllenMcAfee I added a larger margin to the bottom of the menu so that you can always scroll to the bottom of the menu even if you are on a small screen and the black bar is over the menu. You should be able to get to all parts of the menu no matter what.

In the out of the box Read the Docs styling, the bar covers the menu as well and you can scroll to the bottom similar to how we have it set now. Would you rather have it a different way?

@AllenMcAfee @CobyKabili can we close this or do we still want the bar moved?

@bkabili It is still problematic in it's current state.  Check the photo below.

The bar still overs the text if the menu is long enough.  If we can move this directly under the menu, and shrink the menu's bottom margin to fit it, then I think we're in business.


fix(functions): add 2nd-gen cloudevent tags

@GoogleCloudPlatform/php-admins can y'all please review? This is required to fix sample browser generation for gen 1/2 Cloud Functions samples since PHP doesn't require duplicate samples for the different versions but in order for sample browser to show the sample in both places needs 2 region tags.
Thanks.


Fixing consistency of signatures.

data instead of action. Same as https://github.com/trainyard/choo-cli/issues/20 but also including effects and lifecycle methods.

Thanks!


[staging] python3Packages.click: 8.0.2 -> 8.0.3

Small bugfix release to address regression in 8.0.2.
Also fix unmatched substitute call, which has been failing since the
code was formatted with black for v7.1.
Upstream changes: https://github.com/pallets/click/compare/8.0.2...8.0.3
Closes https://github.com/NixOS/nixpkgs/issues/144580

Motivation for this change
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 wip"
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.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

[ ] Fits CONTRIBUTING.md.

This would be nice to have for ZHF 21.11 https://github.com/NixOS/nixpkgs/issues/144627
There are enough rebuilds that this needs to go to staging, but I think since it's only a bugfix release, this isn't blocked by the feature freeze, right? cc @mweinelt

Yup, bugfix release like this are just fine. Palletsprojects adhere to semver AFAIK.


curl: (52) Empty reply from server

% curl -v -H "Content-Type: application/json" -d '{"username":"admin", "password":"password"}' http://localhost:5001/login

Trying <IP_ADDRESS>:5001...
Connected to localhost (<IP_ADDRESS>) port 5001 (#0)

POST /login HTTP/1.1
Host: localhost:5001
User-Agent: curl/7.88.1
Accept: /
Content-Type: application/json
Content-Length: 43

Empty reply from server
Closing connection 0
curl: (52) Empty reply from server

Simplified API which circumvents this issue.

I was able to get it running by setting the host.
if __name__ == '__main__':
-    app.run(debug=True, port=8080)
+    app.run(host='<IP_ADDRESS>', debug=True, port=8080)

This fixed the other issue as well! Thx @benarent


can't use alchemy as l1 rpc

Currently alchemy doesn't support json-api below:

eth_getFinalizedHeader
alchemy_getTransactionReceipts
eth_getBlockReceipts

The missing methods make op-node can't finalize blocks on bsc and opbnb then op-proposer don't work correctly

We are evaluating the issue


Rectangles are mirrored when using front camera

Currently face rectangles are drawn incorrectly when using front camera, because they should be mirrored. At the moment Fotoapparat does not provide us information about whether we should mirror the image or not. So, some changes might be needed there as well.

@dmitry-zaitsev How to fix this in my project?

How to fix ? THX

@dmitry-zaitsev hi, any update for this issue? I'm facing the same issue

@dmitry-zaitsev hi, any update for this issue? I'm facing the same issue


Publish to nuget.org

Currently our packages are only published to our GitHub NuGet feed^1. To make is easier for users to find and consume our packages we should publish our packages to nuget.org.
We should follow Microsoft best practices for creating NuGet packages, including package signing, before publishing to nuget.org

@JamieMagee , is this something you can prioritize to get it done soon? The SBOM OSS project needs to use a public ADO feed to be able to consume the Component Detectors packages
@aasim , @daneshbadlani

I was out at a conference last week, but I will try and get this wrapped up this week.

@JamieMagee , any chance this might happen soon?
@daneshbadlani

We've created the MicrosoftOpenSourceEngineeringTeam^1 organization, and reserved the Microsoft.ComponentDetection and Microsoft.ComponentDetection.* package namespaces.

We're currently blocked on ESRP signing https://dev.azure.com/msazure/ESRPSignOnboarding/_workitems/edit/15434568

Component Detection is now available on nuget.org https://www.nuget.org/packages/Microsoft.ComponentDetection


pull request for e2e test at 12/08/2016 01:26:03

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


method_name in local_accuracy

Hey there,
can anyone give me details about the method_name parameter in the metrics functions what it is about exactly and how we fix it?
Thanks in advance.
def local_accuracy(X, y, model_generator, method_name):

Hi, thanks for your answer. I also wonder what's the model_generator parameter?

Hi, thanks for your answer. I also wonder what's the model_generator parameter?

Looking at the source code https://github.com/slundberg/shap/blob/b6e90c859fdfc6bc145242d9a8082d4ad844e995/shap/benchmark/metrics.py I think it would be a class ref to the local model you fit...?

Hi, thanks for your answer. I also wonder what's the model_generator parameter?

I am not sure but I think (looking at the source code) it's:
metrics.local_accuracy(X, y, SomeSkleanModel, 'sampling_shap_1000')
It would be SomeSkleanModel (a class ref) of the local classifier you want to evaluate.
For example, for me metrics.consistency_guarantees(X, y, LinearRegression, 'sampling_shap_1000') gives some reasonable score (I do regression).


Enable C#12

Complete .NET8 release with C#12 support

Error: (4,22): error CS1002: ; expected

Using statement are not supported in csharp scripting, they won't work

@johngardner58work Is it your expectation that disposal would happen when the kernel is shut down (i.e. when you restart it or close the notebook)?
If so you can do this:
Microsoft.DotNet.Interactive.Kernel.Root.RegisterForDisposal(factory);

Perhaps I should repost for Csharp scripting?

The place to open this issue would be in dotnet/roslyn.


Added "placeholder" props definition

Added "placeholder" prop definition configurable via props

For those wanting a temporary workaround, create an augmentation:
import 'rc-datepicker';

declare module 'rc-datepicker' {
  export interface DatePickerInputProps {
    placeholder?: string;
  }
}

Thanks @ivanghisleni, released this as v5.0.14


kubevirt-vm-latency: Support bridge networks

Currently the checkup supports SR-IOV networks only, it defines the VMs interface with SR-IOV binding method
regardless of the NetworkAttachmentDefinition (NAD) spec.
By supporting bridge network it will enable running the checkup on environment without SR-IOV hardware
such as CI and dev environments.
With this PR changes, the checkup will detect which CNI plugin is being used by the given NAD and define the
VMs interfaces accordingly.
If the bridge CNI is being used the VMs interfaces will be defined with bridge binding method.

Thank you for the PR @ormergi! Can you please separate the pre-flight part to another PR?

Done, first commit is moved to https://github.com/kiagnose/kiagnose/pull/97

/cc @EdDev

@orelmisan @EdDev please take another look.

Rebased

By supporting bridge network it will enable running the checkup on environment with SR-IOV hardware
such as CI and dev environments.

you mean without SR-IOV hardware right?

By supporting bridge network it will enable running the checkup on environment with SR-IOV hardware
such as CI and dev environments.

you mean without SR-IOV hardware right?

Right, thanks for the heads up I will fix it.

@ormergi in the third commit, can you please explain how clientStub{} records the created interfaces on each create?

clientStub{} saves each VM that was created at `clientStub.createdVmis, tests will assert on each VM interfaces and check equality to expected interface.
Does it answer your question?

@EdDev following https://github.com/kiagnose/kiagnose/pull/94#issuecomment-1143743706,
Now I realized that the tests pass with or w/o converting clientStub{} methods to have pointer receiver,
because there is no assertion on clientStub.createdVmis slice:
https://github.com/kiagnose/kiagnose/blob/6e649f2677d7badc9252c46b4bddcbbad6bfe7e2/checkups/kubevirt-vm-latency/vmlatency/internal/checkup/checkup_test.go#L159-L179
Adding this assertion makes the test fail (as expected) when clientStub{}methods to have pointer receiver.
Now answering the question why having pointer reciver in the first place,
looking at CreateVirtualMachineInstance() we can see that if the receiver is not configured as a pointer, clientStub{} will be discarded when it returns.
Here is a nice explanation with another example

Change: address https://github.com/kiagnose/kiagnose/pull/94/commits/6491c3b3250bef8b3cd124a1c8dfdd258e3a43d3#r886726148, change launcher_test.go fakeClient to act like a NetworkAttachmentDefinition exists.

Changes: Prase NetworkAttachmentDefinition using libcni

Changes: Move NetworkAttachmentDefinition existence check from preflight to setup, following https://github.com/kiagnose/kiagnose/pull/94#discussion_r886728686

Changes: Unexport SR-IOV CNI plugin name.

Changes: Add missing CNI plugin names in checkup tests.

Changes: Fix test description and shorten commit message titles.


fleetctl query doesn't work with self-signed cert

Perhaps due to insecure flag not functioning?

I dug into this and it does seem to work with a self-signed cert when running on localhost. Will do some further digging to see if I can understand why the query did not seem to run when running on my test (remote) server with a self-signed cert.

Was not able to reproduce an issue here.


Added Korean translation of "Getting Started"

The "Getting Started" document was translated into Korean for new Korean users. Actually, I thought the topic would be small, but as I was working on it, I ended up editing too many files and lines... :(

[ ] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Great work! Seems that the spell checker wants some words placed in backticks (like `boxShadow`), and there may be a Lern -> Lerna spelling mistake.


Install bowie on docker-compose

Business case
Hi Bowie Team. Am trying to install bowie through docker compose, any help will be appreciate. All bowie components (see Stack below) has been built successfully. Am still unable to get some components (pogues [ui and api], ddi and stromae v1)  working properly. I think that am missing some configurations.
Stack

pogues [ui and api]
enows (core, lunatic)
ddi services (and elasticsearch)
Stromae (v1, v2, db)
Postgresql

Progress
Based on bowie install description Bowie Install, , and this file, I was able to make my docker compose file. All the container running without exit.
Issues
The following components not working and I don't have any errors in their logs:

Pogues (ui and api) return 404 error and Pogues (ui) has "Uncaught (in promise) SyntaxError: JSON.parse: unexpected end of data at line 1 column 1 of the JSON data - prepareInhection.js:244:11' in the console log

The following components not working has well and their logs shows some errors:

ddi services: Properties location [file:${catalina.base}/webapps/rmespogbo.properties] not resolvable: /usr/local/tomcat/webapps/rmespogbo.properties (No such file or directory)

StromaeV1 return 404 error and the logs show:
org.apache.catalina.core.StandardContext.listenerStart Error configuring application listener of class net.sf.ehcache.constructs.web.ShutdownListener
java.lang.ClassNotFoundException: net.sf.ehcache.constructs.web.ShutdownListener

Thanks you for your feedbacks.

Hi Jean! Thank you for using our tools.
This repo is only dedicated to the Bowie roadmap, issues are roadmap milestones, not real user issues, so i propose to move this content in the discussion panel where we would be able to answer you ASAP.

Discussion is here: https://github.com/InseeFr/Bowie/discussions/73


I am getting an error in creating a separate context

new p5(p => {
  p.wordObject;

  p.setup = () => {
    p.createCanvas(400, 400, p.WEBGL);
    p.wordObject = new p.Word3D('Hello', 3, 4, 20);
  }

  p.draw = () => {
    p.background(255);
    p.normalMaterial()
    p.wordObject.show()
  }
});

Uncaught ReferenceError: BOLD is not defined

It seems like I need to rewrite the library slightly because I didn't account for Instance Mode. I'll update this issue thread when it's fixed.

This has now been fixed! Check the latest release and it should all be working. Please let me know if there are any problems.


Allow Recognizer to not be set

If BotFramework::Bot.recognizer isn't set
NoMethodError: undefined method `recognize' for nil:NilClass
        /usr/lib/ruby/gems/2.4.0/gems/bot_framework-0.1.0beta/lib/bot_framework/bot.rb:36:in `receive'
        /usr/lib/ruby/gems/2.4.0/gems/bot_framework-0.1.0beta/lib/bot_framework/server.rb:24:in `receive'
        /usr/lib/ruby/gems/2.4.0/gems/bot_framework-0.1.0beta/lib/bot_framework/server.rb:12:in `call'
        /usr/lib/ruby/gems/2.4.0/gems/bot_framework-0.1.0beta/lib/bot_framework/server.rb:4:in `call'
        /usr/lib/ruby/gems/2.4.0/gems/rack-2.0.1/lib/rack/tempfile_reaper.rb:15:in `call'
        /usr/lib/ruby/gems/2.4.0/gems/rack-2.0.1/lib/rack/lint.rb:49:in `_call'
        /usr/lib/ruby/gems/2.4.0/gems/rack-2.0.1/lib/rack/lint.rb:37:in `call'
        /usr/lib/ruby/gems/2.4.0/gems/rack-2.0.1/lib/rack/show_exceptions.rb:23:in `call'
        /usr/lib/ruby/gems/2.4.0/gems/rack-2.0.1/lib/rack/common_logger.rb:33:in `call'
        /usr/lib/ruby/gems/2.4.0/gems/rack-2.0.1/lib/rack/chunked.rb:54:in `call'
        /usr/lib/ruby/gems/2.4.0/gems/rack-2.0.1/lib/rack/content_length.rb:15:in `call'
        /usr/lib/ruby/gems/2.4.0/gems/rack-2.0.1/lib/rack/handler/webrick.rb:86:in `service'
        /usr/lib/ruby/2.4.0/webrick/httpserver.rb:140:in `service'
        /usr/lib/ruby/2.4.0/webrick/httpserver.rb:96:in `run'
        /usr/lib/ruby/2.4.0/webrick/server.rb:290:in `block in start_thread'

Thanks alot :-)


Coming soon page added

Description:
Coming soon page added for FAQ and Project pages
Issue- #219
Screenshot:

loving this,m super userful!


Updated README.md

Compiling QAT ver 1.7 driver and OpenSSL_1_1_1 was a breeze but when I got to QAT_Engine it was a struggle.
It took me a couple of hours troubleshooting and searching until I realized that
I'm cloning the source from the wrong URL:
git clone https://github.com/01org/QAT_Engine.git
When I  did a clone from the below, all worked like a charm!
git clone https://github.com/intel/QAT_Engine.git

@mveplus
Thanks for spotting it and sorry for the inconvenience.  Although I am able to clone the repo with
git clone https://github.com/01org/QAT_Engine.git  and also access to the link  ( https://github.com/01org/QAT_Engine.git) in the browser redirects automatically to the https://github.com/intel/QAT_Engine.git in my browser.
Anyways We will merge this PR,  but before that Could you please update the pull request commit message with "Signed-off-by:" in the following format
Signed-off-by: Name

@Yogaraj-Alamenda
Thanks for your replay! Amended, please check if everything looks all right?

@mveplus But Email Id is missing in the Signed off  message

@Yogaraj-Alamenda
Thanks, a bit green on this side ;)

Thank you for your contribution! Merged into the release v0.5.43
Updated README.md - a8dab01204ffaa3db618f3322309d7492a382801


drop down does not hide if touched outside area in mobile

Thanks for wonderful library.
I have found one issue, when I touch outside of drop down area. the drop down does not hide.
In browser, when i clicked outside area it actually hides dropdown. But in mobiles, it not working.

@esoyke might fix this for you. https://github.com/esoyke/ngx-international-phone-number2
Put this there. He might help.


Implement User check at generate url

Description
This PR includes the following proposed change(s):
Implement user check at generate url
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Refactoring / Documentation

if your change is a breaking change, please add breaking change label to this PR
How Has This Been Tested?
Postman and unit tests
Checklist:

[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[X] New and existing unit tests pass locally with my changes

@alexjoybc  on you to approve


[HUDI-1829] Use while loop instead of recursive call in MergeOnReadIn…

…putFormat to avoid StackOverflow
Recursive all is risky for StackOverflow when there are too many.
Tips

Thank you very much for contributing to Apache Hudi.
Please review https://hudi.apache.org/contributing.html before opening a pull request.

What is the purpose of the pull request
(For example: This pull request adds quick-start document.)
Brief change log
(for example:)

Modify AnnotationLocation checkstyle rule in checkstyle.xml

Verify this pull request
(Please pick either of the following options)
This pull request is a trivial rework / code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end.
Added HoodieClientWriteTest to verify the change.
Manually verified the change by running a job locally.

Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Codecov Report

Merging #2862 (8e00679) into master (4a34318) will decrease coverage by 43.64%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master   #2862       +/-   ##
============================================
- Coverage     53.01%   9.36%   -43.65%
+ Complexity     3744      48     -3696
============================================
  Files           488      54      -434
  Lines         23435    1996    -21439
  Branches       2500     236     -2264
============================================
- Hits          12423     187    -12236
+ Misses         9913    1796     -8117
+ Partials       1099      13     -1086

Flag
Coverage Δ
Complexity Δ

hudicli
?
?

hudiclient
?
?

hudicommon
?
?

hudiflink
?
?

hudihadoopmr
?
?

hudisparkdatasource
?
?

hudisync
?
?

huditimelineservice
?
?

hudiutilities
9.36% <ø> (-60.38%)
48.00 <ø> (-326.00)

Flags with carried forward coverage won't be shown. Click here to find out more.


E2E tests not getting expected TTS values

https://b.corp.google.com/issues/150902962. Looks like premature truncation of trace data from the logs.
cc @iskakaushik @gw280

Currently assigned to somebody in Google. No action required from Flutter at this point.

Still being worked by Googlers. No action required from Flutter team at this point.

Still being worked by Googlers; escalated at Google to a P0, so if we're asked for help, we'll need to jump on it. No immediate action for the Flutter team, though.

Fix rolled through Google's source code repository and believe fixed. Leaving open until upstream issue closes.

Upstream issue is marked as fixed; closing.


Kf 2270 feat argoexec ROCK update per best practices

Description
Details are in https://github.com/canonical/argo-workflows-rocks/issues/9
Argo Exec ROCK is part of ROCK creation epic. Initial ROCK was created during the workshop. This update introduces unit and integration tests and changes to rockcraft.yaml based on best practices specified in Kuebflow team spec.
Summary of changes:

Updated rockcraft to be up to spec with best practices.
Updatde integration tests for this ROCK in tox.ini
Added unit test to verify ROCK integrity.

Testing
Unit and integration tests for this ROCK are passing locally. Currently, there are no workflows in this repository to trigger tests.
Build
$ rockcraft pack
Retrieved base bare for amd64
Extracted bare:latest
Executed: pull base-deps
Executed: pull base-snaps
Executed: pull builder
Executed: pull copy-files
Executed: pull pebble
Executed: pull security-team-requirement
Executed: overlay base-deps
Executed: overlay base-snaps
Executed: overlay builder
Executed: overlay copy-files
Executed: overlay pebble
Executed: overlay security-team-requirement
Executed: build base-deps
Executed: build base-snaps
Executed: skip pull base-deps (already ran)
Executed: skip overlay base-deps (already ran)
Executed: skip build base-deps (already ran)
Executed: stage base-deps (required to build 'builder')
Executed: build builder
Executed: skip pull builder (already ran)
Executed: skip overlay builder (already ran)
Executed: skip build builder (already ran)
Executed: stage builder (required to build 'copy-files')
Executed: build copy-files
Executed: build pebble
Executed: build security-team-requirement
Executed: skip stage base-deps (already ran)
Executed: stage base-snaps
Executed: skip stage builder (already ran)
Executed: stage copy-files
Executed: stage pebble
Executed: stage security-team-requirement
Executed: prime base-deps
Executed: prime base-snaps
Executed: prime builder
Executed: prime copy-files
Executed: prime pebble
Executed: prime security-team-requirement
Executed parts lifecycle
Exported to OCI archive 'argoexec_v3.3.8_22.04_1_amd64.rock'

$ ls -la argoexec_v3.3.8_22.04_1_amd64.rock
-rw-r--r-- 1 ubuntu ubuntu 78834688 Sep  1 14:42 argoexec_v3.3.8_22.04_1_amd64.rock

Unit tests
$ tox -e unit
unit: commands[0]> bash -c 'NAME=$(yq eval .name rockcraft.yaml) && VERSION=$(yq eval .version rockcraft.yaml) && ARCH=$(yq eval ".platforms | keys" rockcraft.yaml | awk -F " " '"'"'{ print $2 }'"'"') && ROCK="${NAME}_${VERSION}_${ARCH}" && sudo skopeo --insecure-policy copy oci-archive:$ROCK.rock docker-daemon:$ROCK:$VERSION && docker save $ROCK > $ROCK.tar'
Getting image source signatures
Copying blob 7dfb97c84515 done
Copying blob 90d324b54cbd done
Copying blob 49a6e14cf7f4 done
Copying blob 9ca3e10e5356 done
Copying config f9e68d0aa6 done
Writing manifest to image destination
Storing signatures
unit: commands[1]> pytest -v --tb native --show-capture=all --log-cli-level=INFO /home/ubuntu/rocks/argo-workflows-rocks/argoexec/tests
=============================================== test session starts ===============================================
platform linux -- Python 3.8.10, pytest-7.4.0, pluggy-1.2.0 -- /home/ubuntu/rocks/argo-workflows-rocks/argoexec/.tox/unit/bin/python
cachedir: .tox/unit/.pytest_cache
rootdir: /home/ubuntu/rocks/argo-workflows-rocks/argoexec
plugins: anyio-3.7.1, asyncio-0.21.1, operator-0.29.0
asyncio: mode=strict
collected 1 item

tests/test_rock.py::test_rock_artefacts
------------------------------------------------- live log setup --------------------------------------------------
INFO     pytest_operator.plugin:plugin.py:647 Adding model microk8s-localhost:test-rock-h5dl on cloud microk8s
PASSED                                                                                [100%]
------------------------------------------------ live log teardown ------------------------------------------------
INFO     pytest_operator.plugin:plugin.py:783 Model status:

Model           Controller          Cloud/Region        Version  SLA          Timestamp
test-rock-h5dl  microk8s-localhost  microk8s/localhost  2.9.44   unsupported  14:21:25-04:00

INFO     pytest_operator.plugin:plugin.py:789 Juju error logs:

INFO     pytest_operator.plugin:plugin.py:877 Resetting model test-rock-h5dl...
INFO     pytest_operator.plugin:plugin.py:882 Not waiting on reset to complete.
INFO     pytest_operator.plugin:plugin.py:855 Forgetting main...

================================================ warnings summary =================================================
tests/test_rock.py::test_rock_artefacts
tests/test_rock.py::test_rock_artefacts
  /home/ubuntu/rocks/argo-workflows-rocks/argoexec/.tox/unit/lib/python3.8/site-packages/websockets/protocol.py:218: DeprecationWarning: The loop argument is deprecated since Python 3.8, and scheduled for removal in Python 3.10.
    self._drain_lock = asyncio.Lock(loop=loop)

tests/test_rock.py::test_rock_artefacts
tests/test_rock.py::test_rock_artefacts
  /home/ubuntu/rocks/argo-workflows-rocks/argoexec/.tox/unit/lib/python3.8/site-packages/websockets/protocol.py:977: DeprecationWarning: The loop argument is deprecated since Python 3.8, and scheduled for removal in Python 3.10.
    yield from asyncio.sleep(self.ping_interval, loop=self.loop)

tests/test_rock.py: 20 warnings
  /home/ubuntu/rocks/argo-workflows-rocks/argoexec/.tox/unit/lib/python3.8/site-packages/websockets/protocol.py:911: DeprecationWarning: 'with (yield from lock)' is deprecated use 'async with lock' instead
    with (yield from self._drain_lock):

tests/test_rock.py: 20 warnings
  /home/ubuntu/rocks/argo-workflows-rocks/argoexec/.tox/unit/lib/python3.8/site-packages/websockets/protocol.py:416: DeprecationWarning: The loop argument is deprecated since Python 3.8, and scheduled for removal in Python 3.10.
    yield from asyncio.wait(

tests/test_rock.py::test_rock_artefacts
tests/test_rock.py::test_rock_artefacts
  /home/ubuntu/rocks/argo-workflows-rocks/argoexec/.tox/unit/lib/python3.8/site-packages/websockets/protocol.py:532: DeprecationWarning: The loop argument is deprecated since Python 3.8, and scheduled for removal in Python 3.10.
    yield from asyncio.wait_for(

tests/test_rock.py::test_rock_artefacts
tests/test_rock.py::test_rock_artefacts
  /home/ubuntu/rocks/argo-workflows-rocks/argoexec/.tox/unit/lib/python3.8/site-packages/websockets/protocol.py:554: DeprecationWarning: The loop argument is deprecated since Python 3.8, and scheduled for removal in Python 3.10.
    yield from asyncio.wait_for(

tests/test_rock.py::test_rock_artefacts
tests/test_rock.py::test_rock_artefacts
  /home/ubuntu/rocks/argo-workflows-rocks/argoexec/.tox/unit/lib/python3.8/site-packages/websockets/protocol.py:1077: DeprecationWarning: The loop argument is deprecated since Python 3.8, and scheduled for removal in Python 3.10.
    yield from asyncio.wait_for(

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
========================================= 1 passed, 50 warnings in 5.00s ==========================================
  unit: OK (12.88=setup[0.13]+cmd[5.87,6.88] seconds)
  congratulations :) (12.96 seconds)

Integration tests
$ tox -e integration
integration: recreate env because requirements removed: multidict==6.0.4 attrs==23.1.0 tenacity==8.2.3 frozenlist==1.4.0 yarl==1.9.2 websocket-client==1.6.1 aiosignal==1.3.1 async-timeout==4.0.3 aiohttp==3.8.5
integration: remove tox env folder /home/ubuntu/rocks/argo-workflows-rocks/argoexec/.tox/integration
integration: install_deps> python -I -m pip install -r requirements-integration.txt
integration: commands[0]> rm -rf charm_repo
integration: commands[1]> git clone --branch main https://github.com/canonical/argo-operators.git charm_repo
Cloning into 'charm_repo'...
remote: Enumerating objects: 1391, done.
remote: Counting objects: 100% (184/184), done.
remote: Compressing objects: 100% (93/93), done.
remote: Total 1391 (delta 124), reused 123 (delta 89), pack-reused 1207
Receiving objects: 100% (1391/1391), 341.40 KiB | 4.02 MiB/s, done.
Resolving deltas: 100% (681/681), done.
integration: commands[2]> bash -c 'NAME=$(yq eval .name rockcraft.yaml) && VERSION=$(yq eval .version rockcraft.yaml) && ARCH=$(yq eval ".platforms | keys" rockcraft.yaml | awk -F " " '"'"'{ print $2 }'"'"') && ROCK="${NAME}_${VERSION}_${ARCH}" && sudo skopeo --insecure-policy copy oci-archive:$ROCK.rock docker-daemon:$ROCK:$VERSION && docker save $ROCK > $ROCK.tar && microk8s ctr image import $ROCK.tar && microk8s ctr image list | grep argoexec && yq e -i ".options.executor-image.default=\"$ROCK:$VERSION\"" charm_repo/charms/argo-controller/config.yaml'
Getting image source signatures
Copying blob 7dfb97c84515 done
Copying blob 90d324b54cbd done
Copying blob 49a6e14cf7f4 done
Copying blob 9ca3e10e5356 done
Copying config f9e68d0aa6 done
Writing manifest to image destination
Storing signatures
unpacking docker.io/library/argoexec_v3.3.8_22.04_1_amd64:v3.3.8_22.04_1 (sha256:1a0e8e73597f469126b1763e6da198d24d7d7bbcdcd856d2063cba1f529b4164)...done
docker.io/library/argoexec_v3.3.8_22.04_1_amd64:v3.3.8_22.04_1                                                application/vnd.docker.distribution.manifest.v2+json      sha256:1a0e8e73597f469126b1763e6da198d24d7d7bbcdcd856d2063cba1f529b4164 210.7 MiB linux/amd64                                                                                io.cri-containerd.image=managed
integration: commands[3]> tox -c charm_repo/charms/argo-controller -e integration
integration: recreate env because requirements removed: ops==2.5.1 websocket-client==1.6.2
integration: remove tox env folder /home/ubuntu/rocks/argo-workflows-rocks/argoexec/.tox/integration
integration: install_deps /home/ubuntu/rocks/argo-workflows-rocks/argoexec/charm_repo/charms/argo-controller> python -I -m pip install -r requirements-integration.txt
integration: commands[0] /home/ubuntu/rocks/argo-workflows-rocks/argoexec/charm_repo/charms/argo-controller> pytest -v --tb native --asyncio-mode=auto /home/ubuntu/rocks/argo-workflows-rocks/argoexec/charm_repo/charms/argo-controller/tests/integration --log-cli-level=INFO -s
=============================================== test session starts ===============================================
platform linux -- Python 3.8.10, pytest-7.4.0, pluggy-1.2.0 -- /home/ubuntu/rocks/argo-workflows-rocks/argoexec/.tox/integration/bin/python
cachedir: /home/ubuntu/rocks/argo-workflows-rocks/argoexec/.tox/integration/.pytest_cache
rootdir: /home/ubuntu/rocks/argo-workflows-rocks/argoexec/charm_repo/charms/argo-controller
configfile: pyproject.toml
plugins: asyncio-0.21.1, operator-0.28.0
asyncio: mode=auto
collected 3 items

tests/integration/test_charm.py::test_build_and_deploy_with_relations
------------------------------------------------- live log setup --------------------------------------------------
INFO     pytest_operator.plugin:plugin.py:647 Adding model microk8s-localhost:test-charm-tlbr on cloud microk8s
-------------------------------------------------- live log call --------------------------------------------------
INFO     pytest_operator.plugin:plugin.py:526 Using tmp_path: /home/ubuntu/rocks/argo-workflows-rocks/argoexec/.tox/integration/tmp/pytest/test-charm-tlbr0
INFO     pytest_operator.plugin:plugin.py:982 Building charm argo-controller
INFO     pytest_operator.plu$ tox -e integration
integration: recreate env because requirements removed: multidict==6.0.4 attrs==23.1.0 tenacity==8.2.3 frozenlist==1.4.0 yarl==1.9.2 websocket-client==1.6.1 aiosignal==1.3.1 async-timeout==4.0.3 aiohttp==3.8.5
integration: remove tox env folder /home/ubuntu/rocks/argo-workflows-rocks/argoexec/.tox/integration
integration: install_deps> python -I -m pip install -r requirements-integration.txt
integration: commands[0]> rm -rf charm_repo
integration: commands[1]> git clone --branch main https://github.com/canonical/argo-operators.git charm_repo
Cloning into 'charm_repo'...
remote: Enumerating objects: 1391, done.
remote: Counting objects: 100% (184/184), done.
remote: Compressing objects: 100% (93/93), done.
remote: Total 1391 (delta 124), reused 123 (delta 89), pack-reused 1207
Receiving objects: 100% (1391/1391), 341.40 KiB | 4.02 MiB/s, done.
Resolving deltas: 100% (681/681), done.
integration: commands[2]> bash -c 'NAME=$(yq eval .name rockcraft.yaml) && VERSION=$(yq eval .version rockcraft.yaml) && ARCH=$(yq eval ".platforms | keys" rockcraft.yaml | awk -F " " '"'"'{ print $2 }'"'"') && ROCK="${NAME}_${VERSION}_${ARCH}" && sudo skopeo --insecure-policy copy oci-archive:$ROCK.rock docker-daemon:$ROCK:$VERSION && docker save $ROCK > $ROCK.tar && microk8s ctr image import $ROCK.tar && microk8s ctr image list | grep argoexec && yq e -i ".options.executor-image.default=\"$ROCK:$VERSION\"" charm_repo/charms/argo-controller/config.yaml'
Getting image source signatures
Copying blob 7dfb97c84515 done
Copying blob 90d324b54cbd done
Copying blob 49a6e14cf7f4 done
Copying blob 9ca3e10e5356 done
Copying config f9e68d0aa6 done
Writing manifest to image destination
Storing signatures
unpacking docker.io/library/argoexec_v3.3.8_22.04_1_amd64:v3.3.8_22.04_1 (sha256:1a0e8e73597f469126b1763e6da198d24d7d7bbcdcd856d2063cba1f529b4164)...done
docker.io/library/argoexec_v3.3.8_22.04_1_amd64:v3.3.8_22.04_1                                                application/vnd.docker.distribution.manifest.v2+json      sha256:1a0e8e73597f469126b1763e6da198d24d7d7bbcdcd856d2063cba1f529b4164 210.7 MiB linux/amd64                                                                                io.cri-containerd.image=managed
integration: commands[3]> tox -c charm_repo/charms/argo-controller -e integration
integration: recreate env because requirements removed: ops==2.5.1 websocket-client==1.6.2
integration: remove tox env folder /home/ubuntu/rocks/argo-workflows-rocks/argoexec/.tox/integration
integration: install_deps /home/ubuntu/rocks/argo-workflows-rocks/argoexec/charm_repo/charms/argo-controller> python -I -m pip install -r requirements-integration.txt
integration: commands[0] /home/ubuntu/rocks/argo-workflows-rocks/argoexec/charm_repo/charms/argo-controller> pytest -v --tb native --asyncio-mode=auto /home/ubuntu/rocks/argo-workflows-rocks/argoexec/charm_repo/charms/argo-controller/tests/integration --log-cli-level=INFO -s
=============================================== test session starts ===============================================
platform linux -- Python 3.8.10, pytest-7.4.0, pluggy-1.2.0 -- /home/ubuntu/rocks/argo-workflows-rocks/argoexec/.tox/integration/bin/python
cachedir: /home/ubuntu/rocks/argo-workflows-rocks/argoexec/.tox/integration/.pytest_cache
rootdir: /home/ubuntu/rocks/argo-workflows-rocks/argoexec/charm_repo/charms/argo-controller
configfile: pyproject.toml
plugins: asyncio-0.21.1, operator-0.28.0
asyncio: mode=auto
collected 3 items

tests/integration/test_charm.py::test_build_and_deploy_with_relations
------------------------------------------------- live log setup --------------------------------------------------
INFO     pytest_operator.plugin:plugin.py:647 Adding model microk8s-localhost:test-charm-tlbr on cloud microk8s
-------------------------------------------------- live log call --------------------------------------------------
INFO     pytest_operator.plugin:plugin.py:526 Using tmp_path: /home/ubuntu/rocks/argo-workflows-rocks/argoexec/.tox/integration/tmp/pytest/test-charm-tlbr0
INFO     pytest_operator.plugin:plugin.py:982 Building charm argo-controller
INFO     pytest_operator.plugin:plugin.py:987 Built charm argo-controller in 139.37s
INFO     test_charm:test_charm.py:29 Built charm /home/ubuntu/rocks/argo-workflows-rocks/argoexec/.tox/integration/tmp/pytest/test-charm-tlbr0/charms/argo-controller_ubuntu-20.04-amd64.charm
INFO     juju.model:model.py:1981 Deploying local:kubernetes/argo-controller-0
INFO     juju.model:model.py:1981 Deploying ch:amd64/focal/minio-57
INFO     juju.model:model.py:2618 Waiting for model:
  argo-controller/0 [allocating] waiting: installing agent
  minio/0 [allocating] waiting: installing agent
INFO     juju.model:model.py:2618 Waiting for model:
  argo-controller/0 [allocating] waiting: agent initializing
  minio/0 [allocating] waiting: installing agent
INFO     juju.model:model.py:2618 Waiting for model:
  argo-controller/0 [executing] active:
  minio/0 [executing] active:
INFO     juju.model:model.py:2618 Waiting for model:
  argo-controller/0 [idle] active:
INFO     juju.model:model.py:2618 Waiting for model:
  argo-controller/0 [idle] active:
INFO     juju.model:model.py:2618 Waiting for model:
  argo-controller/0 [idle] active:
PASSED
tests/integration/test_charm.py::test_workflow_using_artifacts
-------------------------------------------------- live log call --------------------------------------------------
INFO     test_charm:test_charm.py:105 Found workflow_name=workflow.argoproj.io/artifact-passing-48zcs
INFO     test_charm:test_charm.py:106 Waiting on workflow.argoproj.io/artifact-passing-48zcs to finish
PASSED
tests/integration/test_charm.py::test_prometheus_grafana_integration
-------------------------------------------------- live log call --------------------------------------------------
INFO     juju.model:model.py:1981 Deploying ch:amd64/focal/prometheus-k8s-103
INFO     juju.model:model.py:1981 Deploying ch:amd64/focal/grafana-k8s-81
INFO     juju.model:model.py:1981 Deploying ch:amd64/focal/prometheus-scrape-config-k8s-39
INFO     juju.model:model.py:2618 Waiting for model:
  argo-controller/0 [executing] active:
  minio/0 [idle] active:
  prometheus-k8s/0 [allocating] waiting: installing agent
  grafana-k8s/0 [allocating] waiting: installing agent
  prometheus-scrape-config-k8s/0 [allocating] waiting: installing agent
INFO     juju.model:model.py:2618 Waiting for model:
  argo-controller/0 [executing] active:
  prometheus-k8s/0 [executing] maintenance: installing charm software
  grafana-k8s/0 [allocating] waiting: agent initializing
  prometheus-scrape-config-k8s/0 [executing] maintenance: installing charm software
INFO     juju.model:model.py:2618 Waiting for model:
  argo-controller/0 [executing] active:
  prometheus-k8s/0 [executing] maintenance:
  grafana-k8s/0 [executing] maintenance: installing charm software
INFO     juju.model:model.py:2618 Waiting for model:
  prometheus-k8s/0 [executing] active:
  grafana-k8s/0 [executing] unknown:
INFO     juju.model:model.py:2618 Waiting for model:
  prometheus-k8s/0 [idle] active:
  grafana-k8s/0 [executing] maintenance: Waiting for resource limit patch to apply
INFO     juju.model:model.py:2618 Waiting for model:
  grafana-k8s/0 [executing] maintenance:
INFO     juju.model:model.py:2618 Waiting for model:
  grafana-k8s/0 [executing] active:
INFO     test_charm:test_charm.py:159 Prometheus available at http://<IP_ADDRESS>:9090
INFO     test_charm:test_charm.py:162 Testing prometheus deployment (attempt 1)
INFO     test_charm:test_charm.py:172 Response status is success
INFO     test_charm:test_charm.py:181 Testing prometheus targets (attempt 1)
INFO     test_charm:test_charm.py:187 Response status is success
INFO     test_charm:test_charm.py:196 Testing prometheus rules (attempt 1)
INFO     test_charm:test_charm.py:202 Response status is success
PASSED
------------------------------------------------ live log teardown ------------------------------------------------
INFO     pytest_operator.plugin:plugin.py:790 Model status:

Model            Controller          Cloud/Region        Version  SLA          Timestamp
test-charm-tlbr  microk8s-localhost  microk8s/localhost  2.9.44   unsupported  14:20:42-04:00

App                           Version                         Status  Scale  Charm                         Channel        Rev  Address         Exposed  Message
argo-controller               .../workflow-controller:v3.3.8  active      1  argo-controller                                0                  no
grafana-k8s                   9.2.1                           active      1  grafana-k8s                   latest/stable   81  <IP_ADDRESS>  no
minio                         res:oci-image@1755999           active      1  minio                         latest/stable   57  <IP_ADDRESS>  no
prometheus-k8s                2.33.5                          active      1  prometheus-k8s                latest/stable  103  <IP_ADDRESS>  no
prometheus-scrape-config-k8s  n/a                             active      1  prometheus-scrape-config-k8s  latest/stable   39  <IP_ADDRESS>  no

Unit                             Workload  Agent  Address       Ports     Message
argo-controller/0*               active    idle   <IP_ADDRESS>
grafana-k8s/0*                   active    idle   <IP_ADDRESS>
minio/0*                         active    idle   <IP_ADDRESS>  9000/TCP
prometheus-k8s/0*                active    idle   <IP_ADDRESS>
prometheus-scrape-config-k8s/0*  active    idle   <IP_ADDRESS>

INFO     pytest_operator.plugin:plugin.py:796 Juju error logs:

unit-prometheus-k8s-0: 14:18:15 ERROR juju.worker.uniter pebble poll failed for container "prometheus": failed to send pebble-ready event: terminated

INFO     pytest_operator.plugin:plugin.py:884 Resetting model test-charm-tlbr...
INFO     pytest_operator.plugin:plugin.py:873    Destroying applications argo-controller
INFO     pytest_operator.plugin:plugin.py:873    Destroying applications minio
INFO     pytest_operator.plugin:plugin.py:873    Destroying applications prometheus-k8s
INFO     pytest_operator.plugin:plugin.py:873    Destroying applications grafana-k8s
INFO     pytest_operator.plugin:plugin.py:873    Destroying applications prometheus-scrape-config-k8s
INFO     pytest_operator.plugin:plugin.py:889 Not waiting on reset to complete.
INFO     pytest_operator.plugin:plugin.py:862 Forgetting main...

================================================ warnings summary =================================================
tests/integration/test_charm.py::test_build_and_deploy_with_relations
tests/integration/test_charm.py::test_build_and_deploy_with_relations
  /home/ubuntu/rocks/argo-workflows-rocks/argoexec/.tox/integration/lib/python3.8/site-packages/websockets/protocol.py:218: DeprecationWarning: The loop argument is deprecated since Python 3.8, and scheduled for removal in Python 3.10.
    self._drain_lock = asyncio.Lock(loop=loop)

tests/integration/test_charm.py: 62 warnings
  /home/ubuntu/rocks/argo-workflows-rocks/argoexec/.tox/integration/lib/python3.8/site-packages/websockets/protocol.py:977: DeprecationWarning: The loop argument is deprecated since Python 3.8, and scheduled for removal in Python 3.10.
    yield from asyncio.sleep(self.ping_interval, loop=self.loop)

tests/integration/test_charm.py: 2619 warnings
  /home/ubuntu/rocks/argo-workflows-rocks/argoexec/.tox/integration/lib/python3.8/site-packages/websockets/protocol.py:911: DeprecationWarning: 'with (yield from lock)' is deprecated use 'async with lock' instead
    with (yield from self._drain_lock):

tests/integration/test_charm.py: 2554 warnings
  /home/ubuntu/rocks/argo-workflows-rocks/argoexec/.tox/integration/lib/python3.8/site-packages/websockets/protocol.py:416: DeprecationWarning: The loop argument is deprecated since Python 3.8, and scheduled for removal in Python 3.10.
    yield from asyncio.wait(

tests/integration/test_charm.py: 60 warnings
  /home/ubuntu/rocks/argo-workflows-rocks/argoexec/.tox/integration/lib/python3.8/site-packages/websockets/protocol.py:988: DeprecationWarning: The loop argument is deprecated since Python 3.8, and scheduled for removal in Python 3.10.
    yield from asyncio.wait_for(

tests/integration/test_charm.py::test_prometheus_grafana_integration
tests/integration/test_charm.py::test_prometheus_grafana_integration
  /home/ubuntu/rocks/argo-workflows-rocks/argoexec/.tox/integration/lib/python3.8/site-packages/websockets/protocol.py:532: DeprecationWarning: The loop argument is deprecated since Python 3.8, and scheduled for removal in Python 3.10.
    yield from asyncio.wait_for(

tests/integration/test_charm.py::test_prometheus_grafana_integration
tests/integration/test_charm.py::test_prometheus_grafana_integration
  /home/ubuntu/rocks/argo-workflows-rocks/argoexec/.tox/integration/lib/python3.8/site-packages/websockets/protocol.py:554: DeprecationWarning: The loop argument is deprecated since Python 3.8, and scheduled for removal in Python 3.10.
    yield from asyncio.wait_for(

tests/integration/test_charm.py::test_prometheus_grafana_integration
tests/integration/test_charm.py::test_prometheus_grafana_integration
  /home/ubuntu/rocks/argo-workflows-rocks/argoexec/.tox/integration/lib/python3.8/site-packages/websockets/protocol.py:1077: DeprecationWarning: The loop argument is deprecated since Python 3.8, and scheduled for removal in Python 3.10.
    yield from asyncio.wait_for(

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
================================== 3 passed, 5303 warnings in 602.40s (0:10:02) ===================================
  integration: OK (627.70=setup[23.71]+cmd[603.99] seconds)
  congratulations :) (627.74 seconds)
  integration: OK (660.71=setup[23.23]+cmd[0.04,0.68,8.93,627.84] seconds)
  congratulations :) (660.77 seconds)
gin:plugin.py:987 Built charm argo-controller in 139.37s
INFO     test_charm:test_charm.py:29 Built charm /home/ubuntu/rocks/argo-workflows-rocks/argoexec/.tox/integration/tmp/pytest/test-charm-tlbr0/charms/argo-controller_ubuntu-20.04-amd64.charm
INFO     juju.model:model.py:1981 Deploying local:kubernetes/argo-controller-0
INFO     juju.model:model.py:1981 Deploying ch:amd64/focal/minio-57
INFO     juju.model:model.py:2618 Waiting for model:
  argo-controller/0 [allocating] waiting: installing agent
  minio/0 [allocating] waiting: installing agent
INFO     juju.model:model.py:2618 Waiting for model:
  argo-controller/0 [allocating] waiting: agent initializing
  minio/0 [allocating] waiting: installing agent
INFO     juju.model:model.py:2618 Waiting for model:
  argo-controller/0 [executing] active:
  minio/0 [executing] active:
INFO     juju.model:model.py:2618 Waiting for model:
  argo-controller/0 [idle] active:
INFO     juju.model:model.py:2618 Waiting for model:
  argo-controller/0 [idle] active:
INFO     juju.model:model.py:2618 Waiting for model:
  argo-controller/0 [idle] active:
PASSED
tests/integration/test_charm.py::test_workflow_using_artifacts
-------------------------------------------------- live log call --------------------------------------------------
INFO     test_charm:test_charm.py:105 Found workflow_name=workflow.argoproj.io/artifact-passing-48zcs
INFO     test_charm:test_charm.py:106 Waiting on workflow.argoproj.io/artifact-passing-48zcs to finish
PASSED
tests/integration/test_charm.py::test_prometheus_grafana_integration
-------------------------------------------------- live log call --------------------------------------------------
INFO     juju.model:model.py:1981 Deploying ch:amd64/focal/prometheus-k8s-103
INFO     juju.model:model.py:1981 Deploying ch:amd64/focal/grafana-k8s-81
INFO     juju.model:model.py:1981 Deploying ch:amd64/focal/prometheus-scrape-config-k8s-39
INFO     juju.model:model.py:2618 Waiting for model:
  argo-controller/0 [executing] active:
  minio/0 [idle] active:
  prometheus-k8s/0 [allocating] waiting: installing agent
  grafana-k8s/0 [allocating] waiting: installing agent
  prometheus-scrape-config-k8s/0 [allocating] waiting: installing agent
INFO     juju.model:model.py:2618 Waiting for model:
  argo-controller/0 [executing] active:
  prometheus-k8s/0 [executing] maintenance: installing charm software
  grafana-k8s/0 [allocating] waiting: agent initializing
  prometheus-scrape-config-k8s/0 [executing] maintenance: installing charm software
INFO     juju.model:model.py:2618 Waiting for model:
  argo-controller/0 [executing] active:
  prometheus-k8s/0 [executing] maintenance:
  grafana-k8s/0 [executing] maintenance: installing charm software
INFO     juju.model:model.py:2618 Waiting for model:
  prometheus-k8s/0 [executing] active:
  grafana-k8s/0 [executing] unknown:
INFO     juju.model:model.py:2618 Waiting for model:
  prometheus-k8s/0 [idle] active:
  grafana-k8s/0 [executing] maintenance: Waiting for resource limit patch to apply
INFO     juju.model:model.py:2618 Waiting for model:
  grafana-k8s/0 [executing] maintenance:
INFO     juju.model:model.py:2618 Waiting for model:
  grafana-k8s/0 [executing] active:
INFO     test_charm:test_charm.py:159 Prometheus available at http://<IP_ADDRESS>:9090
INFO     test_charm:test_charm.py:162 Testing prometheus deployment (attempt 1)
INFO     test_charm:test_charm.py:172 Response status is success
INFO     test_charm:test_charm.py:181 Testing prometheus targets (attempt 1)
INFO     test_charm:test_charm.py:187 Response status is success
INFO     test_charm:test_charm.py:196 Testing prometheus rules (attempt 1)
INFO     test_charm:test_charm.py:202 Response status is success
PASSED
------------------------------------------------ live log teardown ------------------------------------------------
INFO     pytest_operator.plugin:plugin.py:790 Model status:

Model            Controller          Cloud/Region        Version  SLA          Timestamp
test-charm-tlbr  microk8s-localhost  microk8s/localhost  2.9.44   unsupported  14:20:42-04:00

App                           Version                         Status  Scale  Charm                         Channel        Rev  Address         Exposed  Message
argo-controller               .../workflow-controller:v3.3.8  active      1  argo-controller                                0                  no
grafana-k8s                   9.2.1                           active      1  grafana-k8s                   latest/stable   81  <IP_ADDRESS>  no
minio                         res:oci-image@1755999           active      1  minio                         latest/stable   57  <IP_ADDRESS>  no
prometheus-k8s                2.33.5                          active      1  prometheus-k8s                latest/stable  103  <IP_ADDRESS>  no
prometheus-scrape-config-k8s  n/a                             active      1  prometheus-scrape-config-k8s  latest/stable   39  <IP_ADDRESS>  no

Unit                             Workload  Agent  Address       Ports     Message
argo-controller/0*               active    idle   <IP_ADDRESS>
grafana-k8s/0*                   active    idle   <IP_ADDRESS>
minio/0*                         active    idle   <IP_ADDRESS>  9000/TCP
prometheus-k8s/0*                active    idle   <IP_ADDRESS>
prometheus-scrape-config-k8s/0*  active    idle   <IP_ADDRESS>

INFO     pytest_operator.plugin:plugin.py:796 Juju error logs:

unit-prometheus-k8s-0: 14:18:15 ERROR juju.worker.uniter pebble poll failed for container "prometheus": failed to send pebble-ready event: terminated

INFO     pytest_operator.plugin:plugin.py:884 Resetting model test-charm-tlbr...
INFO     pytest_operator.plugin:plugin.py:873    Destroying applications argo-controller
INFO     pytest_operator.plugin:plugin.py:873    Destroying applications minio
INFO     pytest_operator.plugin:plugin.py:873    Destroying applications prometheus-k8s
INFO     pytest_operator.plugin:plugin.py:873    Destroying applications grafana-k8s
INFO     pytest_operator.plugin:plugin.py:873    Destroying applications prometheus-scrape-config-k8s
INFO     pytest_operator.plugin:plugin.py:889 Not waiting on reset to complete.
INFO     pytest_operator.plugin:plugin.py:862 Forgetting main...

================================================ warnings summary =================================================
tests/integration/test_charm.py::test_build_and_deploy_with_relations
tests/integration/test_charm.py::test_build_and_deploy_with_relations
  /home/ubuntu/rocks/argo-workflows-rocks/argoexec/.tox/integration/lib/python3.8/site-packages/websockets/protocol.py:218: DeprecationWarning: The loop argument is deprecated since Python 3.8, and scheduled for removal in Python 3.10.
    self._drain_lock = asyncio.Lock(loop=loop)

tests/integration/test_charm.py: 62 warnings
  /home/ubuntu/rocks/argo-workflows-rocks/argoexec/.tox/integration/lib/python3.8/site-packages/websockets/protocol.py:977: DeprecationWarning: The loop argument is deprecated since Python 3.8, and scheduled for removal in Python 3.10.
    yield from asyncio.sleep(self.ping_interval, loop=self.loop)

tests/integration/test_charm.py: 2619 warnings
  /home/ubuntu/rocks/argo-workflows-rocks/argoexec/.tox/integration/lib/python3.8/site-packages/websockets/protocol.py:911: DeprecationWarning: 'with (yield from lock)' is deprecated use 'async with lock' instead
    with (yield from self._drain_lock):

tests/integration/test_charm.py: 2554 warnings
  /home/ubuntu/rocks/argo-workflows-rocks/argoexec/.tox/integration/lib/python3.8/site-packages/websockets/protocol.py:416: DeprecationWarning: The loop argument is deprecated since Python 3.8, and scheduled for removal in Python 3.10.
    yield from asyncio.wait(

tests/integration/test_charm.py: 60 warnings
  /home/ubuntu/rocks/argo-workflows-rocks/argoexec/.tox/integration/lib/python3.8/site-packages/websockets/protocol.py:988: DeprecationWarning: The loop argument is deprecated since Python 3.8, and scheduled for removal in Python 3.10.
    yield from asyncio.wait_for(

tests/integration/test_charm.py::test_prometheus_grafana_integration
tests/integration/test_charm.py::test_prometheus_grafana_integration
  /home/ubuntu/rocks/argo-workflows-rocks/argoexec/.tox/integration/lib/python3.8/site-packages/websockets/protocol.py:532: DeprecationWarning: The loop argument is deprecated since Python 3.8, and scheduled for removal in Python 3.10.
    yield from asyncio.wait_for(

tests/integration/test_charm.py::test_prometheus_grafana_integration
tests/integration/test_charm.py::test_prometheus_grafana_integration
  /home/ubuntu/rocks/argo-workflows-rocks/argoexec/.tox/integration/lib/python3.8/site-packages/websockets/protocol.py:554: DeprecationWarning: The loop argument is deprecated since Python 3.8, and scheduled for removal in Python 3.10.
    yield from asyncio.wait_for(

tests/integration/test_charm.py::test_prometheus_grafana_integration
tests/integration/test_charm.py::test_prometheus_grafana_integration
  /home/ubuntu/rocks/argo-workflows-rocks/argoexec/.tox/integration/lib/python3.8/site-packages/websockets/protocol.py:1077: DeprecationWarning: The loop argument is deprecated since Python 3.8, and scheduled for removal in Python 3.10.
    yield from asyncio.wait_for(

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
================================== 3 passed, 5303 warnings in 602.40s (0:10:02) ===================================
  integration: OK (627.70=setup[23.71]+cmd[603.99] seconds)
  congratulations :) (627.74 seconds)
  integration: OK (660.71=setup[23.23]+cmd[0.04,0.68,8.93,627.84] seconds)
  congratulations :) (660.77 seconds)

Thanks @i-chvets, the rock looks good, just a comment on the tox.ini and test file as we are moving towards improving the way we build and test rocks.
The tox.ini file in this PR will most likely change, and it's completely up to you, but I would split this PR moving thetests/ and tox.ini changes to another PR and just leaving the rock update.

Done.