Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extension doesn't pick up rad binary if the its parent directory is created after the extension is loaded #172

Open
QZera opened this issue Jan 26, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@QZera
Copy link
Collaborator

QZera commented Jan 26, 2025

Describe the bug

The Extension doesn't pick up rad binary if the its parent directory is created after the extension has been loaded. This could be an issue if the extension is installed before Radicle itself.

To Reproduce

  1. Open the Radicle channel in the Output Panel
  2. Set the Radicle › Advanced: Path To Rad Binary setting to a non-existent path (e.g. ~/.radicle.temp/bin/rad)
  3. Create the specified directory and copy the rad binary to it

Expected behaviour

A message in the Output Panel indicating that the extension is using the binary from the specified path (e.g. Using Radicle CLI v1.x.x from "~/.radicle.temp/bin/rad")

Actual behaviour

No such message appears

Platform

  • OS: macOS Sequoia 15.2
  • VSCode Version: 1.96.4
  • Extension Version: 0.6.0

Additional context

Reloading VSCode does cause the extension to pick up the new rad binary path correctly

@QZera QZera added the bug Something isn't working label Jan 26, 2025
@maninak maninak moved this to 📋 Up Next in Radicle VS Code Extension Jan 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: 📋 Up Next
Development

No branches or pull requests

1 participant