Yeah, instantaneous motion data doesn't make much sense, but the continuous motion data file also doesn't work all the time. InfiniTime will stop sending motion data if you have Raise To Wake and…
Yeah, this one is going to be a bit more complicated. The FUSE library does have [an unmount function](0f728ba15b/fuse/mount_lin…
Could you perhaps elaborate on the problem you see?
Try this with something that returns data less commonly, such as battery. Every time cat tries to read from the file, it executes a…
In my opinion, "device" is unclear. I think it should be called "info" instead, that seems clearer.
This is not correct. If no content has been written, you should still create the file because the user might want to create a custom file using a command like touch.
Use os.MkdirAll here instead so that it creates parent directories, and handle the error (just return it).
Sorry it's taken me a while to respond. I wanted to test this PR but my PineTime wasn't booting. Now that I've gotten it to boot, I'll test this and get back to you.
The err can be several different kinds of errors, and FSError is just one of them. It's actually a type I made. You can see it here: https://gitea.arsenm.dev/Arsen6331/infinitime/src/commit/512…
These should be debug logs rather than info logs. Also, the message should be a bit more specific, something like "FUSE getattr". Same for all the similar logs.
This error needs to be handled, you can just return it in this case and update the code that calls this function to do the actual handling
These variables should go above BuildRootNode because it's using them and it would be more readable that way. Also, Go doesn't require semicolons, you can remove those.