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

Fix pgo_handler:decode_tag return value #64

Merged
merged 1 commit into from
Nov 10, 2022

Conversation

asabil
Copy link
Contributor

@asabil asabil commented Nov 8, 2022

When used with commands such as "SET" pgo_handler:decode_tag returned the 'set' atom alone instead of {set, nil} as is done for other commands that don't return any row count.

When used with commands such as "SET" pgo_handler:decode_tag returned
the 'set' atom alone instead of {set, nil} as is done for other commands
that don't return any row count.
@asabil
Copy link
Contributor Author

asabil commented Nov 10, 2022

I don't think the failing tests are due to this PR?

@tsloughter
Copy link
Collaborator

Yea, likely not.

I'm a little worried about changing the API like this. I guess it still is pre 1.0 so we can technically do it... Just prefer not to. So I'm still pondering it.

@asabil
Copy link
Contributor Author

asabil commented Nov 10, 2022

decode_tag/1 is not exported and currently pgo crashes when issuing SET requests. decode_tag/1 is used line 462 as {Command, NumRows} = decode_tag(Tag),.

I don't think this is an API change in any way :)

@tsloughter
Copy link
Collaborator

OOOOH! My bad

@tsloughter tsloughter merged commit d1989c4 into erleans:main Nov 10, 2022
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 this pull request may close these issues.

2 participants