fix(deps): bump maven-dependency-plugin from 3.1.2 to 3.2.0 #23
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
|
The following labels could not be found: |
dependabot
bot
force-pushed
the
dependabot/maven/org.apache.maven.plugins-maven-dependency-plugin-3.2.0
branch
from
b6ed01c to
1d9a0fd
Compare
dependabot
bot
force-pushed
the
dependabot/maven/org.apache.maven.plugins-maven-dependency-plugin-3.2.0
branch
2 times, most recently
from
1808d4a to
04e0cc7
Compare
dependabot
bot
force-pushed
the
dependabot/maven/org.apache.maven.plugins-maven-dependency-plugin-3.2.0
branch
from
04e0cc7 to
a6c2259
Compare
dependabot
bot
force-pushed
the
dependabot/maven/org.apache.maven.plugins-maven-dependency-plugin-3.2.0
branch
from
a6c2259 to
76bbe35
Compare
Bumps [maven-dependency-plugin](https://github.com/apache/maven-dependency-plugin) from 3.1.2 to 3.2.0. - [Release notes](https://github.com/apache/maven-dependency-plugin/releases) - [Commits](apache/maven-dependency-plugin@maven-dependency-plugin-3.1.2...maven-dependency-plugin-3.2.0) --- updated-dependencies: - dependency-name: org.apache.maven.plugins:maven-dependency-plugin dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
force-pushed
the
dependabot/maven/org.apache.maven.plugins-maven-dependency-plugin-3.2.0
branch
from
76bbe35 to
3f142e1
Compare
|
Superseded by #48. |
dependabot
bot
deleted the
dependabot/maven/org.apache.maven.plugins-maven-dependency-plugin-3.2.0
branch
aivinog1
pushed a commit
that referenced
this pull request
Apr 17, 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>
aivinog1
pushed a commit
that referenced
this pull request
Aug 30, 2022
10144: Add more abbreviations to the compact record logger r=saig0 a=korthout ## Description <!-- Please explain the changes you made here. --> While writing an engine test, I encountered some more unabbreviated record value types. This adds a few more abbreviations to create a compact, and easier-to-read record log. ### Before ``` -------- [Partition] ['C'ommand/'E'event/'R'ejection] [valueType] [intent] - #[position]->#[source record position] P[partitionId]K[key] - [summary of value] P9K999 - key; camunda#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 DPLY CREATE - #1-> -1 -1 - E PROC CREATED - #2->#1 K01 - process.xml -> "process" (version:1) E DPLY CREATED - #3->#1 K02 - process.xml E DPLY FULLY_DISTRIBUTED - #4->#1 K02 - C PROC_INST_CREATION CREATE - #5-> -1 -1 - new <process "process"> (default start) with variables: {x=variable} E VAR CREATED - #6->#5 K04 - x->"variable" in <process [K03]> C PROC_INST ACTIVATE - #7->#5 K03 - PROCESS "process" in <process "process"[K03]> E PROC_INST_CREATION CREATED - #8->#5 K05 - new <process "process"> (default start) with variables: {x=variable} E PROC_INST ACTIVATING - #9->#7 K03 - PROCESS "process" in <process "process"[K03]> E PROC_INST ACTIVATED - #10->#7 K03 - PROCESS "process" in <process "process"[K03]> C PROC_INST ACTIVATE - #11->#7 -1 - START_EVENT "startEv..b44a7b4" in <process "process"[K03]> C PROC_INST_MODIFICATION MODIFY - #12-> -1 K03 - ProcessInstanceModificationRecord {"processInstanceKey":2251799813685251,"terminateInstructions":[],"activateInstructions":[{"elementId":"B","ancestorScopeKey":-1,"variableInstructions":[{"elementId":"","variables":{"x":"updated"}}]}]} E PROC_INST ACTIVATING - #13->#11 K06 - START_EVENT "startEv..b44a7b4" in <process "process"[K03]> E PROC_INST ACTIVATED - #14->#11 K06 - START_EVENT "startEv..b44a7b4" in <process "process"[K03]> C PROC_INST COMPLETE - #15->#11 K06 - START_EVENT "startEv..b44a7b4" in <process "process"[K03]> E VAR UPDATED - #16->#12 K04 - x->"updated" in <process [K03]> C PROC_INST ACTIVATE - #17->#12 K07 - USER_TASK "B" in <process "process"[K03]> E PROC_INST_MODIFICATION MODIFIED - #18->#12 K03 - ProcessInstanceModificationRecord {"processInstanceKey":2251799813685251,"terminateInstructions":[],"activateInstructions":[{"elementId":"B","ancestorScopeKey":-1,"variableInstructions":[{"elementId":"","variables":{"x":"updated"}}]}]} E PROC_INST COMPLETING - #19->#15 K06 - START_EVENT "startEv..b44a7b4" in <process "process"[K03]> E PROC_INST COMPLETED - #20->#15 K06 - START_EVENT "startEv..b44a7b4" in <process "process"[K03]> E PROC_INST SEQ_FLOW_TAKEN - #21->#15 K08 - SEQUENCE_FLOW "sequenc..25183c6" in <process "process"[K03]> C PROC_INST ACTIVATE - #22->#15 K09 - USER_TASK "A" in <process "process"[K03]> E PROC_INST ACTIVATING - #23->#17 K07 - USER_TASK "B" in <process "process"[K03]> E JOB CREATED - #24->#17 K10 - K10 "io.camunda.zeebe:userTask" `@"B"[K07]` 1 retries, in <process "process"[K03]> (no vars) E PROC_INST ACTIVATED - #25->#17 K07 - USER_TASK "B" in <process "process"[K03]> E PROC_INST ACTIVATING - #26->#22 K09 - USER_TASK "A" in <process "process"[K03]> E JOB CREATED - #27->#22 K11 - K11 "io.camunda.zeebe:userTask" `@"A"[K09]` 1 retries, in <process "process"[K03]> (no vars) E PROC_INST ACTIVATED - #28->#22 K09 - USER_TASK "A" in <process "process"[K03]> ``` ### After ``` -------- [Partition] ['C'ommand/'E'event/'R'ejection] [valueType] [intent] - #[position]->#[source record position] P[partitionId]K[key] - [summary of value] P9K999 - key; camunda#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 DPLY CREATE - #1-> -1 -1 - E PROC CREATED - #2->#1 K01 - process.xml -> "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"> (default start) with variables: {x=variable} E VAR CREATED - #6->#5 K04 - x->"variable" in <process [K03]> C PI ACTIVATE - #7->#5 K03 - PROCESS "process" in <process "process"[K03]> E CREA CREATED - #8->#5 K05 - new <process "process"> (default start) with variables: {x=variable} E PI ACTIVATING - #9->#7 K03 - PROCESS "process" in <process "process"[K03]> E PI ACTIVATED - #10->#7 K03 - PROCESS "process" in <process "process"[K03]> C PI ACTIVATE - #11->#7 -1 - START_EVENT "startEv..ea8bb20" in <process "process"[K03]> C MOD MODIFY - #12-> -1 K03 - ProcessInstanceModificationRecord {"processInstanceKey":2251799813685251,"terminateInstructions":[],"activateInstructions":[{"elementId":"B","ancestorScopeKey":-1,"variableInstructions":[{"elementId":"","variables":{"x":"updated"}}]}]} E PI ACTIVATING - #13->#11 K06 - START_EVENT "startEv..ea8bb20" in <process "process"[K03]> E PI ACTIVATED - #14->#11 K06 - START_EVENT "startEv..ea8bb20" in <process "process"[K03]> C PI COMPLETE - #15->#11 K06 - START_EVENT "startEv..ea8bb20" in <process "process"[K03]> E VAR UPDATED - #16->#12 K04 - x->"updated" in <process [K03]> C PI ACTIVATE - #17->#12 K07 - USER_TASK "B" in <process "process"[K03]> E MOD MODIFIED - #18->#12 K03 - ProcessInstanceModificationRecord {"processInstanceKey":2251799813685251,"terminateInstructions":[],"activateInstructions":[{"elementId":"B","ancestorScopeKey":-1,"variableInstructions":[{"elementId":"","variables":{"x":"updated"}}]}]} E PI COMPLETING - #19->#15 K06 - START_EVENT "startEv..ea8bb20" in <process "process"[K03]> E PI COMPLETED - #20->#15 K06 - START_EVENT "startEv..ea8bb20" in <process "process"[K03]> E PI SEQ_FLOW_TAKEN - #21->#15 K08 - SEQUENCE_FLOW "sequenc..d3f792d" in <process "process"[K03]> C PI ACTIVATE - #22->#15 K09 - USER_TASK "A" in <process "process"[K03]> E PI ACTIVATING - #23->#17 K07 - USER_TASK "B" in <process "process"[K03]> E JOB CREATED - #24->#17 K10 - K10 "io.camunda.zeebe:userTask" `@"B"[K07]` 1 retries, in <process "process"[K03]> (no vars) E PI ACTIVATED - #25->#17 K07 - USER_TASK "B" in <process "process"[K03]> E PI ACTIVATING - #26->#22 K09 - USER_TASK "A" in <process "process"[K03]> E JOB CREATED - #27->#22 K11 - K11 "io.camunda.zeebe:userTask" `@"A"[K09]` 1 retries, in <process "process"[K03]> (no vars) E PI ACTIVATED - #28->#22 K09 - USER_TASK "A" in <process "process"[K03]> ``` ## Related issues <!-- Which issues are closed by this PR or are related --> while working on camunda#9663 Co-authored-by: Nico Korthout <nico.korthout@camunda.com>
aivinog1
pushed a commit
that referenced
this pull request
May 10, 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 camunda#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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bumps maven-dependency-plugin from 3.1.2 to 3.2.0.
Commits
367a682[maven-release-plugin] prepare release maven-dependency-plugin-3.2.00c7a2a8(doc) Dependabot disable Java 8 depsb0942a6[MDEP-739] Dependency Plugin go-offline doesn't respect artifact classifier205c1a7Disable merge commit button0190eeeMerge pull request #132 from apache/dependabot/maven/org.apache.maven.shared-...4211614[MDEP-749] scope "threshold" term to summarise classpath in/ex-clusion727c669[MDEP-749] improve include/exclude scope documentation26abf6cnext version will be 3.2.0807f24d[MDEP-749] document why excludeScope=test fails and what to do insteada0cba78rename doxiaSiteVersion property to doxiaSitetoolsVersionDependabot 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.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)