After #72 the relay answers before Stalwart does, so the dot went green on open even when Stalwart never sent anything, which is exactly the reporter's situation. Now it turns green on the first ping or state event, and the backoff resets there as well, so a stream that opens and closes right away keeps backing off. Fan-out tabs get a ping from us when they join, since there's no upstream one.
For #71, follow-up to #72.
After #72 the relay answers before Stalwart does, so the dot went green on open even when Stalwart never sent anything, which is exactly the reporter's situation. Now it turns green on the first ping or state event, and the backoff resets there as well, so a stream that opens and closes right away keeps backing off. Fan-out tabs get a ping from us when they join, since there's no upstream one.
Since #72 the relay answers the browser before Stalwart has, so an open
stream no longer proves anything: when Stalwart never answers, the dot
would turn green while no updates arrive. The client now shows
"connected" on the first ping or state event instead of on open, and
resets its backoff there too, so a stream that opens and ends at once
keeps backing off instead of retrying every second.
Relayed tabs get Stalwart's own first ping. Fan-out has no upstream
ping, so the server sends one when a tab joins fan-out, directly or by
moving off the relay.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
For #71, follow-up to #72.
After #72 the relay answers before Stalwart does, so the dot went green on open even when Stalwart never sent anything, which is exactly the reporter's situation. Now it turns green on the first ping or state event, and the backoff resets there as well, so a stream that opens and closes right away keeps backing off. Fan-out tabs get a ping from us when they join, since there's no upstream one.