Vector35 / Vector35/binaryninja-api

Remote project files don't have a reported file size until downloaded

Open
#5,644 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Component: UI Edition: Ultimate Effort: Medium Impact: Low UI: Projects
Dominant language
C++
Stars
1.3k
Forks
298
Avg merge
5d 5h
Merged PRs (30d)
19

Description

See title. This is most frustrating when it turns out the file you tried to open is secretly 500mb in size and you're not on good internet.

This is an artifact of us having previously needed to pass all of this information over the plugin boundary, which is no longer an issue as of 4.1.5270-dev. We just need to do the refactor required to fix this.

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.

Research direction

Start by tracing how remote project files cross the plugin boundary, using the change noted as available in 4.1.5270-dev. The refactor is complete when a remote file reports its size before it is downloaded, including for large files; no specific files or tests are named in the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
backend-api-design
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.