vyzo

Hrm, it might be relates to the notifiee trying to open a stream? Hard to tell what's going on here.

pubsub doesn't do anything out of the ordinary, so it is libp2p bug triggered by pubsub probably.

Pubsub streams are unidirectional. Prevously it would read incoming data and ignore them, now it resets the stream, which makes it stricter. Are you interoping with a faulty peer?

Interesting, seems like an issue with multiple connections. Maybe a bug with the reset handling, can you investigate further around there?

thank you for the detailed investigation on this! On Thu, Jun 29, 2023 at 12:11 PM Iulian Pascalau ***@***.***> wrote: > After trying with the new go-libp2p version v0.28.1 everything...

Any details from the panics?

oooh, it's an Out Of Memory panic.

Validation is run asynchronously in a background goroutine.

With the current implementation it's not possible. With quite a bit of work it may be possible.

It's a rather complex change to implement. The trade off is that the message propagation would be very slow, as it wouldn't be forwarded until it could be validated.