feat: cardinal pretty logging, improve goroutine reliability, kill --watch

[smsunarto]

TL;DR

What changed?

• world cardinal dev now use pretty logging on latest Cardinal version. This is done by setting CARDINAL_PRETTY_LOG to true.
• Refactors to goroutine management in world cardinal start and world cardinal dev to make it more reliable using error group.
• Disable printing the usage guide when a command returns an error.
• Various string reformatting using lipgloss to make things look pretty.
• Prevent exit code 130, 137, 143 from being treated as an error since it's an expected exit code from Docker when it receives termination signal (i.e. Ctrl + C, SIGKILL, SIGTERM, etc)
• Kill world cardinal dev --watch flag because runner is ugly and buggy af

How to test?

1. Run world cardinal dev and world cardinal start and try to break it. This includes running it against various edge cases (i.e. Redis already running, kill redis when cardinal is running, etc)

[graphite-app]

Your org has enabled the Graphite merge queue for merging into main

Add the label “graphite/merge” to the PR and Graphite will automatically add it to the merge queue when it’s ready to merge.

You must have a Graphite account and log in to Graphite in order to use the merge queue. # using this link.

[coderabbitai]

Important

Auto Review Skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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.

[smsunarto]

• feat: cardinal pretty logging, improve goroutine reliability, kill --watch #64 👈
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @smsunarto and the rest of your teammates on Graphite

[codecov]

Codecov Report

Attention: Patch coverage is 47.82609% with 12 lines in your changes are missing coverage. Please review.

Project coverage is 52.63%. Comparing base (03aa9eb) to head (cf5a2a0).

Files	Patch %	Lines
common/teacmd/docker.go	0.00%	8 Missing ⚠️
cmd/world/root/root.go	73.33%	4 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #64      +/-   ##
==========================================
- Coverage   52.72%   52.63%   -0.09%     
==========================================
  Files           9        9              
  Lines         698      720      +22     
==========================================
+ Hits          368      379      +11     
- Misses        262      273      +11     
  Partials       68       68              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[zulkhair]

I'm testing to run with world cardinal dev --watch. It got stuck when i'm tryin to send sigint.

[zulkhair]

Tested all the functionality. LGTM

[zulkhair]

Unit test is failed because cardinal editor run called twice on different test case.

Adding --editor=false flag on line 128 and 184 should resolve this problem.