You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When writing many small files to a folder in wnfs, each new file creates a new nested history entry in the previous folder. This is not needed in my use case (as the files are actually history tracking CRDT records in and of them selves).
Problem
This creates an unnecessarily deep and complex nested DAG situation.
It even rendered my gotjoshua account completely useless.
Impact
I must say I find these template headers annoyingly overlapping and I do not enjoy attempting to comply.
Solution
my ideas:
inhibit history via a config option passed to wnfs add and/or publish
add a .historyignore file to any folder to permanently avoid history tracking for that specific folder
needs consideration about recursion
Describe alternatives you've considered
I tried deleting stuff, but of course its still in the history (and i guess the delete action also deepens the DAG)
The text was updated successfully, but these errors were encountered:
Summary
When writing many small files to a folder in wnfs, each new file creates a new nested history entry in the previous folder. This is not needed in my use case (as the files are actually history tracking CRDT records in and of them selves).
Problem
This creates an unnecessarily deep and complex nested DAG situation.
It even rendered my gotjoshua account completely useless.
Impact
I must say I find these template headers annoyingly overlapping and I do not enjoy attempting to comply.
Solution
my ideas:
Describe alternatives you've considered
I tried deleting stuff, but of course its still in the history (and i guess the delete action also deepens the DAG)
The text was updated successfully, but these errors were encountered: