docs(server-rent): warn against retrying hung rent commands#59
docs(server-rent): warn against retrying hung rent commands#59marvin-69-jpg wants to merge 1 commit into
Conversation
server rent is a billable action with no built-in idempotency. If the foreground command produces no output for a while and you re-issue it, both calls succeed and you end up with two servers (and two monthly charges). The CLI has no 'server delete' subcommand — duplicates have to be removed via the dashboard at https://zeabur.com/account/server. Add an explicit warning to run foreground, wait for output before retrying, and to poll 'server list' rather than guessing. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 58 minutes and 18 seconds. ⌛ 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. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ 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 |
2 participants
Summary
server rentis a billable action with no built-in idempotency. If the foreground command produces no output for a while and the agent re-issues it, both calls can succeed and you end up with two servers (and two monthly charges). I hit this exactly: a foreground rent command appeared hung, I retried, andserver listthen showed two new "Tencent Tokyo 2C 4GB" servers (one ID...49, the other...4c) created within seconds of each other.The CLI has no
server deletesubcommand, so the only recovery is the dashboard at https://zeabur.com/account/server. Cost of a wrongful retry is non-trivial.Adds an explicit warning to:
server list -i=false --jsonto see if a new server has appeared, rather than guessing whether the prior call succeededTest plan
server rent --provider tencent --region ap-tokyo --plan ...issued twice in quick succession produced two distinct servers, both billedserver deletesubcommand (server --helplists onlycatalog,get,list,plans,providers,reboot,regions,rent,ssh)🤖 Generated with Claude Code