GitLab API throws 404 on newly created issue
Summary
Nondeterministically we at least once got a 404 when fetching the information of a newly created issue via your API. This might be a race condition/caching thing because fetching it manually afterwards always worked and it only happened after we upgraded to a new fancy server.
Steps to reproduce
Nondeterministic, hard. Probably you can try getting a decently performant machine hooking up to your webhooks that fetches issue details upon receiving a webhook for the newly created issue, try that a few hundred times and hope it appears.
Example Project
See gitmate/open-source/gitmate-2#176 (closed)
What is the current bug behavior?
get a 404 without the issue data
What is the expected correct behavior?
get a proper response to the request including the issue data
Relevant logs and/or screenshots
See downstream bug gitmate/open-source/gitmate-2#176 (closed)
This is the request we did, it was executed immediately after receiving the webhook of the creation of that issue:
[
'https://gitlab.com/api/v4',
'get',
{
'access_token': [Filtered]
},
'/projects/gitmate%2Fopen-source%2FIGitt/issues/74'
](For more info see gitlab.com/gitmate/open-source/IGitt , our GitLab abstraction library)
Output of checks
This bug happens on GitLab.com