feature/kubernetes-management #70
No reviewers
Labels
No Label
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: sarman/tftsr-devops_investigation#70
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "feature/kubernetes-management"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Automated PR Review (qwen3-coder-next via liteLLM):\n\nSummary
This PR introduces Kubernetes management functionality, including cluster and port forwarding management, but contains critical issues: an uninitialized field in
AppStateforrefresh_registry, and a mismatch in the Tauri command handler registration (refresh_registryfield is present in spawned code but missing fromAppStatedefinition), leading to potential runtime panics or data corruption.Findings
AppStateused inside the OAuth callback spawned task initializesrefresh_registry, butAppStatestruct (as defined insrc-tauri/src/state.rs, confirmed via the registry insrc-tauri/src/kube/refresh.rsbeing used) is not shown to contain this field. Sincerefresh_registryis accessed in theAppStateconstructor inside the spawned task but not declared inAppState, this will fail to compile or cause runtime unsoundness.Evidence: Fix: Either add
pub refresh_registry: Arc<Mutex<RefreshRegistry>>toAppStateinsrc-tauri/src/state.rs, or removerefresh_registryinitialization if it's unused and not needed for OAuth callbacks.Verdict: REQUEST CHANGES