Allow asynchronous tests to run on Task<'a> about fscheck HOT 8 CLOSED

Released in 3.0.0-rc1.

Also merged fscheck3 branch to master.

from fscheck.

tldr: make sure you have .NET 6 SDK installed (not 7), git checkout fscheck3, git pull, build.sh and you should be good.

It's known now, in that I see it too :)

Afaik this is due to some incompatibility between fake and installed MSBuild versions. This kind of thing unfortunately happens a lot. For a project like FsCheck which is essentially untouched, the amount of churn introduced by .NET, Fake, paket and all the build paraphernelia keeps surprising me. Excuse the rant.

In any case it's moot, because since you want to modify 3.0, you need to check out (and PR to) the fscheck3 branch. It is substantially different (i.e. includes the async support...whereas master doesn't).

For that, as well as the eternal prerelease state of 3.0, there is no one to blame but myself.

In any case I managed to update the fscheck3 branch to the latest paket and fake, and after pinning to .NET 6 that builds fine, also in CI: https://ci.appveyor.com/project/kurtschelfthout/fscheck/builds/47399941

Hope this helps!

from fscheck.

aside: While I'm a poster child of what not to do (I'm up to -rc.11 on some prominent public things, though most people can work out the story from looking at the previous full releases being ~2y ago!) I would plead to do as I say, not as I do and make fscheck3 become main, fork off a v2 maintenance badge, and then badge the nuget 3.0.0-rc.1

There's enough info out there (e.g. @pblasucci and Mark's blogs etc) for people with appetite/aptitude for FsCheck to move on past V2. My main reasoning is that there are enough quality of life/usability fixes that the OOTB experience is simply better. And if anyone wants to complain about that, simply put an Issue on GH stating that some docs are not yet in sync with V3 - ultimately if nobody has capacity to do a real complete release with all that might entail on paper, that should not be a blocker on doing the right thing.

from fscheck.

@bartelink yes, I think it's time for that. I'll probably just do 3.0.0 even. If the other plans ever materialize, there'll just have to be another version.

from fscheck.

Agree that a fix is desired. Actually not sure why it doesn’t already work!

Let me know if you get stuck, happy to assist (although it’s quite busy these days, so may take a couple days to reply)

from fscheck.

I've now cloned the repo and executed build.sh. It looks fairly promising, but does report this error:

Script reported an error:
-> BuildFailedException: Target 'Build' failed.
-> One or more errors occurred. (Unsupported log file format. Latest supported version is 14, the log file has version 16.)
-> NotSupportedException: Unsupported log file format. Latest supported version is 14, the log file has version 16.

Is this a know issue?

from fscheck.

All looks green now, thank you!

from fscheck.

When will this be released? :D

from fscheck.