allura-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cory Johns" <>
Subject [allura:tickets] #7005 allura.tasks.repo_tasks.clone clobbers Project record
Date Fri, 10 Jan 2014 16:01:57 GMT
Rebased and force-pushed to:


** [tickets:#7005] allura.tasks.repo_tasks.clone clobbers Project record**

**Status:** code-review
**Created:** Wed Dec 18, 2013 04:30 PM UTC by Dave Brondsema
**Last Updated:** Thu Jan 09, 2014 09:48 PM UTC
**Owner:** Cory Johns

It appears that the allura.tasks.repo_tasks.clone task flushes the Project record at the end,
and since that task can take a very long time, any updates (e.g. to project description) get
lost when it saves the old project document back to mongo.

I haven't duplicated this in development, but here's what happened on sourceforge:

* Google Code import was used; `import_project_info` task ran at 2013/12/17 04:54:38
* Repo clone started at 2013/12/17 04:54:39
* short description was manually set, at 2013-12-17 06:07:16 (per Audit Log)
* Repo clone finished at 2013/12/17 07:32:09 and currently the short description is empty.

I didn't find any other tasks with the specific project_id that completed after 06:07:16,
so I believe it's the repo clone task at fault.


Sent from because is subscribed to

To unsubscribe from further messages, a project admin can change settings at
 Or, if this is a mailing list, you can unsubscribe from the mailing list.
  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message