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(demangle): Update cpp_demangle due to breaking change #244

Merged
merged 1 commit into from
Jun 10, 2020

Conversation

o0Ignition0o
Copy link
Contributor

@o0Ignition0o o0Ignition0o commented Jun 10, 2020

Fixes #243

cpp_demangle::DemangleOptions now has a no_return_type field which causes an issue in symbolic-demangle lib.rs
the breaking change occured in a patch version which means running cargo update breaks people's builds.

cpp_demangle::DemangleOptions now has a no_return_type field which causes an issue in symbolic-demangle lib.rs
the breaking change occured in a patch version which means running `cargo
update` breaks people's builds.
@o0Ignition0o o0Ignition0o requested a review from a team June 10, 2020 10:56
@o0Ignition0o o0Ignition0o changed the title Update cpp_demangle::DemangleOptions so simbolic_demangle can compile. Update cpp_demangle::DemangleOptions so symbolic_demangle can compile. Jun 10, 2020
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.

well this is unfortunate

@calixteman
Copy link
Contributor

Would it be possible to merge & make a new release asap please ?

@o0Ignition0o
Copy link
Contributor Author

In case it helps anyone stumbling on it before a new release is out, a workaround in the meantime is to pin cpp_demangle in a Cargo.toml file, for example:

symbolic-demangle = "6.1"
cpp_demangle  = "=0.2.16"

@jan-auer
Copy link
Member

👍 I'll bump and release. This will take a little bit this time.

Next time something like this happens, I think the "right" course of action would be to ask maintainers to yank the offending version and bump properly.

Copy link
Member

@jan-auer jan-auer left a comment

Choose a reason for hiding this comment

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

Agreed with the TODO comment. There's also #165 still open. I think the proper enhancement will be to add many more generalized flags to DemangleOptions and convert it into a builder to not break.

@jan-auer jan-auer changed the title Update cpp_demangle::DemangleOptions so symbolic_demangle can compile. fix(demangle): Update cpp_demangle due to breaking change Jun 10, 2020
@jan-auer jan-auer merged commit a6760ea into getsentry:master Jun 10, 2020
@o0Ignition0o o0Ignition0o deleted the igni/cpp_demangle_options branch June 10, 2020 14:49
@o0Ignition0o
Copy link
Contributor Author

Next time something like this happens, I think the "right" course of action would be to ask maintainers to yank the offending version and bump properly.

Oh indeed, I'll do just that next time, thanks for your time!

@khuey
Copy link

khuey commented Jun 11, 2020

Thanks for reporting this to me btw.

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.

cpp_demangle patch bump
5 participants