-
Notifications
You must be signed in to change notification settings - Fork 156
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
Update plutus version #3030
Update plutus version #3030
Conversation
13ec291
to
a72e63a
Compare
FYI: kapralVV/Unique#10 |
28b96a8
to
aebbc88
Compare
so that running cabal from within the shell doesn't have to (which sometimes fails).
since plutus brings in version 1.4.1.0 but our dependency Unique is restricting it to 1.4.
which was wrong, but only started failing with the new plutus version
96a42c1
to
b581958
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll close this PR, since I've incorporated it into #2992
PlutusScript PlutusV1 bytes -> (not . null) (PV1.assertScriptWellFormed (transProtocolVersion pv) bytes :: Either ScriptDecodeError ()) | ||
PlutusScript PlutusV2 bytes -> (not . null) (PV2.assertScriptWellFormed (transProtocolVersion pv) bytes :: Either ScriptDecodeError ()) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is better to use specialized function isRight
instead of relying on Foldable instance for Either:
Closed it in favor of #2992 |
Nice, thank you for making something usable from two partial things! |
This is an attempt to isolate changes from #2992, to see what's causing the build error in plutus-core that
cabal build all
is attempting to build.Turns out the problem is happening because the
hashable
library was upgraded in plutus to 1.4.10, but in our project, thedependency on
Unique
is restricting the version ofhashable
to 1.4. It worked after adding theUnique:hashable
to allow-newer in cabal.project.Now that the dependency problems are solved, the remaining issue is adapting to the new code. I have tried (last commit) and might have partially succeeded, but I got stuck at theEDIT: Sorted this out nowValidatorHash
type that seems to have been removed from the API and ran out of time investigating what it was replaced with.I think it would be good to sort this PR out and merge it, and then resume the original prelude-removal one #2992, because the latter depends on this PR.