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.

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

Reporting versioning-related errors #132

Open
michielbdejong opened this issue Dec 4, 2023 · 0 comments
Open

Reporting versioning-related errors #132

michielbdejong opened this issue Dec 4, 2023 · 0 comments

Comments

@michielbdejong
Copy link
Contributor

Section 3.5 says:

If a server has dropped the history that a client requests, the
server can return a 410 GONE response, to tell the client "sorry, I
don't have the history necessary to synchronize with you."

But if the server really dropped the history, then how would it know if the parent 1234567 a client is referring to is really 'gone' or maybe this version ID never was a part of this DAG to begin with?

I think the idea of Braid is that updates and merges never fail, right? So the merge algorithm should guarantee this? That does make it a lot easier than git push, which might for instance result in 'push rejected, please pull and rebase and try again'.

But even then, I could think of a number of useful versioning-related error codes, such as 'version not found', 'parent not found', 'merge algorithm not supported', 'merge failed'.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant