You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Added config - kopf.config.WorkersConfig - class attributes based options to control async workers. So user can just import it before all other kopf modules and change values to required. Maybe not the best decision, but any.
So now can be configured number of next types of workers: queue processing, object patching, event creation.
Blocking synchronous operations such as event creation, changed objects patching, are now asynchronous (i guess).
Added kopf.config.EventsConfig.events_loglevel to control what types of logs should trigger event sending - INFO/WARNING/ERROR/CRITICAL
Existing tests updated for new async functions.
E2E tests required to test performance(how fast large number of new/changed objects can be processed). Such tests would prove efficiency of kopf concurrency.
Types of Changes
New feature (non-breaking change which adds functionality)
Bug fix (non-breaking change which fixes an issue)
Configuration change
Refactor/improvements
Tasks
List of tasks you will do to complete the PR
Documentation
E2E performance tests
Review?
Review
List of tasks the reviewer must do to review the PR
As a side-note: I tried to check why Travis CI pipeline is not triggered for this PR, and for this PR only — it works for other PRs & contributors. Travis CI says "Abuse detected" without any additional explanation.
I will try to contact Travis CI support to clarify what is the actual reason.
My only assumption for now is that this is a PR from the "master" branch of a fork to the "master" branch of the upstream — maybe Travis does not like it. This is the only "unusual" thing in this PR. Just guessing.
The text was updated successfully, but these errors were encountered:
Trying to fix blocking operations, such as objects patching, event posting, etc
Description
Existing tests updated for new async functions.
E2E tests required to test performance(how fast large number of new/changed objects can be processed). Such tests would prove efficiency of kopf concurrency.
Types of Changes
Tasks
List of tasks you will do to complete the PR
Review
List of tasks the reviewer must do to review the PR
As a side-note: I tried to check why Travis CI pipeline is not triggered for this PR, and for this PR only — it works for other PRs & contributors. Travis CI says "Abuse detected" without any additional explanation.
I will try to contact Travis CI support to clarify what is the actual reason.
My only assumption for now is that this is a PR from the "master" branch of a fork to the "master" branch of the upstream — maybe Travis does not like it. This is the only "unusual" thing in this PR. Just guessing.
The text was updated successfully, but these errors were encountered: