RhodeCode - issues: Issueshttps://issues.rhodecode.com/https://issues.rhodecode.com/favicon.ico?16960560042023-12-07T08:05:26ZRhodeCode - issues
Redmine RhodeCode CE/EE - Task #5711 (Resolved): svn: make the SSL detection work better.https://issues.rhodecode.com/issues/57112023-12-07T08:05:26ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>as per discussion here: <a href="https://community.rhodecode.com/t/svn-cant-move-a-file-http-502-bad-gateway/535/13" class="external">https://community.rhodecode.com/t/svn-cant-move-a-file-http-502-bad-gateway/535/13</a></p>
<p>check if the downgrade header can be there always to support http+https traffic</p>
RhodeCode CE/EE - Bug #5710 (Resolved): security: hide env vars on exception without debug modehttps://issues.rhodecode.com/issues/57102023-11-28T08:43:53ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>Currentt exceptions print out a docker env with a lot of secrets, this shoukd be only enabled via debug=true flag on .ini files...</p>
RhodeCode CE/EE - Bug #5709 (Resolved): SSL requirement with traefik for vcs seems to be brokenhttps://issues.rhodecode.com/issues/57092023-11-27T19:42:45ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>from user:</p>
<p>If I enable “Require SSL for vcs operations” in the Admin settings, I get an error 406 while trying to checkout through HTTPS. Is this expected with a Let’s Encrypt certificate?</p>
RhodeCode CE/EE - Bug #5708 (Resolved): fix password reset field mismatchhttps://issues.rhodecode.com/issues/57082023-11-25T06:46:48ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>when making a new user password field goes out of scope and breaks the </p>
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 #5699 (Resolved): Fix Agile pluginhttps://issues.rhodecode.com/issues/56992023-10-17T16:41:33ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>Seems after Redmine upgrade AGILE plugin broke some JS, try to download and upgrade the Agile plugin to sort that out</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 - 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 #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>