Skip to content

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

@QZera

Description

@QZera

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    Status

    📋 Up Next

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions