Skip to content
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

include node name in error when traversing fails #2

Merged
merged 1 commit into from
Apr 1, 2016

Conversation

mnagel
Copy link

@mnagel mnagel commented Mar 31, 2016

I use Syncthing to recursively watch my whole $HOME.
It fails on the FUSE mount .gvfs and this took me muuuch to long to figure out.
With this change it is much more easy to debug such issues.

I use Syncthing to recursively watch my whole `$HOME`.
It fails on the FUSE mount `.gvfs` and this took me *muuuch* to long to figure out.
With this change it is much more easy to debug such issues.
mnagel added a commit to mnagel/syncthing-inotify that referenced this pull request Mar 31, 2016
the logging lacked the information which was the problematic folder id
even though the information is send to the syncthing process.
in combination with an upstream fix in notify ( Zillode/notify#2 )
this will make debugging failures much easier as folder id and the failing node (i.e. path)
will be part of the error message.
@Zillode Zillode merged commit b167a65 into Zillode:master Apr 1, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants