fix missing event for multi protocol

[ShubhamRasal]

Proposed changes

Checklist

• Pull request is created against the dev branch
• All checks passed (lint, unit/integration/regression tests etc.) with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

Summary by CodeRabbit

• Bug Fixes
  • Improved error handling in protocol execution to allow continued processing when non-fatal errors occur.

[coderabbitai]

Walkthrough

The pull request modifies the error handling logic in the ExecuteWithResults method of the MultiProtocol struct within the pkg/tmplexec/multiproto/multi.go file. The key change involves removing the line that previously returned an error, which means the method will now continue executing remaining protocols even if an error occurs during the execution of a specific protocol. This approach aligns with the comment suggesting that certain errors, particularly those related to SSL protocols, should be treated as non-fatal.

Changes

File	Change Summary
pkg/tmplexec/multiproto/multi.go	Removed error return statement in ExecuteWithResults method, allowing continued execution of protocols after encountering an error

Possibly related PRs

• fix(multiproto): missing previous InternalEvents output when ExecuteWithResults #5967: Modifies the ExecuteWithResults method in the MultiProtocol struct, focusing on result handling and error management

Suggested reviewers

• ehsandeep
• dogancanbakir

Poem

🐰 Protocols dance, errors may sway
But execution marches on its way
No halt, no stop, just forward bound
Resilience in code, a rabbit's proud sound!
Continuing the journey, come what may 🚀

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e4a0b8e and 0e3ef3f.

📒 Files selected for processing (1)

• pkg/tmplexec/multiproto/multi.go (0 hunks)

💤 Files with no reviewable changes (1)

• pkg/tmplexec/multiproto/multi.go

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: Lint

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.