[Autocomplete] openOnFocus is not working properly

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
The popup opens even when openOnFocus is set to false which is the default value according to Autocomplete api doc

But if you focus towards the end of the input, it's not opening the popup - i.e., working as expected

Expected Behavior 🤔
The popup should not open when openOnFocus is set to false no matter where the user focuses in the input.
Steps to Reproduce 🕹
https://codesandbox.io/s/gallant-leaf-1u4zg

@sruthisripathi Only a click on the <input> will open the popup. I'm not aware of any alternative.

@sruthisripathi Only a click on the <input> will open the popup. I'm not aware of any alternative.

There is a padding around input field due to which you can focus just outside <input> but well inside what appears to be the textbox for autocomplete. If you focus in that padding area and you have set openOnFocus to false, then the popup is not opening. If you focus inside <input>, the popup's opening even if you set openOnFocus to false.

Ahhh!  It's totally the click.  I think there should at least be a note about that in the docs if this won't be fixed.  The openOnFocus api works when tabbing focus onto the field but doesn't work as expected if I click on it.

I'll be using controlled open with setOpen as a workaround...

useAutomplete.js:868 is responsible of opening the popup, and it doesn't check openOnFocus value.
I got a workaround by using onMouseDownCapture={(e) => e.stopPropagation()}} on the <Input>, but it would be nice to fix it.

Came across this issue after discovering that openOnFocus was not working as expected. My use case is that I do not want to ping my server for options until the user has typed something. Thanks @AurelienVernay for the workaround until this is resolved.

@oliviertassinari I believe it's been properly established that openOnFocus is either broken or by design not working as people expect, this issue should be reopened.

@oliviertassinari Could you clarify what openOnFocus is supposed to do? I can't find a difference with this value on or off and none of our tests run with the prop turned off .

The openOnFocus prop allows developers to open the popup when the textbox receives the focus (Tab). In the issue's description, the popup is open by a click event on the <input>, not by the focus event. So it seems to behave correctly. I think that developers commenting here want a new `disableOpenOnClick prop. So far we didn't implement it. Instead, we have proposed to control the open state and filter the events they want to ignore.

Oh, I got confused by the linked codesandbox which labels itself as openOnFocus: false but actually has openOnFocus={true}. Maybe that is why the behavior was viewed as unexpected by @sruthisripathi.
This is good from my perspective. Should've started with my own codesandbox though I do think we should adjust our tests.

Hi @AurelienVernay
I have tried to use the useAutocomple.js file which will allow restricting the Popup if there is no option available. but getting an error while incorporating it with my existing code.
Followed steps
1)Copy useAutocomplete.js file
2)Import autocomplete files as a component
1)import useAutocomplete  from '../core-comp-customization/useAutocomplete.js   // Since this was showing undefined.
We tried with the below workaround
2)import UseAutocomplete  from '../core-comp-customization/useAutocomplete.js'
After that changes it was showing Getting error message:-  Error: Objects are not valid as a React child
Please share any working example where useAutocomple.js is imported & used
Please suggest

@oliviertassinari I don't think that's the case. I'm setting the internal TextField to autoFocus and the menu opens automatically - no click.

@benwiley4000 Do you have a reproduction with the latest version (v5.0.0-alpha.13)?

This issue still exists. @eps1lon I am using v5

Still experiencing this issue in 2024 on version 5.15.0.
Could we please update openOnFocus such that the popover doesn't open when the input receives focus unless openOnFocus is set (aka true) on the <Autocomplete> component?

Still experiencing this issue in 2024 on version 5.15.11

Still experiencing this on v5.15.14 as well. openOnFocus={false} still opens the popup when focusing the input.


add doc description about recovery

Fixes #70
Desc: Add Recovery descriptions.
Please take a look, I have checked there is no 404 like errors.

cc @Sad-polar-bear


Release documentation out of date

http://pythonhosted.org/CouchDB/changes.html does not list v 1.0.1

Thanks for reporting; I've fixed it.


Add input file type auto-detect for count[graph|table]

I'm wasting a lot of development time loading and re-loading Fastq data into counting data structures. Having the convenience of supporting Fasta/Fastq files as input is a priority, but I desperately need to take advantage of pre-computed countgraphs/counttables when they are available.
I propose the following behavior, which I think is 1) fairly reasonable from a user's perspective and 2) fairly straightforward to implement.

For data files to be loaded into a counting data structure, check the suffix.

If the suffix is .cg or .countgraph, load the file with khmer.load_countgraph().
If the suffix is .ct or .counttable, load the file with khmer.load_counttable().
Otherwise, assume the file is Fast[a|q]; create a counttable ct and load with ct.consume_seqfile().

Isn't there code in khmer that sniffs the file type? Much safer than relying on file extensions.

Looks like #71 is relevant.

Ideally, it would  be great to have khmer detect the file type and handle accordingly. Unless I'm reading the code incorrectly, though, sketches stored on disk only indicate the storage type (bit, byte, or nibble), and do not store whether they are a *table or *graph data structure. So additional input is needed from the user anyway, and that might as well come in the form of a filename, with all the challenges that entails.
All of this is ripe for a fresh look once https://github.com/dib-lab/khmer/pull/1595 is merged. @camillescott may well have already made some changes to the relevant code, but regardless we need to consider how we are going to support a growing list of hash functions (2bit, MurmurHash, rolling hash or hashes, more) and pre-processing options (consume with or without k-mer banding, consume with or without a mask, consume with or without [^ACGT] preprocessing) in a maintainable way.


Issue 11

fixes #11
This does everything described in #11 with the exception of calculating mean and median values when replicates are found. This is a bit too complicated to implement at this stage for two reasons: (1) at this stage we are just grabbing the IDs to compare, and the pairwise difference/distance values are computed later; (2) this would behave very differently for each method — e.g., average alpha diversity is easy but how do we calculate average distance? If you think we should still support averaging replicates in a later release, we can leave this issue open or create a dedicated issue.
This does NOT include unit tests — I will add those later on, as I intend to expand the error handling functions and will test together.

Coverage decreased (-0.5%) to 90.873% when pulling 69fda54ba88d7b9c13624034d6519bd0a71e6bde on nbokulich:issue-11 into b08bea95530a370cbf2c836b543b447765b452a9 on qiime2:master.

thanks @gregcaporaso ! I added a unit test and revised per your suggestions.

thanks @gregcaporaso ! The latter two changes are made as suggested.
The first change (about warning messages) has been turned into ticket #23


Investigate Uncaught ReferenceError: Tether is not defined in docs

Visit http://github.hubspot.com/tooltip and view the console.
@zackbloom maybe Tether isn't being bundled properly?

Forced correct scripts into page. Need to redo documentation though at some point


kube-state-metrics is missing despite being deployed and running and shows in Prometheus

Hi, I have main coroot deployed in one cluster and working on add other clusters to this one by adding already deployed prometheus, kube-state-metrics already deployed on them and just deploying coroot-node-agent, but I can't see kube-state-metrics and service map

so I started investgating and found this fails on the coroot-node-agent pods "failed to get container metadata for pid 16843 -> /kubepods/burstable/pod6f222fb5-3d0e-425e-899c-e5495124a057/ea64d45c2a6338bb0f9aae2f05ec4a77e323915d25ed11b19cb2504cbf2113d0: failed to interact with dockerd (%!s()) or with containerd (%!s())"
kubernetes version : v1.25.16+vmware.1
OS: Ubuntu 22.04.4 LTS
kernal :  6.5.0-21-generic
container runtime : containerd://1.6.28
coroot node agent tag : 1.18.9

@yoyoraso, we need to examine the node-agent's log. Could you please restart it, wait a minute, and then provide the entire log here?

@apetruhin, here it is
I0510 14:40:50.531724  606823 net.go:30] ephemeral-port-range: 32768-60999
I0510 14:40:50.540212  606823 cilium.go:30] Unable to get object /proc/1/root/sys/fs/bpf/tc/globals/cilium_ct4_global: no such file or directory
I0510 14:40:50.540261  606823 cilium.go:36] Unable to get object /proc/1/root/sys/fs/bpf/tc/globals/cilium_ct6_global: no such file or directory
I0510 14:40:50.540272  606823 cilium.go:43] Unable to get object /proc/1/root/sys/fs/bpf/tc/globals/cilium_lb4_backends_v2: no such file or directory
I0510 14:40:50.540280  606823 cilium.go:43] Unable to get object /proc/1/root/sys/fs/bpf/tc/globals/cilium_lb4_backends_v3: no such file or directory
I0510 14:40:50.540290  606823 cilium.go:52] Unable to get object /proc/1/root/sys/fs/bpf/tc/globals/cilium_lb6_backends_v2: no such file or directory
I0510 14:40:50.540300  606823 cilium.go:52] Unable to get object /proc/1/root/sys/fs/bpf/tc/globals/cilium_lb6_backends_v3: no such file or directory
I0510 14:40:50.540313  606823 main.go:102] agent version: 1.18.9
I0510 14:40:50.540380  606823 main.go:108] hostname: ******
I0510 14:40:50.540389  606823 main.go:109] kernel version: 6.5.0-21-generic
I0510 14:40:50.541001  606823 main.go:75] machine-id:  ******
I0510 14:40:50.541035  606823 tracing.go:34] no OpenTelemetry traces collector endpoint configured
I0510 14:40:50.541048  606823 otel.go:26] no OpenTelemetry logs collector endpoint configured
I0510 14:40:50.541180  606823 metadata.go:67] cloud provider:
I0510 14:40:50.541193  606823 collector.go:157] instance metadata:
I0510 14:40:50.541282  606823 profiling.go:49] no profiles endpoint configured
W0510 14:40:50.541721  606823 registry.go:75] Cannot connect to the Docker daemon at unix:///proc/1/root/run/docker.sock. Is the docker daemon running?
W0510 14:40:50.541721  606823 registry.go:75] Cannot connect to the Docker daemon at unix:///proc/1/root/run/docker.sock. Is the docker daemon running?
W0510 14:40:54.544388  606823 registry.go:78] couldn't connect to containerd through the following UNIX sockets [/var/snap/microk8s/common/run/containerd.sock,/run/k0s/containerd.sock,/run/k3s/containerd/containerd.sock,/run/containerd/containerd.sock]: failed to dial "/proc/1/root/run/containerd/containerd.sock": context deadline exceeded
W0510 14:40:54.544388  606823 registry.go:78] couldn't connect to containerd through the following UNIX sockets [/var/snap/microk8s/common/run/containerd.sock,/run/k0s/containerd.sock,/run/k3s/containerd/containerd.sock,/run/containerd/containerd.sock]: failed to dial "/proc/1/root/run/containerd/containerd.sock": context deadline exceeded
W0510 14:40:54.544482  606823 registry.go:81] stat /proc/1/root/var/run/crio/crio.sock: no such file or directory
W0510 14:40:54.544482  606823 registry.go:81] stat /proc/1/root/var/run/crio/crio.sock: no such file or directory
I0510 14:40:54.878632  606823 registry.go:281] calculated container id 1 -> / ->
I0510 14:40:54.878729  606823 registry.go:286] "ignoring" cg="/" pid=1
I0510 14:40:54.878791  606823 registry.go:281] calculated container id 2 -> / ->
I0510 14:40:54.878805  606823 registry.go:286] "ignoring" cg="/" pid=2
I0510 14:40:54.878844  606823 registry.go:281] calculated container id 3 -> / ->
I0510 14:40:54.878856  606823 registry.go:286] "ignoring" cg="/" pid=3
I0510 14:40:54.878893  606823 registry.go:281] calculated container id 4 -> / ->
I0510 14:40:54.878901  606823 registry.go:286] "ignoring" cg="/" pid=4
I0510 14:40:54.878936  606823 registry.go:281] calculated container id 5 -> / ->
I0510 14:40:54.878947  606823 registry.go:286] "ignoring" cg="/" pid=5
I0510 14:40:54.878982  606823 registry.go:281] calculated container id 6 -> / ->
I0510 14:40:54.878994  606823 registry.go:286] "ignoring" cg="/" pid=6
I0510 14:40:54.879027  606823 registry.go:281] calculated container id 8 -> / ->
I0510 14:40:54.879038  606823 registry.go:286] "ignoring" cg="/" pid=8
I0510 14:40:54.879073  606823 registry.go:281] calculated container id 11 -> / ->
I0510 14:40:54.879081  606823 registry.go:286] "ignoring" cg="/" pid=11
I0510 14:40:54.879113  606823 registry.go:281] calculated container id 12 -> / ->
I0510 14:40:54.879121  606823 registry.go:286] "ignoring" cg="/" pid=12
I0510 14:40:54.879153  606823 registry.go:281] calculated container id 13 -> / ->
I0510 14:40:54.879166  606823 registry.go:286] "ignoring" cg="/" pid=13
I0510 14:40:54.879200  606823 registry.go:281] calculated container id 14 -> / ->
I0510 14:40:54.879211  606823 registry.go:286] "ignoring" cg="/" pid=14
I0510 14:40:54.879244  606823 registry.go:281] calculated container id 15 -> / ->
I0510 14:40:54.879251  606823 registry.go:286] "ignoring" cg="/" pid=15
I0510 14:40:54.879283  606823 registry.go:281] calculated container id 16 -> / ->
I0510 14:40:54.879291  606823 registry.go:286] "ignoring" cg="/" pid=16
I0510 14:40:54.879325  606823 registry.go:281] calculated container id 17 -> / ->
I0510 14:40:54.879332  606823 registry.go:286] "ignoring" cg="/" pid=17
I0510 14:40:54.879366  606823 registry.go:281] calculated container id 18 -> / ->
I0510 14:40:54.879377  606823 registry.go:286] "ignoring" cg="/" pid=18
I0510 14:40:54.879410  606823 registry.go:281] calculated container id 19 -> / ->
I0510 14:40:54.879419  606823 registry.go:286] "ignoring" cg="/" pid=19
I0510 14:40:54.879452  606823 registry.go:281] calculated container id 20 -> / ->
I0510 14:40:54.879466  606823 registry.go:286] "ignoring" cg="/" pid=20
I0510 14:40:54.879500  606823 registry.go:281] calculated container id 21 -> / ->
I0510 14:40:54.879511  606823 registry.go:286] "ignoring" cg="/" pid=21
I0510 14:40:54.879544  606823 registry.go:281] calculated container id 22 -> / ->
I0510 14:40:54.879556  606823 registry.go:286] "ignoring" cg="/" pid=22
I0510 14:40:54.879588  606823 registry.go:281] calculated container id 23 -> / ->
I0510 14:40:54.879600  606823 registry.go:286] "ignoring" cg="/" pid=23
I0510 14:40:54.879633  606823 registry.go:281] calculated container id 25 -> / ->
I0510 14:40:54.879640  606823 registry.go:286] "ignoring" cg="/" pid=25
I0510 14:40:54.879674  606823 registry.go:281] calculated container id 26 -> / ->
I0510 14:40:54.879685  606823 registry.go:286] "ignoring" cg="/" pid=26
I0510 14:40:54.879718  606823 registry.go:281] calculated container id 27 -> / ->
I0510 14:40:54.879729  606823 registry.go:286] "ignoring" cg="/" pid=27
I0510 14:40:54.879768  606823 registry.go:281] calculated container id 28 -> / ->
I0510 14:40:54.879781  606823 registry.go:286] "ignoring" cg="/" pid=28
I0510 14:40:54.879816  606823 registry.go:281] calculated container id 29 -> / ->
I0510 14:40:54.879823  606823 registry.go:286] "ignoring" cg="/" pid=29
I0510 14:40:54.879858  606823 registry.go:281] calculated container id 31 -> / ->
I0510 14:40:54.879865  606823 registry.go:286] "ignoring" cg="/" pid=31
I0510 14:40:54.879897  606823 registry.go:281] calculated container id 32 -> / ->
I0510 14:40:54.879904  606823 registry.go:286] "ignoring" cg="/" pid=32
I0510 14:40:54.879936  606823 registry.go:281] calculated container id 33 -> / ->
I0510 14:40:54.879949  606823 registry.go:286] "ignoring" cg="/" pid=33
I0510 14:40:54.879985  606823 registry.go:281] calculated container id 34 -> / ->
I0510 14:40:54.879992  606823 registry.go:286] "ignoring" cg="/" pid=34
I0510 14:40:54.880055  606823 registry.go:281] calculated container id 35 -> / ->
I0510 14:40:54.880063  606823 registry.go:286] "ignoring" cg="/" pid=35
I0510 14:40:54.880098  606823 registry.go:281] calculated container id 37 -> / ->
I0510 14:40:54.880107  606823 registry.go:286] "ignoring" cg="/" pid=37
I0510 14:40:54.880140  606823 registry.go:281] calculated container id 38 -> / ->
I0510 14:40:54.880154  606823 registry.go:286] "ignoring" cg="/" pid=38
I0510 14:40:54.880189  606823 registry.go:281] calculated container id 39 -> / ->
I0510 14:40:54.880202  606823 registry.go:286] "ignoring" cg="/" pid=39
W0510 14:40:54.880228  606823 init.go:35] open /proc/1/net/tcp6: no such file or directory
W0510 14:40:54.880228  606823 init.go:35] open /proc/1/net/tcp6: no such file or directory
I0510 14:40:54.880236  606823 registry.go:281] calculated container id 40 -> / ->
I0510 14:40:54.880290  606823 registry.go:286] "ignoring" cg="/" pid=40
I0510 14:40:54.880340  606823 registry.go:281] calculated container id 41 -> / ->
I0510 14:40:54.880353  606823 registry.go:286] "ignoring" cg="/" pid=41
I0510 14:40:54.880391  606823 registry.go:281] calculated container id 43 -> / ->
I0510 14:40:54.880399  606823 registry.go:286] "ignoring" cg="/" pid=43
I0510 14:40:54.880433  606823 registry.go:281] calculated container id 44 -> / ->
I0510 14:40:54.880439  606823 registry.go:286] "ignoring" cg="/" pid=44
I0510 14:40:54.880472  606823 registry.go:281] calculated container id 45 -> / ->
I0510 14:40:54.880480  606823 registry.go:286] "ignoring" cg="/" pid=45
I0510 14:40:54.880511  606823 registry.go:281] calculated container id 46 -> / ->
I0510 14:40:54.880518  606823 registry.go:286] "ignoring" cg="/" pid=46
I0510 14:40:54.880549  606823 registry.go:281] calculated container id 47 -> / ->
I0510 14:40:54.880556  606823 registry.go:286] "ignoring" cg="/" pid=47
I0510 14:40:54.880591  606823 registry.go:281] calculated container id 50 -> / ->
I0510 14:40:54.880598  606823 registry.go:286] "ignoring" cg="/" pid=50
I0510 14:40:54.880631  606823 registry.go:281] calculated container id 51 -> / ->
I0510 14:40:54.880638  606823 registry.go:286] "ignoring" cg="/" pid=51
I0510 14:40:54.880671  606823 registry.go:281] calculated container id 52 -> / ->
I0510 14:40:54.880678  606823 registry.go:286] "ignoring" cg="/" pid=52
I0510 14:40:54.880711  606823 registry.go:281] calculated container id 53 -> / ->
I0510 14:40:54.880718  606823 registry.go:286] "ignoring" cg="/" pid=53
I0510 14:40:54.880750  606823 registry.go:281] calculated container id 55 -> / ->
I0510 14:40:54.880757  606823 registry.go:286] "ignoring" cg="/" pid=55
I0510 14:40:54.880790  606823 registry.go:281] calculated container id 56 -> / ->
I0510 14:40:54.880797  606823 registry.go:286] "ignoring" cg="/" pid=56
I0510 14:40:54.880835  606823 registry.go:281] calculated container id 57 -> / ->
I0510 14:40:54.880843  606823 registry.go:286] "ignoring" cg="/" pid=57
I0510 14:40:54.880877  606823 registry.go:281] calculated container id 58 -> / ->
I0510 14:40:54.880884  606823 registry.go:286] "ignoring" cg="/" pid=58
I0510 14:40:54.880918  606823 registry.go:281] calculated container id 59 -> / ->
I0510 14:40:54.969239  606823 registry.go:213] TCP connection from unknown container {connection-open none 9196 <IP_ADDRESS>:33262 <IP_ADDRESS>:9093 34<PHONE_NUMBER>67560 }
W0510 14:40:55.888703  606823 registry.go:277] failed to get container metadata for pid 14343 -> /kubepods/besteffort/poda7143171-67b8-4c99-b7b5-3b850b41d2e5/65e74674bb94880aa9b1b8d913b1f37d6ac36613be45fb3e2ca13837db45c1fb: failed to interact with dockerd (%!s()) or with containerd (%!s())
W0510 14:40:55.888703  606823 registry.go:277] failed to get container metadata for pid 14343 -> /kubepods/besteffort/poda7143171-67b8-4c99-b7b5-3b850b41d2e5/65e74674bb94880aa9b1b8d913b1f37d6ac36613be45fb3e2ca13837db45c1fb: failed to interact with dockerd (%!s()) or with containerd (%!s())
I0510 14:40:55.888742  606823 registry.go:213] TCP connection from unknown container {connection-open none 14343 <IP_ADDRESS>:51738 <IP_ADDRESS>:443<PHONE_NUMBER>74116078 }
W0510 14:40:55.929900  606823 registry.go:277] failed to get container metadata for pid 20694 -> /kubepods/burstable/pod671ca5e2-5ce3-46a0-b10f-f5e4f8098e33/4bda181fc1ca52ebe65399cb8e11649c0e133cd6a85f959f0f6a3d370478f2cb: failed to interact with dockerd (%!s()) or with containerd (%!s())
W0510 14:40:55.929900  606823 registry.go:277] failed to get container metadata for pid 20694 -> /kubepods/burstable/pod671ca5e2-5ce3-46a0-b10f-f5e4f8098e33/4bda181fc1ca52ebe65399cb8e11649c0e133cd6a85f959f0f6a3d370478f2cb: failed to interact with dockerd (%!s()) or with containerd (%!s())
I0510 14:40:55.929929  606823 registry.go:213] TCP connection from unknown container {connection-open none 20694 <IP_ADDRESS>:44250 <IP_ADDRESS>:8080 14<PHONE_NUMBER>07215 }
W0510 14:40:55.946816  606823 registry.go:277] failed to get container metadata for pid 14343 -> /kubepods/besteffort/poda7143171-67b8-4c99-b7b5-3b850b41d2e5/65e74674bb94880aa9b1b8d913b1f37d6ac36613be45fb3e2ca13837db45c1fb: failed to interact with dockerd (%!s()) or with containerd (%!s())
W0510 14:40:55.946816  606823 registry.go:277] failed to get container metadata for pid 14343 -> /kubepods/besteffort/poda7143171-67b8-4c99-b7b5-3b850b41d2e5/65e74674bb94880aa9b1b8d913b1f37d6ac36613be45fb3e2ca13837db45c1fb: failed to interact with dockerd (%!s()) or with containerd (%!s())
I0510 14:40:55.946857  606823 registry.go:213] TCP connection from unknown container {connection-open none 14343 <IP_ADDRESS>:51752 <IP_ADDRESS>:443<PHONE_NUMBER>32268869 }
W0510 14:40:55.946943  606823 registry.go:277] failed to get container metadata for pid 14343 -> /kubepods/besteffort/poda7143171-67b8-4c99-b7b5-3b850b41d2e5/65e74674bb94880aa9b1b8d913b1f37d6ac36613be45fb3e2ca13837db45c1fb: failed to interact with dockerd (%!s()) or with containerd (%!s())

Could you please ssh to the node and check for containerd.sock:
# ls -l /run/containerd/containerd.sock
srw-rw---- 1 root root 0 Jan  4 09:04 /run/containerd/containerd.sock

@apetruhin  I can't access the cluster nodes sadly :(

The agent failed to locate containerd.sock.
Please exec into the node-agent pod and try to find the containerd.sock file:
kubectl -n coroot exec -ti coroot-node-agent-dwwrf -- bash

root@coroot-node-agent-dwwrf:/# ls -l /proc/1/root/run/containerd/containerd.sock

The root filesystem should be accessible from a node-agent pod under /proc/1/root/.

@apetruhin
root@node-agent-ntkdw:/# ls -l /proc/1/root/run/containerd/containerd.sock
lrwxrwxrwx 1 root root 44 May  3 10:14 /proc/1/root/run/containerd/containerd.sock -> /var/vcap/sys/run/containerd/containerd.sock

@yoyoraso, could you please verify whether /proc/1/root/var/vcap/sys/run/containerd/containerd.sock is not symlink to another location?
root@node-agent-ntkdw:/# ls -l /proc/1/root/var/vcap/sys/run/containerd/containerd.sock

Hi @apetruhin  root@node-agent-ntkdw:/# ls -l /proc/1/root/var/vcap/sys/run/containerd/containerd.sock
ls: cannot access '/proc/1/root/var/vcap/sys/run/containerd/containerd.sock': No such file or directory

@yoyoraso, please provide details about your setup and instructions on how to run this type of Kubernetes environment to reproduce the issue.

@apetruhin  it is a basic k8s cluster made using vm tanzu
kubernetes version : v1.25.16+vmware.1
Server Version: version.Info{Major:"1", Minor:"25", GitVersion:"v1.25.16+vmware.1", GitCommit:"84fd181a4243c4354b9208f4292f1b6cd82726b1", GitTreeState:"clean", BuildDate:"2023-11-21T10:59:59Z", GoVersion:"go1.20.10", Compiler:"gc", Platform:"linux/amd64"}
OS: Ubuntu 22.04.4 LTS
kernal : 6.5.0-21-generic
container runtime : containerd://1.6.28
coroot node agent tag : 1.18.9
let me know if you needed more information


NoClassDefFoundError

I am unable to use the lib, I get the following error
java.lang.NoClassDefFoundError: Failed resolution of: Lkotlin/jvm/internal/Intrinsics;
        at com.arasthel.spannedgridlayoutmanager.SpannedGridLayoutManager.<init>(SpannedGridLayoutManager.kt)
        at cm.diginov.isitravel.activities.Home.HomeActivity.onCreate(HomeActivity.java:43)

This is how I use it
SpannedGridLayoutManager spannedGridLayoutManager = new SpannedGridLayoutManager(SpannedGridLayoutManager.Orientation.VERTICAL, 3);
spannedGridLayoutManager.setItemOrderIsStable(true);
rv_trips.setLayoutManager(spannedGridLayoutManager);
rv_trips.setAdapter(tripsAdapter);

It looks like you have to add support for Kotlin in your Java project by adding this to your app's build.gradle:
implementation 'org.jetbrains.kotlin:kotlin-stdlib:1.2.71'

I'll think about adding a small section in the README about this.

It looks like you have to add support for Kotlin in your Java project by adding this to your app's build.gradle:
implementation 'org.jetbrains.kotlin:kotlin-stdlib:1.2.71'

I'll think about adding a small section in the README about this.

Thanks


Do not call grpc_init() for per-call-completion-queues created by a C++ sync server

Issue: #9261
Before this PR, every C++ CompletionQueue object creation ended up calling grpc_init  which acquires a mutex g_init_mu to increment the number of grpc-init invocations.
This is ok if the number of completion queues being created was small. However, in case of C++ Synchronous server, a completion queue is create for every call. This ends up making g_init_mu one of top created mutexes in sync servers.
This PR makes calling grpc_init optional when creating C++ CompletionQueue objects. It is always set to true by default but if a C++ CompletionQueue  is being created by passing a grpc_completion_queue * pointer i.e the following constructor (which is what Sync C++ server calls when creating a per-call completion queue), it is okay to NOT call grpc_init.
class CompletionQueue : private GrpcLibraryCodegen {
 ..
  explicit CompletionQueue(grpc_completion_queue* take);
..
}

This change is safe because if we got a grpc_completion_queue * structure, we MUST have already called grpc_init().
Benchmark results
I added a new benchmark BM_CreateDestroyCpp2 (didn't previously include it as a part of the PR because I thought it is trivial - but on a second thought, i think it is a good idea :))
Locks are down from 3 to 1
On master (with BM_CreateDestroyCpp2 temporarily ported):
sreek@sreek-dev:~/workspace/grpc (master) $ bins/counters/bm_cq --benchmark_filter=BM_CreateDestroyCpp2
Run on (12 X 3501 MHz CPU s)
2017-03-29 10:54:34
Benchmark                     Time           CPU Iterations
-----------------------------------------------------------
BM_CreateDestroyCpp2        215 ns        215 ns    3230778 locks/iter:3 atm_cas/iter:0 atm_add/iter:3 allocs/iter:1

On this PR branch:
sreek@sreek-dev:~/workspace/grpc (init-free-cq) $ bins/counters/bm_cq --benchmark_filter=BM_CreateDestroyCpp2
Run on (12 X 3501 MHz CPU s)
2017-03-29 10:56:15
Benchmark                     Time           CPU Iterations
-----------------------------------------------------------
BM_CreateDestroyCpp2        160 ns        160 ns    4413813 locks/iter:1 atm_cas/iter:0 atm_add/iter:3 allocs/iter:1

Beside the minor comment above, this seems LGTM-able. Can you put benchmark results about this into this PR description?

@vjpai, Did the changes you requested. PTAL

gRPC_interop_pull_requests failure is a known issue: https://github.com/grpc/grpc/issues/9011
(Bazel Full Build & Tests suite is not fully implemented yet and we are ignoring those failures)


TooManyBuckets: You have attempted to create more buckets than allowed

Note: If your issue/bug is regarding the AWS Amplify Console service, please log it in the
Amplify Console GitHub Issue Tracker

Describe the bug
Creating new environment throws error saying this:
CREATE_FAILED      S3Bucket AWS::S3::Bucket Wed Jun 03 2020 10:19:42 GMT+0800 (Philippine Standard Time) You have attempted to create more buckets than allowed (Service: Amazon S3; Status Code: 400; Error Code: TooManyBuckets; Request ID: -----; S3 Extended Request ID: -----
CREATE_IN_PROGRESS S3Bucket AWS::S3::Bucket Wed Jun 03 2020 10:19:41 GMT+0800 (Philippine Standard Time)

Amplify CLI Version
4.18.0
To Reproduce
Just create a new environment then do amplify publish.
Expected behavior
Should not happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: Mac
Node Version. v14.0.0

Additional context
I encountered this earlier when I created another environment, on the second try it worked, but on this one it has been 3rd try but still on shows error.

@aprilmintacpineda Can you check on the console how many buckets are in your account? There is a soft limit of 100 buckets

Oooh, I didn't know about the bucket limit. Yes, we have 100 buckets.

I ran around to check as many buckets as I could, looks like amplify leaves behind some buckets when you delete an environment. You can tell if the bucket is being used or not by looking at the contents and checking when the last update was, for me, some buckets were updated months ago.

I believe this has been fixed in an earlier version. Currently when removing an environment also removes its deployment bucket

I'm using version 4.18

@aprilmintacpineda could you please try this with version 4.21.1?

What is the expected output when using version 4.21?

With 4.21.1 if environments are removed in other projects the buckets should also be deleted allowing you to be below the hard limit of 100 buckets. If those projects were already deleted you will need to manually delete their buckets in the console or through aws-cli


Perf: slightly performance improvement

Perf: slightly performance improvement

Pull Request Test Coverage Report for Build 902964796

0 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 2.074%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/useVirtual.ts
0
1
0.0%

Totals

Change from base Build 901747812:
0.0%

Covered Lines:
7

Relevant Lines:
261

💛  - Coveralls


dict :Filename may store a FITS type

https://github.com/RvSpectML/EchelleInstruments.jl/blob/98d5a94f72a863b2cd97cb0b582265e3d4dca96b/src/harps-n/io.jl#L49
Is this OK if fn is a FITS type? The equivalent function read_metadata for EXPRES passes an additional argument filename (string) just for this field.

Same issue for harps:
https://github.com/RvSpectML/EchelleInstruments.jl/blob/98d5a94f72a863b2cd97cb0b582265e3d4dca96b/src/harps/io.jl#L41


Release 1.1.6 into main

What
Release 1.1.6 into main
Why
To flush the latest unreleased singletenant changes.
Checklist
PR Structure

[x] This PR has a reasonably narrow scope (if not, break it down into smaller PRs).
[x] This PR title and description are clear enough for anyone to review it.
[x] This PR does not mix refactoring changes with feature changes (split into two PRs otherwise).

Thoroughness

[x] This PR adds tests for the new functionality or fixes.
[x] This PR contains the link to the Jira ticket it addresses.

Configs and Secrets

[x] No new CONFIG variables are required -OR- the new required ones were added to the helmchart's values.yaml file.
[x] No new CONFIG variables are required -OR- the new required ones were added to the deployments (pr-preview, dev, demo, prd).
[x] No new SECRETS variables are required -OR- the new required ones were mentioned in the helmchart's values.yaml file.
[x] No new SECRETS variables are required -OR- the new required ones were added to the deployments (pr-preview secrets, dev secrets, demo secrets, prd secrets).

Release

[x] This is not a breaking change.
[x] This is ready for production.. If your PR is not ready for production, please consider opening additional complementary PRs using this one as the base. Only merge this into develop or main after it's ready for production!

Deployment

[ ] Does the deployment work after merging?

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr259.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr259.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr259.previews.kube001.services.stellar-ops.com

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr259.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr259.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr259.previews.kube001.services.stellar-ops.com

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr259.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr259.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr259.previews.kube001.services.stellar-ops.com

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr259.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr259.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr259.previews.kube001.services.stellar-ops.com


[Automation] Update stale.py

What does this PR do?
We shouldn't stale issues with the label "PRs welcome to address this"
cc @pacman100

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


@conda-forge-admin, please add user @drbixx

Additional comment:
No response

Closed in favor of #3


Time delay fickleness

I had to double the task delay to 8 seconds for the unbinding to succeed.
I didn't do much testing besides rebooting and changing the value, but 4 seconds didn't work and 8 did 😁
Thank you for this tool! 🚀🥦

You're so welcome, LoScienzo, thanks for showing appreciation! 🤜🏻🤛🏻
Thanks for taking the time to feed that back - I've updated the screenshots for the scheduled task to reflect your findings.
Whilst in there, I also finished and applied another update... The script now automatically finds your Config file, making it path agnostic (the bit I needed to do for non-default installs)
If you find anything else, or have any other feedback, please do let me know! 😇


relax requirements of minimum information model components

see https://github.com/cancervariants/fusion-curation/issues/261
relax requirements of minimum information model components
(do not require assay metadata, causative event, protein domains, reading frame)

bug fix in #131


Adds organization_name to search_fields.

This adds organization_name to the DonorAdmin search_fields.

ping @damonkelley  @somexpert  this is a very small change that adds another field to search_fields in DonorAdmin.

@vphill, think this can go to production today?

:+1:  :+1:


Add total bandwidth formatting options

This PR adds total bandwidth (bandwidthTotalBits, bandwidthTotalOctets and bandwidthTotalBytes) to the network module.
I have decided against adding a variable at the top of the update() method, mostly because it seems calculations are being done on demand if the format is actually requested, but this can be moved if I am interpreting it wrong.
I have also updated the man page, which was missing bytes up/down too.

Thx, can you also update the github wiki? :)

Sure, done.


Order of tests in administration test suite

Hi... I am checking out your mongodb module but struggle because if I run the mongotest.nim file I get an error on listDatabases because in an otherwise empty MongoDB server there is nothing to list and an error emerges from that. I reordered list and drop which makes more sense in my opinion. What do you think?

I think that's a badly written test. Tests must be independent, and order must not play any role here.

Fixed with slightly updated test suite


When i use machine learning, it will call twice, and the result repeat twice

version:

machine learning config:

action :

first interactive call

first interactive result

second interactive call

second interactive result

third call

third result

fourth call

fourth result

use default mmdetection examples

Hi @mengfu188
You used it right. It seems that duplicate results are connected with double calls of interactive annotation - our front end merges all results.
I have asked our front end team to check this issue.
Meanwhile, if you don't want to wait the fix you can add filter for duplicate results in ML backend.

Hello @KonstantinKorotaev
Another question is if i use bicycle tag to auto rectangle. The front end will turn all labels into bicycles. But the back end gives different labels. I use this example https://github.com/heartexlabs/label-studio-ml-backend/tree/master/label_studio_ml/examples/mmdetection

How to use machine learning? The result is a little strange. Did I use it wrong?

I have the exact same problem. The browser calls interactive-annotating twice and all the labels are added twice.
I am running the latest version:
  "release": "1.6.0",
  "label-studio-os-package": {
    "version": "1.6.0",
    "short_version": "1.6",
    "latest_version_from_pypi": "1.6.0",
    "latest_version_upload_time": "2022-09-27T17:09:34",
    "current_version_is_outdated": false
  },

  "label-studio-os-backend": {
    "message": "Bump rc5",
    "commit": "b0df5dd19a5400e8d26fb8269e2add87799af055",
    "date": "2022-09-27 16:32:57 +0100",
    "branch": "HEAD",
    "version": "1.6.0+0.gb0df5dd.dirty"
  },

  "label-studio-frontend": {
    "message": "fix: DEV-3510: fix video regions w/o label",
    "commit": "5d4231c2a8b9703f8c43abdf62948ac892d6f742",
    "branch": "master",
    "date": "2022/09/27 13:58:00"
  },

  "dm2": {
    "message": "feat: DEV-3373: Enable video preview (#106)  * Enable video preview  ...",
    "commit": "8374cbfeceb5aa9870278fc5371f0585d452c111",
    "branch": "master",
    "date": "2022-09-27T08:11:03Z"
  },

  "label-studio-converter": {
    "version": "0.0.44"
  },

  "label-studio-ml": {
    "version": "1.0.8.rc3"
  }
}

If anybody else has the same problem, as a workaround, I cache the last request and return empty predictions if the current one is equal to the last one. This technically creates race condition, if two users initiate a prediction, but my deployment is small enough to accept that risk.
    last_tasks = None

    def predict(self, tasks: List[dict], **kwargs):
        # https://github.com/heartexlabs/label-studio/issues/2546
        if tasks == self.last_tasks:
            logging.warning("Double request, returning 0 predictions.")
            return []
        self.last_tasks = tasks
        # actual prediction starts here


Custom CSS for Preview Mode

Is your feature request related to a problem? Please describe.
Our product currently uses the BeeFree plugin for email template editing. We also use a BeeFree plugin called "Video Studio". The Video Studio block is not reflexive even though it is when injected. So when a user goes into "preview mode", the mobile view does not look as expected. We are currently using the customCSS attribute for the Bee Config to adjust the look of the Video Studio block. This works within the template, but does not work in preview mode.
Describe the solution you'd like
We would like to be able to pass in custom CSS to the preview mode iframe so we can adjust the style for these cases. Custom CSS is available for the main tempalte. We would like an option for preview mode as well.
Describe alternatives you've considered
We created some work arounds currently. If the block is present when a user's template loads in then we can add CSS. This does not work when a new block is added. We also tried using the CustomCSS attribute on the Bee Config. This does not transfer over to preview mode as expected.
Additional context
None.

Curious if there are any future plans to add this since we are unable to effectively preview mobile emails using BeeFree without an enhancement.


Input bug in release version

Godot version: 3.0.stable.official and 3.0.stable template

OS/device including version: MS Windows 10 and Linux Ubuntu 16.04 Gnome

Issue description: Input bug in release version

Steps to reproduce:
I use last version Godot Engine. I don't know why my project of release version is not working.
I created simple project and I found breaking node. It's input node.
Editor: First screenshot

Release version: Second sceenshot

Release version is not working: print to screnn Null, instead true/false.
Minimal reproduction project: Link project
InputBugRelease.zip

Some advices

You should use the Action node instead CallSingleton
Paste screenshots to Github directly, without radikal, same for zip projects(I could not reproduce this bug myself, and download link is not working - freezed on "Файл загружается")

Try Action node instead CallSingleton, paste the project archive to Github directly instead of rgho.st

Sorry. I'm newbie. How do I add a project files and screenshots?

Simply combine it to zip or 7z archive and drag n drop it to comment field on Github.

You are right. Action node is working. But I use other call nodes. So my project still is not working. As a result, any call node is not working in release version?

I think this bug is occur because the node path ../../Label:text in NodeSet looks (for some reason) incorrect to engine in release version(did you mean exported binary ?)
The correct version looks like this..

I could miss, but thats my thoughts..

I fixed it. But it still does not work. I think call nodes does not work in release version.

I fixed it. But it still does not work

:laughing:

I've found the uninitialised variable causing this particular problem. (PR to follow)
However, there's rather heavy use of the preprocessor directives DEBUG_ENABLED, DEBUG_METHODS_ENABLED and TOOLS_ENABLED throughout the visual script stuff, that probably needs a once over from someone well acquainted with the system


Update related release notes to mention the public CVE and reporter

Relates to https://github.com/crate/crate/security/advisories/GHSA-475g-vj6c-xf96.

@mergifyio refresh

@mergifyio refresh

@Tu0Laj1 Thank you again for reporting the issue.


select box height

bootstrap4 select box height is not same as it is on bootstrap3 or as input box

Duplicate of #17194.


Allow Linux JDK locator to find locally installed locations

Allow Linux JDK Locator to find JDKs that are installed locally to the user.
Checks $HOME/.local/jdks as a search path.

Seems reasonable enough to me.
Thanks!


Ci 13616 upload artifacts to j frog

Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description
https://harness.atlassian.net/browse/CI-13616
Added stage variable examples to https://developer.harness.io/docs/continuous-integration/use-ci/build-and-upload-artifacts/upload-artifacts/upload-artifacts-to-jfrog/
and
https://developer.harness.io/docs/continuous-integration/continuous-integration-faqs/#can-i-run-the-upload-artifacts-to-jfrog-artifactory-step-with-a-non-root-user
PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged:

[ ] Successful preview build.
[ ] Code owner review.
[ ] No merge conflicts.
[ ] Release notes/new features docs: Feature/version released to at least one prod environment.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://66b667941c5cc25320094cae--harness-developer.netlify.app

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: lkilpatrick-harness:x: nofarblueYou have signed the CLA already but the status is still pending? Let us recheck it.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://66c3e6a7112bc572cf83f86d--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://66c405cd0516808f60d73502--harness-developer.netlify.app

Hi @lkilpatrick-harness pls address Nofar's comment(s) and the MC. thanks

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://66e3b09c4d733694feabd907--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://66e3cac0fc0ec6a8fc4feda7--harness-developer.netlify.app


redirect configuration not available anymore

Hello all
It seems, that the redirect configuration is not available anymore. In compliance.microsoft.com > Settings, there is no "compliance center redirection". Protection.microsoft.com is also not reachable anymore, so I guess the redirection can't be set anymore. I checked it with two tenants and with the appropriate rights to do so (global admin & compliance admin) and it's the same for both tenants. If this is globally the case, the docs should be updated, that this is not possible anymore, also not as a short-term solution as stated in this article. Can you confirm that this is the case?
Best,
Yannic

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

ID: 18f27732-40e2-dc52-177f-775afa16a753
Version Independent ID: 13cb2ee3-168b-2e80-7fe1-01b798ebd524
Content: Redirect users from the Office 365 Security and Compliance center to the Microsoft 365 compliance center - Microsoft 365 Compliance
Content Source: microsoft-365/compliance/microsoft-365-compliance-center-redirection.md
Service: o365-seccomp
GitHub Login: @robmazz
Microsoft Alias: robmazz

@grabery - thanks for the feedback, this has been updated in the topic.


Animating while using plain routes?

Hi everyone! Has anyone got an example of animating plain routes?
Here's some example code of what I mean:
import React from "react";
import ReactDOM from "react-dom";
import { hashHistory, Router, Route, Link } from "react-router";

// components
import Home from "./components/Home";
import About from "./components/About";

const App = ({children}) => (
  <div>{children}</div>
)

const routes = {
  path: "/",
  component: App,
  indexRoute: { component: Home },
  childRoutes: [{ path: "about", component: About }]
};

const root = document.getElementById("root");
ReactDOM.render(
  <Router history={hashHistory} routes={routes} />,
  document.body)

I'm not sure how you'd do it if you're not using JSX. Is this even possible?
Codesandbox

Haven't used plain routes before, but i think something like this would do: https://codesandbox.io/embed/p5w77z66jq

As always, so helpful. Thanks Paul! 🙏

Hey @drcmda, unfortunately I'm using an older version of react and router, so changing the versions I get the following error:
TypeError
React.forwardRef is not a function

I'm assuming this is something to do with the react-spring version. Any ideas?

I think react didn't have that feature previously. That would be tough to solve since i wouldn't know how to polyfill it.


Remove extraneous round,nimRound from processSpecificCalls

This fixes an old error where round is included in both RCfunction_core.R's nimKeywords and genCpp_processSpecificCalls.R's specificCallReplacements. This should result in no change to behavior, since the logic in processSpecificCalls should never have been triggered.
Tested:  Added two regression tests to ensure that no symbols appear in both places.

LGTM (I'm pretty sure my statement that they are redundant is correct, but wouldn't hurt to do a test of round and be sure.  Also FYI old Issue 197 is about different possible behaviors for round, mimicing either R or an IEC standard.

...test of round...
It looks like round is already tested in test-math.R and test-Math2.R. Did you have any other particular tests in mind that you'd like me to run?

Oh right.  Looks like they passed.  LGTM.
(test-Math2.R duplicates the second section of test-math.R, for Windows purposes).


ARRR LITE WALLET CONNECTION ISSUES  Possibly a BUG

Arrr Pirate.black Can't access my account Connection error/ Error: failed to fill whole buffer.
Charles Swank here; I can't access my ARRR Lite Wallet account. Problem is a connection error, Error: "failed to fill whole buffer." I have recovery seed. No matter what I try to do to recover ARRR account according to instructions, the error, the failure to FILL WHOLE BUFFER status is preventing me from getting full access to my ARRR ACCOUNT.
I was able to recover my ARRR ACCOUNT before and didn't have any problems as I do know.
Please advise
Charles Swank

I am having this same Issue.  Has there been a fix disclosed yet?

update to the newest version


Unable to install iris using dep

I am trying to install iris using dep using below command
dep ensure -add github.com/kataras/iris/v12@latest
but I am getting the below error can you please give me the solution
Warning: Gopkg.lock is out of sync with Gopkg.toml or the project's imports.
Fetching sources...

Failed to add the dependencies:

  ✗ latest is not a valid version for the package github.com/kataras/iris()

adding dependencies failed

when I am trying to use dep ensure I ma getting below error
Solving failure: No versions of github.com/kataras/iris met constraints:
        v12.1.8: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v12.1.7: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v12.1.6: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v12.1.5: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v12.1.4: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v12.1.3: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v12.1.2: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v12.1.1: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v12.1.0: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v12.0.1: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v12.0.0: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v11.2.8: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v11.2.7: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v11.2.6: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v11.2.5: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v11.2.4: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v11.2.3: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v11.2.2: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v11.2.1: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v11.2.0: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v11.1.1: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v11.1.0: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v11.0.4: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v11.0.3: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)   Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).) Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)
        v11.0.2: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        11.0.2: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v11.0.0: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v10.7.1: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)    Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)
        v10.7: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v10.6.7: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)   Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).) Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)
        v10.6.6: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)    Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)
        v10.6.5: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v10.6.4: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v10.6.3: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)   Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).) Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)
        v10.6.0: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v10.5.0: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)    Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)
        v10.4.0: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v10.3.0: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v10.2.1: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v10.1.0: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v10.0.0: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v8.5.9: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v8.5.7: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v8.5.4: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v8.5.2: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v8.5.0: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v8.4.5: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v8.4.4: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v8.4.3: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v8.4.2: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v8.4.0: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v8.3.4: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v8.2.1: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v6.2: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v5: Could not introduce github.com/kataras/iris@v5 due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v4: Could not introduce github.com/kataras/iris@v4 due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)   Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).) Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)
        v12: Could not introduce github.com/kataras/iris@v12 due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)    Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)
        4.0.0: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        5.0.0: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        master: Could not introduce github.com/kataras/iris@master due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)   Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).) Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)
        v10: Could not introduce github.com/kataras/iris@v10 due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)    Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)
        v11: Could not introduce github.com/kataras/iris@v11 due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v11-without-mod-test: Could not introduce github.com/kataras/iris@v11-without-mod-test due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v11.2.0: Could not introduce<EMAIL_ADDRESS>due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v6: Could not introduce github.com/kataras/iris@v6 due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        v8: Could not introduce github.com/kataras/iris@v8 due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)
        withtray-v7: Could not introduce github.com/kataras/iris@withtray-v7 due to multiple problematic subpackages:
        Subpackage github.com/kataras/iris/v12 is missing. (Package is required by (root).)     Subpackage github.com/kataras/iris/v12/middleware/logger is missing. (Package is required by (root).)  Subpackage github.com/kataras/iris/v12/middleware/recover is missing. (Package is required by (root).)

when I am trying to use dep ensure -v I am getting below error
Root project is "test"
 1 transitively valid internal packages
 3 external packages imported from 1 projects
(0)   ✓ select (root)
(1)     ? attempt github.com/kataras/iris with 3 pkgs; 67 versions to try
(1)         try<EMAIL_ADDRESS>(2)     ✗   github.com/kataras/iris at v12.1.8 has problem subpkg(s):
(2)             github.com/kataras/iris/v12/middleware/logger is missing; required by (root).   github.com/kataras/iris/v12/middleware/recover is missing; required by (root). github.com/kataras/iris/v12 is missing; required by (root).
(1)         try<EMAIL_ADDRESS>(2)     ✗   github.com/kataras/iris at v12.1.7 has problem subpkg(s):
(2)             github.com/kataras/iris/v12 is missing; required by (root).     github.com/kataras/iris/v12/middleware/logger is missing; required by (root).  github.com/kataras/iris/v12/middleware/recover is missing; required by (root).
(1)         try<EMAIL_ADDRESS>(2)     ✗   github.com/kataras/iris at v12.1.6 has problem subpkg(s):
(2)             github.com/kataras/iris/v12 is missing; required by (root).     github.com/kataras/iris/v12/middleware/logger is missing; required by (root).  github.com/kataras/iris/v12/middleware/recover is missing; required by (root).
(1)         try<EMAIL_ADDRESS>(2)     ✗   github.com/kataras/iris at v12.1.5 has problem subpkg(s):
(2)             github.com/kataras/iris/v12 is missing; required by (root).     github.com/kataras/iris/v12/middleware/logger is missing; required by (root).  github.com/kataras/iris/v12/middleware/recover is missing; required by (root).
(1)         try<EMAIL_ADDRESS>(2)     ✗   github.com/kataras/iris at v12.1.4 has problem subpkg(s):
(2)             github.com/kataras/iris/v12/middleware/logger is missing; required by (root).   github.com/kataras/iris/v12/middleware/recover is missing; required by (root). github.com/kataras/iris/v12 is missing; required by (root).
(1)         try<EMAIL_ADDRESS>(2)     ✗   github.com/kataras/iris at v12.1.3 has problem subpkg(s):
(2)             github.com/kataras/iris/v12 is missing; required by (root).     github.com/kataras/iris/v12/middleware/logger is missing; required by (root).  github.com/kataras/iris/v12/middleware/recover is missing; required by (root).
(1)         try<EMAIL_ADDRESS>(2)     ✗   github.com/kataras/iris at v12.1.2 has problem subpkg(s):
(2)             github.com/kataras/iris/v12 is missing; required by (root).     github.com/kataras/iris/v12/middleware/logger is missing; required by (root).  github.com/kataras/iris/v12/middleware/recover is missing; required by (root).
(1)         try<EMAIL_ADDRESS>(2)     ✗   github.com/kataras/iris at v12.1.1 has problem subpkg(s):
(2)             github.com/kataras/iris/v12 is missing; required by (root).     github.com/kataras/iris/v12/middleware/logger is missing; required by (root).  github.com/kataras/iris/v12/middleware/recover is missing; required by (root).
(1)         try<EMAIL_ADDRESS>(2)     ✗   github.com/kataras/iris at v12.1.0 has problem subpkg(s):
(2)             github.com/kataras/iris/v12 is missing; required by (root).     github.com/kataras/iris/v12/middleware/logger is missing; required by (root).  github.com/kataras/iris/v12/middleware/recover is missing; required by (root).
(1)         try<EMAIL_ADDRESS>(2)     ✗   github.com/kataras/iris at v12.0.1 has problem subpkg(s):
(2)             github.com/kataras/iris/v12 is missing; required by (root).     github.com/kataras/iris/v12/middleware/logger is missing; required by (root).  github.com/kataras/iris/v12/middleware/recover is missing; required by (root).
(1)         try<EMAIL_ADDRESS>(2)     ✗   github.com/kataras/iris at v12.0.0 has problem subpkg(s):
(2)             github.com/kataras/iris/v12 is missing; required by (root).     github.com/kataras/iris/v12/middleware/logger is missing; required by (root).  github.com/kataras/iris/v12/middleware/recover is missing; required by (root).
(1)         try<EMAIL_ADDRESS>

Hello @iamgkstack , i had same error but i didn't find solution, now i migrate to go mod and its works
https://github.com/golang/go/wiki/Modules#go-modules

In Go 1.14, module support is considered ready for production use, and all users are encouraged to migrate to modules from other dependency management systems.

Dep was officially deprecated earlier this year, and the proposal to archive this repository was accepted. As such, I'm closing outstanding issues before archiving the repository. For any further comments, please use the proposal thread on the Go issue tracker. Thanks!


C code Issue #687

Related Issue
Closes: #687
Describe the changes you've made
No time to wait for CodeChef with Time Complexity O(n)
Describe if there is any unusual behaviour of your code(Write NA if there isn't)
NA
Language used for coding
C
Checklist:

[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have documented the code.
[x] New and existing unit tests pass locally with my changes.

Here also folder name should be "No Time to Wait". Also add some comments to your code.


Number of model parameters

💡 Your Question
I try to print number of model parameters using torchsummary, but I have a some error.
How can I print the total number of parameters of my model?
Versions
super-gradients==3.1.2
No response

To help you with some error you may want to attach some output logs.

In order to let us help you with some error you may want to attach some output logs.

I use the following command: print(summary(model=model, input_size=(3, 320, 320), batch_size=16, device='cpu'))
Traceback (most recent call last):
File "/home/teo/programming/Internship/architectures_comparison/YOLO-NAS/yolo_nas.py", line 144, in
print(summary(model=model, input_size=(3, 320, 320), batch_size=16, device='cpu'))
File "/home/teo/programming/Internship/architectures_comparison/YOLO-NAS/venv/lib/python3.9/site-packages/torchsummary/torchsummary.py", line 72, in summary
model(*x)
File "/home/teo/programming/Internship/architectures_comparison/YOLO-NAS/venv/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
return forward_call(*args, **kwargs)
File "/home/teo/programming/Internship/architectures_comparison/YOLO-NAS/venv/lib/python3.9/site-packages/super_gradients/training/models/detection_models/customizable_detector.py", line 88, in forward
x = self.neck(x)
File "/home/teo/programming/Internship/architectures_comparison/YOLO-NAS/venv/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1538, in _call_impl
result = forward_call(*args, **kwargs)
File "/home/teo/programming/Internship/architectures_comparison/YOLO-NAS/venv/lib/python3.9/site-packages/super_gradients/training/models/detection_models/yolo_nas/panneck.py", line 59, in forward
x_n1_inter, x = self.neck1([c5, c4, c3])
File "/home/teo/programming/Internship/architectures_comparison/YOLO-NAS/venv/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1547, in _call_impl
hook_result = hook(self, args, result)
File "/home/teo/programming/Internship/architectures_comparison/YOLO-NAS/venv/lib/python3.9/site-packages/torchsummary/torchsummary.py", line 19, in hook
summary[m_key]["input_shape"] = list(input[0].size())
AttributeError: 'list' object has no attribute 'size'


HADOOP-19163. Use hadoop-shaded-protobuf_3_25

Description of PR
HADOOP-19163
How was this patch tested?
For code changes:

[x] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 50s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
xmllint
0m  0s

xmllint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+0 :ok:
mvndep
14m 33s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
36m 18s

trunk passed

+1 :green_heart:
compile
19m 45s

trunk passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
compile
18m 41s

trunk passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
mvnsite
3m 20s

trunk passed

+1 :green_heart:
javadoc
2m 47s

trunk passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javadoc
2m 17s

trunk passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
shadedclient
136m 53s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 37s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 49s

the patch passed

+1 :green_heart:
compile
18m 39s

the patch passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javac
18m 39s

the patch passed

+1 :green_heart:
compile
17m 39s

the patch passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
javac
17m 39s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
3m 19s

the patch passed

+1 :green_heart:
javadoc
2m 38s

the patch passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javadoc
2m 18s

the patch passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
shadedclient
49m 27s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
0m 35s

hadoop-project in the patch passed.

+1 :green_heart:
unit
20m 33s

hadoop-common in the patch passed.

+1 :green_heart:
unit
1m 10s

hadoop-yarn-api in the patch passed.

+1 :green_heart:
asflicense
1m  3s

The patch does not generate ASF License warnings.

255m 15s

Subsystem
Report/Notes

Docker
ClientAPI=1.45 ServerAPI=1.45 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6858/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/6858

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient codespell detsecrets xmllint

uname
Linux 338f706bfaa3 5.15.0-106-generic #116-Ubuntu SMP Wed Apr 17 09:17:56 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 464f328f9d8e605ff6a26bc37eef33faaf9484ac

Default Java
Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6858/1/testReport/

Max. process+thread count
1244 (vs. ulimit of 5500)

modules
C: hadoop-project hadoop-common-project/hadoop-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6858/1/console

versions
git=2.25.1 maven=3.6.3

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

@steveloughran @ayushtkn @slfan1989 Is it ok to get this PR merged? It appears to show that the hadoop-shaded-protobuf_3_25 jar works fine.

done. presumably we do this for 3.4.x too?

@steveloughran Would it make more sense to push for a hadoop-thirdparty 1.3.0 release? This would avoid keeping the dependencies on snapshot releases.

yes, let's get a release out.
I don't think I've done one of these..


Used dark papercurl when in dark theme.

Addresses issue #1017.
Made so it when in dark mode, papercurl uses dark mode's background color instead of white.
While not transparent, it provides the desired look.
Before the background was explicitly set to white. I followed this same pattern by doing this.
Is this workaround okay?
Thank you

Great job thanks!
@all-contributors please add @ZeroniaFX for code and bug


Is the RTP Server in config.js supposed to be Asterisk?

Thanks a lot for this repo! Can you please add a line of comments for what do various fields in config.js mean? Does the keyFilename param require absolute or relative filepath? I couldn't find it being used in the code.
Is there any reason why by default all three speech providers are enabled?

Closing the issue since I figured this out,
rtpServer is the node server, keyFilename should have the absolute path.
I noticed the PR that enabled all the speech providers to be used at once.

hey @vcidst sorry for the delay in replying... I'd completely missed your issue! Glad you managed to sort it out :)


Add constructors for PreflightParser with scratch parameter

This is a read only repository, please close your PR. I'll work on your JIRA issue.

Sorry 'bout that.


Output an array of objects

I am unsure of the syntax to have a rule output an array of objects. Arrays of primitives outputs correctly, but I'm not certain the syntax to get the example below to not fall through to the ERROR case. Thank you for the wonderful library!

Hi, array and object constructs are currently not available in the ZEN language. As an alternative you may use function block.
In future we might expose json_parse function in ZEN for such use-cases, but please note that it's not a priority atm.

Hi, this is supported now since #226.


[ISSUE #4223]Delete repeated calls in MQClientInstance#start

fix #4223
Delete repeated calls 'this.defaultMQProducer.getDefaultMQProducerImpl().start(false)' in MQClientInstance.start, It triggers a Heartbeat call and an extra timer.

DefaultMQPushConsumerImpl.java

It will be used to send retry messages if exception happens.
https://github.com/apache/rocketmq/blob/df3f8de4c03a282de052b130ae368ab00faca039/client/src/main/java/org/apache/rocketmq/client/impl/consumer/DefaultMQPushConsumerImpl.java#L512

It's not like we're talking about the same problem,  you can review my code.

DefaultMQPushConsumerImpl.java

It will be used to send retry messages if exception happens.
https://github.com/apache/rocketmq/blob/df3f8de4c03a282de052b130ae368ab00faca039/client/src/main/java/org/apache/rocketmq/client/impl/consumer/DefaultMQPushConsumerImpl.java#L512

It's not like we're talking about the same problem, you can review my code.

Yes, I have reviewed your code before. IMO，the consumer may not work normally if you remove it. Besides, It only brings an extra heartbeat and does not add a new scheduled task.


Adjusted operator-install test case.

Certsuite's PR
https://github.com/redhat-best-practices-for-k8s/certsuite/pull/2653 changed the way CSVs are autodiscovered in order for operator pods to be tested: the operator installation namespace must be explicitly added to the configured namespaces.
This change deploys the operatorgroup and subscription of the logging operator in the random test namespace that is set in the certsuite config file.

Checks passed. Merging it so we can merge certsuite's PR2653 with the main qe ref switched back to main.


Add support for chetv.ru

Hiya everyone!
Another site I am asking you, Authors, to be added to nicest all-oses program youtube-dl !
Here is the log:
C:\temp>youtube-dl.exe -v http://chetv.ru/kino/jeleznaya_hvatka/
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'-v', u'http://chetv.ru/kino/jeleznaya_hvatka/']
[debug] Encodings: locale cp1251, fs mbcs, out cp866, pref cp1251
[debug] youtube-dl version 2015.12.23
[debug] Python version 2.7.10 - Windows-7-6.1.7601-SP1
[debug] exe versions: ffmpeg N-77432-gc0f67e1, rtmpdump 2.4
[debug] Proxy map: {}
[generic] jeleznaya_hvatka: Requesting header
WARNING: Falling back on generic information extractor.
[generic] jeleznaya_hvatka: Downloading webpage
[generic] jeleznaya_hvatka: Extracting information
ERROR: Unsupported URL: http://chetv.ru/kino/jeleznaya_hvatka/
Traceback (most recent call last):
File "youtube_dl\extractor\generic.pyo", line 1287, in _real_extract
File "youtube_dl\compat.pyo", line 248, in compat_etree_fromstring
File "youtube_dl\compat.pyo", line 237, in _XML
File "xml\etree\ElementTree.pyo", line 1642, in feed
File "xml\etree\ElementTree.pyo", line 1506, in _raiseerror
ParseError: not well-formed (invalid token): line 48, column 116
Traceback (most recent call last):
File "youtube_dl\YoutubeDL.pyo", line 665, in extract_info
File "youtube_dl\extractor\common.pyo", line 291, in extract
File "youtube_dl\extractor\generic.pyo", line 1896, in _real_extract
UnsupportedError: Unsupported URL: http://chetv.ru/kino/jeleznaya_hvatka/
Thanks in advance!
-t
ps. btw, sometimes this chetv.ru is redirecting its player to videomore.ru.. I'll open another issue with this site.

Videomore based sites will be supported in the next version. However this video delivered via hds is DRM protected. Non DRM protected videos work fine (e.g. http://chetv.ru/show/dobroe_delo/).

Looks like they're NOT. The log:
C:\temp>youtube-dl -v --list-formats http://chetv.ru/show/dobroe_delo/
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'-v', u'--list-formats', u'http://chetv.ru/show/dob
roe_delo/']
[debug] Encodings: locale cp1251, fs mbcs, out cp866, pref cp1251
[debug] youtube-dl version 2015.12.29
[debug] Python version 2.7.10 - Windows-7-6.1.7601-SP1
[debug] exe versions: ffmpeg N-77432-gc0f67e1, rtmpdump 2.4
[debug] Proxy map: {}
[generic] dobroe_delo: Requesting header
WARNING: Falling back on generic information extractor.
[generic] dobroe_delo: Downloading webpage
[generic] dobroe_delo: Extracting information
ERROR: Unsupported URL: http://chetv.ru/show/dobroe_delo/
Traceback (most recent call last):
File "youtube_dl\extractor\generic.pyo", line 1287, in _real_extract
File "youtube_dl\compat.pyo", line 248, in compat_etree_fromstring
File "youtube_dl\compat.pyo", line 237, in _XML
File "xml\etree\ElementTree.pyo", line 1642, in feed
File "xml\etree\ElementTree.pyo", line 1506, in _raiseerror
ParseError: not well-formed (invalid token): line 49, column 116
Traceback (most recent call last):
File "youtube_dl\YoutubeDL.pyo", line 665, in extract_info
File "youtube_dl\extractor\common.pyo", line 291, in extract
File "youtube_dl\extractor\generic.pyo", line 1896, in _real_extract
UnsupportedError: Unsupported URL: http://chetv.ru/show/dobroe_delo/
Even if I try to get exact video - it won't work. The log:
C:\temp>youtube-dl -v --list-formats http://chetv.ru/show/dobroe_delo/1_sezon/1_vyipusk
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'-v', u'--list-formats', u'http://chetv.ru/show/dobroe_delo/1_sezon/1_vyipusk']
[debug] Encodings: locale cp1251, fs mbcs, out cp866, pref cp1251
[debug] youtube-dl version 2015.12.29
[debug] Python version 2.7.10 - Windows-7-6.1.7601-SP1
[debug] exe versions: ffmpeg N-77432-gc0f67e1, rtmpdump 2.4
[debug] Proxy map: {}
[generic] 1_vyipusk: Requesting header
[redirect] Following redirect to http://chetv.ru/show/dobroe_delo/1_sezon/1_vyipusk/
[generic] 1_vyipusk: Requesting header
WARNING: Falling back on generic information extractor.
[generic] 1_vyipusk: Downloading webpage
[generic] 1_vyipusk: Extracting information
ERROR: Unsupported URL: http://chetv.ru/show/dobroe_delo/1_sezon/1_vyipusk/
Traceback (most recent call last):
File "youtube_dl\extractor\generic.pyo", line 1287, in _real_extract
File "youtube_dl\compat.pyo", line 248, in compat_etree_fromstring
File "youtube_dl\compat.pyo", line 237, in _XML
File "xml\etree\ElementTree.pyo", line 1642, in feed
File "xml\etree\ElementTree.pyo", line 1506, in _raiseerror
ParseError: not well-formed (invalid token): line 49, column 116
Traceback (most recent call last):
File "youtube_dl\YoutubeDL.pyo", line 665, in extract_info
File "youtube_dl\extractor\common.pyo", line 291, in extract
File "youtube_dl\extractor\generic.pyo", line 1896, in _real_extract
UnsupportedError: Unsupported URL: http://chetv.ru/show/dobroe_delo/1_sezon/1_vyipusk/

I've already told you it's not yet released.

You've been talking about VIDEOMORE, not chetv, righto ?:) OK, be waiting for major version update and THEN re-check all the pages, then report back:)

Videomore based sites will be supported in the next version.
in the next version


Fix windows compile

Tested on mingw 32bit and 64bit and on Visual Studio 2013

Can you explain in the commit log why this fixes the build?  Bonus points if you include the actual build error.
PS: Please see CONTRIBUTING.md for the preferred format of the commit log.

Here is error log, actually this is warning, thing is we try to keep compile in our project warning free so treat all warnings are errors  (sorry was not aware of preferred format):
src/win/util.c: In function 'uv_os_homedir':
src/win/util.c:1189:46: warning: passing argument 3 of 'GetUserProfileDirectoryW' from incompatible pointer type
if (!GetUserProfileDirectoryW(token, path, &bufsize)) {
^
In file included from src/win/util.c:39:0:
C:/buildtools/vendor/mingw64/x86_64-w64-mingw32/include/userenv.h:52:29: note: expected 'LPDWORD' but argument is of type 'size_t *'
USERENVAPI WINBOOL WINAPI GetUserProfileDirectoryW(HANDLE hToken,LPWSTR lpProfileDir,LPDWORD lpcchSize);
^

Oh. LGTM

Landed in 7552305, thanks!


Display copied delegations in bonding section

The owner of the copied delegation needs to be able to add ETH to bond. Also, this implementation takes into account escrow redelegations(TokenGrant contract doesn't know about redelegations from escrow) and the fact that the grantee of a managed grant can be changed.

Tested that the owner of the copied delegation is now able to add ETH to bond.