oliverpool

I am facing the same issue. Just building the latest https://github.com/ZigEmbeddedGroup/microchip-atmega fails as well: https://github.com/ZigEmbeddedGroup/microchip-atmega/issues/25 Did you find a workaround?

My 2 cents: call it `gokrazy.WaitForClockAndNetwork`, so that it can be used for https requests (if the clock is wrong, the certificate verification should fail).

In my case I had to add `.default`: ```js /** @param { import("@11ty/eleventy/src/UserConfig.js").default } eleventyConfig */ export default function (eleventyConfig) { ```

~~As a workaround, `Allow0RTT` can be disabled:~~ Edit: the data-race still happens with 0-RTT disabled. The stacktrace is like the one in #4228. Sorry for the unrelated noise.

Affected as well (I initially thought it was a data race like #4303 - however even when disabling 0-RTT, the data race appears sometime). > as it just masks the...

> What system are you running on? Arch Linux. Investigating a bit more, the GSOError happens at the first GSO packet (which is the 7th). The first 6 packets have...

For anyone impacted, add the following line at the bottom of `go.mod` in the meantime: ``` replace github.com/imdario/mergo => dario.cat/mergo v1.0.0 ```

The v0.31.0 release fixes this specific issue: https://codeberg.org/forgejo/forgejo/pulls/3778 Thanks!

Having a more recent tag would also help with Go 1.22: #3070 (different problem, but I guess the tag would solve both issues)

@jdeniau thank you for your investigation! I am now using the following setting to force the extension to use the php-cs-fixer of my project: ``` ${workspaceFolder}/vendor/bin/php-cs-fixer ```