"Christian Berentsen (chrberen)" <chrbe...@cisco.com> writes:
> I was unfortunately not able to get signed in to report the bug. > Something messed up with the browser storing the gitlab login > password, and after using the "forgot password" I couldn't find the > follow up email anywhere (including spam) > Hmm, this is quite unfortunate. I have checked the mail server and gmail claims that the message was successfully delivered to jc.berent...@gmail.com. Is this the expected address? > Maybe something messed up with my mixing the work email for the > mailing list and my personal for gitlab, causing the gitlab account to > not be in the proper approval state? > > I can add some additional info about the bug event: > This was running on a shared cluster where IT identified there were a > lot of unrelated zombie processes, so the "Resource temporarily > unavailable" result was probably real. > > I'd expect this context to lower the severity of this bug. But anyway, > this may possibly trigger in OS environments with resource constraints > or bumping into syslimits. > While I'm not certain precisely what has failed here, I suspect that the fact that we spawn and kill a fresh OS thread for each marking cycle likely doesn't help matters. This is something that I have wanted to fix for quite some time. Over the weekend I carried out the refactoring; the result is !11048 [1] Thanks again for your bug report. It would be great if we could get to the bottom of why your account creation request is stuck. Cheers, - Ben [1] https://gitlab.haskell.org/ghc/ghc/-/merge_requests/11048
signature.asc
Description: PGP signature
_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
