KeyError with store._order[pair]

Bug #673666 reported by Matt Haggard on 2010-11-10
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Thomas Herve

Bug Description

The following code results in a KeyError:


Lines 24, 29 and 32 are all critical -- if you take any one of them out, the error does not occur.

I've seen the error on versions 0.17 and 0.18

Related branches

Jamu Kakar (jkakar) on 2010-11-10
Changed in storm:
status: New → Confirmed
importance: Undecided → High
milestone: none → 0.19
Thomas Herve (therve) on 2010-11-13
Changed in storm:
assignee: nobody → Thomas Herve (therve)
Thomas Herve (therve) on 2011-09-26
Changed in storm:
importance: High → Medium
milestone: 0.19 → 0.20
Changed in storm:
milestone: 0.20 → 0.21
Matt Haggard (iffy) wrote :

What can I do to move this forward?

Matt Haggard (iffy) wrote :

This might be related: Or maybe not. The fix proposed by this branch does not fix the issue encountered in the bug #1334020.

Matt Haggard (iffy) wrote :

In the meantime, I'm literally putting this into production:

+ try:
+ store.flush()
+ except KeyError as e:
+ store._order[e.args[0]] = 1
+ store.flush()

Colin Watson (cjwatson) on 2019-09-20
Changed in storm:
milestone: 0.21 → 0.22
Colin Watson (cjwatson) on 2019-11-21
Changed in storm:
milestone: 0.22 → 0.23
Colin Watson (cjwatson) on 2020-03-18
Changed in storm:
milestone: 0.23 → none
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers