Bug #297
replace asserts to errors that
0%
Description
this will ensure smooth running in MLCR
Related issues
Updated by Tunnell, Christopher almost 13 years ago
errors within the datastructure that is. you don't want datataking to suddenly stop.
Updated by Tunnell, Christopher almost 13 years ago
- Assignee deleted (
Tunnell, Christopher)
somebody else can take this
Updated by Rogers, Chris over 12 years ago
Is this still relevant? Should use the error handler stuff I did?
Updated by Rogers, Chris over 12 years ago
- Status changed from Open to Rejected
- % Done changed from 0 to 100
Not sure what this even means.
Updated by Tunnell, Christopher over 12 years ago
It means to use your error handler. There is a bunch of code (some I wrote) that uses 'asserts' since we didn't have anything else at the time.
Updated by Rogers, Chris over 12 years ago
- Target version changed from Future MAUS release to MAUS-v0.0.4
Updated by Tunnell, Christopher over 12 years ago
- Status changed from Rejected to Open
- Assignee set to Tunnell, Christopher
- % Done changed from 100 to 0
Maybe this should be a bug, but look here:
and grep for 'assert' within the process function. This was code from early days so the error handler doesn't exist. Maybe it should be a bug? Those shouldn't be there so how do we want to handle it? This was a reminder to myself. I'll find all the cases I'm talking about then flag them then try to fix them?
Updated by Tunnell, Christopher over 12 years ago
- Status changed from Open to Closed
- % Done changed from 0 to 100
let's just reject this at code review level
Updated by Tunnell, Christopher over 12 years ago
- Status changed from Closed to Rejected
- % Done changed from 100 to 0