Stabilize workflow test env

[Keyrxng]

The workflow tests have been seen to fail because of env setup issues

• nonce too low
• failed to fork using rpc for x, y or z

The current approach uses a yarn command stuffed with anvil cast ... CLI commands to fund which is the cause of the nonce too low issue and anvil.ts uses a single hardcoded RPC endpoint.

Time: 1hr

original context #204 (comment)

[ubiquibot]

+ Evaluating results. Please wait...

[ubiquity-os-main]

[ 6.225 WXDAI ]

@Keyrxng

Contributions Overview

View	Contribution	Count	Reward
Issue	Specification	1	6.225
Review	Comment	1	0

Conversation Incentives

Comment	Formatting	Relevance	Reward
The workflow tests have been seen to fail because of env setup i…	7.5 p: count: 68 score: 1 code: count: 7 score: 1 em: count: 3 score: 0	0.83	6.225
Resolves #229 - added `rpc-handler` to pull a list of good RPCs…	0 p: count: 36 score: 1 code: count: 1 score: 1	0.905	-

[ubiquibot]

[ 18.4 WXDAI ]

@Keyrxng

Contributions Overview

View	Contribution	Count	Reward
Issue	Specification	1	18.4

Conversation Incentives

Comment	Formatting	Relevance	Reward
The workflow tests have been seen to fail because of env setup i...	18.4 h5: count: 1 score: "1" words: 2 li: count: 2 score: "2" words: 13 code: count: 3 score: "3" words: 7	1	18.4

[ubiquibot]

@Keyrxng the deadline is at 2024-05-29T08:27:10.846Z

[ubiquibot]

+ Evaluating results. Please wait...

[ubiquity-os-main]

[ 31 WXDAI ]

@Keyrxng

Contributions Overview

View	Contribution	Count	Reward
Issue	Task	1	25
Issue	Specification	1	6
Review	Comment	1	0

Conversation Incentives

Comment	Formatting	Relevance	Reward
The workflow tests have been seen to fail because of env setup i…	7.5 p: count: 68 score: 1 code: count: 7 score: 1 em: count: 3 score: 0	0.8	6
Resolves #229 - added `rpc-handler` to pull a list of good RPCs…	0 p: count: 36 score: 1 code: count: 1 score: 1	0.95	-

[ubiquibot]

[ 43.4 WXDAI ]

@Keyrxng

Contributions Overview

View	Contribution	Count	Reward
Issue	Specification	1	18.4
Issue	Task	1	25

Conversation Incentives

Comment	Formatting	Relevance	Reward
The workflow tests have been seen to fail because of env setup i...	18.4 h5: count: 1 score: "1" words: 2 li: count: 2 score: "2" words: 13 code: count: 3 score: "3" words: 7	1	18.4

[0x4007]

[ 31 WXDAI ]

@Keyrxng

Contributions Overview

View Contribution Count Reward
Issue Task 1 25
Issue Specification 1 6
Review Comment 1 0

Conversation Incentives

Comment Formatting Relevance Reward

The workflow tests have been seen to fail because of env setup i…

7.5
0.8 6

Resolves #229 - added rpc-handler to pull a list of good RPCs…

0
p:
count: 36
score: 1
code:
count: 1
score: 1
0.95 -

@gentlementlegen the scoring is very far off maybe you can look into making a matching config so that we know that everything is working as expected?

[gentlementlegen]

@0x4007 First issue I see is that the relevance should be 1 for the specification, and somehow the h5 is not listed. Other than that the configuration should have been quite the same. It is based on https://github.com/ubiquity/ubiquibot-config/blob/development/.github/ubiquibot-config.yml correct?

In the old bot I am not sure how to interpret the result being 18.4 with the given details. Also in the new bot, this is not the latest version I think because it doesn't display the applied multiplier for the user member status (collaborator member etc) which is supposed to be there.