-
Notifications
You must be signed in to change notification settings - Fork 24
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
Error in :ret check when using with Orchestra 2020.07.12-1 #199
Comments
@Limess Thanks for reporting this and apologies for the long delay. It appears the new implementation of Orchestra had some changes in the Do you have the ability to try out a specific git SHA in your project? If so, I'd appreciate it if you could try cdabbff before I release it. I think it may solve your problem, but frankly I'm not 100% sure. I tried to construct a repro based on your description above but I may be missing something crucial. Thanks!! |
No worries, really appreciate your work on this! I checked out that SHA and tried it and it fixes the issue we were seeing 👍🏻. |
@Limess Thanks for trying it out! |
Fixed in #202 |
@Limess Thanks again for your help. I've just released 0.8.6, which includes this fix. |
Copied the details from a discussion on the Clojure slack, the messages in these links may expire.
First message around this issue: https://clojurians.slack.com/archives/CC68FBBAM/p1597150256011800
Follow up where we dug into it a little: https://clojurians.slack.com/archives/CC68FBBAM/p1597677078024100
I'm seeing the following exception:
when using expound with Orchestra:
The explain data for this is:
and the failing spec is an object using
s/keys
, where the failing key is:When attempting to use
stest/instrument
instead I realised this was coming from the failure of:ret
in anfdef
. When calling a new function using the same spec as used in:ret
, but instead in:args
, expound worked as correctly.I also tried removing the usage of
s/and
and this did not affect the failure.The handler where we're using expound is as follows:
The above failures were when the spec definition for
expound.alpha/value-in-context
was overriden, as I'd previously seen this last week, but had written it off as user-error. The discussion led to the suggestion of disabling the spec for that function which was failing as follows (note that the actual spec causing the failure was different in the error below, but was the same failure mode):The text was updated successfully, but these errors were encountered: