Re-enabling a plugin that has been previously installed should not re-install alll of its dependencies

Open
#6,994 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp
Domain
reverse-engineering

Research direction

The payload names no files or tests. Start by reproducing the Sidekick plugin disable-and-re-enable flow and trace the plugin dependency installation entry point; verify whether already-installed dependencies are requested again. Done means re-enabling the plugin leaves existing dependencies in place while still installing any missing ones.

Written by the indexing model from the issue text.

Description

Component: API Component: Python API Effort: Medium Impact: Low UI: Extension Manager

When I disable and then re-enabled the sidekick plugin, I notice that it re-installs all of its dependencies, which I think is unnecesary

Dominant language
C++
Stars
1.3k
Forks
298
Avg merge
5d 5h
Merged PRs (30d)
19

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Vector35/binaryninja-api

All issues in Vector35/binaryninja-api

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.