fix: Potential Fix for Global Timeline Server Error #2372
Merged
Conversation
This file contains 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
5 tasks
michael-genson
deleted the
fix/potential-fix-for-refreshing-timeline-causes-server-error
branch
|
Oh yeah I forgot to check to see if this actually worked. It did, the issue seems to be gone :) |
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.
What type of PR is this?
(REQUIRED)
What this PR does / why we need it:
(REQUIRED)
Maybe fixes a server error related to the new timeline by removing use of
$auth. @hay-kot if you could take a look at the bug report when you get the chance, I can't reproduce in the dev container, so I'm not too sure what's going on. I can reproduce easily in prod though (see reproduction steps reported on the bug report).Also if you know of a way to test it, let me know 😅
Which issue(s) this PR fixes:
(REQUIRED)
(maybe) fixes #2370
Release Notes
(REQUIRED)