client.remove() produces non-existing node errors about remotestorage.js

[raucao]

Before investigating this, just a note:

This could be an edge case with the default caching strategy (caching is enabled with the SEEN strategy by default) and node.js usage, which uses in-memory caching and where the cache is lost between restarts.

See https://remotestoragejs.readthedocs.io/en/latest/js-api/caching.html for details about caching.

However, it is still a bug, of course, because it should fetch metadata of the remote document again in this case, and delete it upon seeing it's there, before claiming that the document does not exist at all.

[raucao]

@bdashore3 Is this still a problem for you? If so, could you provide a more complete version of the failing code, so we can reproduce the error?