stigi opened a new pull request, #9322:
URL: https://github.com/apache/devlake/pull/9322
### Summary
The Linear `Collect Comments` subtask fails when an issue that DevLake
already stored has been deleted in Linear:
```
subtask Collect Comments ended unexpectedly
caused by: graphql query got error
Wraps: (2) Entity not found: Issue
```
The GraphQL collector already skips this case for GitHub, whose message is
`Could not resolve to an Issue`. Linear's message for the same case is `Entity
not found: Issue`, so that error was not skipped. `Collect Issue History` has
the same problem.
The failure also repeats. The collector state is saved only after a
successful run, so the next run uses the same time window, queries the same
deleted issue and fails again. On our instance one team failed every night for
more than two weeks, and every subtask after `Collect Comments` was skipped for
that team.
This PR makes `isIgnorableGraphqlQueryError` match Linear's message too. A
deleted issue then produces the existing warning, and collection continues.
`Entity not found` for any type other than `Issue` still fails.
### Does this close any open issues?
No issue filed.
### Screenshots
Not applicable (collector-only change).
### Tests
`helpers/pluginhelper/api/graphql_collector_test.go`: added cases for
`Entity not found: Issue` (ignored) and `Entity not found: Team` (not ignored).
The new assertion fails before the change and passes after it. `go test
./helpers/pluginhelper/api/ ./plugins/linear/tasks/ ./plugins/linear/impl/`
passes.
<sub>🤖 Generated with [Claude Code](https://claude.com/claude-code)</sub>
--
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]
