daml/triggers
Stephen Compall 4ca02e0eb6
upgrade doobie from 0.6.0 to 0.9.2 (#7618)
* set doobie version to 0.9.2 and rerun maven pin

* port extractor and some of JSON API

* repin maven

* use doobie's own builder compatibility where required

* use probably bad derivations to supply Blockers where transactEC was required

- The point of using Blocker instead of ExecutionContext seems to be to
  especially emphasize to API users that it isn't appropriate to use an
  ExecutionContext with ordinary behavior.  That is what we have done, which
  should probably change, but just compiling for now.

* fix fragment inspection test for internal restructuring

- This test depends on implementation details of Doobie, so naturally it must be
  altered when that runs.  Fortunately, it's been made easier by the changes
  in this upgrade.

* allow 256 blockers for navigator transaction blocker, like the global EC

* allow as many blockers as the pool size for trigger service

- The transactor shouldn't share ExecutionContext for transactions with the
  caller, so we set up a new one based on configured pool size.

* no changelog

CHANGELOG_BEGIN
CHANGELOG_END
2020-10-16 09:46:20 -04:00
..
daml allow updating user state from high-level trigger rule (#7674) 2020-10-14 14:51:25 +00:00
runner LF: add PackageInterface a lightweigh Package (#7577) 2020-10-13 12:41:22 +02:00
service upgrade doobie from 0.6.0 to 0.9.2 (#7618) 2020-10-16 09:46:20 -04:00
tests allow updating user state from high-level trigger rule (#7674) 2020-10-14 14:51:25 +00:00