dat-ecosystem
Empty folders seem to be ignored
If I create an empty folder in an existing dat, it won't get synced to a client. According to @mafintosh this is a dat issue as hyperdrive supports empty folders.
Oh wow I read this as hidden folders not empty folders. Ignore me.
~This is a "feature" not a bug =). You can pass the --no-ignoreHidden option to import hidden folders. I need to alias that to a nicer option.~
~How can we do a better job of documenting this?~
Thanks for the explanation. I'm not sure I like this behavior but it's not really too much important. As soon as bidirectional syncing becomes reality, I think this behavior becomes a little awkward though. Folders give structured access so even an empty folder has meaning.
I can't for the life of me clone empty files and am wondering if that is related to this issue.
Am I correct that empty files appear to be shared and also appear to be cloned as far as the UI, but they are not written out after a clone? That is, it says it is "Sharing: X files" and "Cloning X files" where X includes the empty files, but they aren't appearing in the local filesystem. I can't find any other discussion of this, which also makes me nervous to file a separate issue.
datbase shows the empty files that I cannot otherwise clone, but not the empty directories. however, interestingly, datbase does not show a directory that contains an empty file when it exists within anything other than the root path. That is, I can see empty files in root, in subdirectories of root, but not subsubdirectories of root.
I cannot clone any empty files nor directories containing only empty files.
Hmm, yes that may be a separate issue. But if its showing up on Datbase, it seems like it'd in the metadata - we may just have to fix it in dat-storage (which datbase does not use).
Can you run dat log <key>|<dir> on your dat to see if the empty files appear there? If they do appear there, then it may be the same issue with dat-storage.