sapling/eden/scm/lib/vfs/Cargo.toml

[package]
name = "vfs"
version = "0.0.1"
edition = "2018"

[dependencies]
anyhow = "1"
chashmap = "2.2"
fsinfo = { path = "../fsinfo" }
libc = "0.2"
minibytes = { path = "../minibytes" }
types = { path = "../types"}
util = { path = "../util" }

[dev-dependencies]
tempfile = "3.0"
vfs: move vfs logic into its own crate Summary: This logic will be used in a variety of places (update workers, status, etc). Let's move it somewhere common. Reviewed By: xavierd Differential Revision: D20771623 fbshipit-source-id: b4de7c1d20055a10bbc1143d44c55ea1045ec62a 2020-04-23 05:51:58 +03:00			`[package]`
			`name = "vfs"`
			`version = "0.0.1"`
			`edition = "2018"`

			`[dependencies]`
			`anyhow = "1"`
vfs: make audit cache concurrent Reviewed By: quark-zju Differential Revision: D26233458 fbshipit-source-id: e06f5642f713d0788407e3cc70655ef82261e7c2 2021-02-05 00:11:16 +03:00			`chashmap = "2.2"`
vfs: move vfs logic into its own crate Summary: This logic will be used in a variety of places (update workers, status, etc). Let's move it somewhere common. Reviewed By: xavierd Differential Revision: D20771623 fbshipit-source-id: b4de7c1d20055a10bbc1143d44c55ea1045ec62a 2020-04-23 05:51:58 +03:00			`fsinfo = { path = "../fsinfo" }`
vfs: do not follow symlink when overwriting Summary: Before this diff VFS::write_regular did not handle correctly use case when file already existed as as symlink - it would write into symlink location, instead of replacing symlink with a regular file (see updated test_symlink_overwrite that is failing on old implementation) This diff adds O_NOFOLLOW option on unix when overwriting the file. When destination is a symlink, attempt to write fails with E_LOOP and triggers clear_conflict that removes symlink and allows retry write to succeed. This also allows one of test cases in checkout that previously did not work Reviewed By: quark-zju Differential Revision: D26378893 fbshipit-source-id: 28bcdaba78db283ac7a25bb232c198d3d8f73e5d 2021-02-12 06:08:30 +03:00			`libc = "0.2"`
lib: bytes::Bytes -> minibytes::Bytes Summary: The `bytes` crate still does not support zero-copy on mmaped buffer. Switch to `minibytes::Bytes` so bytes returned from our main storage backend indexedlog is a zero-copy slice backed by a mmap buffer. Migrate vfs, revisionstore, pyworker to minibytes so they can preserve zero-copy mmap buffers from indexedlog. The edenapi/types is unchanged, since it's also used in Mononoke which uses `bytes::Bytes` all the places. The conversion to `minibytes::Bytes` is cheap so it's probably not a performance issue. Reviewed By: kulshrax Differential Revision: D26218289 fbshipit-source-id: e4f1c631143b7676c6b48d3b4f97055299bfd334 2021-02-04 07:19:27 +03:00			`minibytes = { path = "../minibytes" }`
vfs: move vfs logic into its own crate Summary: This logic will be used in a variety of places (update workers, status, etc). Let's move it somewhere common. Reviewed By: xavierd Differential Revision: D20771623 fbshipit-source-id: b4de7c1d20055a10bbc1143d44c55ea1045ec62a 2020-04-23 05:51:58 +03:00			`types = { path = "../types"}`
			`util = { path = "../util" }`

			`[dev-dependencies]`
			`tempfile = "3.0"`