mirror of
https://github.com/facebook/sapling.git
synced 2024-10-12 09:48:05 +03:00
a3cee67af5
Summary: These last 2 errors are still considered fatal, but shouldn't be and are most likely transient. Failing to open a packfile that was successfully opened before can for instance happen when the file is removed by another process, or if it somehow become corrupted. Failing the removal of the pack-file should no longer be an issue, but if it fails, we can also ignore it with the reasoning that the next repack will take care of it. Reviewed By: sfilipco Differential Revision: D14441288 fbshipit-source-id: 6c2758c2a88fd5d2d83b55defe3d263ee9f974a1 |
||
|---|---|---|
| .. | ||
| argparse | ||
| asyncpacks/src | ||
| bookmarkstore | ||
| cdatapack | ||
| clib | ||
| commitcloudsubscriber | ||
| configparser | ||
| cpython-ext | ||
| cpython-failure | ||
| edenapi | ||
| encoding | ||
| hg_watchman_client | ||
| hgpython | ||
| indexedlog | ||
| linelog | ||
| lz4-pyframe | ||
| manifest | ||
| minibench | ||
| mpatch | ||
| mpatch-sys | ||
| mutationstore | ||
| nodemap | ||
| pathmatcher | ||
| radixbuf | ||
| revisionstore | ||
| third-party | ||
| treestate | ||
| types | ||
| url-ext | ||
| vlqencoding | ||
| watchman_client | ||
| zstdelta | ||
| Cargo.toml | ||
| README.md | ||
lib
Any native code (C/C++/Rust) that Mercurial (either core or extensions)
depends on should go here. Python code, or native code that depends on
Python code (e.g. #include <Python.h> or use cpython) is disallowed.
As we start to convert more of Mercurial into Rust, and write new paths entrirely in native code, we'll want to limit our dependency on Python, which is why this barrier exists.
See also hgext/extlib/README.md, mercurial/cext/README.mb.
How do I choose between lib and extlib (and cext)?
If your code is native and doesn't depend on Python (awesome!), it goes here.
Otherwise, put it in hgext/extlib (if it's only used by extensions) or
mercurial/cext (if it's used by extensions or core).