Metadata
- Source
- FLUID-6399
- Type
- Task
- Priority
- Major
- Status
- Open
- Resolution
- N/A
- Assignee
- Antranig Basman
- Reporter
- Tony Atkins [RtF]
- Created
2019-09-23T08:41:51.167-0400 - Updated
2024-07-19T08:02:44.910-0400 - Versions
- N/A
- Fixed Versions
- N/A
- Component
-
- Framework
Description
In working with resource loaders on my own, I encountered the following if more than one resource can't be fetched:
Assertion failure - check console for more details: Error: rejecting promise {"disposition":"reject","value":{"isError":true,"status":404,"textStatus":"Not Found"}}which has already received "reject""
It looks like a single promise is used for more than one fetch, instead of either failing on the first error or accumulating the rejections as we've done elsewhere.
The tests current test for a single failure, adding a grade with two resource definitions that point to /notfound should be sufficient to reproduce the problem.