Date: Wed, 10 May 2023 19:53:09 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 271356] www/gitlab-ce: FrozenError, can't modify frozen String Message-ID: <bug-271356-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D271356 Bug ID: 271356 Summary: www/gitlab-ce: FrozenError, can't modify frozen String Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: mfechner@FreeBSD.org Reporter: yom@iaelu.net Flags: maintainer-feedback?(mfechner@FreeBSD.org) Assignee: mfechner@FreeBSD.org Created attachment 242113 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D242113&action= =3Dedit FrozenError log I've just installed latest gitlab-ce package, 15.10.6, but it seems to be at least in since 15.10.3, since I jumped from 15.5.x to 15.9, then 15.10 since this week-end. The bug I'm reporting has somewhat to do with FrozenError, and frozen_string_literal in ruby. I've attached the log to this report. This error happens when: - you have a shared runner (gitlab runner) registered in the admin - you try to access: http://gitlab.example.com/groupname/projectname/-/settings/ci_cd An error 500 is showing on the ci/cd project ci/cd settings page, for every project in your gitlab instance. I've tried to look for this bug, search gitlab for that, I've also tried so= me of the "recommended" resolution: - some sql command removing runners_token and runners_token_encrypted values - some sql command to "finish" an unfinished upgrade path - removing, adding the runner again - reinstalling gitlab-ce package after backup'ing important files, and remo= ving the complete /usr/local/www/gitlab-ce folder - trying to set frozen_string_literal to false in the runners_helper.rb I'm still at some point where I don't get why there is that frozen error, it was working well for gitlab-ce 15.9.x I think, since my company dev teams w= ere adding things in the ci/cd settings before I upgraded to 15.10.x this last week-end. I'd really like some help here please, obviously because I can't go back to 15.9.x now that I've upgraded/autoremoved packages as recommended. Our comp= any dev team is now blocked since they can't add ci/cd settings to their projec= ts that we are trying to test in the hope we can make it to production. I've got 2 installations: - a test instance where I usually test gitlab-ce upgrades, since it's not always working great, and need a stable production instance. It's a jail wi= th all inside: gitlab-ce and postgresql - a production instance, which consists of one server installed with gitlab= -ce, and a jail in which postgresql is installed. Both, with 15.10.x different versions: production is 15.10.3_3, and test instance is 15.10.6. Also both have this same frozen error. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-271356-7788>