Cannot find 'blobs/sha256/...' in parsed layers using dive 0.12.0

What happened:
I'm still seeing this OCI layout error with dive that #500 was supposed to fix.
$ dive --source docker-archive image.tar
Image Source: docker-archive://image.tar
Fetching image... (this can take a while for large images)
cannot fetch image
could not find 'blobs/sha256/4f4fb700ef54461cfa02571ae0db9a0dc1e0cdb5577484a6d75e68dc38e8acc1' in parsed layers

What you expected to happen:
dive should be able to handle these OCI layout images in v0.12.0+
How to reproduce it (as minimally and precisely as possible):
Here is the source dockerfile, but I've attached a prebuilt image in case.
FROM alpine:3.11.6 as base-image
ARG TARGETARCH

RUN --mount=type=cache,id=apk-${TARGETARCH},sharing=locked,target=/var/cache/apk \
    ln -s /var/cache/apk /etc/apk/cache && \
    ls -lah /var/cache/apk && \
    apk --update add bash

RUN uname -a

download this pre-built image: image.tar.gz
unzip the downloaded image: gunzip image.tar.gz
run dive --source docker-archive image.tar
Optionally: extract the image to look at layers tar xf image.tar -C image
Optionally: load the image into docker and run dive on the loaded image (amd64 only) docker load < image.tar

dive tar.dive.example.com/image:latest

Anything else we need to know?:
Environment:

Dive version: 0.12.0
OS version: NixOS 23.11 (Tapir)
Docker version (if applicable):

Client:
 Cloud integration: v1.0.35+desktop.10
 Version:           25.0.3
 API version:       1.44
 Go version:        go1.21.6
 Git commit:        4debf41
 Built:             Tue Feb  6 21:13:00 2024
 OS/Arch:           linux/amd64
 Context:           default

Server: Docker Desktop
 Engine:
  Version:          25.0.3
  API version:      1.44 (minimum version 1.24)
  Go version:       go1.21.6
  Git commit:       f417435e5f6216828dec57958c490c4f8bae4f98
  Built:            Wed Feb  7 00:39:16 2024
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.6.28
  GitCommit:        ae07eda36dd25f8a1b98dfbf587313b99c0190bb
 runc:
  Version:          1.1.12
  GitCommit:        v1.1.12-0-g51d5e94
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

Ultimately, instead of guessing at layer encodings like https://github.com/wagoodman/dive/blob/925cdd86482edec42185794620a1e616b79bbee5/dive/image/docker/image_archive.go#L52 is doing, why not parse OCI images as they're meant to be?
If we added a quick pass over the archive files to first check if it contains an oci-layout file if it does, read index.json next and follow the manifests from there. Each digest points into the blobs subfolder, and each digest comes with a mediaType that tells us how to decode that blob (eg JSON, TAR, TAR+GZIP, etc).

If we added a quick pass over the archive files to first check if it contains an oci-layout file, if it does read index.json next and follow the manifests from there.

Unless you give it a TAR file, the TAR is directly streamed from the Docker daemon, so doing a 2-pass parsing would mean storing it in a temporary location (and risking filling up the disk/partition)

Thanks @tbroyer, good point. FWIW #511 does fix this issue for me - with those changes as a patch to my personal build of dive everything seems to be working normally now

I encountered a similar issue. I use docker containerd image storage and zstd OCI image. When I build image locally on macOS, dive reports:
Image Source: docker://test:debug
Fetching image... (this can take a while for large images)
cannot fetch image
could not find 'blobs/sha256/022ae4fed1b225b067d78e005f79c63bc1f5281747d428a534c5cf2c4d025028' in parsed layers

When pulling a docker image from the registry, dive reports:
dive ghcr.io/skvk/nexus
Image Source: docker://test
Fetching image... (this can take a while for large images)
cannot fetch image
could not find image config

docker info:
Client:
 Version:    25.0.3
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.12.1-desktop.4
    Path:     /Users/erickg/.docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.24.6-desktop.1
    Path:     /Users/erickg/.docker/cli-plugins/docker-compose
  debug: Get a shell into any image or container. (Docker Inc.)
    Version:  0.0.24
    Path:     /Users/erickg/.docker/cli-plugins/docker-debug
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.0
    Path:     /Users/erickg/.docker/cli-plugins/docker-dev
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.22
    Path:     /Users/erickg/.docker/cli-plugins/docker-extension
  feedback: Provide feedback, right in your terminal! (Docker Inc.)
    Version:  v1.0.4
    Path:     /Users/erickg/.docker/cli-plugins/docker-feedback
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.0.1
    Path:     /Users/erickg/.docker/cli-plugins/docker-init
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
    Version:  0.6.0
    Path:     /Users/erickg/.docker/cli-plugins/docker-sbom
  scout: Docker Scout (Docker Inc.)
    Version:  v1.5.0
    Path:     /Users/erickg/.docker/cli-plugins/docker-scout

Server:
 Containers: 33
  Running: 1
  Paused: 0
  Stopped: 32
 Images: 30
 Server Version: 25.0.3
 Storage Driver: overlayfs
  driver-type: io.containerd.snapshotter.v1
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: ae07eda36dd25f8a1b98dfbf587313b99c0190bb
 runc version: v1.1.12-0-g51d5e94
 init version: de40ad0
 Security Options:
  seccomp
   Profile: unconfined
  cgroupns
 Kernel Version: 6.6.16-linuxkit
 Operating System: Docker Desktop
 OSType: linux
 Architecture: aarch64
 CPUs: 10
 Total Memory: 10.69GiB
 Name: docker-desktop
 ID: 575b1def-c572-44cb-813c-4a614c4adf31
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 HTTP Proxy: http.docker.internal:3128
 HTTPS Proxy: http.docker.internal:3128
 No Proxy: hubproxy.docker.internal
 Experimental: false
 Insecure Registries:
  hubproxy.docker.internal:5555
  <IP_ADDRESS>/8
 Live Restore Enabled: false

Could we please merge #511; dive has been unusable on Apple AMD Macs for over half a year now …
Alternatively, you might want to mark your repository as osslifecycle=maintenance.
Yes, this is open source and free time and thanks for getting dive off the ground!

@sdavids I commented elsewhere, #511 doesn't seem to fix this on Docker 26+


Add support for Libpod configuration file

Add a configuration file (/etc/containerd/libpod.conf) that we can read to override our default configuration. This file is optional, and if not present we'll use our baked-in defaults as before.

I would prefer that we did not have to add a configuration file, because the goal of all these tools is to share content.  So I don't want to have a libpod.conf, buildah.conf, skopeo.conf and would love to get rid of most of crio.conf.  If we decide we really need a libpod.conf, it should be stored in /usr/lib/containers/libpod.conf and should have everything commented out so that it shares storage.conf, policy.conf ... with the other tools.
I don't see many users ever editing this file, so it brings little value, and is likely to cause us issues where crio, buildah, podman, and skopeo don't work together.

This does not override c/storage or c/image configuration. It exists solely for libpod-specific configuration (paths for runc, conmon, where to store the DB, etc).

Ok as long as we stick to those libpod specific paths and don't venture into conflicting with other config, I am fine with it.  But it should be installed in /usr/share/containers/libpod.conf with the overide in /etc/containers/libpod.conf

Default location changed to /usr/share/containers with override path of /etc/containers allowed.

Should be ready now

@rh-atomic-bot r+


Suggestion: Template Helper Add User Parameter

isInRole is great template helper but I found myself in need of also checking specific users to display badges of "Admin", "Editor" so I also publish the roles of those users of specific group and it have my own template helper. This is only a small change in the function :)

Thanks for the suggestion.  I'm not quite following...could you give a little example of how the changed template helper would be used in a template?


Add pin layout field to HardwareDescription and change layout accordingly

RPi pins alternate 1 on left, 2 on right and so on, so 40 is bottom left
Pico physical pins could 1-20 down left side, then 21-40 UP right side, with 40 top right
Thus, for the board layout to be correct, we need to do it differently for RPi and Pico.
We should send the layout as a field in HardwareDescription and then change the layout view to do one way or the other.

I have added this field: PinLayoutScheme in the HardwareDescription for pi_hw, fake_hw and porky in my pico-piglet branch.
@sundaram123krishnan would you like to work on the hardware layout view in this branch, changing how pins are laid out according to that field?

Pi layout, using the Rows scheme

Will do @andrewdavidmackenzie

This would be required prior to announcing/releasing Pico support is working


python2: ctypes.util.find_library is partially broken since gcc10

Describe the bug
Can be noticed when building python2.pkgs.cffi. Since https://github.com/NixOS/nixpkgs/pull/89793.
To Reproduce
Steps to reproduce the behavior:

...
...
...

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Notify maintainers

Metadata
Nixpkgs at b9330fe4ebb5f424919a2e88096859742f05954d
Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:

is this still relevant with #108569 ?

is this still relevant with #108569 ?

nope fixed with https://github.com/NixOS/nixpkgs/pull/108569

nope fixed with https://github.com/NixOS/nixpkgs/pull/108569


[BUG] Volumes fails to remount when they go read-only

Describe the bug
Some volumes go into read-only and requires me to restart the deployment in order to be able to write to the volume again.
To Reproduce

Install longhorn
Create a few volumes and mount them in pods using PVC:s
Volume goes read-only and longhorn tries to remount it
Remount fails and the volume stays in read only

Expected behavior
The volume should be remounted as read write.
Support bundle for troubleshooting
I sent the support bundle to the email<EMAIL_ADDRESS>with the subject "[BUG] Volumes fails to remount when they go read-only".
Environment

Longhorn version: v1.6.1
Impacted volume (PV): vaultwarden, uptime-kuma-data, thalwyrn-uptime-kuma-data
Installation method (e.g. Rancher Catalog App/Helm/Kubectl): kubectl
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version:

Number of control plane nodes in the cluster: 3
Number of worker nodes in the cluster: 3

Node config

OS type and version: Debian
Kernel version: 6.1.0-20-amd64
CPU per node: 6-8
Memory per node: 32-64 Gb
Disk type (e.g. SSD/NVMe/HDD): SSD (nodes *-01, *-03) & HDD (nodes *-02)
Network bandwidth between the nodes (Gbps): 100Mbps - 1Gbps

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal): KVM
Number of Longhorn volumes in the cluster: 9

Additional context
Log snippet from when the vaultwarden volume was read only to give you an idea as to when it was read only:
longhorn-manager-g2vgl time="2024-05-13T19:48:52Z" level=warning msg="Cannot auto-delete Pod when the associated Volume is not found" func="controller.(*KubernetesPodController).getAssociatedVolumes" file="kubernetes_pod_controller.go:466" controller=longhorn-kubernetes-pod error="volume.longhorn.io \"uptime-kuma-data\" not found" node=k3s-worker-01 pod=uptime-kuma-deployment-cc7c58b96-r6qq2

longhorn-manager-g2vgl time="2024-05-13T19:48:52Z" level=warning msg="Cannot auto-delete Pod when the associated Volume is not found" func="controller.(*KubernetesPodController).getAssociatedVolumes" file="kubernetes_pod_controller.go:466" controller=longhorn-kubernetes-pod error="volume.longhorn.io \"thalwyrn-uptime-kuma-data\" not found" node=k3s-worker-01 pod=uptime-kuma-deployment-6466cbffbc-z4mr9

longhorn-manager-8ncnl time="2024-05-13T19:48:56Z" level=info msg="Auto remount volume to read write at due to engine detected read-only filesystem" func="controller.(*VolumeController).requestRemountIfFileSystemReadOnly" file="volume_controller.go:1541" accessMode=rwo controller=longhorn-volume frontend=blockdev migratable=false node=k3s-master-02 owner=k3s-master-02 state=attached volume=vaultwarden

longhorn-manager-8ncnl time="2024-05-13T19:48:56Z" level=warning msg="Failed to remount read only volume" func="controller.(*VolumeController).requestRemountIfFileSystemReadOnly" file="volume_controller.go:1556" accessMode=rwo controller=longhorn-volume error="rpc error: code = Internal desc = remount failed with error: failed to execute: /usr/bin/nsenter [nsenter --mount=/proc/1/ns/mnt --net=/proc/1/ns/net mount -o remount,rw /host/var/lib/kubelet/plugins/kubernetes.io/csi/driver.longhorn.io/2f968f650a0ddcb1aff098dd009f7a161c247710277f77de40d9192006a546f3/globalmount], output , stderr mount: /host/var/lib/kubelet/plugins/kubernetes.io/csi/driver.longhorn.io/2f968f650a0ddcb1aff098dd009f7a161c247710277f77de40d9192006a546f3/globalmount: cannot remount /dev/longhorn/vaultwarden read-write, is write-protected.\n: exit status 32" frontend=blockdev migratable=false node=k3s-master-02 owner=k3s-master-02 state=attached volume=vaultwarden

The issues seems to resolve themselves after I restart the deployment manually. So somewhere in the logs I restarted the deployment after which it works.

cc @ChanYiLin

We're also experiencing this issue in our system.
The issue happens when using CNPG deployments with longhorn volumes attached (0 replicas).

@Shalankwa , sorry to contact you here, but can you elaborate on how it happen on 1 longhorn replica, on CNPG cluster, can the CNPG resolve itself?
if it happen on the primary, does the controller do switchover to another node?

@Shalankwa , sorry to contact you here, but can you elaborate on how it happen on 1 longhorn replica, on CNPG cluster, can the CNPG resolve itself? if it happen on the primary, does the controller do switchover to another node?
@fmiqbal

I believe the CNPG controller does switch to the 2nd CNPG pod when read-only occurs on the primary.
However, the primary instance doesn't get resolved by the CNPG manager (still looking into configuration settings for this) and remains in a restart loop. The CNPG manager continuously restart the postgres container within the pod, but the issues remains as the volume attached remains in read-only.
Only after I manually restart the entire pod (delete the pod - wait for new one) the issue is corrected.
I'll try to provide more logs of this situation when It occurs next.

Removing stale first. cc @derekbit to see if more feedback, it seems some users having similar issues from emoji feedback.

cc @ChanYiLin

Yes, when it is read-only, sometimes it can't be remount due to the device becomes write-protected.
We are now trying another approach to see if we can prevent it from becoming read-only at the first place


Add test for fitEDD

Sorry, I did not have time to review this. Let me know if you need feedback asap.


why api dont show for me in knoxss

why api dont show for me in knoxss , i cant found ?
https://knoxss.me/?page_id=252

KNOXSS is a paid subscription; you need to pay to access the KNOXSS pro API.


Open terminal on rightclick on a folder

What's the Problem?
No response
Solution/Idea
Add to open folder interaction menu (right-click menu on folder) "Open with Terminal". As it already is in right-click on empty space in the folder.
Alternatives
Nothing, because it's already when I enter to the folder and right-click.
Priorities
No response
Files Version
No response
Windows Version
No response
Comments
No response

Merging with #5248


Add generic attributes

Fixes #25681
Add a description of the generic attributes preview feature.

This is ready, pending the questions for the compiler team.

This is ready now.


Feature upgrade dependencies

Basic information

nrich-demo-backend version:

Additional information

Description
Summary
Upgrade dependencies to latest versions.
Details
Upgrade dependencies to latest versions.
Related issue

Types of changes

Dependency upgrade

Checklist

[x] I have read the project's CONTRIBUTING document
[x] I have checked my code with the project's static analysis tooling
[x] I have formatted my code with the project's IDEA code-style configuration
[x] I have checked my code for misspellings
[x] I have organized my changes in easy-to-follow commits
My change requires a change to the documentation
I have updated the documentation accordingly
I have added tests to cover my changes
[x] All new and existing tests pass

Codecov Report
Base: 97.16% // Head: 97.16% // No change to project coverage :thumbsup:

Coverage data is based on head (d4c5d8b) compared to base (5dbc2b0).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##             master      #19   +/-   ##
=========================================
  Coverage     97.16%   97.16%
  Complexity       97       97
=========================================
  Files            39       39
  Lines           247      247
  Branches          4        4
=========================================
  Hits            240      240
  Misses            7        7

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Unresolved external symbol, LNK2019

Hi, I am trying to build is parser on Windows but I am getting the following error. Any idea? 😕
Severity	Code	Description	Project	File	Line	Suppression State
Error	LNK2019	unresolved external symbol tree_sitter_SQL referenced in function "void __cdecl `anonymous namespace'::New(class Nan::FunctionCallbackInfo<class v8::Value> const &)" (?New@?A0x0ea7bc37@@YAXAEBV?$FunctionCallbackInfo@VValue@v8@@@Nan@@@Z)	tree_sitter_SQL_binding	C:\Users\[NAME]\workspace\tree-sitter-sql\build\binding.obj	1

Thanks for testing :) Seems like some symbols were left with capitalized names when I first generated code for this project. Fixed and added CI for windows.


Update C++ client version and compatiblity table to v2.10.1

Motivation
Relates to https://github.com/apache/pulsar-client-node/pull/215 and https://github.com/apache/pulsar/pull/15508
According to https://github.com/apache/pulsar-client-node/pull/215 , "double callback segfault" issue was fixed in https://github.com/apache/pulsar/pull/15508 .
The https://github.com/apache/pulsar/pull/15508 fix was released as v2.10.1 ( https://github.com/apache/pulsar/commit/fa05a850e7356b42591fc04506496026c96ad878 ).
We should use the fixed version of C++ client.
Modifications

Modify pulsar-version.txt to use C++ client version to v2.10.1 in CI
Update compatibility table

Verifying this change

[ ] Make sure that the change passes the CI checks.

This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API: (no)
The schema: (no)
The default values of configurations: (no)
The wire protocol: (no)

Documentation

Does this pull request introduce a new feature? (no)

In apachepulsar/pulsar-build:ubuntu-16.04 image, use -Xlog:gc*:logs/pulsar_gc_%p.log:time,uptime:filecount=10,filesize=20M option for runtime.
https://github.com/apache/pulsar/blob/v2.10.1/conf/pulsar_env.sh#L50-L58
However, pulsar command uses JAVA_HOME=/usr/lib/jvm/java-1.8.0-openjdk-amd64 in runtime.
https://hub.docker.com/layers/apachepulsar/pulsar-build/ubuntu-16.04/images/sha256-57174595e685002c0e4ce768361af8c10fcf30310f466966c3f8663a8638e4b7?context=explore
Unrecognized option: -Xlog:gc*:logs/pulsar_gc_%p.log:time,uptime:filecount=10,filesize=20M
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

(The script file was fixed in https://github.com/apache/pulsar/pull/14711 .)
I updated the docker image tag to ubuntu-20.04 to avoid this issue.
JAVA_HOME was not set in ubuntu-20.04 image.
https://hub.docker.com/layers/apachepulsar/pulsar-build/ubuntu-20.04/images/sha256-5f50d029fa6ba5a1d410faf7d4d0539200246572a1459cb6e3cc32219300f591?context=explore
Also, I modified test scripts to fix the below issue.
fatal: unsafe repository ('/pulsar-client-node' is owned by someone else)
To add an exception for this directory, call:

	git config --global --add safe.directory /pulsar-client-node

It seems https://github.com/apache/pulsar/pull/15009 causes the following errors. This change was released as v2.9.3 and v2.10.1 .
I modified test codes to address this change.
> jest --verbose

Browserslist: caniuse-lite is outdated. Please run:
  npx browserslist@latest --update-db
  Why you should do it regularly: https://github.com/browserslist/browserslist#browsers-data-updating
PASS tests/end_to_end.test.js (9.466 s)
  End To End
    ✓ Produce/Consume (582 ms)
    ✓ negativeAcknowledge (2381 ms)
    ✓ getRedeliveryCount (310 ms)
    ✓ Produce/Consume Listener (103 ms)
    ✓ Produce/Read Listener (98 ms)
    ✓ acknowledgeCumulative (1091 ms)
    ✓ subscriptionInitialPosition (125 ms)
    ✓ Produce/Read (92 ms)
    ✓ Produce-Delayed/Consume (3100 ms)
    ✓ Produce/Consume/Unsubscribe (141 ms)
    ✓ Produce/Read (Compression) (66 ms)
    ✓ Produce/Consume-Pattern (134 ms)
    ✓ Produce/Consume-Multi-Topic (140 ms)
    ✓ Produce/Consume and validate MessageId (224 ms)
    ✓ Basic produce and consume encryption (115 ms)
    ✓ Produce/Consume/Read/IsConnected (17 ms)

FAIL tests/consumer.test.js
  Consumer
    Create
      ✓ No Topic (1 ms)
      ✓ Not String Topic (1 ms)
      ✓ Not String TopicsPattern
      ✓ Not Array Topics
      ✓ Not String in Array Topics (1 ms)
      ✓ No Subscription
      ✓ Not String Subscription (1 ms)
      ✕ Not Exist Tenant (18 ms)
      ✕ Not Exist Namespace (4 ms)
      ✓ Not Positive NAckRedeliverTimeout (1 ms)
    Close
      ✓ throws error on subsequent calls to close (55 ms)

  ● Consumer › Create › Not Exist Tenant

    expect(received).rejects.toThrow(expected)

    Expected substring: "Failed to create consumer: ConnectError"
    Received message:   "Failed to create consumer: BrokerMetadataError"

      103 |           ackTimeoutMs: 10000,
      104 |           nAckRedeliverTimeoutMs: 60000,
    > 105 |         })).rejects.toThrow('Failed to create consumer: ConnectError');
          |                     ^
      106 |       });
      107 |
      108 |       test('Not Exist Namespace', async () => {

      at Object.toThrow (node_modules/expect/build/index.js:285:22)
      at Object.<anonymous> (tests/consumer.test.js:105:21)

  ● Consumer › Create › Not Exist Namespace

    expect(received).rejects.toThrow(expected)

    Expected substring: "Failed to create consumer: ConnectError"
    Received message:   "Failed to create consumer: BrokerMetadataError"

      112 |           ackTimeoutMs: 10000,
      113 |           nAckRedeliverTimeoutMs: 60000,
    > 114 |         })).rejects.toThrow('Failed to create consumer: ConnectError');
          |                     ^
      115 |       });
      116 |
      117 |       test('Not Positive NAckRedeliverTimeout', async () => {

      at Object.toThrow (node_modules/expect/build/index.js:285:22)
      at Object.<anonymous> (tests/consumer.test.js:114:21)

FAIL tests/producer.test.js
  Producer
    Create
      ✓ No Topic (1 ms)
      ✓ Not String Topic (1 ms)
      ✕ Not Exist Tenant (3 ms)
      ✕ Not Exist Namespace (2 ms)
      ✓ Automatic Producer Name (42 ms)
      ✓ Explicit Producer Name (6 ms)
      ✓ Topic Name (6 ms)

  ● Producer › Create › Not Exist Tenant

    expect(received).rejects.toThrow(expected)

    Expected substring: "Failed to create producer: ConnectError"
    Received message:   "Failed to create producer: BrokerMetadataError"

      56 |           sendTimeoutMs: 30000,
      57 |           batchingEnabled: true,
    > 58 |         })).rejects.toThrow('Failed to create producer: ConnectError');
         |                     ^
      59 |       });
      60 |
      61 |       test('Not Exist Namespace', async () => {

      at Object.toThrow (node_modules/expect/build/index.js:285:22)
      at Object.<anonymous> (tests/producer.test.js:58:21)

  ● Producer › Create › Not Exist Namespace

    expect(received).rejects.toThrow(expected)

    Expected substring: "Failed to create producer: ConnectError"
    Received message:   "Failed to create producer: BrokerMetadataError"

      64 |           sendTimeoutMs: 30000,
      65 |           batchingEnabled: true,
    > 66 |         })).rejects.toThrow('Failed to create producer: ConnectError');
         |                     ^
      67 |       });
      68 |
      69 |       test('Automatic Producer Name', async () => {

      at Object.toThrow (node_modules/expect/build/index.js:285:22)
      at Object.<anonymous> (tests/producer.test.js:66:21)

PASS tests/reader.test.js
  Reader
    ✓ No Topic (1 ms)
    ✓ Not String Topic (1 ms)
    ✓ No StartMessageId (1 ms)
    ✓ Not StartMessageId as MessageId

Test Suites: 2 failed, 2 passed, 4 total
Tests:       4 failed, 34 passed, 38 total
Snapshots:   0 total
Time:        9.915 s
Ran all test suites.


Allow for multiple load-balancers in the update launch configuration GUI

The SYD office has started using pitchfork quite extensively and we've encountered a restrictions in the GUI that prevent us from easily setting certain configurations that customers need. I'll create issues for both of them. This ticket is for multiple load-balancerss.
An autoscale group can have multiple load balancers associated with it. Many of our customers often have internet traffic that exceeds the baseline for a single CLB so we often end up recommending they use 2 or more CLBs and use DNS round-robin with them. This in turn means that the autoscaling groups that they use need to be configured with multiple load balancers. Autoscaling allows for this provision because the load_balancers field is a list of values, however it's not currently possible to set multiple load balancers through Reach.
We are aiming to use pitchfork to configure AS for our customers, but the pitchfork gui also does not give the option to specify multiple load balancers. Would it be possible to change the pitchfork gui in a way that it would allow the specification of multiple load balancers in the launch configuration  update API call?
Thanks!
j

PR #62 covered a single field duplication, and will see what can be done for a group of fields.

Closing as active development on this project has stopped.


After importing IvyCarouselModule in my module, it still gives me error in template that carousel is not a known element

solved it

how did you solved this?

I am still facing this issue. Can some please provide the solution

I am facing this issue as well. Not sure what is going on..

Fixed it in the CLI with:
npm install @popperjs/core@latest


Use (legacy) API for updater (v1)

Copied code for KeybaseUpdateSource from v2 updater
Remove "main" channel, since default should be empty ""

@keybase/updater-hackers @maxtaco

What should the API server reply with if no update is necessary?

20:30:18 ../vendor/github.com/keybase/go-updater/sources/keybase.go:38: undefined: util in util.RandString

It can return a 404 on no update

ok build should be fixed... i'm checking 404 now and returning "no update" in that case

on it

Let's hold off until we have a clear ordering in a deployment plan per https://keybase.atlassian.net/browse/DESKTOP-1182

👍


Getting error running preprocessing.py

Hi,
I am getting error
File "preprocessing.py", line 27
prefix = files[ValueError: invalid literal for int() with base 10: 0].rsplit('-', 1)[0]
How can we resolve this issue?
Thanks
sd

Fixed. Problem was the path had extra train folder /data/train/train.
Thanks


Have changes in Selmer template files propagated without needing an Integrant reset (during development).

It feels odd that changes in Selmer templates do not have effect until you do an Integrant reset in the REPL. I know this is analogous to how code changes are handled (reset always needed), but since the template files are referenced from the source itself it seems logical that changes to them take effect immediately.
I do see the value of automatic caching/memoization in production.
I tried disabling the caching by doing (selmer.parser/cache-off!) in the user.clj ns but this does not seem to help.

If you update the init multimethod in the pages namespace as follows, and that should do the trick
(defmethod ig/init-key :reitit.routes/pages
  [_ {:keys [base-path]
      :or   {base-path ""}
      :as   opts}]
  (layout/init-selmer!)
  (when (= :dev (:env opts))
    (selmer.parser/cache-off!))
  [base-path (route-data opts) (page-routes opts)])

Indeed. Perhaps it would be a good idea to add this to the stock pages component template?

Yup, I've updated the module with the code.


1.0.0-beta.19 - React 16 warnings for React.PropTypes, react.createClass

Current Behavior

Using react navigation "^1.0.0-beta.15" installs "1.0.0-beta.19" as expected, however Dev tools now complain that PropTypes have been moved to prop-types and React.createClass has been deprecated.
Is the library @1.0.0-beta.19 using React.PropTypes and React.createClass directly? Because it shouldn't in react.16.x.x.
Has this been changed since 1.0.0-beta-15? I have since locked React Navigation to beta-15.
Thoughts?

Your Environment

software
version

react-navigation
1.0.0-beta.19

react-native
"^0.48.4"

node
lts (8.8.1)

npm or yarn
<EMAIL_ADDRESS>

Duplicate https://github.com/react-community/react-navigation/issues/2019#issuecomment-344848710


ncar_cmip_direct_name_map, 'pr' maps to 'PRECC'

Hi @doutriaux1
I came across this ncar_cmip_direct_name_map list, where 'pr' is mapping to 'PRECC' in NCAR convention. However pr in CMIP stands for total precip flux, while PRECC stands for convective precip flux. 'pr'='PRECT'='PRECC'+'PRECL'. Not sure if this dictionary is still in use. Just a reminder here.

@durack1 did you write this?

@chengzhuzhang @doutriaux1 yep that was me.
@chengzhuzhang the file you have referred to was generated by @gleckler1 in his demos for NCAR.
Thanks for pointing out the PR equivalence, we actually do have this captured in the code here and here (there are also some other fields that require more than a single input)
We will need to revise these demos, and I believe they are now out of sync with the latest master branch.. The example data is also likely deprecated..

@chengzhuzhang it would make sense to generate a "mapping dictionary" for all these variable names, I had started that in https://github.com/PCMDI/pcmdi_metrics/issues/176, however, it seems to have been closed this rather than pursuing this further.. Feel free to kick something like this off, I would be more than happy to iterate over this with you

@chengzhuzhang @durack1  It would be great to set something up as part of the code base, not a GH table.
One possibility would be to create a variable id mapping for all models.  We have a few nascent examples for several groups here:
https://github.com/PCMDI/pcmdi_metrics/tree/master/examples/external-setups
Starting with these, we could pull the variable_id mapping (+units and equations where variables are combined) across models into a common dictionary and build upon it, for example:
https://github.com/PCMDI/pcmdi_metrics/tree/master/examples/external-setups/AllModstoCMIP
or something like that.   Once we get a thought out example started we can close this issue and just open new ones as additions are made.
Thoughts?

@chengzhuzhang can you ping me where these mappings are located in the ACME-Climate/acme_diags?


Why is mono-6.4.0/msbuild-16.3.0 required?

Why have mono-6.4.0/msbuild-16.3.0 become a hard requirement? I am trying to use Omnisharp on a platform having mono6.8 available, but not having a readily available build of msbuild >= 16.3.0 (the only available version is msbuild15).
Since the task of upgrading the msbuild port does not appear to be trivial, as an alternative I am trying to assess the impact of patching Omnisharp to remove the hard requirement on msbuild 16.3.0 (and if this would be possible at all).

It is not a hard requirement, OmniSharp ships with its own bundled MSBuild as well, however if global Mono is available, it is attempted to be used because it will have reference assemblies for desktop .NET, which the bundled one doesn't.
The reason why lowest version of Mono MSBuild is what it is, is because of requirements in .NET Core - e.g. 3.1 requires MSBuiild 16.3 and 5.0 requires 16.8.
You can disable the discovery of global Mono and global MSBuild by adding an omnisharp.json file to the root of your project with the content
{
   "msbuild": {
       "useBundledOnly": true
   }
}

This will work for loading .NET Core projects, for loading desktop .NET the reference assemblies from global Mono are required so you will need to upgrade global Mono.


Just A PR test

do not merge

Description

How Has This Been Tested?

Screenshots, that help to understand the changes(if applicable):
Checklist:

[ ] A test for the new functionality was added.
[ ] All tests run without failure.
[ ] The new code complies with the TiGL style guide.
[ ] New classes have been added to the Python interface.
[ ] API changes were documented properly in tigl.h.

Codecov Report

Merging #729 into master will not change coverage.
The diff coverage is n/a.


When unstaking the fee timestamp is @2.5 minutes before staking receive timestamp

As the title

bug fixed


Assistant can't get terminal access

Describe the bug
When creating a simple python program, ('Hello, World!'), opendevin gets into a loop:

Steps to Reproduce

run with ollama (mixtral, nomic-embed-text)
not with Docker

Expected behavior
Not getting in endless loop
Actual behavior
Additional context

Tracked here https://github.com/OpenDevin/OpenDevin/issues/326

@jabbor what does git log -n1 show? Does the error persist if you pull latest?
Pretty sure we fixed this yesterday

I'll have a look when I'm back home. I'll let you know.
Sent from Outlook for Androidhttps://aka.ms/AAb9ysg

From: Robert Brennan @.>
Sent: Monday, April 1, 2024 5:02:15 PM
To: OpenDevin/OpenDevin @.>
Cc: jabbor @.>; Mention @.>
Subject: Re: [OpenDevin/OpenDevin] Error condensing thoughts (Issue #495)
@jabborhttps://github.com/jabbor what does git log -n1 show? Does the error persist if you pull latest?
Pretty sure we fixed this yesterday
—
Reply to this email directly, view it on GitHubhttps://github.com/OpenDevin/OpenDevin/issues/495#issuecomment-2029901587, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AL5TMOX67KOS5ATLKOB636DY3FZHPAVCNFSM6AAAAABFRMYRLSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRZHEYDCNJYG4.
You are receiving this because you were mentioned.Message ID: @.***>

@jabbor what does git log -n1 show? Does the error persist if you pull latest?
Pretty sure we fixed this yesterday

I'm not sure about that... The console log displays "Original JSON" and "Repaired JSON", which are from the json_repair merge. So this is after https://github.com/OpenDevin/OpenDevin/commit/4404b9af243d5281ebb3587e2daea23cb20fc281 . 😔

Yeah I see the issue now. For some weird reason the LLM is putting \ characters into the JSON to escape underscores. repair is double-escaping the \ instead of removing it.

@jabbor which model are you using? GPT?

https://github.com/mangiucugna/json_repair/issues/19

This is the output of the git log:

I'm going to try another model. Keep you guys posted.

instead of repairing json, a better solution would be to never allow the llm to output improper json.
https://github.com/outlines-dev/outlines

Agree--I'm starting to lean against the json repair and towards just erroring and telling the LLM more about the error

JSON repair has this fix now. We should work on a more robust long-term solution though


Technical debt: move Ouroboros.Consensus.Demo.* to separate package

This is only used for the demo playground and for testing, it shouldn't really live in the main lib. When we do move it, we should cull dependencies, because the main lib has some dependencies that are there only because the demo needs it.

Superseded by #702


FILTERGROUP behavior?

I am still trying to narrow down the behavior more, but it seems that FILTERGROUP has not function anymore really?
What I am doing in "OnOpenPage" is, based on some conditions, set additional filters that I don't want the user to be able to adjust. So, I used to use FILTERGROUP(2) or FILTERGROUP(4) to switch to one of the "protected" filtergroups and set the filter and then switch back to 0 and the user cannot remove the filter.
Doing this now leads to nothing other than the user being able to remove the filter just like any other filter that was set. So, is that intended behavior or is this a bug or am I "buggy" ;) ? If this is now the intended behavior, what am I supposed to do to get the desired functionality?

Hi, we will investigate it but in the meanwhile could I ask for a few more details:
Is this a regression in behavior either between AL vs C/AL,  NAV 2018 vs older versions  or web client vs win client?

@pzentner Could you please help me out with a code snippet showcasing this scenario?

@DominikDitoIvosevic I tried to create a snippet right now and validated in current build that it is now working as expected. So, something must have changed for the better. This now can be closed, I would think.

Great news :)
I'll close the issue then and we can reopen in case it resurfaces. @pzentner could you please share with us the snippet you used for reference?


Method hideAppointmentPopup() do'nt work for dropdownAppointment

Hello Dx Team!
I'm trying to hide all AppointmentPopup, but it doesn't work for dropdownAppointment, and same for AppointmentDblClick.
using this method:
Test(appointment) {
    debugger;
    this.scheduler.instance.hideAppointmentTooltip();
    this.scheduler.instance.hideAppointmentPopup();

   console.log('Call method okay');
}

Thanks,
Péterson Cardoso
devexteme version: 17.2.8
devextreme-angular version: 17.2.7

[x] bug Report
[ ] feature request
[ ] support inquiry

The Scheduler does not have a method to show/hide the appointment collector's drop-down list programmatically. I suggest you open a ticket in our support center to elaborate on why you need to show or hide it in code. We will research your scenario to find an appropriate solution.


MINOR: Clean up core server classes

Follow up from https://github.com/apache/kafka/pull/15252
Mark methods and fields private where possible:

Annotate public methods and fields
Remove unused classes and methods
Make sure Arrays are not printed with .toString
Optimize minor warnings

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@showuon if you have some time, this is a follow up of the one you reviewed already.

Needed to rebase because of merge conflicts

Rebased again to contain https://github.com/apache/kafka/pull/15290


Simple Arithmetic Calculator

Calculator Functions
Functionalities :-
Addition
Subtraction
Division
Multiplication
Contribution Event
GSSOC22
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

/assign

It is already there in the repo !
You can't create duplicate calculator !
Work only on one issue at a time !
Deleting this issue !

Hi there @vasu-1 .
My bad.


fix styling of the search bar

Added a search icon in the search bar and responsiveness in different devices.

Hey @EshanTrivedi21  I have made the search bar at the top so that users don't have to search down and added some styling to the search bar can you review it and merge it finally it has no conflicts with the main

@EshanTrivedi21 Search bar at the top - this pull request has no merge conflicts you can check
https://github.com/EshanTrivedi21/Git-CheatSheet/pull/96

@EshanTrivedi21  Sure I will just make the changes, Thanks

@EshanTrivedi21 Hey Done with the changes moved the Search bar at the top of the topics section.

@EshanTrivedi21 Thanks for accepting my PR , in my Hactoberfest profile it is showing not accepted can you look into it

It will show up in the waiting list for 7 days after which it would be updated and accepted.. its a hacktoberfest policy to surpass a 7 day waiting period @Abhay5855


Gather Top Functions

Close #223.

This is still work in progress but here are some results. For all outputs isthe following procedure used and the experiment is with default settings traced:
#pragma TextEncoding = "UTF-8"
#pragma rtGlobals=3				// Use modern global access method and strict wave access
#pragma DefaultTab={3,20,4}		// Set default tab width in Igor Pro 9 and later
#pragma ModuleName=foo

#include "unit-testing"

static Function Test()
	variable i

	for(i = 0; i < 10; i += 1)
		Foo_IGNORE()
	endfor
End

static Function Foo_IGNORE()
	PASS()
End

static Function Test2()
	variable foo
	if(1)
		foo = 1
	else
		foo = 2
	endif
	CHECK(foo)
End

static Function Test3()
	variable i
	for(i = 0; i<20; i += 1)
		PASS()
	endfor
End

•ShowTopFunctions(5, mode=UTF_ANALYTICS_FUNCTIONS, sorting=UTF_ANALYTICS_CALLS)
  Result:
Function Calls|Sum of called Lines|Procedure |Function  |Line|
--------------|-------------------|----------|----------|----|
10            |30                 |Tracer.ipf|Foo_IGNORE|15  |
1             |25                 |Tracer.ipf|Test      |7   |
1             |7                  |Tracer.ipf|Test2     |19  |
1             |44                 |Tracer.ipf|Test3     |29  |

•ShowTopFunctions(5, mode=UTF_ANALYTICS_FUNCTIONS, sorting=UTF_ANALYTICS_SUM)
  Result:
Function Calls|Sum of called Lines|Procedure |Function  |Line|
--------------|-------------------|----------|----------|----|
1             |44                 |Tracer.ipf|Test3     |29  |
10            |30                 |Tracer.ipf|Foo_IGNORE|15  |
1             |25                 |Tracer.ipf|Test      |7   |
1             |7                  |Tracer.ipf|Test2     |19  |

•ShowTopFunctions(5, mode=UTF_ANALYTICS_LINES, sorting=UTF_ANALYTICS_CALLS)
  Result:
Calls|Procedure |Function  |Line|
-----|----------|----------|----|
20   |Tracer.ipf|Test3     |32  |
20   |Tracer.ipf|Test3     |33  |
10   |Tracer.ipf|Test      |11  |
10   |Tracer.ipf|Test      |12  |
10   |Tracer.ipf|Foo_IGNORE|15  |

•ShowTopFunctions(100, mode=UTF_ANALYTICS_LINES, sorting=UTF_ANALYTICS_CALLS)
  Result:
Calls|Procedure |Function  |Line|
-----|----------|----------|----|
20   |Tracer.ipf|Test3     |32  |
20   |Tracer.ipf|Test3     |33  |
10   |Tracer.ipf|Test      |11  |
10   |Tracer.ipf|Test      |12  |
10   |Tracer.ipf|Foo_IGNORE|15  |
10   |Tracer.ipf|Foo_IGNORE|16  |
10   |Tracer.ipf|Foo_IGNORE|17  |
1    |Tracer.ipf|Test      |7   |
1    |Tracer.ipf|Test      |8   |
1    |Tracer.ipf|Test      |9   |
1    |Tracer.ipf|Test      |10  |
1    |Tracer.ipf|Test      |13  |
1    |Tracer.ipf|Test2     |19  |
1    |Tracer.ipf|Test2     |20  |
1    |Tracer.ipf|Test2     |21  |
1    |Tracer.ipf|Test2     |22  |
1    |Tracer.ipf|Test2     |25  |
1    |Tracer.ipf|Test2     |26  |
1    |Tracer.ipf|Test2     |27  |
1    |Tracer.ipf|Test3     |29  |
1    |Tracer.ipf|Test3     |30  |
1    |Tracer.ipf|Test3     |31  |
1    |Tracer.ipf|Test3     |34  |

•ShowTopFunctions(5, mode=UTF_ANALYTICS_LINES, sorting=UTF_ANALYTICS_SUM)
  Sum sorting is only available for the functions mode

I will organize and reword the commits tomorrow. But what do you think about it? @t-b @MichaelHuth

The output looks good. Is the data also available as permanent text wave with dimension labels (the columns in the output would make very good dimension labels)? I'm asking because this allows developers to massage the output more.
The output would benefit from having spaces around |. For IP7 and above you can use wfprintf for the output.

There is an intermediate (free) text wave with all the data (right now without any dimension labels) which is converted with UTF_Utils#NicifyTableText to string and printed. I can make it permanent and provide labels (for the last part I have to look up how it's done).
I also think spaces around the | will look nice but it's the same method that styles the output for the wave diff. I will see if I can teach it to make spaces around.

I also think spaces around the | will look nice but it's the same method that styles the output for the wave diff. I will see if I can teach it to make spaces around.

I'm okay with always spaces.

Sorry I forgot to mention the global wave.

done

@MichaelHuth Is that assigned correctly?

Thomas noted also that when you use TUFXOP_GetStorage and evaluate V_flag you have to use the /Z flag.


Better positioning of general EDNS option handling

General EDNS options like PADDING and NSID were only returned with answers from cache or from authoritative zones.
This commit repositions the handling of general EDNS options (from the apply_edns_options() function) so it is better cooperating with handling of EDNS options from modules, and as a result the options are handled for synthesized answers (like local data and id.server queries) too.
@gthess I have some questions about this. Can we discuss?

Closing this in favor of #563


Error reading data from metavision raw file

HI!
Instead of opening the camera to view the streaming from it I would like to read the data from the metavision raw file.
The from_file parameter is listed in the README parameters section, which should allow me to do what I want, but it is not present in any launch file.
Then, in the driver_node.launch file I added this line:
<param name="from_file" value="/home/acentauri/Downloads/driving_sample.raw"/>
Once I do this, if I try to launch the driver with the command roslaunch metavision_driver driver_node.launch I get the following error:

Am I forgetting something or what is the way to read the raw files and view them?
I'm using ROS Noetic and Ubuntu 20.04.
Thank you!
Best,
Thomas

Thanks for the reply but that's not what I meant, or maybe I didn't understand your explanation.
What do you mean by the foo.raw and foo.bias files? Where do I find them?
I already have a dataset file called driving_sample.raw and I would like to run it with the driver displaying the events with the render. I therefore don't have to record raw data from the camera.
(also because I believe that if I want to read from raw file it is not necessary to connect the camera, but it is still detected in the ROS INFO message)

Never mind my previous hack with the bias file. The problem is a straight and simple bug in the driver. You do not need a bias file. A pull request (PR #39) is pending, once the tests pass I'll merge into master.

Thank you much for opening this issue! User feedback is very important especially for driver software where automated testing is difficult.
Please close this issue if things work for you now.

Ok now with the changes made the reading of the raw file works without any errors.
I noticed a few things:

The duration of my raw dataset file should be around 12 seconds, while with the renderer and the viewer the display duration is only almost 2 seconds.

NOTE: Before launching the driver I ran the renderer and rqt_image_view to make sure I didn't lose any data.
From what little I can see it seems theat the driver speds up the raw file. Could be?

Also, a limitation is that you cannot play back EVT2 raw files of Gen3.0 or Gen3.1 sensors due to smaller resolution geometry.

I attach the error in this case (Gen3.0 and RAW EVT2):

[ERROR] [1700747806.030973249]: /event_camera: basic_string::substr: __pos (which is<PHONE_NUMBER>3709551612) > this->size() (which is 0)
[event_camera-2] process has died [pid 81853, exit code 255, cmd /home/acentauri/thomas/metavision_ros_ws/devel/lib/metavision_driver/driver_node __name:=event_camera __log:=/home/acentauri/.ros/log/ 235b7016-8a08-11ee-9ae1-e5d118aef45e/event_camera-2.log].
log file: /home/acentauri/.ros/log/235b7016-8a08-11ee-9ae1-e5d118aef45e/event_camera-2*.log

I noticed a few things:
The duration of my raw dataset file should be around 12 seconds, while with the renderer and the viewer the display duration is only almost 2 seconds.
From what little I can see it seems theat the driver speds up the raw file. Could be?

Yes, I confirm that the visualized data are speeded up.

Can you post a (short!) raw file from the Gen 3.0 sensor? The oldest I have available is a 3.1 sensor. Looking into the speedup issue to see if I can reproduce it.

For the raw file from the Gen3.0 sensor I tried with this one: https://docs.prophesee.ai/stable/datasets.html -> traffic_monitoring (Cars moving on a highway) [28 s , 70.3 MB]
Instead for the speedup issue I tried with the driving_sample (Driving on a street road) recording, in the same previous link, which is generated by a Gen4.1 sensor.

I have the speedup issue, too. It does not look like it's easy to fix. Just setting the realtime flag in the file configuration hints did not do the trick. AFAICT the driver would have to decode the messages and sleep until the right time stamp comes up. Right now the driver is not decoding time stamps for performance reasons.
Can you make a strong case that you really need this feature?

If you just want to play a raw file into the ROS ecosystem you have other options. You can for instance convert the raw file to a rosbag using the raw_to_bag from the event_camera_tools repo and then use rosbag play to play the bag. That should address the playback speed issues.

Sorry, but EVT2 file format is not supported. You'd have to write a decoder for it which is quite some work.

I have the speedup issue, too. It does not look like it's easy to fix. Just setting the realtime flag in the file configuration hints did not do the trick. AFAICT the driver would have to decode the messages and sleep until the right time stamp comes up. Right now the driver is not decoding time stamps for performance reasons.
Can you make a strong case that you really need this feature?

The timestamp is useful in the case of a moving event camera to perform motion compensation.
But the conversion from raw to rosbag file might be fine for me.
If there are no other considerations or updates regarding the timestamp, you can close this issue.
Thank you!

As far as time stamps are concerned: the sped up playback will only affect the ROS stamps, i.e. the "header.stamp" field in the message header. The sensor time stamp is embedded in the EVT3 data stream and is unaffected by the sped up playback. You can fully recover it from the rosbag.
The ROS header time stamps are only useful for correlating two different sensors, e.g. an event camera and a frame based camera. But in this scenario you would not be playing back the event data from a raw file, but rather recording both event and frame based sensors live.
Alright, closing the issue.


Error reported when running multiple cards with docker container on cloud platform

WARNING 08-18 01:35:48 tokenizer.py:63] Using a slow tokenizer. This might cause a significant slowdown. Consider using a fast tokenizer instead.
 To troubleshoot the problem, check the logs for the dead worker. RayTask ID: ffffffffffffffff21c4c317b5f12f485dd3ed9601000000 Worker ID: cbf297e4214dfe3a61a62347babe5995cec3a1c41787c1360a8e9b2b Node ID: 833e5e412a4498ac61480486982c4a8dbcaf6081437a976c4bbf2579 Worker IP address: <IP_ADDRESS> Worker port: 42604 Worker PID: 4711 Worker exit type: SYSTEM_ERROR Worker exit detail: Worker unexpectedly exits with a connection error code 2. End of file. There are some potential root causes. (1) The process is killed by SIGKILL by OOM killer due to high memory usage. (2) ray stop --force is called. (3) The worker is crashed unexpectedly due to SIGSEGV or other unexpected errors.
Traceback (most recent call last):
File "/workspace/vllm_server/vllm_server.py", line 448, in
engine = AsyncLLMEngine.from_engine_args(engine_args)
File "/usr/local/lib/python3.10/site-packages/vllm/engine/async_llm_engine.py", line 232, in from_engine_args
engine = cls(engine_args.worker_use_ray,
File "/usr/local/lib/python3.10/site-packages/vllm/engine/async_llm_engine.py", line 55, in init
self.engine = engine_class(*args, **kwargs)
File "/usr/local/lib/python3.10/site-packages/vllm/engine/llm_engine.py", line 104, in init
self._init_cache()
File "/usr/local/lib/python3.10/site-packages/vllm/engine/llm_engine.py", line 182, in _init_cache
num_blocks = self._run_workers(
File "/usr/local/lib/python3.10/site-packages/vllm/engine/llm_engine.py", line 474, in _run_workers
all_outputs = ray.get(all_outputs)
File "/usr/local/lib/python3.10/site-packages/ray/_private/auto_init_hook.py", line 18, in auto_init_wrapper
return fn(*args, **kwargs)
File "/usr/local/lib/python3.10/site-packages/ray/_private/client_mode_hook.py", line 103, in wrapper
return func(*args, **kwargs)
File "/usr/local/lib/python3.10/site-packages/ray/_private/worker.py", line 2542, in get
raise value
ray.exceptions.RayActorError: The actor died unexpectedly before finishing this task.
class_name: RayWorker
actor_id: 21c4c317b5f12f485dd3ed9601000000
pid: 4711
namespace: 5e81e4ce-e6f9-4a5a-9850-91ec998fdc6c
ip: <IP_ADDRESS>
The actor is dead because its worker process has died. Worker exit type: SYSTEM_ERROR Worker exit detail: Worker unexpectedly exits with a connection error code 2. End of file. There are some potential root causes. (1) The process is killed by SIGKILL by OOM killer due to high memory usage. (2) ray stop --force is called. (3) The worker is crashed unexpectedly due to SIGSEGV or other unexpected errors.
2023-08-18 01:35:59,200	WARNING worker.py:2019 -- A worker died or was killed while executing a task by an unexpected system error. To troubleshoot the problem, check the logs for the dead worker. RayTask ID: ffffffffffffffff60393bd46c6885795e8c860a01000000 Worker ID: bdd9060e04da02c94c78e0576e5dab9fa63c0cd82eeb9a09870749d1 Node ID: 833e5e412a4498ac61480486982c4a8dbcaf6081437a976c4bbf2579 Worker IP address: <IP_ADDRESS> Worker port: 35128 Worker PID: 4712 Worker exit type: SYSTEM_ERROR Worker exit detail: Worker unexpectedly exits with a connection error code 2. End of file. There are some potential root causes. (1) The process is killed by SIGKILL by OOM killer due to high memory usage. (2) ray stop --force is called. (3) The worker is crashed unexpectedly due to SIGSEGV or other unexpected errors.
(RayWorker pid=4712) *** SIGBUS received at time=1692322557 on cpu 3 ***
(RayWorker pid=4712) PC: @     0x7fb345256b41  (unknown)  (unknown)
(RayWorker pid=4712)     @     0x7fb34542b420       3424  (unknown)
(RayWorker pid=4712)     @ 0x574e2d6c63636e2f  (unknown)  (unknown)
(RayWorker pid=4712) [2023-08-18 01:35:57,940 E 4712 4961] logging.cc:361: *** SIGBUS received at time=1692322557 on cpu 3 ***
(RayWorker pid=4712) [2023-08-18 01:35:57,941 E 4712 4961] logging.cc:361: PC: @     0x7fb345256b41  (unknown)  (unknown)
(RayWorker pid=4712) [2023-08-18 01:35:57,942 E 4712 4961] logging.cc:361:     @     0x7fb34542b420       3424  (unknown)
(RayWorker pid=4712) [2023-08-18 01:35:57,943 E 4712 4961] logging.cc:361:     @ 0x574e2d6c63636e2f  (unknown)  (unknown)
(RayWorker pid=4712) Fatal Python error: Bus error
(RayWorker pid=4712)  [repeated 2x across cluster] (Ray deduplicates logs by default. Set RAY_DEDUP_LOGS=0 to disable log deduplication, or see https://docs.ray.io/en/master/ray-observability/ray-logging.html#log-deduplication for more options.)
(RayWorker pid=4712) Extension modules: msgpack._cmsgpack, setproctitle, google._upb._message, psutil._psutil_linux, psutil._psutil_posix, yaml._yaml, grpc._cython.cygrpc, ray._raylet, charset_normalizer.md, numpy.core._multiarray_umath, numpy.core._multiarray_tests, numpy.linalg._umath_linalg, numpy.fft._pocketfft_internal, numpy.random._common, numpy.random.bit_generator, numpy.random._bounded_integers, numpy.random._mt19937, numpy.random.mtrand, numpy.random._philox, numpy.random._pcg64, numpy.random._sfc64, numpy.random._generator, torch._C, torch._C._fft, torch._C._linalg, torch._C._nested, torch._C._nn, torch._C._sparse, torch._C._special, sentencepiece._sentencepiece, pyarrow.lib, pyarrow._hdfsio, pyarrow._fs, pyarrow._hdfs, pyarrow._gcsfs, pyarrow._s3fs, pandas._libs.tslibs.np_datetime, pandas._libs.tslibs.dtypes, pandas._libs.tslibs.base, pandas._libs.tslibs.nattype, pandas._libs.tslibs.timezones, pandas._libs.tslibs.ccalendar, pandas._libs.tslibs.fields, pandas._libs.tslibs.timedeltas, pandas._libs.tslibs.tzconversion, pandas._libs.tslibs.timestamps, pandas._libs.properties, pandas._libs.tslibs.offsets, pandas._libs.tslibs.strptime, pandas._libs.tslibs.parsing, pandas._libs.tslibs.conversion, pandas._libs.tslibs.period, pandas._libs.tslibs.vectorized, pandas._libs.ops_dispatch, pandas._libs.missing, pandas._libs.hashtable, pandas._libs.algos, pandas._libs.interval, pandas._libs.lib, pandas._libs.hashing, pandas._libs.tslib, pandas._libs.ops, pyarrow._compute, pandas._libs.arrays, pandas._libs.sparse, pandas._libs.reduction, pandas._libs.indexing, pandas._libs.index, pandas._libs.internals, pandas._libs.join, pandas._libs.writers, pandas._libs.window.aggregations, pandas._libs.window.indexers, pandas._libs.reshape, pandas._libs.groupby, pandas._libs.testing, pandas._libs.parsers, pandas._libs.json, pydantic.typing, pydantic.errors, pydantic.version, pydantic.utils, pydantic.class_validators, pydantic.config, pydantic.color, pydantic.datetime_parse, pydantic.validators, pydantic.networks, pydantic.types, pydantic.json, pydantic.error_wrappers, pydantic.fields, pydantic.parse, pydantic.schema, pydantic.main, pydantic.dataclasses, pydantic.annotated_types, pydantic.decorator, pydantic.env_settings, pydantic.tools, pydantic, pyarrow._json, PIL._imaging (total: 103)

Device information is as follows：
root@e5ada9ab73f0:/workspace/vllm_server# df -h
Filesystem      Size  Used Avail Use% Mounted on
overlay         296G   77G  204G  28% /
tmpfs            64M     0   64M   0% /dev
tmpfs            53G     0   53G   0% /sys/fs/cgroup
shm              64M   20M   45M  31% /dev/shm
/dev/vdb        296G   77G  204G  28% /workspace/models
tmpfs            53G   12K   53G   1% /proc/driver/nvidia
/dev/vda1        40G  4.7G   33G  13% /usr/bin/nvidia-smi
devtmpfs         53G     0   53G   0% /dev/nvidia0
tmpfs            53G     0   53G   0% /proc/asound
tmpfs            53G     0   53G   0% /proc/acpi
tmpfs            53G     0   53G   0% /proc/scsi
tmpfs            53G     0   53G   0% /sys/firmware
root@e5ada9ab73f0:/workspace/vllm_server# free -g
total        used        free      shared  buff/cache   available
Mem:            105           3          39           0          63         101
Swap:             0           0           0
root@e5ada9ab73f0:/workspace/vllm_server# nvidia-smi
Fri Aug 18 01:51:40 2023
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 515.105.01   Driver Version: 515.105.01   CUDA Version: 11.8     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  NVIDIA A30          Off  | 00000000:00:08.0 Off |                    0 |
| N/A   38C    P0    31W / 165W |      0MiB / 24576MiB |      0%      Default |
|                               |                      |             Disabled |
+-------------------------------+----------------------+----------------------+
|   1  NVIDIA A30          Off  | 00000000:00:09.0 Off |                    0 |
| N/A   35C    P0    30W / 165W |      0MiB / 24576MiB |      0%      Default |
|                               |                      |             Disabled |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
|  No running processes found                                                 |
+-----------------------------------------------------------------------------+

I am not a maintainer. Are you running anything else on your GPU?

vLLM is designed to occupy all the GPU memory for storing KV cache blocks. You can pass in the gpu_memory_utilization=0.5 (50% utilization, or can be set even lower) when initialize the LLM class to reduce the memory footprint.

https://github.com/vllm-project/vllm/issues/304#issuecomment-1613254311
Did you try using the parameter --gpu-memory-utilization GPU_MEMORY_UTILIZATION?
See also: #751

Thank you for your reply.  I am running the task exclusively,  it has nothing to do with the parameter.
And the error only appears in multi-card running, single card is normal.  Does the use of ray running multi-card take up more cpu memory?

Resolved, the container's shared memory is insufficient

the same issue in container, but memory is enough,
did you how to resolve?

@luefei  try run docker that use "--shm-size" to  increase container's shared memory.

how much memory did you allocate to /dev/shm ? Even with 30GB I get this error for Mistral model. I don't get this error for Llama-2-13b-chat

I'm also having the same issue, I started vllm qwen acceleration in a container, using 8 graphics cards, --shm-size gave 380G, and I also get an error like this