Closed 0x4007 closed 11 months ago
/query user (not called @) should still fetch "user"
Skipping /query
because it is disabled on this repo
/query user (not called @) should still fetch "user"
Possibly but this is a separate issue
/start
is the bot sleeping because of my merged pr 💀
/start
/start
Looks like it's broken?
/help
/help
/query @pavlovcik
broke hard
/help
- /start: Assign the origin sender to the issue automatically.
- /stop: Unassign the origin sender from the issue automatically.
- /help: List all available commands.
- /autopay: Toggle automatic payment for the completion of the current issue.
- /query: Comments the users multiplier and address
- /ask: Ask a technical question to the Ubiquity AI.
example usage: "/ask How do I do X?"
- /multiplier: Set the bounty payout multiplier for a specific contributor, and provide the reason for why.
example usage: "/wallet @user 0.5 'Multiplier reason'"
- /allow: Set access control. (Admin Only)
- /wallet: <WALLET_ADDRESS | ENS_NAME>: Register the hunter's wallet address.
ex1: /wallet 0x0000000000000000000000000000000000000000
ex2: /wallet vitalik.eth
https://github.com/ubiquity/ubiquibot/commit/4b4c8f89909424f1c4ca37ebd16b513dae42816b
Invalid config according to the logs
but why commented out? did not tried to set to false
instead?
/help
- /start: Assign the origin sender to the issue automatically.
- /stop: Unassign the origin sender from the issue automatically.
- /help: List all available commands.
- /autopay: Toggle automatic payment for the completion of the current issue.
- /query: Comments the users multiplier and address
- /ask: Ask a technical question to the Ubiquity AI.
example usage: "/ask How do I do X?"
- /multiplier: Set the bounty payout multiplier for a specific contributor, and provide the reason for why.
example usage: "/wallet @user 0.5 'Multiplier reason'"
- /allow: Set access control. (Admin Only)
- /wallet: <WALLET_ADDRESS | ENS_NAME>: Register the hunter's wallet address.
ex1: /wallet 0x0000000000000000000000000000000000000000
ex2: /wallet vitalik.eth
/start
Deadline | Sat, 23 Sep 2023 03:15:48 UTC |
Registered Wallet | 0x0BEd00438D57d07E3667b85Fa8EB86Af147C7025 |
/wallet 0x0000...0000
if you want to update your registered payment wallet address @user.Mannn
Mannn
shall I unassign myself if you want to work on it?
Nah you can have this issue
/query @pavlovcik
Error retrieving access for @pavlovcik
/query @Sadaf-A
Error retrieving access for @Sadaf-A
/allow-time @Sadaf-A true
Invalid syntax for allow usage: '/allow set-(access type) @user true|false' ex-1 /allow set-multiplier @user false
/allow set-time @Sadaf-A true
Updated access for @Sadaf-A successfully! Access: time for "ubiquity/ubiquibot"
/query @Sadaf-A
@Sadaf-A's wallet address is 0x0BEd00438D57d07E3667b85Fa8EB86Af147C7025, multiplier is 1 and access levels are
access type | access level |
---|---|
multiplier | false |
priority | false |
time | true |
price | false |
There is a bug @Sadaf-A but now you're good to query yourself.
/query @Sadaf-A
@Sadaf-A's wallet address is 0x0BEd00438D57d07E3667b85Fa8EB86Af147C7025, multiplier is 1 and access levels are
access type | access level |
---|---|
multiplier | false |
priority | false |
time | true |
price | false |
@pavlovcik can you elaborate a little more on what this issue is supposed to fix?
Any instance you see the string literal "@user"
should never actually write "@user" in any bot comments.
Deadline Sat, 23 Sep 2023 03:15:48 UTC Registered Wallet 0x0BEd00438D57d07E3667b85Fa8EB86Af147C7025 Tips:
- Use
/wallet 0x0000...0000
if you want to update your registered payment wallet address @user.- Be sure to open a draft pull request as soon as possible to communicate updates on your progress.
- Be sure to provide timely updates to us when requested, or you will be automatically unassigned from the bounty.
@pavlovcik I see like here the bot writes '@user' but what should it write instead? the actual user's tag?
Yes
0x0BEd00438...f147C7025
no conversation rewards expected? @pavlovcik
Did you guys up the price mul
/query @Sadaf-A
@Sadaf-A's wallet address is 0x0BEd00438D57d07E3667b85Fa8EB86Af147C7025, multiplier is 1 and access levels are
access type | access level |
---|---|
multiplier | false |
priority | false |
time | true |
price | false |
@pavlovcik the issue price is 25USD why did I receive 37.5? and even more confusing when I opened it. It was for 18.75 okay I get it. The bot deducted it because of the parse-permit-url
PR
no conversation rewards expected? @pavlovcik
The bot is pretty broken. Fortunately due to the permit issuance design, in the future when it's stable we should be able to force regen on these old issues to generate the rewards.
@pavlovcik the issue price is 25USD why did I receive 37.5? and even more confusing when I opened it. It was for 18.75 okay I get it. The bot deducted it because of the
parse-permit-url
PR
I filed a new issue to fix this. You should be able to see the back reference on this conversation from a few hours ago.
@user is supposed to be referencing a specific user usually who invoked the bot. I've seen this in a few places already and it must be fixed. Especially see it all the time on the
/start
tableOriginally posted by @ubiquibot in https://github.com/ubiquity/ubiquity-dollar/issues/774#issuecomment-1730056879