[allura:tickets] #8558 user email changes not getting into solr
---
**[tickets:#8558] user email changes not getting into solr**
**Status:** open
**Milestone:** unreleased
**Created:** Thu Apr 25, 2024 04:58 PM UTC by Dave Brondsema
**Last Updated:** Thu Apr 25, 2024 04:58 PM UTC
**Owner:** nobody
For example, when a primary email address is deleted on a user, and one of
their other emails becomes the primary, that doesn't get into solr. So
/nf/admin/search_users has old results
`IndexerSessionExtension` only indexes Users changes. I think if an email
address record is added or deleted, we probably want to trigger a user index
then.
Also (and maybe even more importantly) the `user.set_pref('email_address',
primary_addr)` call doesn't make `IndexerSessionExtension` do anything which is
surprising since that is a field saved on the user record directly. Need to
figure out why.
minor, kinda related, I think this should be fixed:
```
--- Allura/allura/controllers/auth.py
+++ Allura/allura/controllers/auth.py
@@ -617,7 +617,7 @@ def _update_emails(self, user, admin=False, form_params={}):
flash('You must provide your current password to delete an
email', 'error')
return
if primary_addr == user.email_addresses[i]:
-if select_new_primary_addr(user,
ignore_emails=primary_addr) is None \
+if select_new_primary_addr(user,
ignore_emails=[primary_addr]) is None \
and asbool(config.get('auth.require_email_addr',
False)):
flash('You must have at least one verified email
address.', 'error')
return
```
---
Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed
to https://forge-allura.apache.org/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is
a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8555 check blocked users better
- **status**: in-progress --> review --- **[tickets:#8555] check blocked users better** **Status:** review **Milestone:** unreleased **Created:** Tue Apr 02, 2024 09:39 PM UTC by Dave Brondsema **Last Updated:** Tue Apr 02, 2024 09:42 PM UTC **Owner:** Dave Brondsema If a user is blocked at the tool level, they still may be able to post in discussion forums that have additional ACLs. E.g. a forum within the discussion tool, which has anonymous posting allowed, or has developer only posting. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8556 deprecate and remove has_access(..)() syntax
- **status**: open --> review - **Comment**: db/8556 on allura, forgehg, and forgepastebin db/8556-breaking-removal needs to be merged later, after we do a release and give anyone a chance to update their code. You can review and test it though. --- **[tickets:#8556] deprecate and remove has_access(..)() syntax** **Status:** review **Milestone:** unreleased **Created:** Wed Apr 03, 2024 06:09 PM UTC by Dave Brondsema **Last Updated:** Wed Apr 03, 2024 06:09 PM UTC **Owner:** nobody `has_access` returns a TruthyCallable which can be treated as a bool or called again, which is confusing. There's lots of `has_access(...)()` syntax that can be cleaned up now. After cleanup is done (including within external plugins/extensions), we can then remove the TruthyCallable and predicate behavior of has_access, and have it return a simple bool. Code changes necessary: - `has_access(...)()` -> `has_access(...)` - `has_access(c.app, 'read')(user=user)` -> `has_access(c.app, 'read', user)` - `require(has_access(c.app, 'read'))` -> `require_access(c.app, 'read'))` If `require(...)` is used in other situations, ideally it should be changed completely. Or, change from a callable to a bool like `require(lambda: foo == bar)` -> `require(foo == bar)` but this cannot be done ahead of time, it mus be done at the time of full removal. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8556 deprecate and remove has_access(..)() syntax
--- **[tickets:#8556] deprecate and remove has_access(..)() syntax** **Status:** open **Milestone:** unreleased **Created:** Wed Apr 03, 2024 06:09 PM UTC by Dave Brondsema **Last Updated:** Wed Apr 03, 2024 06:09 PM UTC **Owner:** nobody `has_access` returns a TruthyCallable which can be treated as a bool or called again, which is confusing. There's lots of `has_access(...)()` syntax that can be cleaned up now. After cleanup is done (including within external plugins/extensions), we can then remove the TruthyCallable and predicate behavior of has_access, and have it return a simple bool. Code changes necessary: - `has_access(...)()` -> `has_access(...)` - `has_access(c.app, 'read')(user=user)` -> `has_access(c.app, 'read', user)` - `require(has_access(c.app, 'read'))` -> `require_access(c.app, 'read'))` If `require(...)` is used in other situations, ideally it should be changed completely. Or, change from a callable to a bool like `require(lambda: foo == bar)` -> `require(foo == bar)` but this cannot be done ahead of time, it mus be done at the time of full removal. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8555 check blocked users better
db/8555 It was tempting to change this `has_access` code: ```python # access is denied for this role break ``` to be `return False`. That would've fixed this situation, but made several other tests fail. Instead, I decided it'd be better to change a few non-core places, and not change the core has_access logic (even if maybe it deserves a refactor some day) --- **[tickets:#8555] check blocked users better** **Status:** in-progress **Milestone:** unreleased **Created:** Tue Apr 02, 2024 09:39 PM UTC by Dave Brondsema **Last Updated:** Tue Apr 02, 2024 09:39 PM UTC **Owner:** Dave Brondsema If a user is blocked at the tool level, they still may be able to post in discussion forums that have additional ACLs. E.g. a forum within the discussion tool, which has anonymous posting allowed, or has developer only posting. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8555 check blocked users better
--- **[tickets:#8555] check blocked users better** **Status:** in-progress **Milestone:** unreleased **Created:** Tue Apr 02, 2024 09:39 PM UTC by Dave Brondsema **Last Updated:** Tue Apr 02, 2024 09:39 PM UTC **Owner:** Dave Brondsema If a user is blocked at the tool level, they still may be able to post in discussion forums that have additional ACLs. E.g. a forum within the discussion tool, which has anonymous posting allowed, or has developer only posting. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8540 fix wiki page 'recent' sort
- **status**: open --> review - **assigned_to**: Dave Brondsema - **Comment**: fixed on db/8540 there aren't any tests, and I didn't add any. But you can test manualyl: create just 4 or 5 wiki pages and then go Browse Pages, then click on the sort options. Then add `=2` to the URL to force small page sizes to see the problem & verify the fix. --- **[tickets:#8540] fix wiki page 'recent' sort** **Status:** review **Milestone:** unreleased **Created:** Thu Mar 28, 2024 06:21 PM UTC by Dave Brondsema **Last Updated:** Thu Mar 28, 2024 06:21 PM UTC **Owner:** Dave Brondsema The "Recently Updated" sort option on wiki's Browse Pages does not work correctly. It does the query and then applies a sort afterwards. So if you have more than one page of results, it only sorts within the current page not the whole set of pages. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8540 fix wiki page 'recent' sort
--- **[tickets:#8540] fix wiki page 'recent' sort** **Status:** open **Milestone:** unreleased **Created:** Thu Mar 28, 2024 06:21 PM UTC by Dave Brondsema **Last Updated:** Thu Mar 28, 2024 06:21 PM UTC **Owner:** nobody The "Recently Updated" sort option on wiki's Browse Pages does not work correctly. It does the query and then applies a sort afterwards. So if you have more than one page of results, it only sorts within the current page not the whole set of pages. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8539 add more ruff checks
- **status**: review --> closed --- **[tickets:#8539] add more ruff checks** **Status:** closed **Milestone:** unreleased **Created:** Wed Mar 20, 2024 09:27 PM UTC by Dave Brondsema **Last Updated:** Tue Mar 26, 2024 03:27 PM UTC **Owner:** Dave Brondsema https://docs.astral.sh/ruff/rules/#flake8-bandit-s in particular would be good, some others too --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8538 Slight tweak to timeline helper methods
- **status**: open --> closed --- **[tickets:#8538] Slight tweak to timeline helper methods** **Status:** closed **Milestone:** unreleased **Created:** Wed Mar 13, 2024 07:37 PM UTC by Dillon Walls **Last Updated:** Wed Mar 13, 2024 07:38 PM UTC **Owner:** Dillon Walls --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8539 add more ruff checks
- **status**: open --> review - **Comment**: db/8539 --- **[tickets:#8539] add more ruff checks** **Status:** review **Milestone:** unreleased **Created:** Wed Mar 20, 2024 09:27 PM UTC by Dave Brondsema **Last Updated:** Wed Mar 20, 2024 09:27 PM UTC **Owner:** Dave Brondsema https://docs.astral.sh/ruff/rules/#flake8-bandit-s in particular would be good, some others too --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8539 add more ruff checks
--- **[tickets:#8539] add more ruff checks** **Status:** open **Milestone:** unreleased **Created:** Wed Mar 20, 2024 09:27 PM UTC by Dave Brondsema **Last Updated:** Wed Mar 20, 2024 09:27 PM UTC **Owner:** Dave Brondsema https://docs.astral.sh/ruff/rules/#flake8-bandit-s in particular would be good, some others too --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
Re: [Feedback] Personal feedback regarding your mailing-list health
Hi Chris, Our dev list is pretty low traffic overall, a dozen or so emails a month. So even though Jenkins build failures are a lot of that, I don't think they are distracting, at least not for me. Back in January I see there were more. I think that was uncommon though. If anyone else on the list thinks we should make some adjustments, do feel free to speak up. My own email management isn't necessarily the same as how everyone does it :) Thanks Chris for the input -Dave On 3/15/24 7:46 AM, Christofer Dutz wrote: Hi all, while reviewing your projects activities as part of my preparation for next week's board meeting, I came across the fact that the one entity responsible for almost 50% of your dev-lists traffic, is build failure notices from Jenkins. I also left a comment on your last board report about this. Generally I'm a big fan of having build failure notifications on dev@, however I guess this only applies to build failures on the main branch. From me it looks as if here for every pr, issue, whatsoever all messages are delivered here. I would consider that harmful. The dev list should be a place where the project discusses matters of the project and is not flooded by such notifications. Perhaps an approach that other projects are using might be something the project could consider? Many other projects use GitHub Actions for the building of PRs etc. and only use Jenkins for special tests that require special agents or for staging and deploying websites and artifacts. The good thing here is that when using GitHub Actions, only the people involved in a PR get direct feedback emails and the rest of the project is not disturbed. I hope this sort of feedback is welcome, if not, give me a notice and I'll try to remember that for the next time. Also please add me in CC for any responses, as I'm not subscribed here. Chris -- Dave Brondsema : d...@brondsema.net http://www.brondsema.net : personal http://www.splike.com : programming <><
[allura:tickets] #8537 a few JS performance improvements
- **summary**: Move GA further down the page --> a few JS performance improvements - Description has changed: Diff: --- old +++ new @@ -1 +1,2 @@ -move `GoogleAnalytics` further down the page +- move `GoogleAnalytics` further down the page +- remove `scanMessages` from `jquery.notify.js` - **status**: in-progress --> closed - **Reviewer**: Dave Brondsema --- **[tickets:#8537] a few JS performance improvements** **Status:** closed **Milestone:** unreleased **Created:** Thu Feb 22, 2024 08:41 PM UTC by Guillermo Cruz **Last Updated:** Thu Feb 22, 2024 08:41 PM UTC **Owner:** Guillermo Cruz - move `GoogleAnalytics` further down the page - remove `scanMessages` from `jquery.notify.js` --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
Re: Import / export of a project
Hi,
That sounds like a neat idea. And Allura has a good amount of import & export
behavior already so you'd have a good starting point to work from.
For importers, you can start by looking at ForgeImporters/setup.py where it has
a [allura.importers] section that points at several types of importers. Those
reference python classes like GitHubTrackerImporter, and more could be added.
They all inherit ToolImporter and will get some behavior for free, like showing
up on every projects' Admin > Import page.
For exporters, there is a Admin > Export page for every project, but it isn't as
flexible to support additional export formats currently. That page is set up by
this function:
@expose('jinja:allura.ext.admin:templates/export.html')
def export(self, tools=None, with_attachments=False):
And then backend work is done by `class BulkExport` and the `def bulk_export`
functions across the codebase.
If you want realtime mirroring, that sounds more challenging, but could be
possible by expanding upon Allura's REST APIs
https://forge-allura.apache.org/docs/getting_started/administration.html#public-api
Other parts of our docs cover installation and some general concepts of the code
& systems, so might be helpful. https://forge-allura.apache.org/docs/index.html
Happy to answer any more questions you might have
On 3/5/24 12:56 AM, Loïc Dachary wrote:
Hi,
I would be grateful if someone had a few pointers regarding the import / export
operations in Allura. I'm working on data portability between forges, in the
context of the F3 project[0], and I'd like to write a driver for Allura. It
would allow for bi-directional mirroring from/to other forges. Not just the
repository but also issues[1].
Cheers
[0] https://f3.forgefriends.org
[1] https://forge-allura.apache.org/p/allura/wiki/Features/
--
Dave Brondsema : d...@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
<><
[allura:tickets] #8536 improve |safe and Markup usage
--- **[tickets:#8536] improve |safe and Markup usage** **Status:** open **Milestone:** unreleased **Created:** Fri Feb 09, 2024 04:17 PM UTC by Dave Brondsema **Last Updated:** Fri Feb 09, 2024 04:17 PM UTC **Owner:** Dave Brondsema - `Markup()` objects can use `%` or `.format` to automatically escape things into them, that's nicer - `|safe` in templates is not ideal, better to use Markup() right when the string is constructed and known to be safe html. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8534 set up github codeql
- **status**: review --> closed --- **[tickets:#8534] set up github codeql** **Status:** closed **Milestone:** unreleased **Labels:** security **Created:** Fri Jan 05, 2024 05:07 PM UTC by Dave Brondsema **Last Updated:** Fri Jan 05, 2024 07:16 PM UTC **Owner:** Dave Brondsema Our repo gets mirrored to https://github.com/apache/allura/ so we can set up CodeQL to run there and check for security issues in code --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8533 switch python email 'policy' for better line length handling
- **status**: in-progress --> closed --- **[tickets:#8533] switch python email 'policy' for better line length handling** **Status:** closed **Milestone:** unreleased **Created:** Thu Jan 04, 2024 07:31 PM UTC by Dave Brondsema **Last Updated:** Thu Jan 04, 2024 07:31 PM UTC **Owner:** Dave Brondsema If an email has a super long subject header (for example) with no spaces in it, email delivery can fail. For example `exim` gives `message has lines too long for transport` We’ve handled this before: - in `SMTPClient.sendmail` and `test_send_email_long_lines_use_quoted_printable` but apparently it doesn’t split a header if there’s no spaces or other chars to split on - `encode_email_part` handled it too, and debugging that seems like it works correctly (setting header charsets) but it still ends up rewritten later in sendmail, and causes the error https://docs.python.org/3/library/email.mime.html for MIMEText and MIMEMultipart extend from Message which has a default policy of compat32 (python 3.2 compatibility, bugs included). Specifying a different policy (or using EmailMessage perhaps) seems to work better, and maybe we can get rid of workarounds within our code. See https://docs.python.org/3/library/email.policy.html in the middle of the page. SMTP seems best. (SMTPUTF8 sound appealing, but not all mail servers support utf8) --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8534 set up github codeql
- **status**: in-progress --> review - **Comment**: db/8534 I tested it on my fork, I think it should work fine. It has some fixes, and all the remaining alerts I reviewed and aren’t a concern and can be dismissed in the GitHub UI after this is merged --- **[tickets:#8534] set up github codeql** **Status:** review **Milestone:** unreleased **Labels:** security **Created:** Fri Jan 05, 2024 05:07 PM UTC by Dave Brondsema **Last Updated:** Fri Jan 05, 2024 05:07 PM UTC **Owner:** Dave Brondsema Our repo gets mirrored to https://github.com/apache/allura/ so we can set up CodeQL to run there and check for security issues in code --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8534 set up github codeql
--- **[tickets:#8534] set up github codeql** **Status:** in-progress **Milestone:** unreleased **Labels:** security **Created:** Fri Jan 05, 2024 05:07 PM UTC by Dave Brondsema **Last Updated:** Fri Jan 05, 2024 05:07 PM UTC **Owner:** Dave Brondsema Our repo gets mirrored to https://github.com/apache/allura/ so we can set up CodeQL to run there and check for security issues in code --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8533 switch python email 'policy' for better line length handling
--- **[tickets:#8533] switch python email 'policy' for better line length handling** **Status:** in-progress **Milestone:** unreleased **Created:** Thu Jan 04, 2024 07:31 PM UTC by Dave Brondsema **Last Updated:** Thu Jan 04, 2024 07:31 PM UTC **Owner:** Dave Brondsema If an email has a super long subject header (for example) with no spaces in it, email delivery can fail. For example `exim` gives `message has lines too long for transport` We’ve handled this before: - in `SMTPClient.sendmail` and `test_send_email_long_lines_use_quoted_printable` but apparently it doesn’t split a header if there’s no spaces or other chars to split on - `encode_email_part` handled it too, and debugging that seems like it works correctly (setting header charsets) but it still ends up rewritten later in sendmail, and causes the error https://docs.python.org/3/library/email.mime.html for MIMEText and MIMEMultipart extend from Message which has a default policy of compat32 (python 3.2 compatibility, bugs included). Specifying a different policy (or using EmailMessage perhaps) seems to work better, and maybe we can get rid of workarounds within our code. See https://docs.python.org/3/library/email.policy.html in the middle of the page. SMTP seems best. (SMTPUTF8 sound appealing, but not all mail servers support utf8) --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8532 improve ruff config
--- **[tickets:#8532] improve ruff config** **Status:** in-progress **Milestone:** unreleased **Created:** Tue Jan 02, 2024 10:34 PM UTC by Dave Brondsema **Last Updated:** Tue Jan 02, 2024 10:34 PM UTC **Owner:** Dave Brondsema --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8529 support unicode in repo branch names
- **status**: open --> review - **assigned_to**: Dave Brondsema - **Comment**: db/8529 --- **[tickets:#8529] support unicode in repo branch names** **Status:** review **Milestone:** unreleased **Created:** Tue Dec 05, 2023 07:10 PM UTC by Dave Brondsema **Last Updated:** Tue Dec 05, 2023 07:10 PM UTC **Owner:** Dave Brondsema Currently a branch name with unicode in it is browsable, but only if you go their directly. If you go to a code tool it'll try to do a redirect and get this error ``` File "/src/allura/Allura/allura/lib/custom_middleware.py", line 638, in __call__ start_response(status, headers, exc_info) ValueError: unicode object contains non latin-1 characters ``` --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8529 support unicode in repo branch names
--- **[tickets:#8529] support unicode in repo branch names** **Status:** open **Milestone:** unreleased **Created:** Tue Dec 05, 2023 07:10 PM UTC by Dave Brondsema **Last Updated:** Tue Dec 05, 2023 07:10 PM UTC **Owner:** nobody Currently a branch name with unicode in it is browsable, but only if you go their directly. If you go to a code tool it'll try to do a redirect and get this error ``` File "/src/allura/Allura/allura/lib/custom_middleware.py", line 638, in __call__ start_response(status, headers, exc_info) ValueError: unicode object contains non latin-1 characters ``` --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
Re: Problems with nginx-proxy and letsencrypt-nginx-proxy-companion
Hi, Unfortunately I don't have any ideas what might be wrong. It does seem like everything is configured correctly already. Have you tried restarting nginx-proxy and letsencrypt-nginx-proxy-companion and even the whole docker service? Sometimes I've had weird problems and just restarting them helped. Other than that, I'd say look for help from Docker or nginx-proxy communities, since it seems to be an issue with docker more so than with Allura. -Dave On 11/25/23 10:32 AM, Iacopo Ciampa wrote: Dear community of Allura developers, My name is Iacopo Ciampa and I’m new to Allura and Docker so I hope that my question isn’t too naive. I am using Allura 1.16.0 installed with docker desktop 4.25.2 on a Macbook M2. I am writing to you about the services nginx-proxy and letsencrypt-nginx-proxy-companion, used in the production version of Allura. The derived containers run successfully locally, but I can’t run the images independently or deploy them on AWS EC2 because I obtain the errors: 2023-11-25 15:19:45 Info: running nginx-proxy version 1.3.1-40-g67ab97e 2023-11-25 15:19:45 ERROR: you need to share your Docker host socket with a volume at /tmp/docker.sock 2023-11-25 15:19:45 Typically you should run your nginxproxy/nginx-proxy with: `-v /var/run/docker.sock:/tmp/docker.sock:ro` 2023-11-25 15:19:45 See the documentation at: https://github.com/nginx-proxy/nginx-proxy/#usage And: 2023-11-25 15:38:45 Info: running acme-companion version v2.2.8-14-g9fbd668 2023-11-25 15:38:45 Error: you need to share your Docker host socket with a volume at /var/run/docker.sock 2023-11-25 15:38:45 Typically you should run your container with: '-v /var/run/docker.sock:/var/run/docker.sock:ro' These suggestions can’t solve my problem as the volumes are already mounted in the correct way in docker-compose-prod.yml and that link only contains general setup advice. I suspect that since the containers run successfully but the images alone don’t the issue could indicate that the images are not self contained, but I could be wrong. Could you help me to solve this problem? Thank you very much in advance, Kind regards, Iacopo Ciampa -- Dave Brondsema : d...@brondsema.net http://www.brondsema.net : personal http://www.splike.com : programming <><
[allura:tickets] #8527 discussion app display thread subject in header
- **status**: in-progress --> closed - **Reviewer**: Dave Brondsema --- **[tickets:#8527] discussion app display thread subject in header ** **Status:** closed **Milestone:** unreleased **Created:** Thu Nov 16, 2023 09:07 PM UTC by Guillermo Cruz **Last Updated:** Thu Nov 16, 2023 09:07 PM UTC **Owner:** Guillermo Cruz The discussion app currently displays the project name and the tool label but it should display the thread subject instead. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8528 improve allura.command_init
- **status**: open --> review - **Comment**: db/8528 --- ** [tickets:#8528] improve allura.command_init** **Status:** review **Milestone:** unreleased **Created:** Tue Nov 21, 2023 02:50 PM UTC by Dave Brondsema **Last Updated:** Tue Nov 21, 2023 02:50 PM UTC **Owner:** Dave Brondsema It'd be helpful to know which command is being run. And this entry point should be documented --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8528 improve allura.command_init
--- ** [tickets:#8528] improve allura.command_init** **Status:** open **Milestone:** unreleased **Created:** Tue Nov 21, 2023 02:50 PM UTC by Dave Brondsema **Last Updated:** Tue Nov 21, 2023 02:50 PM UTC **Owner:** Dave Brondsema It'd be helpful to know which command is being run. And this entry point should be documented --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8526 improve session cookie handling NEEDS CONFIG CHANGES
- **status**: in-progress --> review --- ** [tickets:#8526] improve session cookie handling NEEDS CONFIG CHANGES** **Status:** review **Milestone:** unreleased **Labels:** security **Created:** Wed Nov 15, 2023 07:48 PM UTC by Dave Brondsema **Last Updated:** Wed Nov 15, 2023 08:40 PM UTC **Owner:** Dave Brondsema Main thing is to move away from pickle, but we can also implement stronger keys, support key rotation, etc. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8526 improve session cookie handling NEEDS CONFIG CHANGES
- **summary**: improve session cookie handling --> improve session cookie handling NEEDS CONFIG CHANGES - **Comment**: for deployment/changelog: - add `session.jwt_secret_keys` to .ini file, with a value `python -c 'import secrets; print(secrets.token_hex());'` - `session.type = cookie` is no longer used - optionally `session.read_original_format = true` and rename `session.validate_key` to `session.original_format_validate_key` for backwards compatibility. Remove after a transition period - optionally `session.write_original_format = true` if it takes a while to deploy all your code to multiple hosts/procs. Then remove once all processes have new code. --- ** [tickets:#8526] improve session cookie handling NEEDS CONFIG CHANGES** **Status:** in-progress **Milestone:** unreleased **Labels:** security **Created:** Wed Nov 15, 2023 07:48 PM UTC by Dave Brondsema **Last Updated:** Wed Nov 15, 2023 07:48 PM UTC **Owner:** Dave Brondsema Main thing is to move away from pickle, but we can also implement stronger keys, support key rotation, etc. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8526 improve session cookie handling
--- ** [tickets:#8526] improve session cookie handling** **Status:** in-progress **Milestone:** unreleased **Labels:** security **Created:** Wed Nov 15, 2023 07:48 PM UTC by Dave Brondsema **Last Updated:** Wed Nov 15, 2023 07:48 PM UTC **Owner:** Dave Brondsema Main thing is to move away from pickle, but we can also implement stronger keys, support key rotation, etc. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[ANNOUNCE] Apache Allura 1.16.0 released, contains critical security fix
The Apache Allura team is pleased to announce the release of Apache Allura 1.16.0 Apache 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. This release contains a critical security fix for CVE-2023-46851 If you are unable to upgrade, set this in your .ini config file: disable_entry_points.allura.importers = forge-tracker, forge-discussion That same .ini setting is also recommend for users who want maximum security on their Allura instance and don't need those importers available. Also, this release drops support for Python 3.7 To see all the details and upgrade instructions, view the release changelog at https://forge-allura.apache.org/p/allura/git/ci/master/tree/CHANGES Download at https://allura.apache.org/download.html
CVE-2023-46851: Apache Allura: sensitive information exposure via import
Severity: critical Affected versions: - Apache Allura 1.0.1 through 1.15.0 Description: Allura Discussion and Allura Forum importing does not restrict URL values specified in attachments. Project administrators can run these imports, which could cause Allura to read local files and expose them. Exposing internal files then can lead to other exploits, like session hijacking, or remote code execution. This issue affects Apache Allura from 1.0.1 through 1.15.0. Users are recommended to upgrade to version 1.16.0, which fixes the issue. If you are unable to upgrade, set "disable_entry_points.allura.importers = forge-tracker, forge-discussion" in your .ini config file. Credit: Stefan Schiller (Sonar) (finder) References: https://allura.apache.org/ https://www.cve.org/CVERecord?id=CVE-2023-46851
[allura:tickets] #8524 Docker Upgrade Node Version
- **Milestone**: unreleased --> v1.16.0 --- ** [tickets:#8524] Docker Upgrade Node Version** **Status:** closed **Milestone:** v1.16.0 **Created:** Mon Oct 23, 2023 09:02 PM UTC by Guillermo Cruz **Last Updated:** Wed Oct 25, 2023 03:01 PM UTC **Owner:** Guillermo Cruz Update the installation url path for node 16 --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8523 github api improvements
- **Milestone**: unreleased --> v1.16.0 --- ** [tickets:#8523] github api improvements** **Status:** closed **Milestone:** v1.16.0 **Created:** Wed Oct 18, 2023 06:43 PM UTC by Dave Brondsema **Last Updated:** Mon Oct 23, 2023 04:11 PM UTC **Owner:** Dave Brondsema --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8522 Python Packages Upgrade
- **Milestone**: unreleased --> v1.16.0 --- ** [tickets:#8522] Python Packages Upgrade** **Status:** closed **Milestone:** v1.16.0 **Created:** Mon Oct 16, 2023 02:52 PM UTC by Guillermo Cruz **Last Updated:** Fri Oct 20, 2023 10:07 PM UTC **Owner:** Guillermo Cruz Quarterly upgrades for Allura --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] Mass edit changes by Dave Brondsema
Mass edit changing: - **Milestone**: v1.16.0 ticket: tickets:#8519 Drop Python 3.7 Support - **Milestone**: unreleased --> v1.16.0 ticket: tickets:#8521 Do not index empty ticket pages - **Milestone**: unreleased --> v1.16.0
[RESULT] [VOTE] Release of Apache Allura 1.16.0
The vote passes with 4 +1s from PMC members: Dave Brondsema Kenton Taylor Dillon Walls Guillermo Cruz I'll publish the release, and make the website updates and news announcements after it gets on some of the release mirrors.
[VOTE] Release of Apache Allura 1.16.0
Hello, This is a call for a vote on Apache Allura 1.16.0. Source tarball, signature and checksums are available at: https://dist.apache.org/repos/dist/dev/allura/ Checksums: SHA512: 1ca0ea9752db7033030d50f47c931929fb5b053a0e82ab7a7fe184068a843affc4754e7353d8b70d7021568ddc887d68f312c7c7342779417dbfba2119b08ae6 allura-1.16.0.tar.gz The KEYS file can be found at: https://www.apache.org/dist/allura/KEYS The release has been signed with key EAB0FABEDEA81AD4086902FE56F0526F9BB3CE70: http://pgp.mit.edu:11371/pks/lookup?op=vindex=0xEAB0FABEDEA81AD4086902FE56F0526F9BB3CE70 Source corresponding to this release can be found at: Commit: 705f6d38c47347113eb7b7032aa4932f4ef645bc Tag:rel/1.16.0 (pending successful vote) Browse: https://forge-allura.apache.org/p/allura/git/ci/705f6d38c47347113eb7b7032aa4932f4ef645bc/log/ Changes for this version are listed at: https://forge-allura.apache.org/p/allura/git/ci/705f6d38c47347113eb7b7032aa4932f4ef645bc/tree/CHANGES The RAT license report is available at: https://forge-allura.apache.org/p/allura/pastebin/654519d9f9adad853b39d3c9 Vote will be open for at least 72 hours (Mon, 06 Nov 2023 18:32:25 UTC). Votes from Allura PMC members are binding, but we welcome all community members to vote as well. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks & Regards
Re: [VOTE] Release of Apache Allura 1.16.0
+1 On 11/3/23 2:41 PM, Dave Brondsema wrote: Hello, This is a call for a vote on Apache Allura 1.16.0. Source tarball, signature and checksums are available at: https://dist.apache.org/repos/dist/dev/allura/ Checksums: SHA512: 1ca0ea9752db7033030d50f47c931929fb5b053a0e82ab7a7fe184068a843affc4754e7353d8b70d7021568ddc887d68f312c7c7342779417dbfba2119b08ae6 allura-1.16.0.tar.gz The KEYS file can be found at: https://www.apache.org/dist/allura/KEYS The release has been signed with key EAB0FABEDEA81AD4086902FE56F0526F9BB3CE70: http://pgp.mit.edu:11371/pks/lookup?op=vindex=0xEAB0FABEDEA81AD4086902FE56F0526F9BB3CE70 Source corresponding to this release can be found at: Commit: 705f6d38c47347113eb7b7032aa4932f4ef645bc Tag: rel/1.16.0 (pending successful vote) Browse: https://forge-allura.apache.org/p/allura/git/ci/705f6d38c47347113eb7b7032aa4932f4ef645bc/log/ Changes for this version are listed at: https://forge-allura.apache.org/p/allura/git/ci/705f6d38c47347113eb7b7032aa4932f4ef645bc/tree/CHANGES The RAT license report is available at: https://forge-allura.apache.org/p/allura/pastebin/654519d9f9adad853b39d3c9 Vote will be open for at least 72 hours (Mon, 06 Nov 2023 18:32:25 UTC). Votes from Allura PMC members are binding, but we welcome all community members to vote as well. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks & Regards -- Dave Brondsema : d...@brondsema.net http://www.brondsema.net : personal http://www.splike.com : programming <><
[allura:tickets] #8524 Docker Upgrade Node Version
- **status**: review --> closed --- ** [tickets:#8524] Docker Upgrade Node Version** **Status:** closed **Milestone:** unreleased **Created:** Mon Oct 23, 2023 09:02 PM UTC by Guillermo Cruz **Last Updated:** Mon Oct 23, 2023 09:02 PM UTC **Owner:** Guillermo Cruz Update the installation url path for node 16 --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8466 Docker Install Fails on aarch64 Archicheture
- **status**: open --> invalid - **Comment**: We can no longer reproduce this error --- ** [tickets:#8466] Docker Install Fails on aarch64 Archicheture ** **Status:** invalid **Milestone:** unreleased **Created:** Wed Sep 21, 2022 04:48 PM UTC by Guillermo Cruz **Last Updated:** Wed Sep 21, 2022 04:48 PM UTC **Owner:** Guillermo Cruz `init-docker-dev.sh` errors out when trying to install `pysnv` on `aarch64` architectures. ``` Building PySVN... Processing /tmp/tmpgwy4ajtc.pysvn-install/pysvn-1.9.18 Preparing metadata (setup.py) ... done Building wheels for collected packages: pysvn Building wheel for pysvn (setup.py) ... error error: subprocess-exited-with-error × python setup.py bdist_wheel did not run successfully. │ exit code: 1 ╰─> [34 lines of output] running bdist_wheel running build running build_ext running egg_info creating pysvn.egg-info writing pysvn.egg-info/PKG-INFO writing dependency_links to pysvn.egg-info/dependency_links.txt writing top-level names to pysvn.egg-info/top_level.txt writing manifest file 'pysvn.egg-info/SOURCES.txt' reading manifest file 'pysvn.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no previously-included files found matching 'Source/pysvn/__init__.py' warning: no previously-included files found matching 'Source/pysvn/*.so' warning: no previously-included files found matching 'Source/*.o' warning: no previously-included files found matching 'Source/Makefile' warning: no previously-included files found matching 'Source/pysvn_docs.cpp' warning: no previously-included files found matching 'Source/pysvn_docs.hpp' warning: no previously-included files found matching 'Source/pysvn_version.hpp' warning: no previously-included files found matching 'Source/generate_svn_error_codes.hpp' warning: no previously-included files found matching 'Source/generate_svn_error_codes/generate_svn_error_codes' writing manifest file 'pysvn.egg-info/SOURCES.txt' Info: Configure for python 3.7.14 in exec_prefix /allura-data/virtualenv Info: Using C compiler gcc Info: Using C++ compiler g++ Info: Found PyCXX include in /tmp/tmpgwy4ajtc.pysvn-install/pysvn-1.9.18/Import/pycxx-7.1.5 Info: Found PyCXX Source in /tmp/tmpgwy4ajtc.pysvn-install/pysvn-1.9.18/Import/pycxx-7.1.5/Src Info: FoundSVN include in /usr/include/subversion-1 Error: Cannot find SVN library libsvn_client-1.so - use --svn-lib-dir make: *** No rule to make target 'clean'. Stop. make: *** No targets. Stop. creating /tmp/tmpgwy4ajtc.pysvn-install/pysvn-1.9.18/build creating /tmp/tmpgwy4ajtc.pysvn-install/pysvn-1.9.18/build/lib.linux-aarch64-3.7 creating /tmp/tmpgwy4ajtc.pysvn-install/pysvn-1.9.18/build/lib.linux-aarch64-3.7/pysvn error: [Errno 2] No such file or directory: 'pysvn/__init__.py' [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. ERROR: Failed building wheel for pysvn Running setup.py clean for pysvn Failed to build pysvn Installing collected packages: pysvn Running setup.py install for pysvn ... error error: subprocess-exited-with-error × Running setup.py install for pysvn did not run successfully. │ exit code: 1 ╰─> [31 lines of output] running install running build running build_ext running egg_info writing pysvn.egg-info/PKG-INFO writing dependency_links to pysvn.egg-info/dependency_links.txt writing top-level names to pysvn.egg-info/top_level.txt reading manifest file 'pysvn.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no previously-included files found matching 'Source/pysvn/__init__.py' warning: no previously-included files found matching 'Source/pysvn/*.so' warning: no previously-included files found matching 'Source/*.o' warning: no previously-included files found matching 'Source/pysvn_docs.cpp' warning: no previously-included files found matching 'Source/pysvn_docs.hpp' warning: no previously-included files found matching 'Source/pysvn_version.hpp' warning: no previously-included files found matching 'Source/generate_svn_error_codes.hpp' warning: no previously-included files found matching 'Source/generate_svn_error_codes/generate_svn_error_codes' writing manifest file 'pysvn.egg-info/SOURCES.txt' Info: Configure for python 3.7.14 in exec_prefix /allura-data/virtualenv Info: Using C compiler gcc Info: Using C++ compiler g++ Info: Found PyCXX include in /tmp/tmpgwy4ajtc.pysvn-install/pysvn-1.9.18/Import/pycxx-7.1.5 Info: Found PyCXX Source in /tmp/tmpgwy4ajtc.pysvn-install/pysvn-1.9.18/Import/pycxx-7.1.5/Src Info: FoundSVN include in /usr/include/subversion-1 Error: Cannot find SVN
[allura:tickets] #8522 Python Packages Upgrade
- **status**: in-progress --> closed - **Reviewer**: Dave Brondsema --- ** [tickets:#8522] Python Packages Upgrade** **Status:** closed **Milestone:** unreleased **Created:** Mon Oct 16, 2023 02:52 PM UTC by Guillermo Cruz **Last Updated:** Mon Oct 16, 2023 02:52 PM UTC **Owner:** Guillermo Cruz Quarterly upgrades for Allura --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8523 github api improvements
- **status**: open --> review --- ** [tickets:#8523] github api improvements** **Status:** review **Milestone:** unreleased **Created:** Wed Oct 18, 2023 06:43 PM UTC by Dave Brondsema **Last Updated:** Wed Oct 18, 2023 06:43 PM UTC **Owner:** Dave Brondsema --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8523 github api improvements
--- ** [tickets:#8523] github api improvements** **Status:** open **Milestone:** unreleased **Created:** Wed Oct 18, 2023 06:43 PM UTC by Dave Brondsema **Last Updated:** Wed Oct 18, 2023 06:43 PM UTC **Owner:** Dave Brondsema --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8521 Do not index empty ticket pages
- Description has changed: Diff: --- old +++ new @@ -1 +0,0 @@ -Also exclude the app by default when generating a site map. - **status**: open --> closed --- ** [tickets:#8521] Do not index empty ticket pages** **Status:** closed **Milestone:** unreleased **Created:** Thu Sep 28, 2023 05:33 PM UTC by Guillermo Cruz **Last Updated:** Thu Sep 28, 2023 05:33 PM UTC **Owner:** Guillermo Cruz --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8519 Drop Python 3.7 Support
- **status**: in-progress --> closed --- ** [tickets:#8519] Drop Python 3.7 Support** **Status:** closed **Milestone:** unreleased **Created:** Tue Sep 12, 2023 07:44 PM UTC by Dillon Walls **Last Updated:** Tue Sep 12, 2023 07:44 PM UTC **Owner:** Dillon Walls * upgrade: `pre-commit`, `PIL`, `werkzeug` * rebuild req.txt * update apache jenkins 3.7 -> 3.8(??) * update docker default (to 3.11?) * update docs * pyupgrade? --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[ANNOUNCE] Apache Allura 1.15.0 released
The Apache Allura team is pleased to announce the release of Apache Allura 1.15.0 Apache 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. 1.15.0 adds support for more Python versions (see next section) and Content-Security-Policy headers. Many other fixes and improvements are also included, they relate to SEO, performance and different parts of Allura. This release supports Python 3.7 through Python 3.11 The next release will drop support for Python 3.7 so please upgrade your Python version soon, to stay compatible with future Allura releases. To see all the details and upgrade instructions, view the release changelog at https://forge-allura.apache.org/p/allura/git/ci/master/tree/CHANGES Download at https://allura.apache.org/download.html
[allura:tickets] #8518 Git Improve set_default_branch
- **Milestone**: unreleased --> v1.15.0 --- ** [tickets:#8518] Git Improve set_default_branch** **Status:** closed **Milestone:** v1.15.0 **Created:** Tue Aug 08, 2023 09:53 PM UTC by Guillermo Cruz **Last Updated:** Fri Aug 18, 2023 03:35 PM UTC **Owner:** Guillermo Cruz When setting a default branch the branch name get updated in mongo but not in the actual repo. We should update the head reference so the users won't have to do it manually. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8517 Python Package Upgrades
- **Milestone**: unreleased --> v1.15.0 --- ** [tickets:#8517] Python Package Upgrades** **Status:** closed **Milestone:** v1.15.0 **Created:** Mon Jul 31, 2023 01:59 PM UTC by Guillermo Cruz **Last Updated:** Tue Aug 08, 2023 03:22 PM UTC **Owner:** Guillermo Cruz Upgrade Python packages --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
Re: [VOTE] Release of Apache Allura 1.15.0
+1 On 9/11/23 3:48 PM, Dillon Walls wrote: +1 On Mon, Sep 11, 2023 at 3:24 PM Simone Gatti wrote: +1 Il giorno lun 11 set 2023 alle ore 19:56 Kenton Taylor ha scritto: +1 --- Kenton Taylor Principal Engineer - sourceforge.net Phone: 616-425-9149 On Mon, Sep 11, 2023 at 1:15 PM Guillermo Cruz wrote: Hello, This is a call for a vote on Apache Allura 1.15.0. Source tarball, signature and checksums are available at: https://dist.apache.org/repos/dist/dev/allura/ Checksums: SHA512: b45004d18dc51ac72b1ae07d372fe32bd78333a7bba747b69c5bfe16e3ca20c315b3c5d5d318f213f3991677305ec095add993ec0a60ff90d8a4fb873092a0b1 allura-1.15.0.tar.gz The KEYS file can be found at: https://www.apache.org/dist/allura/KEYS The release has been signed with key D53F0F5A8A4B16951911A9A252FF6B0E63234CE4: https://people.apache.org/keys/committer/gcruz.asc Source corresponding to this release can be found at: Commit: 52683f78d68969e33b54e4068cb259f879c21549 Tag:rel/1.15.0 (pending successful vote) Browse: https://forge-allura.apache.org/p/allura/git/ci/52683f78d68969e33b54e4068cb259f879c21549/log/ Changes for this version are listed at: https://forge-allura.apache.org/p/allura/git/ci/52683f78d68969e33b54e4068cb259f879c21549/tree/CHANGES The RAT license report is available at: https://forge-allura.apache.org/p/allura/pastebin/64ff417190a69eb6d7daf5d5 Vote will be open for at least 72 hours (Sun, 10 Sep 2023 21:48:51 UTC). Votes from Allura PMC members are binding, but we welcome all community members to vote as well. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks & Regards -- Dave Brondsema : d...@brondsema.net http://www.brondsema.net : personal http://www.splike.com : programming <><
[allura:tickets] #8518 Git Improve set_default_branch
- **status**: in-progress --> closed --- ** [tickets:#8518] Git Improve set_default_branch** **Status:** closed **Milestone:** unreleased **Created:** Tue Aug 08, 2023 09:53 PM UTC by Guillermo Cruz **Last Updated:** Thu Aug 10, 2023 05:49 PM UTC **Owner:** Guillermo Cruz When setting a default branch the branch name get updated in mongo but not in the actual repo. We should update the head reference so the users won't have to do it manually. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8518 Git Improve set_default_branch
instead of f'{project_url}{mount_point}/' or '/' you can do c.app.url
---
** [tickets:#8518] Git Improve set_default_branch**
**Status:** in-progress
**Milestone:** unreleased
**Created:** Tue Aug 08, 2023 09:53 PM UTC by Guillermo Cruz
**Last Updated:** Tue Aug 08, 2023 09:53 PM UTC
**Owner:** Guillermo Cruz
When setting a default branch the branch name get updated in mongo but not in
the actual repo. We should update the head reference so the users won't have to
do it manually.
---
Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed
to https://forge-allura.apache.org/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is
a mailing list, you can unsubscribe from the mailing list.
dropping python3.7 support
With the latest package upgrades from Guillermo today, we actually have run into a problem. Our latest Jenkins using on 3.7 https://ci-builds.apache.org/job/Allura/job/Allura-py3.7/254/console errored out on Pillow: """ ERROR: Ignored the following versions that require a different python version: 10.0.0 Requires-Python >=3.8; 6.8.0 Requires-Python >=3.8 ERROR: Could not find a version that satisfies the requirement pillow==10.0.0 """ So I think we should drop Python 3.7 support, since it is end-of-life and keeping it would prevent us from using the latest versions of packages like Pillow. However! Our last release 1.14 was last fall and supported *only* Python 3.7 https://forge-allura.apache.org/p/allura/git/ci/master/tree/CHANGES I don't think we want that Allura release to support only 3.7 and then our next Allura release to support only 3.8-3.11 Better to have a release that supports 3.7-3.11 before we drop 3.7 so its an easier upgrade path So I propose: 1) downgrade Pillow temporarily so that it works on 3.7 again 2) make an Allura release which supports 3.7-3.11. Its been a long time since a release anyway 3) drop python 3.7 support and upgrade Pillow back up 4) the subsequent release (later) will then be 3.8+ only Thoughts? -- Dave Brondsema : d...@brondsema.net http://www.brondsema.net : personal http://www.splike.com : programming <><
[allura:tickets] #8517 Python Package Upgrades
- **status**: in-progress --> closed --- ** [tickets:#8517] Python Package Upgrades** **Status:** closed **Milestone:** unreleased **Created:** Mon Jul 31, 2023 01:59 PM UTC by Guillermo Cruz **Last Updated:** Mon Jul 31, 2023 01:59 PM UTC **Owner:** Guillermo Cruz Upgrade Python packages --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8512 I'm trying to create a git project
- **status**: open --> invalid - **Comment**: This website is for development of the Allura project only, we don't provide project registration or website services. --- ** [tickets:#8512] I'm trying to create a git project** **Status:** invalid **Milestone:** unreleased **Created:** Wed Jun 07, 2023 06:55 AM UTC by Awesome247 **Last Updated:** Wed Jun 07, 2023 06:55 AM UTC **Owner:** nobody Hello, I'm trying to create a project so I can save my [website](https://omoyetips.com) files, I clicked on **"My profile and my projects"** and I scrolled down to **"Add project"** when clicked on the add project. It then took me to a new page, displaying this error message **"Error 403 Register access required"**. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8510 Add HTTP Header Add Permissions-Policy
- **status**: in-progress --> closed - **Reviewer**: Dave Brondsema --- ** [tickets:#8510] Add HTTP Header Add Permissions-Policy** **Status:** closed **Milestone:** unreleased **Created:** Thu May 11, 2023 02:26 PM UTC by Guillermo Cruz **Last Updated:** Thu May 11, 2023 02:26 PM UTC **Owner:** Guillermo Cruz Add a new header to disable features for iframes --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8509 Upgrade markdown to lastest version
- **status**: in-progress --> closed --- ** [tickets:#8509] Upgrade markdown to lastest version** **Status:** closed **Milestone:** unreleased **Created:** Wed May 03, 2023 04:59 PM UTC by Guillermo Cruz **Last Updated:** Wed May 03, 2023 04:59 PM UTC **Owner:** Guillermo Cruz Upgrade from 3.3.7 to 3.4.1 --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8504 CSP Headers Add Support For script-src-attr
- **status**: in-progress --> closed --- ** [tickets:#8504] CSP Headers Add Support For script-src-attr** **Status:** closed **Milestone:** unreleased **Created:** Tue Mar 14, 2023 05:40 PM UTC by Guillermo Cruz **Last Updated:** Tue Mar 14, 2023 05:40 PM UTC **Owner:** Guillermo Cruz Add support and remove inline events like `onclick` `onkeyup` etc. from code. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8507 Python Package Upgrades
- **status**: in-progress --> closed --- ** [tickets:#8507] Python Package Upgrades** **Status:** closed **Milestone:** unreleased **Created:** Fri Apr 21, 2023 04:39 PM UTC by Guillermo Cruz **Last Updated:** Fri Apr 21, 2023 04:39 PM UTC **Owner:** Guillermo Cruz upgrade Python packages --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
Re: /allura-data ?
On 4/27/23 6:05 PM, Jon Labrie wrote: Hi - Trying a new install. In production-docker-example.ini I find this instruction: Copy this file to /allura-data/production.ini allura-data doesn’t seem to exist; am I supposed to create it (at root level)? Or should it be ~/allura-data/production.ini? Or…? Thanks for any guidance. Best, Jon Hi! IIRC, inside docker it is /allura-data and outside docker it is a local ./allura-data directory. Have you run through the installation with the default ini file (docker-dev.ini) yet? I think the first time you go through the steps it'll create the allura-data directory, which should help you locate it. -- Dave Brondsema : d...@brondsema.net http://www.brondsema.net : personal http://www.splike.com : programming <><
[allura:tickets] #8505 python 3.11 - jenkins setup
- **status**: review --> closed - **assigned_to**: Dillon Walls --- ** [tickets:#8505] python 3.11 - jenkins setup** **Status:** closed **Milestone:** unreleased **Created:** Wed Mar 29, 2023 04:39 PM UTC by Dave Brondsema **Last Updated:** Fri Apr 21, 2023 09:50 PM UTC **Owner:** Dillon Walls Update Apache jenkins (https://builds.apache.org/job/Allura/) and add a build for py3.11. It currently has a build for 3.7 only. (Probably can skip all those in-between right?) The docker/compose setup supports passing in which version you want already, like: `--build-arg PY_VERSION=3.8` See `allura/scripts/jenkins-python3.7.sh` for current setup Update Allura docs where it mentions 3.7 to say 3.7 through 3.11 are supported. Make a release next? Update default version sometime? --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8506 Incorrect links to ticket search rss feeds
--- ** [tickets:#8506] Incorrect links to ticket search rss feeds** **Status:** open **Milestone:** unreleased **Created:** Fri Apr 07, 2023 04:21 PM UTC by Dave Brondsema **Last Updated:** Fri Apr 07, 2023 04:21 PM UTC **Owner:** nobody On ticket searches for example /p/test/tickets/search/?q=foo we have these references which are wrong: ```html ``` Check the ForgeTracker code to see if we have any support for feeds of a ticket search. I think probably not, in which case we should remove those links. (Make sure to keep them on other types of ticket pages where appropriate) And then ideally we should make those urls like ../search/feed.rss and ../search/feed.atom return a 410 Gone status so bots stop trying to crawl them. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #6847 OAuth improvement: track last access time
--- ** [tickets:#6847] OAuth improvement: track last access time** **Status:** duplicate **Milestone:** unreleased **Labels:** bitesize **Created:** Tue Nov 05, 2013 06:17 PM UTC by Cory Johns **Last Updated:** Sat Mar 07, 2015 05:55 PM UTC **Owner:** nobody We should record the last access time for an `OAuthAccessToken` when it is used and present that information on the OAuth settings page. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] Ticket 6847 discussion
- **status**: open --> duplicate - **Comment**: Done in [#8405] --- ** [tickets:#6847] OAuth improvement: track last access time** **Status:** duplicate **Milestone:** unreleased **Labels:** bitesize **Created:** Tue Nov 05, 2013 06:17 PM UTC by Cory Johns **Last Updated:** Sat Mar 07, 2015 05:55 PM UTC **Owner:** nobody We should record the last access time for an `OAuthAccessToken` when it is used and present that information on the OAuth settings page. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8501 remove twemoji
- **status**: open --> closed --- ** [tickets:#8501] remove twemoji** **Status:** closed **Milestone:** unreleased **Created:** Thu Feb 23, 2023 07:27 PM UTC by Dave Brondsema **Last Updated:** Thu Feb 23, 2023 07:27 PM UTC **Owner:** nobody The "twemoji" library was added to replace emoji characters with images. I guess in case the OS/browser doesn't support some of the emoji? This was done back in https://forge-allura.apache.org/p/allura/git/merge-requests/135/ We self-hosted the .js file for twemoji but not the images. And now the images from maxcdn aren't loading. https://github.com/twitter/twemoji#cdn-support I think we should just remove twemoji and rely on native emoji rendering, I think its good enough. And that's what's happening right now since the images don't load :smile: --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
python support up through 3.11!
With a recent merge request https://forge-allura.apache.org/p/allura/git/merge-requests/396/ from contributor Ellery, Allura now works on python 3.7 all the way up through 3.11. Next steps I think are: - updating jenkins & docs to cover 3.11 https://forge-allura.apache.org/p/allura/tickets/8505/ - make a release? - make 3.11 the default - drop 3.7 when its end-of-life in a few months? Or keep supporting as long as practical. https://endoflife.date/python (FWIW, Ellery works at SourceForge with me and some other Allura devs) -- Dave Brondsema : d...@brondsema.net http://www.brondsema.net : personal http://www.splike.com : programming <><
[allura:tickets] #8505 python 3.11 - jenkins setup
--- ** [tickets:#8505] python 3.11 - jenkins setup** **Status:** open **Milestone:** unreleased **Created:** Wed Mar 29, 2023 04:39 PM UTC by Dave Brondsema **Last Updated:** Wed Mar 29, 2023 04:39 PM UTC **Owner:** nobody Update Apache jenkins (https://builds.apache.org/job/Allura/) and add a build for py3.11. It currently has a build for 3.7 only. (Probably can skip all those in-between right?) The docker/compose setup supports passing in which version you want already, like: `--build-arg PY_VERSION=3.8` See `allura/scripts/jenkins-python3.7.sh` for current setup Update Allura docs where it mentions 3.7 to say 3.7 through 3.11 are supported. Make a release next? Update default version sometime? --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8503 Fix some Deprecation Warnings
- **status**: open --> closed --- ** [tickets:#8503] Fix some Deprecation Warnings** **Status:** closed **Milestone:** unreleased **Created:** Tue Mar 07, 2023 07:13 PM UTC by Dillon Walls **Last Updated:** Tue Mar 07, 2023 07:13 PM UTC **Owner:** Dillon Walls --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8502 Replace pyflake with ruff
- **status**: in-progress --> closed - **Reviewer**: Dave Brondsema --- ** [tickets:#8502] Replace pyflake with ruff** **Status:** closed **Milestone:** unreleased **Created:** Mon Mar 06, 2023 06:37 PM UTC by Guillermo Cruz **Last Updated:** Mon Mar 06, 2023 06:37 PM UTC **Owner:** Guillermo Cruz Setup ruff and fix code issues that might appear. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8500 upgrade TurboGears
- **status**: in-progress --> review - **Comment**: on branch db/8500 --- ** [tickets:#8500] upgrade TurboGears** **Status:** review **Milestone:** unreleased **Created:** Thu Feb 16, 2023 08:40 PM UTC by Dave Brondsema **Last Updated:** Thu Feb 16, 2023 08:40 PM UTC **Owner:** Dave Brondsema --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8501 remove twemoji
--- ** [tickets:#8501] remove twemoji** **Status:** open **Milestone:** unreleased **Created:** Thu Feb 23, 2023 07:27 PM UTC by Dave Brondsema **Last Updated:** Thu Feb 23, 2023 07:27 PM UTC **Owner:** nobody The "twemoji" library was added to replace emoji characters with images. I guess in case the OS/browser doesn't support some of the emoji? This was done back in https://forge-allura.apache.org/p/allura/git/merge-requests/135/ We self-hosted the .js file for twemoji but not the images. And now the images from maxcdn aren't loading. https://github.com/twitter/twemoji#cdn-support I think we should just remove twemoji and rely on native emoji rendering, I think its good enough. And that's what's happening right now since the images don't load :smile: --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8500 upgrade TurboGears
--- ** [tickets:#8500] upgrade TurboGears** **Status:** in-progress **Milestone:** unreleased **Created:** Thu Feb 16, 2023 08:40 PM UTC by Dave Brondsema **Last Updated:** Thu Feb 16, 2023 08:40 PM UTC **Owner:** Dave Brondsema --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8498 PEP8 Cleanup
- **status**: in-progress --> closed --- ** [tickets:#8498] PEP8 Cleanup** **Status:** closed **Milestone:** unreleased **Created:** Wed Feb 08, 2023 08:37 PM UTC by Guillermo Cruz **Last Updated:** Wed Feb 08, 2023 08:37 PM UTC **Owner:** Guillermo Cruz Look for files that have the most violations and clean them up. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8496 Trove Category Skip Limit for Admins
- **status**: in-progress --> closed - **Reviewer**: Dave Brondsema --- ** [tickets:#8496] Trove Category Skip Limit for Admins** **Status:** closed **Milestone:** unreleased **Created:** Fri Feb 03, 2023 09:03 PM UTC by Guillermo Cruz **Last Updated:** Fri Feb 03, 2023 09:03 PM UTC **Owner:** Guillermo Cruz When adding a trove category there's a limit set but this should not apply if the user is a site admin --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8497 ForgeMarkdown speedup
- **status**: in-progress --> review - **Comment**: db/8497 --- ** [tickets:#8497] ForgeMarkdown speedup** **Status:** review **Milestone:** unreleased **Labels:** performance **Created:** Tue Feb 07, 2023 02:46 PM UTC by Dave Brondsema **Last Updated:** Tue Feb 07, 2023 02:46 PM UTC **Owner:** Dave Brondsema `g.forge_markdown` constructs a new `ForgeMarkdown` with a lot of extensions every time it is used. This can be a bit expensive. Re-using the same instance would probably require updates/fixes to some of our custom extensions. But lots of times `cached_convert` is used and gets a cached result so a full Markdown instance doesn't even need to be created then. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8495 fix DeprecationWarnings
- **status**: in-progress --> closed - **Reviewer**: Dave Brondsema --- ** [tickets:#8495] fix DeprecationWarnings** **Status:** closed **Milestone:** unreleased **Created:** Tue Jan 24, 2023 07:50 PM UTC by Dillon Walls **Last Updated:** Tue Jan 24, 2023 07:50 PM UTC **Owner:** Dillon Walls There are several DeprecationWarnings that pytest unearthed. Let's get them fixed! --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8497 ForgeMarkdown speedup
--- ** [tickets:#8497] ForgeMarkdown speedup** **Status:** in-progress **Milestone:** unreleased **Labels:** performance **Created:** Tue Feb 07, 2023 02:46 PM UTC by Dave Brondsema **Last Updated:** Tue Feb 07, 2023 02:46 PM UTC **Owner:** Dave Brondsema `g.forge_markdown` constructs a new `ForgeMarkdown` with a lot of extensions every time it is used. This can be a bit expensive. Re-using the same instance would probably require updates/fixes to some of our custom extensions. But lots of times `cached_convert` is used and gets a cached result so a full Markdown instance doesn't even need to be created then. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8491 JS Libraries Tablesorter and Sylvester
- **status**: open --> closed - **assigned_to**: Guillermo Cruz --- ** [tickets:#8491] JS Libraries Tablesorter and Sylvester** **Status:** closed **Milestone:** unreleased **Created:** Tue Jan 17, 2023 06:07 PM UTC by Guillermo Cruz **Last Updated:** Fri Jan 20, 2023 04:38 PM UTC **Owner:** Guillermo Cruz tablesorter.js needs an upgrade and sylvester.js needs to be minified instead of being compressed/obfuscated. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8493 Make tracking snippet more self-contained
- **status**: open --> closed - **assigned_to**: Dillon Walls --- ** [tickets:#8493] Make tracking snippet more self-contained** **Status:** closed **Milestone:** unreleased **Created:** Thu Jan 19, 2023 07:52 PM UTC by Dillon Walls **Last Updated:** Thu Jan 19, 2023 07:52 PM UTC **Owner:** Dillon Walls The google analytics tracking macro assumes it will be executed from within a
[allura:tickets] #8491 JS Libraries Tablesorter and Sylvester
I didn't know what "sylvester" was. It's hardly mentioned anywhere in our codebase. `git log -G sylvester` shows [9d390e545382040cd84cae8b278b67e973199684] for IE support. Can you look into removing sylvester completely? I think we can drop IE support for this, just make sure things work fine in modern browsers still. I think CSS rules for `headerSortUp` `headerSortDown` need to be updated? --- ** [tickets:#8491] JS Libraries Tablesorter and Sylvester** **Status:** open **Milestone:** unreleased **Created:** Tue Jan 17, 2023 06:07 PM UTC by Guillermo Cruz **Last Updated:** Tue Jan 17, 2023 06:07 PM UTC **Owner:** nobody tablesorter.js needs an upgrade and sylvester.js needs to be minified instead of being compressed/obfuscated. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8490 Fix Failing Parallel Tests
- **status**: review --> closed - **Reviewer**: Dave Brondsema --- ** [tickets:#8490] Fix Failing Parallel Tests** **Status:** closed **Milestone:** unreleased **Created:** Tue Jan 17, 2023 02:33 PM UTC by Dillon Walls **Last Updated:** Tue Jan 17, 2023 02:33 PM UTC **Owner:** Dillon Walls Some tests intermittently fail when run in parallel now that we're on pytest. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8484 Add Support For Fediverse Addresses
- **status**: in-progress --> closed - **Reviewer**: Dillon Walls --- ** [tickets:#8484] Add Support For Fediverse Addresses** **Status:** closed **Milestone:** unreleased **Created:** Fri Dec 09, 2022 05:32 PM UTC by Guillermo Cruz **Last Updated:** Fri Dec 09, 2022 05:32 PM UTC **Owner:** Guillermo Cruz Enable users and projects to set fediverse username addresses --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8489 support python 3.8
- **status**: in-progress --> review - **Comment**: db/8489 --- ** [tickets:#8489] support python 3.8** **Status:** review **Milestone:** unreleased **Created:** Fri Jan 13, 2023 06:22 PM UTC by Dave Brondsema **Last Updated:** Fri Jan 13, 2023 06:22 PM UTC **Owner:** Dave Brondsema Currently only python 3.7 is supported. Shouldn't be too hard to get it running on 3.8 We can *allow* the Docker container to install 3.8 but leave the **default** to 3.7 I imagine we'll have more tickets to support 3.9, 3.10, 3.11. And then at the end can make the docker default be 3.11 or something like that. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8487 Enable Analytics In Debug Mode
- **status**: open --> closed - **assigned_to**: Dillon Walls - **Reviewer**: Dave Brondsema --- ** [tickets:#8487] Enable Analytics In Debug Mode** **Status:** closed **Milestone:** unreleased **Created:** Thu Dec 22, 2022 10:19 PM UTC by Dillon Walls **Last Updated:** Thu Dec 22, 2022 10:19 PM UTC **Owner:** Dillon Walls --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8489 support python 3.8
--- ** [tickets:#8489] support python 3.8** **Status:** in-progress **Milestone:** unreleased **Created:** Fri Jan 13, 2023 06:22 PM UTC by Dave Brondsema **Last Updated:** Fri Jan 13, 2023 06:22 PM UTC **Owner:** Dave Brondsema Currently only python 3.7 is supported. Shouldn't be too hard to get it running on 3.8 We can *allow* the Docker container to install 3.8 but leave the **default** to 3.7 I imagine we'll have more tickets to support 3.9, 3.10, 3.11. And then at the end can make the docker default be 3.11 or something like that. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8483 Markdown: image target URL fails when reaches 100 chars + FIX(?)
- **status**: open --> closed - **assigned_to**: Dave Brondsema - **Comment**: The limit was initially done in [#8410] and then when [#8416] was done the limit wasn't needed at all any more, but we didn't realize it. So I've pushed a fix to remove the limit. (FYI this will probably go live on SourceForge later this week and then you'll need to edit your wiki page to make it update, since markdown outputs are cached) --- ** [tickets:#8483] Markdown: image target URL fails when reaches 100 chars + FIX(?)** **Status:** closed **Milestone:** unreleased **Created:** Wed Dec 07, 2022 05:59 PM UTC by Bogdan Drozdowski **Last Updated:** Sat Dec 24, 2022 07:13 PM UTC **Owner:** Dave Brondsema **Attachments:** - [link-limit-250-chars.diff](https://forge-allura.apache.org/p/allura/tickets/8483/attachment/link-limit-250-chars.diff) (587 Bytes; text/x-patch) Hi. I've noticed on the wiki (on SourceForge) that some "image badges" and their links are not rendered correctly. Namely, the image is rendered, but links to some weird URL while the correct URL is rendered as plain text right after the image. Sample: https://sourceforge.net/p/wipefreespace/wiki/Sandbox/ (hover the mouse over the image to see the URL). Perhaps it's just an error on SF, but I've noticed that the failing link "suspiciously" exceeds 100 characters, while the working one doesn't. Looks like some hard-coded limit. Links nowadays can contain commit hashes or other long IDs, so I think the limit should be raised. I've done a little digging in the code (although I'm far from being an expert in Python or any other technology used here) and may have found the place to fix this. You can use the simple patch I'm attaching, or fix it in some other place (I haven't done any testing) or perhaps fix the "TODO" in the code and maybe get rid of the problem the right way. Regards and thank you for your work! --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8483 Markdown: image target URL fails when reaches 100 chars + FIX(?)
Thanks for this suggestion. We'll probably investigate it in January. It hasn't been forgotten :) --- ** [tickets:#8483] Markdown: image target URL fails when reaches 100 chars + FIX(?)** **Status:** open **Milestone:** unreleased **Created:** Wed Dec 07, 2022 05:59 PM UTC by Bogdan Drozdowski **Last Updated:** Wed Dec 07, 2022 05:59 PM UTC **Owner:** nobody **Attachments:** - [link-limit-250-chars.diff](https://forge-allura.apache.org/p/allura/tickets/8483/attachment/link-limit-250-chars.diff) (587 Bytes; text/x-patch) Hi. I've noticed on the wiki (on SourceForge) that some "image badges" and their links are not rendered correctly. Namely, the image is rendered, but links to some weird URL while the correct URL is rendered as plain text right after the image. Sample: https://sourceforge.net/p/wipefreespace/wiki/Sandbox/ (hover the mouse over the image to see the URL). Perhaps it's just an error on SF, but I've noticed that the failing link "suspiciously" exceeds 100 characters, while the working one doesn't. Looks like some hard-coded limit. Links nowadays can contain commit hashes or other long IDs, so I think the limit should be raised. I've done a little digging in the code (although I'm far from being an expert in Python or any other technology used here) and may have found the place to fix this. You can use the simple patch I'm attaching, or fix it in some other place (I haven't done any testing) or perhaps fix the "TODO" in the code and maybe get rid of the problem the right way. Regards and thank you for your work! --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8486 Git should look for 'main' branch
- **status**: open --> review - **Comment**: db/8486 --- ** [tickets:#8486] Git should look for 'main' branch** **Status:** review **Milestone:** unreleased **Created:** Mon Dec 19, 2022 09:59 PM UTC by Dave Brondsema **Last Updated:** Mon Dec 19, 2022 09:59 PM UTC **Owner:** nobody I noticed on a repo that was imported, it had a `main` branch and some others, and Allura's logic to find a default branch didn't work well. It didn't find `master` so it defaulted to the first one. We should look for `main` as a possible default. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8486 Git should look for 'main' branch
--- ** [tickets:#8486] Git should look for 'main' branch** **Status:** open **Milestone:** unreleased **Created:** Mon Dec 19, 2022 09:59 PM UTC by Dave Brondsema **Last Updated:** Mon Dec 19, 2022 09:59 PM UTC **Owner:** nobody I noticed on a repo that was imported, it had a `main` branch and some others, and Allura's logic to find a default branch didn't work well. It didn't find `master` so it defaulted to the first one. We should look for `main` as a possible default. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8485 Commit references get removed
--- ** [tickets:#8485] Commit references get removed** **Status:** open **Milestone:** unreleased **Created:** Fri Dec 16, 2022 06:58 PM UTC by Dave Brondsema **Last Updated:** Fri Dec 16, 2022 06:58 PM UTC **Owner:** nobody If an artifact like a ticket has commit references (created by `repo_refresh.py`'s `update_artifact_refs`) and then the ticket is updated, those references get removed. Could it be that the function is saving them as forward references from the ticket, but they should be back references (commit to ticket)? Just specualting --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8482 saved comments (memorable) race condition
- **status**: open --> review - **Comment**: db/8482 Apparently its "normal" for jquery to be able to run `load` events before `domready` sometimes. https://stackoverflow.com/questions/61910610/window-onload-fires-before-jquery-document-ready-in-firefox --- ** [tickets:#8482] saved comments (memorable) race condition** **Status:** review **Milestone:** unreleased **Created:** Tue Dec 06, 2022 07:32 PM UTC by Dave Brondsema **Last Updated:** Tue Dec 06, 2022 07:32 PM UTC **Owner:** Dave Brondsema Sometimes the `Memorable.add` from `sf_markitup.js` runs before `memorable.js` initializes itself. This means that sometimes when you submit a comment, when the page reloads it'll show your comment in the edit box again, incorrectly. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8482 saved comments (memorable) race condition
--- ** [tickets:#8482] saved comments (memorable) race condition** **Status:** open **Milestone:** unreleased **Created:** Tue Dec 06, 2022 07:32 PM UTC by Dave Brondsema **Last Updated:** Tue Dec 06, 2022 07:32 PM UTC **Owner:** Dave Brondsema Sometimes the `Memorable.add` from `sf_markitup.js` runs before `memorable.js` initializes itself. This means that sometimes when you submit a comment, when the page reloads it'll show your comment in the edit box again, incorrectly. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8481 Commit Activity More Context
- **status**: open --> closed - **Reviewer**: Dave Brondsema --- ** [tickets:#8481] Commit Activity More Context** **Status:** closed **Milestone:** unreleased **Created:** Wed Nov 23, 2022 07:58 PM UTC by Guillermo Cruz **Last Updated:** Wed Nov 23, 2022 07:59 PM UTC **Owner:** Guillermo Cruz In project activity would be useful to display the project name and the repo or mount label of the code tool --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8479 CSP Headers Add Support For script-src
- **status**: in-progress --> closed - **Reviewer**: Dave Brondsema --- ** [tickets:#8479] CSP Headers Add Support For script-src** **Status:** closed **Milestone:** unreleased **Created:** Thu Nov 17, 2022 05:08 PM UTC by Guillermo Cruz **Last Updated:** Thu Nov 17, 2022 05:08 PM UTC **Owner:** Guillermo Cruz Continuing with the previous work related to `Content-Security-Policy` headers we are adding support for `script-src` this time. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8480 More package upgrades
- **status**: review --> closed - **Reviewer**: Dave Brondsema --- ** [tickets:#8480] More package upgrades** **Status:** closed **Milestone:** unreleased **Created:** Mon Nov 21, 2022 03:29 PM UTC by Dillon Walls **Last Updated:** Mon Nov 21, 2022 03:29 PM UTC **Owner:** Dillon Walls --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8478 upgrade importlib-metadata to 5
- **status**: in-progress --> closed --- ** [tickets:#8478] upgrade importlib-metadata to 5** **Status:** closed **Milestone:** unreleased **Created:** Wed Nov 16, 2022 09:04 PM UTC by Dillon Walls **Last Updated:** Wed Nov 16, 2022 09:04 PM UTC **Owner:** Dillon Walls --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8476 Upgrade Underscore Library
- **status**: open --> closed --- ** [tickets:#8476] Upgrade Underscore Library** **Status:** closed **Milestone:** unreleased **Created:** Wed Nov 09, 2022 09:33 PM UTC by Guillermo Cruz **Last Updated:** Wed Nov 09, 2022 09:49 PM UTC **Owner:** nobody Current version is 1.8.3 we should upgrade to the latest release --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8475 Return 404 on "Awaiting Moderation" Threads
- **status**: review --> closed - **Reviewer**: Dave Brondsema --- ** [tickets:#8475] Return 404 on "Awaiting Moderation" Threads ** **Status:** closed **Milestone:** unreleased **Created:** Wed Nov 02, 2022 03:14 PM UTC by Guillermo Cruz **Last Updated:** Fri Nov 04, 2022 05:33 PM UTC **Owner:** Guillermo Cruz Content on threads that are awaiting moderation should not be indexed by search engines. Return a 404 status code but allow administrators to moderate the content. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8455 Convert from nosetests to pytest
- **status**: in-progress --> closed - **assigned_to**: Kenton Taylor --> Dillon Walls --- ** [tickets:#8455] Convert from nosetests to pytest** **Status:** closed **Milestone:** unreleased **Created:** Mon Aug 22, 2022 07:10 PM UTC by Kenton Taylor **Last Updated:** Mon Aug 22, 2022 07:10 PM UTC **Owner:** Dillon Walls --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
