feat(debug): comprehensive debug logging across all layers#132
Merged
Conversation
Cover API layer (compute, network, image, volume, LB, cloud), system infrastructure (SSH, self-update, config, quota), app core (connect, routing), and 22 previously uncovered UI views with shared.Debugf() calls using consistent start/success/error triplets and module tags.
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.
Summary
shared.Debugf()coverage to the API layer (compute, network, image, volume, loadbalancer, cloud) — previously at 0%[tag] verb resource paramspattern with start/success/error tripletsshared.Debugf()calls and necessary imports addedTest plan
go build ./...passes (verified)go vet ./...passes (verified)lazystack --debugand exercise all resource types~/.cache/lazystack/debug.logfor correct lifecycle logging