Strange stderr errors

[Vagabond]

When using inet_ext via erlang-nat we sometimes see messages on stderr like this:

erl_child_setup: failed with error 32 on line 253

cut: write error: Broken pipe

They don't appear consistently, and I'm not sure why.

[benoitc]

no trace? On which OS do you get it? Seems like it get the error from there.

https://github.com/benoitc/inet_ext/blob/master/src/inet_ext.erl#L60

[Vagabond]

Yes, exactly. It happens on linux and if I run the shell command manually it never throws a broken pipe.

[benoitc]

it may be the cut command is not finished before cut is ending , do you always reproduce it on the same interface?

[benoitc]

bump, i am thinking for a simple patch to eventually retry if it happens. Maybe it's an issue with the number of fds available .

[benoitc]

@Vagabond i wasn't able to reproduce the issue yet. Can you five me more context. Also is this true linux or WSL ?

[benoitc]

@Vagabond can you try to set the vm args +spp to true and let me know if it solves the issue for you?

[Vagabond]

This is true linux, I will see if I can find out how to set +spp, I see it running unit tests, so it's a bit tricky to figure out how to enable that flag under rebar3.

[benoitc]

@Vagabond is there any way I can run the unit tests myself? I didn't reproduced it yet.

[Vagabond]

Yeah, if you run the erlang-libp2p test suite with make test you'll see them.