gituser

@eliotstock Not sure why you're getting issues there. All you need to do is to create a systemd unit like this in **/etc/systemd/system/nethermind.service** (example is for ropsten network): ``` [Unit]...

@eliotstock did you paste into */etc/sudoers.d/nethermind* the content from my post? try deleting and re-adding nethermind user: ``` userdel nethermind adduser --disabled-password nethermind ```

Also there is a memory leak somewhere in Pruning if it's triggered manually. My Nethermind crashed by OOM with 92GB in VM when I've activated pruning.

I have the same issue, polkadot v0.9.29 compiled just fine on the same machine whilst v0.9.30 fails to compile with exactly same error. OS is `Ubuntu 18.04.6 LTS`

@ggwpez v0.9.29 compilation worked just fine, why the sudden change? I'm using latest rust, I do update it before I build polkadot. ``` stable-x86_64-unknown-linux-gnu unchanged - rustc 1.64.0 (a55dd71d5 2022-09-19)...

@ggwpez it might be some cache issue after all, I've tried multiple times rolling back to `v0.9.29`, building, then building `v0.9.30` and then issuing `cargo clean` and building again `v0.9.30`...

getting same error when trying to build v0.9.31: ``` Compiling names v0.13.0 error: failed to run custom build command for `sc-network-bitswap v0.10.0-dev (https://github.com/paritytech/substrate?branch=polkadot-v0.9.31#7a4e5163)` Caused by: process didn't exit successfully: `/home/build/polkadot/source/target/release/build/sc-network-bitswap-5bd8ccf92111e3c9/build-script-build`...

@bkchr how do I compile v0.9.31 with master branch of substrate? and why not push this commit to polkadot-v0.9.31 branch?

@bkchr that didn't help

@bkchr is there any way to apply that fix without creating a fork of this repository and changing dependencies somehow in the build process? it seems cargo makes a fresh...