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.

Sign up for GitHub

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

Jump to bottom

[7.7.x] [RHPAM-2782] Error boundary event not working as expected with reusable subprocess node. #1612

Merged
merged 1 commit into from Mar 23, 2020
Merged

[7.7.x] [RHPAM-2782] Error boundary event not working as expected with reusable subprocess node. #1612

merged 1 commit into from Mar 23, 2020

Conversation

elguardian
Copy link
Member

error boundary compensation event is not thrown.

[RHPAM-2782] Error boundary event not working as expected with reusab…
8e15088 
…le subprocess node.

error boundary compensation event is not thrown.
@elguardian
Copy link
Member Author

cherry picked from 50a61c9

@elguardian elguardian changed the title [RHPAM-2782] Error boundary event not working as expected with reusable subprocess node. [7.7.x] [RHPAM-2782] Error boundary event not working as expected with reusable subprocess node. Mar 19, 2020
@sonarcloud
Copy link

sonarcloud bot commented Mar 19, 2020

SonarCloud Quality Gate failed.

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities (and Security Hotspot 0 Security Hotspots to review)
Code Smell A 0 Code Smells

2.9% 2.9% Coverage
0.0% 0.0% Duplication

gmunozfe
gmunozfe approved these changes Mar 19, 2020
View reviewed changes
Copy link
Member

@gmunozfe gmunozfe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me

@elguardian elguardian merged commit 520f67a into kiegroup:7.33.x Mar 23, 2020
@elguardian elguardian deleted the RHPAM-2382_7.7.x branch March 23, 2020 16:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@gmunozfe gmunozfe gmunozfe approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
2 participants
@elguardian @gmunozfe