expand code blocks in preview

[zugdev]

Code blocks in issue previews are currently barely readable, take the image from this preview as an example:

On GitHub it looks like this:

Which is much more readable.

[0x4007]

It's tricky to do correctly with css but yeah would be nice

[ubiquity-os]

! Please set your wallet address with the /wallet command first and try again.

[dawidsawa]

/wallet 0x2C0494B5C7199ae844c0dF08ba6828075FC462Fc

[ubiquity-os]

+ Successfully registered wallet address

[ubiquity-os]

Deadline	Tue, Nov 5, 4:16 PM UTC
Beneficiary	0x2C0494B5C7199ae844c0dF08ba6828075FC462Fc

Tip

• Use /wallet 0x0000...0000 if you want to update your registered payment wallet address.
• Be sure to open a draft pull request as soon as possible to communicate updates on your progress.
• Be sure to provide timely updates to us when requested, or you will be automatically unassigned from the task.

[zugdev]

@gentlementlegen apparently permit generation did not run.

[zugdev]

This is how it looks now:

We could possibly look into a coloring lib in the future.

[gentlementlegen]

@zugdev got a lot of fetch request that went loose:

I will try to regenerate.

[ubiquity-os]

 [ 6 UUSD ] 

@dawidsawa

Contributions Overview

View	Contribution	Count	Reward
Issue	Task	1	6
Review	Comment	5	0

Conversation Incentives

Comment	Formatting	Relevance	Reward
Resolves #155	0 content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 2 wordValue: 0 result: 0	0.7	0
Before![before](https://github.com/user-attachments/assets/756…	10.36 content: content: p: score: 0 elementCount: 4 img: score: 5 elementCount: 2 result: 10 regex: wordCount: 2 wordValue: 0.2 result: 0.36	0.8	0
Given the background is already very dark adding even an absolut…	13.19 content: content: p: score: 0 elementCount: 2 a: score: 5 elementCount: 1 img: score: 5 elementCount: 1 result: 10 regex: wordCount: 26 wordValue: 0.2 result: 3.19	0.9	0
How about now:![dark](https://github.com/user-attachments/asse…	10.51 content: content: p: score: 0 elementCount: 3 img: score: 5 elementCount: 2 result: 10 regex: wordCount: 3 wordValue: 0.2 result: 0.51	0.6	0
EDIT: my bad, that did not fix it.https://a642e753.devpool-dir…	7.22 content: content: p: score: 0 elementCount: 3 img: score: 5 elementCount: 1 result: 5 regex: wordCount: 17 wordValue: 0.2 result: 2.22	0.2	0

 [ 0.616 UUSD ] 

@0x4007

Contributions Overview

View	Contribution	Count	Reward
Issue	Comment	1	0.616

Conversation Incentives

Comment	Formatting	Relevance	Reward
It's tricky to do correctly with css but yeah would be nice	0.88 content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 13 wordValue: 0.1 result: 0.88	0.7	0.616

 [ 69.0875 UUSD ] 

@zugdev

Contributions Overview

View	Contribution	Count	Reward
Issue	Specification	1	50.25
Issue	Comment	2	6.215
Review	Comment	4	12.6225

Conversation Incentives

Comment	Formatting	Relevance	Reward
Code blocks in issue previews are currently barely readable, tak…	16.75 content: content: p: score: 0 elementCount: 5 a: score: 5 elementCount: 1 img: score: 5 elementCount: 2 result: 15 regex: wordCount: 29 wordValue: 0.1 result: 1.75	1	50.25
@gentlementlegen apparently permit generation did not run.	1.05 content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 7 wordValue: 0.2 result: 1.05	0.1	0.105
This is how it looks now:![image](https://github.com/user-atta…	7.22 content: content: p: score: 0 elementCount: 3 img: score: 5 elementCount: 1 result: 5 regex: wordCount: 17 wordValue: 0.2 result: 2.22	0.5	6.11
Please add `overflow-x: scroll` in code block, to handle…	11.44 content: content: p: score: 0 elementCount: 3 a: score: 5 elementCount: 1 img: score: 5 elementCount: 1 result: 10 regex: wordCount: 23 wordValue: 0.1 result: 1.44	0.9	2.824
Please consider the inverted style too because when browser is i…	21.61 content: content: p: score: 0 elementCount: 5 img: score: 5 elementCount: 3 ol: score: 1 elementCount: 2 li: score: 0.5 elementCount: 2 result: 18 regex: wordCount: 68 wordValue: 0.1 result: 3.61	1	5.4
That's better, one last thing check [this issue](https://de78886…	17.69 content: content: p: score: 0 elementCount: 5 a: score: 5 elementCount: 1 img: score: 5 elementCount: 2 result: 15 regex: wordCount: 48 wordValue: 0.1 result: 2.69	0.8	4.2855
Looks good! Not sure about hard-coded colors tho, @0x4007 RFC	0.77 content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 11 wordValue: 0.1 result: 0.77	0.6	0.113

 [ 0.57 UUSD ] 

@gentlementlegen

Contributions Overview

View	Contribution	Count	Reward
Issue	Comment	1	0.57

Conversation Incentives

Comment	Formatting	Relevance	Reward
@zugdev got a lot of fetch request that went loose:<img wid…	1.9 content: content: p: score: 0 elementCount: 3 result: 0 regex: wordCount: 32 wordValue: 0.1 result: 1.9	0.3	0.57

[gentlementlegen]

It seems we get a lot of errors during runs

I am not sure if that's because we start to have too many plugins to call. @0x4007 rfc

[zugdev]

My reward seems incorrect. @0x4007 if necessary revoke it.

[gentlementlegen]

@zugdev as long as you don't claim it we can regenerate it. Seems that there is a high boost on the specification.

So technically your reward is correct, but I remember somewhere we talked about capping it so it doesn't go higher than the reward of the issue itself or something like that (there currently is a x3 boost on the specs so you got 16.75 * 3 = 50.25).

[zugdev]

It seems we get a lot of errors during runs

I am not sure if that's because we start to have too many plugins to call.

I am not an expert in workers but, from my experience with distributed systems, it seems super weird that there isn't a way to wait for resources or schedule a never reverting call. There must be a way to make it deterministic.

[zugdev]

So technically your reward is correct,

I understand that, initially I thought it was that recent misconfiguration, but that was related to PR author getting review comments credited. I won't claim for now, I will let him decide what should be done in this case.

[gentlementlegen]

It seems we get a lot of errors during runs

I am not sure if that's because we start to have too many plugins to call.

I am not an expert in workers but, from my experience with distributed systems, it seems super weird that there isn't a way to wait for resources or schedule a never reverting call. There must be a way to make it deterministic.

We also have to check the code itself the error might be totally different but logs are not very verbose within Cloud flare. Let's see if it also occurs on the development bot version because it could also mean some problem in the main branch only.

[zugdev]

We also have to check the code itself the error might be totally different but logs are not very verbose within Cloud flare. Let's see if it also occurs on the development bot version because it could also mean some problem in the main branch only.

I will look into it today.