Oxen Tree
You can useoxen tree to view the current state of the merkle tree for a commit. This gives you a view of the metadata contained in the tree for each file and directory, as well as how many VNodes are present.
Oxen Node
oxen node can be used to inspect file and dir nodes in the merkle tree. This can be used to check whether nodes exist and have been created properly in the merkle tree. You can search for a node by hash or by path.
Concurrency
By default, oxen will use up to 8 threads for its parallelized operations (oxen add, oxen push, etc.). This can be configured via the OXEN_NUM_THREADS environment variable. If OXEN_NUM_THREADS is set, oxen will instead use that many threads, so long as they are available on the local machine.
HTTP Requests
When uploading or downloading data, if any files fail to transfer, oxen will wait and retry the request. By default, oxen will allow up to 10 retries before cancelling the operation. This can be configured via the enviornment variableNUM_HTTP_REQUESTS
Chunk Size
Under the hood, oxen groups files into small files and large files for more efficient transfer inoxen push, oxen workspace add, etc. Files are considered large if theyβre larger than AVG_CHUNK_SIZE, which is set to 10 MB by default. This can be configured via the AVG_CHUNK_SIZE environment variable
Debug Logs
The oxen codebase contains plenty of debug logs, which you can turn on with the RUST_LOG variable.info or warn for more restrictive debug logs