Closed 0x4007 closed 11 months ago
/start
Deadline | Sat, 23 Sep 2023 14:02:50 UTC |
Registered Wallet | 0x9e4EF4353C928cD3eb473E8f12aeCF58C2089999 |
/wallet 0x0000...0000
if you want to update your registered payment wallet address @user./stop
You have been unassigned from the bounty @wannacfuture
@seprintour maybe you can take this one
/start
Too many assigned issues, you have reached your max of 2
@seprintour The time limit for this bounty is on Sun, 24 Sep 2023 10:15:04 UTC
@pavlovcik Am i dumping errors like the logger to supabase implementation?
Wouldn't that be too much data on the group?, or we just send only the logger.error
messages
I have no idea. But I am inclined to make available the full info if it is for debugging purposes. Ideally a truncated version in the group chat with a. Link to full information
I have no idea. But I am inclined to make available the full info if it is for debugging purposes. Ideally a truncated version in the group chat with a. Link to full information
I think the full error is usually on supabase but it's not public, maybe I'd just dump errors and warns on to the group chat
Would be more useful that way, including a link to the issue the error occurred
0x36233380...2176f39E5