Skip to content

Conversation

@efirs
Copy link
Contributor

@efirs efirs commented Apr 8, 2025

No description provided.

Copilot AI review requested due to automatic review settings April 8, 2025 06:00
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

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

Copilot reviewed 2 out of 4 changed files in this pull request and generated no comments.

Files not reviewed (2)
  • test/cases/tigris_posix_meta.sh: Language not supported
  • test/run-cases.sh: Language not supported
Comments suppressed due to low confidence (2)

main_nowindows.go:93

  • Ensure that removing the debug log messages for both the parent and child processes does not reduce visibility in the daemonization process's failure scenarios. Verify the new logging behavior provides adequate context for troubleshooting.
if child != nil {

main.go:115

  • Re-initializing the loggers after daemonization might override earlier configuration; please confirm that this ordering meets the intended logging setup without causing unintended side effects.
cfg.InitLoggers(flags)

@efirs efirs force-pushed the fix_logger_daemonize branch from fd22a99 to 58023a5 Compare April 8, 2025 06:04
@efirs efirs changed the title fix: Fix logger after daemonizing fix: Fix no logs after daemonizing Apr 8, 2025
@efirs efirs force-pushed the fix_logger_daemonize branch 2 times, most recently from 5e280ea to 02647ef Compare April 8, 2025 20:20
@efirs efirs force-pushed the fix_logger_daemonize branch from 02647ef to 0cffdd2 Compare April 9, 2025 05:26
@efirs efirs merged commit 0cffdd2 into main Apr 9, 2025
4 checks passed
@tigrisdata-argocd-bot
Copy link

🎉 This PR is included in version 1.1.2 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@efirs efirs deleted the fix_logger_daemonize branch April 11, 2025 23:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants