* scoping out multi-binary stuff
* todo notes for pack/unpack [ci skip]
* new version of r in gh action
* created lib.rs and moved ffs main.rs bin. added bfs traversal of json structure.
* moved main.rs last commit. forgot to commit the removal
* added file creation for null,bool,num,str
* main.rs > ffs.rs to have ffs as executable
* error condition for already existing root dir and text files
* first cut at BFS with nodes
* unpack supports all 3 types now
* use config object for file name parsing, change from_args to from_ffs_args in ffs.rs
* fixed unpack configs
* added from_pack_args and some code to get the Value structure from a file
* added dep walkdir
* not working pack.rs
* remove dep walkdir
* almost working pack.rs
* pack works, but not too efficient
* change pack to return name and value so recursion can work without queue
* pack.rs similar to as_other_value now and works
* unpack and pack now have their own args parsers
* changed cli options for pack-unpack (unfinished)
* edited config to better support pack and unpack actions
* fixed unpacking into empty dir. only unpacking into unempty dir errors
* checked almost all error statuses
* fix no-xattr option for unpack
* prevent non-object/array from being unpacked
* fixed missing RUST_LOG warnings
* roundtrip tests for formats. since comments and formatting aren't preserved, unpack and pack twice
* fix pack: added --exact
* rm ERR_MSG tmp file in all tests. added all possible format conversion tests. edit to run_tests.sh to support new tests
* fix packunpack tests
* another update to test scripts
* unpack: don't remove dir if value is not map or list. pack: detect file type without xattr. started adapting more scripts to use unpack/pack
* changed user.type xattr for non-lists from 'map' to 'named'. converted 10 scripts
* added more scripts. fixed bug in infer_mount_relative fail()
* more tests, fix: original_name xattr only gets used if name is invalid
* more tests, missing 1 fail message in yaml_output test, changed pack list sorting to use file name instead of parsed integers to match ffs
* fixed tests for unpack/pack
* edit script formatting using quotes around vars, rm readonly for unpack
* pack: added back ignored file for lists and --no-xattr option in cli, added macos_noxattr_cleanup (not exactly the same as ffs test)
* Run `pack/`unpack` in macOS CI; factor out benchmarks (#63)
* added quiet inplace, umask test based on mode.sh
* added fail (un)pack for every call, fix missing n in fail msg for basic_object_exact
* fixed issues with adding fail conditions
* added (un)pack exit status tests
* added symlink support for pack
* symlinks mostly done. cleanup + efficiency checks needed
* added test for packing symlinks, added some comments for pack
* fix test4 for symlink test on linux
* see why test5 not working on linux
* actually print out the xattr
* fix: setting xattr on symlink doesn't work in linux :( making it macOS-specific
* impl --max-depth and --allow-symlink-escape. tests needed
* fix: macos links /var to /private/var so checking if symlinked path starts with mount errors. canonicalizing mount works.
* fix: wrong detected type map instead of named. add: symlink escape and maxdepth test.
* code cleanup, added test for symlink escape and maxdepth together, show warnings in config for pack/unpack not just errors
* simple changes for requests:
pack:122 add loop to error msg
debug! for received config in unpack & pack
f.write(s)? instead of write!
shadowed original_name
verb agreement in cli.rs
remove reserve for BTreeMap and now useless TODOs
* while let instead of queue.empty
* use auto instead of detect and check for auto and is_dir to resolve directory type
use .as_ref instead of .clone for accessing mount
remove non-symlinks from mapping
* resolve directory type always. warn for unknown path_type.
* warn when hitting broken symlinks.
* better warn message for broken symlink
* resolve repeated traversal of broken symlinks
store bool of whether link is broken in symlink mapping
checks symlinks a maximum of two times for broken links
* use struct instead of tuple in symlink map
for better naming and code clarity
* loosen criterion for determining directory type
directories get resolved as list if all files begin with an integer.
if a directory's user.type gets forcibly set to list without obeying
that property, all filenames that don't begin with an integer get put
to the end of the list, but are still sorted alphabetically.
* don't use regex to detect. just check first or first two chars manually.
continue to use regex for sorting because lexicographic sorting for files starting with -
means larger negative numbers go to the right
---------
Co-authored-by: Michael Greenberg <michael.greenberg@stevens.edu>
Lazy implementation is now the default. Use `--eager` to force ffs to construct the entire filesystem on startup.
NB that lazy loading is not the same as lazy parsing. There's still plenty of savings left on the table.
There is some unwelcome code duplication in saving to accommodate type-level jiggery pokery.
Update to fuser=0.9 (i.e., 0.9.1). Update websites, version numbers, etc. for new release.
Finally use `destroy` properly, got rid of the `Drop` impl for `FS`. Drop `AutoUnmount` which wasn't doing anything anyway.
Fixes and improvements to CI, docs, and logging.
Benchmarks, in two flavors: real-world benchmarks and synthetic microbenchmarks.
`--time` flag for benchmarking output on stderr.
Using R to generate pretty graphs. Some overhaul of build scripts and artifacts, with the hope of simplifying the release system.
@RaphaelWimmer reports in #42 an issue with nested mounts (which are just disallowed by FUSE and macFUSE), which we were handling poorly.
The solution is to check that mount2 worked correctly and report messages.
A new flag `--munge [rename|filter]` controls how a name munging will work.
Name munging only applies to fields named '.', '..', containing a NUL byte, or containing a forward slash '/'.
The `rename` option (the default) will change '.' to '_.' and '..' to '_..'; each NUL byte turns into '_NUL_' and each slash turns into '_SLASH_'.
This greatly simplified policy means that spaces and other special characters should work just fine in field names now.
Running `--new FILE.EXT` will:
- infer the output format form `EXT`
- use `FILE.EXT` as the output
- start with a single, empty, named directory (but allocate a bit more space)
In implementing this, I realized that introducing metadata (fad45bed4b) meant we no longer inferred types automatically. I added a type `Typ::Auto` and some inference code.
Save original names that don't work as filenames (e.g., `.` and `..`).
We restore these names as appropriate---if a file is `rename`d with the _same_ name, we leave it alone. But renames to fresh names destroy original names.
Resolves#29.
There is no way to create a file with such a name: the metadata is purely copied. There's a TODO note in the code to allow users to inspect and edit this metadata, but it's not worth exposing until somebody asks for it. (I mean, really, please don't use `.` or `:/` as a property name.)
Clearer ignored files, cleanup formatting in `fs`.
Add a test to make sure the various macOS flags do what they ought to. Astonishingly, tests pass on 10.13 _and_ whatever crazy shit they're on now.
Extended attributes in `user.type` track the type of files and directories. Users can update these to alter the metadata.
Loading files records types; serialization tries to use them (but will default to strings or bytes if it can't interpret the file appropriately).
In particular, it's now possible to convert between both kinds of directories (list and named).
This isn't a long term solution, because extended attributes have no real affordances---it's not obvious that they even exist, and even once you see `user.type`, it's obvious what it means or what values it has. #2 has other ideas about ways to represent and manipulate metadata.
All of this comes with a few new flags and some brittle file ignoring behavior (macOS will generate `._*` files to hold extended attributes on filesystems that don't support them). The man page is updated with detail on the data model, and now the manpage is part of the website proper.
