-
-
Notifications
You must be signed in to change notification settings - Fork 782
Fix a bug with trigger payload validation in linux.FileWatchSensor sensor #4491
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
Merged
Merged
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
5caddb7
Update affected tests.
Kami cffe8f2
Use remove_windows_and_cloudslang_runner st2-packages branch.
Kami 61745f3
Merge branch 'master' of github.com:StackStorm/st2
Kami b6d11da
Fix two issues in FileWatchSensor:
Kami c8f45a8
Fix validate_trigger_payload() method so it also works if a trigger
Kami 2e113d1
Revert "Use remove_windows_and_cloudslang_runner st2-packages branch."
Kami a78c317
Update inaccurate comment.
Kami 2390a5a
Determine if the trigger_type_ref is actually a trigger ref based if the
Kami 290e7f1
Add a test case for it.
Kami 5840c7e
Merge branch 'master' into file_watch_payload_validation_fix
Kami File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is an edge case in logshipper library.
If a trigger is added and
add_fileis called before the tailer is initialized, an exception will be thrown and the sensor will die / crash (this can happen becauseadd_triggermethod is called asynchronously and it could be called beforerun()and tailer fully initialized).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
:(
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, it's not ideal.
I could make it 100% deterministic by shuffling around the code (set
initializedor similar variable to True insiderun()and only proceed insideadd_handlerwhen that variable is True).I think that's too complicated though since sleep seems to work just as fine (and it's one line of code).
It also only affects a single sensor right now so there is no point in handling that inside sensor container / base sensor class code.