---
** [tickets:#8329] Add username hover cards in more places**
**Status:** open
**Milestone:** unreleased
**Created:** Wed Aug 28, 2019 07:54 PM UTC by Dave Brondsema
**Last Updated:** Wed Aug 28, 2019 07:54 PM UTC
**Owner:** nobody
`@username` mentions added the class=user-mention
t file upload code in Allura uses "attachment" classes (although you can go
more low-level than that). For one example, see BlogAttachment and
BlogAttachmentsController classes and their usages. There are a lot of parts,
but that might be a good example.
--
Dave Brondsema : d...@br
---
** [tickets:#8328] timeouts with LastCommit build**
**Status:** open
**Milestone:** unreleased
**Created:** Tue Aug 27, 2019 08:09 PM UTC by Dave Brondsema
**Last Updated:** Tue Aug 27, 2019 08:09 PM UTC
**Owner:** nobody
I've had to lower the `lcd_timeout` in forge-allura's .ini file
- **status**: review --> closed
- **Comment**:
Looks good, merged! I did notice the link text for merge requests wasn't too
great, so created [#8327] for that.
---
** [tickets:#8323] gsoc19 - Trigger notification task per each artifact
creation/modification and add tests**
**Status:**
UTC by Dave Brondsema
**Last Updated:** Tue Aug 27, 2019 03:26 PM UTC
**Owner:** nobody
Currently user notifications say:
> Your name was mentioned at 5d5c300707ae313e84dccf59 by John Doe
because its not implemented. Maybe refactor the 'title' value from `def index`
and use that. Actually: r
- **status**: review --> closed
---
** [tickets:#8324] gsoc19 - d1 - Writing documentation for user mentions
feature**
**Status:** closed
**Milestone:** unreleased
**Labels:** gsoc19
**Created:** Sun Aug 18, 2019 02:19 AM UTC by Shalitha Suranga
**Last Updated:** Mon Aug 19, 2019 04:39 PM
---
** [tickets:#8327] Implement link_text() or shorthand_id() for MergeRequest**
**Status:** open
**Milestone:** unreleased
**Created:** Tue Aug 27, 2019 03:26 PM UTC by Dave Brondsema
**Last Updated:** Tue Aug 27, 2019 03:26 PM UTC
**Owner:** nobody
Currently user notifications say
The response being a 302 redirect is normal, that's what happens after a form
submit, it redirects back to the wiki page. You can do `r = r.follow()` if you
want to continue to the page.
I wouldn't patch `send_user_mention_notification` though. We want that to run,
and then make assertions
Hey @pranav good to hear from you :) We don't have any Kubernetes or Helm
configs for Allura. Would be great if you wanted to contribute it! I haven't
done anything with Kubernetes myself, but I'm sure if you make an easy config
for it, it'd be easy to test out.
---
** [tickets:#8326]
- **status**: in-progress --> review
- **Comment**:
db/8325
---
** [tickets:#8325] Upgrade more packages**
**Status:** review
**Milestone:** unreleased
**Created:** Tue Aug 20, 2019 08:54 PM UTC by Dave Brondsema
**Last Updated:** Tue Aug 20, 2019 08:54 PM UTC
**Owner:** Dave Bronds
---
** [tickets:#8325] Upgrade more packages**
**Status:** in-progress
**Milestone:** unreleased
**Created:** Tue Aug 20, 2019 08:54 PM UTC by Dave Brondsema
**Last Updated:** Tue Aug 20, 2019 08:54 PM UTC
**Owner:** Dave Brondsema
---
Sent from forge-allura.apache.org because dev
A common pattern that we use in tests is like this:
```
h.set_context('test', 'wiki', neighborhood='Projects')
```
And then can use `c.project` and `c.app` variables just like "normal" non-test
code often does. `c.app` should be the wiki.
Also since there is such small amount of data in tests
That looks good @shalithasuranga
---
** [tickets:#8324] gsoc19 - d1 - Writing documentation for user mentions
feature**
**Status:** review
**Milestone:** unreleased
**Labels:** gsoc19
**Created:** Sun Aug 18, 2019 02:19 AM UTC by Shalitha Suranga
**Last Updated:** Mon Aug 19, 2019 03:45 PM
Looking good adding a test in `TestNotificationTasks` would be good. I
think with sample test data there, there should be a wiki `Page` artifact
created that you could query for. Or make a new artifact of some type. And
then use that to call `send_usermentions_notification`
And the
Good idea to add to https://forge-allura.apache.org/p/allura/wiki/Features/
It isn't a complete list of all the features, and is pretty brief about some
features, but that's ok. Still good to add this one. Maybe add a single
bullet point in either Issue Tracking or Threaded Discussion
Ah yea that makes sense, because post() will create a mongo document
representing the task and all its parameters, so the parameters have to be
something simple like strings/numbers/lists/etc and not model objects. (The
c.user and c.project and c.app models are automatically handled).
So I
I didn't notice this earlier, but all `send_usermentions_notification` usage
should be like `send_usermentions_notification.post(...)` The `post` is a
method automatically added by the `@task` decorator, and calling `post(...)`
makes it run via the background task queue instead of being run
I agree [#8294] will be too much work for now.
The recent tickets had test coverage for setting the preference. But no tests
for the sending the notification. Can you add a test for the
`send_usermentions_notification` task? I also am remembering now that the
send_usermentions_notification
---
** [tickets:#8322] Better from address than just "nore...@mysite.com"**
**Status:** open
**Milestone:** unreleased
**Created:** Thu Aug 08, 2019 09:22 PM UTC by Dave Brondsema
**Last Updated:** Thu Aug 08, 2019 09:22 PM UTC
**Owner:** nobody
Many places like `sendsimpl
- **status**: in-progress --> closed
---
** [tickets:#8284] gsoc19-c4: Implement the notification email sender**
**Status:** closed
**Milestone:** unreleased
**Labels:** gsoc19
**Created:** Wed May 08, 2019 03:03 PM UTC by Shalitha Suranga
**Last Updated:** Wed Aug 07, 2019 03:36 PM UTC
- **status**: review --> closed
---
** [tickets:#8285] gsoc19-c5: Add an area for user mentions notifications**
**Status:** closed
**Milestone:** unreleased
**Labels:** gsoc19
**Created:** Wed May 08, 2019 03:26 PM UTC by Shalitha Suranga
**Last Updated:** Thu Aug 08, 2019 09:17 PM UTC
Looks good, I've merged this and will close [#8284] also. What are you working
on next then? This is the last of the tickets you initially made, but I'm
thinking there should be some test coverage for this latest functionality
added. Your project proposal also mentions documentation and
And changes for steps 1, 2 and 3 look good.
---
** [tickets:#8285] gsoc19-c5: Add an area for user mentions notifications**
**Status:** in-progress
**Milestone:** unreleased
**Labels:** gsoc19
**Created:** Wed May 08, 2019 03:26 PM UTC by Shalitha Suranga
**Last Updated:** Tue Aug 06, 2019
I think linking to #notifications is good enough. If they aren't logged in,
and that part gets dropped its ok. Because I can't think of an obvious way to
make that work.
---
** [tickets:#8285] gsoc19-c5: Add an area for user mentions notifications**
**Status:** in-progress
**Milestone:**
ss/8285 looks fine
---
** [tickets:#8285] gsoc19-c5: Add an area for user mentions notifications**
**Status:** in-progress
**Milestone:** unreleased
**Labels:** gsoc19
**Created:** Wed May 08, 2019 03:26 PM UTC by Shalitha Suranga
**Last Updated:** Mon Aug 05, 2019 03:17 PM UTC
**Owner:**
- **status**: in-progress --> review
- **Comment**:
easywidgets:db/8320 (need to release it on pypi) and db/8320
---
** [tickets:#8320] Upgrade various packages**
**Status:** review
**Milestone:** unreleased
**Created:** Tue Jul 30, 2019 09:02 PM UTC by Dave Brondsema
**Last Updated:**
- **status**: in-progress --> review
- **Comment**:
db/8321
---
** [tickets:#8321] Unhandled error in Antispam class**
**Status:** review
**Milestone:** unreleased
**Created:** Wed Jul 31, 2019 02:53 PM UTC by Dave Brondsema
**Last Updated:** Wed Jul 31, 2019 02:53 PM UTC
**Owner:** D
---
** [tickets:#8321] Unhandled error in Antispam class**
**Status:** in-progress
**Milestone:** unreleased
**Created:** Wed Jul 31, 2019 02:53 PM UTC by Dave Brondsema
**Last Updated:** Wed Jul 31, 2019 02:53 PM UTC
**Owner:** Dave Brondsema
If a form submission uses our Antispam class
---
** [tickets:#8320] Upgrade various packages**
**Status:** in-progress
**Milestone:** unreleased
**Created:** Tue Jul 30, 2019 09:02 PM UTC by Dave Brondsema
**Last Updated:** Tue Jul 30, 2019 09:02 PM UTC
**Owner:** Dave Brondsema
---
Sent from forge-allura.apache.org because dev
- **status**: review --> in-progress
---
** [tickets:#8285] gsoc19-c5: Add an area for user mentions notifications**
**Status:** in-progress
**Milestone:** unreleased
**Labels:** gsoc19
**Created:** Wed May 08, 2019 03:26 PM UTC by Shalitha Suranga
**Last Updated:** Tue Jul 30, 2019 07:02 PM
* `allow_umnotif and True or False` is kinda confusing to me to read. How
about `bool(allow_umnotif)` instead?
* small grammar improvement: `Send a notification via e-mail if my username is
mentioned in somewhere` remove "in" so it is just `... mentioned somewhere`
* we should add an audit log
---
** [tickets:#8319] Website: make our own dedicated download page**
**Status:** open
**Milestone:** unreleased
**Labels:** asf
**Created:** Mon Jul 29, 2019 02:54 PM UTC by Dave Brondsema
**Last Updated:** Mon Jul 29, 2019 02:54 PM UTC
**Owner:** nobody
Instead of just release
Looks good!
---
** [tickets:#8284] gsoc19-c4: Implement the notification email sender**
**Status:** in-progress
**Milestone:** unreleased
**Labels:** gsoc19
**Created:** Wed May 08, 2019 03:03 PM UTC by Shalitha Suranga
**Last Updated:** Sun Jul 21, 2019 04:55 PM UTC
**Owner:** Shalitha
Good improvements. Was pretty easy to handle old_text for edits I see - nice.
I would also try to use `artifact.link_text()` in the email content, I think
that will add a lot of value in showing the thread title, etc. Instead of only
mount point name.
And the artifact_link URL isn't always
- **status**: in-progress --> review
- **Comment**:
db/8318
---
** [tickets:#8318] Admin option to generate password reset link**
**Status:** review
**Milestone:** unreleased
**Created:** Thu Jul 18, 2019 03:48 PM UTC by Dave Brondsema
**Last Updated:** Thu Jul 18, 2019 03:48 PM UTC
**Ow
---
** [tickets:#8318] Admin option to generate password reset link**
**Status:** in-progress
**Milestone:** unreleased
**Created:** Thu Jul 18, 2019 03:48 PM UTC by Dave Brondsema
**Last Updated:** Thu Jul 18, 2019 03:48 PM UTC
**Owner:** Dave Brondsema
It'd be helpful if site admins had
I am not sure what exactly I think would be best for notifications and
subscriptions, there are a lot of options. I guess I would recommend we start
simple and then as time allows add more towards the ideal best approach. If we
try to implement something special for all the different
The Apache Allura team is pleased to announce the release of Apache Allura
1.11.1
Allura is an open source implementation of a software forge, a web site that
manages source code repositories, bug reports, discussions, wiki pages, blogs,
and more for any number of individual projects.
Version
- **private**: Yes --> No
---
** [tickets:#8315] XSS when adding another user to a project**
**Status:** closed
**Milestone:** v1.11.1
**Created:** Wed Jul 10, 2019 03:55 PM UTC by Dave Brondsema
**Last Updated:** Mon Jul 15, 2019 03:27 PM UTC
**Owner:** nobody
When adding a u
Mass edit changing:
- **Milestone**: v1.11.1
ticket: tickets:#8299 More precise markdown @username regex
- **Milestone**: unreleased --> v1.11.1
ticket: tickets:#8317 Docker image for git/http not working for pushes
- **Milestone**: unreleased --> v1.11.1
ticket: tickets:#8300 Update to
The vote passes with 5 +1s from PMC members:
Shalitha Suranga
Simone Gatti
Rohan Verma
Dave Brondsema
Kenton Taylor
I'll publish the release, and make the updates and news announcements after it
gets on some of the release mirrors.
--
Dave Brondsema : d...@brondsema.net
http
+1
--
Dave Brondsema
> On Jul 12, 2019, at 5:36 AM, Rohan Verma wrote:
>
> +1
>
> On Fri, Jul 12, 2019 at 2:10 PM Simone Gatti
> wrote:
>
>> +1
>>
>> Il giorno ven 12 lug 2019 alle ore 09:38 Shalitha Suranga <
>> shalithasura...@gmail.com
Hi folks,
We've had several fixes committed since our 1.11.0 release, and some of them
fairly important, so I thought we should do a .1 bugfix release.
So this is a call for a vote on Apache Allura 1.11.1.
Source tarball, signature and checksums are available at:
- **status**: in-progress --> review
- **Comment**:
Fixed in db/8317
---
** [tickets:#8317] Docker image for git/http not working for pushes**
**Status:** review
**Milestone:** unreleased
**Created:** Thu Jul 11, 2019 05:31 PM UTC by Dave Brondsema
**Last Updated:** Thu Jul 11, 2019 05:31
---
** [tickets:#8317] Docker image for git/http not working for pushes**
**Status:** in-progress
**Milestone:** unreleased
**Created:** Thu Jul 11, 2019 05:31 PM UTC by Dave Brondsema
**Last Updated:** Thu Jul 11, 2019 05:31 PM UTC
**Owner:** Dave Brondsema
Since `allura/scm_config/git
Looks like a good start to this ticket. Here's some thoughts:
In `get_usernames_from_md`, the `usernames` variable should be a set instead of
a list, so if a username is mentioned multiple times, they don't get multiple
notifications.
Our email templates are markdown (and jinja), so might be
- **status**: in-progress --> review
- **Comment**:
Fix on db/8316
---
** [tickets:#8316] Award/accolades error if project is removed**
**Status:** review
**Milestone:** unreleased
**Created:** Wed Jul 10, 2019 04:14 PM UTC by Dave Brondsema
**Last Updated:** Wed Jul 10, 2019 04:17 PM
ibute 'url'
- ```
+```
---
** [tickets:#8316] Award/accolades error if project is removed**
**Status:** in-progress
**Milestone:** unreleased
**Created:** Wed Jul 10, 2019 04:14 PM UTC by Dave Brondsema
**Last Updated:** Wed Jul 10, 2019 04:14 PM UTC
**Owner:** Dave Brondsema
Error on `/p/_admin
---
** [tickets:#8316] Award/accolades error if project is removed**
**Status:** in-progress
**Milestone:** unreleased
**Created:** Wed Jul 10, 2019 04:14 PM UTC by Dave Brondsema
**Last Updated:** Wed Jul 10, 2019 04:14 PM UTC
**Owner:** Dave Brondsema
Error on `/p/_admin/accolades
Yea I think using the markdown conversion is good, so it matches exactly what
is rendered as links.
Another option using markdown would be to have `UserMentionExtension` record
the usernames as it processes them, instead of using BeautifulSoup later. But
I am not sure where it would save the
che
---
** [tickets:#8314] @memoize on methods should still allow garbage collection**
**Status:** review
**Milestone:** unreleased
**Created:** Wed Jul 03, 2019 08:14 PM UTC by Dave Brondsema
**Last Updated:** Wed Jul 03, 2019 08:14 PM UTC
**Owner:** Dave Brondsema
Our `@memoize` works pretty simila
---
** [tickets:#8314] @memoize on methods should still allow garbage collection**
**Status:** in-progress
**Milestone:** unreleased
**Created:** Wed Jul 03, 2019 08:14 PM UTC by Dave Brondsema
**Last Updated:** Wed Jul 03, 2019 08:14 PM UTC
**Owner:** Dave Brondsema
Our `@memoize` works
---
** [tickets:#8313] Make saved search cache expiry configurable, disable-able**
**Status:** in-progress
**Milestone:** unreleased
**Created:** Tue Jul 02, 2019 09:44 PM UTC by Dave Brondsema
**Last Updated:** Tue Jul 02, 2019 09:44 PM UTC
**Owner:** Dave Brondsema
Currently ticket saved
- **status**: review --> closed
- **assigned_to**: Shalitha Suranga
- **Reviewer**: Dave Brondsema
- **Comment**:
Nice, works better now :)
---
** [tickets:#8299] More precise markdown @username regex**
**Status:** closed
**Milestone:** unreleased
**Labels:** gsoc19
**Created:** Thu Jun
- **status**: in-progress --> review
- **Comment**:
db/8311
---
** [tickets:#8311] Split up and organize requirements.txt**
**Status:** review
**Milestone:** unreleased
**Created:** Wed Jun 26, 2019 10:04 PM UTC by Dave Brondsema
**Last Updated:** Wed Jun 26, 2019 10:04 PM UTC
**Ow
Looks good, merged, but we should add a test to ensure flash messages are
rendered properly.
---
** [tickets:#8312] Flash message regression due to TG upgrade **
**Status:** review
**Milestone:** unreleased
**Created:** Thu Jun 27, 2019 06:27 PM UTC by Kenton Taylor
**Last Updated:** Thu Jun
---
** [tickets:#8311] Split up and organize requirements.txt**
**Status:** in-progress
**Milestone:** unreleased
**Created:** Wed Jun 26, 2019 10:04 PM UTC by Dave Brondsema
**Last Updated:** Wed Jun 26, 2019 10:04 PM UTC
**Owner:** Dave Brondsema
Using `pip-compile` from https://pypi.org
Merged ss/8299
---
** [tickets:#8299] More precise markdown @username regex**
**Status:** open
**Milestone:** unreleased
**Labels:** gsoc19
**Created:** Thu Jun 06, 2019 04:31 PM UTC by Dave Brondsema
**Last Updated:** Wed Jun 26, 2019 04:28 PM UTC
**Owner:** nobody
If there exists a user
. That
is really a separate issue but similar. Not too critical, so can be dealt with
later if you wish.
---
** [tickets:#8299] More precise markdown @username regex**
**Status:** open
**Milestone:** unreleased
**Labels:** gsoc19
**Created:** Thu Jun 06, 2019 04:31 PM UTC by Dave Brondsema
**Last
- **status**: review --> closed
- **assigned_to**: Shalitha Suranga
- **Reviewer**: Dave Brondsema
- **Comment**:
Merged in https://forge-allura.apache.org/p/allura/git/merge-requests/329/
---
** [tickets:#8304] Higher resolution icons in user card**
**Status:** closed
**Milest
- **status**: open --> duplicate
- **Comment**:
Yes, this is currently true for ticket creators that are not members of a
project. [#4842] is for that issue. Project developers and admins of course
can edit tickets.
---
** [tickets:#8307] Cannot edit ticket**
**Status:** duplicate
- **status**: open --> closed
- **Comment**:
Project admins may configure their ticket trackers to have any number of custom
fields including type, priority, etc. On our self-hosted allura instance here,
we have opted for a simple approach without setting up those types of
classificiation
- **status**: open --> duplicate
- **Comment**:
Duplicate of [#8267]
---
** [tickets:#8306] Incorrect From header in emails from ticketing system**
**Status:** duplicate
**Milestone:** unreleased
**Created:** Wed Jun 19, 2019 04:21 PM UTC by Sebb
**Last Updated:** Wed Jun 19, 2019 04:22 PM
- **status**: open --> closed
- **assigned_to**: Dave Brondsema
- **Comment**:
https links fixed in [98a240]
The download page http://www.apache.org/dyn/closer.cgi/allura/ has instructions
about verifying those downloads.
---
** [tickets:#8305] Download links must use https**
**Sta
- **private**: Yes --> No
---
** [tickets:#8303] CVE-2019-10085: XSS on user autocomplete**
**Status:** closed
**Milestone:** v1.11.0
**Created:** Mon Jun 10, 2019 02:18 PM UTC by Dave Brondsema
**Last Updated:** Mon Jun 17, 2019 03:19 PM UTC
**Owner:** Dave Brondsema
Via se
CVE-2019-10085 Apache Allura XSS vulnerability in ticket user dropdown selector
Severity: Important
Versions Affected: 1.10.0 and earlier
Description:
A vulnerability exists for stored XSS on the user dropdown selector when
creating or editing tickets. The XSS executes when a user engages with
The Apache Allura team is pleased to announce the release of Apache Allura
1.11.0
Allura is an open source implementation of a software forge, a web site that
manages source code repositories, bug reports, discussions, wiki pages, blogs,
and more for any number of individual projects.
The
---
** [tickets:#8304] Higher resolution icons in user card**
**Status:** open
**Milestone:** unreleased
**Labels:** gsoc19
**Created:** Mon Jun 17, 2019 08:06 PM UTC by Dave Brondsema
**Last Updated:** Mon Jun 17, 2019 08:06 PM UTC
**Owner:** nobody
The user card uses an image with src
- **status**: in-progress --> closed
- **Comment**:
Done via https://forge-allura.apache.org/p/allura/git/merge-requests/328/
---
** [tickets:#8283] gsoc19-c3: Adding infotip for user mentions**
**Status:** closed
**Milestone:** unreleased
**Labels:** gsoc19
**Created:** Wed May 08, 2019
Mass edit changing:
- **Milestone**: v1.11.0
ticket: tickets:#8280 Faster spam controls in discussions
- **Milestone**: unreleased --> v1.11.0
ticket: tickets:#8274 Add optional HaveIBeenPwned checks for password changes
- **Milestone**: unreleased --> v1.11.0
ticket: tickets:#6440
The vote passes with 7 +1s from PMC members:
Heith Seewald
Shalitha Suranga
Rohan Verma
Deshani Geethika
Simone Gatti
Dave Brondsema
Kenton Taylor
And additional +1s from:
Ingo Hornberger
I'll publish the release, and make the updates and news announcements after it
gets on some of the release
t;>>
>>> On Fri, Jun 14, 2019 at 9:35 AM Ingo Hornberger wrote:
>>>
>>>> +1
>>>>
>>>> Shalitha Suranga schrieb am Fr., 14. Juni
>>>> 2019,
>>>> 02:24:
>>>>
>>>>> +1
>&
Hello,
We haven't made a release for many months, so I've started the process for our
next release. This is a call for a vote on Apache Allura 1.11.0.
Source tarball, signature and checksums are available at:
https://dist.apache.org/repos/dist/dev/allura/
Checksums:
SHA512:
regex**
**Status:** open
**Milestone:** unreleased
**Labels:** gsoc19
**Created:** Thu Jun 06, 2019 04:31 PM UTC by Dave Brondsema
**Last Updated:** Thu Jun 06, 2019 04:31 PM UTC
**Owner:** nobody
If there exists a user with username "foo" and some markdown content has
john...@foo.com
- **status**: in-progress --> review
- **Comment**:
db/8302
---
** [tickets:#8302] Screenshot caption inputs not clickable in chrome**
**Status:** review
**Milestone:** unreleased
**Created:** Fri Jun 07, 2019 04:04 PM UTC by Dave Brondsema
**Last Updated:** Fri Jun 07, 2019 04:04 PM
---
** [tickets:#8302] Screenshot caption inputs not clickable in chrome**
**Status:** in-progress
**Milestone:** unreleased
**Created:** Fri Jun 07, 2019 04:04 PM UTC by Dave Brondsema
**Last Updated:** Fri Jun 07, 2019 04:04 PM UTC
**Owner:** Dave Brondsema
The "sortable" event
Fixed on db/8301
---
** [tickets:#8301] Fix some issues with encoding in urls**
**Status:** review
**Milestone:** unreleased
**Created:** Thu Jun 06, 2019 10:34 PM UTC by Dave Brondsema
**Last Updated:** Thu Jun 06, 2019 10:34 PM UTC
**Owner:** Dave Brondsema
---
Sent from forge
---
** [tickets:#8301] Fix some issues with encoding in urls**
**Status:** review
**Milestone:** unreleased
**Created:** Thu Jun 06, 2019 10:34 PM UTC by Dave Brondsema
**Last Updated:** Thu Jun 06, 2019 10:34 PM UTC
**Owner:** Dave Brondsema
---
Sent from forge-allura.apache.org
- **status**: in-progress --> review
- **Comment**:
On branch db/8300 (and pypeline branch py3)
---
** [tickets:#8300] Update to py3-compatible Pypeline pkg**
**Status:** review
**Milestone:** unreleased
**Created:** Thu Jun 06, 2019 07:20 PM UTC by Dave Brondsema
**Last Updated:** Thu
---
** [tickets:#8300] Update to py3-compatible Pypeline pkg**
**Status:** in-progress
**Milestone:** unreleased
**Created:** Thu Jun 06, 2019 07:20 PM UTC by Dave Brondsema
**Last Updated:** Thu Jun 06, 2019 07:20 PM UTC
**Owner:** Dave Brondsema
---
Sent from forge-allura.apache.org
] Consider changing from html5lib sanitizer to bleach
sanitizer**
**Status:** open
**Milestone:** unreleased
**Created:** Wed Jun 05, 2019 02:34 PM UTC by Dave Brondsema
**Last Updated:** Wed Jun 05, 2019 02:34 PM UTC
**Owner:** nobody
https://bleach.readthedocs.io/en/latest/goals.html#bleach-vs
---
** [tickets:#8299] More precise markdown @username regex**
**Status:** open
**Milestone:** unreleased
**Labels:** gsoc19
**Created:** Thu Jun 06, 2019 04:31 PM UTC by Dave Brondsema
**Last Updated:** Thu Jun 06, 2019 04:31 PM UTC
**Owner:** nobody
If there exists a user with username
any
assertion errors.
---
** [tickets:#8298] Use jinja caching settings for EW core widgets**
**Status:** review
**Milestone:** unreleased
**Created:** Thu Jun 06, 2019 03:27 PM UTC by Dave Brondsema
**Last Updated:** Thu Jun 06, 2019 03:27 PM UTC
**Owner:** Dave Brondsema
During an upgr
---
** [tickets:#8298] Use jinja caching settings for EW core widgets**
**Status:** in-progress
**Milestone:** unreleased
**Created:** Thu Jun 06, 2019 03:27 PM UTC by Dave Brondsema
**Last Updated:** Thu Jun 06, 2019 03:27 PM UTC
**Owner:** Dave Brondsema
During an upgrade of EasyWidgets
ave Brondsema
**Last Updated:** Wed Jun 05, 2019 02:29 PM UTC
**Owner:** Dave Brondsema
```
Traceback (most recent call last):
File "/var/local/allura/Allura/allura/tasks/mail_tasks.py", line 64, in
route_email
msg = mail_util.parse_message(data)
File "/var/local/allura
---
** [tickets:#8297] Consider changing from html5lib sanitizer to bleach
sanitizer**
**Status:** open
**Milestone:** unreleased
**Created:** Wed Jun 05, 2019 02:34 PM UTC by Dave Brondsema
**Last Updated:** Wed Jun 05, 2019 02:34 PM UTC
**Owner:** nobody
https://bleach.readthedocs.io/en
In the config file you should be able to set for example
`user_prefs_storage.ldap.fields.email_address = emailAddr` if `emailAddr` is
the name of the field in ldap, of course change it if it is something different.
I think that should work, but we haven't tested all types of LDAP
- **status**: in-progress --> review
- **Comment**:
Fixed on db/8296
---
** [tickets:#8296] Regression on branches with "/" in name**
**Status:** review
**Milestone:** unreleased
**Created:** Tue Jun 04, 2019 07:29 PM UTC by Dave Brondsema
**Last Updated:** Tue Jun 04, 2019
Hi,
Is the `taskd` process running? That is used for background tasks like sending
mails.
https://forge-allura.apache.org/docs/getting_started/install_each_step.html#allura-task-processing
If it is running, check its log file to see what it outputs or if it has any
errors there.
The
- **status**: in-progress --> closed
---
** [tickets:#8295] error with latest EasyWidgets and debug=false**
**Status:** closed
**Milestone:** unreleased
**Created:** Tue Jun 04, 2019 03:52 PM UTC by Dave Brondsema
**Last Updated:** Tue Jun 04, 2019 07:53 PM UTC
**Owner:** nobody
.
Example on our own site here:
https://forge-allura.apache.org/p/allura/git/ci/rel/1.5.0/~/tree/CHANGES
---
** [tickets:#8296] Regression on branches with "/" in name**
**Status:** in-progress
**Milestone:** unreleased
**Created:** Tue Jun 04, 2019 07:29 PM UTC by Dave Brondsema
**La
---
** [tickets:#8296] Regression on branches with "/" in name**
**Status:** in-progress
**Milestone:** unreleased
**Created:** Tue Jun 04, 2019 07:29 PM UTC by Dave Brondsema
**Last Updated:** Tue Jun 04, 2019 07:29 PM UTC
**Owner:** nobody
Most likely a recent regression with
easywidgets:db/8295 and then we need to cut a 0.3.1 release for it
and then allura:db/8295
---
** [tickets:#8295] error with latest EasyWidgets and debug=false**
**Status:** in-progress
**Milestone:** unreleased
**Created:** Tue Jun 04, 2019 03:52 PM UTC by Dave Brondsema
**Last Updated
---
** [tickets:#8295] error with latest EasyWidgets and debug=false**
**Status:** in-progress
**Milestone:** unreleased
**Created:** Tue Jun 04, 2019 03:52 PM UTC by Dave Brondsema
**Last Updated:** Tue Jun 04, 2019 03:52 PM UTC
**Owner:** nobody
.ini settings of `debug = false` turn
ory: No such file or
> directory'
> >> begin captured stdout << -
> Running setup_app() from allura.websetup
>
This fails somewhat often so I made a small change in
https://forge-allura.apache.org/p/allura/git/ci/fd67f6c70b343696e1312226f947f0e3ef768c6d/
which hopefully will help avoid it.
--
Dave Brondsema : d...@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
<><
---
** [tickets:#8294] Style @username within editor**
**Status:** open
**Milestone:** unreleased
**Labels:** gsoc19
**Created:** Tue Jun 04, 2019 03:17 PM UTC by Dave Brondsema
**Last Updated:** Tue Jun 04, 2019 03:17 PM UTC
**Owner:** nobody
>From [#8282] https://forge-allura.apache.
- **status**: review --> closed
---
** [tickets:#8282] gsoc19-c2: Implement audocomplete list to selected users
for mentioning**
**Status:** closed
**Milestone:** unreleased
**Labels:** gsoc19
**Created:** Wed May 08, 2019 02:53 PM UTC by Shalitha Suranga
**Last Updated:** Wed May 29, 2019
feedback on https://forge-allura.apache.org/p/allura/git/merge-requests/327/
---
** [tickets:#8282] gsoc19-c2: Implement audocomplete list to selected users
for mentioning**
**Status:** review
**Milestone:** unreleased
**Labels:** gsoc19
**Created:** Wed May 08, 2019 02:53 PM UTC by
/8286/ has the commands
you'll need to run.
--
Dave Brondsema : d...@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
<><
- **status**: in-progress --> review
- **Comment**:
db/8290
---
** [tickets:#8290] Move previous_login_details to a separate collection**
**Status:** review
**Milestone:** unreleased
**Created:** Wed May 29, 2019 04:15 PM UTC by Dave Brondsema
**Last Updated:** Wed May 29, 2019 04:15 PM
401 - 500 of 2272 matches
Mail list logo
