Conversation
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📝 WalkthroughWalkthroughNeovim PPA source in Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
9e8ae15 to
c5f1924
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@bootstrap.sh`:
- Line 397: The script currently adds the unstable Neovim PPA via the call to
runCmdAndLog add-apt-repository -y ppa:neovim-ppa/unstable which fails on Ubuntu
20.04; update bootstrap.sh to choose the stable PPA for focal or fall back to
stable when the OS version is 20.04: detect the release (e.g., via lsb_release
-rs or /etc/os-release), and replace the unconditional add-apt-repository
invocation with logic that sets the PPA variable to ppa:neovim-ppa/stable for
"20.04" (focal) and ppa:neovim-ppa/unstable for newer releases, then call
runCmdAndLog add-apt-repository -y "$PPA".
| logStep "Installing NeoVim..." | ||
| # Adds repo for latest neovim version | ||
| runCmdAndLog add-apt-repository -y ppa:neovim-ppa/stable | ||
| runCmdAndLog add-apt-repository -y ppa:neovim-ppa/unstable |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
neovim-ppa/unstable PPA Ubuntu 20.04 focal support
💡 Result:
As of February 2, 2026, the ppa:neovim-ppa/unstable PPA does not publish packages for Ubuntu 20.04 (focal). On the PPA page, the selectable / published series are Jammy (22.04) and newer (Noble 24.04, Plucky 25.04, Questing 25.10, Resolute 26.04), with no Focal entry. [1]
Historically, there were focal builds in this PPA (e.g., recipe builds targeting the Focal series), but focal is not currently supported/published. [2]
Sources: [1] [2]
🏁 Script executed:
# Find and examine the bootstrap.sh file around line 397
find . -name "bootstrap.sh" -type fRepository: yorch/ubuntu-server-bootstrap
Length of output: 87
🏁 Script executed:
# Search for NeoVim-related installation code
rg -A 5 -B 5 "neovim-ppa" --type shRepository: yorch/ubuntu-server-bootstrap
Length of output: 651
NeoVim unstable PPA is incompatible with Ubuntu 20.04, a required supported version.
The ppa:neovim-ppa/unstable does not publish packages for Ubuntu 20.04 (focal). Switching from the stable PPA breaks the bootstrap script on Ubuntu 20.04, which is listed as a supported LTS version. Either:
- Use
ppa:neovim-ppa/stablefor cross-version compatibility - Add logic to use stable PPA on Ubuntu 20.04 and unstable on newer versions
- Remove Ubuntu 20.04 from supported versions
🤖 Prompt for AI Agents
In `@bootstrap.sh` at line 397, The script currently adds the unstable Neovim PPA
via the call to runCmdAndLog add-apt-repository -y ppa:neovim-ppa/unstable which
fails on Ubuntu 20.04; update bootstrap.sh to choose the stable PPA for focal or
fall back to stable when the OS version is 20.04: detect the release (e.g., via
lsb_release -rs or /etc/os-release), and replace the unconditional
add-apt-repository invocation with logic that sets the PPA variable to
ppa:neovim-ppa/stable for "20.04" (focal) and ppa:neovim-ppa/unstable for newer
releases, then call runCmdAndLog add-apt-repository -y "$PPA".
There was a problem hiding this comment.
Pull request overview
This PR makes small style adjustments to arithmetic and redirection expressions and changes the Neovim APT repository used during bootstrap. The primary behavioral change is that Neovim will now be installed from the unstable PPA instead of the stable one.
Changes:
- Normalize spacing in redirections and arithmetic expansions in
runCmdAndLog,startSpinner, and the elapsed-time calculation at the end of the script. - Change the Neovim installation source from
ppa:neovim-ppa/stabletoppa:neovim-ppa/unstable.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| logStep "Installing NeoVim..." | ||
| # Adds repo for latest neovim version | ||
| runCmdAndLog add-apt-repository -y ppa:neovim-ppa/stable | ||
| runCmdAndLog add-apt-repository -y ppa:neovim-ppa/unstable |
There was a problem hiding this comment.
Switching from ppa:neovim-ppa/stable to ppa:neovim-ppa/unstable changes this step from installing the latest stable Neovim to tracking an "unstable" channel, which can introduce breaking changes or repository issues over time and makes bootstrap runs less predictable. If the intent is to get the newest features, consider either keeping the stable PPA and updating when needed, making the channel (stable vs unstable) configurable via a flag/env var, or clearly documenting that this script now depends on an unstable PPA so users understand the tradeoff.
c5f1924 to
b3feea6
Compare
The unstable PPA package does not register nvim in the vi/vim alternatives groups, so update-alternatives --set fails with exit code 2. Switch to --install which both registers and selects the alternative with priority 110. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Summary
ppa:neovim-ppa/stabletoppa:neovim-ppa/unstableto get the latest Neovim buildsTest plan
bash run-tests.sh ubuntu:24.04to verify Neovim installs from the unstable PPAnvim --versionshows a newer version than the stable PPA provides🤖 Generated with Claude Code
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.