Jérôme

@YellowOnion I'm curious to know what triggered closing this issue. I haven't been following the project as much lately.

You can enforce the same thing by using MANAGER_PORT=8080 and adding --cap-drop ALL That way, you don't depend on the Dockerfile to do the right thing.

This does not seem to happen when all clients are using Websockets instead of BOSH, however, changing status on other resources will affect all ConverseJS ressources.

This also happens quite often to me. Usually minutes after doing subvolume operations or writing to multiple subvolumes in quick successions. I just can't tell the exact trigger and have...

On Windows, it appears as an inline file with the following dates:  On Linux: ``` # stat app.info File: app.info Size: 31 Blocks: 8 IO Block: 4096 regular...

I also noticed that it doesn't happen to be the same file every time a send/receive operation is attempted. ``` At subvol Snapshot of Beat Saber (2022-06-07) ERROR: utimes o269-150798-0/142e6...

This seems to be a WinMD issue. WinBtrfs handles neither NTFS nor MD arrays.

This project is WinBtrfs, to handle Btrfs formatted volumes. Not related to NTFS.

There's a serious lack of information in this issue.

> Is this a beta version? Microsoft have been known to break things like this in the betas, only for them to be fixed by the time the proper release...