You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@allura.apache.org by Cory Johns <ma...@users.sf.net> on 2014/01/27 18:48:45 UTC
[allura:tickets] #7103 Stale project flush affects other tool imports
---
** [tickets:#7103] Stale project flush affects other tool imports**
**Status:** open
**Created:** Mon Jan 27, 2014 05:48 PM UTC by Cory Johns
**Last Updated:** Mon Jan 27, 2014 05:48 PM UTC
**Owner:** nobody
The stale project flushing issue that was fixed for repositories in [#7005] is still an issue for other long-running tool imports. Any time an artifact is saved, the `Artifact.__metaclass__.before_save` method updates `c.project.last_updated` which causes `c.project` to become dirty and, when flushed, overwrite any other changes to the project from another source.
For project imports, this can cause the metadata import (or even manual updates to the project metadata) to be overwritten by the tool imports.
---
Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #7103 Stale project flush affects other tool imports
Posted by Tim Van Steenburgh <va...@users.sf.net>.
- **status**: code-review --> closed
---
** [tickets:#7103] Stale project flush affects other tool imports**
**Status:** closed
**Created:** Mon Jan 27, 2014 05:48 PM UTC by Cory Johns
**Last Updated:** Mon Jan 27, 2014 09:23 PM UTC
**Owner:** Cory Johns
The stale project flushing issue that was fixed for repositories in [#7005] is still an issue for other long-running tool imports. Any time an artifact is saved, the `Artifact.__metaclass__.before_save` method updates `c.project.last_updated` which causes `c.project` to become dirty and, when flushed, overwrite any other changes to the project from another source.
For project imports, this can cause the metadata import (or even manual updates to the project metadata) to be overwritten by the tool imports.
---
Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #7103 Stale project flush affects other tool imports
Posted by Cory Johns <ma...@users.sf.net>.
- **status**: open --> in-progress
- **assigned_to**: Cory Johns
- **Milestone**: forge-backlog --> forge-feb-7
---
** [tickets:#7103] Stale project flush affects other tool imports**
**Status:** in-progress
**Created:** Mon Jan 27, 2014 05:48 PM UTC by Cory Johns
**Last Updated:** Mon Jan 27, 2014 05:48 PM UTC
**Owner:** Cory Johns
The stale project flushing issue that was fixed for repositories in [#7005] is still an issue for other long-running tool imports. Any time an artifact is saved, the `Artifact.__metaclass__.before_save` method updates `c.project.last_updated` which causes `c.project` to become dirty and, when flushed, overwrite any other changes to the project from another source.
For project imports, this can cause the metadata import (or even manual updates to the project metadata) to be overwritten by the tool imports.
---
Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #7103 Stale project flush affects other tool imports
Posted by Cory Johns <ma...@users.sf.net>.
This could potentially affect ticket bulk edit, though that seems less likely to take long enough to have much chance of overlap.
---
** [tickets:#7103] Stale project flush affects other tool imports**
**Status:** in-progress
**Created:** Mon Jan 27, 2014 05:48 PM UTC by Cory Johns
**Last Updated:** Mon Jan 27, 2014 05:48 PM UTC
**Owner:** Cory Johns
The stale project flushing issue that was fixed for repositories in [#7005] is still an issue for other long-running tool imports. Any time an artifact is saved, the `Artifact.__metaclass__.before_save` method updates `c.project.last_updated` which causes `c.project` to become dirty and, when flushed, overwrite any other changes to the project from another source.
For project imports, this can cause the metadata import (or even manual updates to the project metadata) to be overwritten by the tool imports.
---
Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #7103 Stale project flush affects other tool imports
Posted by Cory Johns <ma...@users.sf.net>.
- **status**: in-progress --> code-review
- **Size**: --> 2
---
** [tickets:#7103] Stale project flush affects other tool imports**
**Status:** code-review
**Created:** Mon Jan 27, 2014 05:48 PM UTC by Cory Johns
**Last Updated:** Mon Jan 27, 2014 05:53 PM UTC
**Owner:** Cory Johns
The stale project flushing issue that was fixed for repositories in [#7005] is still an issue for other long-running tool imports. Any time an artifact is saved, the `Artifact.__metaclass__.before_save` method updates `c.project.last_updated` which causes `c.project` to become dirty and, when flushed, overwrite any other changes to the project from another source.
For project imports, this can cause the metadata import (or even manual updates to the project metadata) to be overwritten by the tool imports.
---
Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #7103 Stale project flush affects other tool imports
Posted by Cory Johns <ma...@users.sf.net>.
`allura:cj/7103`
---
** [tickets:#7103] Stale project flush affects other tool imports**
**Status:** code-review
**Created:** Mon Jan 27, 2014 05:48 PM UTC by Cory Johns
**Last Updated:** Mon Jan 27, 2014 05:53 PM UTC
**Owner:** Cory Johns
The stale project flushing issue that was fixed for repositories in [#7005] is still an issue for other long-running tool imports. Any time an artifact is saved, the `Artifact.__metaclass__.before_save` method updates `c.project.last_updated` which causes `c.project` to become dirty and, when flushed, overwrite any other changes to the project from another source.
For project imports, this can cause the metadata import (or even manual updates to the project metadata) to be overwritten by the tool imports.
---
Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #7103 Stale project flush affects other tool imports
Posted by Tim Van Steenburgh <va...@users.sf.net>.
- **QA**: Tim Van Steenburgh
---
** [tickets:#7103] Stale project flush affects other tool imports**
**Status:** code-review
**Created:** Mon Jan 27, 2014 05:48 PM UTC by Cory Johns
**Last Updated:** Mon Jan 27, 2014 09:08 PM UTC
**Owner:** Cory Johns
The stale project flushing issue that was fixed for repositories in [#7005] is still an issue for other long-running tool imports. Any time an artifact is saved, the `Artifact.__metaclass__.before_save` method updates `c.project.last_updated` which causes `c.project` to become dirty and, when flushed, overwrite any other changes to the project from another source.
For project imports, this can cause the metadata import (or even manual updates to the project metadata) to be overwritten by the tool imports.
---
Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.