I can poll/lock and complete tasks #29
Assignees
Comments
ThorbenLindhauer
added a commit
that referenced
this issue
Jul 21, 2016
- refactors create, complete, and lock task request handlers to use the BufferReader/BufferWriter abstraction level related to #29
ThorbenLindhauer
added a commit
that referenced
this issue
Jul 25, 2016
bors bot
added a commit
that referenced
this issue
Sep 6, 2018
1275: build(deps): bump appassembler-maven-plugin from 1.10 to 2.0.0 r=menski a=dependabot[bot] Bumps [appassembler-maven-plugin](https://github.com/mojohaus/appassembler) from 1.10 to 2.0.0. <details> <summary>Commits</summary> - [`1ec8420`](mojohaus/appassembler@1ec8420) [maven-release-plugin] prepare release appassembler-2.0.0 - [`8eb2fec`](mojohaus/appassembler@8eb2fec) revert back to mojo-parent-39 to get good build again. - [`e098be8`](mojohaus/appassembler@e098be8) Fixed appveyor.yml using Maven 3.2.5 to - [`ed174bb`](mojohaus/appassembler@ed174bb) Fixed [#43](https://github-redirect.dependabot.com/mojohaus/appassembler/issues/43) - [`fff8d9f`](mojohaus/appassembler@fff8d9f) Based on Maven 3.3.X we can only use JDK 7 and JDK 8 - [`264c1a5`](mojohaus/appassembler@264c1a5) Added appveyor build on windows. - [`64ebaa6`](mojohaus/appassembler@64ebaa6) Fixed [#40](https://github-redirect.dependabot.com/mojohaus/appassembler/issues/40) - [`b70ba04`](mojohaus/appassembler@b70ba04) Fixed [#32](https://github-redirect.dependabot.com/mojohaus/appassembler/issues/32) - [`b3c3bcd`](mojohaus/appassembler@b3c3bcd) Fixed [#29](https://github-redirect.dependabot.com/mojohaus/appassembler/issues/29) - [`e99ba84`](mojohaus/appassembler@e99ba84) Fixed [#35](https://github-redirect.dependabot.com/mojohaus/appassembler/issues/35) - Additional commits viewable in [compare view](mojohaus/appassembler@appassembler-1.10...appassembler-2.0.0) </details> <br /> [](https://dependabot.com/compatibility-score.html?dependency-name=org.codehaus.mojo:appassembler-maven-plugin&package-manager=maven&previous-version=1.10&new-version=2.0.0) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. --- **Note:** This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 PRs we'll remove that limit. You can always request more updates by clicking `Bump now` in your [Dependabot dashboard](https://app.dependabot.com). <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot ignore this [patch|minor|major] version` will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired) Finally, you can contact us by mentioning @dependabot. </details> Co-authored-by: dependabot[bot] <support@dependabot.com>
bors bot
added a commit
that referenced
this issue
Sep 9, 2018
1287: build(deps): bump maven-checkstyle-plugin from 2.17 to 3.0.0 r=menski a=dependabot[bot] Bumps [maven-checkstyle-plugin](https://github.com/apache/maven-checkstyle-plugin) from 2.17 to 3.0.0. <details> <summary>Commits</summary> - [`7803030`](apache/maven-checkstyle-plugin@7803030) [maven-release-plugin] prepare release maven-checkstyle-plugin-3.0.0 - [`eb11ed6`](apache/maven-checkstyle-plugin@eb11ed6) Can't generate checkstyle report with same version, due to usage of replaced ... - [`71b2675`](apache/maven-checkstyle-plugin@71b2675) Make project Java 9 proof - [`18881c5`](apache/maven-checkstyle-plugin@18881c5) moved to git - [`17c66b8`](apache/maven-checkstyle-plugin@17c66b8) Revert fix and IT changes for MCHECKSTYLE-314 - [`c4a93f9`](apache/maven-checkstyle-plugin@c4a93f9) [MCHECKSTYLE-338] Add support for 'omitIgnoredModules' - [`898a9db`](apache/maven-checkstyle-plugin@898a9db) Fixing Javadoc issues when building with JDK 8: - [`5f9eb5f`](apache/maven-checkstyle-plugin@5f9eb5f) [MCHECKSTYLE-337] checkstyle:check only supports xml output format, but the d... - [`7abd8b6`](apache/maven-checkstyle-plugin@7abd8b6) [MCHECKSTYLE-338] Add support for 'omitIgnoredModules' - [`22c075c`](apache/maven-checkstyle-plugin@22c075c) [MCHECKSTYLE-220] Debug shows unnecessary stacktrace with java.net.MalformedU... - Additional commits viewable in [compare view](apache/maven-checkstyle-plugin@maven-checkstyle-plugin-2.17...maven-checkstyle-plugin-3.0.0) </details> <br /> [](https://dependabot.com/compatibility-score.html?dependency-name=org.apache.maven.plugins:maven-checkstyle-plugin&package-manager=maven&previous-version=2.17&new-version=3.0.0) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. --- **Note:** This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 PRs we'll remove that limit. You can always request more updates by clicking `Bump now` in your [Dependabot dashboard](https://app.dependabot.com). <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot ignore this [patch|minor|major] version` will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired) Finally, you can contact us by mentioning @dependabot. </details> 1292: build(deps): bump jackson-bom from 2.9.5 to 2.9.6 r=menski a=dependabot[bot] Bumps [jackson-bom](https://github.com/FasterXML/jackson-bom) from 2.9.5 to 2.9.6. <details> <summary>Commits</summary> - [`993b189`](FasterXML/jackson-bom@993b189) [maven-release-plugin] prepare release jackson-bom-2.9.6 - [`02f27dc`](FasterXML/jackson-bom@02f27dc) prepare for 2.9.6 - [`4107503`](FasterXML/jackson-bom@4107503) try to upgrade 2.9 to latest working parent poms - [`06e0e36`](FasterXML/jackson-bom@06e0e36) update jackson-parent dep - [`673b494`](FasterXML/jackson-bom@673b494) disable lint for 2.9 - [`bc7bb04`](FasterXML/jackson-bom@bc7bb04) [maven-release-plugin] prepare for next development iteration - See full diff in [compare view](FasterXML/jackson-bom@jackson-bom-2.9.5...jackson-bom-2.9.6) </details> <br /> [](https://dependabot.com/compatibility-score.html?dependency-name=com.fasterxml.jackson:jackson-bom&package-manager=maven&previous-version=2.9.5&new-version=2.9.6) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. --- **Note:** This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 PRs we'll remove that limit. You can always request more updates by clicking `Bump now` in your [Dependabot dashboard](https://app.dependabot.com). <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot ignore this [patch|minor|major] version` will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired) Finally, you can contact us by mentioning @dependabot. </details> 1293: build(deps): bump maven-plugin-plugin from 3.2 to 3.5.2 r=menski a=dependabot[bot] Bumps [maven-plugin-plugin](https://github.com/apache/maven-plugin-tools) from 3.2 to 3.5.2. <details> <summary>Commits</summary> - [`4c4fdf4`](apache/maven-plugin-tools@4c4fdf4) [maven-release-plugin] prepare release maven-plugin-tools-3.5.2 - [`73edece`](apache/maven-plugin-tools@73edece) [MPLUGIN-334] - Upgrade mave-surefire/failsafe-plugin 2.21.0 - [`95c8d08`](apache/maven-plugin-tools@95c8d08) site configuration cleanup - [`ad56a64`](apache/maven-plugin-tools@ad56a64) [MPLUGIN-333] upgraded parent to 31 - [`ef44d09`](apache/maven-plugin-tools@ef44d09) [MPLUGIN-338] upgrade plexus-archiver to 3.4.1 (Java 6) - [`3ddfa0c`](apache/maven-plugin-tools@3ddfa0c) [MNGSITE-328] use sha1 checksum instead of md5 - [`dbbb127`](apache/maven-plugin-tools@dbbb127) Merge pull request [#13](https://github-redirect.dependabot.com/apache/maven-plugin-tools/issues/13) from aldaris/mplugin-335 - [`5d192bd`](apache/maven-plugin-tools@5d192bd) [MPLUGIN-335] - Fix build and tests - [`7dfedcb`](apache/maven-plugin-tools@7dfedcb) Merge pull request [#9](https://github-redirect.dependabot.com/apache/maven-plugin-tools/issues/9) from don-vip/master - [`85b3702`](apache/maven-plugin-tools@85b3702) [MPLUGIN-335] - Support JDK 10 for plugin generation - Additional commits viewable in [compare view](apache/maven-plugin-tools@maven-plugin-tools-3.2...maven-plugin-tools-3.5.2) </details> <br /> [](https://dependabot.com/compatibility-score.html?dependency-name=org.apache.maven.plugins:maven-plugin-plugin&package-manager=maven&previous-version=3.2&new-version=3.5.2) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. --- **Note:** This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 PRs we'll remove that limit. You can always request more updates by clicking `Bump now` in your [Dependabot dashboard](https://app.dependabot.com). <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot ignore this [patch|minor|major] version` will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired) Finally, you can contact us by mentioning @dependabot. </details> 1294: build(deps): bump os-maven-plugin from 1.5.0.Final to 1.6.0 r=menski a=dependabot[bot] Bumps [os-maven-plugin](https://github.com/trustin/os-maven-plugin) from 1.5.0.Final to 1.6.0. <details> <summary>Release notes</summary> *Sourced from [os-maven-plugin's releases](https://github.com/trustin/os-maven-plugin/releases).* > ## os-maven-plugin-1.6.0 > - Added support for MIPS and MIPSEL 32/64-bit architecture > - `mips_32` - if the value is one of: `mips`, `mips32` > - `mips_64` - if the value is `mips64` > - `mipsel_32` - if the value is one of: `mipsel`, `mips32el` > - `mipsel_64` - if the value is `mips64el` > - Added support for PPCLE 32-bit architecture > - `ppcle_32` - if the value is one of: `ppcle`, `ppc32le` > - Added support for IA64N and IA64W architecture > - `itanium_32` - if the value is `ia64n` > - `itanium_64` - if the value is one of: `ia64`, `ia64w` (new), `itanium64` > - Fixed classpath conflicts due to outdated Guava version in transitive dependencies ([#29](https://github-redirect.dependabot.com/trustin/os-maven-plugin/issues/29)) > - Fixed incorrect prerequisite ([#21](https://github-redirect.dependabot.com/trustin/os-maven-plugin/issues/21)) > - Overall code clean-up and dependency updates </details> <details> <summary>Commits</summary> - [`cd54571`](trustin/os-maven-plugin@cd54571) [maven-release-plugin] prepare release os-maven-plugin-1.6.0 - [`fa82fef`](trustin/os-maven-plugin@fa82fef) Use `[**Inject**](https://github.com/Inject)` annotation instead of `[**Requirement**](https://github.com/Requirement)` / Change dict to Map<Strin... - [`59fd029`](trustin/os-maven-plugin@59fd029) Support MIPS(EL) 32/64 and PPCLE 32 - [`72e3f62`](trustin/os-maven-plugin@72e3f62) Understand IA64N and IA64W - [`cd6d803`](trustin/os-maven-plugin@cd6d803) Add automated test + TravisCI settings - [`cfe63a0`](trustin/os-maven-plugin@cfe63a0) Overall clean-up - [`4027186`](trustin/os-maven-plugin@4027186) Update dependencies - [`2905705`](trustin/os-maven-plugin@2905705) Fix incorrect plugin prerequisites - [`66e9aab`](trustin/os-maven-plugin@66e9aab) Use Maven wrapper - [`9b06010`](trustin/os-maven-plugin@9b06010) Update of version in readme ([#28](https://github-redirect.dependabot.com/trustin/os-maven-plugin/issues/28)) - Additional commits viewable in [compare view](trustin/os-maven-plugin@os-maven-plugin-1.5.0.Final...os-maven-plugin-1.6.0) </details> <br /> [](https://dependabot.com/compatibility-score.html?dependency-name=kr.motd.maven:os-maven-plugin&package-manager=maven&previous-version=1.5.0.Final&new-version=1.6.0) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. --- **Note:** This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 PRs we'll remove that limit. You can always request more updates by clicking `Bump now` in your [Dependabot dashboard](https://app.dependabot.com). <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot ignore this [patch|minor|major] version` will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired) Finally, you can contact us by mentioning @dependabot. </details> 1295: build(deps): bump version.sbe from 1.5.6 to 1.8.7 r=menski a=dependabot[bot] Bumps `version.sbe` from 1.5.6 to 1.8.7. Updates `sbe-tool` from 1.5.6 to 1.8.7 <details> <summary>Release notes</summary> *Sourced from [sbe-tool's releases](https://github.com/real-logic/simple-binary-encoding/releases).* > ## 1.8.7 > * Use find package to discover java executable when building C++ codecs tests. > * Use pointers in golang codecs to improve efficiency. [PR [#578](https://github-redirect.dependabot.com/real-logic/simple-binary-encoding/issues/578)](https://github-redirect.dependabot.com/real-logic/simple-binary-encoding/pull/578). > * Upgrade to Checkstyle 8.12. > * Upgrade to Mockito 2.21.0. > * Upgrade to Agrona 0.9.23. > > Java binaries can be found [here...](http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22uk.co.real-logic%22%20sbe) > > ## 1.8.6 > * Provide the ability to query for an empty bit set in Java and C++ codecs for simplicity. [PR [#575](https://github-redirect.dependabot.com/real-logic/simple-binary-encoding/issues/575)](https://github-redirect.dependabot.com/real-logic/simple-binary-encoding/pull/575). > * Upgrade to Mockito 2.20.1. > * Upgrade to Gradle 4.9. > * Upgrade to Agrona 0.9.22. > > Java binaries can be found [here...](http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22uk.co.real-logic%22%20sbe) > > ## 1.8.5 > * Invalid Java generated for codec with an extension string field that is appendable. [PR [#574](https://github-redirect.dependabot.com/real-logic/simple-binary-encoding/issues/574)](https://github-redirect.dependabot.com/real-logic/simple-binary-encoding/pull/574). > > Java binaries can be found [here...](http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22uk.co.real-logic%22%20sbe) > > ## 1.8.4 > * Upgrade to Mockito 2.19.1. > * Upgrade to Agrona 0.9.21. > > Java binaries can be found [here...](http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22uk.co.real-logic%22%20sbe) > > ## 1.8.3 > * Regenerate IR Codecs to quote strings when printing. > * Upgrade to Checkstyle 8.11. > * Upgrade to Gradle 4.8.1. > * Upgrade to Agrona 0.9.20. > > Java binaries can be found [here...](http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22uk.co.real-logic%22%20sbe) > > ## 1.8.2 > * Update to latest CME fix binary market template for testing. > * Allow, with warning, `numInGroup` type to use `uint32` for repeating groups. > * Add support to C# codecs for constant presence enums. > * Fix issue with loss of IR data on encoding the IR for constant presence enums. [Issue [#560](https://github-redirect.dependabot.com/real-logic/simple-binary-encoding/issues/560)](https://github-redirect.dependabot.com/real-logic/simple-binary-encoding/issues/560). > * Complete functionality for `JsonPrinter` so that an SBE message can be transformed to JSON for debugging. [Issue [#560](https://github-redirect.dependabot.com/real-logic/simple-binary-encoding/issues/560)](https://github-redirect.dependabot.com/real-logic/simple-binary-encoding/issues/560). > * Remove debugging output from C++ IR decoder. [Issue [#559](https://github-redirect.dependabot.com/real-logic/simple-binary-encoding/issues/559)](https://github-redirect.dependabot.com/real-logic/simple-binary-encoding/issues/559). > * Make `HEADER_SIZE` a public constant in Java codecs for repeating groups. > * Allow Java decoders to use an `Appendable` for ASCII strings. [PR [#557](https://github-redirect.dependabot.com/real-logic/simple-binary-encoding/issues/557)](https://github-redirect.dependabot.com/real-logic/simple-binary-encoding/pull/557). > * Upgrade to Mockito 2.19.0. > * Upgrade to Checkstyle 8.10.1. > * Upgrade to Agrona 0.9.19. > * Upgrade to GSON 2.8.5. > ></table> ... (truncated) </details> <details> <summary>Commits</summary> - [`40b53ab`](real-logic/simple-binary-encoding@40b53ab) 1.8.7 released. - [`e941ade`](real-logic/simple-binary-encoding@e941ade) [Java] Upgrade to Checkstyle 8.12. - [`efb04b4`](real-logic/simple-binary-encoding@efb04b4) [Java] Upgrade to Mockito 2.21.0. - [`7b3420e`](real-logic/simple-binary-encoding@7b3420e) [C++]: use find package info for building IR codecs. - [`fe5a25d`](real-logic/simple-binary-encoding@fe5a25d) Merge pull request [#578](https://github-redirect.dependabot.com/real-logic/simple-binary-encoding/issues/578) from lkramer/optimize_functions - [`abc4913`](real-logic/simple-binary-encoding@abc4913) golang: Use pointer receiver where appropriate - [`3d4290e`](real-logic/simple-binary-encoding@3d4290e) Update README.md - [`feba135`](real-logic/simple-binary-encoding@feba135) post release bump - [`e38cedc`](real-logic/simple-binary-encoding@e38cedc) 1.8.6 released. - [`df76964`](real-logic/simple-binary-encoding@df76964) [Java] Fix warnings in build script when trying to find cargo. - Additional commits viewable in [compare view](real-logic/simple-binary-encoding@1.5.6...1.8.7) </details> <br /> Updates `sbe-all` from 1.5.6 to 1.8.7 <details> <summary>Release notes</summary> *Sourced from [sbe-all's releases](https://github.com/real-logic/simple-binary-encoding/releases).* > ## 1.8.7 > * Use find package to discover java executable when building C++ codecs tests. > * Use pointers in golang codecs to improve efficiency. [PR [#578](https://github-redirect.dependabot.com/real-logic/simple-binary-encoding/issues/578)](https://github-redirect.dependabot.com/real-logic/simple-binary-encoding/pull/578). > * Upgrade to Checkstyle 8.12. > * Upgrade to Mockito 2.21.0. > * Upgrade to Agrona 0.9.23. > > Java binaries can be found [here...](http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22uk.co.real-logic%22%20sbe) > > ## 1.8.6 > * Provide the ability to query for an empty bit set in Java and C++ codecs for simplicity. [PR [#575](https://github-redirect.dependabot.com/real-logic/simple-binary-encoding/issues/575)](https://github-redirect.dependabot.com/real-logic/simple-binary-encoding/pull/575). > * Upgrade to Mockito 2.20.1. > * Upgrade to Gradle 4.9. > * Upgrade to Agrona 0.9.22. > > Java binaries can be found [here...](http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22uk.co.real-logic%22%20sbe) > > ## 1.8.5 > * Invalid Java generated for codec with an extension string field that is appendable. [PR [#574](https://github-redirect.dependabot.com/real-logic/simple-binary-encoding/issues/574)](https://github-redirect.dependabot.com/real-logic/simple-binary-encoding/pull/574). > > Java binaries can be found [here...](http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22uk.co.real-logic%22%20sbe) > > ## 1.8.4 > * Upgrade to Mockito 2.19.1. > * Upgrade to Agrona 0.9.21. > > Java binaries can be found [here...](http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22uk.co.real-logic%22%20sbe) > > ## 1.8.3 > * Regenerate IR Codecs to quote strings when printing. > * Upgrade to Checkstyle 8.11. > * Upgrade to Gradle 4.8.1. > * Upgrade to Agrona 0.9.20. > > Java binaries can be found [here...](http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22uk.co.real-logic%22%20sbe) > > ## 1.8.2 > * Update to latest CME fix binary market template for testing. > * Allow, with warning, `numInGroup` type to use `uint32` for repeating groups. > * Add support to C# codecs for constant presence enums. > * Fix issue with loss of IR data on encoding the IR for constant presence enums. [Issue [#560](https://github-redirect.dependabot.com/real-logic/simple-binary-encoding/issues/560)](https://github-redirect.dependabot.com/real-logic/simple-binary-encoding/issues/560). > * Complete functionality for `JsonPrinter` so that an SBE message can be transformed to JSON for debugging. [Issue [#560](https://github-redirect.dependabot.com/real-logic/simple-binary-encoding/issues/560)](https://github-redirect.dependabot.com/real-logic/simple-binary-encoding/issues/560). > * Remove debugging output from C++ IR decoder. [Issue [#559](https://github-redirect.dependabot.com/real-logic/simple-binary-encoding/issues/559)](https://github-redirect.dependabot.com/real-logic/simple-binary-encoding/issues/559). > * Make `HEADER_SIZE` a public constant in Java codecs for repeating groups. > * Allow Java decoders to use an `Appendable` for ASCII strings. [PR [#557](https://github-redirect.dependabot.com/real-logic/simple-binary-encoding/issues/557)](https://github-redirect.dependabot.com/real-logic/simple-binary-encoding/pull/557). > * Upgrade to Mockito 2.19.0. > * Upgrade to Checkstyle 8.10.1. > * Upgrade to Agrona 0.9.19. > * Upgrade to GSON 2.8.5. > ></table> ... (truncated) </details> <details> <summary>Commits</summary> - [`40b53ab`](real-logic/simple-binary-encoding@40b53ab) 1.8.7 released. - [`e941ade`](real-logic/simple-binary-encoding@e941ade) [Java] Upgrade to Checkstyle 8.12. - [`efb04b4`](real-logic/simple-binary-encoding@efb04b4) [Java] Upgrade to Mockito 2.21.0. - [`7b3420e`](real-logic/simple-binary-encoding@7b3420e) [C++]: use find package info for building IR codecs. - [`fe5a25d`](real-logic/simple-binary-encoding@fe5a25d) Merge pull request [#578](https://github-redirect.dependabot.com/real-logic/simple-binary-encoding/issues/578) from lkramer/optimize_functions - [`abc4913`](real-logic/simple-binary-encoding@abc4913) golang: Use pointer receiver where appropriate - [`3d4290e`](real-logic/simple-binary-encoding@3d4290e) Update README.md - [`feba135`](real-logic/simple-binary-encoding@feba135) post release bump - [`e38cedc`](real-logic/simple-binary-encoding@e38cedc) 1.8.6 released. - [`df76964`](real-logic/simple-binary-encoding@df76964) [Java] Fix warnings in build script when trying to find cargo. - Additional commits viewable in [compare view](real-logic/simple-binary-encoding@1.5.6...1.8.7) </details> <br /> Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. --- **Note:** This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 PRs we'll remove that limit. You can always request more updates by clicking `Bump now` in your [Dependabot dashboard](https://app.dependabot.com). <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot ignore this [patch|minor|major] version` will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired) Finally, you can contact us by mentioning @dependabot. </details> 1296: build(deps): bump slf4j-api from 1.7.23 to 1.7.25 r=menski a=dependabot[bot] Bumps [slf4j-api](https://github.com/qos-ch/slf4j) from 1.7.23 to 1.7.25. <details> <summary>Commits</summary> - [`a81440e`](qos-ch/slf4j@a81440e) fix date issue in news.html - [`c2a7cca`](qos-ch/slf4j@c2a7cca) prepare release 1.7.25 - [`a848912`](qos-ch/slf4j@a848912) change serialVersionUID since internals changed - [`2fc2dc1`](qos-ch/slf4j@2fc2dc1) Merge pull request [#173](https://github-redirect.dependabot.com/qos-ch/slf4j/issues/173) from hazendaz/master - [`60eb95e`](qos-ch/slf4j@60eb95e) [license] Update copyright year to 2017 - [`2f06933`](qos-ch/slf4j@2f06933) use SLF4J formatter - [`97472ca`](qos-ch/slf4j@97472ca) fix deprecation issues - [`4a8c166`](qos-ch/slf4j@4a8c166) fix SLF4J-395 - [`509c344`](qos-ch/slf4j@509c344) fix SLF4J-394 - [`898e222`](qos-ch/slf4j@898e222) type fix - Additional commits viewable in [compare view](qos-ch/slf4j@v_1.7.23...v_1.7.25) </details> <br /> [](https://dependabot.com/compatibility-score.html?dependency-name=org.slf4j:slf4j-api&package-manager=maven&previous-version=1.7.23&new-version=1.7.25) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. --- **Note:** This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 PRs we'll remove that limit. You can always request more updates by clicking `Bump now` in your [Dependabot dashboard](https://app.dependabot.com). <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot ignore this [patch|minor|major] version` will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired) Finally, you can contact us by mentioning @dependabot. </details> Co-authored-by: dependabot[bot] <support@dependabot.com> Co-authored-by: Sebastian Menski <sebastian@menski.org>
ghost
pushed a commit
that referenced
this issue
Mar 31, 2021
6701: Improve compact log for rejections and error records r=saig0 a=saig0 ## Description * log rejections in the same way as commands and events * provide more data for root causing a rejection (e.g. value type, intent, position, etc.) * add summarize for error records * shrink the terms with `INSTANCE` -> `INST` and `VARIABLE` -> `VAR` * remove the term `ELEMENT` completely because it is too verbose and redundant (every activate/activating/activated etc. belongs to elements) <details><summary>Current output</summary> <p> ``` 07:43:02.648 [] INFO io.zeebe.test - Compact log representation: -------- ['C'ommand/'E'event/'R'ejection] [valueType] [intent] - #[position]->#[source record position] P[partitionId]K[key] - [summary of value] P9K999 - key; #999 - record position; "ID" element/process id; @"elementid"/[P9K999] - element with ID and key Keys are decomposed into partition id and per partition key (e.g. 2251799813685253 -> P1K005). If single partition, the partition is omitted. Long IDs are shortened (e.g. 'startEvent_5d56488e-0570-416c-ba2d-36d2a3acea78' -> 'star..acea78' -------- C DEPLOYMENT CREATE - #1-> -1 -1 - process.xml E PROC CREATED - #2->#1 K01 - process.xml->"process" (version:1) E DEPLOYMENT CREATED - #3->#1 K02 - process.xml E DEPLOYMENT FULLY_DISTR - #4->#1 K02 - C MSG PUBLISH - #5-> -1 -1 - "msg1" correlationKey: order-123 (no vars) E MSG PUBLISHED - #6->#5 K03 - "msg1" correlationKey: order-123 (no vars) C PROC_INSTANCE_CREATION CREATE - #7-> -1 -1 - new <process "process"> with variables: {key=order-123} E VARIABLE CREATED - #8->#7 K05 - key->"order-123" in <process [K04]> E PROC_INSTANCE ELMNT_ACTIVATING - #9->#7 K04 - PROCESS "process" in <process "process"[K04]> E PROC_INSTANCE_CREATION CREATED - #10->#7 K06 - new <process "process"> with variables: {key=order-123} E PROC_INSTANCE ELMNT_ACTIVATED - #11->#9 K04 - PROCESS "process" in <process "process"[K04]> E PROC_INSTANCE ELMNT_ACTIVATING - #12->#11 K07 - START_EVENT "startEv..323d1cb" in <process "process"[K04]> E PROC_INSTANCE ELMNT_ACTIVATED - #13->#12 K07 - START_EVENT "startEv..323d1cb" in <process "process"[K04]> E PROC_INSTANCE ELMNT_COMPLETING - #14->#13 K07 - START_EVENT "startEv..323d1cb" in <process "process"[K04]> E PROC_INSTANCE ELMNT_COMPLETED - #15->#14 K07 - START_EVENT "startEv..323d1cb" in <process "process"[K04]> E PROC_INSTANCE SEQ_FLOW_TAKEN - #16->#15 K08 - SEQUENCE_FLOW "sequenc..8cfbcaa" in <process "process"[K04]> C PROC_INSTANCE ACTIVATE_ELMNT - #17->#16 K09 - RECEIVE_TASK "task" in <process "process"[K04]> E PROC_INSTANCE ELMNT_ACTIVATING - #18->#17 K09 - RECEIVE_TASK "task" in <process "process"[K04]> E PROC_MSG_SUB CREATING - #19->#17 -1 - "taskMsg" (inter.) correlationKey: order-123 @[K09] in <process "process"[K04]> (no vars) E PROC_MSG_SUB CREATING - #20->#17 -1 - "msg2" (inter.) correlationKey: order-123 @[K09] in <process "process"[K04]> (no vars) E PROC_MSG_SUB CREATING - #21->#17 -1 - "msg1" (inter.) correlationKey: order-123 @[K09] in <process "process"[K04]> (no vars) E PROC_INSTANCE ELMNT_ACTIVATED - #22->#17 K09 - RECEIVE_TASK "task" in <process "process"[K04]> C MSG_SUB CREATE - #23-> -1 -1 - "taskMsg" (inter.) correlationKey: order-123 @[K09] in <process "process"[K04]> (no vars) C MSG_SUB CREATE - #24-> -1 -1 - "msg2" (inter.) correlationKey: order-123 @[K09] in <process "process"[K04]> (no vars) C MSG_SUB CREATE - #25-> -1 -1 - "msg1" (inter.) correlationKey: order-123 @[K09] in <process "process"[K04]> (no vars) E MSG_SUB CREATED - #26->#23 K10 - "taskMsg" (inter.) correlationKey: order-123 @[K09] in <process "process"[K04]> (no vars) C PROC_MSG_SUB CREATE - #27-> -1 -1 - "taskMsg" (inter.) @[K09] in <process ?> (no vars) E MSG_SUB CREATED - #28->#24 K11 - "msg2" (inter.) correlationKey: order-123 @[K09] in <process "process"[K04]> (no vars) C PROC_MSG_SUB CREATE - #29-> -1 -1 - "msg2" (inter.) @[K09] in <process ?> (no vars) E MSG_SUB CREATED - #30->#25 K12 - "msg1" (inter.) correlationKey: order-123 @[K09] in <process "process"[K04]> (no vars) E MSG_SUB CORRELATING - #31->#25 K12 - "msg1" (inter.) correlationKey: order-123 @[K09] in <process "process"[K04]> (no vars) C PROC_MSG_SUB CORRELATE - #32-> -1 -1 - "msg1" (inter.) correlationKey: order-123 @[K09] in <process "process"[K04]> (no vars) E PROC_MSG_SUB CREATED - #33->#27 -1 - "taskMsg" (inter.) @[K09] in <process ?> (no vars) E PROC_MSG_SUB CREATED - #34->#29 -1 - "msg2" (inter.) @[K09] in <process ?> (no vars) E PROC_MSG_SUB CORRELATED - #35->#32 -1 - "msg1" (inter.) correlationKey: order-123 @[K09] in <process "process"[K04]> (no vars) C PROC_INSTANCE ACTIVATE_ELMNT - #36->#32 -1 - RECEIVE_TASK "task" in <process "process"[K04]> C MSG_SUB CORRELATE - #37-> -1 -1 - "msg1" (inter.) @[K09] in <process "process"[K04]> (no vars) PROCESSING_ERROR Expected to process event 'TypedEventImpl{metadata=RecordMetadata{recordType=COMMAND, intentValue=255, intent=ACTIVATE_ELEMENT, requestStreamId=-2147483648, requestId=-1, protocolVersion=3, valueType=PROCESS_INSTANCE, rejectionType=NULL_VAL, rejectionReason=, brokerVersion=1.0.0}, value={"bpmnProcessId":"process","version":1,"processDefinitionKey":2251799813685249,"processInstanceKey":2251799813685252,"elementId":"task","flowScopeKey":2251799813685252,"bpmnElementType":"RECEIVE_TASK","parentProcessInstanceKey":-1,"parentElementInstanceKey":-1}}' without errors, but exception occurred with message 'Not expected to have an active sequence flow count lower then zero!'.#38->#36 -1 - E ERROR CREATED - #39->#36 -1 - ErrorRecord {"stacktrace":"java.lang.IllegalStateException: Not expected to have an active sequence flow count lower then zero!\n\tat io.zeebe.engine.state.instance.ElementInstance.decrementActiveSequenceFlows(ElementInstance.java:168)\n\tat io.zeebe.engine.state.appliers.ProcessInstanceElementActivatingApplier.decrementActiveSequenceFlow(ProcessInstanceElementActivatingApplier.java:108)\n\tat io.zeebe.engine.state.appliers.ProcessInstanceElementActivatingApplier.applyState(ProcessInstanceElementActivatingApplier.java:62)\n\tat io.zeebe.engine.state.appliers.ProcessInstanceElementActivatingApplier.applyState(ProcessInstanceElementActivatingApplier.java:26)\n\tat io.zeebe.engine.state.appliers.EventAppliers.applyState(EventAppliers.java:217)\n\tat io.zeebe.engine.processing.streamprocessor.writers.EventApplyingStateWriter.appendFollowUpEvent(EventApplyingStateWriter.java:49)\n\tat io.zeebe.engine.processing.streamprocessor.writers.EventApplyingStateWriter.appendFollowUpEvent(EventApplyingStateWriter.java:39)\n\tat io.zeebe.engine.processing.bpmn.behavior.BpmnStateTransitionBehavior.transitionTo(BpmnStateTransitionBehavior.java:216)\n\tat io.zeebe.engine.processing.bpmn.behavior.BpmnStateTransitionBehavior.transitionToActivating(BpmnStateTransitionBehavior.java:103)\n\tat io.zeebe.engine.processing.bpmn.BpmnStreamProcessor.processEvent(BpmnStreamProcessor.java:146)\n\tat io.zeebe.engine.processing.bpmn.BpmnStreamProcessor.processRecord(BpmnStreamProcessor.java:134)\n\tat io.zeebe.engine.processing.streamprocessor.TypedRecordProcessor.processRecord(TypedRecordProcessor.java:54)\n\tat io.zeebe.engine.processing.streamprocessor.ProcessingStateMachine.lambda$processInTransaction$3(ProcessingStateMachine.java:296)\n\tat io.zeebe.db.impl.rocksdb.transaction.ZeebeTransaction.run(ZeebeTransaction.java:84)\n\tat io.zeebe.engine.processing.streamprocessor.ProcessingStateMachine.processInTransaction(ProcessingStateMachine.java:286)\n\tat io.zeebe.engine.processing.streamprocessor.ProcessingStateMachine.processEvent(ProcessingStateMachine.java:254)\n\tat io.zeebe.engine.processing.streamprocessor.ProcessingStateMachine.tryToReadNextEvent(ProcessingStateMachine.java:219)\n\tat io.zeebe.engine.processing.streamprocessor.ProcessingStateMachine.readNextEvent(ProcessingStateMachine.java:210)\n\tat io.zeebe.util.sched.ActorJob.invoke(ActorJob.java:73)\n\tat io.zeebe.util.sched.ActorJob.execute(ActorJob.java:39)\n\tat io.zeebe.util.sched.ActorTask.execute(ActorTask.java:122)\n\tat io.zeebe.util.sched.ActorThread.executeCurrentTask(ActorThread.java:94)\n\tat io.zeebe.util.sched.ActorThread.doWork(ActorThread.java:78)\n\tat io.zeebe.util.sched.ActorThread.run(ActorThread.java:191)\n","processInstanceKey":2251799813685252,"exceptionMessage":"Not expected to have an active sequence flow count lower then zero!","errorEventPosition":36} -------- Decomposed keys (for debugging): -1 <-> -1 K01 <-> 2251799813685249 K02 <-> 2251799813685250 K03 <-> 2251799813685251 K04 <-> 2251799813685252 K05 <-> 2251799813685253 K06 <-> 2251799813685254 K07 <-> 2251799813685255 K08 <-> 2251799813685256 K09 <-> 2251799813685257 K10 <-> 2251799813685258 K11 <-> 2251799813685259 K12 <-> 2251799813685260 ``` <p> </details> <details><summary>Output with the changes</summary> <p> ``` 07:38:03.861 [] INFO io.zeebe.test - Compact log representation: -------- ['C'ommand/'E'event/'R'ejection] [valueType] [intent] - #[position]->#[source record position] P[partitionId]K[key] - [summary of value] P9K999 - key; #999 - record position; "ID" element/process id; @"elementid"/[P9K999] - element with ID and key Keys are decomposed into partition id and per partition key (e.g. 2251799813685253 -> P1K005). If single partition, the partition is omitted. Long IDs are shortened (e.g. 'startEvent_5d56488e-0570-416c-ba2d-36d2a3acea78' -> 'star..acea78' -------- C DEPLOYMENT CREATE - #1-> -1 -1 - process.xml E PROC CREATED - #2->#1 K01 - process.xml->"process" (version:1) E DEPLOYMENT CREATED - #3->#1 K02 - process.xml E DEPLOYMENT FULLY_DISTR - #4->#1 K02 - C MSG PUBLISH - #5-> -1 -1 - "msg1" correlationKey: order-123 (no vars) E MSG PUBLISHED - #6->#5 K03 - "msg1" correlationKey: order-123 (no vars) C PROC_INST_CREATION CREATE - #7-> -1 -1 - new <process "process"> with variables: {key=order-123} E VAR CREATED - #8->#7 K05 - key->"order-123" in <process [K04]> E PROC_INST ACTIVATING - #9->#7 K04 - PROCESS "process" in <process "process"[K04]> E PROC_INST_CREATION CREATED - #10->#7 K06 - new <process "process"> with variables: {key=order-123} E PROC_INST ACTIVATED - #11->#9 K04 - PROCESS "process" in <process "process"[K04]> E PROC_INST ACTIVATING - #12->#11 K07 - START_EVENT "startEv..b233ada" in <process "process"[K04]> E PROC_INST ACTIVATED - #13->#12 K07 - START_EVENT "startEv..b233ada" in <process "process"[K04]> E PROC_INST COMPLETING - #14->#13 K07 - START_EVENT "startEv..b233ada" in <process "process"[K04]> E PROC_INST COMPLETED - #15->#14 K07 - START_EVENT "startEv..b233ada" in <process "process"[K04]> E PROC_INST SEQ_FLOW_TAKEN - #16->#15 K08 - SEQUENCE_FLOW "sequenc..fb40cc7" in <process "process"[K04]> C PROC_INST ACTIVATE - #17->#16 K09 - RECEIVE_TASK "task" in <process "process"[K04]> E PROC_INST ACTIVATING - #18->#17 K09 - RECEIVE_TASK "task" in <process "process"[K04]> E PROC_MSG_SUB CREATING - #19->#17 -1 - "taskMsg" (inter.) correlationKey: order-123 @[K09] in <process "process"[K04]> (no vars) E PROC_MSG_SUB CREATING - #20->#17 -1 - "msg2" (inter.) correlationKey: order-123 @[K09] in <process "process"[K04]> (no vars) E PROC_MSG_SUB CREATING - #21->#17 -1 - "msg1" (inter.) correlationKey: order-123 @[K09] in <process "process"[K04]> (no vars) E PROC_INST ACTIVATED - #22->#17 K09 - RECEIVE_TASK "task" in <process "process"[K04]> C MSG_SUB CREATE - #23-> -1 -1 - "taskMsg" (inter.) correlationKey: order-123 @[K09] in <process "process"[K04]> (no vars) C MSG_SUB CREATE - #24-> -1 -1 - "msg2" (inter.) correlationKey: order-123 @[K09] in <process "process"[K04]> (no vars) C MSG_SUB CREATE - #25-> -1 -1 - "msg1" (inter.) correlationKey: order-123 @[K09] in <process "process"[K04]> (no vars) E MSG_SUB CREATED - #26->#23 K10 - "taskMsg" (inter.) correlationKey: order-123 @[K09] in <process "process"[K04]> (no vars) C PROC_MSG_SUB CREATE - #27-> -1 -1 - "taskMsg" (inter.) @[K09] in <process ?[K04]> (no vars) E MSG_SUB CREATED - #28->#24 K11 - "msg2" (inter.) correlationKey: order-123 @[K09] in <process "process"[K04]> (no vars) C PROC_MSG_SUB CREATE - #29-> -1 -1 - "msg2" (inter.) @[K09] in <process ?[K04]> (no vars) E MSG_SUB CREATED - #30->#25 K12 - "msg1" (inter.) correlationKey: order-123 @[K09] in <process "process"[K04]> (no vars) E MSG_SUB CORRELATING - #31->#25 K12 - "msg1" (inter.) correlationKey: order-123 @[K09] in <process "process"[K04]> (no vars) C PROC_MSG_SUB CORRELATE - #32-> -1 -1 - "msg1" (inter.) correlationKey: order-123 @[K09] in <process "process"[K04]> (no vars) E PROC_MSG_SUB CREATED - #33->#27 -1 - "taskMsg" (inter.) @[K09] in <process ?[K04]> (no vars) E PROC_MSG_SUB CREATED - #34->#29 -1 - "msg2" (inter.) @[K09] in <process ?[K04]> (no vars) E PROC_MSG_SUB CORRELATED - #35->#32 -1 - "msg1" (inter.) correlationKey: order-123 @[K09] in <process "process"[K04]> (no vars) C PROC_INST ACTIVATE - #36->#32 -1 - RECEIVE_TASK "task" in <process "process"[K04]> C MSG_SUB CORRELATE - #37-> -1 -1 - "msg1" (inter.) @[K09] in <process "process"[K04]> (no vars) R PROC_INST ACTIVATE - #38->#36 -1 - RECEIVE_TASK "task" in <process "process"[K04]> !PROCESSING_ERROR (Expected to process event 'TypedEventImpl{metadata=RecordMetadata{recordType=COMMAND, intentValue=..) E ERROR CREATED - #39->#36 -1 - "Not expected to have an active sequence flow count lower then zero!" in <process ?[K04]> (java.lang.IllegalStateException: Not expected to have an active sequence flow count lower then zer..) -------- Decomposed keys (for debugging): -1 <-> -1 K01 <-> 2251799813685249 K02 <-> 2251799813685250 K03 <-> 2251799813685251 K04 <-> 2251799813685252 K05 <-> 2251799813685253 K06 <-> 2251799813685254 K07 <-> 2251799813685255 K08 <-> 2251799813685256 K09 <-> 2251799813685257 K10 <-> 2251799813685258 K11 <-> 2251799813685259 K12 <-> 2251799813685260 ``` <p> </details> _The most changes happened on the last two records._ ## Related issues ## Definition of Done _Not all items need to be done depending on the issue and the pull request._ Code changes: * [ ] The changes are backwards compatibility with previous versions * [ ] If it fixes a bug then PRs are created to [backport](https://github.com/zeebe-io/zeebe/compare/stable/0.24...develop?expand=1&template=backport_template.md&title=[Backport%200.24]) the fix to the last two minor versions. You can trigger a backport by assigning labels (e.g. `backport stable/0.25`) to the PR, in case that fails you need to create backports manually. Testing: * [ ] There are unit/integration tests that verify all acceptance criterias of the issue * [ ] New tests are written to ensure backwards compatibility with further versions * [ ] The behavior is tested manually * [ ] The change has been verified by a QA run * [ ] The impact of the changes is verified by a benchmark Documentation: * [ ] The documentation is updated (e.g. BPMN reference, configuration, examples, get-started guides, etc.) * [ ] New content is added to the [release announcement](https://drive.google.com/drive/u/0/folders/1DTIeswnEEq-NggJ25rm2BsDjcCQpDape) Co-authored-by: Philipp Ossler <philipp.ossler@gmail.com>
9 tasks
ghost
pushed a commit
that referenced
this issue
Feb 28, 2022
8843: test(test-util): summarize DMN records r=saig0 a=saig0 ## Description * extend the compact logger that is mainly used to print the records when a test failed * display DMN resources of deployment record * summarize decision requirements and decision records * summarize decision evaluation records Before: ``` C DEPLOYMENT CREATE - #1-> -1 -1 - E DECISION_REQUIREMENTS CREATED - #2->#1 K01 - DecisionRequirementsRecord {"resource":"PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4KPG...","decisionRequirementsKey":2251799813685249,"decisionRequirementsId":"force_users","resourceName":"/dmn/drg-force-user.dmn","checksum":"4CVEZphbvJhEHAY8+PoEbw==","decisionRequirementsName":"force_users","decisionRequirementsVersion":1,"namespace":"http://camunda.org/schema/1.0/dmn","duplicate":false} E DECISION CREATED - #3->#1 K02 - DecisionRecord {"version":1,"decisionKey":2251799813685250,"decisionId":"jedi_or_sith","decisionName":"Jedi or Sith","decisionRequirementsKey":2251799813685249,"decisionRequirementsId":"force_users","duplicate":false} E DECISION CREATED - #4->#1 K03 - DecisionRecord {"version":1,"decisionKey":2251799813685251,"decisionId":"force_user","decisionName":"Which force user?","decisionRequirementsKey":2251799813685249,"decisionRequirementsId":"force_users","duplicate":false} E PROC CREATED - #5->#1 K04 - process.xml -> "process" (version:1) E DEPLOYMENT CREATED - #6->#1 K05 - process.xml E DEPLOYMENT FULLY_DISTR - #7->#1 K05 - ... E DECISION_EVALUATION EVALUATED - #24->#22 K13 - DecisionEvaluationRecord {"decisionKey":2251799813685251,"decisionId":"force_user","decisionName":"Which force user?","decisionRequirementsKey":2251799813685249,"decisionRequirementsId":"force_users","processDefinitionKey":2251799813685252,"bpmnProcessId":"process","processInstanceKey":2251799813685254,"elementId":"task","evaluatedDecisions":[{"decisionKey":2251799813685250,"decisionId":"jedi_or_sith","decisionName":"Jedi or Sith","evaluatedInputs":[{"inputId":"Input_1","inputName":"Lightsaber color","inputValue":"\"blue\""}],"matchedRules":[{"evaluatedOutputs":[{"outputId":"Output_1","outputName":"jedi_or_sith","outputValue":"\"Jedi\""}],"ruleId":"DecisionRule_0zumznl","ruleIndex":1}],"decisionType":"DECISION_TABLE","decisionOutput":"\"Jedi\""},{"decisionKey":2251799813685251,"decisionId":"force_user","decisionName":"Which force user?","evaluatedInputs":[{"inputId":"InputClause_0qnqj25","inputName":"Jedi or Sith","inputValue":"\"Jedi\""},{"inputId":"InputClause_0k64hys","inputName":"Body height","inputValue":"182"}],"matchedRules":[{"evaluatedOutputs":[{"outputId":"OutputClause_0hhe1yo","outputName":"force_user","outputValue":"\"Obi-Wan Kenobi\""}],"ruleId":"DecisionRule_0uin2hk","ruleIndex":2}],"decisionType":"DECISION_TABLE","decisionOutput":"\"Obi-Wan Kenobi\""}],"decisionOutput":"\"Obi-Wan Kenobi\"","elementInstanceKey":2251799813685260,"decisionVersion":1,"evaluationFailureMessage":"","failedDecisionId":""} ``` After: ``` C DEPLOYMENT CREATE - #1-> -1 -1 - E DRG CREATED - #2->#1 K01 - /dmn/drg-force-user.dmn -> "force_users" (version:1) E DECISION CREATED - #3->#1 K02 - "jedi_or_sith" (version:1) of <drg "force_users"[K01]> E DECISION CREATED - #4->#1 K03 - "force_user" (version:1) of <drg "force_users"[K01]> E PROC CREATED - #5->#1 K04 - process.xml -> "process" (version:1) E DEPLOYMENT CREATED - #6->#1 K05 - process.xml, /dmn/drg-force-user.dmn E DEPLOYMENT FULLY_DISTR - #7->#1 K05 - ... E DECISION_EVAL EVALUATED - #24->#22 K13 - "Obi-Wan Kenobi" of <decision "force_user"[K03]> in <process "process"[K06]> @"task"[K12] ``` <details> <summary>Full test output</summary> <pre> C DEPLOYMENT CREATE - #1-> -1 -1 - E DRG CREATED - #2->#1 K01 - /dmn/drg-force-user.dmn -> "force_users" (version:1) E DECISION CREATED - #3->#1 K02 - "jedi_or_sith" (version:1) of <drg "force_users"[K01]> E DECISION CREATED - #4->#1 K03 - "force_user" (version:1) of <drg "force_users"[K01]> E PROC CREATED - #5->#1 K04 - process.xml -> "process" (version:1) E DEPLOYMENT CREATED - #6->#1 K05 - process.xml, /dmn/drg-force-user.dmn E DEPLOYMENT FULLY_DISTR - #7->#1 K05 - C PROC_INST_CREATION CREATE - #8-> -1 -1 - new <process "process"> with variables: {lightsaberColor=blue, height=182} E VAR CREATED - #9->#8 K07 - height->182 in <process [K06]> E VAR CREATED - #10->#8 K08 - lightsaberColor->"blue" in <process [K06]> C PROC_INST ACTIVATE - #11->#8 K06 - PROCESS "process" in <process "process"[K06]> E PROC_INST_CREATION CREATED - #12->#8 K09 - new <process "process"> with variables: {lightsaberColor=blue, height=182} E PROC_INST ACTIVATING - #13->#11 K06 - PROCESS "process" in <process "process"[K06]> E PROC_INST ACTIVATED - #14->#11 K06 - PROCESS "process" in <process "process"[K06]> C PROC_INST ACTIVATE - #15->#11 -1 - START_EVENT "startEv..29dbbd9" in <process "process"[K06]> E PROC_INST ACTIVATING - #16->#15 K10 - START_EVENT "startEv..29dbbd9" in <process "process"[K06]> E PROC_INST ACTIVATED - #17->#15 K10 - START_EVENT "startEv..29dbbd9" in <process "process"[K06]> C PROC_INST COMPLETE - #18->#15 K10 - START_EVENT "startEv..29dbbd9" in <process "process"[K06]> E PROC_INST COMPLETING - #19->#18 K10 - START_EVENT "startEv..29dbbd9" in <process "process"[K06]> E PROC_INST COMPLETED - #20->#18 K10 - START_EVENT "startEv..29dbbd9" in <process "process"[K06]> E PROC_INST SEQ_FLOW_TAKEN - #21->#18 K11 - SEQUENCE_FLOW "sequenc..272f6f6" in <process "process"[K06]> C PROC_INST ACTIVATE - #22->#18 K12 - BUSINESS_RULE_TASK "task" in <process "process"[K06]> E PROC_INST ACTIVATING - #23->#22 K12 - BUSINESS_RULE_TASK "task" in <process "process"[K06]> E DECISION_EVAL EVALUATED - #24->#22 K13 - "Obi-Wan Kenobi" of <decision "force_user"[K03]> in <process "process"[K06]> @"task"[K12] E PROC_EVNT TRIGGERING - #25->#22 K14 - @"task"[K12] in <process K04[K06]> with variables: {result=Obi-Wan Kenobi} E PROC_INST ACTIVATED - #26->#22 K12 - BUSINESS_RULE_TASK "task" in <process "process"[K06]> C PROC_INST COMPLETE - #27->#22 K12 - BUSINESS_RULE_TASK "task" in <process "process"[K06]> E PROC_INST COMPLETING - #28->#27 K12 - BUSINESS_RULE_TASK "task" in <process "process"[K06]> E VAR CREATED - #29->#27 K15 - result->"Obi-Wan Kenobi" in <process [K06]> E PROC_INST COMPLETED - #30->#27 K12 - BUSINESS_RULE_TASK "task" in <process "process"[K06]> C PROC_INST COMPLETE - #31->#27 K06 - PROCESS "process" in <process "process"[K06]> E PROC_INST COMPLETING - #32->#31 K06 - PROCESS "process" in <process "process"[K06]> E PROC_INST COMPLETED - #33->#31 K06 - PROCESS "process" in <process "process"[K06]> </pre> </details> ## Related issues None. Co-authored-by: Philipp Ossler <philipp.ossler@gmail.com>
zeebe-bors-camunda bot
added a commit
that referenced
this issue
May 9, 2023
12697: Fix flaky `EmbeddedSubProcessTest` r=koevskinikola a=remcowesterhoud ## Description <!-- Please explain the changes you made here. --> The test was flaky because it could occur that the messages got published before the subscription were opened. As the messages have no TTL this means they were not getting correlated, as expected. Log of a failing run: ``` C DPLY CREATE - #1-> -1 -1 - E PROC CREATED - #2->#1 K01 - process.xml -> "process..process" (version:1) E DPLY CREATED - #3->#1 K02 - process.xml E DPLY FULLY_DISTRIBUTED - #4->#1 K02 - C CREA CREATE - #5-> -1 -1 - new <process "process..process"> with variables: {correlationKey=correlationKey} E VAR CREATED - #6->#5 K04 - correlationKey->"correlationKey" in <process [K03]> C PI ACTIVATE - #7->#5 K03 - PROCESS "process..process" in <process "process..process"[K03]> E CREA CREATED - #8->#5 K05 - new <process "process..process"> with variables: {correlationKey=correlationKey} E PI ACTIVATING - #9->#7 K03 - PROCESS "process..process" in <process "process..process"[K03]> E PI ACTIVATED - #10->#7 K03 - PROCESS "process..process" in <process "process..process"[K03]> C PI ACTIVATE - #11->#7 -1 - START_EVENT "startEv..8897acc" in <process "process..process"[K03]> E PI ACTIVATING - #12->#11 K06 - START_EVENT "startEv..8897acc" in <process "process..process"[K03]> E PI ACTIVATED - #13->#11 K06 - START_EVENT "startEv..8897acc" in <process "process..process"[K03]> C PI COMPLETE - #14->#11 K06 - START_EVENT "startEv..8897acc" in <process "process..process"[K03]> E PI COMPLETING - #15->#14 K06 - START_EVENT "startEv..8897acc" in <process "process..process"[K03]> E PROC_MSG_SUB CREATING - #16->#14 K07 - "eventSubProcess" (inter.) correlationKey: correlationKey `@[K03]` in <process "process..process"[K03]> (no vars) E PI COMPLETED - #17->#14 K06 - START_EVENT "startEv..8897acc" in <process "process..process"[K03]> E PI SEQ_FLOW_TAKEN - #18->#14 K08 - SEQUENCE_FLOW "sequenc..b7cb1a6" in <process "process..process"[K03]> C PI ACTIVATE - #19->#14 K09 - SUB_PROCESS "subProcess" in <process "process..process"[K03]> E PI ACTIVATING - #20->#19 K09 - SUB_PROCESS "subProcess" in <process "process..process"[K03]> E PI ACTIVATED - #21->#19 K09 - SUB_PROCESS "subProcess" in <process "process..process"[K03]> C PI ACTIVATE - #22->#19 -1 - START_EVENT "startEv..8b12a7c" in <process "process..process"[K03]> E PI ACTIVATING - #23->#22 K10 - START_EVENT "startEv..8b12a7c" in <process "process..process"[K03]> E PI ACTIVATED - #24->#22 K10 - START_EVENT "startEv..8b12a7c" in <process "process..process"[K03]> C PI COMPLETE - #25->#22 K10 - START_EVENT "startEv..8b12a7c" in <process "process..process"[K03]> E PI COMPLETING - #26->#25 K10 - START_EVENT "startEv..8b12a7c" in <process "process..process"[K03]> E PROC_MSG_SUB CREATING - #27->#25 K11 - "boundary" (inter.) correlationKey: correlationKey `@[K09]` in <process "process..process"[K03]> (no vars) E PI COMPLETED - #28->#25 K10 - START_EVENT "startEv..8b12a7c" in <process "process..process"[K03]> E PI SEQ_FLOW_TAKEN - #29->#25 K12 - SEQUENCE_FLOW "sequenc..8c72ad0" in <process "process..process"[K03]> C PI ACTIVATE - #30->#25 K13 - SERVICE_TASK "task" in <process "process..process"[K03]> E PI ACTIVATING - #31->#30 K13 - SERVICE_TASK "task" in <process "process..process"[K03]> E JOB CREATED - #32->#30 K14 - K14 "task" `@"task"[K13]` 3 retries, in <process "process..process"[K03]> (no vars) E PI ACTIVATED - #33->#30 K13 - SERVICE_TASK "task" in <process "process..process"[K03]> C MSG PUBLISH - #34-> -1 K01 - "boundary" correlationKey: correlationKey (no vars) C MSG PUBLISH - #35-> -1 K01 - "eventSubProcess" correlationKey: correlationKey (no vars) E MSG PUBLISHED - #36->#34 K15 - "boundary" correlationKey: correlationKey (no vars) E MSG EXPIRED - #37->#34 K15 - "boundary" correlationKey: correlationKey (no vars) E MSG PUBLISHED - #38->#35 K16 - "eventSubProcess" correlationKey: correlationKey (no vars) E MSG EXPIRED - #39->#35 K16 - "eventSubProcess" correlationKey: correlationKey (no vars) C MSG_SUB CREATE - #40-> -1 -1 - "eventSubProcess" (inter.) correlationKey: correlationKey `@[K03]` in <process "process..process"[K03]> (no vars) C MSG_SUB CREATE - #41-> -1 -1 - "boundary" (inter.) correlationKey: correlationKey `@[K09]` in <process "process..process"[K03]> (no vars) E MSG_SUB CREATED - #42->#40 K17 - "eventSubProcess" (inter.) correlationKey: correlationKey `@[K03]` in <process "process..process"[K03]> (no vars) C PROC_MSG_SUB CREATE - #43-> -1 -1 - "eventSubProcess" (inter.) `@[K03]` in <process ?[K03]> (no vars) E MSG_SUB CREATED - #44->#41 K18 - "boundary" (inter.) correlationKey: correlationKey `@[K09]` in <process "process..process"[K03]> (no vars) C PROC_MSG_SUB CREATE - #45-> -1 -1 - "boundary" (inter.) `@[K09]` in <process ?[K03]> (no vars) E PROC_MSG_SUB CREATED - #46->#43 K07 - "eventSubProcess" (inter.) correlationKey: correlationKey `@[K03]` in <process "process..process"[K03]> (no vars) E PROC_MSG_SUB CREATED - #47->#45 K11 - "boundary" (inter.) correlationKey: correlationKey `@[K09]` in <process "process..process"[K03]> (no vars) ``` The test isn't really flaky on 8.2+ anymore. This is a result of batch processing that was introduced recently. However, I believe it's still good to fix it on all versions and keep the test aligned across versions. ## Related issues <!-- Which issues are closed by this PR or are related --> closes #11844 Co-authored-by: Remco Westerhoud <remco@westerhoud.nl>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Clean up and test the code we have right now.
Subtask of #4
The text was updated successfully, but these errors were encountered: