Fabian Meumertzheim

While possible, this would require non-trivial changes since `ics2gcal` currently relies on at least some Chrome-specific APIs, such as `chrome.identity`. I would certainly support whoever forks `ics2gcal` and makes it...

Is this still broken for you? Do you get more information if you click on the `{}` in the line starting with `background.js:343`? The referenced line 233 gets the active...

I haven't been able to keep up with the recent manifest changes myself, thank you very much for taking care of this! I will look into this now and do...

I verified that this issue is still present with https://github.com/bazelbuild/bazel/pull/20603. I dug further and think that this logic just doesn't work with the kind of relocation performed by `--incompatible_sandbox_hermetic_tmp`: https://github.com/aspect-build/gcc-toolchain/blob/e2a34698bd20c7a2f771586ddfcf504330b77a97/toolchain/wrapper.sh.tpl#L20-L25...

@pawsaw I closed it as not planned since it's more of a bug in the gcc toolchain that isn't part of Bazel. But it's still referenced by Bazel examples, so...

I have RBE support implemented [on a branch](https://github.com/fmeum/bazel/commits/unresolved-symlinks-rbe), which I can submit for review after https://github.com/bazelbuild/bazel/pull/15700 and https://github.com/bazelbuild/bazel/pull/15773. Specifically, the tests I added in https://github.com/bazelbuild/bazel/pull/15700 seems to indicate that everything...

@ismell `--experimental_allow_unresolved_symlinks` should just work with RBE with Bazel HEAD. The flag is planned to be flipped for Bazel 6. I don't think that support covers unresolved symlinks in tree...

I don't know, but I think @larsrc-google does.

FYI @Wyverald

> I’d feel more comfortable accepting just package_relative_label, because it seems this function doesn’t lead into parsing and concatenating the labels and is covered by a clear usecase. Other functions...