Open Keyrxng opened 3 months ago
/wallet 0xbB689fDAbBfc0ae9102863E011D3f897b079c80F
+ Successfully registered wallet address
/start
/start
Deadline | Wed, Aug 28, 10:48 AM UTC |
Registered Wallet | 0xAe5D1F192013db889b1e2115A370aB133f359765 |
<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>
/stop
# You have been unassigned from the task
@zugdev can you use the /start
command again and assign this. I'm unsure why it did not assign you the first time
@gentlementlegen it's not trivial to access our worker logs is it? i.e need correct access etc
@Keyrxng Sadly no, you need to live check the logs, we do not retain them. We can consider pushing them to a db but it will be huge. Cloudflare has a log system but it's a paying feature.
I see, we can only assume it was a rate limit of some kind considering my comment went through okay. If it happens again I'll make a point of implementing a core plugin logger with SB posting but this is the first time I've seen it
/start
! Please set your wallet address with the /wallet command first and try again.
/wallet 0x648a958766de4cba2C9884C3c703c40392923163
+ Successfully registered wallet address
/start
/start
Deadline | Wed, Aug 28, 11:29 AM UTC |
Registered Wallet | 0x648a958766de4cba2C9884C3c703c40392923163 |
<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>
@gentlementlegen it's not trivial to access our worker logs is it? i.e need correct access etc
We just have to manually invite their Cloudflare account with read only access I believe.
@0x4007 Yes but we cannot retroactively check the logs, so in this case it would not be helpful.
@zugdev Should have been assigned and this task un-assignable in the first place. There is an issue on that regard here. @Keyrxng that would be truly appreciated that you focus on https://github.com/ubiquibot/command-start-stop/pull/19 so this case doesn't happen again.
@Dhruv245 @zugdev
I don't think either PR has correctly implemented the required changes so it's first one to completion gets the reward. I will assign the PR author to the task before merging.
Where the package is used in the codebase, does anything need updated such as init values etc? If you are confident that you have made the required changes and there are no errors introduced request a review from myself please
And @gentlementlegen I will do it later tonight as I have an apt to get to shortly
/start
Deadline | Wed, Aug 28, 2:40 PM UTC |
Registered Wallet | 0xbB689fDAbBfc0ae9102863E011D3f897b079c80F |
<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>
It's strange that the start command is unreliable. Perhaps we can save logs to our database as we used to for review temporarily.
I just realized that this is the first version of conversation rewards. We should archive this repository as it is deprecated.
This plugin is using my published package and not the official ubiquity package
"@keyrxng/rpc-handler": "^1.0.3"
- remove"@ubiquity-dao/rpc-handler": "^1.3.0"
- replace