Integrated wal with ironhawk server

[ayushsatyam146]

Integrated WAL with ironhawk engine by putting the initialized WAL in ShardManager struct and consuming it from there to Log the commands

Summary by CodeRabbit

• Chores
  • Enhanced internal tracking and diagnostics, boosting overall system stability and reliability while maintaining a seamless user experience.

[coderabbitai[bot]]

Walkthrough

The changes integrate write-ahead logging into the command execution and shard management processes. In the command execution flow (in internal/cmd/cmds.go), a new conditional block checks for non-replay commands and logs them using the WAL interface, returning errors if logging fails. The ShardManager (in internal/shardmanager/main.go) now includes a new Wal field, and its constructor has been updated to accept a wal.AbstractWAL parameter. Correspondingly, the server instantiation (in server/main.go) has been modified to pass the WAL instance during the creation of the shard manager.

Changes

File(s)	Change Summary
internal/cmd/cmds.go	Added a conditional block in the Execute method to log non-replay commands using the WAL interface; returns current result and error if logging fails.
internal/shardmanager/main.go server/main.go	Updated ShardManager to include a new Wal field and modified its constructor to require a wal.AbstractWAL parameter. Instantiation in the server now includes the additional WAL parameter.

Sequence Diagram(s)

sequenceDiagram
    participant Cmd as Command
    participant WAL as WAL Interface
    participant Handler as Command Handler

    Cmd->>Handler: Execute command
    alt Command is not a replay and WAL exists
        Handler->>WAL: LogCommand(formatted command & args)
        alt Logging fails
            WAL-->>Handler: Return error
            Handler-->>Cmd: Return result with error
        else Logging succeeds
            WAL-->>Handler: Acknowledge logging
            Handler-->>Cmd: Continue execution
        end
    else 
        Handler-->>Cmd: Continue execution without logging
    end

sequenceDiagram
    participant Server as Server
    participant SMConstructor as NewShardManager
    participant WAL as WAL Instance

    Server->>+SMConstructor: NewShardManager(numShards, serverErrCh, wal)
    SMConstructor->>SMConstructor: Initialize ShardManager with new Wal field
    SMConstructor-->>-Server: Return new ShardManager with WAL dependency

Poem

I'm a rabbit with a coding hop,
Logging commands is now on top.
With WAL injected in every beat,
ShardManager marches fast and neat.
I nibble bugs with joyful cheer,
Hopping through code, innovation is here!
🐇💻 Hop on to the updated frontier!

✨ Finishing Touches

• [ ] 📝 Generate Docstrings

---

🪧 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.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.

[CLAassistant]

All committers have signed the CLA.