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

upgrade to 0.9.3 produces Execution error, 'Unable to resolve spec: ...' #37

Closed
pupcus opened this issue Mar 20, 2020 · 5 comments
Closed

Comments

@pupcus
Copy link

pupcus commented Mar 20, 2020

For the 0.9.x series, things seem fine through the 0.9.2 release. When I try to use the 0.9.3 release I get the following error when compiling:

Execution error at diehard.util/verify-opt-map-keys-with-spec (util.clj:13).
Unable to resolve spec: :retry/retry-policy-new

We are backing up to 0.9.2 for the work we are doing but I thought you would want to know.
Perhaps we are doing something wrong on our end, but this is code that has been working well and has not changed in quite some time.

Thanks for your work on this library! :-)

@sunng87
Copy link
Owner

sunng87 commented Mar 20, 2020

Thank you for the information! Unfortunately I cannot reproduce this issue with my tests. Do you have a context of this error? Is it inside your repl?

@msassak
Copy link

msassak commented Mar 20, 2020

I'm seeing the same thing after upgrading to 0.9.3:

Execution error at diehard.util/verify-opt-map-keys-with-spec (util.clj:13).
Unable to resolve spec: :retry/retry-block

I think there is a missing require in diehard.core. To get around the error in 0.9.3 I required diehard.spec before diehard.core and the error is gone.

@sunng87
Copy link
Owner

sunng87 commented Mar 21, 2020

Thank yoy! It's an issue introduced in this lint fix: 79e966c

I will fix and create a new release soon.

@sunng87
Copy link
Owner

sunng87 commented Mar 21, 2020

Fixed in 0.9.4

@pupcus
Copy link
Author

pupcus commented Mar 21, 2020

Thanks! :-)

@pupcus pupcus closed this as completed Mar 21, 2020
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