Bug: menubar app has to be restarted to get current data

[rdouma]

I had it running fine since yesterday's fix of #273. In the morning it crossed over to a new day and seemed to work fine at first and went to sleep. Computer stays on, screens off. After getting back to my computer today I noticed the data was not updating, even though it should. Refresh button was grayed out. I quit and restarted and it came back with updated information.

[iamtoruk]

Thanks for the detailed report -- this matches what we've been tracking.

The root cause was the pipe I/O layer using a blocking read that couldn't be cancelled after sleep/wake. The child process would exit, but the read handle stayed pinned, leaving the loading state stuck permanently.

We've pushed a fix on fix/menubar-loading-watchdog that replaces the blocking drain with non-blocking POSIX I/O, adds proper signal handling (EINTR from child exit), and a 60-second watchdog as a safety net. If you want to try it before we merge:

git clone https://github.com/getagentseal/codeburn.git
cd codeburn
git checkout fix/menubar-loading-watchdog
cd mac
swift build -c release

Then copy .build/release/CodeBurnMenubar into ~/Applications/CodeBurnMenubar.app/Contents/MacOS/ and relaunch.

We're testing it for a day on our end. If everything holds up, it'll ship in the next release.

[rdouma]

Ok, running that, I'll keep an eye open for weird behavior and report back if I see anything.

[rdouma]

And thanks for the quick fixes!!

[rdouma]

After coming back to my computer today, it was stuck again. Quitting and restarting works to show new data.

[iamtoruk]

Same on my side, but I have provided another fix this morning and tested it, and it seems to be working. Repackaged it to Mac 0.9.7 you can use that with --force