You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@allura.apache.org by Dave Brondsema <da...@brondsema.net> on 2015/06/09 22:44:54 UTC
[allura:tickets] #7894 Don't update merge request timestamps incorrectly
---
** [tickets:#7894] Don't update merge request timestamps incorrectly**
**Status:** open
**Milestone:** unreleased
**Labels:** merge-requests
**Created:** Tue Jun 09, 2015 08:44 PM UTC by Dave Brondsema
**Last Updated:** Tue Jun 09, 2015 08:44 PM UTC
**Owner:** nobody
Merge request's "updated" timestamp changes when you view it and it calculates if a one-click merge is possible. That shouldn't happen. Make sure no other operations incorrectly update the timestamp either.
---
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] #7894 Don't update merge request timestamps incorrectly
Posted by Dave Brondsema <da...@brondsema.net>.
- **labels**: merge-requests, sf-2, sf-current --> merge-requests, sf-2
---
** [tickets:#7894] Don't update merge request timestamps incorrectly**
**Status:** closed
**Milestone:** unreleased
**Labels:** merge-requests sf-2
**Created:** Tue Jun 09, 2015 08:44 PM UTC by Dave Brondsema
**Last Updated:** Fri Jul 03, 2015 11:05 AM UTC
**Owner:** Heith Seewald
Merge request's "updated" timestamp changes when you view it and it calculates if a one-click merge is possible. That shouldn't happen. Make sure no other operations incorrectly update the timestamp either.
---
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] Re: #7894 Don't update merge request timestamps incorrectly
Posted by Igor Bondarenko <je...@gmail.com>.
One option is flushing inside `set_can_merge_cache`, thus inside context manager
---
** [tickets:#7894] Don't update merge request timestamps incorrectly**
**Status:** in-progress
**Milestone:** unreleased
**Labels:** merge-requests sf-2 sf-current
**Created:** Tue Jun 09, 2015 08:44 PM UTC by Dave Brondsema
**Last Updated:** Wed Jul 01, 2015 03:22 PM UTC
**Owner:** Heith Seewald
Merge request's "updated" timestamp changes when you view it and it calculates if a one-click merge is possible. That shouldn't happen. Make sure no other operations incorrectly update the timestamp either.
---
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] #7894 Don't update merge request timestamps incorrectly
Posted by Dave Brondsema <da...@brondsema.net>.
Also I think `skip_mod_date` only works when the changes are flushed, not when you are setting the values. If that's correct, we might need to set it directly and leave it (not context manager), or think of some other approach.
---
** [tickets:#7894] Don't update merge request timestamps incorrectly**
**Status:** in-progress
**Milestone:** unreleased
**Labels:** merge-requests sf-2 sf-current
**Created:** Tue Jun 09, 2015 08:44 PM UTC by Dave Brondsema
**Last Updated:** Wed Jul 01, 2015 02:24 PM UTC
**Owner:** Heith Seewald
Merge request's "updated" timestamp changes when you view it and it calculates if a one-click merge is possible. That shouldn't happen. Make sure no other operations incorrectly update the timestamp either.
---
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] #7894 Don't update merge request timestamps incorrectly
Posted by Heith Seewald <hs...@slashdotmedia.com>.
- **status**: open --> in-progress
- **assigned_to**: Heith Seewald
---
** [tickets:#7894] Don't update merge request timestamps incorrectly**
**Status:** in-progress
**Milestone:** unreleased
**Labels:** merge-requests sf-2 sf-current
**Created:** Tue Jun 09, 2015 08:44 PM UTC by Dave Brondsema
**Last Updated:** Mon Jun 15, 2015 03:48 PM UTC
**Owner:** Heith Seewald
Merge request's "updated" timestamp changes when you view it and it calculates if a one-click merge is possible. That shouldn't happen. Make sure no other operations incorrectly update the timestamp either.
---
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] #7894 Don't update merge request timestamps incorrectly
Posted by Dave Brondsema <da...@brondsema.net>.
- **labels**: merge-requests, sf-2 --> merge-requests, sf-2, sf-current
---
** [tickets:#7894] Don't update merge request timestamps incorrectly**
**Status:** open
**Milestone:** unreleased
**Labels:** merge-requests sf-2 sf-current
**Created:** Tue Jun 09, 2015 08:44 PM UTC by Dave Brondsema
**Last Updated:** Mon Jun 15, 2015 03:47 PM UTC
**Owner:** nobody
Merge request's "updated" timestamp changes when you view it and it calculates if a one-click merge is possible. That shouldn't happen. Make sure no other operations incorrectly update the timestamp either.
---
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] #7894 Don't update merge request timestamps incorrectly
Posted by Igor Bondarenko <je...@gmail.com>.
- **status**: review --> in-progress
- **Comment**:
I've rebased on a new master and removed a couple of unused dependencies from previous commits. See `ib/7894`
That works fine, but few tests are failing https://forge-allura.apache.org/p/allura/pastebin/5594fec86d19cd6b98fe5b42
---
** [tickets:#7894] Don't update merge request timestamps incorrectly**
**Status:** in-progress
**Milestone:** unreleased
**Labels:** merge-requests sf-2 sf-current
**Created:** Tue Jun 09, 2015 08:44 PM UTC by Dave Brondsema
**Last Updated:** Wed Jul 01, 2015 05:40 PM UTC
**Owner:** Heith Seewald
Merge request's "updated" timestamp changes when you view it and it calculates if a one-click merge is possible. That shouldn't happen. Make sure no other operations incorrectly update the timestamp either.
---
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] #7894 Don't update merge request timestamps incorrectly
Posted by Heith Seewald <hs...@slashdotmedia.com>.
- **status**: in-progress --> review
- **Comment**:
Review at **hs/7894**
---
** [tickets:#7894] Don't update merge request timestamps incorrectly**
**Status:** review
**Milestone:** unreleased
**Labels:** merge-requests sf-2 sf-current
**Created:** Tue Jun 09, 2015 08:44 PM UTC by Dave Brondsema
**Last Updated:** Mon Jun 15, 2015 06:04 PM UTC
**Owner:** Heith Seewald
Merge request's "updated" timestamp changes when you view it and it calculates if a one-click merge is possible. That shouldn't happen. Make sure no other operations incorrectly update the timestamp either.
---
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] #7894 Don't update merge request timestamps incorrectly
Posted by Dave Brondsema <da...@brondsema.net>.
- **labels**: merge-requests --> merge-requests, sf-2
---
** [tickets:#7894] Don't update merge request timestamps incorrectly**
**Status:** open
**Milestone:** unreleased
**Labels:** merge-requests sf-2
**Created:** Tue Jun 09, 2015 08:44 PM UTC by Dave Brondsema
**Last Updated:** Tue Jun 09, 2015 08:44 PM UTC
**Owner:** nobody
Merge request's "updated" timestamp changes when you view it and it calculates if a one-click merge is possible. That shouldn't happen. Make sure no other operations incorrectly update the timestamp either.
---
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] #7894 Don't update merge request timestamps incorrectly
Posted by Heith Seewald <hs...@slashdotmedia.com>.
- **status**: in-progress --> review
- **Comment**:
Review at:
*Allura hs/7894*
*Forge-classic hs/7894*
I ended up moving skip_mod_date into Allura *(allura.lib.utils)*.
---
** [tickets:#7894] Don't update merge request timestamps incorrectly**
**Status:** review
**Milestone:** unreleased
**Labels:** merge-requests sf-2 sf-current
**Created:** Tue Jun 09, 2015 08:44 PM UTC by Dave Brondsema
**Last Updated:** Tue Jun 16, 2015 12:10 PM UTC
**Owner:** Heith Seewald
Merge request's "updated" timestamp changes when you view it and it calculates if a one-click merge is possible. That shouldn't happen. Make sure no other operations incorrectly update the timestamp either.
---
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] #7894 Don't update merge request timestamps incorrectly
Posted by Igor Bondarenko <je...@gmail.com>.
- **status**: review --> in-progress
- **Comment**:
I'm getting errors like this from the task
~~~~~
Traceback (most recent call last):
File "/home/ibondarenko/ibondarenko-1154/forge/Allura/allura/model/monq_model.py", line 260, in __call__
self.result = func(*self.args, **self.kwargs)
File "/home/ibondarenko/ibondarenko-1154/forge/Allura/allura/tasks/repo_tasks.py", line 174, in can_merge
mr.set_can_merge_cache(result)
File "/home/ibondarenko/ibondarenko-1154/forge/Allura/allura/model/repository.py", line 854, in set_can_merge_cache
with utils.skip_mod_date(self):
File "/usr/lib64/python2.7/contextlib.py", line 17, in __enter__
return self.gen.next()
File "/home/ibondarenko/ibondarenko-1154/forge/Allura/allura/lib/utils.py", line 623, in skip_mod_date
skip_mod_date = getattr(session(model_cls)._get(), 'skip_mod_date', False)
AttributeError: 'ODMSession' object has no attribute '_get'
~~~~~
Also, do we really need `with skip_mod_date` inside both `can_merge` task and `set_can_merge_cache`. It seems to me that skipping it just in `set_can_merge_cache` should be sufficient. Or `repo.can_merge` also modifies merge request objects somehow?
---
** [tickets:#7894] Don't update merge request timestamps incorrectly**
**Status:** in-progress
**Milestone:** unreleased
**Labels:** merge-requests sf-2 sf-current
**Created:** Tue Jun 09, 2015 08:44 PM UTC by Dave Brondsema
**Last Updated:** Mon Jun 29, 2015 08:31 PM UTC
**Owner:** Heith Seewald
Merge request's "updated" timestamp changes when you view it and it calculates if a one-click merge is possible. That shouldn't happen. Make sure no other operations incorrectly update the timestamp either.
---
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] #7894 Don't update merge request timestamps incorrectly
Posted by Heith Seewald <hs...@slashdotmedia.com>.
- **status**: in-progress --> review
- **Comment**:
Force pushed to **hs/7894**
`tests.model.test_repo.TestMergeRequest` are now passing.
---
** [tickets:#7894] Don't update merge request timestamps incorrectly**
**Status:** review
**Milestone:** unreleased
**Labels:** merge-requests sf-2 sf-current
**Created:** Tue Jun 09, 2015 08:44 PM UTC by Dave Brondsema
**Last Updated:** Thu Jul 02, 2015 09:07 AM UTC
**Owner:** Heith Seewald
Merge request's "updated" timestamp changes when you view it and it calculates if a one-click merge is possible. That shouldn't happen. Make sure no other operations incorrectly update the timestamp either.
---
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] #7894 Don't update merge request timestamps incorrectly
Posted by Igor Bondarenko <je...@gmail.com>.
- **status**: review --> closed
---
** [tickets:#7894] Don't update merge request timestamps incorrectly**
**Status:** closed
**Milestone:** unreleased
**Labels:** merge-requests sf-2 sf-current
**Created:** Tue Jun 09, 2015 08:44 PM UTC by Dave Brondsema
**Last Updated:** Thu Jul 02, 2015 03:14 PM UTC
**Owner:** Heith Seewald
Merge request's "updated" timestamp changes when you view it and it calculates if a one-click merge is possible. That shouldn't happen. Make sure no other operations incorrectly update the timestamp either.
---
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] #7894 Don't update merge request timestamps incorrectly
Posted by Heith Seewald <hs...@slashdotmedia.com>.
Ah, nice catch Igor, thanks.
---
** [tickets:#7894] Don't update merge request timestamps incorrectly**
**Status:** in-progress
**Milestone:** unreleased
**Labels:** merge-requests sf-2 sf-current
**Created:** Tue Jun 09, 2015 08:44 PM UTC by Dave Brondsema
**Last Updated:** Tue Jun 16, 2015 12:05 PM UTC
**Owner:** Heith Seewald
Merge request's "updated" timestamp changes when you view it and it calculates if a one-click merge is possible. That shouldn't happen. Make sure no other operations incorrectly update the timestamp either.
---
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] #7894 Don't update merge request timestamps incorrectly
Posted by Heith Seewald <hs...@slashdotmedia.com>.
- **status**: in-progress --> review
- **Comment**:
force-pushed to: **hs/7894**
I also added docstrings to `skip_mod_date` with some of the notes from this ticket.
---
** [tickets:#7894] Don't update merge request timestamps incorrectly**
**Status:** review
**Milestone:** unreleased
**Labels:** merge-requests sf-2 sf-current
**Created:** Tue Jun 09, 2015 08:44 PM UTC by Dave Brondsema
**Last Updated:** Wed Jul 01, 2015 03:22 PM UTC
**Owner:** Heith Seewald
Merge request's "updated" timestamp changes when you view it and it calculates if a one-click merge is possible. That shouldn't happen. Make sure no other operations incorrectly update the timestamp either.
---
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] #7894 Don't update merge request timestamps incorrectly
Posted by Igor Bondarenko <je...@gmail.com>.
- **Reviewer**: Igor Bondarenko
---
** [tickets:#7894] Don't update merge request timestamps incorrectly**
**Status:** review
**Milestone:** unreleased
**Labels:** merge-requests sf-2 sf-current
**Created:** Tue Jun 09, 2015 08:44 PM UTC by Dave Brondsema
**Last Updated:** Mon Jun 15, 2015 08:33 PM UTC
**Owner:** Heith Seewald
Merge request's "updated" timestamp changes when you view it and it calculates if a one-click merge is possible. That shouldn't happen. Make sure no other operations incorrectly update the timestamp either.
---
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] #7894 Don't update merge request timestamps incorrectly
Posted by Igor Bondarenko <je...@gmail.com>.
- **status**: review --> in-progress
- **Comment**:
This doesn't work for me. To test it properly you should disable caching inside `def can_merge`, like this:
~~~~
+# if cached is not None:
+# return cached
~~~~
This way task will be fired on every page hit.
I think to properly fix this we should set `skip_mod_date == True` in the beginning of the `repo_tasks.can_merge` and set it back to `False` in the end. Maybe it can even go inside `set_can_merge_cache()`, so that no matter from which place cache is updated it will not trigger `mod_date` update.
Also, we should consider adding context manager helper for this to the Allura, similar to one we use in SF internal code:
~~~~
@contextmanager
def skip_mod_date(model_cls):
skip_mod_date = getattr(session(model_cls)._get(), 'skip_mod_date', False)
session(model_cls)._get().skip_mod_date = True
try:
yield
finally:
session(model_cls)._get().skip_mod_date = skip_mod_date
~~~~
---
** [tickets:#7894] Don't update merge request timestamps incorrectly**
**Status:** in-progress
**Milestone:** unreleased
**Labels:** merge-requests sf-2 sf-current
**Created:** Tue Jun 09, 2015 08:44 PM UTC by Dave Brondsema
**Last Updated:** Tue Jun 16, 2015 11:39 AM UTC
**Owner:** Heith Seewald
Merge request's "updated" timestamp changes when you view it and it calculates if a one-click merge is possible. That shouldn't happen. Make sure no other operations incorrectly update the timestamp either.
---
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] Re: #7894 Don't update merge request timestamps incorrectly
Posted by Dave Brondsema <da...@brondsema.net>.
Thanks. I've fixed the failures on master.
---
** [tickets:#7894] Don't update merge request timestamps incorrectly**
**Status:** in-progress
**Milestone:** unreleased
**Labels:** merge-requests sf-2 sf-current
**Created:** Tue Jun 09, 2015 08:44 PM UTC by Dave Brondsema
**Last Updated:** Thu Jul 02, 2015 09:07 AM UTC
**Owner:** Heith Seewald
Merge request's "updated" timestamp changes when you view it and it calculates if a one-click merge is possible. That shouldn't happen. Make sure no other operations incorrectly update the timestamp either.
---
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] Re: #7894 Don't update merge request timestamps incorrectly
Posted by Igor Bondarenko <je...@gmail.com>.
Individually they pass, they fail only when run using `./run-tests` or:
~~~~~
$ cd ForgeGit && nosetests forgegit.tests.model.test_repository
~~~~~
---
** [tickets:#7894] Don't update merge request timestamps incorrectly**
**Status:** in-progress
**Milestone:** unreleased
**Labels:** merge-requests sf-2 sf-current
**Created:** Tue Jun 09, 2015 08:44 PM UTC by Dave Brondsema
**Last Updated:** Thu Jul 02, 2015 09:07 AM UTC
**Owner:** Heith Seewald
Merge request's "updated" timestamp changes when you view it and it calculates if a one-click merge is possible. That shouldn't happen. Make sure no other operations incorrectly update the timestamp either.
---
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] Re: #7894 Don't update merge request timestamps incorrectly
Posted by Dave Brondsema <da...@brondsema.net>.
How do `test_branches` and `test_tags` fail for you? I saw them fail at Apache Jenkins also, but couldn't reproduce it locally. I thought maybe it was because I lowered the default cache threshold, and it was a timing thing. But I still couldn't reproduce it locally with a setting of 0 or -1.
---
** [tickets:#7894] Don't update merge request timestamps incorrectly**
**Status:** in-progress
**Milestone:** unreleased
**Labels:** merge-requests sf-2 sf-current
**Created:** Tue Jun 09, 2015 08:44 PM UTC by Dave Brondsema
**Last Updated:** Thu Jul 02, 2015 09:07 AM UTC
**Owner:** Heith Seewald
Merge request's "updated" timestamp changes when you view it and it calculates if a one-click merge is possible. That shouldn't happen. Make sure no other operations incorrectly update the timestamp either.
---
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] Re: #7894 Don't update merge request timestamps incorrectly
Posted by Igor Bondarenko <je...@gmail.com>.
`test_branches` and `test_tags` are failing in master also :( There are one more test failure specific to this ticket, though
---
** [tickets:#7894] Don't update merge request timestamps incorrectly**
**Status:** in-progress
**Milestone:** unreleased
**Labels:** merge-requests sf-2 sf-current
**Created:** Tue Jun 09, 2015 08:44 PM UTC by Dave Brondsema
**Last Updated:** Thu Jul 02, 2015 09:07 AM UTC
**Owner:** Heith Seewald
Merge request's "updated" timestamp changes when you view it and it calculates if a one-click merge is possible. That shouldn't happen. Make sure no other operations incorrectly update the timestamp either.
---
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.