-
Notifications
You must be signed in to change notification settings - Fork 91
Last commit broke the project #27
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
Comments
Incidentally, it looks like you aren't running the unit-tests on pull-requests. Otherwise, that could've allowed you to identify this issue before merging. |
…rsion is very legacy and very unsupported. go-errors/errors#27
…rsion is very legacy and very unsupported. go-errors/errors#27
…rsion is very legacy and very unsupported. go-errors/errors#27
…rsion is very legacy and very unsupported. go-errors/errors#27
…rsion is very legacy and very unsupported. go-errors/errors#27 red, and an empty message aborts the commit.
…rsion is very legacy and very unsupported. go-errors/errors#27 red, and an empty message aborts the commit.
…rsion is very legacy and very unsupported. go-errors/errors#27 red, and an empty message aborts the commit.
Tip of dependency is broken and it was affecting us: go-errors/errors#27
Tip of dependency is broken and it was affecting us: go-errors/errors#27 - We also disabled 1.10 and 1.11 due to lack of support in dependencies now that we're being recognized as a module.
Thanks for reporting @dsoprea, it looks like the tests are running We introduced a fix that only works on @titouanfreville I think it should be easy to make your change backward compatible by using go build tags to conditionally change the implementation of |
I hadn't realized that several of my projects weren't recognized as
modulized in Travis. So, I was running against your master tip. I forced
module support, disabled 1.10 and 1.11, and got unblocked.
I would encourage you to revert immediately as your project is currently
unusable for first-time implementers. Put the current version in a branch
for them to fix. Once fixed, squash and rebase back to master.
…On Mon, Jun 1, 2020, 13:00 Conrad Irwin ***@***.***> wrote:
Thanks for reporting @dsoprea <https://github.com/dsoprea>, it looks like
the tests are running go1.10 which has been unsupported for a while now.
We introduced a fix that only works on go1.13 (the oldest maintained
version of go) and above; what version of go are you running?
@titouanfreville <https://github.com/titouanfreville> I think it should
be easy to make your change backward compatible by using go build tags to
conditionally change the implementation of Is depending on the go
version, or by copy-pasting the code from go1.13's errors package into
here. Is that something you'll have time to look at?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#27 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFOW2SVWR4RWHTXELIMYRDRUPNBXANCNFSM4NPPC5PQ>
.
|
Implemented solution with tags. Test are now ok. |
Your code isn't currently compiling. The tests are reflecting this. Looks like the last change broke it.
https://travis-ci.org/github/go-errors/errors/jobs/692460222
baa9282#diff-faeee970b41138d8bdc51e7aa3601141R147
You probably meant
Is()
, noterrors.Is()
.Please fix or revert.
The text was updated successfully, but these errors were encountered: