Skip to content

fix: resolve pre-existing compilation errors in redfish and gcp libs#790

Open
mihir-dixit2k27 wants to merge 1 commit intolitmuschaos:masterfrom
mihir-dixit2k27:fix/compilation-errors
Open

fix: resolve pre-existing compilation errors in redfish and gcp libs#790
mihir-dixit2k27 wants to merge 1 commit intolitmuschaos:masterfrom
mihir-dixit2k27:fix/compilation-errors

Conversation

@mihir-dixit2k27
Copy link

This PR resolves critical pre-existing compilation errors and logging panics identified within the redfish and gcp libraries of the litmus-go repository. These issues were discovered during the environment setup phase and prevent the successful building of several experiment packages.

Key Changes:

Redfish Library: Corrected a log.Errorf call in pkg/baremetal/redfish/redfish.go that was missing the required %v format verb, which would lead to malformed logs or potential runtime issues.

GCP Library: Fixed a stacktrace.Propagate call in chaoslib/litmus/gcp-vm-instance-stop-by-label/lib/gcp-vm-instance-stop-by-label.go that was missing its mandatory error message argument, causing a compilation failure.

Which issue this PR fixes: N/A (Discovered during local development/build verification)
I have isolated these fixes from my main feature branch to maintain a clean and focused commit history. All changes were verified by running go build ./... on the affected directories to ensure they now compile successfully.

Signed-off-by: Mihir Dixit <dixitmihir1@gmail.com>
Copy link
Member

@neelanjan00 neelanjan00 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@mihir-dixit2k27
Copy link
Author

Observation regarding CI Failure: I noticed the Trivy security scan failed with exit code 1.

I have verified that my changes are strictly limited to logic fixes in redfish.go and gcp-vm-instance-stop-by-label.go. I have not modified go.mod, go.sum, or the Dockerfile, so this PR does not introduce any new dependencies or version changes.

This appears to be an infrastructure flake or a pre-existing baseline issue unrelated to this patch. Could a maintainer please re-trigger the workflow?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants