Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adjust ytsync queues #19

Closed
nikooo777 opened this issue Jul 9, 2018 · 0 comments
Closed

Adjust ytsync queues #19

nikooo777 opened this issue Jul 9, 2018 · 0 comments
Assignees

Comments

@nikooo777
Copy link
Collaborator

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.

@nikooo777 nikooo777 added this to the July 11th (APIs) milestone Jul 9, 2018
@nikooo777 nikooo777 self-assigned this Jul 9, 2018
nikooo777 added a commit that referenced this issue Jul 17, 2018
merge sync and selfsync
export sync manager out of cmd package
clean up ytsync.go
address #19 and #20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants