Open 0x4007 opened 6 months ago
@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.
@whilefoo would be great to figure out centralized error logging from the kernel
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: https://github.com/ubiquity/ubiquibot-kernel/issues/5
/start
Warning! | This task was created over 181 days ago. Please confirm that this issue specification is accurate before starting. |
Deadline | Tue, Jul 16, 6:32 AM UTC |
Registered Wallet | 0x0fC1b909ba9265A846b82CF4CE352fc3e7EeB2ED |
<ul>
<li>Use <code>/wallet 0x0000...0000</code> if you want to update your registered payment wallet address.</li>
<li>Be sure to open a draft pull request as soon as possible to communicate updates on your progress.</li>
<li>Be sure to provide timely updates to us when requested, or you will be automatically unassigned from the task.</li>
<ul>
Warning! | This task was created over 181 days ago. Please confirm that this issue specification is accurate before starting. |
Deadline | Tue, Jul 16, 6:32 AM UTC |
Registered Wallet | 0x0fC1b909ba9265A846b82CF4CE352fc3e7EeB2ED |
/wallet 0x0000...0000
if you want to update your registered payment wallet address.
https://github.com/ubiquity/ubiquibot/issues/909#issuecomment-1894620433
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
https://github.com/ubiquity/ubiquibot/issues/909#issuecomment-1894626568