Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash at request-reponse assertion #4898

Closed
nazar-pc opened this issue Nov 19, 2023 · 2 comments
Closed

Crash at request-reponse assertion #4898

nazar-pc opened this issue Nov 19, 2023 · 2 comments

Comments

@nazar-pc
Copy link
Contributor

nazar-pc commented Nov 19, 2023

I have request-response protocol crashing on this debug assertion:

debug_assert_eq!(connections.is_empty(), remaining_established == 0);

Logs with following level:

RUST_LOG=info,subspace_network=trace,libp2p_core=trace,libp2p_identify=trace,libp2p_swarm=trace,libp2p_kad=trace,libp2p_autonat=trace,libp2p_request_response=trace

dsn-sync-debug-farmer-3.log.zip

UPD: While reproducible, the same app with RUST_LOG=trace:
dsn-sync-debug-farmer-4.log.zip

@thomaseizinger
Copy link
Contributor

Could this be related to #4773?

Do you use any connection management behaviours like connection limits? If yes, then the temporary fix is to put them as the very first field in your behaviour struct.

@nazar-pc
Copy link
Contributor Author

Possibly related, we do use connection limits indeed. Will move connection limits to the beginning then and closing this as duplicate.

@nazar-pc nazar-pc closed this as not planned Won't fix, can't repro, duplicate, stale Nov 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants