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

Replace memmap #484

Merged
merged 2 commits into from Jan 5, 2022
Merged

Replace memmap #484

merged 2 commits into from Jan 5, 2022

Conversation

Jake-Shadle
Copy link
Contributor

memmap has been marked as unmaintained for over a year now, this just replaces it with the maintained memmap2 fork.

@Jake-Shadle Jake-Shadle requested a review from a team as a code owner January 5, 2022 10:31
Copy link
Member

@Swatinem Swatinem left a comment

Choose a reason for hiding this comment

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

Is there some discussion I can read through regarding this is unmaintained/superceded?

@Jake-Shadle
Copy link
Contributor Author

The advisory links to the original issue danburkert/memmap-rs#90 where multiple people tried to get in contact with the maintainer.

@Swatinem Swatinem merged commit 30b5223 into getsentry:master Jan 5, 2022
@Swatinem
Copy link
Member

Swatinem commented Jan 5, 2022

Thanks for clarifying! I guess its time to add automatic checking for this in CI, looks like we only have that for the rust SDK.

@extrawurst
Copy link

glad this was finally tackled. interested what has changed since: #304

@Swatinem
Copy link
Member

I think if it gets flagged via RUSTSEC advisories, that is a bit of an incentive to do the transition. Although the advisories can be a bit overeager sometimes.

@extrawurst
Copy link

when can we get a release with this? :)

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.

None yet

3 participants