Yu Hu

i'm trying the same thing, but seeing slightly different errors. i got these warning when i run pkg . ``` > [email protected] > Warning Cannot resolve 'config.extends' /$PWD/tmp/cli/dist/spec-node/devContainersSpecCLI.js Dynamic require...

i can see that's useful if I'm importing my data from somewhere else. but if I already have the data mounted as volume inside the container, why do i still...

also when you say link to the added dataset by id, do you mean i can go there through a path based routing (e.g. localhost:5000/datasets/) or do you mean from...

thanks Josh, I can work with that :)

Hi josh, circling back here. can we support [http://127.0.0.1:5000/#q={"url":"/path/to/*.zarr"}] too? any reason we are not forcing uniqueness based on the dataset path?

hi, we are observing artifacts missing for the beta version. The older version 4426.1.0 contains [flatcar-nvidia-drivers-570-open.gz](https://update.release.flatcar-linux.net/amd64-usr/4426.1.0/flatcar-nvidia-drivers-570-open.gz). https://update.release.flatcar-linux.net/amd64-usr/4459.1.0/ is returning 404. We are forced to pin to 4426.1.0 before this issue...

that's surprising because the beta image on gcp is already pulling 4459 gcloud compute images describe-from-family flatcar-beta \ --project=kinvolk-public ``` archiveSizeBytes: '571233408' creationTimestamp: '2025-10-13T07:32:32.432-07:00' description: The Beta channel consists of...

Should we check the order of the release to make sure that the image is not the default beta image to pull when the artifacts are not uploaded yet? As...

> > hi, we are observing artifacts missing for the beta version. The older version 4426.1.0 contains [flatcar-nvidia-drivers-570-open.gz](https://update.release.flatcar-linux.net/amd64-usr/4426.1.0/flatcar-nvidia-drivers-570-open.gz). > > https://update.release.flatcar-linux.net/amd64-usr/4459.1.0/ is returning 404. We are forced to pin to...