#205 saving tickets seems broken
Originally created by: sf-overlords
Created by: wolf
Created date: 2010-04-08 17:59:41.717000
Assigned to:jbeard
-
there's something odd with latest version of master on demo box -- it fails on ticket create
:::python
AttributeError: 'dict' object has no attribute 'artifact_index_id'
looks like a subscribe issue (http://pastebin.com/MjP6DC6G) which might be related to [#119]; anyone else seeing this error?
ticket name: Production Push (R: release_20100408, D: 2010040
Richard Copeland: That was supposed to be fixed
jbeard: it's odd
i tried to create ticket twice
and it failed both times
but i had filled out every field
component, assigned_to, milestone, time estimate, etc
Richard Copeland
what line is trying to read artifact_id?
jbeard
when i created the ticket with none of those filled out
...
and just filled the name, it worked
i'll check line
pyforge.model.notification:184 in subscribed
is being called through the ticket.commit() stack
Richard Copeland
hmm, that should work... just a sec.
jbeard
like i said, simply filling out only the ticket summary and nothing else allowed me to create ticket
but it appears as though these failures left two "partial" tickets in the db
[#203] & [#204]
Richard Copeland
those don't appear to be there at all
but the ticket_num may have incremented
is that consistent with what you're seeing?
jbeard
yes
Wolf Wolf
we should move number assignment to be the very last thing that happens to a ticket
maybe