mirror of
https://github.com/facebook/sapling.git
synced 2024-10-09 16:31:02 +03:00
4f632c4e8b
Summary: This is the first diff that tries to make megarepo asynchronous methods idempotent - replaying the same reqeust twice shouldn't cause corruption on the server. At the moment this is not the case - if we have a runaway add_sync_target call, then in the end it moves a bookmark to a random place, even if there was another same successful add_sync_target call and a few others on top. add_sync_target should create a new bookmark, and if a bookmark already exists it's better to not move it to a random place. This diff does it, however it creates another problem - if a request was successful on mononoke side, but we failed to deliver the successful result to the client (e.g. network issues), then retrying this request would fail because bookmark already exists. This problem will be addressed in the next diff. Reviewed By: mojsarn Differential Revision: D29848378 fbshipit-source-id: 8a58e35c26b989a7cbd4d4ac4cbae1691f6e9246 |
||
|---|---|---|
| .. | ||
| fs | ||
| hg-server | ||
| integration | ||
| locale | ||
| mononoke | ||
| scm | ||
| test_support | ||
| test-data | ||
| .gitignore | ||
| Eden.project.toml | ||