fix possible leaking scope in Flow#22359
Merged
nickvergessen merged 1 commit intomasterfrom Aug 25, 2020
Merged
Conversation
Member
Author
|
/backport to stable19 |
Member
Author
|
/backport to stable18 |
juliusknorr
approved these changes
Aug 24, 2020
Member
|
php-cs says no ;) |
Member
Author
it always does the first few pushes |
- 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>
6eb56fc to
28c0eea
Compare
ChristophWurst
approved these changes
Aug 24, 2020
|
🤖 beep boop beep 🤖 Here are the logs for the failed build: Status of 32247: failuremysql5.6-php7.2Show full logacceptance-app-files
Show full logacceptance-header
Show full log |
This was referenced Aug 25, 2020
This file contains hidden or 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
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.
How to reproduce:
curl -i -X POST -H "Content-Type: application/json" -d '{"foo": "bar"}' https://my.nc.srv/ocs/v2.php/apps/flow_webhooks/api/v1/hook/1234567890, see personal config)The reason is that the
getFlows()method does not take the event into account that is being currently processed.This draft implements an API extension to
IRuleMatcherto fix this, and also to backport it. Since it is not a component that is implemented by third parties, but initialized by ourselves. Existing methods are not touched. Thus it is safe to backport. Usual operation implementation do not need to worry about this as it dealt with in the Manager code.IComplexOperationsmight need to use that method, if it possible to react and configure different events. However, they are picked up by themselves (and they do event listening themselves), so even in these cases it is extremely unlikely that this needs to be used.