Bernhard Kaindl

I've had this error even inside vscode, at least when using a venv. For this and the case when run outside of vscode, this `ìmport` appears to help (yes, the...

> I kinda wish i could enable auto deleting bad chunks to prevent this. It really sucks that this causes prometheus to just not be able to run. Bogs about...

Agreed, getting uftrace updated in debian should be the next priority. To get the ball rolling, I've taken thepaul's commit history for the debian subdirectory from his repo, rebased it...

These are the last words from `strace -f`, the subprocesses are calls to `/bin/echo`, the program is an automatic conversion of the original *TCL*(sigh) script into an ELF exectuable to...

When built by `npm install -g` and then installed by `pm2 install --tarball ...` or `pm2 start exporter.js`, current HEAD works on: ```py node -v v14.19.3 pm2 -V 5.2.0 ```

> As an aside, I noticed that this repository lists 1.0.47, but https://www.npmjs.com/package/pm2-metrics only lists 1.0.43. Yes, `pm2 install pm2-metrics` installs 1.0.43 and it does not work with pm2 5.2.0....

Sample g++ call from the verbose build output (this is from Intel CascadeLake system using spack's [email protected]. which PASSed the test) > ...spack/lib/spack/env/gcc/g++ -DASTER_ARCH=64 -DCASTEM_UNIX_TYPE=UNIX64 -DCYRANO_ARCH=64 -DHAVE_ABAQUS=1 -DHAVE_ANSYS=1 -DHAVE_ASTER=1 -DHAVE_CALCULIX=1...

@thelfer - An Update * On an Intel CasadeLake, when using `[email protected]` built by spack with `spack install -v spack install [email protected];spack load gcc;spack compiler find`, the test passes: `Test...

@thelfer I suspect the AMD EPYC Rome(Zen2) might play a role in this riddle. Running a few more builds: So far, the AMD Rome/Zen2 in the only Server producing fails...

In case this testcase uses/exercises `numpy`, it could have to do with a possible remaining gcc-11 issue. It *should* be fixed with `gcc-11.2` (which still fails when used on the...