<html><head></head><body>Thanks Matt. I did my best to make things as functional but I'm off skiing today so there won't be any further progress until tonight. <br><br><div class="gmail_quote">On March 24, 2019 3:29:45 PM EDT, Matthew Pickering <matthewtpickering@gmail.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">Gitlab is still broken unfortunately.<br><br>* Forking new projects doesn't work (according to deepfire)<br>* MRs are not updated when the branch is pushed to<br><br>I added a broadcast message to gitlab to inform people of the problem.<br><br>Cheers,<br><br>Matt<br><br>On Sat, Mar 23, 2019 at 10:13 PM Ben Gamari <ben@smart-cactus.org> wrote:<br>><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> Ben Gamari <ben@smart-cactus.org> writes:<br><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"> Matthew Pickering <matthewtpickering@gmail.com> writes:<br><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #8ae234; padding-left: 1ex;"> I don't know what has changed since yesterday but pushing new branches<br> to GitLab is broken.<br><br> The two most recent branches pushed to origin 404 when you click on the link.<br><br> <a href="https://gitlab.haskell.org/ghc/ghc/branches">https://gitlab.haskell.org/ghc/ghc/branches</a><br><br> <a href="https://gitlab.haskell.org/ghc/ghc/tree/wip/mp/15646">https://gitlab.haskell.org/ghc/ghc/tree/wip/mp/15646</a><br><br> I also pushed some commits to a fork and the MR which they appear on<br> didn't update at all. Perhaps a symptom of the same problem.<br><br> Also a recent MR by Ben complains of the source branch for the MR not<br> existing. <a href="https://gitlab.haskell.org/ghc/ghc/merge_requests/625">https://gitlab.haskell.org/ghc/ghc/merge_requests/625</a><br><br> The summary is that GitLab seems unusable at the moment. Did you<br> fiddle with anything recently Ben?<br><br></blockquote> Yes, I am aware of these issues have been working in the background to<br> resolve or report them. In short, I updated to 11.9.0 yesterday. This<br> seems to have introduced a bug in the handling of branches whose names<br> contain forward slashes. Unfortunately it hasn't been easy to nail down<br> precisely what broke.<br><br> I have tried rolling back to 11.8.2 but sadly the issues seem to persist.<br><br></blockquote> For what it's worth, I managed to come up with a patch that appears to<br> avoid the issue. It appears to be due to caching within GitLab, although<br> I can't say I understand precisely how it is going wrong. I have<br> reported the regression as gitlab-ce#59403 [1].<br><br> Cheers,<br><br> - Ben<br><br><br> [1] <a href="https://gitlab.com/gitlab-org/gitlab-ce/issues/59403">https://gitlab.com/gitlab-org/gitlab-ce/issues/59403</a><br></blockquote><hr>ghc-devs mailing list<br>ghc-devs@haskell.org<br><a href="http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs">http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs</a><br></pre></blockquote></div><br>-- <br>Sent from my Android device with K-9 Mail. Please excuse my brevity.</body></html>