Adjust ytsync queues #19

New issue

Closed

opened 2018-07-09 15:38:41 +02:00 by nikooo777 · 0 comments

nikooo777 commented

2018-07-09 15:38:41 +02:00

(Migrated from github.com)

A channel might be in one of the following states:

pending (awaiting approval by the owner)
queued (approved, awaiting synchronization)
syncing (being synchronized by the tool)
synced (finished synchronizing)
failed (failure in synchronizing)

The ytsync tool is capable of fetching from all those queues depending on the startup instructions.

When syncing without specific flags the behavior should be the following:

process the syncing queue (if anything was left half-way previously it will be finished first)
sync the queued queue
repeat endlessly or until the maximum number of cycles (specified) is reached

When syncing with the update flag:

process the syncing queue (if anything was left half-way previously it will be finished first)
sync the synced queue (all previously synced channels will be updated)
repeat endlessly or until the maximum number of cycles (specified) is reached

when syncing with a status specified:

sync that specified queue only

Something in the logic isn't quite right and the wrong queues are pulled.

A channel might be in one of the following states: - pending (awaiting approval by the owner) - queued (approved, awaiting synchronization) - syncing (being synchronized by the tool) - synced (finished synchronizing) - failed (failure in synchronizing) The ytsync tool is capable of fetching from all those queues depending on the startup instructions. When syncing without specific flags the behavior should be the following: 1) process the syncing queue (if anything was left half-way previously it will be finished first) 2) sync the queued queue 3) repeat endlessly or until the maximum number of cycles (specified) is reached When syncing with the update flag: 1) process the syncing queue (if anything was left half-way previously it will be finished first) 2) sync the synced queue (all previously synced channels will be updated) 3) repeat endlessly or until the maximum number of cycles (specified) is reached when syncing with a status specified: 1) sync that specified queue only Something in the logic isn't quite right and the wrong queues are pulled.

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.go#19

No description provided.