Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: GET command gives an error invalid number of arguments #1423

Open
4 tasks
arpitbbhayani opened this issue Jan 29, 2025 · 3 comments · May be fixed by #1431
Open
4 tasks

Bug: GET command gives an error invalid number of arguments #1423

arpitbbhayani opened this issue Jan 29, 2025 · 3 comments · May be fixed by #1431

Comments

@arpitbbhayani
Copy link
Contributor

arpitbbhayani commented Jan 29, 2025

Pick this issue only after #1420 is merged.

Start the DiceDB server

$ go run main.go --engine ironhawk --log-level debug

Start the DiceDB CLI

$ go run main.go --engine ironhawk

Fire the commands

localhost:7379> GET 
ERR wrong number of arguments for 'GET' command
localhost:7379> GET k1
ERR wrong number of arguments for 'GET' command
localhost:7379> GET k1
ERR wrong number of arguments for 'GET' command

If the first time there is an error in number of arguments, then the error continues even if we pass the right number of arguments. Must be some dirty buffer or variable.

Steps to patch

  1. setup DiceDB server locally from source - instructions
  2. setup DiceDB CLI locally from source - instructions

Follow the contribution guidelines

These are general guidelines to follow before you submit a patch. Please mark them as done
once you complete them

@rawwar

This comment has been minimized.

@debadutta98 debadutta98 linked a pull request Jan 29, 2025 that will close this issue
@debadutta98
Copy link

@arpitbbhayani The issue is resolved could you please review the PR?

@rawwar

This comment has been minimized.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants