-
Notifications
You must be signed in to change notification settings - Fork 847
Fix #13686 by upgrading the FsCheck version to next alpha version (stable version is not available on dotnet-public) #13687
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 #13686 by upgrading the FsCheck version to next alpha version (stable version is not available on dotnet-public) #13687
Conversation
|
Odd, as this wasn't an issue locally, which used the same Let's try the latest alpha then. |
|
@abelbraaksma , if you let us know what version to prop to our nuget feed, we will ensure it gets added. thanks KEvin |
|
@KevinRansom, thanks! From the referred issue #13686, that would be stable FsCheck I tested locally with the stable branch, I think that, if we can, we should use that, and no alpha or beta branches. |
|
This is ready for review, unless the nuget feed gets updated such that I can pick up a newer version (not sure how long that normally takes, ie, is there some formal process or not?), in which case we could use the latest version instead. |
|
@KevinRansom and/or @vzarytovskii I'm not sure about what's needed to change the MS nuget feed, please advice. Otherwise, the current PR solves the problems with running these tests on Windows machines. It would be nice to get unblocked on other PRs ;). |
|
2.6.15 should be in dotnet-public |
|
@vzarytovskii, see #13687 (comment). It isn't picked up. Re-quoting the error: |
I can see it in the feed: |
|
@vzarytovskii localky that works, but CI fails. See this commit, it was my first try, I don’t know how to solve that: 8d0df9a If you know how to make CI happy, I’d love to use that version. |
But this commit was 3 days ago. The package was only added today morning. Sorry for the confusion in the original message. |
|
@vzarytovskii thanks, I wasn't aware, indeed. Trying with stable |
|
@vzarytovskii, or @dsyme this very small PR is ready, can you review and/or merge? It unblocks other work. |
|
Thanks! Small change solves a lot of issues! |
Fixes #13686.
Unblocks: #13558
Related to: #13557 (part of the cause of that mess)
As explained in that issue, on certain platforms (in this case Windows), the very old (2018!) version of FsCheck, which is an alpha release (
3.0.0-alpha4to be exact) can raiseInvalidCastExceptionon invocation of theCheck.QuickThrowOnFailuremethods.This aims to solve that.
EDIT 2: going for
2.16.5, see discussion below, it was added to the available MS packages.Ready for review.
Overview of versions that exhibit
InvalidCastException:QuickThrowOnFailure* Not available in MS's nuget feed, not known whether it exhibits this issue, probably not
** Not available in MS's nuget feed, but I've locally checked that it solves the problem