mirror of
https://github.com/digital-asset/daml.git
synced 2024-09-20 01:07:18 +03:00
d6fc2bbb58
* participant-integration-api: `GrpcServerOwner` -> `GrpcServer.Owner`. Mostly so I can create a test class named `GrpcServerSpec`. * ports: Move the free port search from postgresql-testing. * participant-integration-api: Test the basics of GrpcServer. This uses the HelloService to make sure the server behaves normally. * ledger-api-client: Extract out channel configuration from LedgerClient. So we can test it independently of the LedgerClient itself. * ledger-api-client: Increase the default maximum inbound header size. Increased from 8 KB to 1 MB. * participant-integration-api: Reduce the maximum error message size. Truncate GRPC error descriptions to 256 KB. * participant-integration-api: Use `Port.Dynamic` instead of `FreePort`. In tests. * participant-integration-api: Explicit null checks when they're shorter. Co-authored-by: Stefano Baghino <43749967+stefanobaghino-da@users.noreply.github.com> * ledger-api-client: Reduce the max inbound message size back to 8 KB. And reduce the maximum size of an error description pushed out by the server accordingly. CHANGELOG_BEGIN - [Integration Kit] Truncate GPRC error messages at 4 KB. This ensures that we won't trigger a protocol error when sending errors to the client. CHANGELOG_END Co-authored-by: Stefano Baghino <43749967+stefanobaghino-da@users.noreply.github.com> |
||
---|---|---|
.. | ||
grpc-definitions | ||
perf-testing | ||
rs-grpc-akka | ||
rs-grpc-bridge | ||
rs-grpc-testing-utils | ||
sample-service | ||
scripts | ||
testing-utils | ||
.gitignore | ||
.sbtopts | ||
BUILD.bazel | ||
README.md |
Ledger-API
This is the API code for the ledger, which contains:
- gRPC API definitions
- Generated Scala bindings
- gRPC-RS bridge
- gRPC-Akka bridge
- Server API classes with validation
- Prototype Server
- Prototype Clients
- Scala
- Python
- Node.js
- Integration tests for all of the above
Documentation
The Ledger API Introduction contains introductory material as well as links to the protodocs reference documentation.
See the docs README for more about how to preview and publish documentation.