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

[catmem] Don't Close Pipe When EoF is Reached #482

Merged
merged 7 commits into from
Feb 28, 2023
Merged

Conversation

ppenna
Copy link
Contributor

@ppenna ppenna commented Feb 24, 2023

Description

This PR closes #480

Summary of Changes

@ppenna ppenna added the bug Something Isn't Working label Feb 24, 2023
@ppenna ppenna self-assigned this Feb 24, 2023
Copy link
Contributor

@iyzhang iyzhang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The changes to catmem conflict with my changes in PR #486. It should be easy to replace the ring field in CatmemQueue without disturbing any of the rest of the code, but I'm not sure what order in which these two PRs should go in. Otherwise, the changes look good to me.

@ppenna
Copy link
Contributor Author

ppenna commented Feb 28, 2023

The changes to catmem conflict with my changes in PR #486. It should be easy to replace the ring field in CatmemQueue without disturbing any of the rest of the code, but I'm not sure what order in which these two PRs should go in. Otherwise, the changes look good to me.

Yes, let us work together on your enhancement changes to make sure that they also cover this bug fix.

@ppenna ppenna merged commit 91dd687 into dev Feb 28, 2023
@ppenna ppenna deleted the bugfix-catmem-eof branch February 28, 2023 11:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something Isn't Working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[catmem] Don't Close Pipe When EoF is Reached
2 participants