TraCI crashes when SUMO responds with an error (trac #1043)

[behrisch]

SUMO errors should be handled cleanly and not result in a stacktrace pointing at the bowels of traci.Storage. Throwing a custom exception somewhere along the call stack would be preferable.

Migrated from http://sumo.dlr.de/ticket/1043

{
    "status": "closed", 
    "changetime": "2013-11-22T11:26:07Z", 
    "description": "SUMO errors should be handled cleanly and not result in a stacktrace pointing at the bowels of traci.Storage. Throwing a custom exception somewhere along the call stack would be preferable.", 
    "reporter": "namdre", 
    "cc": "", 
    "resolution": "fixed", 
    "_ts": "1385119567761860", 
    "component": "TraCI", 
    "summary": "TraCI crashes when SUMO responds with an error", 
    "priority": "major", 
    "keywords": "", 
    "time": "2013-10-02T14:43:39Z", 
    "milestone": "0.19.0", 
    "owner": "behrisch", 
    "type": "defect"
}

[behrisch]

@namdre changed description from "SUMO errors should be handled cleanly and not result in a stacktrace pointing at the bowels of traci.Storage." to "SUMO errors should be handled cleanly and not result in a stacktrace pointing at the bowels of traci.Storage. Throwing a custom exception somewhere along the call stack would be preferable."

[behrisch]

@namdre commented:

see M:\Daten\Sumo\Bugreports\1010_python_traci_crash

[behrisch]

• @behrisch commented:

the new link is O:\Daten\Sumo\Bugreports\1043_python_traci_crash

• @behrisch changed status from "new" to "accepted"

[behrisch]

• @behrisch commented:

37d0060 (aka r15197)

• @behrisch changed resolution from "" to "fixed"
• @behrisch changed status from "accepted" to "closed"