RhodeCode - issues: Issueshttps://issues.rhodecode.com/https://issues.rhodecode.com/favicon.ico?16960560042023-11-14T12:54:14ZRhodeCode - issues
Redmine RhodeCode CE/EE - Bug #5706 (Resolved): GIT: new commit cannot be made with parent that is NOT a ...https://issues.rhodecode.com/issues/57062023-11-14T12:54:14ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>Checking tests failures and it seem new commits cannot be made with a parent that is not a branch</p>
RhodeCode CE/EE - Bug #5621 (Resolved): LDAP + User Groups authentication plugin not working afte...https://issues.rhodecode.com/issues/56212020-06-15T05:42:55ZMichael Davis
<p>After upgrading our RhodeCode EE server to 4.19.3, the LDAP + User Groups authentication plugin no longer works for us. I get "invalid username/password" errors when trying to log in with an LDAP account. If I switch the server to the regular LDAP plugin, it works fine with the same settings.</p>
<p>The problem appears to have first occurred in 4.19.0. I tested this by updating a copy of our server from 4.18.3 (where the LDAP + Groups authentication plugin worked) to 4.19.0 (where it did not).</p>
<p>I see this error in the log file when the authentication failure occurs:</p>
<pre><code>2020-06-14 22:24:16.746 [15542] INFO [rhodecode.authentication.base] Authenticating user `mdavis` using egg:rhodecode-enterprise-ee#ldap_group plugin
2020-06-14 22:24:16.776 [15542] ERROR [rhodecode.rc_auth_plugins.auth_ldap_group] Other exception
Traceback (most recent call last):
File "rc_auth_plugins/auth_ldap_group.py", line 835, in rc_auth_plugins.auth_ldap_group.RhodeCodeAuthPlugin.auth
File "rc_auth_plugins/auth_ldap_group.py", line 295, in rc_auth_plugins.auth_ldap_group.AuthLdap.authenticate_ldap
AttributeError: 'AuthLdap' object has no attribute 'BASE_DN'
2020-06-14 22:24:16.783 [15542] WARNI [rhodecode.model.validators] user `mdavis` failed to authenticate
</code></pre> RhodeCode CE/EE - Bug #5517 (Resolved): Problem with upgrading to Community-4.15https://issues.rhodecode.com/issues/55172018-12-11T03:56:46ZLeonardo Ferreira Guimarães
<p>During the process of upgrading the Community-4.15 product, there is a check problem (MD5 check), the following information appears:</p>
<p>rccontrol self-update<br>
Falling back and looking at the MANIFEST<br>
Currently running RhodeCode Control version "1.21.0"<br>
Updating MANIFEST file with latest version from <a href="https://dls.rhodecode.com/linux/MANIFEST" class="external">https://dls.rhodecode.com/linux/MANIFEST</a></p>
<p>New version of Community:community-1 is available. Installed 4.14.1, 4.15.0 is available.</p>
<p>Latest version "1.21.0"<br>
No new version of RhodeCode Control available.</p>
<p>$ rccontrol self-update && rccontrol upgrade '*'<br>
Falling back and looking at the MANIFEST<br>
Currently running RhodeCode Control version "1.21.0"<br>
Updating MANIFEST file with latest version from <a href="https://dls.rhodecode.com/linux/MANIFEST" class="external">https://dls.rhodecode.com/linux/MANIFEST</a></p>
<p>New version of Community:community-1 is available. Installed 4.14.1, 4.15.0 is available.</p>
<p>Latest version "1.21.0"<br>
No new version of RhodeCode Control available.</p>
<p>Checking for available update for community-1 @ 4.14.1<br>
Upgrade to version 4.15.0 is available.<br>
Stopped community-1<br>
Downloading <a href="https://dls.rhodecode.com/linux/RhodeCodeCommunity-4.15.0+x86_64-linux_build20181210_2100.tar.bz2" class="external">https://dls.rhodecode.com/linux/RhodeCodeCommunity-4.15.0+x86_64-linux_build20181210_2100.tar.bz2</a> ...<br>
MD5 check failed. '/home/rhodecode/.rccontrol/cache/RhodeCodeCommunity-4.15.0+x86_64-linux_build20181210_2100.tar.bz2.tmp' should be '33319fb97a39d28a52c109fd9c5fd5e6' but got 'c0af1199b391917b84eef93552e58f1d'<br>
Traceback (most recent call last):<br>
File "/opt/rhodecode/store/aj0j6v1jkb76k62p0ss0xiay9llrs89b-python2.7-rhodecode-control-1.21.0/lib/python2.7/site-packages/rccontrol/upgrade.py", line 83, in main<br>
File "/opt/rhodecode/store/aj0j6v1jkb76k62p0ss0xiay9llrs89b-python2.7-rhodecode-control-1.21.0/lib/python2.7/site-packages/rccontrol/lib/context.py", line 2643, in upgrade<br>
File "/opt/rhodecode/store/aj0j6v1jkb76k62p0ss0xiay9llrs89b-python2.7-rhodecode-control-1.21.0/lib/python2.7/site-packages/rccontrol/lib/context.py", line 627, in upgrade<br>
File "/opt/rhodecode/store/aj0j6v1jkb76k62p0ss0xiay9llrs89b-python2.7-rhodecode-control-1.21.0/lib/python2.7/site-packages/rccontrol/lib/context.py", line 646, in upgrade_profile_link<br>
File "/opt/rhodecode/store/aj0j6v1jkb76k62p0ss0xiay9llrs89b-python2.7-rhodecode-control-1.21.0/lib/python2.7/site-packages/rccontrol/lib/context.py", line 249, in _get_app_path<br>
File "/opt/rhodecode/store/aj0j6v1jkb76k62p0ss0xiay9llrs89b-python2.7-rhodecode-control-1.21.0/lib/python2.7/site-packages/rccontrol/lib/context.py", line 861, in install<br>
File "/opt/rhodecode/store/aj0j6v1jkb76k62p0ss0xiay9llrs89b-python2.7-rhodecode-control-1.21.0/lib/python2.7/site-packages/rccontrol/lib/context.py", line 814, in download<br>
DownloadFailedChecksum: MD5 check failed. '/home/rhodecode/.rccontrol/cache/RhodeCodeCommunity-4.15.0+x86_64-linux_build20181210_2100.tar.bz2.tmp' should be '33319fb97a39d28a52c109fd9c5fd5e6' but got 'c0af1199b391917b84eef93552e58f1d'<br>
Rolling back to previous version.<br>
Auto starting community-1<br>
Checking for available update for vcsserver-1 @ 4.15.0<br>
Instance is at the latest known version.</p>
<p>Run 'rccontrol self-update' to check for new versions.<br>
Supervisord state is: RUNNING</p>
RhodeCode CE/EE - Bug #5434 (Resolved): Locale problemhttps://issues.rhodecode.com/issues/54342018-02-02T14:55:03ZNikolay Yankin
<p>Same problem as described here <a href="https://issues.rhodecode.com/issues/5297" class="external">https://issues.rhodecode.com/issues/5297</a> on Gentoo x64</p>
<p>Problem was appeared after upgrading from 4.9.1 to 4.11.1 (4.10.6 also affected)</p>
Documentation - Support #5423 (Resolved): API-Documentation for Method "create_repo_group" faultyhttps://issues.rhodecode.com/issues/54232018-01-22T13:39:57ZMalte Onnen
<p>Adding the group_description does not work as described in the Docs.</p>
<p>Api-Call from PowerShell:<br>
<code>Invoke-WebRequest https://rhodecode-url/_admin/api -Method Post -Body {"args":{"description":"testDescriptionWithoutBlanks","owner":2,"group_name":"testgrp"},"method":"create_repo_group","auth_token":"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa","id":1}</code><br>
I also tried: <br>
<code>Invoke-WebRequest https://rhodecode-url/_admin/api -Method Post -Body {"args":{"group_description":"testDescriptionWithoutBlanks","owner":2,"group_name":"testgrp"},"method":"create_repo_group","auth_token":"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa","id":1}</code></p>
<p>Expected Result: <br>
<code>}<br>
"id": 1,<br>
"result": {<br>
"repo_group": {<br>
"parent_group": null,<br>
"group_name": "testgrp",<br>
"group_description": "testDescriptionWithoutBlanks",<br>
"group_id": 12,<br>
"owner": "SUPERADMIN-USER",<br>
"repositories": []<br>
},<br>
"msg": "Created new repo group</code>testgrp<code>"<br>
},<br>
"error": null<br>
}</code></p>
<p>Actual Result:<br>
<code>{<br>
"id": 1,<br>
"result": {<br>
"repo_group": {<br>
"parent_group": null,<br>
"group_name": "testgrp",<br>
"group_description": "testgrp",<br>
"group_id": 12,<br>
"owner": "SUPERADMIN-USER",<br>
"repositories": []<br>
},<br>
"msg": "Created new repo group</code>testgrp<code>"<br>
},<br>
"error": null<br>
}<br>
</code></p>
Documentation - Task #5408 (Resolved): Upate nginx documentation for non standard SSL porthttps://issues.rhodecode.com/issues/54082017-12-02T16:04:42ZMaurice Müller
<p>I'm currently in an evaluation process for rhodecode. During my test setup it give me a headache that the given nginx example was not working fully in my set up (login and logout were getting a timeout although the user was logged in / out).</p>
<p>After a long search I figured out that the non standard SSL port was the issue. This can easily be fixed by replacng the following in the proxy.conf file (<a href="https://docs.rhodecode.com/RhodeCode-Enterprise/admin/nginx-tuning.html" class="external">https://docs.rhodecode.com/RhodeCode-Enterprise/admin/nginx-tuning.html</a>) :</p>
<p>replace:<br>
proxy_set_header Host $host;<br>
with:<br>
proxy_set_header Host $host:$server_port;</p>
<p>I hope this helps some other guys in the future ;)</p>
Documentation - Bug #5153 (Resolved): Documentation: /tmp permissions https://issues.rhodecode.com/issues/51532017-01-04T12:42:31ZSystems Administration
<p>Hello,<br>
in the documentation I'd suggest different permissions for the tmpfs-mounted <code>/tmp</code> directory: from</p>
<pre><code># mount tmp to memory with 2GB limit and 755 write permissions
</code></pre>
<p>to</p>
<pre><code># mount tmp to memory with 2GB limit and 1777 write permissions
</code></pre> RhodeCode CE/EE - Bug #4273 (Resolved): GIT executable not seen by vcsserverhttps://issues.rhodecode.com/issues/42732016-10-12T23:09:12ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>Reported by user. It seems git executable is not detected by vcsserver, and it's using the system one. In case there's NO git server it doesn't work.<br>
I'm not sure how this happened but the system somehow supposed to use the GIT from profile link, i think johannes explicitly removed git path from configuration.</p>
RhodeCode CE/EE - Task #4251 (Feedback): [customer] Pull request with subreposhttps://issues.rhodecode.com/issues/42512016-09-29T13:41:00ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>While a lot of time passed since we’ve exchanged emails last time, let me share some details about the way we work at R and what kind of Rhodecode improvements would be useful for us. </p>
<ul>
<li>Most of our iOS/Mac product repositories are Mercurial </li>
<li>We extensively use Mercurial’s subrepositories for internal dependencies: our internal libraries are Mercurial or git repositories, which are added to product repository as a subrepo. </li>
<li>I like github flow: creating feature branches (bookmarks in Mercurial), opening pull request to master (default), code-reviewing this pull request and merging it after review is finished</li>
</ul>
<p>Unfortunately Rhodecode does not allow to create pull request for Mercurial repository in case it contains any subrepo, even if there were no changes in that sub-repositories. </p>
<p>So that’s the main reason why we can’t use github flow with Rhodecode and that’s the reason why we have to Crucible. </p>
<p>I’ve shared these details with team about a year ago : <a href="https://rhodecode.tenderapp.com/help/discussions/support-tickets/1234-unable-to-create-pull-request" class="external">https://rhodecode.tenderapp.com/help/discussions/support-tickets/1234-unable-to-create-pull-request</a></p>
<p>Currently Rhodecode is more like a repository storage for us and while post-commit reviews are possible they are rarely used. That’s why most people at R almost never see Rhodecode web interface. </p>
<p>Let me know if you need any more details or have any workaround that would still allow us to use pull requests. </p>
RhodeCode CE/EE - Bug #4173 (Resolved): [ce, ee] mysql recycle pool timeout not workinghttps://issues.rhodecode.com/issues/41732016-08-12T16:41:27ZDaniel Ddaniel@rhodecode.com
<p>Replication:</p>
<ul>
<li>new config using mysql database</li>
<li>set mysql's wait_timeout to 6</li>
<li><code>threads = 1</code> in ini</li>
<li><code>sqlalchemy.db1.pool_recycle = 3</code> in ini</li>
<li>git push a repo (no changes need, just a push)</li>
<li>wait 7 seconds</li>
<li>git push again</li>
<li>get - <code>OperationalError: (OperationalError) (2006, 'MySQL server has gone away)</code></li>
</ul>
<p>This will also break subsequent requests with <code>StatementError: Can't reconnect until invalid transaction is rolled back</code></p>
RhodeCode CE/EE - Bug #4092 (Feedback): [ce, ee] Redmine/JIRA integrations - smart commitshttps://issues.rhodecode.com/issues/40922016-07-15T12:29:44ZDaniel Ddaniel@rhodecode.com
<p>For the redmine case there are 5 states for a ticket:</p>
<ul>
<li>new</li>
<li>in progress</li>
<li>resolved</li>
<li>feedback</li>
<li>closed'</li>
</ul>
<p>Commit messages should be able to auto close/resolve tickets using keywords such as <code>fixes #42</code></p>
<p>The thing to think about is that the user may want 'fixes #20' to set the redmine issue to any of 'resolved', 'feedback' or 'closed' - this should be set in the integration options.</p>
<p>Allowing custom multiple regex => state mappers per integration is the most powerful but might be overkill- making standard keywords might be better eg:</p>
<p>fixes => resolved<br>
closes => closed</p>
<p>Then again this might be no good for international users.</p>
RhodeCode Appenlight - Bug #3991 (Resolved): report logs need upper marginhttps://issues.rhodecode.com/issues/39912016-06-07T12:01:45ZLisa Quatmannlisa@rhodecode.com
<p>See attached; this text needs some padding around it.</p>
RhodeCode Appenlight - Bug #3989 (Resolved): even up report spacinghttps://issues.rhodecode.com/issues/39892016-06-07T12:00:03ZLisa Quatmannlisa@rhodecode.com
<p>See attached; note that the headers are closer to the report stats than they are to each other. Could use a little straightening out.</p>
RhodeCode CE/EE - Task #3454 (Feedback): [ce/ee] visually differentiate the two editionshttps://issues.rhodecode.com/issues/34542016-04-07T15:38:27ZOliver Strobeloliver@rhodecode.com
<p>Currently we are only changing the footer to include Community vs. Enterprise differentiation.</p>
<p>Purpose: It should be possible to tell the difference in edition quickly when switching between CE/EE tabs.</p>
<p>Potential solutions:<br>
1) Add the edition name into the header after the logo on the top left<br>
2) Change the colour of the header between editions, eg.<br>
CE = dark grey<br>
EE = black</p>
<p>Thoughts?</p>
RhodeCode CE/EE - Feature #2539 (Feedback): Recursive deletion of resourceshttps://issues.rhodecode.com/issues/25392015-08-25T18:11:48ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>Ticket from support: <a href="https://rhodecode.tenderapp.com/help/discussions/problems/7125-rc-225-after-deleting-repo-groups-on-file-system-then-rescan-the-repo-groups-are-always-in-the-db" class="external">https://rhodecode.tenderapp.com/help/discussions/problems/7125-rc-225-after-deleting-repo-groups-on-file-system-then-rescan-the-repo-groups-are-always-in-the-db</a></p>
<p>Use case:</p>
<ul>
<li>gemalto needs to often delete large repository groups, current system doesn't allow doing it from web interface</li>
<li>users need to delete manually each repo inside repo group and then delete the group itself</li>
</ul>
<p>Currently our system supports this operation in cleanup mode, so you can delete whole directory from the filesystem and run remap-and rescan. This is a workaround and should allow<br>
big cleanup, but it's far from being straightforward to do.</p>
<p>We need a consistent interface for deletion of resource that hold other resources. This should currently include two places</p>
<ul>
<li>user deletion (that hold repo groups/user groups/repositories)</li>
<li>repository group deletion (that hold other repositories)</li>
</ul>
<p>You can delete user or repository group in two ways, goind to admin > users or admin > repo groups and clicking delete.<br>
In case there are dependent objects, we should trigger a warning flash message, and redirect user to advanced settings section of user, or repo group. and allow them to do recursive delete.</p>
<p>There's already an interface for that in users advanced section, when you can select if you want to delete or transfer ownership of repositories or groups that user owns. <br>
We should re-use the logic, and make the same option available to deletion of repository groups. The user advanced section also needs some small improvements.</p>
<p>Recursive delete should have two options.</p>
<ul>
<li>delete resources</li>
<li>transfer ownership of resources to a different user in the system</li>
</ul>
<p>Currently part of that is implemented in user > settings > advanced where we have delete or detach option. <br>
Detach option unfortunetly picks the first super admin in the system which leads to<br>
odd results and you cannot control to whom you need to transfer the ownership.</p>