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

bugfix for resp parser #4

Merged
merged 3 commits into from
Dec 20, 2022
Merged

bugfix for resp parser #4

merged 3 commits into from
Dec 20, 2022

Conversation

brayniac
Copy link
Collaborator

@brayniac brayniac commented Dec 20, 2022

Fixes #3 by improving the utlity functions which we use to operate
on the array of tokens.

Previously, we were having to track our position in the token
stream but were mixing that with functions which removed tokens
from the stream.

This change makes all the utility functions act by attempting to
take a token from the front of the token stream. This makes the
parser more intuitive to write and less likely to have the same
class of bug.

move rustcommon dependency to pelikan-io fork
Fixes pelikan-io#3 by improving the utlity functions which we use to operate
on the array of tokens.

Previously, we were having to track our position in the token
stream but were mixing that with functions which removed tokens
from the stream.

This change makes all the utility functions act by attempting to
take a token from the front of the token stream. This makes the
parser more intuitive to write and less likely to have the same
class of bug.
@brayniac brayniac changed the title Resp fix bugfix for resp parser Dec 20, 2022
@brayniac brayniac merged commit ddeb75f into pelikan-io:main Dec 20, 2022
@brayniac brayniac deleted the resp-fix branch December 20, 2022 18:27
@luzhang6
Copy link

Hi @brayniac @thinkingfish @kevyang, sorry to ask an irrelevant question on this pr, recently I am testing segcache, and I would like to ask about the eviction policy for segcache, are both ttl and segment size factors that will trigger eviction for cache item?
For example, I set 500s ttl, and my test would take about 1 minute to run. If I am still getting 0s for a cached key, is that caused by the cache segment is full and that value is kicked out? Thank you.

@brayniac
Copy link
Collaborator Author

@luzhang6 - it would be better to ask this question in a new issue since it isn't relevant to this PR. Will be happy to address the question once asked in a new issue.

@luzhang6
Copy link

Thanks, will do!

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.

Set command option's like 'EX 1000' and NX failing to parse
3 participants