-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: handle state change with identical or missing currentWidgetId #181
Open
cbarber
wants to merge
4
commits into
master
Choose a base branch
from
cmb/fix-stuck-current-widget
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
cbarber
requested review from
aaddaamm,
chewnoill,
geraldalewis,
havivian,
joealba and
thedelchop
as code owners
March 2, 2020 14:11
The pi exhibited an issue where a current widget could become stuck and never continue to the next widget. It seems to be caused by clicking on the current widget in the tab. Added some logging in case there are other edge cases.
joealba
previously approved these changes
Mar 2, 2020
There is potentially a race condition between prefetch triggering onComplete and the onComplete for updated query from the state change. This functionality could use a refactor/rethink.
cbarber
force-pushed
the
cmb/fix-stuck-current-widget
branch
from
March 2, 2020 14:16
f7ab65f
to
0f7704d
Compare
Do you know of any javascript log drains that have a free tier for an easier way to look at these messages? |
chewnoill
approved these changes
May 20, 2021
chewnoill
reviewed
May 24, 2021
Comment on lines
+146
to
+147
nextWidgetId: null, | ||
prevWidgetId: null, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
are these all calculated values?
I'm going need some time to remember what this is and if its still neccessary |
closed in favor of #252 |
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.
The pi exhibited an issue where a current widget could become stuck and
never continue to the next widget. It seems to be caused by clicking on
the current widget in the tab. Added some logging in case there are
other edge cases.