chore: debug

[Keyrxng]

something aint right with config

Resolves #

Quality Assurance:

• https://github.com/Keyrxng/ubiquibot/issues/4#issuecomment-1732367813

[netlify[bot]]

✅ Deploy Preview for ubiquibot-staging ready!

Name	Link
🔨 Latest commit	8a855e9a069edc92c16a2271e56e6db931b1a2cc
🔍 Latest deploy log	https://app.netlify.com/sites/ubiquibot-staging/deploys/650f1cd7bf43750008782b3a
😎 Deploy Preview	https://deploy-preview-815--ubiquibot-staging.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[Keyrxng]

@pavlovcik @0xcodercrane

[Keyrxng]

• https://github.com/ubiquity/ubiquibot/issues/812#issuecomment-1732368338

Just ran /start and got a max active on this repo, so idk what it is I've got wrong here as I've pulled fresh from development to debug /ask.

[Keyrxng]

idk where I'm going wrong.

I do know that:

• I have no repo config or org config

But the bot should be able to run on it's own default config if those other two fail surely?

[0x4007]

But the bot should be able to run on it's own default config if those other two fail surely?

It's supposed to be able to do that yes

[Keyrxng]

• https://github.com/Keyrxng/UbiquityBotTesting/issues/58#issuecomment-1732373425

/help

export const generateHelpMenu = () => {
  let helpMenu = "### Available commands\n```";
  const commands = userCommands();
  commands.map((command) => {

/ask not being displayed in the help table despite looping through all commands despite being in commands:

" ASK = "/ask", // ask GPT a question"

[0x4007]

Your code is probably out of date. Pull upstream

[0x4007]

/help

[ubiquibot[bot]]

Available commands

- /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

[Keyrxng]

I'm up to date otherwise there would be a notification on this pr to update to current commit and my branch is 100% up to date just pulled earlier and double checked right there... wtf

[Keyrxng]

Not sure what to do here.

I can't refork the repo I'd need to delete first and lose my current work.

I'm 100% up to date with the current dev branch.

I have to figure out setting up an organization to get around the default config issue atm to be able to debug the actual bot.

If your help command is showing ask, and your getting rate limited with tokens then it's registering as a command.

I noticed during my trials that if I spammed an /ask on two repos before the first had finalized one or both was likely to fail.

So it may be a good issue to have raised to create a queue for gpt requests (I'd say to the same api key as that's probs the blocker but likely there will only ever be one api in use for folks)

But why it's currently silently failing is beyond me at the minute from what I can see myself.

I was certain that it was returning an error or at least logging one for every path, would you be able to check your logs for me pav? Was anything registered at all when invoking /ask earlier?

[0x4007]

I couldn't find logs related to it that's why I filed the issue but I could add you to the Supabase project if you dm me your Supabase account email