RhodeCode - issues: Issueshttps://issues.rhodecode.com/https://issues.rhodecode.com/favicon.ico?16960560042024-02-27T17:23:51ZRhodeCode - issues
Redmine RhodeCode CE/EE - Support #5713 (New): Deployment of Rhodecode on CentOS or Rocky Linuxhttps://issues.rhodecode.com/issues/57132024-02-27T17:23:51ZJean-Michel Mazzocco
<p>Hello </p>
<p>We need to rebuild a Rhodecode server due to OS obsolescence (CentOS 6) on version 4.27</p>
<p>I can see on configuration recommended only centOS 8 is supported.<br>
Our it team we propose to use a Linux machin with a fork of CentOS after the switch to stream, the rocky linux </p>
<p>I don't know if it's supported the current version of rocky Linux is the 9.3</p>
<p>Thank you </p>
RhodeCode CE/EE - Task #5705 (New): 5.X - activate update task automatically over rcstackhttps://issues.rhodecode.com/issues/57052023-11-13T08:06:05ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>Because rcstack has enabled scheduler by default, we should activate the periodic update check</p>
RhodeCode CE/EE - Bug #5698 (Resolved): 5.0.0 release - documentation 4.X -> 5.X migration step-b...https://issues.rhodecode.com/issues/56982023-10-17T16:32:54ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>In order to smoothen the transition from 4.X release we need to write a guide how to move to 5.X series.</p>
RhodeCode CE/EE - Task #5697 (New): Improve CI & CD integrationshttps://issues.rhodecode.com/issues/56972023-10-17T16:31:20ZMarcin Kuzminski [CTO]marcin@rhodecode.comRhodeCode CE/EE - Feature #5696 (New): Code Browser UIhttps://issues.rhodecode.com/issues/56962023-10-17T16:29:39ZMarcin Kuzminski [CTO]marcin@rhodecode.comRhodeCode CE/EE - Task #5695 (New): Artifacts - Making artifacts a prime functionalityhttps://issues.rhodecode.com/issues/56952023-10-17T16:28:43ZMarcin Kuzminski [CTO]marcin@rhodecode.comRhodeCode CE/EE - Task #5694 (New): GIT LFS 2.0https://issues.rhodecode.com/issues/56942023-10-17T16:27:54ZMarcin Kuzminski [CTO]marcin@rhodecode.comRhodeCode CE/EE - Bug #5691 (Resolved): Fix 5.0.0 exceptionhttps://issues.rhodecode.com/issues/56912023-10-17T07:57:13ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p><a href="https://code.rhodecode.com/_admin/settings/exceptions/140374526066368" class="external">https://code.rhodecode.com/_admin/settings/exceptions/140374526066368</a></p>
<p>This seems to be a regression</p>
RhodeCode CE/EE - Bug #5684 (New): Integrations do not send through commits for new brancheshttps://issues.rhodecode.com/issues/56842022-07-27T22:50:57ZAndrew Whalan
<p>When pushing the first commit on a new branch, the commit information is not included in the resulting repo-push event.</p>
RhodeCode CE/EE - Bug #5682 (New): Login Page stuck until page is refreshedhttps://issues.rhodecode.com/issues/56822022-06-30T08:37:52ZEDV Habemus
<p>When logging in over the Web GUI, after the credentials are typed in, your're stuck on the login page until the page gets refreshed. <br>
Even after updating the issue keeps on happening.</p>
RhodeCode CE/EE - Bug #5680 (New): Inconsistent timezone displayhttps://issues.rhodecode.com/issues/56802022-04-20T14:15:36ZEmiliano Funes
<p>Setting a timezone different than UTC-0 causes inconsistencies in the displayed commit ages.<br>
In our case we use UTC-3. After a new commit, the last modified date is shown as if the commit was created 3 hours in the future. <br>
Also, creation dates of groups and repos are saved in 1/1/1970 (in our case UTC-3)<br>
<img src="https://issues.rhodecode.com/attachments/download/3096/homepage_bug.png" title="Homepage bug" alt="Homepage bug" loading="lazy" /><br>
When I enter in the repo details, the last modified date is shown in UTC-0, for example, showing "4 minutes and 14 seconds ago"<br>
<img src="https://issues.rhodecode.com/attachments/download/3097/details_bug.png" title="Commit details bug" alt="Commit details bug" loading="lazy" /></p>
RhodeCode CE/EE - Bug #5679 (New): Data directory continues to grow until it fills disk partitionhttps://issues.rhodecode.com/issues/56792022-03-28T16:24:19Zlee loucks
<p>Our data/cache directory will continue to grow until it fills the partition and the web interface of RC becomes inaccessible. We have been increasing the partition size (now up to 20G) and it still is filling/failing. </p>
<p>After removing clearing the cache entries from the data directory, was able to pull this exception from the Exception Tracker</p>
<pre><code>Exception `OSError` generated on UTC date: 2022-03-28T13:15:03.975409
Request: POST https://127.0.0.1:5000/rc4/_admin/api
127.0.0.1 RhodeCode-CLI/1.4.0
Traceback (most recent call last):
File "/opt/rhodecode/store/da2il1f83gci4333j0sd256nji9nlhpa-python2.7-pyramid-1.10.4/lib/python2.7/site-packages/pyramid/router.py", line 277, in default_execution_policy
return router.invoke_request(request)
File "/opt/rhodecode/store/da2il1f83gci4333j0sd256nji9nlhpa-python2.7-pyramid-1.10.4/lib/python2.7/site-packages/pyramid/router.py", line 252, in invoke_request
request._process_response_callbacks(response)
File "/opt/rhodecode/store/da2il1f83gci4333j0sd256nji9nlhpa-python2.7-pyramid-1.10.4/lib/python2.7/site-packages/pyramid/request.py", line 83, in _process_response_callbacks
callback(self, response)
File "/opt/rhodecode/store/7a23dpzkkqnqmai1kx8wfnflmngr7q9x-python2.7-rhodecode-enterprise-ce-4.26.0/lib/python2.7/site-packages/rhodecode/lib/rc_beaker.py", line 40, in session_callback
self.persist()
File "/opt/rhodecode/store/bq0n2vs76d5c5yxwjab17a7pfgsrfr9x-python2.7-beaker-1.9.1/lib/python2.7/site-packages/beaker/session.py", line 823, in persist
self._session().save()
File "/opt/rhodecode/store/bq0n2vs76d5c5yxwjab17a7pfgsrfr9x-python2.7-beaker-1.9.1/lib/python2.7/site-packages/beaker/session.py", line 463, in save
self.namespace.acquire_write_lock(replace=True)
File "/opt/rhodecode/store/bq0n2vs76d5c5yxwjab17a7pfgsrfr9x-python2.7-beaker-1.9.1/lib/python2.7/site-packages/beaker/container.py", line 220, in acquire_write_lock
r = self.access_lock.acquire_write_lock(wait)
File "/opt/rhodecode/store/bq0n2vs76d5c5yxwjab17a7pfgsrfr9x-python2.7-beaker-1.9.1/lib/python2.7/site-packages/beaker/synchronization.py", line 186, in acquire_write_lock
x = self.do_acquire_write_lock(wait)
File "/opt/rhodecode/store/bq0n2vs76d5c5yxwjab17a7pfgsrfr9x-python2.7-beaker-1.9.1/lib/python2.7/site-packages/beaker/synchronization.py", line 261, in do_acquire_write_lock
filedescriptor = self._open(os.O_CREAT | os.O_WRONLY)
File "/opt/rhodecode/store/bq0n2vs76d5c5yxwjab17a7pfgsrfr9x-python2.7-beaker-1.9.1/lib/python2.7/site-packages/beaker/synchronization.py", line 242, in _open
filedescriptor = os.open(self.filename, mode)
OSError: [Errno 28] No space left on device: '/home/rhodecode/.rccontrol/community-1/data/sessions/lock/5/5a/5a4e4f9d514d72d417d9cff05380f5b798e93b33.lock
</code></pre><pre><code>$ rccontrol status
RHODECODE CONTROL VERSION: 1.24.3
- NAME: community-1
- STATUS: RUNNING
logs: /home/rhodecode/.rccontrol/community-1/community.log
- VERSION: 4.26.0 Community
- VCS: vcsserver-1
- URL: http://127.0.0.1:5000
- CONFIG: /home/rhodecode/.rccontrol/community-1/rhodecode.ini
- NAME: vcsserver-1
- STATUS: RUNNING
logs: /home/rhodecode/.rccontrol/vcsserver-1/vcsserver.log
- VERSION: 4.26.0 VCSServer
- URL: http://127.0.0.1:10010
- CONFIG: /home/rhodecode/.rccontrol/vcsserver-1/vcsserver.ini
</code></pre> RhodeCode CE/EE - Support #5677 (New): PR cross mergehttps://issues.rhodecode.com/issues/56772022-01-28T16:59:51ZJean-Michel Mazzocco
<p>Hello,</p>
<p>We have one case concerning the PR, we have 2 PR cross each other like this:<br>
PR 1 who merge branch "dev1" to "product1"<br>
PR 2 who merge branch "dev2" to "product1"</p>
<p>On the PR 2 we have this message <br>
"- This pull request cannot be merged because the target reference <code>product1</code> is missing."</p>
<p>The user of PR2 have remove the PR1 and the message still present on PR2<br>
He need to remove the PR2 and recreate a PR3</p>
<p>I don't known if this behavior is expected or not, and if we don't have a way not to be blocked and to redo the PRs</p>
<p>Thanks</p>
RhodeCode CE/EE - Bug #5672 (Resolved): Unable to browse git repository folders with # in nameshttps://issues.rhodecode.com/issues/56722021-12-16T16:00:28ZGreg Gaskill
<p>When browsing a git repository on our Rhodecode EE server web gui, we are unable to descend into folder whose names contain a # symbol.</p>
<p>An example browsing URI:</p>
<pre><code>https://example.com/projects/vendor/site/jobname/files/tip/Code/CP3%231?at=tip
</code></pre>
<p>Example error text for the above message says:</p>
<pre><code>error: There is no file nor directory at the given path: `Code/CP3` at commit xxxx
</code></pre>
<p>The actual folder name in the repository is "Code/CP#3"</p>
<p>Also note the actual rhodecode version running is 4.26 , not 4.24 (but the options didn't allow me to specify it)</p>
RhodeCode CE/EE - Bug #5670 (New): Repo-level administrators can usurp owner of repoistoryhttps://issues.rhodecode.com/issues/56702021-10-12T14:50:43ZYechen Qiao
<p>Not sure if this is a bug or a feature, but what I have found out is that any admins designated to be just a repo-level administrator (no repo group level admin and not super-admin), can modify the ownership of the repository to someone else. Even though in the access control page, the owners's rights looks unmodifiable.</p>