Gunnar Wagenknecht

Same. See here: https://github.com/utmapp/UTM/issues/6003#issuecomment-3508864232 Might be duplicate issue.

I am hitting a similar (the same?) issue linking protobuf 33.1 in Bazel. ``` ld.lld: error: undefined symbol: __stop_linkarr_upb_AllExts >>> referenced by extension_registry.c >>> extension_registry.o:(upb_ExtensionRegistry_AddAllLinkedExtensions) in archive bazel-out/aarch64-opt-exec-ST-12dfad941fb6/bin/external/protobuf+/upb/mini_table/libmini_table.a >>> referenced...

I am seeing the same in my build but not for all cache actions. It doesn't fail the build, though. Is this something I need to address? Is the content...

@lonhutt can you check if this is ok to merge?

I think the discussion is stuck because of a fundamental design choice, which is controversial by itself: Looking at these statements: > Unconditionally picking the Bazel module at least ensures...

Go has the additional complexity that it doesn't distribute as consumable output but source code, which must be compiled. That's a fair point and already causes confusion by itself (should...

I can confirm that there is an issue. I think it's worse than what is described here. What I observer is that - quite frequently - the `Next Alarm` switches...