Required dandi-cli 0.78.0 in the dandi image - #33
Merged
Conversation
dispatch.py runs every download with `-e refresh`, which skipped nothing at all on filesystems whose mtimes are coarser than sub-second (dandi/dandi-cli#1907). On the production runner that meant each pass re-fetched whole incoming dandisets rather than refreshing them. dandi/dandi-cli#1910 fixed it upstream, released in 0.78.0. The image already resolved dandi loosely on every no-cache rebuild, so a rebuild alone picks the fix up; the floor is what makes a build fail loudly instead of quietly resolving back to a dandi without it. Co-Authored-By: Claude Code 2.1.251 / Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GgF3exUHnXfZpZ76qwEqJL
CodyCBakerPhD
marked this pull request as ready for review
August 28, 2026 20:18
CodyCBakerPhD
commented
Aug 28, 2026
Signed-off-by: Cody Baker <51133164+CodyCBakerPhD@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
dispatch.pyruns every download with-e refresh, which skipped nothing at all on filesystems whose mtimes are coarser than sub-second (dandi/dandi-cli#1907). On the production runner that meant each pass re-fetched whole incoming dandisets rather than refreshing them.dandi/dandi-cli#1910 fixed it upstream, released in 0.78.0 on 2026-08-28.
dispatch/containers/dandi.Dockerfilealready resolveddandiloosely on every no-cache rebuild, so a rebuild alone picks the fix up. The floor is what makes a build fail loudly instead of quietly resolving back to a dandi without it.Merging republishes
ghcr.io/brain-bbqs/dandi-cli:latest, which is what the production runner pulls.Checked locally:
dandi>=0.78.0anddispatch/envs[test]resolve together with no conflicts,MTIME_TOLERANCEis present in the installeddandi/download.py, and all 59dispatch/testspass against that environment.Prompts
Generated by Claude Code