refactor(DetailedStopGroup): replace async_stream#3310
Open
thecristen wants to merge 1 commit into
Open
Conversation
Don't create possible timeouts, just get everything anyway
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Scope
MBTA-DOTCOM-JV
In the continued vein of, we unearth old but recurring Sentry issues from the archive...
Implementation
This message appears when
Task.async_streamdoesn't specify anon_timeoutaction - the default behavior is the task exits!In this case I think it's better if we don't create possible timeouts: just get everything anyway without async calls, since we'll always want this page (
/stops) to list all the stops.I think the code had likely been structured this way because fetching and processing all the stops can be kinda slow. So this updated code leverages
StreamoverEnumin a few spots for some hopeful performance improvements. The flame charts are still massive here, but I did see this page go from producing an SVG of 5.2MB to one that's 3.4MB...