Buffer of stream grows beyond limit

Issue Report

Environment

  • Operating System: Ubuntu 22.04
  • Pulsar/Advanced CLI/Docker: Docker

Problem

I started to see an error message on farmer logs. Maybe It is worth investigating.

subspace-farmer-1  | 2024-04-29T13:25:15.646906Z ERROR yamux::connection: 8491cfd2/243: buffer of stream grows beyond limit    
subspace-farmer-1  | 2024-04-29T13:25:15.647110Z ERROR yamux::connection: 8491cfd2/243: buffer of stream grows beyond limit    
subspace-farmer-1  | 2024-04-29T13:26:23.021530Z ERROR yamux::connection: f3a12c67/66: buffer of stream grows beyond limit    
subspace-farmer-1  | 2024-04-29T13:26:23.037080Z ERROR yamux::connection: f3a12c67/66: buffer of stream grows beyond limit    
subspace-farmer-1  | 2024-04-29T13:27:17.280353Z ERROR yamux::connection: 02833cf7/2567: buffer of stream grows beyond limit    
subspace-farmer-1  | 2024-04-29T13:27:17.280390Z ERROR yamux::connection: 02833cf7/2567: buffer of stream grows beyond limit

This is an upstream issue, I’ll update yamux dependency and see if it helps in the next release.

Should be non-fatal though.

1 Like

@shamil another thing to report and discuss upstream

Reported upstream: buffer of stream grows beyond limit · Issue #188 · libp2p/rust-yamux · GitHub

1 Like

Can someone who sees this regularly test Snapshot build · subspace/subspace@e5a8236 · GitHub?
It has a change suggested upstream that may help with this.

According to @PuNkYsHuNgRy it helped, so Remove setting receive window size for Yamux by nazar-pc · Pull Request #2791 · subspace/subspace · GitHub will likely be included in the next release

Still haven’t seen it come up.

@nazar-pc Why not merge it to the main branch? I didn’t test it because it seems have no impact on the replotting.

It needs to be reviewed first, I’m generally not pushing code into main without second pair of eyes on it.

Testing is important because even small changes sometimes have unexpected consequences. I don’t expect any in this case, but it is also important to get confirmation from the community that it does actually help with the issue.

Fix included in Release gemini-3h-2024-jun-11 · subspace/subspace · GitHub

1 Like