Revision 39dbe1e3c744cc83a06f693fe4be7785d47a45f9 authored by Julien Tesson on 17 December 2019, 21:55:44 UTC, committed by Adrian Brink on 11 May 2020, 13:44:36 UTC
When an RPC resulted in an error that does not carry a json list of encoded error, it was producing an empty error trace for the error monad. Empty error trace should not happen.
1 parent ea08caf
tezos-crypto.opam
opam-version: "2.0"
maintainer: "contact@tezos.com"
authors: [ "Tezos devteam" ]
homepage: "https://www.tezos.com/"
bug-reports: "https://gitlab.com/tezos/tezos/issues"
dev-repo: "git+https://gitlab.com/tezos/tezos.git"
license: "MIT"
depends: [
"tezos-tooling" { with-test }
"dune" { >= "1.11" }
"tezos-stdlib"
"data-encoding" { = "0.2" }
"tezos-error-monad"
"tezos-rpc"
"tezos-clic"
"lwt"
"blake2"
"hacl"
"zarith"
"secp256k1-internal"
"uecc"
"alcotest" { with-test & = "0.8.5" }
]
build: [
["dune" "build" "-p" name "-j" jobs]
["dune" "runtest" "-p" name "-j" jobs] {with-test}
]
synopsis: "Tezos: library with all the cryptographic primitives used by Tezos"
Computing file changes ...
