Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

deps(maven): bump version.log4j from 2.14.1 to 2.15.0 #31

Closed
wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Dec 10, 2021

Bumps version.log4j from 2.14.1 to 2.15.0.
Updates log4j-api from 2.14.1 to 2.15.0

Updates log4j-slf4j-impl from 2.14.1 to 2.15.0

Updates log4j-core from 2.14.1 to 2.15.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.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps `version.log4j` from 2.14.1 to 2.15.0.

Updates `log4j-api` from 2.14.1 to 2.15.0

Updates `log4j-slf4j-impl` from 2.14.1 to 2.15.0

Updates `log4j-core` from 2.14.1 to 2.15.0

---
updated-dependencies:
- dependency-name: org.apache.logging.log4j:log4j-api
  dependency-type: direct:development
  update-type: version-update:semver-minor
- dependency-name: org.apache.logging.log4j:log4j-slf4j-impl
  dependency-type: direct:development
  update-type: version-update:semver-minor
- dependency-name: org.apache.logging.log4j:log4j-core
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github
Copy link
Author

dependabot bot commented on behalf of github Dec 10, 2021

The following labels could not be found: dependencies.

@dependabot @github
Copy link
Author

dependabot bot commented on behalf of github Dec 19, 2021

Looks like these dependencies are up-to-date now, so this is no longer needed.

@dependabot dependabot bot closed this Dec 19, 2021
@dependabot dependabot bot deleted the dependabot/maven/version.log4j-2.15.0 branch December 19, 2021 10:58
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 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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants