Anders Kaseorg fde9b1d366 channel: Remove idempotent retry loop. ... This was added by commit 7f174213ed, and appears to have been designed for responses that are *successful* but falsy. Logically, these should not implicitly represent a failure to be retried if it were. Note from tabbott: The background is that this idempotent retry loop was a hacky workaround for a bug we never understood but saw daily in production. Especially during server restarts / client reloads, something would result in 200 responses with no data being seen by the frontend, despite the Django server not having received/processed the request. Fortunately, this strange failure mode appears to have stopped happening in late 2019, so we can delete this hack. Signed-off-by: Anders Kaseorg <anders@zulip.com>		2022-08-19 12:14:41 -07:00
..
node_tests	channel: Remove idempotent retry loop.	2022-08-19 12:14:41 -07:00
puppeteer_lib	left-sidebar: Make Subscribe to more streams more informative.	2022-08-15 12:32:43 -07:00
puppeteer_tests	puppeteer: Fix flake in `user-deactivation.ts`.	2022-08-17 11:58:16 -07:00
zjsunit	zjsunit: Support asynchronous overrides.	2022-08-18 16:21:04 -07:00