Laurent Demailly
Laurent Demailly
again 1.22.8
Just to point out in case it helps someone, that I had a build suddenly break out of the blue... (way past the deadline) and the fix was https://github.com/fortio/fortiotel/pull/254/commits/e5572ad176041f84c638d4a9a8a40b7011ca58b2 ie...
the above (go mod tidy removing the entry) is a problem because it means every dependabot PR fails... any idea what the correct fix is?
> @ldemailly can you give a small reproducer of this problem with a go.mod. Likely the solution is to bump some other out of date dependency. Thanks! yes: ```sh git...
turns out... it's the go.work or something related to the simple/ sub directory (btw trying to _ import didn't work because there is nothing at the top and even trying...
So in short, sorry for the noise yet maybe that oddity that a sub project go.mod can cause that issue might help someone else
well it's actually not fixed... go mod tidy in simple if they all use the same toolchain does remove it... thankfully that one isn't done by dependabot and rots but......
aforementioned PR is https://github.com/istio/istio/pull/1840
I agree the | "unknown" needed all over isn't right
IMO it's not similar because the compiler doesn't tell you you should catch said exception the default/least surprise (and smallest config input/least inconvenience to authors) is to have 1 or...