[Bug]: Prebuilt binary download 404s and falls back to a slow cargo build
Maintainers usually reply within 3 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- build-system, release, tooling
Research direction
Start in lua/fff/download.lua and trace how the local git checkout produces the release tag and download URL. Compare the failing 0.10.7-nightly.48c77f5 and -dev. versions with the working 0.10.7-nightly.c1ec5f3, then verify downloads across the affected version formats. Done means valid prebuilt binaries download without falling back to cargo build.
Written by the indexing model from the issue text.
Description
Which fff frontend?
Neovim plugin (fff.nvim)
has logs
INFO Downloading fff.nvim binary for 0.11.1-dev.62740ec
WARN Do not open fff until you see a success notification.
WARN Error downloading binary: Failed to download: curl: (56) The requested URL returned error: 404
Trying cargo build --release
INFO fff.nvim binary built successfully!
Description
Every time I update the plugin, the prebuilt binary download 404s and it falls back to cargo build --release, which takes forever. This has been happening for a few months now. I'm on macOS (Apple Silicon) using lazy.nvim.
Looking at lua/fff/download.lua, the download URL is built from a release tag that comes from my local git checkout, and it seems like that tag doesn't always exist as a release:
0.10.7-nightly.48c77f5gives a 404, while the commit right before it,0.10.7-nightly.c1ec5f3, downloads fine.- I can't find any
-dev.releases newer than0.8.4-dev.180783ffrom May, even though the log shows a-dev.version.
The current main HEAD downloads fine for me, so it looks like only some commits or branches are affected.
Related: #623, #702
- Dominant language
- Rust
- Stars
- 11.2k
- Forks
- 473
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 32
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dmtrKovalenko/fff
-
triaged
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
dmtrKovalenko/fff#842 · 2 comments ·
Maintainers usually reply within 3 days
-
[Bug]: zlob walker ignores `.git/info/exclude`Possibly taken @gustav-fff claimed this 1 day ago. Opentriaged
Difficulty 4/5 3-5 days Newbie friendliness 35/100
dmtrKovalenko/fff#982 · 1 comment ·
Maintainers usually reply within 3 days
-
triaged
Difficulty 3/5 1-2 days Newbie friendliness 68/100
dmtrKovalenko/fff#980 · 1 comment ·
Maintainers usually reply within 3 days
-
[Bug]: pi-fff blocks session startup while indexing filesPossibly taken @adonis0147 claimed this 4 days ago. Openduplicate triaged
Difficulty 3/5 1-2 days Newbie friendliness 70/100
dmtrKovalenko/fff#975 · 1 comment ·
Maintainers usually reply within 3 days
-
[Bug]: on a non-git base path, the watcher indexes new files in hidden folders that the scan skips (0.11.0)Possibly taken @gustav-fff claimed this 6 days ago. Opentriaged
Difficulty 3/5 1-2 days Newbie friendliness 35/100
dmtrKovalenko/fff#972 · 2 comments ·
Maintainers usually reply within 3 days
All issues in dmtrKovalenko/fff
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
libnativeapi/nativeapi#21 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
longbridge/nsh#804 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day