Fixed outdated testcases and all compiler warning issues

[srinivas365]

Summary by CodeRabbit

• New Features

  • Expanded command support by adding operations like PING, ECHO, SET, GET, and related key commands to enhance interaction capabilities.
  • Introduced a structured approach to testing commands against a DiceDB client, including error handling and result verification.

• Improvements

  • Refined error messages for several commands to provide clearer, more concise feedback during command usage.
  • Adjusted the initialization process for the store across various tests to enhance configuration consistency.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[coderabbitai[bot]]

Walkthrough

The changes update multiple modules and test files to accommodate a modified dstore.NewStore signature, which now requires an additional integer parameter (set to 0). Various test files have been updated accordingly, and error messages in the Bloom filter tests have been streamlined by removing the "ERR " prefix and adjusting command names. Additionally, several new stub evaluation functions have been added to the evaluation module to expand command handling, and a new test file in the ironhawk package introduces a structured approach to executing DiceDB client commands.

Changes

File(s)	Change Summary
internal/eval/bloom_test.go	Updated TestBloomFilter and TestGetOrCreateBloomFilter to call dstore.NewStore(nil, nil, 0) and modified error messages by removing the "ERR " prefix and adjusting command names.
internal/eval/countminsketch_test.go internal/eval/eval_test.go internal/eval/hmap_test.go internal/eval/main_test.go internal/store/expire_test.go	Revised store initialization calls to include the new third parameter (0). In eval_test.go, removed testEvalGETSET; in hmap_test.go, updated variable assignments to ignore unused return values.
internal/store/batchevictionlru_test.go	Changed instantiation by removing the eviction rate parameter in NewPrimitiveEvictionStrategy and updating NewStore calls to include an extra parameter (0).
internal/eval/eval.go	Added new stub evaluation functions (evalPING, evalECHO, evalSET, evalGETEX, evalGETDEL, evalGET, evalEXPIRE, evalEXPIRETIME, evalEXPIREAT, evalTTL, evalDEL, evalTYPE, evalSETEX, evalINCR, evalINCRBY, evalDECR, evalDECRBY) to handle various commands, all currently returning nil.
tests0/main_test.go	Introduced a new test file in the ironhawk package featuring a TestCase struct, a local connection function, and a test runner (runTestcases) that executes command sequences and asserts expected results.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant Eval
    participant Store
    Client->>Eval: Send command (e.g., "PING", "SET", "GET")
    Eval->>Store: Process command with arguments (if applicable)
    Store-->>Eval: Return data (if applicable)
    Eval-->>Client: Return response (currently nil/stub)

sequenceDiagram
    participant T as TestRunner
    participant C as DiceDB Client
    participant DB as Server
    T->>C: Establish connection (getLocalConnection)
    T->>C: Flush database before tests
    loop For each TestCase
        T->>C: Execute command sequence
        C->>DB: Process command
        DB-->>C: Return response
        T->>C: Assert response equals expected result
    end

Poem

I'm a clever rabbit on a coding spree,
Hopping through changes as quick as can be.
New parameters and functions that gleam,
Like carrots of code in a springtime dream.
With streamlined errors and tests so bright 🥕,
I celebrate each change with a joyful hop tonight!

✨ 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.