| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
…e pages When a Jira issue page returns a successful (2xx) status but a body that cannot be parsed as JSON (e.g. a truncated/partial response), collectIssues currently fails the entire subtask and aborts the whole Jira collection. This adds an opt-in config JIRA_SKIP_UNPARSEABLE_ISSUES that, when true, logs a warning and skips the unparseable page so the rest of the collection can finish. Default behaviour (false) is unchanged. Signed-off-by: Murad-Suleymanov <muradsuleymanov868@gmail.com>
|
This could work. But I think a better approach would be adding the option to ScopeConfig and allowing user to toggle on the config-ui. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Summary
Adds an opt-in config JIRA_SKIP_UNPARSEABLE_ISSUES to the Jira collectIssues subtask.
When an issue page returns a 2xx status but a body that can't be parsed as JSON (e.g. a
truncated/partial response), the subtask currently fails and aborts the whole Jira collection.
With this flag set to true, the unparseable page is logged and skipped so the rest of the
collection finishes. Default (false) keeps current behaviour.
Closes #8949