Afri

> Do you happen to have `debug:` logs with this too? Debug logs seem to be useless here. ``` ~/lodestar tags/v1.21.0* user@franz ❯ ./lodestar validator --network mainnet --logLevel trace Sep-10...

Running lodestar through node directly without args says "illegal hardware instruction" ``` ~/lodestar tags/v1.21.0* user@franz ❯ node ./packages/cli/bin/lodestar.js validator Sep-10 13:27:00.060[] info: Lodestar network=mainnet, version=v1.21.0/ae1f9d5, commit=ae1f9d5d8896cf8e5e1dc42cfeea5fbb4b69e99a Sep-10 13:27:00.063[] info: Connecting...

Core dump: ``` PID: 4566 (node) UID: 1000 (user) GID: 984 (users) Signal: 4 (ILL) Timestamp: Tue 2024-09-10 13:27:00 CEST (5min ago) Command Line: node ./packages/cli/bin/lodestar.js validator Executable: /home/user/.nvm/versions/node/v20.17.0/bin/node Control...

Looks like a blst wrapper issue (or blst itself?)

Just to be sane I did remove everything and built a fresh lodestar on both the affected machine and my workstation. I can confirm that this can not be reproduced...

@matthewkeil this build from branch `mkeil/afri-debug` does not crash at signal 4. You fixed it 😛

Yes, I always maintain a Rust toolchain. The OS is Archlinux, by the way.

``` ~/lodestar-debug unstable user@irena ❯ rustc --version rustc 1.81.0 (eeb90cda1 2024-09-04) ~/lodestar-debug unstable user@irena ❯ rustc --print cfg debug_assertions panic="unwind" target_abi="" target_arch="x86_64" target_endian="little" target_env="gnu" target_family="unix" target_feature="fxsr" target_feature="sse" target_feature="sse2" target_has_atomic="16" target_has_atomic="32"...

That works and does not fail with illegal instruction.

Thanks for bringing this up. Just to clarify - would you prefer that the gem returns the full response instead of raising an error so that you can handle the...