Changes for v2.10.2 release #4553
Merged
Conversation
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
1. Mitigate / avoid race when calling add_file() before tailer has been initialized 2. Fix a bug with failing to dispatch a trigger due to code using invalid trigger type reference (it uses trigger ref instead of trigger type ref)
reference and not trigger type reference is passed to it.
value is a valid UUID4.
indefinetly if connection to RabbitMQ cannot be established. Also add errback which logs an actual error when trying to re-establish a connection.
NOTE: Security vulnerability doesn't affect our code because we already use yaml.safe_load everywhere, but it's still good to update.
pyyaml to old version.
…s match help text
mode / log level is not enabled.
since this can potentially result in too many unique metrics.
when sys.prefix is relative (e.g. when calling ./tools/launchdev.sh script outside of tools directory or similar).
(https://blog.hackeriet.no/cve-2019-6690-python-gnupg-vulnerability/). NOTE: This security vulnerability doesn't affect us because we only this library in an isolated scenario (encrypting debug tarball without using a passphrase).
handle unicode (utf-8) data. Previously we didn't correctly convert string to bytes before padding data which resulted in incorrectly padded data (incorrect length) so the actual encryption step failed. Thanks to @dswebbthg for reporting this issue. Resolves #4513.
"pack" attribute to the execution context.
If we don't add that, {{ config_context }} won't work correctly for
default parameter values for action executions which are scheduled as
part of an Orquesta workflow.
sure also also add "pack" attribute to LiveActionDB.context attribute inside "create_request" function. We already add it in RunnerContainer.dispatch(), but that's not the best place since some tests don't call that method so that value won't be present.
execution context.
default parameter values works for executions scheduled via Orquesta workflow.
Add retries in the scheduler handler to temporarily handle DB connection failures. Refactor how threads exit for the process to return proper code.
entrypoint exceptions. NOTE: Tests currently fail because issue hasn't been fully fixed yet.
Regenerated the sample st2 config with the scheduler retry configuration options.
Add a unit test to cover failure in the handler cleanup. This should signal the run method to also pause and exit the scheduler handler process.
Add unit tests to cover the retries in the run and cleanup in the scheduler handler.
Add or move the parsing of test configs to the top of affected test modules and make sure the scheduler default config options do not conflict with test configs.
Update orquesta to version 0.4 to include fixes on CPU usage, interpretation of quoted strings and boolean values in shorthand publish, with items variable with the word "in" that conflict with syntax, and other docs updates.
they get large enough. Also use larger poll interval.
them under a correct section.
Member
Author
|
NOTE: Circle CI packages build will keep failing until this is merged in v2.10 branch and a new build is triggered using st2-packages v2.10 branch. The reason for that is that this PR is using st2-packages master where cloudslang and old winexe based runners have been removed (but they are still present in v2.10 branch). |
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.
Included changes (https://github.com/StackStorm/st2/pulls?q=is%3Apr+is%3Aclosed+milestone%3A2.10.2):