Support new daemon startup process #1728

Closed
opened 2018-07-03 16:58:22 +02:00 by tzarebczan · 2 comments
tzarebczan commented 2018-07-03 16:58:22 +02:00 (Migrated from github.com)

The Issue

When https://github.com/lbryio/lbry/pull/1164 is merged, the status calls returned to the app will be different. From changelog:
STARTUP_STAGES from status API and CLI call, it instead returns a dictionary of components along with their running status(this is a potentially breaking change if STARTUP_STAGES is relied upon)

This might be a good opportunity to make the startup messages more user friendly.

Suggested Solutions

Tell us your suggested solutions if you have any.

System Configuration

  • LBRY Daemon version:
  • LBRY App version:
  • LBRY Installation ID:
  • Operating system:

Anything Else

Screenshots

<!-- Thanks for reporting an issue to LBRY and helping us improve! To make it possible for us to help you, please fill out below information carefully. Before reporting any issues, please make sure that you're using the latest version. - App releases: https://github.com/lbryio/lbry-app/releases - Standalone daemon: https://github.com/lbryio/lbry/releases We are also available on live chat at https://chat.lbry.io --> ## The Issue When https://github.com/lbryio/lbry/pull/1164 is merged, the status calls returned to the app will be different. From [changelog](https://github.com/lbryio/lbry/blob/26098879e77149fc8401b0e9f04436964f83013c/CHANGELOG.md#removed): `STARTUP_STAGES from status API and CLI call, it instead returns a dictionary of components along with their running status(this is a potentially breaking change if STARTUP_STAGES is relied upon) ` This might be a good opportunity to make the startup messages more user friendly. ### Suggested Solutions Tell us your suggested solutions if you have any. ## System Configuration <!-- For the app, this info is in the About section at the bottom of the Help page. You can include a screenshot instead of typing it out --> <!-- For the daemon, run: curl 'http://localhost:5279' --data '{"method":"version"}' and include the full output --> - LBRY Daemon version: - LBRY App version: - LBRY Installation ID: - Operating system: ## Anything Else <!-- Include anything else that does not fit into the above sections --> ## Screenshots <!-- If a screenshot would help explain the bug, please include one or two here -->
neb-b commented 2018-07-09 17:54:26 +02:00 (Migrated from github.com)

@tzarebczan Is this different from #1686 ?

@tzarebczan Is this different from #1686 ?
neb-b commented 2018-07-09 17:55:25 +02:00 (Migrated from github.com)

Oh. Just saw you referenced a PR, which has been reverted.

Oh. Just saw you referenced a PR, which has been reverted.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbry-desktop#1728
No description provided.