Skip to content
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.

Sign up for GitHub

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

Jump to bottom

(pre) push should check for new revisions #3

Open
gaak99 opened this issue Nov 15, 2016 · 1 comment
Open

(pre) push should check for new revisions #3

gaak99 opened this issue Nov 15, 2016 · 1 comment
Assignees
@gaak99

Comments

@gaak99
Copy link
Owner

gaak99 commented Nov 15, 2016

The user should be warned if a new revision was saved on Dropbox before a push is done.
@gaak99 gaak99 self-assigned this Nov 15, 2016
@gaak99
Copy link
Owner Author

gaak99 commented Sep 14, 2018 •
edited
Loading

Stepping back a bit ...

The current code has data races galore -- was not orig designed to be robust if mult users at once -- but if we now can make it so would be nice...

Would be xtra nice if we had a way (api, lock file? aka file.lck) to upload the new version and update ancdb atomically -- but only if here there we're no changes to data file or ancdb since we last fetched it. If it detects a change then it errors out.

In lieu of that, we should probably replace one big ancdb with a file.anc per data file --
thus limit the collisions if working with mult files.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gaak99 gaak99

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gaak99