Qualitative Analysis: Error Message #22
Comments
|
@wannacfuture the deadline is at 2024-01-18T07:07:06.604Z |
# No linked pull requests to close |
|
/start |
! Too many assigned issues, you have reached your max limit |
|
@pavlovcik the deadline is at 2024-02-19T12:50:35.720Z |
# No linked pull requests to close |
|
@whilefoo would be great to figure out centralized error logging from the kernel |
|
Moving the task to the new https://github.com/ubiquibot/conversation-rewards as it is more relevant there. |
I think that the Kernel should indeed pick up errors from the plugins, but not posting them to GitHub messages as this should be done by the plugin itself (not every plugin actually posts comments for example). It could post the error to the Supabase logs instead. Since this is an Action, what could be nice is to have the linked Action Run within the comment's metadata to easily debug and create tickets with the associated run. It seems that there is a ticket in the Kernel that relates to this: ubiquity-os/ubiquity-os-kernel#5 |
|
/start |
![UbiquiBot[dev]](https://avatars.githubusercontent.com/in/257883?s=40&u=1eea9b595c7c8aa1f9dd80751aa25f169024431e&v=4){kind=avatar}
Tips:
|
Tips:
|
+ Evaluating results. Please wait... |
|
| View | Contribution | Count | Reward |
|---|---|---|---|
| Issue | Task | 1 | 37.5 |
| Issue | Comment | 2 | 0 |
Conversation Incentives
| Comment | Formatting | Relevance | Reward |
|---|---|---|---|
Moving the task to the new https://github.com/ubiquibot/conversa… | 0content:
p:
count: 13
score: 1
wordValue: 0
formattingMultiplier: 0
| 0.3 | - |
I think that the Kernel should indeed pick up errors from the pl… | 0content:
p:
count: 92
score: 1
wordValue: 0
formattingMultiplier: 0
| 0.9 | - |
[ 3.27 WXDAI ]
@0x4007
Contributions Overview
| View | Contribution | Count | Reward |
|---|---|---|---|
| Issue | Specification | 1 | 0.51 |
| Issue | Comment | 2 | 2.76 |
Conversation Incentives
| Comment | Formatting | Relevance | Reward |
|---|---|---|---|
https://github.com/ubiquity/ubiquibot/issues/909#issuecomment-18… | 5.1content:
p:
count: 43
score: 1
a:
count: 8
score: 1
wordValue: 0.1
formattingMultiplier: 1
| 0.1 | 0.51 |
https://github.com/ubiquibot/comment-incentives/issues/8#issueco… | 0.2content:
p:
count: 1
score: 1
wordValue: 0.2
formattingMultiplier: 1
| 0.8 | 0.16 |
@whilefoo would be great to figure out centralized error logging… | 2.6content:
p:
count: 13
score: 1
wordValue: 0.2
formattingMultiplier: 1
| 1 | 2.6 |
ubiquity/ubiquibot#909 (comment)
Looks like the qualitative analysis of comments is shaky. On crash, the bot should reply back to the original conversation (here, where it says evaluating results, please wait) with an error message to let us know that it failed.
Source
ubiquity/ubiquibot#909 (comment)
The text was updated successfully, but these errors were encountered: