Add retry attempts for peertube up/down logic? #38

Open
opened 2022-07-18 10:42:07 +00:00 by decentral1se · 1 comment
Owner
❯ docker logs beta_lumbung_space_tv.1....
generating tv posts...
didn't get a response from peertube, instance might have been taken down or made private. removing all posts.
deleted ...
deleted ...
deleted ...
deleted ...
deleted ...
...

tv.lumbung.space was up, should we rather add some retry logic here instead of deleting everything? Because then everything is re-downloaded when the logic picks up the instance again. deleting is a waste in this case... is there a better way to detect private-ness? @r @knoflook

``` ❯ docker logs beta_lumbung_space_tv.1.... generating tv posts... didn't get a response from peertube, instance might have been taken down or made private. removing all posts. deleted ... deleted ... deleted ... deleted ... deleted ... ... ``` tv.lumbung.space was up, should we rather add some retry logic here instead of deleting everything? Because then everything is re-downloaded when the logic picks up the instance again. deleting is a waste in this case... is there a better way to detect private-ness? @r @knoflook
Owner

is there a better way to detect private-ness?

i don't think so, private videos just don't appear when you type the link in AFAIK

should we rather add some retry logic here instead of deleting everything?

yes, maybe it could try 30 secs and a minute later?

> is there a better way to detect private-ness? i don't think so, private videos just don't appear when you type the link in AFAIK > should we rather add some retry logic here instead of deleting everything? yes, maybe it could try 30 secs and a minute later?
Sign in to join this conversation.
No Label
No Milestone
No project
No Assignees
2 Participants
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: ruangrupa/konfluks#38
No description provided.