Releases: bokwoon95/wgo
Releases · bokwoon95/wgo
v0.6.3: Fix -stdin being blocked after a restart until Enter is pressed.
Closes #22. os.Stdin.Read() blocks until a newline `\n` is provided (due to the OS doing line-by-line buffering https://groups.google.com/g/golang-nuts/c/NvD-pOTASIk). Therefore, do not tie the lifecycle of a command with os.Stdin.Read(). Instead, read from os.Stdin continuously in a background goroutine and feed its data into the stdinPipe of whichever exec.Cmd is currently running.
v0.6.2
fix bug where we were unwatching everything but 256 files, instead of…
v0.6.1: make unwatching when we hit "too many open files" deterministic
Also clarify in the log message that it's the number of directories watched, not number of files watched. We don't actually know the number of files watched since we only add directories to the watcher. On kqueue (macOS) that translates to one file descriptor used per directory and one file decriptor used per file, while on inotify (Linux) only needs one file descriptor per directory (https://news.ycombinator.com/item?id=9063910).
v0.6.0
bump dependencies
v0.5.14: executing debug (#19)
useful to indicate what is being executed
v0.5.13
fix tests for commit 551751b
v0.5.12
-verbose: report parallel wgo command number
v0.5.11
fix readme
v0.5.10: properly drain the timer before use
this might have been the source of various race conditions I saw in the past 😩 references: https://www.reddit.com/r/golang/comments/1inw7nc/anyone_else_seeing_old_unit_tests_that_involve/ https://blogtitle.github.io/go-advanced-concurrency-patterns-part-2-timers/#time-newtimer
v0.5.9: remove t.Parallel() from problematic tests
Why did the test TestWgoCmd_Run/postpone_on fail once in GitHub Actions but run successfully when the job was re-triggered?? Why???? Remove parallelism from problematic tests in hopes it never happens again.