Error reporting improvisation on Download Redline, Response Package, Harms dropdown
- Dominant language
- Python
- Stars
- 8
- Forks
- 2
- Avg merge
- 14h 34m
- Merged PRs (30d)
- 46
Description
Title of ticket:
#### Description
While testing the scenario#4 on #3301, which is the checking error scenarios with REDLINE package , its been understood that there are bit more things to considered other than exceptions thrown on code. Like, resource issue with in the containers, restarts due to other infra level issues etc. - refer comments on #4510. So to address those kind of issue and report on the Front end, we can update API and FE components to a logic that checks time difference between latest job status(started, in progress) and current time, and if its greater than 30 min (or any config. time) we will consider that as a failure! - rather than showing `inprogress` icon for ever!
#### Dependencies
Are there any dependencies?
#### DOD
- [ ] API update with logic described above
- [ ] Unit testing.
- [ ] More DODs! Welcome.
- [ ]
- [ ]
Contributor guide
Research direction
Start by tracing the API and frontend components that display Download Redline, Response Package, and Harms job statuses, then review scenario #4 in #3301 and the comments on #4510. Define how the timeout is configured and verify the API behavior, frontend reporting, and unit tests for jobs that remain in progress beyond the threshold.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend, frontend, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100