mirror of
https://github.com/facebook/sapling.git
synced 2024-10-11 01:07:15 +03:00
1fac9783e3
Summary: This is really a continuation of D13479516; the issue is that the osxfuse kernel module is very eager to recycle `unique` request id values, recycling them before our code has had a chance to update internal state. This diff re-keys the requests map so that we generate our own sequence of identifiers to use as the key rather than the fuse protocol `unique` value. Because we cannot reliably track by `unique` value we also cannot reliably implement interrupt support. We've never really tested interrupt support, and it relies on functionality in folly futures that hasn't really been tested or proven either, so I've removed that functionality as part of this diff. That allows simplifying some code in RequestData and FuseChannel; we're now able to simply tack an `.ensure` on the end of the future chain to ensure that we remove the entry from the map once the future is resolved, successfully or otherwise. Reviewed By: chadaustin Differential Revision: D13679964 fbshipit-source-id: c1081a868c4061de2a725589ec1614959a8e9316 |
||
|---|---|---|
| .. | ||
| benchmarks | ||
| cli | ||
| docs | ||
| fs | ||
| integration | ||
| py | ||
| scripts | ||
| test_support | ||
| test-data | ||
| third-party | ||
| win | ||
| .pyre_configuration.local | ||
| Eden.project.toml | ||