#2874 new defect

early reporting of errors to users on the CLI

Reported by: dawuud Owned by:
Priority: normal Milestone: undecided
Component: unknown Version: 1.12.1
Keywords: Cc:
Launchpad Bug:

Description (last modified by dawuud)

Perhaps: we should replace the tahoe start command something very similar that tails the log looking for a magic string and then exits. If magic completion string is not found then report an error to the user telling them to look at the log file for more info.

We would like to systematically iterate towards an asynchronous startup for tahoe... because we've got an accounting database that needs async startup... and the accounting db is needed for everything else. There are many failure paths that can occur on startup and we'd like to catch all of them as soon as possible and report them to the user instead of what tahoe start does: background the daemon and report nothing to the CLI. Silently fail.

Change History (2)

comment:1 Changed at 2017-04-18T17:22:09Z by dawuud

  • Description modified (diff)

comment:2 Changed at 2017-04-18T17:55:25Z by dawuud

discussed briefly with jean paul and meejah; the implementation of tahoe start will open the log file, seek to the end, and do a read for loop with a 100 millisecond sleep. if timeout is reached before magic string then join all the read chunks and print them to stdout. otherwise exit 0.

Note: See TracTickets for help on using tickets.