-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Formatting issue #76
Comments
Why not study the old code closer to see why we don't have these problems? |
The old code was totally broken when it came to formatting as well and would cut the results instead. This is an issue regarding the metadata part I think. |
@gentlementlegen the deadline is at 2024-08-13T07:38:43.182Z |
@0x4007 It seems that the problem was solved after my changes in #78, see results here by |
You should retroactively link your pull to this issue. Then we have a formal record for audits, and you receive your credit. However as you know, we generally require targeted pulls (only the relevant changes per one issue) but we can make an exception here. |
+ Evaluating results. Please wait... |
! Failed to run comment evaluation. Error: execution reverted (no data present; likely require(false) occurred (action="call", data="0x", reason="require(false)", transaction={ "data": "0x95d89b41", "to": "0xe91D153E0b41518A2Ce8Dd3D7944Fa863463a97d" }, invocation=null, revert=null, code=CALL_EXCEPTION, version=6.13.1) |
@gentlementlegen the deadline is at 2024-08-20T11:14:56.843Z |
+ Evaluating results. Please wait... |
|
View | Contribution | Count | Reward |
---|---|---|---|
Issue | Task | 1 | 50 |
Issue | Specification | 1 | 6 |
Issue | Comment | 3 | 17.16 |
Conversation Incentives
Comment | Formatting | Relevance | Reward |
---|---|---|---|
There seem to be some formatting issue in the pull-request: htt… | 6content: p: count: 20 score: 1 wordValue: 0.1 formattingMultiplier: 3 | 1 | 6 |
The old code was totally broken when it came to formatting as we… | 5.8content: p: count: 29 score: 1 wordValue: 0.2 formattingMultiplier: 1 | 0.7 | 4.06 |
@0x4007 It seems that the problem was solved after my changes in… | 5.8content: p: count: 28 score: 1 code: count: 1 score: 1 wordValue: 0.2 formattingMultiplier: 1 | 0.8 | 4.64 |
@0x4007 Yes I agree, I guess everything went in in one block bec… | 9.4content: p: count: 47 score: 1 wordValue: 0.2 formattingMultiplier: 1 | 0.9 | 8.46 |
[ 3.15 WXDAI ]
@0x4007
Contributions Overview
View | Contribution | Count | Reward |
---|---|---|---|
Issue | Comment | 2 | 3.15 |
Conversation Incentives
Comment | Formatting | Relevance | Reward |
---|---|---|---|
Why not study the old code closer to see why we don't have these… | 1.5content: p: count: 15 score: 1 wordValue: 0.1 formattingMultiplier: 1 | 0.3 | 0.45 |
You should retroactively link your pull to this issue. Then we h… | 4.5content: p: count: 45 score: 1 wordValue: 0.1 formattingMultiplier: 1 | 0.6 | 2.7 |
|
View | Contribution | Count | Reward |
---|---|---|---|
Issue | Comment | 2 | 6.1 |
Conversation Incentives
Comment | Formatting | Relevance | Reward |
---|---|---|---|
Why not study the old code closer to see why we don't have these... | 1.6 | 0.45 | 1.6 |
You should retroactively link your pull to this issue. Then we h... | 4.5 | 0.635 | 4.5 |
[ 82.8 WXDAI ]
@gentlementlegen
Contributions Overview
View | Contribution | Count | Reward |
---|---|---|---|
Issue | Specification | 1 | 6.2 |
Issue | Task | 1 | 50 |
Issue | Comment | 3 | 26.6 |
Issue | Comment | 3 | 0 |
Conversation Incentives
Comment | Formatting | Relevance | Reward |
---|---|---|---|
There seem to be some formatting issue in the pull-request: htt... | 6.2 | 1 | 6.2 |
The old code was totally broken when it came to formatting as we... | 5.8 | 0.67 | 5.8 |
@0x4007 It seems that the problem was solved after my changes in... | 10code: count: 1 score: "1" words: 1 | 0.76 | 10 |
@0x4007 Yes I agree, I guess everything went in in one block bec... | 10.8 | 0.85 | 10.8 |
The old code was totally broken when it came to formatting as we... | - | 0.67 | - |
@0x4007 It seems that the problem was solved after my changes in... | -code: count: 1 score: "0" words: 1 | 0.76 | - |
@0x4007 Yes I agree, I guess everything went in in one block bec... | - | 0.85 | - |
@0x4007 Seems that updating the packages fixed the issue, at least for now. |
@gentlementlegen Please link the correct pull |
There seem to be some formatting issue in the pull-request:
ubiquity-os-marketplace/command-start-stop#4 (comment)
The comment should not be displayed in this case.
The text was updated successfully, but these errors were encountered: