Hacker News Reader

Rather comically, I've been unable to import my Gitlab.com repo into an on-prem Gitlab EE instance for the last 3-4 months, due to an import bug -- seems like that's the one import that should be easy to test thoroughly, but apparently not.

Here's to hoping that this version happens to have fixed the issue!

View on HN

Thanks for the report @theptip.

Did you happen to open an issue? It would be great to ensure this one is being tracked appropriately.

I opened tickets with GitLab support, which were eventually closed due to inactivity (i.e. support let the issues time out without a resolution, despite me doing two 1-hour live debugging sessions with a support rep and a full stack trace highlighting the failing code).

In general I wasn't expecting to have to raise issues on the open source tracker myself after reporting to internal/paid support, but perhaps that's where I went wrong.

I'm working this quarter to help improve our quality of service. If you email me the ticket number(s) at lee@gitlab.com I'm happy to dive in and take a look. In theory, if we had clear traces an issue should have been made on your behalf. Happy to help get to the bottom of this.

Reply on news.ycombinator.com