Exponential Backoff Instead of Fail

[0x4007]

I guess my aspiration would be that we can handle situations where we fail to retrieve the data elegantly. What about an exponential back off? The GitHub action has the ability to run for six hours!

Otherwise, if that's a bad idea then yes I agree with whilefoo that it should throw and exit the process.

I'm still definitely leaning towards exponential backoff idea though, which implies that it should never be null, but instead perhaps, undefined.

This can be addressed in another task

Originally posted by @pavlovcik in #3 (comment)

[PhantomCracker]

@0x4007 is this still available?
I was thinking on implementing a backoff solution, but I already see some changes there:
self: GitHubIssue | null = null;

[0x4007]

@gentlementlegen did you implement this in the new plugin? Never let it fail, just exponential back off!

[gentlementlegen]

@0x4007 Partially, but there should be fatal errors that still stop the plugin from running otherwise it would indefinitely fail isn't it?

[0x4007]

This task is strictly about collecting the information that it should have access to from GitHub. Six hour hard timeout anyways.

[ubiquibot]

@gentlementlegen the deadline is at 2024-07-19T02:16:56.547Z

[ubiquibot]

+ Evaluating results. Please wait...

[ubiquibot-dev]

[ 25 WXDAI ]

@gentlementlegen

Contributions Overview

View	Contribution	Count	Reward
Issue	Task	1	25
Issue	Comment	1	0

Conversation Incentives

Comment	Formatting	Relevance	Reward
@0x4007 Partially, but there should be fatal errors that still s…	0 content: p: count: 22 score: 1 wordValue: 0 formattingMultiplier: 0	0.8	-

[ 0.56 WXDAI ]

@PhantomCracker

Contributions Overview

View	Contribution	Count	Reward
Issue	Comment	1	0.56

Conversation Incentives

Comment	Formatting	Relevance	Reward
@0x4007 is this still available? I was thinking on implementing …	0.8 content: p: count: 26 score: 1 code: count: 6 score: 1 wordValue: 0.1 formattingMultiplier: 0.25	0.7	0.56

[ 0 WXDAI ]

@0x4007

Contributions Overview

View	Contribution	Count	Reward

Conversation Incentives

Comment	Formatting	Relevance	Reward

[ubiquibot]

[ 7.6 WXDAI ]

@0x4007

Contributions Overview

View	Contribution	Count	Reward
Issue	Specification	1	0
Issue	Comment	2	7.6

Conversation Incentives

Comment	Formatting	Relevance	Reward
> I guess my aspiration would be that we can handle situation...	-	1	-
@gentlementlegen did you implement this in the new plugin? Never...	3.4	0.81	3.4
This task is strictly about collecting the information that it s...	4.2	0.42	4.2

[ 2.65 WXDAI ]

@PhantomCracker

Contributions Overview

View	Contribution	Count	Reward
Issue	Comment	1	2.65

Conversation Incentives

Comment	Formatting	Relevance	Reward
@0x4007 is this still available? I was thinking on implementing...	2.65 code: count: 1 score: "0.25" words: 4	0.35	2.65

[ 61.9 WXDAI ]

@gentlementlegen

Contributions Overview

View	Contribution	Count	Reward
Issue	Task	1	25
Issue	Comment	1	0
Issue	Comment	1	2.3
Review	Comment	2	17.3
Review	Comment	2	17.3

Conversation Incentives

Comment	Formatting	Relevance	Reward
@0x4007 Partially, but there should be fatal errors that still s...	-	0.49	-
@0x4007 Partially, but there should be fatal errors that still s...	2.3	0.49	2.3
## What's new When retrieving the comments, if there is any fai...	13.2 h2: count: 2 score: "2" words: 5 code: count: 1 score: "1" words: 1	0.5	13.2
@0x4007 We can do that although in this case it cannot be more t...	4.1	0.37	4.1
## What's new When retrieving the comments, if there is any fai...	13.2 h2: count: 2 score: "2" words: 5 code: count: 1 score: "1" words: 1	0.5	13.2
@0x4007 We can do that although in this case it cannot be more t...	4.1	0.37	4.1