You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you start tailing the same file twice (by calling TailFile and supplying an identical filename), and are using the inotify backend, then only one of the Tail objects is notified when a line is appended to the file. Which one of the two objects gets notice is chosen at random, and the one which does then catches up on lines it has slept on in previous appends.
I would expect both of the objects to be notified at each append.
The text was updated successfully, but these errors were encountered:
It boils down to the two Tail instances internally receiving on the same channel here. I would like to fix this but first I am interested in input on whether the interface provided by watch.Watch, watch.Events, watch.RemoveWatch and friends can have a breaking change. I would expect that no, it can't.
If you start tailing the same file twice (by calling
TailFile
and supplying an identical filename), and are using the inotify backend, then only one of theTail
objects is notified when a line is appended to the file. Which one of the two objects gets notice is chosen at random, and the one which does then catches up on lines it has slept on in previous appends.I would expect both of the objects to be notified at each append.
The text was updated successfully, but these errors were encountered: