MeltanoLabs / MeltanoLabs/tap-gitlab
Availability issues on Gitlab causing job failures
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12
- Forks
- 29
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 1
Description
In GitLab by @aaronsteers on Mar 12, 2021, 17:28
As brought up in a recent slack conversation, an uptick in 500 errors on the Gitlab side recently seems to be manifesting as an increased number of job failures from tap-gitlab. As proposed in that thread, this could be an opportunity to improve network handling and retries within tap-gitlab.
The SDK refactor (#34) might relate to this as well. While the SDK does have built-in retry capability with backoff, we'd have to make sure the correct errors would get retries, according to the error codes gitlab is returning.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing tap-gitlab's network handling and the SDK refactor in #34, then compare GitLab's returned error codes with the SDK's built-in retry behavior. Done means transient GitLab 500 responses are retried with backoff so they do not unnecessarily fail jobs. No specific files or tests are named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100