This happened with ssh but I suspect it will happen with any provider as I believe the issue is death in the API.
If you open a file locally and then execute a :w protocol://host///path it will appear to succeed (or at least not appear to fail) but it will actually end up truncating the file remotely. Which is... Cool
Quick check shows this happens in both ssh and docker, so this is likely an issue with how the API is handling the data is is giving to the underlying provider
This happened with ssh but I suspect it will happen with any provider as I believe the issue is death in the API.
If you open a file locally and then execute a
:w protocol://host///path
it will appear to succeed (or at least not appear to fail) but it will actually end up truncating the file remotely. Which is... Cool