phlax

@yaroslavros the currently supported llvm version is 14 - we are trying to update this but there are a bunch of issues that will need to be addressed before we...

i would check on @adisuissa 's suggestion first the issue is related to gcc (cf https://www.spinics.net/lists/libreoffice/msg08609.html) i would recommend using llvm via `ci/run_envoy_docker.sh` to ensure you have the correct version

> I don't know why this failure ... it has increased the cache size, and now its running out of (tmpfs) space to load the cache

yeah - i think lets update to latest

@nnewton unfortunately this is correct - there is a ci issue with diskspace that i didnt figure out a solution for yet

hi yeah - help would be hugely appreciated - but i think i probably will need to help even in that case - the repo is here https://github.com/envoyproxy/apt the problem...

i think this is more/less correct - altho the current issue with publishing is netlify - i think github runners can probably work using GCP - esp with fuse sounds...

> Would it help if I were to create a draft PR to install and configure GCS Fuse? so, as mentioned above, i think getting this working in a more...

so @kindlehl im not sure how much gcsfuse will help - from initial testing the main issue im hitting is that it requires a directory-like structure - this then takes...

cc @ggreenway