Ticket #320 (closed enhancement: fixed)

Opened 4 years ago

Last modified 4 years ago

Logging improvements

Reported by: Joel Owned by: Joel
Priority: major Milestone: Eraser 6.1/6.2
Component: Core Version:
Keywords: Cc:
Processor Architecture: Blocked By: #300
Blocking: #275 Operating System:

Description (last modified by Joel) (diff)

The logger is currently very involved when doing logging -- we need to instantiate new LogEntry structs, we need to initiate sessions etc. It's also very fickle about the validity of sessions. The Logging should be able to tolerate errors and should be more flexible.

  • The Last Sesssion timestamp is not reset after a session is completed; new messages go to the wrong session.
  • The log should also include the statistics and result of an erase task.
  • Differentiate between "Completed with Errors" vs "Aborted with Errors" etc etc.
    • What qualifies as errors?
    • What do errors imply? Do Errors mean that the target didn't complete? Do fatal errors mean that the entire task didn't complete?

Blocking

IdSummaryMilestone
#320Logging improvementsEraser 6.1/6.2
#275Code ReviewEraser 6.1/6.2
#262Localise the Util.Native and Util librariesEraser 6.1/6.2

Blocked by

IdSummaryMilestone
#320Logging improvementsEraser 6.1/6.2
#300Tasks - Information log entries for start / endEraser 6.1/6.2

Change History

comment:1 Changed 4 years ago by Joel

  • Blocked By 300 removed

comment:2 Changed 4 years ago by Joel

  • Description modified (diff)

comment:3 Changed 4 years ago by Joel

  • Description modified (diff)

comment:4 Changed 4 years ago by Joel

  • Description modified (diff)

comment:5 Changed 4 years ago by Joel

  • Owner set to Joel
  • Status changed from new to accepted

comment:6 Changed 4 years ago by Joel

  • Description modified (diff)

These are fixed in r1777

comment:7 Changed 4 years ago by Joel

  • Blocking 300 added

comment:8 Changed 4 years ago by Joel

  • Blocking 300 removed
  • Blocked By 300 added

comment:9 Changed 4 years ago by Joel

  • Description modified (diff)

These really trigger conditions which can't be recovered simply by returning.

comment:10 Changed 4 years ago by Joel

  • Description modified (diff)

Yeah, these are already handled -- Not Completed vs. Completed with Errors.

comment:11 Changed 4 years ago by Joel

  • Status changed from accepted to closed
  • Resolution set to fixed

The rest of this task is actually a non-issue. I'll close this.

Note: See TracTickets for help on using tickets.