vbhanuchander-lang commented on issue #8949: URL: https://github.com/apache/devlake/issues/8949#issuecomment-5152051418
I'd like to help move this along if it's still open. @Murad-Suleymanov, are you still planning to submit a PR for this? If so I'll stay out of the way. If not, I'm happy to pick it up. The scope looks contained: both the V2 (`api/2/search`) and V3 (`api/3/search/jql`) response parsers in `plugins/jira/tasks/issue_collector.go` return an error on `json.Unmarshal` failure, so the flag would sit there and fall back to logging a warning and skipping the page instead. `JIRA_JQL_AUTO_FULL_REFRESH` in the same plugin already establishes the `taskCtx.GetConfigReader().GetBool(...)` pattern, so it would follow that, default to `false`, and cover only parse failures on otherwise-successful (2xx) responses — HTTP error statuses would keep their existing retry behaviour, as you noted. Happy to adjust the approach if maintainers would rather see this handled generically in the collector helper rather than in the Jira plugin. -- 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]
