Skip to content

[stable19] fix possible leaking scope in WorkFlow - #22410

Merged
rullzer merged 2 commits into
stable19from
backport/22359/stable19
Aug 26, 2020
Merged

[stable19] fix possible leaking scope in WorkFlow#22410
rullzer merged 2 commits into
stable19from
backport/22359/stable19

Conversation

@backportbot-nextcloud

@backportbot-nextcloudbackportbot-nextcloudBot commented Aug 25, 2020

Copy link
Copy Markdown

⚠️ This backport had conflicts and is incomplete ⚠️ this is fine

backport of #22359

- a configured flow can be brought into consideration, despite its event
was not fired
- it could either run through
- or run into a RuntimeException and killing processing of valid flows
Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
@blizzzblizzz added the 3. to review Waiting for reviews label Aug 25, 2020
Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
@blizzzblizzz added 4. to release Ready to be released and/or waiting for tests to finish and removed 3. to review Waiting for reviews labels Aug 25, 2020
@rullzer
rullzer merged commit c9a1379 into stable19Aug 26, 2020
@rullzer
rullzer deleted the backport/22359/stable19 branch August 26, 2020 18:22
@rullzerrullzer mentioned this pull request Sep 4, 2020
@MorrisJobkeMorrisJobke mentioned this pull request Sep 9, 2020
@aignerataignerat changed the title [stable19] fix possible leaking scope in Flow[stable19] fix possible leaking scope in WorkFlowSep 16, 2020
@aignerat

Copy link
Copy Markdown
Member

adjusted headline, because Flow alone could be mistaken for loginFlow

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

4. to releaseReady to be released and/or waiting for tests to finishbugfeature: workflows

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants

@aignerat@ChristophWurst@blizzz@juliusknorr@rullzer