0.9.0b7 niggles
Two things since I have had 0.9.0b7 running for 24 hours:
- Lots of non-CT display names needed resetting, mostly but not all non-RDSR sources. But I didn't check what it was like before the upgrade, and I don't know how much of it is due to having been on b6...
- Lots of 'None' tasks in 'older tasks' with status FAILURE. Don't know what they are from. Just me?
Comments (10)
-
-
I've checked my server logs, and there are no errors reported since I upgraded from b6 to b7 (celery, flower, qr).
-
reporter I'm going to need to do some more testing of the upgrade process
-
reporter Setting the new fields to None rather than False or "" succeeds in preventing new UniqueEquipmentName rows being created. Refs
#731→ <<cset 950aa77fd98c>>
-
reporter Applying None display name fix to ct_philips and dx. Refs
#731→ <<cset 35da0ee223b3>>
-
reporter I think I have the resetting of display names licked. I've just restarted Flower without the local host restriction so I can see if the failed tasks have any more information I can extract. I'll update when/if I get any to look at.
Has anyone else checked to see if there are failures in the tasks list? They aren't dated, so I assume they'll go straight to 'older tasks'.
-
I haven't seen any failures in the tasks list so far.
-
reporter Same with me since I restarted Flower earlier.
I'll check my system tonight if I get a chance and do a final beta to install on my other production system that is still on vanilla 0.8.1 tomorrow (again if I get a chance!)
-
reporter Adding ref
#731to changes→ <<cset 987e11bbce7a>>
-
reporter - changed status to resolved
Merged in issue731displaynameupgradeniggles (pull request #284)
Fixes
#731Approved-by: David Platten
→ <<cset 9202125e3c82>>
- Log in to comment
The display name for every mammo and radiographic system that has sent data since moving from b6 to b7 needs to be reset for me.
I don't have anything in 'older tasks' right now, although it looks like flower was restarted this morning. I'll update on this later on today.