Alexei Mikhailov

@hulkish it's using nodejs streams to write out instead of console, and streams are non-blocking by nature (so the process doesn't need to wait for the log message to be...

Fwiw I'm getting pretty similar error, except message starts with `Request textDocument/documentHighlight failed` (and the same filtering fix config for noice works as expected).

@faho sorry about that, something wonky must've happened with my previous commit. But, as also mentioned in the PR description, I'm fine with deleting the file altogether.

> Probably this can be replaced with `exercism completion fish | source`? Hm, if that's what other competion scripts here doing as well (haven't checked) -- then yea, sounds reasonable!...

@cole-h this is how it looks for me (with same error happening, albeit still on Sonoma): ``` launchctl print system/systems.determinate.nix-installer.nix-hook ``` ``` system/systems.determinate.nix-installer.nix-hook = { active count = 0 path...

I actually got it fixed by reboot 😅 And now that I tried uninstalling / reinstalling nix a couple of times, I don't seem to get that problem anymore.

Seems like this happened as part of https://github.com/redis/node-redis/pull/2852

It seems to me that `isoWeek` mixes up utc dates and local dates 🤔 ``` > dayjs(new Date('2025-10-05T20:00:00Z')).isoWeek() 40 > dayjs(new Date('2025-10-05T21:00:00Z')).isoWeek() 41 > new Date() 2025-06-05T06:59:32.740Z > new Date().toString()...

Ah, right, I wasn't aware that [there is explicit `dayjs.utc`](https://day.js.org/docs/en/plugin/utc) (somewhat akin to moment, should've known 😅); So these work as expected: ``` > dayjs.utc(new Date('2025-10-05T21:00:00Z')).isoWeek() 40 > dayjs.utc(new Date('2025-10-05T20:00:00Z')).isoWeek()...