As seen in https://gitlab.com/gitlab-org/gitlab-runner/issues/4029, a few people...

sytse · on Sept 10, 2019

I agree this issue hasn't been prioritized as high as it should. I meant to indicate that with "This bug took too long to fix." but I should have said it took to long to schedule.

We concluded the same internally recently and hence the focus on bugs and wider community contributions in 12.4. We overly focussed on getting the DAG https://docs.gitlab.com/ee/ci/directed_acyclic_graph/ and Merge Trains https://docs.gitlab.com/ee/ci/merge_request_pipelines/pipeli... out the door and missed a bad bug, we're sorry.

sooheon · on Sept 10, 2019

Not a GitLab user, but I'm deeply impressed with your openness in handling issues on this thread.

Operyl · on Sept 10, 2019

I've always appreciated how open he is, I just wish it never came down to having to flag him down on Hacker News to get something properly fixed (although, I appreciate that is still something I can do).

joshlambert · on Sept 11, 2019

Hi - just wanted to confirm that this issue has been addressed and will be included in our 12.4 runner release.

MR: https://gitlab.com/gitlab-org/gitlab-runner/merge_requests/1...