New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ERROR:root:Attempt to get non-existent Item #24
Comments
This is very weird. It looks like it is failing to find the root directory. But this is provided directly by rmfuse/rmcl; it doesn't get this at all from the cloud API. Can you let me know your OS, Python version, FUSE version, and whether you're using pyfuse3 or llfuse? If you are able, can you try running the following script? It will try to print out all the items it can find in the cloud account. You can post the output here, if you are comfortable, or email it to me at my user name at gmail. It will contain document names; feel free to redact them if you like. The output will be in the form
The main thing I'm curious about is, do any documents have a name of empty string? (There should be exactly one, a "VirtualFolder".) Also, most of the id-strings should be UUIDs (~40 hexadecimal digits); the only two that aren't should be '' (empty string, corresponding to that same element as before) and 'trash'. If you see something unusual along these lines, you can just report it without listing the whole output, if you prefer. Here's the script. You should be able to run it from within the same environment that rmfuse runs. from pprint import pprint
import trio
from rmcl import api
async def list_items():
client = await api.get_client()
await client.update_items()
pprint(client.by_id)
trio.run(list_items) |
I just found and fixed two bugs. One of them, related to modification dates prior to 1970 was causing a sudden crash, which could be what you're seeing. The other won't fix a crash, but it does fix the debug output with the |
I'm running Arch Linux 😎
sure, output is bellow:
|
You've managed to get a document with a parent that doesn't exist. I don't know quite how, but I was able to reproduce the problem on my end. The new version of rmcl (0.4.2) contains a fix, so updating that should be all you need to do. I just pushed a commit that moves rmfuse up to this version, so updating rmfuse (from git) should also work. If this doesn't fix things, please reopen the issue. If it does, let me know and I'll release a new version of rmfuse. |
yes, it worked by updating rmcl to 0.4.2 thank you very much |
Today I tryed again to use rmfuse, but now I get a different error, see bellow.
Disclaimer: I used other unnoficial APIs before, so I might have an inconsistent reMarkable cloud. Yet, it works elsewhere.
output when trying to access the mounted cloud:
rmfuse -vvv /media/remarkable
output:The text was updated successfully, but these errors were encountered: