King_DuckZ/orotool

Add some retry capabilities on server error #2

New issue

Closed

opened 2020-09-12 12:12:03 +00:00 by King_DuckZ · 1 comment

King_DuckZ commented

2020-09-12 12:12:03 +00:00

Owner

The daemon should not quit immediately if the communication with the server fails. There should be some new settings in the ini file that allow to set how many retries should be attempted before giving up, or possibly to keep trying forever. Another setting sholud be added to specify an amount of time to wait between retries.

In code, this means the API nap backend should throw an exception that timers can easily recognise and react to, unless a better way is found.

The daemon should not quit immediately if the communication with the server fails. There should be some new settings in the ini file that allow to set how many retries should be attempted before giving up, or possibly to keep trying forever. Another setting sholud be added to specify an amount of time to wait between retries. In code, this means the API nap backend should throw an exception that timers can easily recognise and react to, unless a better way is found.

King_DuckZ added the

label 2020-09-12 12:14:18 +00:00

King_DuckZ added this to the v0.2.1 milestone 2020-09-12 12:19:24 +00:00

King_DuckZ self-assigned this 2020-09-12 12:19:28 +00:00

King_DuckZ referenced this issue from a commit

2020-09-14 22:47:24 +00:00

Add retry capability on connection errors This fixes bug #2

King_DuckZ commented

2020-09-14 22:48:44 +00:00

Author

Owner

Implemented at commit 36b0c6f6f0

Implemented at commit 36b0c6f6f0284a247f17a74875c4cf582911b684

King_DuckZ closed this issue

2020-09-14 22:48:44 +00:00

Sign in to join this conversation.

No labels

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: King_DuckZ/orotool#2

No description provided.