facebook/sapling
1
1
Fork 0
mirror of https://github.com/facebook/sapling.git synced 2024-08-16 22:10:29 +03:00
Code Issues Projects Releases Wiki Activity
A Scalable, User-Friendly Source Control System.
86,718 Commits 22 Branches 62 Tags 318 MiB
Rust 44.9%
Python 21%
C++ 10.4%
Perl 9.1%
TypeScript 7.2%
Other 7.2%
81e5df1336
Go to file
Saul Gutierrez 81e5df1336 config: prevent requires from the backing repo to affect symlinks and FilteredFS 
Summary:
If a new repo was to be cloned with symlinks disabled on Windows, this would make the repo have a wrong config for symlinks.
In order for symlinks to be enabled for a working copy, they have to be enabled both in the EdenFS config for that checkout as well as having them inabled in hg by having `windowssymlinks` in `.hg/requires`.
Having symlinks enabled **in only one of the two** can cause really wonky behavior.

Some users were reporting having issues with symlinks being partially enabled on their working copies. This was caused by the backing repo having `windowssymlinks` enabled on the backing repo, since the requires is copied from there into the newly cloned repo.

This diff makes changes to that, preventing copying the requires file into a new one for both symlinks and FilteredFS, since both can be affected by this kind of behavior.

Reviewed By: MichaelCuevas

Differential Revision: D52311410

fbshipit-source-id: bca76757f1b9b6f2cafd4e024b8eafc0735e7e89
2023-12-19 18:09:50 -08:00
.github/workflows push reviewstack.dev daily 2023-12-19 11:05:15 -08:00
addons Commit: remove unused "FoldOperation" 2023-12-19 15:37:53 -08:00
build getdeps: add --build-type option to build in Debug or RelWithDebInfo mode (#786) 2023-12-19 12:24:39 -08:00
ci oss: increase HOMEBREW_FAIL_LOG_LINES for macOS 2023-11-13 14:52:54 -08:00
CMake LMDBInodeCatalog + LMDBFileContentStore 2023-11-13 12:47:14 -08:00
common Remove hostcaps fb feature 2023-12-15 20:25:56 -08:00
configerator/structs/scm repo_client: move unbundle commit limit to config 2023-12-19 06:23:40 -08:00
eden config: prevent requires from the backing repo to affect symlinks and FilteredFS 2023-12-19 18:09:50 -08:00
website find replace rest of files in fbsource 2023-11-29 07:28:17 -08:00
.gitignore mononoke: add README.md and the missing pieces for supporting cargo (#13) 2020-02-13 00:12:36 -08:00
.projectid replace the old getdeps.py script with a build.sh script 2020-03-30 19:27:54 -07:00
build.bat fs: fix license header 2022-01-04 15:00:07 -08:00
build.sh fs: fix license header 2022-01-04 15:00:07 -08:00
clippy.toml clippy: prevent holding a span guard over an .await 2023-11-16 07:31:54 -08:00
CMakeLists.txt fix getdeps build on Windows 2023-07-25 15:24:16 -07:00
CODE_OF_CONDUCT.md Adopt Contributor Covenant 2019-08-29 23:23:31 -07:00
CONTRIBUTING.md fix CONTRIBUTING.md to reference main instead of master (#436) 2023-01-18 19:58:13 -08:00
LICENSE relicense to GPLv2 2019-06-19 17:02:45 -07:00
make-client.py fs: fix license header 2022-01-04 15:00:07 -08:00
README.md Fix spelling mistake (#677) 2023-07-25 12:33:29 -07:00
requirements_ubuntu.txt include oss installation instructions for ubuntu 2020-07-24 11:34:17 -07:00
rustfmt.toml rustfmt.toml: group_imports = StdExternalCrate 2022-08-06 12:33:42 -07:00
SAPLING_VERSION bump SAPLING_VERSION from 0.1 to 0.2 in preparation for the next release 2022-12-21 12:23:53 -08:00

README.md

Sapling SCM

Sapling SCM is a cross-platform, highly scalable, Git-compatible source control system.

It aims to provide both user-friendly and powerful interfaces for users, as well as extreme scalability to deal with repositories containing many millions of files and many millions of commits.

Using Sapling

To start using Sapling, see the Getting Started page for how to clone your existing Git repositories. Checkout the Overview for a peek at the various features. Coming from Git? Checkout the Git Cheat Sheet.

Sapling also comes with an Interactive Smartlog (ISL) web UI for seeing and interacting with your repository, as well as a VS Code integrated Interactive Smartlog.

The Sapling Ecosystem

Sapling SCM is comprised of three main components:

  • The Sapling client: The client-side sl command line and web interface for users to interact with Sapling SCM.
  • Mononoke: A highly scalable distributed source control server. (Not yet supported publicly.)
  • EdenFS: A virtual filesystem for efficiently checking out large repositories. (Not yet supported publicly.)

Sapling SCM's scalability goals are to ensure that all source control operations scale with the number of files in use by a developer, and not with the size of the repository itself. This enables fast, performant developer experiences even in massive repositories with millions of files and extremely long commit histories.

Sapling CLI

The Sapling CLI, sl, was originally based on Mercurial, and shares various aspects of the UI and features of Mercurial.

The CLI code can be found in the eden/scm subdirectory.

Mononoke

Mononoke is the server-side component of Sapling SCM.

While it is used in production within Meta, it currently does not build in an open source context and is not yet supported for external usage.

EdenFS

EdenFS is a virtual file system for managing Sapling checkouts.

While it is used in production within Meta, it currently does not build in an open source context and is not yet supported for external usage.

EdenFS speeds up operations in large repositories by only populating working directory files on demand, as they are accessed. This makes operations like checkout much faster, in exchange for a small performance hit when first accessing new files. This is quite beneficial in large repositories where developers often only work with a small subset of the repository at a time.

More detailed EdenFS design documentation can be found at eden/fs/docs/Overview.md.

Building the Sapling CLI

The Sapling CLI currently builds and runs on Linux, Mac, and Windows. It can be built by running make oss in the eden/scm directory and running the resulting sl executable.

Building the Sapling CLI requires Python 3.8, Rust, CMake, and OpenSSL for the main cli, and Node and Yarn for the ISL web UI.

License

See LICENSE.