Merged
Conversation
ba6c055 to
9229079
Compare
a0cfe09 to
d352cd6
Compare
631f8ff to
a42bafe
Compare
This doesn't fix the current issue, but it helps us stay up to date
Github runners have been updated which aslo updated Chrome. There is a regression in Chrome that causes the shaders used by Three.js to break when running in enviroments without a GPU. This issue will affect our users too interacting with astropi if they also don't have a GPU although I'm not clear how common this would be. We could investigate better handling errors from the webGL canvas. [1] https://github.com/orgs/community/discussions/185629 [2] https://issues.chromium.org/issues/476172421
a42bafe to
bc35c39
Compare
jamiebenstead
approved these changes
Jan 29, 2026
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.
Github runners have been updated which also updated Chrome. There is a regression in Chrome that causes the shaders used by Three.js to break when running in environments without a GPU.
This issue will affect our users too interacting with astropi if they also don't have a GPU although I'm not clear how common this would be. We could investigate better handling errors from the webGL canvas.
Other reports of the issue:
https://github.com/orgs/community/discussions/185629
https://issues.chromium.org/issues/476172421