Add error checking for crowdsecDaemon.Process.Kill() in hubtest #145
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.
Problem
The
crowdsecDaemon.Process.Kill()call inpkg/hubtest/hubtest_item.gowas not checking for errors, which could lead to silent failures during test cleanup. This violates Go best practices for error handling and makes debugging difficult when process termination fails.Solution
Added proper error checking for the
Process.Kill()call following the existing error handling patterns in the file:Changes
pkg/hubtest/hubtest_item.goRunWithNucleiTemplate()methodBenefits
log.Errorf()pattern used throughout the filenilfor cleanup)The change is minimal and surgical, affecting only the error handling for this specific cleanup operation while maintaining full backward compatibility.
This pull request was created as a result of the following prompt from Copilot chat.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.