summaryrefslogtreecommitdiff
path: root/doc/bugs/Error_writing_log_message_when_filename_contains_Unicode_chars/comment_2_1be17780fd4244053c504383ad56969b._comment
blob: fabe85a3ae7e3782a8be40a5a4e8b93921cad116 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
[[!comment format=mdwn
 username="joey"
 subject="""comment 2"""
 date="2015-08-03T14:33:38Z"
 content="""
I was able to reproduce this, but only once I started the assistant with
LANG=C. I suspect that the bug reporter's locale in the shell is not
the locale the assistant was started with.

(Also, I included the French quotes in the filename, which wasn't very
clear in the bug report.)

The failure to output a debug message is not actually fatal. The file
still gets added and committed if it exists when the assistant starts up,
despite this "error". What actually seems to be failing is the
inotify code. Creating the file while the assistant is running with LANG=C
results in no inotify event being received for it. AFAICS, the
inotify library is falling over on the filename, before git-annex ever gets
to see the file.

Hmm, it looks like the inotify library is generating events with
filenames that have high bit characters stripped out when run in the C
locale! So, git-annex gets an event for a file that's not present, and
ignores it. This sure seems like a bug in the inotify library to me. Bug
filed: <https://github.com/kolmodin/hinotify/issues/13>. 
"""]]