3 ms·
Hey - I'm the PM for our Code Review group. Sorry to see you're running in to that issue, it's been a real challenge for us. If you're running in to it pretty o
by phikai 3y ago
Hey - I'm the PM for our Code Review group. Sorry to see you're running in to that issue, it's been a real challenge for us. If you're running in to it pretty often, it'd be great if you could provide some details on what steps you're taking (maybe even record a video) to help us figure out what's going on. For lots of bugs, the hardest thing for us to do is reproduce them... so if you've got a reliable way to do that, it really helps us prioritize things to fix.
- thunky 3y ago> it'd be great if you could provide some details on what steps you're taking (maybe even record a video) to help us figure out what's going on The comment you're replying to has a link to an issue which includes a video and a test project.
- jufiydk 3y agoThe user you are replying to has stated that the problem has not yet been made reproducible in the issue you are referring to.
- yjftsjthsd-h 3y agoThat's the opposite of my reading? https://gitlab.com/gitlab-org/gitlab/-/issues/350662#note_1065545131 https://gitlab.com/gitlab-org/gitlab/-/issues/350662#note_10... > However, I can still reproduce it under certain conditions: Separately, that's not much of a defense; inconsistent errors are still problems for users. Although, I suppose gitlab only fixing bugs that are 100% reproducible would explain a lot about their product.
- amf12 3y agoMaybe you should read the comments on the issue first.