incubator-allura-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cory Johns" <masterbunn...@users.sf.net>
Subject [allura:tickets] #7103 Stale project flush affects other tool imports
Date Mon, 27 Jan 2014 17:48:59 GMT
- **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.
Mime
  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message