fix(ux): add operation context to error messages at command boundary#133
Conversation
Wrap 6 bare error returns in cmd/up.go and cmd/logs.go with fmt.Errorf so that when errors reach the top-level log.Fatal handler, users see what operation was being attempted.
✅ Deploy Preview for devsydev canceled.
|
|
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 32 minutes and 42 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 (2)
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 |
Summary
Wraps 6 bare
return err/return nil, errsites at the cmd/ boundary (cmd/up.goandcmd/logs.go) withfmt.Errorfcontext so that errors reaching the top-levellog.Fatalhandler tell the user what operation failed:load devsy config— config loading inupcommandstart workspace—devsyUpcall inexecuteDevsyUplock workspace—client.LockindevsyUpwait for machine—StartWaitindevsyUpMachineget agent info—AgentInfoindevsyUpMachineget workspace for logs—workspace.Getinlogscommand