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

Compile error after braking change in pkg/errors #74

Open
arcana261 opened this issue Jan 5, 2019 · 5 comments
Open

Compile error after braking change in pkg/errors #74

arcana261 opened this issue Jan 5, 2019 · 5 comments

Comments

@arcana261
Copy link
Contributor

arcana261 commented Jan 5, 2019

Hiiiiiii

Today a breaking change in github.com/pkg/errors package was merged which changes type for errors.Frame from a simple program counter to runtime.Frame.

github.com/evalphobia/logrus_sentry/sentry.go:314:16
cannot convert stFrames[i] (type "github.com/pkg/errors".Frame) to type uintptr

I will work on a MR right away

@mexisme
Copy link

mexisme commented Jan 6, 2019

Is pkg/errors#188 related to this?
As it looks like related PR pkg/errors#183 has just been merged.

@arcana261
Copy link
Contributor Author

@mexisme Yes dear good sir..

@evalphobia
Copy link
Owner

@arcana261 Thanks 🍡 #75 has been Merged.
https://github.com/evalphobia/logrus_sentry/releases/tag/v0.7.0

davecheney added a commit to pkg/errors that referenced this issue Jan 9, 2019
Updates aws/aws-xray-sdk-go#77
Updates evalphobia/logrus_sentry#74

Go 1.12 has updated the behaviour of runtime.FuncForPC so that it
behaves as it did in Go 1.11 and earlier.

This allows errors.Frame to return to a uintptr representing the PC +1
of the caller. This will fix the build breakages of projects that were
tracking HEAD of this package.

Signed-off-by: Dave Cheney <dave@cheney.net>
@arcana261
Copy link
Contributor Author

OMG They've done it again :'( :'( :'(

@arcana261
Copy link
Contributor Author

I've again submitted another PR #76 which reverts us to using just PC's.

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

No branches or pull requests

3 participants