digital-asset/daml
1
1
Fork 0
mirror of https://github.com/digital-asset/daml.git synced 2024-09-20 09:17:43 +03:00
Code Issues Projects Releases Wiki Activity
5ffe4a70c0
daml/extractor
History
Jost Berthold 5ffe4a70c0 extractor, navigator: --ledger-api-inbound-message-size-max option replaces 50MiB hard-coded [package size] limit (#1520) 
50MiB is no longer hard-coded on extractor, navigator input for sandbox
or any other server, permitting large packages; e.g. pass
--ledger-api-inbound-message-size-max 62914560 to extractor or navigator
to get a 60MiB limit.

Fixes #1463.

* extractor: --ledger-api-inbound-message-size-max option replaces 50MiB hard-coded [package size] limit

* navigator: make inbound buffer size configurable in navigator backend

* _actually_ change the max inbound size, scalafmt

* release note for --ledger-api-inbound-message-size-max option

* another release note for --ledger-api-inbound-message-size-max option
2019-06-05 12:09:11 -04:00
..
bin open-sourcing daml 2019-04-04 09:33:38 +01:00
src extractor, navigator: --ledger-api-inbound-message-size-max option replaces 50MiB hard-coded [package size] limit (#1520) 2019-06-05 12:09:11 -04:00
.gitignore open-sourcing daml 2019-04-04 09:33:38 +01:00
BUILD.bazel Improving logging, using scala-logging (#1518) 2019-06-04 20:02:59 +00:00
README.md open-sourcing daml 2019-04-04 09:33:38 +01:00
UNRELEASED.md open-sourcing daml 2019-04-04 09:33:38 +01:00

README.md

Extractor

Build

The code uses SBT as a build system

sbt compile

To run the tests

sbt test

Release

  1. Create a branch extractor-release-<major>-<minor>-<point> for the release. Check the file ledger-tools/extractor/version.sbt. For example, let's say the the current version of the project is 0.9.3-SNAPSHOT. You need to create a branch called extractor-release-0-9-3;
  2. Move the ## Unreleased section of ledger-tools/extractor/UNRELEASED.md to the new release version you have created in ledger-tools/extractor/CHANGELOG.md and commit to that branch. The message of the commit is not important as it will be discarded;
  3. Run sbt release . This will ask for the release version and the next version, and will create commit with the release version and next version, and also takes care about tagging;
  4. Push your branch and tag:
git push origin release/extractor/0.9.3    # check the tag that has been created, and push it
git push -u origin extractor-release-0-9-3 # push your branch
  1. Go to the release Jenkins job Enter the tag you published and run the job.
  2. Create a Pull Request from your branch, have it reviewed and merged. After it's done, you can delete the branch.