secor loses partition ownership during rebalancing

In case we are adding new topic it triggers rebalance in consumer group.
partition assignment strategy: round robin
and once rebalancing is done, secor is not able to get ownership for all the partitions in that consumer group.
This behavior is intermittent and reproducing it is not easy.
Took a thread dump during the time when partition ownership was missing.
I shows that there is a possible deadlock.
Strangely when we stop all the instances in the consumer group and start it again it works.
Not sure why synchronization is creating issue in running service during rebalancing
thread dump lines:

0x0000000375332de0ObjectPossible deadlock
Held by secor-consumer-awz_s3_ip-172-31-43-12.ap-southeast-1.compute.internal_2491_189_watcher_executorawaiting notification on [ 0x0000000377f1e898 ] , holding [ 0x0000000375332de0 ]2 thread(s) waiting to take lock Thread-153 Thread-153

0x0000000377f1d368ReentrantLock$NonfairSyncPossible deadlock
Held by ConsumerFetcherThread-secor-consumer-awz_s3_ip-172-31-43-12.ap-southeast-1.compute.internal_2491_189-0-212awaiting notification on [ 0x0000000375345078 ] , holding [ 0x0000000377f1d368 ]1 thread(s) waiting for notifcation: secor-consumer-awz_s3_ip-172-31-43-12.ap-southeast-1.compute.internal_2491_189-leader-finder-thread

0x0000000377f1e378ReentrantLock$NonfairSyncPossible deadlock
Held by ConsumerFetcherThread-secor-consumer-awz_s3_ip-172-31-43-12.ap-southeast-1.compute.internal_2491_189-0-212awaiting notification on [ 0x0000000375345078 ] , holding [ 0x0000000377f1e378 ]1 thread(s) waiting for notifcation: secor-consumer-awz_s3_ip-172-31-43-12.ap-southeast-1.compute.internal_2491_189-leader-finder-thread

<<<

leader finder is waiting indefinitely for consumer fetcher.

The issue might be in the Kafka consumer rebalancing code, which Kafka version are you using?


[FEATURE REQUEST] Gist's viml script couldn't install

Problems summary
Why not implement installation of using gist?
I want to use this viml script. https://gist.github.com/tamanobi/3cb51380e10a9231c7aed15894ef5be0
Expected
call dein#add('tamanobi/3cb51380e10a9231c7aed15894ef5be0')
# https://gist.github.com/tamanobi/3cb51380e10a9231c7aed15894ef5be0

Environment Information

OS: Arch Linux
Vim version: NVIM 0.1.5

Provide a minimal .vimrc with less than 50 lines (Required!)
" Your minimal .vimrc
set runtimepath^=~/path/to/dein.nvim/
call dein#begin(path)

call dein#add('tamanobi/3cb51380e10a9231c7aed15894ef5be0')

call dein#end()

The reproduce ways from Vim starting (Required!)

Add installation code for dein.vim
Execute :call dein#install()
Occurred an error.

Screen shot (if possible)
Sorry.
Upload the log messages by :redir and :message
[dein] Update started: (2016/11/11 12:40:06)
[dein] /home/sachin21dev/.config/nvim/dein/repos/repos/github.com/tamanobi/3cb51380e10a9231c7aed15894ef5be0
[dein] Maybe wrong username or repository.
[dein] Cloning into '/home/sachin21dev/.config/nvim/dein/repos/repos/github.com/tamanobi/3cb51380e10a9231c7aed15894ef5be0'...
[dein] fatal: could not read Username for 'https://github.com': terminal prompts disabled
[dein] Error installing plugins:
[dein]   3cb51380e10a9231c7aed15894ef5be0
[dein] Please read the error message log with the :message command.
remote/host: python3 host registered plugins ['deoplete']
remote/host: generated rplugin manifest: /home/sachin21dev/.local/share/nvim/rplugin.vim
[dein] Runtimepath updated: (2016/11/11 12:40:09)
Press ENTER or type command to continue

call dein#add('https://gist.github.com/tamanobi/3cb51380e10a9231c7aed15894ef5be0', {'script_type': 'plugin'})

@Shougo Oh! Really!? Thank you so much.


feat: Reset to initial sort state for GridTable

GridTable sorting state now toggle between ASC -> DESC -> Initial Sort State. For client side sorting, the initial sort is defined either by the specified initial sort, or as the first sortable column.
For server side sorting we do not define an initially sorted column if it was not specified, (i.e. we do not look for a "first sortable column"). This gives the ability for server side sorting implementations to handle an undefined sort state. For use cases like Blueprint's Schedule V2, this allows the table to handle it's sorting reset via:
<GridTable sorting={{ on: "server", value: undefined, onSort: (sortState) => {
  if (sortState[0] === undefined) {
    // reset to original list
  } else {
    // sort tasks locally
  }
}} />

Granted, this now requires Blueprint's Schedule V2 table to do their sorting locally (as it is currently client-side sorted), but this seemed like kind of a one-off. I did not think it worth maintaining a list of the initial order (especially when it comes to nested structures) for a "reset" look up. Happy to revisit if we find it a more common pattern.

I think we have several existing tests that test sorting behavior; add a new one/update existing that shows the cycle back to initial?

@stephenh, Definitely. I should have put this out as a draft, though wanted to get eyes on it. This was more of a exploration to see if this was a good first approach and get some feedback. I'll update/add tests and address your comments. Thanks for looking it over.

For client side sorting, the initial sort is defined either by the specified initial sort, or as the first sortable column.

I think this makes sense, same with the "schedules v2 can use the cough server-side sorting cough" escape hatch. :-)
That said, we could probably allow:
sorting={{ on: "client", initial: undefined }}
To enable the "initial sort is 'not sorted'" behavior, while still using client-side sorting. I.e. use key presence to turn on/off the current "pick the 1st column if initial is unset" behavior.
I'm a little tempted to suggest doing that in this PR just for completeness, but also would be fine with a TODO somewhere noting that we could implement it this way when/if needed later.

sorting={{ on: "client", initial: undefined }}
To enable the "initial sort is 'not sorted'" behavior, while still using client-side sorting. I.e. use key presence to turn on/off the current "pick the 1st column if initial is unset" behavior.

@stephenh - Right now initial is an optional property, so undefined kind of already has a meaning. Though, it could have an explicit vs implicit meaning. What do you think about doing initial: null instead? 🤔 Then we should probably make sure on: server handles null vs undefined in the same fashion, which could be confusing with existing instances? Maybe just an explicit vs. implicit undefined...

some ideas on storing that initial order for resetting the client side sort

Ah yeah...we should probably just stop mutating the rows that the client passes in, which is kind of cheating / not kosher anyway.
I.e. when client-sorting is on, always make a copy of rows, and sort that, then on re-sort (or back to initial sort), just use the not-touched-by-us rows props as-is.
(We've been kinda lucky re mutating the rows prop, i.e. the apollo client technically gives us Object.freeze-n data that we shouldn't be allowed to sort anyway ... except that we always .map/copy it to add our kind flags, so are accidentally setting rows to an already-copied/mutable array.)


export TreeNodeWrapperComponent and TreeAnimateOpenDirective

Since these are referenced in the TreeModukle declarations, they
should be exported from the library. This will make the package more
IVY compatible.

Thanks!


[BUG]  LongHorn is not detecting any nodes after 16

Describe the bug (🐛 if you encounter this issue)
LongHorn is not detecting any nodes after 16th node.   I tryed  creating new nodes with differnt names  and even though kubernetes sees them Longhorn is not.   the nodes  longhorn added is working correctly.

Sorry  this is my first support request
new pods  destined for them nodes get the following:
31m         Warning   FailedAttachVolume    pod/engineering-databases-0         AttachVolume.Attach failed for volume "pvc-bac537b6-3ae4-4c2c-a858-abdbf52aeae2" : rpc error: code = Internal desc = Bad response statusCode [404]. Status [404 Not Found]. Body: [code=Not Found, detail=, message=unable to attach volume pvc-bac537b6-3ae4-4c2c-a858-abdbf52aeae2 to vadatam-07: node.longhorn.io "vadatam-07" not found] from [http://longhorn-backend:9500/v1/volumes/pvc-bac537b6-3ae4-4c2c-a858-abdbf52aeae2?action=attach]

To Reproduce

To my knoledge    seems to  happen after 16 nodes
Expected behavior
Should be able to accept new nodes

Support bundle for troubleshooting

Environment

Longhorn version: v1.6.0-dev
Installation method (e.g. Rancher Catalog App/Helm/Kubectl):Helm
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version: k8 v1.28.2

Number of management node in the cluster:1
Number of worker node in the cluster:16

Node config

OS type and version: debian 12
Kernel version:
CPU per node:
Memory per node: 15G
Disk type(e.g. SSD/NVMe/HDD): 200G SSD
Network bandwidth between the nodes: 1.5G

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal): rackspace VM
Number of Longhorn volumes in the cluster:110
Impacted Longhorn resources:2+

Volume names:engineering-databases-engineering-databases-0   Bound    pvc-bac537b6-3ae4-4c2c-a858-abdbf52aeae2   2Gi        RWO            longhorn       14h

Additional context

Name:             longhorn-manager-tpg74
Namespace:        longhorn-system
Priority:         0
Service Account:  longhorn-service-account
Node:             vadatam-07/<IP_ADDRESS>
Start Time:       Wed, 13 Dec 2023 13:40:57 -0500
Labels:           app=longhorn-manager
app.kubernetes.io/instance=longhorn
app.kubernetes.io/name=longhorn
app.kubernetes.io/version=v1.6.0-dev
controller-revision-hash=fcc8d9d75
pod-template-generation=9
Annotations:
Status:           Running
IP:               <IP_ADDRESS>
IPs:
IP:           <IP_ADDRESS>
Controlled By:  DaemonSet/longhorn-manager
Containers:
longhorn-manager:
Container ID:  containerd://308c48575a588208619019811e96ed67eaaa5cee851b700e9141c204c40a663a
Image:         longhornio/longhorn-manager:master-head
Image ID:      docker.io/longhornio/longhorn-manager@sha256:214e80028ffad97abbdf7d284b371a91b71a9ba08d2db84e015e832c2a511f5d
Ports:         9500/TCP, 9501/TCP, 9502/TCP, 9503/TCP
Host Ports:    0/TCP, 0/TCP, 0/TCP, 0/TCP
Command:
longhorn-manager
-d
daemon
--engine-image
longhornio/longhorn-engine:master-head
--instance-manager-image
longhornio/longhorn-instance-manager:master-head
--share-manager-image
longhornio/longhorn-share-manager:master-head
--backing-image-manager-image
longhornio/backing-image-manager:master-head
--support-bundle-manager-image
longhornio/support-bundle-kit:v0.0.27
--manager-image
longhornio/longhorn-manager:master-head
--service-account
longhorn-service-account
State:          Waiting
Reason:       CrashLoopBackOff
Last State:     Terminated
Reason:       Error
Exit Code:    1
Started:      Wed, 13 Dec 2023 13:47:24 -0500
Finished:     Wed, 13 Dec 2023 13:47:28 -0500
Ready:          False
Restart Count:  6
Readiness:      http-get https://:9501/v1/healthz delay=0s timeout=1s period=10s #success=1 #failure=3
Environment:
POD_NAMESPACE:  longhorn-system (v1:metadata.namespace)
POD_IP:          (v1:status.podIP)
NODE_NAME:       (v1:spec.nodeName)
Mounts:
/host/dev/ from dev (rw)
/host/proc/ from proc (rw)
/tls-files/ from longhorn-grpc-tls (rw)
/var/lib/longhorn/ from longhorn (rw)
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-rbrz2 (ro)
Conditions:
Type              Status
Initialized       True
Ready             False
ContainersReady   False
PodScheduled      True
Volumes:
dev:
Type:          HostPath (bare host directory volume)
Path:          /dev/
HostPathType:
proc:
Type:          HostPath (bare host directory volume)
Path:          /proc/
HostPathType:
longhorn:
Type:          HostPath (bare host directory volume)
Path:          /var/lib/longhorn/
HostPathType:
longhorn-grpc-tls:
Type:        Secret (a volume populated by a Secret)
SecretName:  longhorn-grpc-tls
Optional:    true
kube-api-access-rbrz2:
Type:                    Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds:  3607
ConfigMapName:           kube-root-ca.crt
ConfigMapOptional:
DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:
Tolerations:                 node.kubernetes.io/disk-pressure:NoSchedule op=Exists
node.kubernetes.io/memory-pressure:NoSchedule op=Exists
node.kubernetes.io/not-ready:NoExecute op=Exists
node.kubernetes.io/pid-pressure:NoSchedule op=Exists
node.kubernetes.io/unreachable:NoExecute op=Exists
node.kubernetes.io/unschedulable:NoSchedule op=Exists
Events:
Type     Reason                  Age                     From               Message

Normal   Scheduled               8m41s                   default-scheduler  Successfully assigned longhorn-system/longhorn-manager-tpg74 to vadatam-07
Warning  FailedCreatePodSandBox  8m41s                   kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "5bc5d2ed18065728f32a200ec4c426a32fdf85035c896d37b2533f12517ea5fa": plugin type="antrea" failed (add): rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial unix /var/run/antrea/cni.sock: connect: connection refused"
Normal   SandboxChanged          8m29s (x2 over 8m40s)   kubelet            Pod sandbox changed, it will be killed and re-created.
Warning  Unhealthy               8m2s (x2 over 8m24s)    kubelet            Readiness probe failed: Get "https://<IP_ADDRESS>:9501/v1/healthz": dial tcp <IP_ADDRESS>:9501: connect: connection refused
Normal   Pulled                  7m27s (x4 over 8m29s)   kubelet            Container image "longhornio/longhorn-manager:master-head" already present on machine
Normal   Created                 7m27s (x4 over 8m29s)   kubelet            Created container longhorn-manager
Normal   Started                 7m27s (x4 over 8m29s)   kubelet            Started container longhorn-manager
Warning  BackOff                 3m32s (x26 over 8m21s)  kubelet            Back-off restarting failed container longhorn-manager in pod longhorn-manager-tpg74_longhorn-system(9ecf4370-f394-4862-8495-6d36d327051

Additinal Details

A full support bundle will be most helpful if you can provide it, but we may be able to quickly get an idea of what's going on with kubectl logs -n longhorn-system longhorn-manager-tpg74.
Seems like the longhorn-manager pod is failing and there should be some log indicating why.

A full support bundle will be most helpful if you can provide it, but we may be able to quickly get an idea of what's going on with kubectl logs -n longhorn-system longhorn-manager-tpg74.

Seems like the longhorn-manager pod is failing and there should be some log indicating why.
Thanks,   here is the logs:

root@vadatam-07:~# kubectl logs -n longhorn-system longhorn-manager-v29v6
warning: GOCOVERDIR not set, no coverage data emitted
W1213 22:30:56.794837       1 client_config.go:618] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I1213 22:30:56.796734       1 shared_informer.go:311] Waiting for caches to sync for longhorn datastore
I1213 22:30:57.197129       1 shared_informer.go:318] Caches are synced for longhorn datastore
time="2023-12-13T22:30:57Z" level=info msg="Starting longhorn conversion webhook server" func=webhook.StartWebhook file="webhook.go:23"
time="2023-12-13T22:30:57Z" level=info msg="Waiting for conversion webhook to become ready" func=webhook.StartWebhook file="webhook.go:42"
time="2023-12-13T22:30:57Z" level=warning msg="Failed to get webhook health endpoint https://localhost:9501/v1/healthz" func=webhook.StartWebhook file="webhook.go:54" error="Get "https://localhost:9501/v1/healthz\": dial tcp [::1]:9501: connect: connection refused"
time="2023-12-13T22:30:57Z" level=info msg="Active TLS secret longhorn-system/longhorn-webhook-tls (ver=1540) (count 2): map[listener.cattle.io/cn-longhorn-admission-webhook.longhor-59584d:longhorn-admission-webhook.longhorn-system.svc listener.cattle.io/cn-longhorn-conversion-webhook.longho-6a0089:longhorn-conversion-webhook.longhorn-system.svc listener.cattle.io/fingerprint:SHA1=A2147F09762167293786550E6D72E5C399A7396A]" func="memory.(*memory).Update" file="memory.go:42"
time="2023-12-13T22:30:57Z" level=info msg="Listening on :9501" func=server.ListenAndServe.func2 file="server.go:77"
time="2023-12-13T22:30:57Z" level=info msg="Starting apiextensions.k8s.io/v1, Kind=CustomResourceDefinition controller" func="controller.(*controller).run" file="controller.go:144"
time="2023-12-13T22:30:57Z" level=info msg="Starting /v1, Kind=Secret controller" func="controller.(*controller).run" file="controller.go:144"
time="2023-12-13T22:30:57Z" level=info msg="Building conversion rules..."  func="server.(*WebhookServer).runConversionWebhookListenAndServe.func1" file="server.go:203"
time="2023-12-13T22:30:59Z" level=info msg="Active TLS secret longhorn-system/longhorn-webhook-tls (ver=1540) (count 2): map[listener.cattle.io/cn-longhorn-admission-webhook.longhor-59584d:longhorn-admission-webhook.longhorn-system.svc listener.cattle.io/cn-longhorn-conversion-webhook.longho-6a0089:longhorn-conversion-webhook.longhorn-system.svc listener.cattle.io/fingerprint:SHA1=A2147F09762167293786550E6D72E5C399A7396A]" func="memory.(*memory).Update" file="memory.go:42"
time="2023-12-13T22:30:59Z" level=info msg="Listening on :9502" func=server.ListenAndServe.func2 file="server.go:77"
time="2023-12-13T22:30:59Z" level=info msg="Webhook admission is ready" func=webhook.StartWebhook file="webhook.go:56"
time="2023-12-13T22:30:59Z" level=warning msg="Started longhorn admission webhook server" func=webhook.StartWebhook file="webhook.go:74"
time="2023-12-13T22:30:59Z" level=info msg="Starting longhorn recovery-backend server" func=recovery_backend.StartRecoveryBackend file="recovery_backend.go:13"
time="2023-12-13T22:30:59Z" level=info msg="Started longhorn recovery-backend server" func=recovery_backend.StartRecoveryBackend file="recovery_backend.go:22"
W1213 22:30:59.212448       1 client_config.go:618] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
time="2023-12-13T22:30:59Z" level=info msg="Recovery-backend server is running at :9503" func="server.(*RecoveryBackendServer).ListenAndServe" file="server.go:36"
time="2023-12-13T22:30:59Z" level=info msg="Updating TLS secret for longhorn-system/longhorn-webhook-tls (count: 2): map[listener.cattle.io/cn-longhorn-admission-webhook.longhor-59584d:longhorn-admission-webhook.longhorn-system.svc listener.cattle.io/cn-longhorn-conversion-webhook.longho-6a0089:longhorn-conversion-webhook.longhorn-system.svc listener.cattle.io/fingerprint:SHA1=A2147F09762167293786550E6D72E5C399A7396A]" func="kubernetes.(*storage).saveInK8s" file="controller.go:225"
time="2023-12-13T22:30:59Z" level=info msg="Checking if the upgrade path from v1.6.0-dev to v1.6.0-dev is supported" func=util.CheckUpgradePathSupported file="util.go:198"
time="2023-12-13T22:30:59Z" level=info msg="Waiting for old Longhorn manager pods to be fully removed" func=upgrade.waitForOldLonghornManagersToBeFullyRemoved file="upgrade.go:264"
time="2023-12-13T22:30:59Z" level=info msg="Building validation rules..."    Using the inClusterConfig.  This might not work.
time="2023-12-13T22:30:59Z" level=info msg="Starting Longhorn replica controller" func="controller.(*ReplicaController).Run" file="replica_controller.go:137" controller=longhorn-replica node=vaweb49
I1213 22:30:59.267584       1 shared_informer.go:311] Waiting for caches to sync for longhorn replicas
I1213 22:30:59.267710       1 shared_informer.go:318] Caches are synced for longhorn replicas
time="2023-12-13T22:30:59Z" level=info msg="Starting Longhorn engine controller" func="controller.(*EngineController).Run" file="engine_controller.go:179" controller=longhorn-engine node=vaweb49
I1213 22:30:59.268968       1 shared_informer.go:311] Waiting for caches to sync for longhorn engines
I1213 22:30:59.269073       1 shared_informer.go:318] Caches are synced for longhorn engines
time="2023-12-13T22:30:59Z" level=info msg="Start Longhorn VolumeAttachment controller" func="controller.(*VolumeAttachmentController).Run" file="volume_attachment_controller.go:210" controller=longhorn-volume-attachment node=vaweb49
I1213 22:30:59.271634       1 shared_informer.go:311] Waiting for caches to sync for longhorn-volume-attachment
I1213 22:30:59.271650       1 shared_informer.go:318] Caches are synced for longhorn-volume-attachment
time="2023-12-13T22:30:59Z" level=info msg="Starting Longhorn volume controller" func="controller.(*VolumeController).Run" file="volume_controller.go:186" controller=longhorn-volume node=vaweb49
I1213 22:30:59.273004       1 shared_informer.go:311] Waiting for caches to sync for longhorn engines
I1213 22:30:59.273064       1 shared_informer.go:318] Caches are synced for longhorn engines
time="2023-12-13T22:30:59Z" level=info msg="Starting Longhorn restore controller" func="controller.(*VolumeRestoreController).Run" file="volume_restore_controller.go:100" controller=longhorn-volume-restore node=vaweb49
I1213 22:30:59.276106       1 shared_informer.go:311] Waiting for caches to sync for longhorn-volume-restore
I1213 22:30:59.276354       1 shared_informer.go:318] Caches are synced for longhorn-volume-restore
time="2023-12-13T22:30:59Z" level=info msg="Start Longhorn rebuilding controller" func="controller.(*VolumeRebuildingController).Run" file="volume_rebuilding_controller.go:100" controller=longhorn-volume-rebuilding node=vaweb49
I1213 22:30:59.278673       1 shared_informer.go:311] Waiting for caches to sync for longhorn-volume-rebuilding
I1213 22:30:59.278777       1 shared_informer.go:318] Caches are synced for longhorn-volume-rebuilding
time="2023-12-13T22:30:59Z" level=info msg="Starting Longhorn eviction controller" func="controller.(*VolumeEvictionController).Run" file="volume_eviction_controller.go:102" controller=longhorn-volume-eviction node=vaweb49
I1213 22:30:59.280502       1 shared_informer.go:311] Waiting for caches to sync for longhorn-volume-eviction
I1213 22:30:59.280631       1 shared_informer.go:318] Caches are synced for longhorn-volume-eviction
time="2023-12-13T22:30:59Z" level=info msg="Starting Longhorn volume clone controller" func="controller.(*VolumeCloneController).Run" file="volume_clone_controller.go:123" controller=longhorn-volume-clone node=vaweb49
I1213 22:30:59.282415       1 shared_informer.go:311] Waiting for caches to sync for longhorn-volume-clone
I1213 22:30:59.282516       1 shared_informer.go:318] Caches are synced for longhorn-volume-clone
time="2023-12-13T22:30:59Z" level=info msg="Starting Longhorn node controller" func="controller.(*NodeController).Run" file="node_controller.go:285"
I1213 22:30:59.284539       1 shared_informer.go:311] Waiting for caches to sync for longhorn node
I1213 22:30:59.284650       1 shared_informer.go:318] Caches are synced for longhorn node
time="2023-12-13T22:30:59Z" level=warning msg="Number of node disks 1 and collected disk info 0 are not equal" func=controller.isDiskMatched file="node_controller.go:1425"
time="2023-12-13T22:30:59Z" level=info msg="mismatching disks in node resource object and monitor collected data" func="controller.(*NodeController).syncNode" file="node_controller.go:517"
time="2023-12-13T22:30:59Z" level=info msg="Starting Longhorn Engine Image controller" func="controller.(*EngineImageController).Run" file="engine_image_controller.go:122" controller=longhorn-engine-image node=vaweb49
I1213 22:30:59.287341       1 shared_informer.go:311] Waiting for caches to sync for longhorn engine images
I1213 22:30:59.287383       1 shared_informer.go:318] Caches are synced for longhorn engine images
time="2023-12-13T22:30:59Z" level=warning msg="Failed to create disk service client" func="monitor.(*NodeMonitor).collectDiskData" file="disk_monitor.go:164" error="failed to get disk service client: instance-manager-c20ae25f65f92a45508db593fe764bd0 instance manager is in error, not running state"
time="2023-12-13T22:30:59Z" level=info msg="Starting Longhorn websocket controller" func="controller.(*WebsocketController).Run" file="websocket_controller.go:96" controller=longhorn-websocket node=vaweb49
I1213 22:30:59.288028       1 shared_informer.go:311] Waiting for caches to sync for longhorn websocket
I1213 22:30:59.288154       1 shared_informer.go:318] Caches are synced for longhorn websocket
time="2023-12-13T22:30:59Z" level=info msg="Starting Longhorn Setting controller" func="controller.(*SettingController).Run" file="setting_controller.go:160" controller=longhorn-setting node=vaweb49
I1213 22:30:59.288411       1 shared_informer.go:311] Waiting for caches to sync for longhorn settings
I1213 22:30:59.288530       1 shared_informer.go:318] Caches are synced for longhorn settings
time="2023-12-13T22:30:59Z" level=info msg="Starting Longhorn instance manager controller" func="controller.(*InstanceManagerController).Run" file="instance_manager_controller.go:213"
I1213 22:30:59.329876       1 shared_informer.go:311] Waiting for caches to sync for longhorn instance manager
I1213 22:30:59.329917       1 shared_informer.go:318] Caches are synced for longhorn instance manager
time="2023-12-13T22:30:59Z" level=info msg="Instance manager state is updated from error to running after syncing with the pod" func="controller.(*InstanceManagerController).syncStatusWithPod.func1" file="instance_manager_controller.go:367" controller=longhorn-instance-manager instanceManager=instance-manager-c20ae25f65f92a45508db593fe764bd0 node=vaweb49 nodeID=vaweb49
time="2023-12-13T22:30:59Z" level=info msg="Starting Longhorn share manager controller" func="controller.(*ShareManagerController).Run" file="share_manager_controller.go:211" controller=longhorn-share-manager node=vaweb49
I1213 22:30:59.331286       1 shared_informer.go:311] Waiting for caches to sync for longhorn-share-manager-controller
I1213 22:30:59.331297       1 shared_informer.go:318] Caches are synced for longhorn-share-manager-controller
time="2023-12-13T22:30:59Z" level=info msg="Starting Longhorn Backing Image controller" func="controller.(*BackingImageController).Run" file="backing_image_controller.go:111"
I1213 22:30:59.331370       1 shared_informer.go:311] Waiting for caches to sync for longhorn backing images
I1213 22:30:59.331409       1 shared_informer.go:318] Caches are synced for longhorn backing images
time="2023-12-13T22:30:59Z" level=info msg="Starting Longhorn backing image manager controller" func="controller.(*BackingImageManagerController).Run" file="backing_image_manager_controller.go:169"
I1213 22:30:59.331496       1 shared_informer.go:311] Waiting for caches to sync for longhorn backing image manager
I1213 22:30:59.331518       1 shared_informer.go:318] Caches are synced for longhorn backing image manager
time="2023-12-13T22:30:59Z" level=info msg="Starting Longhorn backing image data source controller" func="controller.(*BackingImageDataSourceController).Run" file="backing_image_data_source_controller.go:155"
I1213 22:30:59.331600       1 shared_informer.go:311] Waiting for caches to sync for longhorn backing image data source
I1213 22:30:59.331609       1 shared_informer.go:318] Caches are synced for longhorn backing image data source
time="2023-12-13T22:30:59Z" level=info msg="Starting Longhorn Backup Target controller" func="controller.(*BackupTargetController).Run" file="backup_target_controller.go:138" controller=longhorn-backup-target node=vaweb49
I1213 22:30:59.331665       1 shared_informer.go:311] Waiting for caches to sync for longhorn-backup-target
I1213 22:30:59.331673       1 shared_informer.go:318] Caches are synced for longhorn-backup-target
time="2023-12-13T22:30:59Z" level=warning msg="Failed to clean up all mount points" func="controller.(*BackupTargetController).reconcile" file="backup_target_controller.go:282" controller=longhorn-backup-target cred= error="failed to get engine client proxy: instance-manager-c20ae25f65f92a45508db593fe764bd0 instance manager is in error, not running state" interval=5m0s node=vaweb49 url=
time="2023-12-13T22:30:59Z" level=info msg="Starting Longhorn Backup Volume controller" func="controller.(*BackupVolumeController).Run" file="backup_volume_controller.go:106" controller=longhorn-backup-volume node=vaweb49
I1213 22:30:59.332245       1 shared_informer.go:311] Waiting for caches to sync for longhorn-backup-volume
I1213 22:30:59.332290       1 shared_informer.go:318] Caches are synced for longhorn-backup-volume
time="2023-12-13T22:30:59Z" level=info msg="Starting Longhorn Backup controller" func="controller.(*BackupController).Run" file="backup_controller.go:129" controller=longhorn-backup node=vaweb49
I1213 22:30:59.332442       1 shared_informer.go:311] Waiting for caches to sync for longhorn-backup
I1213 22:30:59.332496       1 shared_informer.go:318] Caches are synced for longhorn-backup
time="2023-12-13T22:30:59Z" level=info msg="Starting Longhorn Recurring Job controller" func="controller.(*RecurringJobController).Run" file="recurring_job_controller.go:102"
I1213 22:30:59.332647       1 shared_informer.go:311] Waiting for caches to sync for longhorn recurring jobs
I1213 22:30:59.332694       1 shared_informer.go:318] Caches are synced for longhorn recurring jobs
time="2023-12-13T22:30:59Z" level=info msg="Starting Longhorn Orphan controller" func="controller.(*OrphanController).Run" file="orphan_controller.go:133" controller=longhorn-orphan node=vaweb49
I1213 22:30:59.332809       1 shared_informer.go:311] Waiting for caches to sync for longhorn-orphan
I1213 22:30:59.332820       1 shared_informer.go:318] Caches are synced for longhorn-orphan
time="2023-12-13T22:30:59Z" level=info msg="Starting Longhorn Snapshot Controller" func="controller.(*SnapshotController).Run" file="snapshot_controller.go:269" controller=longhorn-snapshot node=vaweb49
I1213 22:30:59.332877       1 shared_informer.go:311] Waiting for caches to sync for longhorn-snapshot
I1213 22:30:59.332888       1 shared_informer.go:318] Caches are synced for longhorn-snapshot
time="2023-12-13T22:30:59Z" level=info msg="Starting Longhorn Support Bundle controller" func="controller.(*SupportBundleController).Run" file="support_bundle_controller.go:151" controller=longhorn-support-bundle node=vaweb49
I1213 22:30:59.333918       1 shared_informer.go:311] Waiting for caches to sync for longhorn-support-bundle
I1213 22:30:59.333934       1 shared_informer.go:318] Caches are synced for longhorn-support-bundle
time="2023-12-13T22:30:59Z" level=info msg="Starting Longhorn SystemBackup controller" func="controller.(*SystemBackupController).Run" file="system_backup_controller.go:165" controller=longhorn-system-backup node=vaweb49
I1213 22:30:59.334004       1 shared_informer.go:311] Waiting for caches to sync for longhorn-system-backup
I1213 22:30:59.334013       1 shared_informer.go:318] Caches are synced for longhorn-system-backup
time="2023-12-13T22:30:59Z" level=info msg="Starting Longhorn SystemRestore controller" func="controller.(*SystemRestoreController).Run" file="system_restore_controller.go:127" controller=longhorn-system-restore node=vaweb49
I1213 22:30:59.334071       1 shared_informer.go:311] Waiting for caches to sync for longhorn-system-restore
I1213 22:30:59.334088       1 shared_informer.go:318] Caches are synced for longhorn-system-restore
time="2023-12-13T22:30:59Z" level=fatal msg="Error starting manager: admission webhook "validator.longhorn.io" denied the request: failed to set the setting detach-manually-attached-volumes-when-cordoned with invalid value false: value false of settings detach-manually-attached-volumes-when-cordoned is invalid: setting detach-manually-attached-volumes-when-cordoned is not supported" func=app.DaemonCmd.func1 file="daemon.go:84"

I ran the support bundle before  and it disapeared,   running it again.

Ah, this is unfortunate. It looks like you are running a development version of Longhorn, which just incorporated the detach-manually-attached-volumes-when-cordoned setting.
https://github.com/longhorn/longhorn-manager/pull/2324
Unless there is a problem with that PR we haven't detected yet (I think this is unlikely), my best guess is that some of your nodes are running a version of longhorn-manager that hasn't picked it up the PR yet and some are running a version of longhorn-manager that has. So whatever longhorn-manager is responding to the webhook request doesn't know about the setting, but the longhorn-manager that is starting does.
I would definitely not recommend running a dev version of Longhorn in anything that approaches production. To get out of the current bind, it's probably sufficient to ensure that the PullPolicy on the longhorn-manager DaemonSet is Always and then restart all longhorn-manager pods. I'm not sure how you installed Longhorn, so I'm not sure exactly how to recommend you set the PullPolicy.

Is it this setting?    if so i set it  and deleted the longhorn that was crashing an it did not change

also   i did not drain  until  this issue  started happening too...          i think longhorn just couldnt drain a node it was not aware of

support bundle is 3 G  ,   where do i upload it lol

Is it this setting? if so i set it and deleted the longhorn that was crashing an it did not change

No. The longhorn-manager DaemonSet is not affected by this setting. It is deployed directly by Helm or kubectl during the Longhorn install. You can directly edit the ImagePullPolicy for all containers in this DaemonSet, or you can modify the setting in the Helm values and/or longhorn.yaml and redeploy.
Again, I want to reiterate that it is very dangerous to run Longhorn at the tip of the current development branch. You are likely to encounter any number of problems that will not exist in a released version.

Is it this setting? if so i set it and deleted the longhorn that was crashing an it did not change

The longhorn-manager that is crashing is not the problem. It is a running longhorn-manager providing webhook functionality that is causing the problem. All longhorn-managers in the cluster must be restarted and they must pull the latest version of the longhorn-manager image (even though the tag is v1.6.0-dev either way).

Yes  it is really on our DEV network  not  so much production..   its just live on our dev  and with over 200 devs  i can not affford downtime  even there lol.  i remember i tryed to downgrade before and had issues too..  so i just kept it..    I also do not see a branch for 1.6.0  anymore..     not sure  where i got the .yaml file

However  i do see it saved on my desktop

my new  pod i get this error..        even though kubernetes sees vadatam-07    longhorn doesnt..      i did make the change u said    and restarted the failed manager   but no luck       gonna  try re adding the node to the cluster now

The .yaml file came from the master branch, which uses v1.6.0-head images by default (currently).

it seems   adding this test pod  works on my new node  ..     after  applying update too longhorn-manager  my gui is gone,,    so need to remake that an check...      my main db pods  still not working   but maybe seprate issue
kubectl -n databases  delete -f https://k8s.io/examples/application/nginx-with-request.yaml

kubectl -n databases apply-f https://k8s.io/examples/application/nginx-with-request.yaml
maybe it is not using pvc's as i do not see pvc's made for it

I agree. This pod will not be effective in testing Longhorn.
Is there still a failing longhorn-manager pod? If the longhorn-manager pod on the node is failing, the node will not be recognized by Longhorn. Once you can run kubectl get pod -n longhorn-system -l app=longhorn-manager and see longhorn-manager pods running on all nodes (including the new ones), you will likely be good to go.
If it is still failing, I suggest: kubectl delete -n longhorn-system -l app=longhorn-manager. This should restart all longhorn-manager pods with the latest version of the longhornio/longhorn-manager:master-head image.

Omg  im having a nightmare lol   ..   I called myself being safe  and creating a new cluster,    I had issues with getting longhorn working on it with the stable version..   Asked my co-worker to help me get it deleted  and he  did it on the wrong cluster lol..    so now    all databases are offline lol..     i have unstalled Longhorn     and i still see the pvc,  and pv's     I have tryed to reinstall Longhorn  both  5.3  and 6.0   and both   managers are failing  ..  Not sure if i need a new thread now  or if i can continue here..   but i need serious help ..  perferably   saving my exsisting data

I think the main question i need to ask.. can i uninstall 6.0 install 5.3 and still be able to use the same pvs?
i know there is no downgrade method.. but this doesnt mean i shouldnt be able to uninstall an reinstall a diff version does it?

Hi @cyford Yes, you can fully uninstall 1.6.0 then install 1.5.3. However, the PVC and PV will be deleted. If you have backup of the volume you can restore them, otherwise, you will need to recreate brand new PVC/PV


Karma cannot start PhantomJS on Windows Server 2012

Hi all,
I have a project that is working on all of the development workstations cross-platform, but not on my Jenkins server. If I remote in with the same account Jenkins uses and run grunt karma, I get a number of Cannot start PhantomJS errors, with no useful debug information aside from the exit code<PHONE_NUMBER> (see below, whereby I have the karma config set to DEBUG).
I have tracked down the phantomJS exe that is being used to the appropriate lib folder beneath karma-phantomjs-launcher in the project's node modules, and verified that it is running that exe.
Is there anything someone can suggest I try?
DEBUG [plugin]: Loading plugin D:\Jenkins\workspace\...\n
ode_modules/karma-jade-preprocessor.
DEBUG [plugin]: Loading plugin D:\Jenkins\workspace\...\n
ode_modules/karma-jasmine.
DEBUG [plugin]: Loading plugin D:\Jenkins\workspace\...\n
ode_modules/karma-ng-html2js-preprocessor.
DEBUG [plugin]: Loading plugin D:\Jenkins\workspace\...\n
ode_modules/karma-ng-jade2js-preprocessor.
DEBUG [plugin]: Loading plugin D:\Jenkins\workspace\...\n
ode_modules/karma-ng-scenario.
DEBUG [plugin]: Loading plugin D:\Jenkins\workspace\...\n
ode_modules/karma-phantomjs-launcher.
DEBUG [plugin]: Loading plugin D:\Jenkins\workspace\...\n
ode_modules/karma-requirejs.
DEBUG [plugin]: Loading plugin D:\Jenkins\workspace\...\n
ode_modules/karma-script-launcher.
WARN [karma]: Port 8080 in use
INFO [karma]: Karma v0.12.31 server started at http://localhost:8081/
INFO [launcher]: Starting browser PhantomJS
DEBUG [temp-dir]: Creating temp dir at C:\Users\Jenkins\AppData\Local\Temp\karma
-89315879
DEBUG [launcher]: D:\Jenkins\workspace\...\node_modules\k
arma-phantomjs-launcher\node_modules\phantomjs\lib\phantom\phantomjs.exe C:\User
s\Jenkins\AppData\Local\Temp\karma-89315879/capture.js
WARN [watcher]: Pattern "D:/Jenkins/workspace/.../client/
bower_components/angular-route/angular-route.js" does not match any file.
WARN [watcher]: Pattern "D:/Jenkins/workspace/.../client/
app/app.coffee" does not match any file.
WARN [watcher]: Pattern "D:/Jenkins/workspace/.../client/
components/**/*.js" does not match any file.
WARN [watcher]: Pattern "D:/Jenkins/workspace/.../client/
components/**/*.coffee" does not match any file.
WARN [watcher]: Pattern "D:/Jenkins/workspace/.../client/
components/**/*.jade" does not match any file.
WARN [watcher]: Pattern "D:/Jenkins/workspace/.../client/
components/**/*.html" does not match any file.
WARN [watcher]: Pattern "D:/Jenkins/workspace/.../client/
app/**/*.coffee" does not match any file.
WARN [watcher]: Pattern "D:/Jenkins/workspace/.../client/
app/**/*.jade" does not match any file.
DEBUG [preprocessor.html2js]: Processing "D:/Jenkins/workspace/...my files...
DEBUG [watcher]: Resolved files: ...my files...
DEBUG [launcher]: Process PhantomJS exited with code<PHONE_NUMBER>
ERROR [launcher]: Cannot start PhantomJS

DEBUG [temp-dir]: Cleaning temp dir C:\Users\Jenkins\AppData\Local\Temp\karma-89
315879
INFO [launcher]: Trying to start PhantomJS again (1/2).
DEBUG [launcher]: Restarting PhantomJS
DEBUG [temp-dir]: Creating temp dir at C:\Users\Jenkins\AppData\Local\Temp\karma
-89315879
DEBUG [launcher]: D:\Jenkins\workspace\...\node_modules\k
arma-phantomjs-launcher\node_modules\phantomjs\lib\phantom\phantomjs.exe C:\User
s\Jenkins\AppData\Local\Temp\karma-89315879/capture.js C:\Users\Jenkins\AppData\
Local\Temp\karma-89315879/capture.js
DEBUG [launcher]: Process PhantomJS exited with code<PHONE_NUMBER>
ERROR [launcher]: Cannot start PhantomJS

DEBUG [temp-dir]: Cleaning temp dir C:\Users\Jenkins\AppData\Local\Temp\karma-89
315879
INFO [launcher]: Trying to start PhantomJS again (2/2).
DEBUG [launcher]: Restarting PhantomJS
DEBUG [temp-dir]: Creating temp dir at C:\Users\Jenkins\AppData\Local\Temp\karma
-89315879
DEBUG [launcher]: D:\Jenkins\workspace\...\node_modules\k
arma-phantomjs-launcher\node_modules\phantomjs\lib\phantom\phantomjs.exe C:\User
s\Jenkins\AppData\Local\Temp\karma-89315879/capture.js C:\Users\Jenkins\AppData\
Local\Temp\karma-89315879/capture.js C:\Users\Jenkins\AppData\Local\Temp\karma-8
9315879/capture.js
DEBUG [launcher]: Process PhantomJS exited with code<PHONE_NUMBER>
ERROR [launcher]: Cannot start PhantomJS

DEBUG [temp-dir]: Cleaning temp dir C:\Users\Jenkins\AppData\Local\Temp\karma-89
315879
ERROR [launcher]: PhantomJS failed 2 times (cannot start). Giving up.
DEBUG [karma]: Run complete, exiting.
DEBUG [launcher]: Disconnecting all browsers
Warning: Task "karma:unit" failed. Use --force to continue.

Aborted due to warnings.

I'm having a similar problem.  Karma is running fine for me on Unix/Mac, but failing with a bunch of warnings like this on Windows:
[2015-03-27 13:24:16.160] [WARN] watcher - Pattern "e:/dev/cli/trunk/runtime/ui/bower_components/angular-mocks/angular-mocks.js" does not match any file.
That file exists, but for some reason Karma isn't finding it.
I'm guessing it is the backslashes in the path, but can't figure out why they are getting changed.

That happens because you haven't added the angular-mocks package to your karma.conf.js.

I think I have a similar issue to this on my build server. It works fine locally.

Looking into it, I am pretty sure this is nothing to do with karma-phantomjs-launcher, but is in fact a bad build of PhantomJS hosted on their binary server at Bitbucket. The later version (2.0) works on the system. If I have time, I'll fork this repo and try to update it, or if someone else can do it in the meantime, that would be very helpful. In the meantime, I'll try to use Chrome version in a non-UI session (you need a version from at least four months ago, as referenced in this thread).

Interesting - so if I update to phantomjs 2 it will work? The latest version on npm is still 1.9.16 so I guess I have to wait until it's released there or try and hack something together.

https://github.com/Medium/phantomjs/issues/288

@robdmoore: I can only say that version 2 runs and works from command line. I haven't configured it in karma-phantomjs-launcher yet. FWIW: my Jenkins server is working fine now using Chrome as a non-UI system process, which I'll stick to using for now.

Ref #56


Cosmetic - missing space between words in exception message

between ignoreRemoteDependencyManagement and are:
https://github.com/mojohaus/versions-maven-plugin/blob/0b900141cba0f84a7ee1a032daf7349fcc23fba4/src/main/java/org/codehaus/mojo/versions/CompareDependenciesMojo.java#L131-L132

As #418 couldn't get merged - closing this one due to inactivity.


Update dependencies for security fixes

Coverage decreased (-0.2%) to 97.816% when pulling 62d15a1520efa455ff7200816e0f8e083ba5df0c on security-updates into 60bb9ce68a014b80bef82f8321e27960cab88ec1 on master.


feat(atomic): popover menu basic structure

Current Successful Implementation -
Demo:
https://user-images.githubusercontent.com/97299176/182375029-6b332f53-40ea-4553-b42a-ce547078eff3.mov
Other non-successful solutions attempted:

Listen to the focusout event inside the popover component and altering the state of isMenuVisible to false when the mouse pointer isn't inside the slot-wrapper and the focousout event has been triggered.

The state variable isInsideSlotWrapper sometimes wasn't accurate as it would get reset when the popover component would rerender

Altering state of isMenuVisible to false when focusout event is caught inside the popover component while keeping the slot-wrapper visible when hovered over using css.

Inconsistent isMenuVisible state

Uses the atomic-focus-detector component implemented by Benjamin where the mouseDown event is prevented as it is responsible for removing focus

atomic-facet search bar rendered unclickable
Closes popover menu when clicking on value-button

Will merge with master after getting a couple reviews !


Tic Tac Toe-Game

Tic Tac Toe Game in Beginners Level

Why are there 37 files changed? There should only be 1 or 2.

Why are there 37 files changed? There should only be 1 or 2.

I didn't know how to upload only the md file I created, so I had to upload all the files in that beginners folder. It's my first PR, how can I do that in the right way?

Do you have Git?
If not, get it: https://git-scm.com/
Then fork the repo, click the download button, grab the git link and run git clone [your git link] in your terminal. It will create an app-ideas folder. Open that in your editor and make your changes.  Then just make the PR...


delete depracated perception pkg

Description
delete following pkgs

naive path prediction
dynamic object visualizer
roi_image_saver

Review Procedure

Remarks

Pre-Review Checklist for the PR Author
PR Author should check the checkboxes below when creating the PR.

[ ] Read pull request guidelines
[ ] Code follows coding guidelines
[ ] Assign PR to reviewer

Checklist for the PR Reviewer
Reviewers should check the checkboxes below before approval.

[ ] Commits are properly organized and messages are according to the guideline
[ ] Code follows coding guidelines
[ ] (Optional) Unit tests have been written for new behavior
[ ] PR title describes the changes

Post-Review Checklist for the PR Author
PR Author should check the checkboxes below before merging.

[ ] All open points are addressed and tracked via issues or tickets
[ ] Write release notes

CI Checks

Build and test for PR / build-and-test-pr: Required to pass before the merge.
Build and test for PR / clang-tidy-pr: NOT required to pass before the merge. It is up to the reviewer(s). Found false positives? See the guidelines.
Check spelling: NOT required to pass before the merge. It is up to the reviewer(s). See here if you want to add some words to the spell check dictionary.

object_flow_fusion and bev_optical_flow are also able to remove.

Okay


questions about java

I'm kinda dumb.
I admire your work, though! It's amazing. Anyway, this isn't much of an issue, it's rather an issue I have with myself specifically.
I don't know where to start exactly when it comes to learning Java for beginners and that's partially explained in the first line of this comment and the other part is that I look like even more of a beginner than I am because I only know very basic things e.g simplistic data structure parts and control flow  parent/child class, the public/private/protected thing,...but all in all the stuff is amateurish.
I was wondering if you could give me some pointers on where to start, cause I've seen you entertain me quite a lot. Tips in general are fine, as well.

Hello!
So, first off it's great that you want to get into programming! It's challenging but very rewarding.
Without knowing your exact skill level, I would say there is a progression that can make a lot of sense. Something like:

Start with some visual coding- the kind of thing you'll find on code.org. They may seem kind of childish, but it's a good way to get a footing on basic logic and control flow. If you feel like you're beyond this level, that's ok, it's maybe still fun to play around with.

Move on to some basic scripting language. This could be Javascript, or maybe even Skript. Javascript has some advantages in that it's easy to get going with, you can use platforms like jsfiddle.net to get instant feedback on your code.

Do some generalized learning about object orientation, if you end goal is to get into Java. I am honestly not sure of a good place to learn this, but maybe codeacademy (?). This is more about book learning, and less about practical application. You want to have the concepts down.

Then move on to Java. I would not start with something like a Bukkit plugin, but rather try making a simple program. There are probably some good tutorials out there, maybe the Sun ones... not sure.

Somewhere around step 3 you should definitely get a good IDE. I use IntelliJ, Eclipse works great too. For something like Java this is crucial to your learning process.
Now sadly I'm kind of bad at giving real examples, I learned Java a long time ago, partly in a school setting, so none of the ways I've learned really apply anymore, I never had to go fishing around on the Internet for tutorials or anything like that.
Once you've got a good handle on Java, writing a Bukkit plugin can be a very rewarding way to expand your skill set with it. It's a lot of fun to be able to see the effects of your code in-game, but it's also really important to understand the basics of object orientation and the structure of a Java class before trying to delve into the Bukkit API.
Some basic answers to some of your general questions:

In Java you must have an import at the top of every class file for each other class you want to use. These could be classes from the Bukkit API, or core Java classes, or some other class of your own. The more imports you see, the more classes are used in there.

An API stands for Application Programming Interface. Originally the meaning here was a an interface (a set of functions to call or classes to use) that is provided by an operating system to an application developer. This would be what someone writing a program or app would use to interact with the computer. Things like writing files, putting graphics on the screen.

More generally it now refers to an interface some piece of software exposes so other pieces of software can interact with it.
The most obvious example is the Bukkit API. This is an interface exposed by the Bukkit code that lets plugins interact with core Minecraft server code.
Some plugins (like Magic) also offer an API so that other plugins can interact with them.
For the most part it's just a way of defining a strict contract. Something that one program says should not change, so other programs can safely use it. Otherwise, if I were to just start calling functions inside the mcserver code, for instance, that may work now but is not guaranteed to work in the future. An API is (more or less) guaranteed to have the same behavior and to continue to provide the same functions from version to version.
Well I hope some of that helps... feel free to ask more questions, I'm not sure how much I can help but I will certainly try!


Support res.set/setHeader with a map of headers

https://expressjs.com/en/api.html#res.set
@Aminadav Let me know when you can get this in!! Thanks!!

@Aminadav Awesome, thanks for the speedy response. Let me know if it will be a bit before it gets published. Might internally publish my fork to get people by. A lot of devs use this as part of our preview tool. Great tool!

Perfect!
Sent from my iPhone

On Jul 14, 2018, at 13:28, Aminadav Glickshtein<EMAIL_ADDRESS>wrote:
Thank you. In a day or two. Thanks for the pull request.
On Fri, Jul 13, 2018, 9:53 PM Andy<EMAIL_ADDRESS>wrote:

@Aminadav https://github.com/Aminadav Awesome, thanks for the speedy
response. Let me know if it will be a bit before it gets published. Might
internally publish my fork to get people by. A lot of devs use this as part
of our preview tool. Great tool!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Aminadav/node-run-middleware/pull/22#issuecomment-404921975,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADaxPXy_u8V9CqwT8OrMxii-f3lw2vBFks5uGOyYgaJpZM4VOIXG
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Sorry to bother, I noticed a new version of run-middleware was released but
when I diff'd the changes it looks like they are the same. Just checking in
case you intended to release my changes with that release. Thanks again
man!!
On Sat, Jul 14, 2018 at 3:18 PM, Andy Gertjejansen <
<EMAIL_ADDRESS>wrote:

Perfect!
Sent from my iPhone
On Jul 14, 2018, at 13:28, Aminadav Glickshtein<EMAIL_ADDRESS>wrote:
Thank you. In a day or two. Thanks for the pull request.
On Fri, Jul 13, 2018, 9:53 PM Andy<EMAIL_ADDRESS>wrote:

@Aminadav https://github.com/Aminadav Awesome, thanks for the speedy
response. Let me know if it will be a bit before it gets published. Might
internally publish my fork to get people by. A lot of devs use this as
part
of our preview tool. Great tool!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/Aminadav/node-run-middleware/pull/22#
issuecomment-404921975>,
or mute the thread
<https://github.com/notifications/unsubscribe-
auth/ADaxPXy_u8V9CqwT8OrMxii-f3lw2vBFks5uGOyYgaJpZM4VOIXG>
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Aminadav/node-run-middleware/pull/22#issuecomment-405041410,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AOPhE7oUrepJe6tcbR0f03JpkELT5x6Oks5uGjhDgaJpZM4VOIXG
.

Wow, mistake. Now I published again. Please see the version now:
<EMAIL_ADDRESS>

It happens! Thanks so much!
Sent from my iPhone

On Jul 16, 2018, at 15:08, Aminadav Glickshtein<EMAIL_ADDRESS>wrote:
Wow, mistake. Now I published again. Please see the version now:
<EMAIL_ADDRESS>—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Fix golint in json_path.go

Following lint error should be fixed:
Line 23: should not use dot imports (golint)
Line 36: exported function Selection should have comment or be unexported (golint)
Line 65: exported type SelectionList should have comment or be unexported (golint)
Line 71:  exported method SelectionList.ValuesByName should have comment or be unexported (golint)
Line 80: exported method SelectionList.ValueByName should have comment or be unexported (golint)
Line 88:exported method SelectionList.ValuesByPath should have comment or be unexported (golint)
Line 97:  exported method SelectionList.ValueByPath should have comment or be unexported (golint)
Line 113:  exported function JSONPath should have comment or be unexported (golint)
Help Links :
Contributors guide

can i take this one @sonasingh46 ?

@rafa-acioly
That would be great. Go ahead.

done @sonasingh46 https://github.com/openebs/maya/pull/563


model_id & series_id is a media id

Pull request
Issue# fixed
Not clearly state that the value must be a media id (stock art file id).
Summary of Changes

Added an explicit message about the need to use a media id
Removed part of the sentence that leads to thinking they were ids different than the media id

What kind of change does this PR introduce?

[X] Enhancement (Clarifying documentation)

@Suisse00 This repository is no longer in use, but I made this change in the new repo:
https://github.com/AdobeDocs/stock-api-docs/pull/14
Thank you for your help!


Fixed early sell bug and Added auto-sell functionality

Due to way that conditional statements were structured, bug occurred where some stock would sell 0 shares at the beginning. Fixed this bug as well as added functionality to sell all owned stocks when the function is done running

Remove the unused code and comments

Done


Embed links queue - only log a warning instead of an exception if the worker times out

Discussion in https://chat.zulip.org/#narrow/stream/3-backend/topic/error.3A.20.22Timed.20out.20after.2030.20seconds.20processing.201.20events.22/near/1210121
Tested manually with manage.py process_queue in the dev environment

I decided a test was important for this, so I wrote a small test; while doing so I revised the formatting.  Thanks @mateuszmandera!

I'm not convinced about the direction of this, for a couple reasons:

This prints a warning, but doesn't terminate the work.  That means that I can prevent forward progress of the queue (for all realms on the server) with a single message with enough links in it.  You can currently do this with multiple messages (30s per message) but it's much more efficient when you can cram 10 links in and get 150s delay per message.  Making the worker async, and processing the links for messages in parallel, is of course the only real solution here -- but it feels like this pessimizes the current situation.
If we do terminate the work after 30s, and make it a warning, it means we're likely hiding real failures where we don't show unfurls.  I'm not clear why links are a special case of when those errors are more forgivable.

(1) Ah, that's definitely not intended - not raising an exception just causes consume() to get back to doing its thing after the signal handler runs, that was an oversight. Pushed #19148 to  try to address this
(2) Would it help to simply add the stack trace to the logging.warning call? I don't think we want to hide real failures - but it also is expected for this queue to time out sometimes because of issues with the URLs, so we also don't want to overreact to those situations, which are likely to be the vast majority of cases.


Added chief to the default device_filters for /job:ps

This behaviour matches the description in the _get_default_session_config_distributed docstring, and restores the symmetry of the default device_filters.

Nagging Assignee @caisq: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

@superbobry please fix:

FAIL: Found 2 non-whitelited pylint errors:
tensorflow/python/estimator/run_config_test.py:1200: [C0330(bad-continuation), ] Wrong hanging indentation (add 2 spaces).
tensorflow/python/estimator/run_config_test.py:1201: [C0330(bad-continuation), ] Wrong hanging indentation (add 2 spaces).


Feature allow full domain

Hello,
In my case, freshservice URL is under my company domain https://fresh.my.corp. Allow domain to be a full name instead of subdomain.

Note : PR not tested, I just test than the go code is valid
The goal is to use it with https://github.com/theapsgroup/steampipe-plugin-freshservice


MOB-5: Adding error notifications on login and sign-up

What's up?
We need to show some errors when user input is not matched with our login/signup criterias.
To Do

[x] Add a simple error notification on login
[x] Add a simple error notification on signup

Deadline
29.10.2022 @12.00
Additional Information
No response
Reviewers
@ooodogodogodogo

Added simple text message to notify user. Currently error text is static. It will be changed with response body to give correct output to the user. This part can be done after sending requests and receiving responses. As for now, that is enough.

As pull request is confirmed and merged, there are no reasons to keep this issue open.


[#903] plot_diagnostic_geometrical_coverage() operational

Main changes:

plot_diagnostic_geometrical_coverage() implemented

Issues:
Fixes, in devel, issue #903
Example:
dax = coll.plot_diagnostic_geometrical_coverage('OMP', plot_config=conf)

Hello @dvezinet! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file tofu/data/_class8_plot_coverage.py:

Line 159:32: E228 missing whitespace around modulo operator
Line 377:33: E261 at least two spaces before inline comment
Line 411:15: W292 no newline at end of file


Unable to follow symbol for "Omit"

Describe the bug
When trying to build a component library, an error occurs:
[vite:dts] Internal Error: Unable to follow symbol for "Omit"
If you disable rollupTypes, the build runs normally.
The problem is very similar #367
vite.config.js:
import react from "@vitejs/plugin-react-swc";
import { defineConfig } from "vite";
import dts from "vite-plugin-dts";
import svgr from "vite-plugin-svgr";
import mkcert from "vite-plugin-mkcert";

import { libInjectCss } from "vite-plugin-lib-inject-css";

import { resolve } from "path";

const resolvePath = (path: string) => resolve(__dirname, path);

import { peerDependencies } from "./package.json";

export default defineConfig(() => {
  return {
    plugins: [
      react(),
      svgr(),
      libInjectCss(),
      dts({ rollupTypes: true }),
      mkcert(),
    ],
    build: {
      target: "esnext",
      minify: true,
      cssCodeSplit: true,
      lib: {
        entry: resolvePath("lib/index.ts"),
        formats: ["es", "cjs"],
        fileName: "index",
      },
      rollupOptions: {
        external: ["react/jsx-runtime", ...Object.keys(peerDependencies)],
        input: {
          main: resolvePath("lib/index.ts"),
          toast: resolvePath("lib/assets/styles/toast.css"),
        },
      },
      emptyOutDir: true,
    },
  };
});

Reproduction
Not related
Steps to reproduce
No response
System Info
System:
    OS: Windows 11 10.0.22631
    CPU: (16) x64 AMD Ryzen 7 6800H with Radeon Graphics
    Memory: 3.82 GB / 15.19 GB
  Binaries:
    Node: 20.16.0
    npm: 10.8.2
  npmPackages:
    @vitejs/plugin-react-swc: ^3.7.0 => 3.7.0
    vite: ^5.4.0 => 5.4.0
    vite-plugin-dts: ^4.0.2 => 4.0.2

Validations

[X] Read the FAQ.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] The provided reproduction is a minimal reproducible example of the bug.

Fix by #366.


The Readme doc provide invalid links

Describe the bug
In the README.md, it provided an invalid link for "building the operator from source"
https://quarks.suse.dev/docs/core-tasks/building/
when access it, it report a 404 error.
also in the doc deploy/helm/cf-operator/README.md
the url https://quarks.suse.dev/docs/core-tasks/install/ it report a 404 error.
To Reproduce
try to access the links
https://quarks.suse.dev/docs/core-tasks/building/
https://quarks.suse.dev/docs/core-tasks/install/
Expected behavior
the provided links should be consistent with the latest doc files.

I've create the RP for this issue https://github.com/cloudfoundry-incubator/quarks-operator/pull/1148

PR merged, close this issue.


First stage of new tests which share logic with library tests

This is part1 of replacing the existing api tests and is a work in progress. The idea is for the library test and api test to use the same code for generating valid devfiles which will exist in the api repo. The code is not complete yet but the current set of tests run. The library tests depend on this PR before they can be merged.
Things to do include, but are not limited to:

Expand tests to fully cover the schema.
Expand test README with more detail on how the tests work and how to update them.
Come up with a way to configure which schema to use.

For more information see: https://github.com/devfile/api/issues/347

@maysunfaisal @yangcao77. Thanks for the comments would like to address term in my next PR if OK, nothing functional in the comments that would affect outcomes.
On a note the idea is that common code is common to both sides and is agnostic to which side is using it. To make this possible I added two interfaces in the common code for the api and library components to implement as necessary. Both need to implement the DevfileValidator and just the library needs to implement DevfileFollower.  How this is then implemented is pretty standard for go - given the interface is defined in a different package to the implementor. If this is not what you expected please shout now.
One impact of this is that  of this is that TestDevfile is now in common code but used in the api and library sides. In common code I can implement functions for it but I cannot in api and library so I had to modify some methods in api and library to take it as a parameter. If it was Java would have used "extends" but not sure that can be done in go. Would be interested if there is a better way. but for now I think this PR is good to go.

@maysunfaisal @yangcao77 have now added a commit for all the things I planned to do in the next PR.

I'm still feeling wired of this: https://github.com/devfile/api/pull/348#discussion_r579349706his
I understand this is trying to resolve the cycle import issue, but it is very confusing when reading the code. Need to figure out a better way to make it more clearer. But we can do it in the next PR.
My concerns have been resolved, just a minor typo as pointed out.
Waiting for Maysun's response as he also put some review comments

Have pushed more changes for the comments I missed.
For info on the interface structure I worked from this: https://github.com/golang/go/wiki/CodeReviewComments#interfaces


Set a max name for the IdlingResource

When tracing is enabled in the app, Espresso add IdlingResources to traces. This can cause IllegalArgumentException because createUnmanagedSpan calls IdlingResource.getName() and BusyBee returns a String that is not bounded:
override fun getName() = busyBee.getName()

This PR set a limit of 100 for the resource name. Trace has a limit of 127 characters. But I wanted to be on the safe side if there's a mechanism that adds prefix or suffix eventually.
The stacktrace that shows this error:
2022-10-28 12:48:39.111 19053-19108/com.example E/TestRunner: java.lang.IllegalArgumentException: sectionName is too long
        at android.os.Trace.beginSection(Trace.java:384)
        at androidx.tracing.TraceApi18Impl.beginSection(TraceApi18Impl.java:49)
        at androidx.tracing.Trace.beginSection(Trace.java:129)
        at androidx.test.platform.tracing.AndroidXTracer.beginSpan(AndroidXTracer.java:44)
        at androidx.test.platform.tracing.Tracing.createUnmanagedSpan(Tracing.java:171)
        at androidx.test.platform.tracing.Tracing.beginSpan(Tracing.java:113)
        at androidx.test.espresso.base.IdlingResourceRegistry$IdlingState.createUnmanagedTracerSpan(IdlingResourceRegistry.java:1)
        at androidx.test.espresso.base.IdlingResourceRegistry$IdlingState.setIdle(IdlingResourceRegistry.java:2)
        at androidx.test.espresso.base.IdlingResourceRegistry.allResourcesAreIdle(IdlingResourceRegistry.java:4)
        at androidx.test.espresso.base.IdlingResourceRegistry$6.isIdleNow(IdlingResourceRegistry.java:1)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for filing this.

Can you provide the versions of Espresso you are using?
Can you provide an instrumentation test that reproduces this issue?

Thanks!

Updating to the latest version of AndroidX core fix the crash. Thanks for pointing that out!


Pre-Check update

The scaling governor check is based on a driver. In my case, when I switched to using uefi this driver wasn't being used by default and thus this check was constantly failing. Might want to do more about this in the future (performance setting check). For now, just pass the check if the file doesn't exist.

@NickStephens, @Jacopo, this is more to your guys' expertise. It looks great to me, but I don't want to pull the trigger without the aid of your wisdom ;-)

OK, it matches afl's behavior.
Just a general note: we repeated afl's checks to catch problems in our setup ASAP. In other cases you may want to skip them and leave the job to afl.


Map: new map key not added if value is undefined

🐛 Bug Report
On Maps:
adding a new key with undefined value to a map does not create the new key.
To Reproduce
Here a simple test to show the problem
https://github.com/immerjs/immer/compare/master...visciang:master

Fixed in https://github.com/immerjs/immer/pull/630


publish wix-media.v2

https://github.com/wix-incubator/wix-code-docs/pull/1657
original autodocs branch - moved here for clean publish
fyi @imnotashrimp


Logging frequence has no effect on DL4J logging intervals

No matter what I set as logging frequence in "NeuralNetwork" (for example TrainingAmount.minibatches(1) or TrainingAmount.minibatches(300)), every iteration is logged. I have to admit, that I got new hardware, and compiled against latest dagli combined with dl4j-SNAPSHOT to get it running with cuda-11.2, so I am not sure, if this is reproducible.

That's very curious.  I'm assuming the number of examples per iteration size is at least twice the number of examples per minibatch?  Also, could you please share the line of code you're using to configure the logging frequency and the unexpected log lines you're seeing?  It might be that something related is being logged rather than what's specifically being configured.

These are the logged lines (2 iterations)
[pool-1-thread-27] INFO org.deeplearning4j.optimize.listeners.TimeIterationListener - Remaining time : 2mn - End expected : Tue Feb 09 21:55:39 CET 2021 [pool-1-thread-27] INFO org.deeplearning4j.optimize.listeners.PerformanceListener - ETL: 0 ms; iteration 360204; iteration time: 62 ms; samples/sec: 2064,516; batches/sec: 16,129;  GC: [G1 Young Generation: 0 (0ms)], [G1 Old Generation: 0 (0ms)]; [pool-1-thread-27] INFO org.deeplearning4j.optimize.listeners.TimeIterationListener - Remaining time : 2mn - End expected : Tue Feb 09 21:55:39 CET 2021 [pool-1-thread-27] INFO org.deeplearning4j.optimize.listeners.PerformanceListener - ETL: 0 ms; iteration 360205; iteration time: 61 ms; samples/sec: 2098,361; batches/sec: 16,393;  GC: [G1 Young Generation: 0 (0ms)], [G1 Old Generation: 0 (0ms)]; [pool-1-thread-27] INFO org.deeplearning4j.optimize.listeners.TimeIterationListener - Remaining time : 2mn - End expected : Tue Feb 09 21:55:39 CET 2021
Currently configured with:
.withTrainingProgressLoggingFrequency(TrainingAmount.minibatches(300))
.withTrainingPerformanceLoggingFrequency(TrainingAmount.minibatches(300))
.withMinibatchSize(3000)
In my understanding, there are 16 batches per second, so the log rows should appear around every 18 seconds, but multiple per second appear.

I checked the code and the conversion from "minibatches" to "iterations" is just an identity function, and the check against frequency is straightforward, so there's no obvious bug; I also ran a test and checked that the logging behaves as expected.  Is it possible that you might be configuring the neural network but not storing the result?  E.g. if you were to write code like this:
NeuralNetwork myModel = ...;
myModel.withTrainingProgressLoggingFrequency(TrainingAmount.minibatches(300));
The new variant of myModel with the modified logging frequency is just discarded (because it's not stored in myModel), and subsequent use of myModel would use the original version, without the every-300-minibatches logging.
Of course, if this were the case, I'd expect the result would be the default behavior of no logging, not logging every iteration.  If this isn't the case, is there any chance you could add a breakpoint inside org.deeplearning4j.optimize.listeners.PerformanceListener's constructor and report the value of the frequency parameter?  It should be 300.


The unused check loop method should be disabled by default for non-coroutine methods

Normal methods are likely to be used for non-asyncio tests.

This check is here to ensure that the test is actually a coroutine when it should:

an old-style coroutine missing the @asyncio.coroutine decorator will not run on the loop, the test will never fail (it only creates an instance of the generator),

when all assertions are running in async code, failure can be hidden, like in this example:
def test_start_my_app(self):
   @asyncio.coroutine
   def verify_things():
        self.assertTrue(False)
   # start_my_app can be buggy and never schedule verify_things, but the test will pass
   start_my_app(verify_things)

I assume that someone using asynctest will run asynchronous stuff in its test. If not, the @lenient decorator is here to disable all checks.

@Martiusweb I do not think it makes sense to complicate testing of old-style coroutines when 3.7 is about to be released and async / await syntax is pretty standard.
It's true it can be configured but if asynctest strives to be a drop in replacement non-async methods should work out of the box.

I agree with your last comment. We can deactivate the "unused loop" check by default.


May you add lobotomize and breeding delay features from PurpurMC, please?

Lobotomize completely kills villager's brain in 1x1 boxes.
Breeding delay adds possibility to increase breeding delay from 5 minutes.
I saw you messages about using Purpur, instead of adding this feature to plugin, but it seems that it would be easier to add
it's in one plugin than to download a separate server core with a billion patches to use only 2 features.
(translated with Google Translator)

How do you do this in purpur, I use purpur and would like to see this comment


Renaming ProtocolConnetion to ProtocolConnection

Reading through the code, I found a typo in one of the object names.  It's unclear to me how far outside of this project this might extend, however.  Please let me know if there is any more work around this.

@object88,
Thanks for your contribution.
To ensure that the project team has proper rights to use your work, please complete the Contribution License Agreement at https://cla.microsoft.com.
It will cover your contributions to all Microsoft-managed open source projects.
Thanks,
Microsoft Pull Request Bot

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: object88 sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

@object88, thanks for signing the contribution license agreement. We will now validate the agreement and then the pull request.
Thanks, Microsoft Pull Request Bot

Thanks. To make this non breaking and will add a type def for the old name.


Wrong docs ApiRequestFormat

I suspect too much copy-paste, not enough coffee ☕
https://github.com/aspnet/Mvc/blob/760c8f38678118734399c58c2dac981ea6e47046/src/Microsoft.AspNetCore.Mvc.ApiExplorer/ApiDescription.cs#L50

What is it supposed to be?
/// <summary>
/// Gets the list of possible formats for a request.
/// </summary>

Anything else that I should find out to add to the Remarks section?

I would add a similar blurb to the remarks. It will be empty if the action doesn't take a 'body' parameter.


CVE - Vulnerabilities <libflutter.so>

Our security team has scanned the flutter sdk we are using for our project and found that it contains cve security ， please check to see if there is a fix available.
cve_vulnerabilities.xlsx

The email address of your security team seems to be incorrect and I can't reach them.

@HLUO18-ford
What version of flutter sdk you scanned and found out the behavior ?


vscode-extensions: update 10

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Tested the Python extension.
Opened a couple scripts in vscodium. Tried linting, auto-formatting, and goto-definition.
Looks good.


[BUG] Using LOCAL_SIZE with CPU accelerator crashes on startup

Describe the bug
When using deepspeed with CPU Accelerator and LOCAL_SIZE, the application crashes with this error
'str' object cannot be interpreted as an integer

This is because in this snippet we are not converting LOCAL_SIZE to integer.
deepspeed/accelerator/cpu_accelerator.py
    def device_count(self):
        device_count = int(os.environ.get('LOCAL_SIZE', 0))
        if device_count > 0:
            return os.environ.get('LOCAL_SIZE')

To Reproduce
Steps to reproduce the behavior:

Launch deepspeed with any example using DS_ACCELERATOR=cpu accelerator and setting LOCAL_SIZE
See error

Expected behavior
Training should take place
System info (please complete the following information):

OS: Debian 11
GPU count and types [e.g. two machines with x8 A100s each] 0
Interconnects (if applicable) [e.g., two machines connected with 100 Gbps IB] 0
Python version 3.8
Any other relevant info about your setup

Launcher context
Are you launching your experiment with the deepspeed launcher, MPI, or something else? Deepspeed launcher
Docker context
Are you using a specific docker image that you can share? Custom
Additional context
Add any other context about the problem here.
Created PR to fix it https://github.com/microsoft/DeepSpeed/pull/3971

Closing becasue PR fixed it.


[docs] Enable flow on much more demos

[x] PR has tests / docs demo, and is linted.
[x] Commit and PR titles begin with [ComponentName], and are in imperative form: "[Component] Fix leaky abstraction".
[x] Description explains the issue / use-case resolved, and auto-closes the related issue(s) (http://tr.im/vFqem).

@rosskevin flow power 🚀


tiffsave_buffer

I can not seem to figure out the tiffsave_buffer method. If I simply use tiffsave it works as expected, but this is what I get with the buffer.
$tifOptions = [
        'compression' => 'jpeg',
        'tile' => true,
        'pyramid' => true
    ];
$image = Image::newFromFile($pageSource);
$tiffBlob = $image->tiffsave_buffer($tifOptions);

TIFFOpen: (null): Bad address tiff: unable to open "(null)" for input, exception="[object] (Jcupitt\Vips\Exception(code: 0): TIFFOpen: (null): Bad address tiff: unable to open "(null)" for input at /vendor/jcupitt/vips/src/Image.php:664)
[stacktrace]
#0 /vendor/jcupitt/vips/src/Image.php(685): Jcupitt\Vips\Image::errorVips()
#1 /vendor/jcupitt/vips/src/Image.php(1052): Jcupitt\Vips\Image::errorIsArray(-1)
#2 /vendor/jcupitt/vips/src/Image.php(1130): Jcupitt\Vips\Image::callBase('tiffsave_buffer', Object(Jcupitt\Vips\Image), Array)

Am I doing it wrong?

Hello, there's an example here:
https://github.com/jcupitt/php-vips/blob/master/tests/write.php#L47
That's for .jpg, but just use .tif instead and it should work.
tiffsave_buffer was added in 8.5, so make sure you have at least 8.5.0.

So, changing my code to
$tifOptions = [
        'compression' => 'jpeg',
        'tile' => true,
        'pyramid' => true
    ];
$image = Image::newFromFile($pageSource);
try {
    $tiffBlob = $image->writeToBuffer('.tif', $this->tifOptions);
} catch (\Exception $e) {
    dd($e);
}

gives me precisely the same error. I am running:

╰─ vips --version
vips-8.5.6-Sat Jul 22 10:12:12 BST 2017
╰─ php -i | grep vips
vips
vips property => value
VIPSHOME => /usr/local/Cellar/vips/8.5.6_2
$_SERVER['VIPSHOME'] => /usr/local/Cellar/vips/8.5.6_2

It appears to be the 'pyramid' => true flag. If I do not use that option, everything works as expected ... but as soon as I try for a pyramid tiff, it goes toes up.

Ooop, sorry, I hadn't noticed the pyramid flag there. You're right, tiffsave_buffer does not support pyramid images. I guess this is a bug, sorry. I'll see if there's an easy fix.

OK, added a bug on the main libvips tracker. Thanks for pointing this out.

Done and working, it'll be in 8.6.


If organization isn't passed as in input the workflow fails

We've been using this action for a while, but I just tried to convert one of our actions to a reusable action, and got this error:
Run<EMAIL_ADDRESS>  with:
    username: cmltaWt0
    GITHUB_TOKEN: ***
ReferenceError: context is not defined
    at run (/home/runner/work/_actions/tspascoal/get-user-teams-membership/v1.0.1/dist/index.js:1:105323)
    at Object.351 (/home/runner/work/_actions/tspascoal/get-user-teams-membership/v1.0.1/dist/index.js:1:105188)
    at __webpack_require__ (/home/runner/work/_actions/tspascoal/get-user-teams-membership/v1.0.1/dist/index.js:1:107309)
    at /home/runner/work/_actions/tspascoal/get-user-teams-membership/v1.0.1/dist/index.js:1:107474
    at Object.<anonymous> (/home/runner/work/_actions/tspascoal/get-user-teams-membership/v1.0.1/dist/index.js:1:107500)
    at Module._compile (internal/modules/cjs/loader.js:959:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:995:10)
    at Module.load (internal/modules/cjs/loader.js:815:32)
    at Function.Module._load (internal/modules/cjs/loader.js:727:14)
    at Function.Module.runMain (internal/modules/cjs/loader.js:1047:10)
Error: context is not defined

This could be my error somehow, but I've converted other workflows to be reusable, so I'm not sure what's different here.
Here is the failing action run:  https://github.com/openedx/devstack/runs/4857946347?check_suite_focus=true
Here's the pull request making the workflow reusable: https://github.com/openedx/.github/pull/6

@nedbat Sorry for the problem you are having.
I did a cursory look at your reusable workflow and can't find anything wrong with it, it should just work.
Specially since you are passing the organization, I will try to diagnose this on the weekend.

Hi @nedbat I have fixed the issue, my guess is that the secrets CC_TEAM_CONTRIBUTORS_ORG isn't defined. So if organization it is not passed as a parameter, it will use the organization of the caler workflow. If you intention is to use a secret is to reference  another organization it wouldn't work either, otherwise just skip the parameter or use ${{ github.repository_owner }} to reference the caller organization to spare a secret

I am running into what I think is a similar problem. I creaeted a personal (not org) Personal Access Token. The workflow works fine for an issue contributed by wholly external user but does not work for a pr...

success for issue here, https://github.com/betterscientificsoftware/bssw.io/actions/runs/4758360292/jobs/8456320369
failure for pr here, https://github.com/betterscientificsoftware/bssw.io/actions/runs/4767748401/jobs/8476351185

Again, I created the PAT in my own personal account, not the associated rep or org. Should I have done there?

@markcmiller86 The PR job is failing, because secrets are not available in pull requests (the hint is the error that GITHUB_TOKEN parameter is empty) created from a fork (see)
That is visible on the logs (notice Secret Source: None , it would show Actions otherwise like visible in the sucessful job )

The only way I am aware (I maybe be missing a simpler method) is to decouple the notification and be triggered on a workflow_run event when another WF completes (but then you might not have access to the PR/Issue)
As for using a PAT , you did good. (classic ) PATs always belong to a user not to an organization

FYI...it looks like simply switching the trigger from pull_request to pull_request_target fixed it for me.


more config

Is there any way to disable stay-centered just under certain circumstances, such as: in tagbar.

@416207298 not sure I understand the example, could you clarify what you mean by tagbar?
There's an option to disable it for certain filetypes, so if there's a filetype for what you're referring to--you can disable it that way.
Towards the bottom of the README

I'm going to close this issue as stale, if you have some clarifying info or would like to re-open--feel free to do so!

Sorry for this late reply. Tagbar is a plugin for nvim which is used for show functions and defines on the right/left side. And stay-centered is not quite good when cursor is in tagbar window. That's why I want to disable it.

@416207298 No worries, I believe you should be able to do this now as of this change that was merged last week: https://github.com/arnamak/stay-centered.nvim/pull/11


Login Google to a specific domain name only

how to login to a specific domain name (avoid login with other domains)

Google Api, set specific domain.
P.s: sorry my english


Add plugin-config package

The earlier monolithic sdeverywhere package had support for reading csv config files and generating a simple web app that runs the generated model.  When we added the new build and plugin packages, I removed that config file / web app generation code from the core cli/compiler packages because it's the kind of thing that works better as an optional plugin (which also helps avoid having too many non-optional dependencies in the core packages).
Now that the build and plugin packages have been added, this would be a good time to add back some of that config file support as part of an optional plugin-config package.  The user would no longer need to manually implement the modelSpec function in the sde.config.js file, and could instead use this new package to read the csv files from a config directory.  This would supply the necessary info to allow the rest of the build process to proceed, and would also generate some JS/JSON config files that could be used in the "core" and "app" packages that will be created by the new feature in #228.

As part of implementing this issue, I added an examples/sir project that uses the new plugin-config package.  For now, it includes boilerplate "app" and "core" package sources, but these will serve as the templates for the create package being implemented in #228.  Once that package is ready, I'll remove the boilerplate packages from the repo since they can be trivially reconstructed using npx create @sdeverywhere.
Here's what the sample app looks like (it's very minimal but serves as a good starting place for further customization):

Here's the small amount of code that needs to be added to an sde.config.js file to make use of the new plugin-config package:
import { configProcessor } from '@sdeverywhere/plugin-config'

export async function config() {
  return {
    // Specify the Vensim model to read
    modelFiles: ['model/sir.mdl'],

    // Read csv files from `config` directory and write to the `generated` directory
    modelSpec: configProcessor({
      config: configDir,
      out: genDir
    }),

    plugins: [
      // ...
    ]
  }
}


python3.7 测试的时候加载数据报错 TypeError: can't pickle dict_keys objects

Traceback (most recent call last):
  File "tools/test.py", line 246, in <module>
    main()
  File "tools/test.py", line 223, in main
    args.gpu_collect)
  File "/home/xxx/lib/python3.7/site-packages/mmdet/apis/test.py", line 100, in multi_gpu_test
    for i, data in enumerate(data_loader):
  File "/home/xxx/lib/python3.7/site-packages/torch/utils/data/dataloader.py", line 360, in __iter__
    return self._get_iterator()
  File "/home/xxx/lib/python3.7/site-packages/torch/utils/data/dataloader.py", line 306, in _get_iterator
    return _MultiProcessingDataLoaderIter(self)
  File "/home/xxx/lib/python3.7/site-packages/torch/utils/data/dataloader.py", line 919, in __init__
    w.start()
  File "/home/xxx/lib/python3.7/multiprocessing/process.py", line 112, in start
    self._popen = self._Popen(self)
  File "/home/xxx/lib/python3.7/multiprocessing/context.py", line 223, in _Popen
    return _default_context.get_context().Process._Popen(process_obj)
  File "/home/xxx/lib/python3.7/multiprocessing/context.py", line 284, in _Popen
    return Popen(process_obj)
  File "/home/xxx/lib/python3.7/multiprocessing/popen_spawn_posix.py", line 32, in __init__
    super().__init__(process_obj)
  File "/home/xxx/lib/python3.7/multiprocessing/popen_fork.py", line 20, in __init__
    self._launch(process_obj)
  File "/home/xxx/lib/python3.7/multiprocessing/popen_spawn_posix.py", line 47, in _launch
    reduction.dump(process_obj, fp)
  File "/home/xxx/lib/python3.7/multiprocessing/reduction.py", line 61, in dump
    ForkingPickler(file, protocol).dump(obj)
TypeError: can't pickle dict_keys objects
ERROR:torch.distributed.elastic.multiprocessing.api:failed (exitcode: 1) local_rank: 0 (pid: 82601) of binary: /home/xxx/bin/python
Traceback (most recent call last):
  File "/home/xxx/lib/python3.7/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/xxx/lib/python3.7/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/home/xxx/lib/python3.7/site-packages/torch/distributed/launch.py", line 193, in <module>
    main()
  File "/home/xxx/lib/python3.7/site-packages/torch/distributed/launch.py", line 189, in main
    launch(args)
  File "/home/xxx/lib/python3.7/site-packages/torch/distributed/launch.py", line 174, in launch
    run(args)
  File "/home/xxx/lib/python3.7/site-packages/torch/distributed/run.py", line 713, in run
    )(*cmd_args)
  File "/home/xxx/lib/python3.7/site-packages/torch/distributed/launcher/api.py", line 131, in __call__
    return launch_agent(self._config, self._entrypoint, list(args))
  File "/home/xxx/lib/python3.7/site-packages/torch/distributed/launcher/api.py", line 261, in launch_agent
    failures=result.failures,
torch.distributed.elastic.multiprocessing.errors.ChildFailedError:
============================================================
tools/test.py FAILED
------------------------------------------------------------
Failures:
  <NO_OTHER_FAILURES>
------------------------------------------------------------
Root Cause (first observed failure):
[0]:
  time      : 2022-02-24_14:57:48
  host      : k8s-deploy-xxx
  rank      : 0 (local_rank: 0)
  exitcode  : 1 (pid: 82601)
  error_file: <N/A>
  traceback : To enable traceback see: https://pytorch.org/docs/stable/elastic/errors.html
============================================================

Hi @Light-- ，
Could you follow the issue template to provide more details about the failure? For now, we are not able to help given limited information.


add GeoJSON support per message

Foreach message, provide a GeoJSON representation (as a Python dict) in the response.  This will allow users to use the messages as part of geospatial workflows.

Done.


Keeping selection after last paste

Keeping selection after last paste if pasted code replacing existing code, eg. function.
The feature is related with this:
https://github.com/microsoft/vscode-python/issues/23923

pasted selection can help easy tabulate or delete last paste part if not required.

There is case where in outline can be selected function after click, but paste then "re-formating" clipboard as all under def is without indention.

MS not have enough free community for this type requirements. : )
By this no sense to produce any feature request.

Great organization MS : )


Having trouble with multiple worlds.

So me and my friends have a server set up to play minecraft together and goof off. Our simple world is in survival, but we wanted to look into multiverse to have a creative world we can switch to at any given moment. However, I'm not particularly tech savvy and are having trouble with setting up the worlds the way I want them to be.
Here's the setting I want and don't know how to do.

Gamemode to automatically change between worlds.
No items to transfer between worlds
My friends to be able to switch between worlds without being admins.

What commands should I use? Thanks for the help!

You may want to ask on the discord https://discord.gg/NZtfKky This is really for reporting bugs/issues. I would also do a search on how to setup multiverse you will find some videos that will help explain how to set it up.

to change the enforce gamemode you can run /mvm set gamemode <gamemode> <worldname> if you want to bypass it entirely, you need to give mv.bypass.gamemode.GAMEMODE permission node using a permission plugin like luckperms.

Use Multiverse-Inventories. https://dev.bukkit.org/projects/multiverse-inventories https://github.com/Multiverse/Multiverse-Core/wiki/Basics-(Inventories)

you shouldn't give them teleport permissions. MV permissions nodes: https://github.com/Multiverse/Multiverse-Core/wiki/Big-List-O'-Permissions#teleport-permissions Tho, you may have other plugins that have teleport command.


Nucleovar Pre-Release Notes

<!--
# msk/nucleovar pull request

Many thanks for contributing to msk/nucleovar!

This new release includes the following changes/updates:

1. Each variant caller is organized in its own subworkflow
2. outputs of nucleovar pipeline and sample sheets are emit for downstream analysis
3. normalization/sorting is removed for complex variants VarDict VCF
4. README.md is added for any secondary files used to test pipeline end to end

<!--
# msk/nucleovar pull request

Many thanks for contributing to msk/nucleovar!

This new release includes the following changes/updates:

1. Each variant caller is organized in its own subworkflow
2. outputs of nucleovar pipeline and sample sheets are emit for downstream analysis
3. normalization/sorting is removed for complex variants VarDict VCF
4. README.md is added for any secondary files used to test pipeline end to end


Proposal to Modernize Testing Approach with @testing-library/user-event

Summery
I'd like to suggest migrating the current "overlay-kit"'s testing methods to use userEvent. Would you please consider it?
Benefit

By using userEvent, you will be able to write test code in a form that is more similar to the user's actual use cases.

The more your tests resemble the way your software is used, the more confidence they can give you.

All test cases currently used in "overlay-kit" can be migrated to userEvent without any problems.

My Opinion
If this proposal seems like a necessary but tedious task,
I am ready to work on it.
Could you please consider this suggestion?
Thank you always for your dedication.

I have always thought that the current overlay-kit tests needed improvement, as they are not perfectly written, but I haven’t had the time to address this.
As you mentioned, using user-event to write the tests would make them more similar to actual user scenarios. I think it’s a good direction and have no reason to oppose it.
If you have the time, could you proceed with the work? There’s no need to push yourself too hard.

Wow, now let's do the userEvent migration.
And this is a bit of a different topic, but I think it would be nice to have more test cases for "overlay-kit"
What do you think about this?

I think it would be nice to have more test cases for "overlay-kit"

Absolutely, I agree with adding more test cases for the “overlay-kit.”
Expanding the test coverage is an excellent idea. It enhances the robustness and reliability of the codebase and helps catch potential issues early. By simulating more user interactions and edge cases, we can create a more polished and user-friendly product.
Additionally, more test cases serve as valuable documentation for new developers joining the project. They can quickly understand the expected behavior of various components and functionalities by looking at the tests.
I fully support this initiative and am ready to work together to identify and implement additional test scenarios. Please feel free to share any specific ideas or areas you think need more testing. Thank you for your dedication and commitment to improving our project.

great! First, we will perform user event migration and then think about this issue.
thank you


Please also see https://github.com/dnnsoftware/Dnn.Platform/pull/829.


Please remove stun.sipgate.net from the list

Hey there,
we would like to get stun.sipgate.net permanently removed from the list.
Thanks,
Daniel

Hi @weuthen-sipgate,
Thanks for filing the issue.
I have removed your service from the automated checks.


Bump Quarkus and OpenTelemetry

@brunobat The OTel Jaeger exporter has been removed: https://github.com/open-telemetry/opentelemetry-java/pull/6119

I guess we will need to remove that exporter... Will send a deprecation for removal notice.
Another lovely breaking change.

@brunobat The Azure tests are now working, but not the GCP ones.

We need to bump the GCP version... Will look into it

@jeanbisutti Did the fix for the GCP

@brunobat I have fixed a problem related to the documentation.
There is now a problem with the Azure test in the native mode:
Caused by: java.net.MalformedURLException: Accessing a URL protocol that was not enabled. The URL protocol https is supported but not enabled by default. It must be enabled by adding the --enable-url-protocols=https option to the native-image command.
	at org.graalvm.nativeimage.builder/com.oracle.svm.core.jdk.JavaNetSubstitutions.unsupported(JavaNetSubstitutions.java:253)

It may be related to a Mandrel release 3 days ago: https://github.com/graalvm/mandrel/releases/tag/mandrel-<IP_ADDRESS>-Final
CI log:
[INFO] [io.quarkus.deployment.pkg.steps.NativeImageBuildStep] Running Quarkus native-image plugin on MANDREL <IP_ADDRESS> JDK 21.0.4+7-LTS
What would you recommend to fix this?

@jeanbisutti for some reason SSL was being set as disabled... I'm forcing it to be active and removed a redundant dependency causing problems with the build.