Paul Draper

> The latter is especially worrisome, because it’s unclear how Yarn PnP and typescript-go will coexist. It would be unfortunate if developers had to abandon one technology to use the...

Yikes, I just ran into this with https://github.com/StreakYC/react-draggable-list/issues/67 It made it impossible to extract the tarball on Linux (without some extra funkiness at least).

`outputs` is deprecated (EDIT: #7977)

It doesn't work with --incompatible_no_rule_outputs_param . AFAIK no one creates such a flag unless they intend to remove the feature in a future (breaking) release. https://docs.bazel.build/versions/master/backward-compatibility.html

> The inability to get this simple fixed merged is quite depressing. It makes me question the health of terraform-cdk going forward. Thanks for your efforts 🫡

Same. `overwrite: true` doesn't prevent conflict from happening. It seems to be non-deterministic; a re-run fixes it. --- My money is on read-modify-write. Will we ever improve?

> My money is on read-modify-write > Will we ever improve? https://github.com/actions/upload-artifact/blob/552bf3722c16e81001aea7db72d8cedf64eb5f68/src/upload/upload-artifact.ts#L11 Though FWIW, I don't think this is sole source of the problem. I suspect`@actions/artifact`.

> (I realise the name of the flag is misleading, but it is what it is sweat_smile) But ideally, the flag would actual disable caching? No point in writing to...

> can we disable all cache usage? ---- >> Is there any way to disable creating the cache entirely? > Not at the moment

This seems like a bad proposal. Better to have explicit difference between Bazel Watcher options and Bazel options.