GitLab seems quite poorly

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

GitLab seems quite poorly

Matthew Pickering
I don't know what has changed since yesterday but pushing new branches
to GitLab is broken.

The two most recent branches pushed to origin 404 when you click on the link.

https://gitlab.haskell.org/ghc/ghc/branches

https://gitlab.haskell.org/ghc/ghc/tree/wip/mp/15646

I also pushed some commits to a fork and the MR which they appear on
didn't update at all. Perhaps a symptom of the same problem.

Also a recent MR by Ben complains of the source branch for the MR not
existing.  https://gitlab.haskell.org/ghc/ghc/merge_requests/625

The summary is that GitLab seems unusable at the moment. Did you
fiddle with anything recently Ben?

Cheers,

Matt
_______________________________________________
ghc-devs mailing list
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
Reply | Threaded
Open this post in threaded view
|

Re: GitLab seems quite poorly

Ben Gamari-2
Matthew Pickering <[hidden email]> writes:

> I don't know what has changed since yesterday but pushing new branches
> to GitLab is broken.
>
> The two most recent branches pushed to origin 404 when you click on the link.
>
> https://gitlab.haskell.org/ghc/ghc/branches
>
> https://gitlab.haskell.org/ghc/ghc/tree/wip/mp/15646
>
> I also pushed some commits to a fork and the MR which they appear on
> didn't update at all. Perhaps a symptom of the same problem.
>
> Also a recent MR by Ben complains of the source branch for the MR not
> existing.  https://gitlab.haskell.org/ghc/ghc/merge_requests/625
>
> The summary is that GitLab seems unusable at the moment. Did you
> fiddle with anything recently Ben?
>
Yes, I am aware of these issues have been working in the background to
resolve or report them. In short, I updated to 11.9.0 yesterday. This
seems to have introduced a bug in the handling of branches whose names
contain forward slashes. Unfortunately it hasn't been easy to nail down
precisely what broke.

I have tried rolling back to 11.8.2 but sadly the issues seem to persist.

Cheers,

- Ben

_______________________________________________
ghc-devs mailing list
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

signature.asc (497 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: GitLab seems quite poorly

Ben Gamari-2
Ben Gamari <[hidden email]> writes:

> Matthew Pickering <[hidden email]> writes:
>
>> I don't know what has changed since yesterday but pushing new branches
>> to GitLab is broken.
>>
>> The two most recent branches pushed to origin 404 when you click on the link.
>>
>> https://gitlab.haskell.org/ghc/ghc/branches
>>
>> https://gitlab.haskell.org/ghc/ghc/tree/wip/mp/15646
>>
>> I also pushed some commits to a fork and the MR which they appear on
>> didn't update at all. Perhaps a symptom of the same problem.
>>
>> Also a recent MR by Ben complains of the source branch for the MR not
>> existing.  https://gitlab.haskell.org/ghc/ghc/merge_requests/625
>>
>> The summary is that GitLab seems unusable at the moment. Did you
>> fiddle with anything recently Ben?
>>
> Yes, I am aware of these issues have been working in the background to
> resolve or report them. In short, I updated to 11.9.0 yesterday. This
> seems to have introduced a bug in the handling of branches whose names
> contain forward slashes. Unfortunately it hasn't been easy to nail down
> precisely what broke.
>
> I have tried rolling back to 11.8.2 but sadly the issues seem to persist.
>
For what it's worth, I managed to come up with a patch that appears to
avoid the issue. It appears to be due to caching within GitLab, although
I can't say I understand precisely how it is going wrong. I have
reported the regression as gitlab-ce#59403 [1].

Cheers,

- Ben


[1] https://gitlab.com/gitlab-org/gitlab-ce/issues/59403

_______________________________________________
ghc-devs mailing list
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

signature.asc (497 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: GitLab seems quite poorly

Matthew Pickering
Gitlab is still broken unfortunately.

* Forking new projects doesn't work (according to deepfire)
* MRs are not updated when the branch is pushed to

I added a broadcast message to gitlab to inform people of the problem.

Cheers,

Matt

On Sat, Mar 23, 2019 at 10:13 PM Ben Gamari <[hidden email]> wrote:

>
> Ben Gamari <[hidden email]> writes:
>
> > Matthew Pickering <[hidden email]> writes:
> >
> >> I don't know what has changed since yesterday but pushing new branches
> >> to GitLab is broken.
> >>
> >> The two most recent branches pushed to origin 404 when you click on the link.
> >>
> >> https://gitlab.haskell.org/ghc/ghc/branches
> >>
> >> https://gitlab.haskell.org/ghc/ghc/tree/wip/mp/15646
> >>
> >> I also pushed some commits to a fork and the MR which they appear on
> >> didn't update at all. Perhaps a symptom of the same problem.
> >>
> >> Also a recent MR by Ben complains of the source branch for the MR not
> >> existing.  https://gitlab.haskell.org/ghc/ghc/merge_requests/625
> >>
> >> The summary is that GitLab seems unusable at the moment. Did you
> >> fiddle with anything recently Ben?
> >>
> > Yes, I am aware of these issues have been working in the background to
> > resolve or report them. In short, I updated to 11.9.0 yesterday. This
> > seems to have introduced a bug in the handling of branches whose names
> > contain forward slashes. Unfortunately it hasn't been easy to nail down
> > precisely what broke.
> >
> > I have tried rolling back to 11.8.2 but sadly the issues seem to persist.
> >
> For what it's worth, I managed to come up with a patch that appears to
> avoid the issue. It appears to be due to caching within GitLab, although
> I can't say I understand precisely how it is going wrong. I have
> reported the regression as gitlab-ce#59403 [1].
>
> Cheers,
>
> - Ben
>
>
> [1] https://gitlab.com/gitlab-org/gitlab-ce/issues/59403
_______________________________________________
ghc-devs mailing list
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
Reply | Threaded
Open this post in threaded view
|

Re: GitLab seems quite poorly

Ben Gamari-3
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.

On March 24, 2019 3:29:45 PM EDT, Matthew Pickering <[hidden email]> wrote:
Gitlab is still broken unfortunately.

* Forking new projects doesn't work (according to deepfire)
* MRs are not updated when the branch is pushed to

I added a broadcast message to gitlab to inform people of the problem.

Cheers,

Matt

On Sat, Mar 23, 2019 at 10:13 PM Ben Gamari <[hidden email]> wrote:
>
Ben Gamari <[hidden email]> writes:

Matthew Pickering <[hidden email]> writes:

I don't know what has changed since yesterday but pushing new branches
to GitLab is broken.

The two most recent branches pushed to origin 404 when you click on the link.

https://gitlab.haskell.org/ghc/ghc/branches

https://gitlab.haskell.org/ghc/ghc/tree/wip/mp/15646

I also pushed some commits to a fork and the MR which they appear on
didn't update at all. Perhaps a symptom of the same problem.

Also a recent MR by Ben complains of the source branch for the MR not
existing. https://gitlab.haskell.org/ghc/ghc/merge_requests/625

The summary is that GitLab seems unusable at the moment. Did you
fiddle with anything recently Ben?

Yes, I am aware of these issues have been working in the background to
resolve or report them. In short, I updated to 11.9.0 yesterday. This
seems to have introduced a bug in the handling of branches whose names
contain forward slashes. Unfortunately it hasn't been easy to nail down
precisely what broke.

I have tried rolling back to 11.8.2 but sadly the issues seem to persist.

For what it's worth, I managed to come up with a patch that appears to
avoid the issue. It appears to be due to caching within GitLab, although
I can't say I understand precisely how it is going wrong. I have
reported the regression as gitlab-ce#59403 [1].

Cheers,

- Ben


[1] https://gitlab.com/gitlab-org/gitlab-ce/issues/59403

ghc-devs mailing list
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
_______________________________________________
ghc-devs mailing list
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
Reply | Threaded
Open this post in threaded view
|

Re: GitLab seems quite poorly

Ben Gamari-2
In reply to this post by Matthew Pickering
Matthew Pickering <[hidden email]> writes:

> I don't know what has changed since yesterday but pushing new branches
> to GitLab is broken.
>
I managed to roll back the upgrade and appear to be stable again.

Cheers,

- Ben


_______________________________________________
ghc-devs mailing list
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

signature.asc (497 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: GitLab seems quite poorly

Ryan Scott
In reply to this post by Matthew Pickering
Things still appear not to work whenever I try to push a new branch:

    fatal: unable to access 'https://gitlab.haskell.org/RyanGlScott/ghc.git/': The requested URL returned error: 500

Ryan S.

_______________________________________________
ghc-devs mailing list
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
Reply | Threaded
Open this post in threaded view
|

Re: GitLab seems quite poorly

Ben Gamari-2
Ryan Scott <[hidden email]> writes:

> Things still appear not to work whenever I try to push a new branch:
>
>     fatal: unable to access 'https://gitlab.haskell.org/RyanGlScott/ghc.git/':
> The requested URL returned error: 500
>
Sigh; it looks like this is due to a change in the database schema left
over from the upgrade. I have opened gitlab-migration#62 to track this
[1].

Note, however, that SSH access is unaffected.

Cheers,

- Ben

[1] https://gitlab.haskell.org/bgamari/gitlab-migration/issues/62

_______________________________________________
ghc-devs mailing list
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

signature.asc (493 bytes) Download Attachment