Murad-Suleymanov opened a new issue, #8949:
URL: https://github.com/apache/devlake/issues/8949

   ### Search before asking
   
   - [x] I had searched in the 
[issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and 
found no similar feature requirement.
   
   
   ### Use case
   
   When DevLake collects Jira issues (`jira:collectIssues`), each page body is 
parsed with
   `json.Unmarshal`. If a page that returned a **successful (2xx) status** has 
a body that
   cannot be parsed as JSON — e.g. a **truncated/partial response** (connection 
dropped, or a
   proxy buffered only part of the body), or in rare misconfigured-proxy cases 
an HTML body
   served with a `200` status — the `ResponseParser` returns an error and the 
**entire
   `collectIssues` subtask fails**, aborting the whole Jira collection.
   
   Note: this is distinct from HTTP error statuses (e.g. `502/503/504`), which 
are already
   handled by the collector's retry logic. This request only concerns **parse 
failures on
   otherwise-successful responses**.
   
   On large Jira instances a single bad page (often on deep pagination with
   `expand=changelog`) can kill an entire sync even though thousands of other 
pages are fine.
   
   ### Description
   
   A configurable flag `JIRA_SKIP_UNPARSEABLE_ISSUES`:
   - **default `false`** → current behaviour (surface the error, fail the 
subtask).
   - **`true`** → log a warning and skip the unparseable page, letting the rest 
of the
     collection finish.
   
   This keeps collection resilient on big/flaky Jira instances without hiding 
the problem
   (the warning is still logged).
   
   ### Related issues
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [x] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to