Besu support
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 32/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- rust
- Domain
- networking
Research direction
Start by reproducing the Besu execution-layer client issue and review the socket-related warnings in udp.rs, legacy_tcp.rs, and mod.rs. Determine the required SO_REUSEADDR and other syscall or socket-option behavior from the reported logs. Done means Besu can run without the port-occupied failure and the required unsupported-operation warnings are addressed.
Written by the indexing model from the issue text.
Description
We want to support the execution layer client Besu.
We seem to require suport for SO_REUSEADDR, as Besu incorrectly claims that the port is already occupied. Furthermore, there are more warnings logged by shadow:
Log
00:00:03.348554 [126508:shadow-worker] 00:00:05.022849390 [WARN] [node6:29.251.164.100] [mod.rs:602] [shadow_rs::host::syscall::handler] (LOG_ONCE) Detected unsupported syscall times (100) called from thread 1023 in process java on host node6
00:00:04.740233 [126508:shadow-worker] 00:00:05.031794670 [WARN] [node6:29.251.164.100] [udp.rs:642] [shadow_rs::host::descriptor::socket::inet::udp] (LOG_ONCE) We do not yet handle ioctl request SIOCGIFCONF on tcp sockets
00:00:04.828432 [126508:shadow-worker] 00:00:05.032529800 [WARN] [node6:29.251.164.100] [legacy_tcp.rs:1110] [shadow_rs::host::descriptor::socket::inet::legacy_tcp] (LOG_ONCE) getsockopt called with unsupported level 6 and opt 12
00:00:04.828511 [126508:shadow-worker] 00:00:05.032533800 [WARN] [node6:29.251.164.100] [legacy_tcp.rs:1110] [shadow_rs::host::descriptor::socket::inet::legacy_tcp] (LOG_ONCE) getsockopt called with unsupported level 6 and opt 4
00:00:04.828585 [126508:shadow-worker] 00:00:05.032537800 [WARN] [node6:29.251.164.100] [legacy_tcp.rs:1110] [shadow_rs::host::descriptor::socket::inet::legacy_tcp] (LOG_ONCE) getsockopt called with unsupported level 1 and opt 56
00:00:04.831917 [126508:shadow-worker] 00:00:05.032584380 [WARN] [node6:29.251.164.100] [udp.rs:965] [shadow_rs::host::descriptor::socket::inet::udp] (LOG_ONCE) setsockopt called with unsupported level 0 and opt 49
00:00:04.834225 [126508:shadow-worker] 00:00:05.032603290 [WARN] [node6:29.251.164.100] [udp.rs:945] [shadow_rs::host::descriptor::socket::inet::udp] (LOG_ONCE) setsockopt SO_REUSEADDR not yet implemented for udp
- Dominant language
- Rust
- Stars
- 59
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ethereum/ethshadow
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Nethermind supportOpen
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in ethereum/ethshadow
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 3 days
-
state:triage-needed
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Automattic/harper#4503 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 2 days