RhodeCode - issues: Issueshttps://issues.rhodecode.com/https://issues.rhodecode.com/favicon.ico?16960560042016-10-14T18:34:09ZRhodeCode - issues
Redmine RhodeCode CE/EE - Bug #4279 (Resolved): re-captcha validation is brokenhttps://issues.rhodecode.com/issues/42792016-10-14T18:34:09ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>re-captcha on EE doesn't work and validate the input...</p>
RhodeCode CE/EE - Bug #4277 (Resolved): [frontend] System info page does not work correctly in sa...https://issues.rhodecode.com/issues/42772016-10-13T13:04:34ZMartin Bornholdmartin@rhodecode.com
<p>I noticed that the system info page (<a href="http://localhost:5000/_admin/settings/system" class="external">http://localhost:5000/_admin/settings/system</a>) does not work correctly on safari. If i open it, the whole "System Info" container is empty.<br>
Looks like also the full text serach page is affected (<a href="http://localhost:5000/_admin/settings/search" class="external">http://localhost:5000/_admin/settings/search</a>)</p>
<p>Tested on:</p>
<ul>
<li>OSX 10.11.6 (15G31)</li>
<li>Safari Version 9.1.2 (11601.7.7)</li>
<li>RhodeCode CE <a href="https://internal-code.rhodecode.com/rhodecode-enterprise-ce/changeset/0dd9ca245933267ffef10fec800185c854a285ee" class="external">https://internal-code.rhodecode.com/rhodecode-enterprise-ce/changeset/0dd9ca245933267ffef10fec800185c854a285ee</a></li>
</ul>
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 - Bug #4271 (Resolved): Browsing new repository groups via SVN issuehttps://issues.rhodecode.com/issues/42712016-10-10T23:08:39ZBert Zahniser
<p>When creating a new repository group and a new repository under that group, it is not available via an SVN connection until the apache2 service is reloaded/restarted. The group creation successfully updates the apache configuration file as outlined here: <a href="https://docs.rhodecode.com/RhodeCode-Enterprise/release-notes/release-notes-4.3.0.html?highlight=svn" class="external">https://docs.rhodecode.com/RhodeCode-Enterprise/release-notes/release-notes-4.3.0.html?highlight=svn</a>, but apache2 does not load the updated file until a reload/restart is issued. Can the server also reload the apache2 configuration when this file is changed?</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 #4247 (Resolved): [vcs] Using current time as timestamp during archive crea...https://issues.rhodecode.com/issues/42472016-09-27T16:55:41ZMartin Bornholdmartin@rhodecode.com
<p>Our code uses the current time as modification timestamp when creating repository archives. This leads to different hash values (e.g. md5sum) of the created archive files although no code was changes. This is the reason why we had to chenge the hash of rhodecode-tools repository several times.</p>
RhodeCode CE/EE - Support #4244 (Resolved): mod_dav_svn template error when using auth_realm with...https://issues.rhodecode.com/issues/42442016-09-26T14:48:45ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>[tenderapp] report: <a href="https://rhodecode.tenderapp.com/help/discussions/problems/9626" class="external">https://rhodecode.tenderapp.com/help/discussions/problems/9626</a> reported by user: <a href="mailto:gildas.fargeas@nerd.nintendo.com">gildas.fargeas@nerd.nintendo.com</a></p>
<p>Hi,<br>
i've noticed this small bug in the template you use for mod_dav_svn.conf. When the HTTP[S] authentication realm (set up in global settings page) is using multiple words separated with a space, the mod_dav_svn.conf file does not quote the name in the configuration resulting in an apache crash. </p>
<p>Additionnally, when using special characters there, these are converted to html so you should make sure the resulting string is not causing a potential error (or forbid special characters in the text input :) ).</p>
<p>I've quick-fixed it by quoting the ${rhodecode_realm} in the mako template located in /opt/rhodecode/store/bc6w8dzvdcs6dixi83cs32rbaj5zyz67-python2.7-rhodecode-enterprise-ce-4.4.0/lib/python2.7/site-packages/rhodecode/svn_support/templates/mod-dav-svn.conf.mako </p>
<p>That's it.</p>
RhodeCode CE/EE - Support #4243 (Resolved): Gist visibility update?https://issues.rhodecode.com/issues/42432016-09-26T12:47:50ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>[tenderapp] report: <a href="https://rhodecode.tenderapp.com/help/discussions/questions/33218" class="external">https://rhodecode.tenderapp.com/help/discussions/questions/33218</a> reported by user: <a href="mailto:rhodecode@x.keshi.org">rhodecode@x.keshi.org</a></p>
<p>When I edit an existing public gist entry, it always turns into a private gist without any indications. And there seems no way to change the visibility of gists from private to public. Is this an intended behavior?</p>
<p>Confirmed with my own RhodeCode CE 4.3.1 installation and <a href="https://code.rhodecode.com" class="external">https://code.rhodecode.com</a>.</p>
<p>How to reproduce:</p>
<ol>
<li>Sign in to <a href="https://code.rhodecode.com/" class="external">https://code.rhodecode.com/</a>.</li>
<li>Open <a href="https://code.rhodecode.com/_admin/gists/new" class="external">https://code.rhodecode.com/_admin/gists/new</a>.</li>
<li>Fill anything in the body and push "Create Public Gist" button. </li>
<li>Push "Edit" button.</li>
<li>Push "Update Gist" button.</li>
</ol>
<p>Expected result:</p>
<ul>
<li>The gist entry should remain public.</li>
</ul>
<p>Actual result:</p>
<ul>
<li>The gist entry turns into "Private Gist".</li>
</ul>
RhodeCode CE/EE - Task #4237 (Resolved): Enable HTTP supporthttps://issues.rhodecode.com/issues/42372016-09-21T16:24:18ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>We must enable http support by default. We need to make sure that the defaults are now NOT pyro4 but the http backends. It means that commented out .ini settings should now default into http mode for hooks, scm_app, and server. </p>
<ul>
<li>we need to make sure http mode is used for testing</li>
<li>we should make sure that any auto-runned vcsserver is in http mode not pyro</li>
<li>http mode should be in default config so even with things commented in the .ini the default mode should be http</li>
</ul>
RhodeCode CE/EE - Task #4203 (Resolved): Get rid of svn.proxy.parent_path_root, and replace it wi...https://issues.rhodecode.com/issues/42032016-08-29T19:35:40ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>the SVN setting: svn.proxy.parent_path_root is not required and actually makes configuration much harder. We have this stored inside the database the event should read this setting instead.</p>
RhodeCode CE/EE - Bug #4127 (Closed): auth_cache_ttl settings are not correctly storedhttps://issues.rhodecode.com/issues/41272016-07-26T12:12:15ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p><a href="https://internal-code.rhodecode.com/rhodecode-enterprise-ce/files/tip/rhodecode/authentication/base.py#L568" class="external">https://internal-code.rhodecode.com/rhodecode-enterprise-ce/files/tip/rhodecode/authentication/base.py#L568</a></p>
<p>Seems if you set this inside the web interface it's not correctly stored, and cache_ttl is always 0</p>
<p>It's again issue with settings naming/storing for auth-plugins i think it happened not for the first time. Could we additionally do a sanity check for all the auth-plugin settings and make sure values are correctly stored ?</p>
RhodeCode CE/EE - Support #4104 (Closed): Switch to commit in file view PBhttps://issues.rhodecode.com/issues/41042016-07-18T16:06:35ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>[tenderapp] report: <a href="https://rhodecode.tenderapp.com/help/discussions/problems/9564" class="external">https://rhodecode.tenderapp.com/help/discussions/problems/9564</a> reported by user: <a href="mailto:alexis.jeandet@lpp.polytechnique.fr">alexis.jeandet@lpp.polytechnique.fr</a></p>
<p>Hi,</p>
<p>When we browse our repository in the file view, the "switch to commit" combo box seems to redirect us to a bad address.</p>
<p>With this repository(public):<br>
<a href="https://hephaistos.lpp.polytechnique.fr/rhodecode/HG_REPOSITORIES/LPP/INSTRUMENTATION/USERS/JEANDET/qtcharts" class="external">https://hephaistos.lpp.polytechnique.fr/rhodecode/HG_REPOSITORIES/LPP/INSTRUMENTATION/USERS/JEANDET/qtcharts</a><br>
jumping to 5.6 branch redirects to:<br>
<a href="https://hephaistos.lpp.polytechnique.fr/rhodecode/qtcharts/files/5.6/?at=5.6" class="external">https://hephaistos.lpp.polytechnique.fr/rhodecode/qtcharts/files/5.6/?at=5.6</a><br>
instead of:<br>
<a href="https://hephaistos.lpp.polytechnique.fr/rhodecode/HG_REPOSITORIES/LPP/INSTRUMENTATION/USERS/JEANDET/qtcharts/files/5.6/?at=5.6" class="external">https://hephaistos.lpp.polytechnique.fr/rhodecode/HG_REPOSITORIES/LPP/INSTRUMENTATION/USERS/JEANDET/qtcharts/files/5.6/?at=5.6</a></p>
<p>It just skip all the sub-repositories in the path.</p>
<p>Best regards,<br>
Alexis.</p>
RhodeCode CE/EE - Bug #4048 (Closed): saving form with wrong values on LDAP raises 500 errorhttps://issues.rhodecode.com/issues/40482016-06-27T22:14:23ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>Basically failing test is: test_ldap_error_form_wrong_port_number, we should fix it it's a release blocker</p>
RhodeCode CE/EE - Bug #3950 (Resolved): [ce, ee] trying to merge pr against a deleted branch/book...https://issues.rhodecode.com/issues/39502016-05-20T12:35:41ZDaniel Ddaniel@rhodecode.com
<p>reproduce steps:</p>
<ul>
<li>create PR against a bookmark/branch</li>
<li>delete bookmark/branch in the target repository</li>
<li>try merge the PR or even just opening the PR page again</li>
</ul>
<p>reproduce steps:</p>
<ul>
<li>create a PR from a bookmark in a fork to the base repo</li>
<li>remove the bookmark in the fork</li>
<li>Observe: Message that an unknown exception occured</li>
<li>Expect: Understandable message that the source bookmark does not exist anymore. (compare missing source commits)</li>
</ul>
<p>ae report:<br>
<a href="https://internal-code.rhodecode.com/dan/rhodecode-enterprise-ce-dan/pull-request/2229" class="external">https://internal-code.rhodecode.com/dan/rhodecode-enterprise-ce-dan/pull-request/2229</a></p>
RhodeCode CE/EE - Feature #1055 (Resolved): [pr, vcs] Expose the shadow repository of a pull requesthttps://issues.rhodecode.com/issues/10552015-02-05T15:45:55ZJohannes Bornholdjohannes@rhodecode.com
<p>The idea: Since we have a shadow repository which we use to find out if a merge operation would be successful, we can expose this repository so that a CI server could fetch directly the merge result out of this Shadow and run the tests based on this.</p>