-
Notifications
You must be signed in to change notification settings - Fork 63
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
BUG: neptune sync is not fault-tolerant #1224
Comments
Hey @cemde Could you try updating to the lastest release and let me know if the issue persists? |
@Blaizzy still exists |
That's odd. Has it worked in the past? |
I never noticed it before, but I also never logged from inside a docker image. The objects2sync = [obj1,obj2,....]
failed_objs = []
for obj in tqdm(objects2sync):
try:
sync_object(obj)
except:
failed_objs.append(obj._id, obj_short_id, inspect.traceback())
print("Successful:", objects2sync - failed_objs)
print("Failed:", failed_objs)) |
Let me check with the team and come back to you |
Hey @cemde I've discussed it with the team and decided to send your issue to our product team as a feature request. They will take it from here and explore how to incorporate it into our future plans. While I don't have an ETA for this feature, I do want to keep you in the loop. Thanks for sharing your feedback! Really appreciate it :) |
Describe the bug
When errors occur with a single run during
neptune sync
, the scipt stops, but it should skip it and print the error.Reproduction
Works for other kinds of file corruptions as well.
Expected behavior
When neptune encounters a run it cant sync, it should skip it, continue with the next and at the end list all runs it couldnt sync.
Traceback
Neptune Version
The text was updated successfully, but these errors were encountered: