-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
--mode verify detects lots of unexpected diffs in metadata without server timestamp boost #49
Comments
@yarikoptic The error message seems pretty clear to me:
This is the Archive's fault for not updating the Dandiset's draft version's |
But it is |
@yarikoptic Based on the below script, there are only 6 Dandisets that have been unembargoed (000253, 000408, 000773, 000774, 000897, and 000935). Is the problem described in the original comment still an issue? #!/bin/bash
set -eu -o pipefail
dandiset_root=/mnt/backup/dandi/dandisets
cd "$dandiset_root"
for ds in 0*
do
embargo_status="$(git -C "$ds" config --file .datalad/config --default OPEN --get dandi.dandiset.embargo-status)"
if [ "$embargo_status" = OPEN ] \
&& git -C "$ds" log -S EMBARGOED -n1 -- .datalad/config | grep -q .
then echo "$ds"
fi
done |
@yarikoptic Ping. |
blocked by #56 ATM. Please just rerun that command with --verify whenever we do not have ongoing backup process running |
@yarikoptic This problem is still occurring, but seeing as it's affecting Dandisets that are still embargoed, the problem seems to be solely with Dandi Archive. I have filed dandi/dandi-archive#2002. |
After
I manually ran the
--mode verify
sweep and it errorred out quite loudly -- here is the trail pointing to the full logfrom which it looks like potentially unemabrgoing forgetting to reset the
modified
may be?The text was updated successfully, but these errors were encountered: