[NUMI] ... Querying Numi CLI doesn't work

[alexbet]

Extension

https://www.raycast.com/andresmorelos/numi

Description

When I check the "Use numi-cli" checkbox, quering Numi doesn't work. It says that numi-cli is not installed, when in fact it is. It is installed with Homebrew as suggested on the Numi Github page, and the path to the numi file (a symbolic link) is correct. The symbolic link is at

/opt/homebrew/bin/numi-cli

Here are a couple of screenshots of the setting and the result.

I tried uninstalling/installing the extension, the numi-cli, Numi itself, but nothing changed.

Steps To Reproduce

1. Check the "use numi-cli" option in the extension
2. Try to query Numi

Current Behaviour

It says that numi-cli is not installed, which is not correct. If I query the numi-cli directly in Terminal, it works fine.

Expected Behaviour

It should work with the numi-cli.

[raycastbot]

Thank you for opening this issue!

🔔 @AndresMorelos @pernielsentikaer @viandwi24 you might want to have a look.

💡 Author and Contributors commands

The author and contributors of andresmorelos/numi can trigger bot actions by commenting:

• @raycastbot close this issue Closes the issue.
• @raycastbot rename this issue to "Awesome new title" Renames the issue.
• @raycastbot reopen this issue Reopen the issue.

[pernielsentikaer]

I just tested this and downloaded it from brew too, no errors. What does which numi-cli in the terminal gives you?

[alexbet]

I just tested this and downloaded it from brew too, no errors. What does which numi-cli in the terminal gives you?

That is weird. Here you go:

[alexbet]

BTW, does it matter that Numi itself is installed? Could that somehow impact the numi-cli? I tried uninstalling Numi the application too, but still getting the error.

[pernielsentikaer]

No that should be more than fine, do you know how to debug an extension by forking it? If so I'd like to check it with you 🙂

[alexbet]

Unfortunately not. Are there instructions how to do that somewhere? Also, could it be a permissions problem of some kind maybe?

[pernielsentikaer]

If you know just a little bit of coding, then you can use the Fork action like this

That will guide you a bit, let me know if that files, then you can open the forked extension and add console.logs to the code and run the code with npm run dev

[alexbet]

I did this, but when I execute npm run dev, I get a ray: command not found error.

[alexbet]

OK, I figured it out. I ran the extension from Raycast, and it worked like that. It turns out there was an error in my .bashrc file which was causing the problem. Actually, it wasn't an error, it was the initialization of the Startship prompt. After commenting that out, it started working fine. You might want to look into that.

[AndresMorelos]

@alexbet could you please share a minimal .bashrc to replicate it? I also have Starship prompt but with ZSH, and, it works without issues.

Probably, it's related to starship/starship#5816

[AndresMorelos]

BTW, I see here (#10986 (comment)) that you use ZSH too

Why not use a .zshrc file instead of .bashrc and add

eval "$(starship init zsh)"

[alexbet]

The code use is:

eval "$(starship init bash)"

I have no idea why this would be a problem. Anyway, switched to ZSH instead.

[AndresMorelos]

The code use is:

eval "$(starship init bash)"

I have no idea why this would be a problem. Anyway, switched to ZSH instead.

I'm not sure why this happened, but it also with the VSCode integrated terminal when it tried to source the .bashrc file, probably something related to the starship prompt for the bash environment.

Now that you switched to ZSH, is all working as expected?

Let me know to close this issue.

@alexbet

[AndresMorelos]

@alexbet I'll close this issue, feel free to reopen if the issue persists

@raycastbot close this issue

[kevinm6]

@AndresMorelos @pernielsentikaer I’ve encountered the same issue for some weird things in my .bashrc file.
Since I use zsh daily, could you consider use --norc arg to bash?

[AndresMorelos]

@kevinm6 let me verify this option

[kevinm6]

@kevinm6 let me verify this option

Thanks! You should get it free using /bin/sh, but maybe in some machine/configuration it doesn't load the PATH and in that case can't find the numi-cli binary.