<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ticket search results</title><link>https://forge-allura.apache.org/p/allura/tickets/</link><description>You searched for reported_by:$USER </description><language>en</language><lastBuildDate>Mon, 10 Jun 2024 15:31:45 -0000</lastBuildDate><item><title>500 when viewing pull request</title><link>https://forge-allura.apache.org/p/allura/tickets/7785/</link><description>*Originally created by:* jwb1980

https://sourceforge.net/p/forge/site-support/8792/

----

[forge:site-support:#8792]

----

https://sourceforge.net/p/sormula/code/merge-requests/2/ reports:
Error 500
We're sorry but we weren't able to process this request.

----

I was able to duplicate the reported issue:

I asked for some help the sog/eng IRC channel it was looked into and the following error was found:

mercurial.error:RepoLookupError: unknown revision 'c2f35c90ee417b785e6725d8507da86177c13dde' 
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Thu, 20 Aug 2015 22:06:09 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7785/</guid></item><item><title>Login failure with Tor Browser and NoScript extension</title><link>https://forge-allura.apache.org/p/allura/tickets/7782/</link><description>*Originally created by:* thimsmith

Current Tor Browser Bundle (Firefox ESR 31.2.0 (Tor Browser 4.0)) with current version of NoScript extension (2.6.9.2). Running on OS X 10.9.5. With the default Tor setup, one is immediately logged out after logging in to https://sourceforge.net/auth/.

Login works, since entering a wrong password shows the usual /auth/do_login "Invalid login" error. Using the correct password returns to http://sourceforge.net/ (not logged in).

I was unable to reproduce with stock Firefox.

Notice the request for `GET http://sourceforge.net/` half way through:

~~~~~
GET https://sourceforge.net/auth/ [HTTP/1.1 200 OK 3423ms]
[NoScript HTTPS] AUTOMATIC SECURE on https://sourceforge.net: sourceforge=38fb1da…REDACTED…W6nUu; domain=sourceforge.net; path=/; HttpOnly; Secure
[NoScript HTTPS] AUTOMATIC SECURE on https://sourceforge.net: _session_id=fbc2d561a…REDACTED…51a344aad1; domain=sourceforge.net; path=/; Secure
window.controllers is deprecated. Do not use it for UA detection. https-everywhere.js:342
downloadable font: download not allowed (font-family: "Ubuntu" style:normal weight:normal stretch:normal src index:0): status=2147500037
source: (invalid URI) css
GET https://googleads.g.doubleclick.net/pagead/viewthroughconversion/1002083962/ [HTTP/1.1 302 Found 1639ms]
[NoScript HTTPS] AUTOMATIC SECURE on https://googleads.g.doubleclick.net: test_cookie=CheckForPermission; domain=.doubleclick.net; path=/; Secure
GET https://www.google.com/ads/user-lists/1002083962/ [HTTP/1.1 200 OK 1977ms]
POST https://sourceforge.net/auth/do_login [HTTP/1.1 302 Found 4541ms]
[NoScript HTTPS] AUTOMATIC SECURE on https://sourceforge.net: allura-loggedin=true; domain=sourceforge.net; path=/; HttpOnly; Secure
[NoScript HTTPS] AUTOMATIC SECURE on https://sourceforge.net: sourceforge=3a2f3fc…REDACTED…lNlup1Lg==; domain=sourceforge.net; path=/; HttpOnly; Secure
[NoScript HTTPS] AUTOMATIC SECURE on https://sourceforge.net: _session_id=fbc2d561…REDACTED…a344aad1; domain=sourceforge.net; path=/; Secure
GET http://sourceforge.net/ [HTTP/1.1 200 OK 915ms]
window.controllers is deprecated. Do not use it for UA detection. https-everywhere.js:342
downloadable font: download not allowed (font-family: "Ubuntu" style:normal weight:normal stretch:normal src index:0): status=2147500037
source: (invalid URI) css
downloadable font: download not allowed (font-family: "Pictos" style:normal weight:normal stretch:normal src index:0): status=2147500037
source: (invalid URI)
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://a.fsdn.com/con/css/fonts/sftheme/pictos-web.woff. This can be fixed by moving the resource to the same domain or enabling CORS. pictos-web.woff
downloadable font: download failed (font-family: "Pictos" style:normal weight:normal stretch:normal src index:1): bad URI or cross-site access not allowed
source: http://a.fsdn.com/con/css/fonts/sftheme/pictos-web.woff
GET https://sb.scorecardresearch.com/p [HTTP/1.1 302 Moved Temporarily 1644ms]
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://a.fsdn.com/con/css/fonts/sftheme/pictos-web.ttf. This can be fixed by moving the resource to the same domain or enabling CORS. pictos-web.ttf
downloadable font: download failed (font-family: "Pictos" style:normal weight:normal stretch:normal src index:2): bad URI or cross-site access not allowed
source: http://a.fsdn.com/con/css/fonts/sftheme/pictos-web.ttf
[NoScript HTTPS] AUTOMATIC SECURE on https://sb.scorecardresearch.com: UID=38017039-95.100.139.120-1413932548; domain=.scorecardresearch.com; path=/; Secure
[NoScript HTTPS] AUTOMATIC SECURE on https://sb.scorecardresearch.com: UIDR=1413932548; domain=.scorecardresearch.com; path=/; Secure
GET https://sb.scorecardresearch.com/p2 [HTTP/1.1 200 OK 332ms]
~~~~~

If I either disable the NoScript extension, or fiddle around with the NoScript options (usually the "Reset" button will do the trick), the problem goes away and it allows me to log in.

~~~~~
GET https://sourceforge.net/auth/ [HTTP/1.1 200 OK 3258ms]
POST http://gb.symcd.com/ [HTTP/1.1 200 OK 1024ms]
POST http://gb.symcd.com/ [HTTP/1.1 200 OK 1867ms]
[NoScript HTTPS] AUTOMATIC SECURE on https://sourceforge.net: _session_id=e9550531…REDACTED…20def; domain=sourceforge.net; path=/; Secure
window.controllers is deprecated. Do not use it for UA detection. https-everywhere.js:342
GET https://fonts.googleapis.com/css [HTTP/1.1 200 OK 2249ms]
GET https://a.fsdn.com/allura/nf/1413560425/_ew_/_slim/css [HTTP/1.1 200 OK 625ms]
GET https://sourceforge.net/nf/tool_icon_css [HTTP/1.1 200 OK 2495ms]
GET https://a.fsdn.com/allura/nf/1413560425/_ew_/theme/sftheme/css/forge.css [HTTP/1.1 200 OK 2820ms]
GET https://googleads.g.doubleclick.net/pagead/viewthroughconversion/1002083962/ [HTTP/1.1 302 Found 3975ms]
POST http://clients1.google.com/ocsp [HTTP/1.1 200 OK 884ms]
POST http://vassg141.ocsp.omniroot.com/ [HTTP/1.1 200 OK 865ms]
POST http://clients1.google.com/ocsp [HTTP/1.1 200 OK 1250ms]
downloadable font: download not allowed (font-family: "Ubuntu" style:normal weight:normal stretch:normal src index:0): status=2147500037
source: (invalid URI) css
GET https://a.fsdn.com/allura/nf/1413560425/_ew_/theme/sftheme/images/sftheme/logo.png [HTTP/1.1 200 OK 3234ms]
GET https://a.fsdn.com/allura/nf/1413560425/_ew_/theme/sftheme/images/sftheme/sf-footer-logo.png [HTTP/1.1 200 OK 2274ms]
GET https://fonts.gstatic.com/s/ubuntu/v7/_xyN3apAT_yRRDeqB3sPRg.woff [HTTP/1.1 200 OK 2955ms]
POST http://clients1.google.com/ocsp [HTTP/1.1 200 OK 850ms]
[NoScript HTTPS] AUTOMATIC SECURE on https://googleads.g.doubleclick.net: test_cookie=CheckForPermission; domain=.doubleclick.net; path=/; Secure
GET https://www.google.com/ads/user-lists/1002083962/ [HTTP/1.1 200 OK 2573ms]
POST http://clients1.google.com/ocsp [HTTP/1.1 200 OK 832ms]
GET https://sourceforge.net/favicon.ico#-moz-resolution=16,16 [0ms]
POST https://sourceforge.net/auth/do_login [HTTP/1.1 302 Found 3023ms]
GET https://sourceforge.net/favicon.ico [HTTP/1.1 200 OK 2241ms]
[NoScript HTTPS] AUTOMATIC SECURE on https://sourceforge.net: allura-loggedin=true; domain=sourceforge.net; path=/; HttpOnly; Secure
[NoScript HTTPS] AUTOMATIC SECURE on https://sourceforge.net: sourceforge=2e3d43…REDACTED…CIh1Lg==; domain=sourceforge.net; path=/; HttpOnly; Secure
[NoScript HTTPS] AUTOMATIC SECURE on https://sourceforge.net: _session_id=e9550…REDACTED…720def; domain=sourceforge.net; path=/; Secure
GET https://sourceforge.net/ [HTTP/1.1 200 OK 4117ms]
[NoScript HTTPS] Secure cookie set by sourceforge.net: sourceforge=7d72c5…REDACTED…UQirdS4=; domain=sourceforge.net; path=/; HttpOnly; Secure
window.controllers is deprecated. Do not use it for UA detection. https-everywhere.js:342
GET https://a.fsdn.com/con/css/sf.css [HTTP/1.1 200 OK 1478ms]
GET https://a.fsdn.com/con/img/sftheme/favicon.ico [HTTP/1.1 200 OK 2049ms]
GET https://secure.gravatar.com/avatar/222a7d8f00720ce2bfe50d1297f81650 [HTTP/1.1 200 OK 2187ms]
GET https://c.fsdn.com/allura/p/miranda/icon [HTTP/1.1 200 OK 6218ms]
GET https://c.fsdn.com/allura/p/portableapps/icon [HTTP/1.1 200 OK 4530ms]
GET https://c.fsdn.com/allura/p/birtihubftype/icon [HTTP/1.1 200 OK 4246ms]
GET https://c.fsdn.com/allura/p/exo/icon [HTTP/1.1 200 OK 3089ms]
GET https://c.fsdn.com/allura/p/scummvm/icon [HTTP/1.1 200 OK 3846ms]
GET https://c.fsdn.com/allura/p/zabbix/icon [HTTP/1.1 200 OK 4418ms]
GET https://c.fsdn.com/allura/p/winpenpack/icon [HTTP/1.1 200 OK 3790ms]
GET https://c.fsdn.com/allura/p/reactos/icon [HTTP/1.1 200 OK 4352ms]
GET https://c.fsdn.com/allura/p/gnuplot/icon [HTTP/1.1 200 OK 6291ms]
GET https://c.fsdn.com/allura/p/clamav/icon [HTTP/1.1 200 OK 4008ms]
GET https://c.fsdn.com/allura/p/shareaza/icon [HTTP/1.1 200 OK 5040ms]
GET https://c.fsdn.com/allura/p/gretl/icon [HTTP/1.1 200 OK 4659ms]
GET https://c.fsdn.com/allura/p/tenfourfox/icon [HTTP/1.1 200 OK 5149ms]
Loading mixed (insecure) display content on a secure page "http://b.scorecardresearch.com/p?c1=2&amp;c2=6035546&amp;c3=&amp;c4=&amp;c5=&amp;c6=&amp;c15=&amp;cj=1"[Learn More] sourceforge.net
GET https://sb.scorecardresearch.com/p [HTTP/1.1 302 Moved Temporarily 4495ms]
An error occurred during a connection to secure.gravatar.com:443.

SSL received a record with an unknown content type.

(Error code: ssl_error_rx_unknown_record_type)

downloadable font: download not allowed (font-family: "Pictos" style:normal weight:normal stretch:normal src index:0): status=2147500037
source: (invalid URI)
GET https://a.fsdn.com/con/img/sftheme/logo.png [HTTP/1.1 200 OK 1007ms]
GET https://a.fsdn.com/con/img/sftheme/carbon.png [HTTP/1.1 200 OK 1104ms]
GET https://a.fsdn.com/con/img/sftheme/sf-footer-logo.png [HTTP/1.1 200 OK 977ms]
GET https://a.fsdn.com/con/css/fonts/sftheme/pictos-web.woff [HTTP/1.1 200 OK 1761ms]
POST http://gtssldv-ocsp.geotrust.com/ [HTTP/1.1 200 OK 970ms]
POST http://vassg141.ocsp.omniroot.com/ [HTTP/1.1 200 OK 912ms]
POST http://gtssldv-ocsp.geotrust.com/ [HTTP/1.1 200 OK 1774ms]
[NoScript HTTPS] AUTOMATIC SECURE on https://sb.scorecardresearch.com: UID=89d5dd3-2.23.107.120-1413933512; domain=.scorecardresearch.com; path=/; Secure
[NoScript HTTPS] AUTOMATIC SECURE on https://sb.scorecardresearch.com: UIDR=1413933512; domain=.scorecardresearch.com; path=/; Secure
GET https://sb.scorecardresearch.com/p2 [HTTP/1.1 200 OK 631ms]
~~~~~

The only real difference I spot is that the sourceforge= cookie value is much longer when it fails than when it succeeds, at least in this instance (384 chars vs. 244 chars, encoded).</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Wed, 25 Feb 2015 21:33:00 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7782/</guid></item><item><title>Type text is splitted in more lines if separated by spaces in bulk edit‏</title><link>https://forge-allura.apache.org/p/allura/tickets/7772/</link><description>*Originally created by:* zangune

Hi, even if in [Field Management][] I can read
 
&gt;Options (separate with spaces; **quote if containing spaces**; prefix with * to set a default)
 
and it works in [New Tickets][], it doesn't work well in [Bulk Edit][], so text is shown in more than one line and I can see quotes, too.
[[img src=BulkEditTypeSplittedIfSpacesExists.PNG]]
 
[Field Management]:https://sf.net/p/allura/admin/tickets/fields
[Bulk Edit]:http://sf.net/p/allura/tickets/edit/
[New Tickets]:http://sf.net/p/allura/tickets/new/
 </description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Thu, 20 Aug 2015 22:06:52 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7772/</guid></item><item><title>UnicodeDecodeError when generating code snapshot on hg repo</title><link>https://forge-allura.apache.org/p/allura/tickets/7757/</link><description>*Originally created by:* jwb1980

https://sourceforge.net/p/forge/site-support/8700/

----

[forge:site-support:#8700]


----

From IRC #sourceForge
download the source code of this project https://sourceforge.net/p/nhunspell/code/ci/default/tree/
3:55 When I try the snapshot Sourceforge says "We're having trouble finding that snapshot. Would you like to resubmit?"
3:55 TortoiseSVN gives me error 500 in my fork repository

----

</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Mon, 10 Aug 2015 15:21:59 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7757/</guid></item><item><title>Option to be able scroll by more than one page at once in history of commits and be able to jump to the oldest page.</title><link>https://forge-allura.apache.org/p/allura/tickets/7707/</link><description>*Originally created by:* blueflower100

Currently in history of commits you can only scroll by one page by clicking ''older'' and in browse commmits by clicking ''show more''. Still getting to the oldest commits can take very long if project has thousands of commits. So it would be very useful if there was an option to jump through few pages and even to the very first oldest page like you can on forums.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Sun, 08 Feb 2015 15:21:09 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7707/</guid></item><item><title>Attached images cannot be embedded in discussion forum posts</title><link>https://forge-allura.apache.org/p/allura/tickets/7691/</link><description>*Originally created by:* t_hoffmann

See for example https://sourceforge.net/p/texstudio/discussion/907840/thread/0363a1f4/#9611

I added an attachment named custom_build.png and the following source code: `[[img src=custom_build.png]]`

**Expected Result**: The image is shown within the post.

**Actual Result**: an empty placeholder appears instead of the actual image.

**Reason**: My code is converted to a relative url `./attachment/custom_build.png`. This expands to an absolute url of
`https://sourceforge.net/p/texstudio/discussion/907840/thread/0363a1f4/attachment/custom_build.png`

But the actual storage location seems to be 
`https://sourceforge.net/p/texstudio/discussion/907840/thread/0363a1f4/9611/attachment/custom_build.png`
Note the extra level `/9611`, which is missing when the relative url is translated to an absolute one.


</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Thu, 11 Oct 2018 08:06:22 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7691/</guid></item><item><title>git fork workflow improvement suggestions</title><link>https://forge-allura.apache.org/p/allura/tickets/7681/</link><description>*Originally created by:* zeromus

This was motivated by a user who wanted to delete a git fork, and needed guidance to find it in the user tools area. This is not an obvious thing at all and only makes sense if you understand the internal allura organization. It seemed there was a simpler way (item #4) we could direct him to it. The rest of these items I discovered while writing up #4
&lt;p&gt;
1. https://sourceforge.net/u/zeromus/profile/ : From this page, it is not clear that to _edit_ a tool, I have to pick [Add Tools]. The button should be called [Edit Tools] and one would assume that you can add tools from there. 
&lt;p&gt;
2. There should be a page you can generate for every installed tool which would just contain a list of commands--the same list of commands printed for every tool at https://sourceforge.net/u/zeromus/admin/tools . For example, https://sourceforge.net/u/zeromus/admin/my-git-fork/tools . This will be useful for item #4
&lt;p&gt;
3. For the git tool, https://sourceforge.net/u/zeromus/admin/tools there is no way to get to the actual fork page. This is odd, because from https://sourceforge.net/u/zeromus/profile/ , I could _only_ get to the actual fork page. There should be a command on the git tool called: Visit Fork Page
&lt;p&gt;
4. There is no way to way to delete a git fork from the fork's page. There is a little list of commands (fork, request merge), but some users expect the full assortment of commands (which are currently only visible from the tools administration page) to appear here. A simple way to effect this would be to add a link to the fork page called [ Config ] or [ Admin ] which would take you to the appropriate place in the tools administration. Now, the ideal destination for this link is the https://sourceforge.net/u/zeromus/admin/my-git-fork/tools described in item #2. If it goes to https://sourceforge.net/u/zeromus/admin/tools instead, then the user is forced to look through unrelated administration stuff before finding the options for the git repository/fork that he was just looking at. However... it's not the end of the world. </description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Thu, 26 Feb 2015 05:35:21 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7681/</guid></item><item><title>"Error 500" when saving SVN permissions #8522 </title><link>https://forge-allura.apache.org/p/allura/tickets/7675/</link><description>*Originally created by:* jwb1980

Support Ticket#: https://sourceforge.net/p/forge/site-support/8522/

Project: https://sourceforge.net/p/flightgear/admin/fgaddon/update

description:
Hi,

I try to set "permissions" for my SVN repo ( https://sourceforge.net/p/flightgear/fgaddon/ )

I'm able to access the setting page ( https://sourceforge.net/p/flightgear/admin/fgaddon/permissions ) and select groups, but when I press "Save" button I fallback on https://sourceforge.net/p/flightgear/admin/fgaddon/update where there is "Error 500 We're sorry but we weren't able to process this request."
Thus my settings are not saved.

This happened yesterday, before I was able to save permissions settings without problem but since yesterday I have this "Error 500" each time I press "Save" button.

I hope you will be able to help me to fix it because I really need to change the permissions on my SVN repo.

Regards,
Clément


Research:
Had IM conversation with Dave asked that I escalate this ticket to Engineering for code changes


</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:00 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7675/</guid></item><item><title>Project News and RSS feed are not synchronized</title><link>https://forge-allura.apache.org/p/allura/tickets/7638/</link><description>*Originally created by:* yellowjug

The project news and the related RSS feed on Sourceforge are not synchronized. If a comment is added to a news, this comment remains in the RSS feed even when removed. If a news is completely deleted, it remains in the RSS feed anyway. 

See my project as as example. News:
https://sourceforge.net/p/podcastgen/news/
and related Feed (contained comments and news that I deleted):
https://sourceforge.net/p/podcastgen/news/feed

This should be solved for the sake of coherence. The RSS news feed of a project should be always in sync with the actual news section.

NB.This issue was first found because of SPAM comments in the feed ( see also https://sourceforge.net/p/allura/tickets/7378/ )</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Tue, 15 Dec 2015 18:34:03 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7638/</guid></item><item><title>Email Subs</title><link>https://forge-allura.apache.org/p/allura/tickets/7630/</link><description>*Originally created by:* stamimail

Somtimes when I'm posting in a Project, I'm getting an EMail for my own post. (Instead only of others)
Can you let the user choose, if to get an Email for his own post or not?

In other words:
There some projects in SF that if I post a fourum (Bug/Feature Request) I get an Email for my post.
I want this will be disable. only others posts should be delivered to my Email.

Thanks
Stamimail</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Mon, 24 Nov 2014 06:18:30 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7630/</guid></item><item><title>suggestion: dont vanish [Create Ticket] button</title><link>https://forge-allura.apache.org/p/allura/tickets/7505/</link><description>*Originally created by:* zeromus

Instead of just vanishing the [Create Ticket] button for non-loggedin users on projects which require an authenticated user to create tickets, which confuses most users not savvy enough to already be logged in, put text which indicates that (maybe a hyperlink equivalent to login button) 

Or, just have the [Create Ticket] button take you to a login page when necessary. Most people will figure it out.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Tue, 19 Jan 2016 19:37:49 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7505/</guid></item><item><title>Show markdown syntax of pages without edit permission</title><link>https://forge-allura.apache.org/p/allura/tickets/7429/</link><description>*Originally created by:* r_x

The best way to learn a language is by example. Therefore every Allura Wiki page should have a link for displaying the markdown syntax of the currently displayed Wiki page. 

This would allow Allura users to learn from other Allura Wikis where they don't have an account nor edit permissions.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Thu, 22 Jan 2015 08:57:41 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7429/</guid></item><item><title>Need sys V init script for graceful shutdown of allura</title><link>https://forge-allura.apache.org/p/allura/tickets/7411/</link><description>*Originally created by:* jdt20010

Unable to locate init scripts for allura for startup and graceful shutdown of the allura application.  Will your team provide /etc/init.d scripts in a future release, or as an add-on to the allura vm?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Sun, 02 Nov 2014 16:59:49 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7411/</guid></item><item><title>Improving LDAP registration methods</title><link>https://forge-allura.apache.org/p/allura/tickets/7406/</link><description>*Originally created by:* ifreeman

The use case I had in mind when using ldap auth was for an enterprise environment where there is already an existing ldap server containing existing user accounts. Users would register by providing their ldap credentials and Allura would authenticate them against ldap and then automatically provision their account. Even better if all this would happen simply by logging in (bypassing registration altogether).

But it seems the ldap plugin author had a different use case in mind: a local ldap server that is only managing accounts for this Allura instance. When registering an account on Allura, an admin account on the ldap server is used to create a new ldap object for the username in the domain. It is not possible to register an account without the ldap's admin account.

I believe the existing functionality to be contrary to the wishes of most enterprise installations.

I propose the attached patch to *./Allura/allura/lib/plugin.py* to accomplish the following:
- Add a new *registration.method = ldap* to repurpose the existing behavior (creating a new ldap account upon allura registration, error if exists in ldap)
- Repurpose the existing *registration.method = local* configuration to be used in conjunction with *auth.method = ldap* as follows:
    1. authenticate against ldap with an *existing* user
    2. create local account in allura with the provided and ldap-authenticated username
    3. use ldap to authenticate future logins

This being my first experience with python and this project I have not yet found the best way I should extend widgets/auth_widgets.py to be able to display errors to the user on the registration page. There are a great number of error conditions that should not be throwing exceptions (for such common occurances as an invalid password). Can any of you point me in the right direction/take it from here?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:00 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7406/</guid></item><item><title>[Allura|Bug] - Typo found in initial Git command description.</title><link>https://forge-allura.apache.org/p/allura/tickets/7403/</link><description>*Originally created by:* valhalam

When creating a new project, if you click on the code tab once it has been created, you get redirected to /p/\&lt;projectname\&gt;/code/ref/master. A typo is found under "First time using Git" section.

See attached screenshot.

Typo:
\# add all your files.  Use can use specific filenames or directories instead of '.'

Expected result:
\# add all your files.  **User** can use specific filenames or directories instead of '.'</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Mon, 24 Aug 2015 16:21:30 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7403/</guid></item><item><title>text area on create ticket screen should not allow horizontal resize</title><link>https://forge-allura.apache.org/p/allura/tickets/7327/</link><description>*Originally created by:* vampire0

The text area on the create ticket screen allows horizontal and vertical resize.
horizontal though breaks the design.
If you make it wider than the design, the text area is only displayed partially and without scrollin opportunity.
If you make it narrower than intended, the lower Preview button appears on the left of the text area. (Maybe this should prevented additionally in case a browser doesn't respect that only vertical resize is allowed.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Mon, 17 Aug 2015 21:15:06 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7327/</guid></item><item><title>Uninitialized git repo allows forking.</title><link>https://forge-allura.apache.org/p/allura/tickets/7325/</link><description>*Originally created by:* algorithms

Uninitialized repositories should not allow you to for them since you cannot create a merge request for an uninitialized repository.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:00 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7325/</guid></item><item><title>Fix incorrect div width on URL shortening tool</title><link>https://forge-allura.apache.org/p/allura/tickets/7324/</link><description>*Originally created by:* jarmour

I noticed that the top div with class="grid-20 pad" at the top of the page on http://sourceforge.net/p/sfu/url/ is too short and cutting off functionality. Please make this bigger or reformat the display to see all  contents of div.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:00 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7324/</guid></item><item><title>NetBeans Allura Ticket System Support</title><link>https://forge-allura.apache.org/p/allura/tickets/7312/</link><description>*Originally created by:* puce

I created an issue for NetBeans to support the Allura Ticketing system:
https://netbeans.org/bugzilla/show_bug.cgi?id=243557

I created this issue to track that 3rd part issue.

Maybe the Allura team could contribute this Allura integration.

</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Sun, 15 Mar 2015 14:27:17 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7312/</guid></item><item><title>Option to modify tickets by tickets creators</title><link>https://forge-allura.apache.org/p/allura/tickets/7302/</link><description>*Originally created by:* blueflower100

Could you add option to modify tickets by tickets creators.Currently users can edit comments but it seems tickets can be edited only by project members.Users who created those tickets cant edit them.It would be very useful for someone who want to add additional informations to tickets.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Tue, 01 Apr 2014 14:25:36 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7302/</guid></item><item><title>Project feed doesn't show commits with correct/usable date/time stamp</title><link>https://forge-allura.apache.org/p/allura/tickets/7299/</link><description>*Originally created by:* manuelbi

E.g. at this moment: https://sourceforge.net/p/openmsx/openmsx/feed shows latest commits of 24-03-14.... they all have the same date and time there. But the actual commits have different dates and have a different order. See the git log e.g. at https://sourceforge.net/p/openmsx/openmsx/commit_browser

&lt;ctsai-sf\&gt; Hmm, I have a suspicion, let me know if this sounds feasible with your situation.
&lt;ctsai-sf\&gt; I’m thinking that the feed is generated with timestamps based on when the data is scanned/entered into the Allura system, whereas the code browser’s data is generated from the data in the git log.
&lt;Quibus\&gt; it seems that the timestamps of the feed are not correct either
&lt;ctsai-sf\&gt; ie., if you made a number of commits before pushing, all those commits will have commits based on the push time
&lt;ctsai-sf\&gt; In the feed that is.
&lt;Quibus\&gt; But they were not pushed at the same time, because the last commit is from someone else
&lt;ctsai-sf\&gt; Hmm…
&lt;ctsai-sf\&gt; I mean, even if my suspicion is correct, that’s probably not ideal handling, and we should look into changing the behavior. But just trying to get at the root of what’s going on here.

&lt;ctsai-sf\&gt; Sounds like our options so far are:
&lt;ctsai-sf\&gt; 1) change pubdate to match commit time, though that doesn’t comply with RSS spec (atom seems okay though)
&lt;ctsai-sf\&gt; 2) add a new “dc:date” field, but that would only be useful for customized feed readers
&lt;ctsai-sf\&gt; 3) add more info to the description for a feed item, ie., the actual commit date and possibly more than the first line of the commit msg.


&lt;ctsai-sf\&gt; That was the last on your topic Quibus.
&lt;Quibus\&gt; As a plain user, I'd expect both the dates and the order to be the same as the git log, that's all I can say, I guess
&lt;Quibus\&gt; I'll check with the guy who mentioned this (who wrote our IRC bot based on the feed)

&lt;Quibus\&gt; &lt;FiXato\&gt; Feedzirra supports Atom feeds afaik, so option 1 would be fine for me :-)
&lt;Quibus\&gt; &lt;FiXato\&gt; option 2 could also be implemented into the bot I guess, but might be more work
&lt;Quibus\&gt; &lt;FiXato\&gt; not sure how 3 will fix the ordering


&lt;ctsai-sf\&gt; To be clear, not really sure if any of those would fix the ordering.
&lt;Quibus\&gt; FiXato: good, you joined just in time to miss nothing
&lt;Quibus\&gt; FiXato: do you use the order of the items in the feed, or do you look at a date in the bot?
&lt;Quibus\&gt; (I mean: do you look at some date field in the feed for using in the bot to determine what is the latest)
&lt;FiXato\&gt; but regardless of what default order the library returns, I should fairly easily be able to sort by each item's date.
&lt;ctsai-sf\&gt; Given that, personally I’d like to see a combination of my 2 and 3 from before. Since I’d rather not depart from published spec without very good reason. But also, I’m neither affected by this bug, nor someone who’d be fixing it…
&lt;FiXato\&gt; yeah, looks like feedjirra sorts entries by their published date. So I would guess that going for option 1, changing pubdate to commit time would solve the issue in our case.
&lt;FiXato\&gt; even adding another field, if that is allowed per RSS standard, would be sufficient for us I think; just would need a bit more work on the bot.

</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Sat, 14 Mar 2015 04:52:52 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7299/</guid></item><item><title>Support for OAuth 2.0 - NEEDS INDEX</title><link>https://forge-allura.apache.org/p/allura/tickets/7272/</link><description>*Originally created by:* blueflower100

Could you add support for OAuth 2.0 in Sourceforge.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Mon, 10 Jun 2024 15:31:45 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7272/</guid></item><item><title>More advanced network graph design.</title><link>https://forge-allura.apache.org/p/allura/tickets/7243/</link><description>*Originally created by:* blueflower100

Network graph on Sourceforge has very simplistic design more advanced graph feature would be useful for example searching commits based on keywords,more detailed descriptions of commits, statistics which fork has most commits/merge requests notifications on forks and option to send messages to forkers  and fork management.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Sun, 01 Feb 2015 06:13:23 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7243/</guid></item><item><title>Contributors, Code Frequency, Commit Activity Graphs</title><link>https://forge-allura.apache.org/p/allura/tickets/7242/</link><description>*Originally created by:* blueflower100

Could you add Contributors, Code Frequency , Commit Activity Graphs similar to the ones on Github they would be very useful.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Thu, 11 Oct 2018 08:23:36 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7242/</guid></item><item><title>Option to review and compare diffrent commits and branches/forks and to add comments to commits. </title><link>https://forge-allura.apache.org/p/allura/tickets/7241/</link><description>*Originally created by:* blueflower100

Could you add option to compare side by side diffrent commits and branches/forks it would be especially helpful in Git based projects also option to add comments to commits would be useful.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Fri, 20 Feb 2015 17:59:54 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7241/</guid></item></channel></rss>