-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
Fix failed sub-asset loads getting stuck in LoadState::Loading
#22628
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
Open
greeble-dev
wants to merge
9
commits into
bevyengine:main
Choose a base branch
from
greeble-dev:test-asset-load-fail
base: main
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.
+204
−9
Open
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
29f779b
First pass.
greeble-dev 5241f1a
Redid test as a simpler function. Fixed misleading "root asset is wro…
greeble-dev a22ca54
Fixed missing sub-asset errors failing to set `LoadState::Failed`, at…
greeble-dev 1295646
Fixed sub-assets getting stuck in the loading state when the sub-asse…
greeble-dev f8d3ceb
Added tested for malformed root and sub-assets, and "sub-asset is not…
greeble-dev 35b6c0b
Added "sub-asset of root asset that does not exist" test.
greeble-dev 795363a
Improved legibility when `TestAssetLoadError` is lacking support for …
greeble-dev 6aedd51
Tidy ups.
greeble-dev 51f8ae3
Fixed loader error events getting sent to the root asset when the loa…
greeble-dev File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
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.
Should we just use run_app_until here instead?
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.
I did this initially, but found that it made debugging test failures harder -
run_app_untilwill panic without any information about what failed. Doing it manually lets me print a clear "did X, expected Y, got Z".I do think there's room for improvement. Maybe adding a
run_app_untilvariant with more options, or even better a way to say "run until all loads have resolved". But don't think that would fit in this PR.