Skip to content
This repository was archived by the owner on May 3, 2019. It is now read-only.

Milestones

List view

  • Blockchain Reorganization Handling

    If Papi detects that a reorganization has occurred, it will utilize an internal function to undo (roll back) transactions up to the point of the chain branching, and then process new transactions on the valid chain. This will require the following: - Reorganization Detection and Alert - Database rollback to most recent valid checkpoint - Process new transactions

    Overdue by 7 year(s)
    •
    Due by July 29, 2018
    •0/2 issues closed
    0% complete2 open0 closed

  • Authentication Preliminary Design

    Implement an optional authentication scheme ( dependent on server use-case ).

    Overdue by 7 year(s)
    •
    Due by August 26, 2018
    0% complete0 open0 closed

  • Comprehensive API Documentation Review

    Review the documentation. This means removing unnecessary jargon and refactoring the language used to be less verbose and more concise. Ensure that the examples given are in fact valid.

    Overdue by 7 year(s)
    •
    Due by August 26, 2018
    0% complete0 open0 closed

  • Comprehensive API Documentation

    The API documentation has direct implications on adoption and maintainability. It will be oriented towards the use by software engineers but should be explicit in terms of defining the services in which the application can provide. Ensure that the following are concisely defined in the documentation: - Authentication - Requests - Error Messages - Terms of Use

    Overdue by 7 year(s)
    •
    Due by August 19, 2018
    0% complete0 open0 closed

  • Logging and Custom API Error Handling Review

    Test and review that the application logging sufficiently covers all required events. Ensure that the flow of log event information is properly configured.

    Overdue by 7 year(s)
    •
    Due by August 5, 2018
    0% complete0 open0 closed

  • Logging and Custom API Error Handling

    - Display console output for ordinary usage of a command line script or program - Report events that occur during normal operation (e.g. for status monitoring or fault investigation) - Issue a warning regarding a particular run-time event - Report an error regarding a particular run-time event - Report suppression of an error without raising an exception (e.g. error handler in a long-running server process)

    Overdue by 7 year(s)
    •
    Due by July 29, 2018
    •0/1 issues closed
    0% complete1 open0 closed

  • Asyncronus Tasks and Coroutines Review

    Review implementation and refactor the design as needed.

    Overdue by 7 year(s)
    •
    Due by July 29, 2018
    0% complete0 open0 closed

  • Asyncronus Tasks and Coroutines Preliminary Design

    Implement an asynchronous approach when loading decks, cards, and computing deck states. This means writing and replacing existing functions with the proper co-routines necessary to improve initialization speed and run-time operations.

    Overdue by 7 year(s)
    •
    Due by July 15, 2018
    •0/2 issues closed
    0% complete2 open0 closed