Closed ipovalyaev closed 7 months ago
Applied some fancy hack -
modified base.py to False
.
After this hack and push-from-original-dir, pull-from-new-one, seems issue has gone.
I may suspect digital ocean doesn't properly supports traverse, but can't confirm it for 100%. If this would be the case - would be nice to add option to avoid traverse on particular storage and add note in documentation, where it refers to digital ocean as aws compatible.
NB (not relevant to the issue, but maybe worth mentioning in doc?) :
Seems digital ocean is not 100% stable, but setting dvc remote modify digital_ocean connect_timeout 600
helped to rectify errors like
ERROR: failed to transfer 'md5: cd508e4b837c3c968372b679fd49f1ee' - Could not connect to the endpoint URL: "https://lacmus-dvc.fra1.digitaloceanspaces.com/dvc/cd/508e4b837c3c968372b679fd49f1ee"
@ipovalyaev Thanks for your reports as well as the analysis on the digital ocean.
Update: without aforementioned patch even dvc pull
is failing on new installation, so it makes pull not working for anyone, the issue impact not only those, who pushed.
This could be regression of s3 issue https://github.com/iterative/dvc/issues/6691 in previous version
2022-01-27 10:31:04,000 DEBUG: Querying 10 hashes via object_exists
2022-01-27 10:31:04,176 DEBUG: Querying 0 hashes via object_exists
2022-01-27 10:31:04,283 DEBUG: Estimated remote size: 4096 files
2022-01-27 10:31:04,284 DEBUG: Querying '6' hashes via traverse
2022-01-27 10:31:04,331 WARNING: Some of the cache files do not exist neither locally nor on remote. Missing cache files:
name: weights/keras-retinanet/resnet50_liza_alert_prod.h5, md5: 0e0d5fa91b6b8f14a500c5ffc6eab70a
name: weights/yolo5/yolo5_fullDS_TF.pb, md5: 049171ca83a35de90b250967a6da45f8
name: weights/yolo5/yolo5_fullDS_native.pt, md5: 5400e4d2a34d59b0deb9d7a1030decc8
name: weights/torch/pretrain/resnet50_SDD.pth, md5: 62d8d0def79df800be81831325a62ea6
name: weights/torch/experimental/resnet50_FRCNN_LADD_epoch_9.pth, md5: dfec2c7f61ef2752b0270c36a5601ac5
name: weights/torch/experimental/resnet50_FRCNN_SDD_epoch_9.pth, md5: f5887fdc93f17e1f4c2b204896b280dc
Description
Some of the files are not being pushed to aws s3 compatible storage (spaces at digital ocean). No any error is displayed, but actual push doesn't happen. I didn't find any useful information how to check if my files are actually in the bucket and how can I find those :( Or any other ways to find out what going on under the cover (except studying the source code in repo, which I didn't got to)
Reproduce
I have a local remote, but want to share files with others over digital ocean bucket
Cache and remote 'local_remote' are in sync
)(tried to clean bucket, set dvc remote modify digital_ocean listobjects true, but this didn't changed anything)
Some files didn't got there
Attempt to fetch those files from other machine, or different folder on other machine with
gives
Expected
All files are pushed and available for pull
Environment information