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.
This function should be called startFUSE instead to adhere to Go naming conventions
Thanks for your PR. There are some changes I'd like, mostly readability improvements.
I've had a closer look at your fork. It looks good. The only thing I'd say should be changed is that the fuse.go file should only contain the startFuse function (which should be called…
Assuming the fuse library you're using doesn't link libfuse, I think this is a great idea. I don't think it does, but it doesn't explicitly state that anywhere. The easiest way to check is to…
It's not much overhead, it's less than 10 MB, and takes almost no work to install, but I can make an AUR package if you prefer.
Interesting. That shouldn't be possible. The bot keeps track of which posts/comments have been replied to and shouldn't reply to them again. Did the post ID change when Lemmy was updated? That…
I'm going to close this due to inactivity and because there's nothing obvious that I can do about this. If you're still having this problem and think it's due to ITD, please re-open the issue or…
The problem is that both archive and filesystem files are handled by the exact same code, so there shouldn't be any discrepancies in the actual bluetooth data as long as the data being read is the…
Actually, I guess there isn't much more to capture.
$ ./itctl notify one two 10:00PM FTL Error while running app error="not connected"And the output of itd has…