fixed log level mismatch

[knakul853]

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

• Style
  • Adjusted logging levels to ensure debug messages are only shown when debug logging is enabled.
  • Improved error messages for failed debug output file operations by providing clearer, structured error logs.

[coderabbitai]

Walkthrough

The changes adjust logging behaviors in two areas: the debug callback in the DSL package now logs at the debug level instead of info, and error handling in the output package uses structured error logging instead of printing errors directly to standard output.

Changes

File(s)	Change Summary
pkg/operators/common/dsl/dsl.go	Changed dsl.PrintDebugCallback to log at debug level instead of info.
pkg/output/output.go	Updated error handling in WriteStoreDebugData to use structured error logging via gologger.

Poem

A rabbit tweaks the logs today,
Debug and info, swapped their way.
Errors now with structure told,
No more prints, but logs so bold.
In burrows deep, the code runs neat—
Hop along, the logs repeat!
🐇✨

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

pkg/operators/common/dsl/dsl.go (1)

117-117: Lower DSL print callback to Debug level
Switching from Info to Debug here correctly reduces verbosity for DSL debug output. Consider using %v instead of %s to log the slice of arguments directly and avoid the extra fmt.Sprint call:

-   gologger.Debug().Msgf("print_debug value: %s", fmt.Sprint(args))
+   gologger.Debug().Msgf("print_debug value: %v", args)

pkg/output/output.go (1)

563-563: Use structured error logging for debug file open failures
Replacing fmt.Print with gologger.Error().Msgf ensures consistency with the application's logging framework. For better diagnostics, include the filename being opened in the log message:

-   gologger.Error().Msgf("Could not open debug output file: %s", err)
+   gologger.Error().Msgf("Could not open debug output file %q: %v", filename, err)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 5af6feb and aba8c47.

📒 Files selected for processing (2)

• pkg/operators/common/dsl/dsl.go (1 hunks)
• pkg/output/output.go (1 hunks)

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

• GitHub Check: Lint