mwhittaker / aries Goto Github PK

• Parse operations from the user using some parser combinator library most likely.
• Display the current phase of the algorithm.
• Display the current position in the operations or in the log.
• set status of in-progress transactions to "aborted" at end of analysis phase rather than during analysis_update
• CLR prevLSN is incorrect, needs fixing
• I think buffer pool needs to be updated during UNDO? when undo'ing an update, just write the before data to the buffer pool
• instead of the simulator just mutating a single state object, it would be awesome if states were immutable, so the simulator could return a list of states. Then the UI can just transition between the states
  • the simulate function should just output a list of aries.State objects
• after getting the above to work, there should be some notion of a UI state which contains:

{
    aries_state: aries.State,
    ui_actions: string list
}

the ui_actions is just a list of human-readable actions the DB performs so that we can show the user what actions are causing the changes they see to the state e.g.

['Operation: T1 writes value "foo" to page A',
 'Operation: T2 writes value "foo" to page B',
 'DB CRASHED! Starting recovery...',
 'Analysis: DPT and Txn Table recovered from checkpoint',
  ...]

• styling + ui fixes
  • Show what portion of the log has been forced to disk.
  • Add ui controls for transitioning between different states
  • Add missing log columns (e.g. undoNextLSN).
  • Assign a color to each transaction and color log entries accordingly? I find this useful, but maybe it'll look tacky?
  • Draw arrows connecting a log entry to its prevLSN? Might get too cluttered.

Thanks for the simulator, helped me better understand the protocol.
I don't see any examples of abort operation.
Not sure if this simulator support abort transaction operation.
If it's not yet implemented can I submit a PR?