web: fix inactive environment details (1.6.178) - #177
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix inactive environment view/edit after globally authorized project and member reads succeed. Skip only inapplicable inactive-scoped network and policy-manager reads; show the state-specific explanation in English/Traditional Chinese and prevent stale network persistence. Preserve global action links, all non-inactive/error paths, backend authorization, authentication/session and workspace lifecycle contracts. Dependencies are unchanged.
Reviewed tree 5febc2791e331d514ae08958ce8a6a083a72f0d2 based on de09be0. Local focused coverage is 24 distinct passing cases: 21 unchanged cases plus the final three affected integrations, not a single 24/24 run. The first two test-fixture failure logs are retained; localization validation has no missing keys. Exact-source workflow-dispatched validation, retained regressions, two reproducible archives and normal CodeQL gates remain required before immutable release. Source candidate README/release notes do not claim publication or deployed acceptance. Historical HOLDs and the full incomplete matrix remain unchanged. No production deployment or runtime patch.