issue: add v9 issue types - #636
Conversation
|
Warning Review limit reachedNext included review available in 40 minutes. View limit detailsLimit details: You’ve used the included review currently available. This review ran on the open-source allowance, not this organization's plan, because the pull request author doesn't have an assigned seat. Waiting won't change this — ask an organization admin to assign them a seat, or add seats in Billing if every seat is already assigned, then retry. Review configuration: ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe issue type contracts add four new values: split tunneling, smart routing, server selection, and upgrade failures. ChangesIssue type contract expansion
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~5 minutes Suggested reviewers: Merge Risk: ⚪ Minimal · up to This change adds four issue-type values for v9 features with aligned numeric assignments. No current correctness, compatibility, or deployment risk remains beyond normal checks. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
🟡 Changes recommended
IssueType currently relies on iota/offsets while being cast to the protobuf enum, which is fragile for wire/API compatibility if constants are ever reordered or inserted later.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Pull request overview
Adds the v9 issue-type expansion to Radiance’s issue reporting API so clients can report additional categories that match the lantern-cloud enum.
Changes:
- Added
SPLIT_TUNNEL,SMART_ROUTING,SERVER_SELECTION,UPGRADE_FAIL(11–14) toReportIssueRequest.ISSUE_TYPE. - Regenerated the Go protobuf bindings to include the new enum values.
- Extended the local
IssueTypeconstants to cover the new categories.
File summaries
| File | Description |
|---|---|
| issue/issue.proto | Adds the four new enum values to ReportIssueRequest.ISSUE_TYPE. |
| issue/issue.pb.go | Regenerated protobuf output to reflect the enum changes. |
| issue/issue.go | Adds corresponding IssueType constants used by the issue reporter. |
Review details
Files not reviewed (1)
- issue/issue.pb.go: Generated file
- Files reviewed: 2/3 changed files
- Comments generated: 2
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
context
implements:
used by:
API side:
summary
SPLIT_TUNNEL,SMART_ROUTING,SERVER_SELECTION,UPGRADE_FAIL(11-14) to theReportIssueRequestproto and theIssueTypeconstants, matching lantern-cloud's apipb enumSummary by CodeRabbit