Wayne Boucher wrote:
> It turns out that the problem is an inconsistency that version 1
> allowed (in fact so much so that even checkValid() doesn't catch it).
> So that constraint (serial 1026) had two items that were both pointing
> to the same two resonances, but in the opposite order (version 2 code
> uses sets not lists so that cannot happen now). With Rasmus' help I
> removed the offending bits in the xml file and then the upgrade
> worked, so fortunately that was the only example of this problem.
> I'll send you the link in a subsequent email.
> On Wed, 29 Jul 2009, Gary Thompson wrote:
>> we tried to convert a 1.0 project to a 2.0 project using the online
>> server and got the following error:
>> Job failed: ApiError: Cannot add child - key already in use:
>> [1, 1, 1026]>:frozenset([<ccp.nmr.NmrConstraint.FixedResonance [1,
>> 2]>, <ccp.nmr.NmrConstraint.FixedResonance [1, 4]>])
>> File "/data/ccpn/www/cgi-bin/upgrade/upgrade", line 575, in
>> File "/data/ccpn/www/cgi-bin/upgrade/upgrade", line 549, in
>> p = Converters.doMajorUpgradeToCurrent(oldPath, oldTag, newDir=newDir)
>> line 76, in doMajorUpgradeToCurrent
>> globalMapping=globalMapping, oldTags=oldTags)
>> line 95, in majorUpgradeToCurrent
>> return upgrader.majorUpgrade(doSave=doSave)
>> line 204, in majorUpgrade
>> line 618, in transferData
>> line 1008, in transferData
>> line 4750, in linkChildData
>> + ": %s:%s:%s" % (obj.getQualifiedName(), obj.getParent(), key)
>> however, the response from the server gives no information as to what
>> to do next... It seems that the original project isn't valid ....