Fix the stop-flag setting: no arguments are expected

[nolar]

Issue: #142, introduced in #147

Description

Sadly so, in #147, an error sneaked into the code:

Event.set() does not accept any arguments, but they are passed into a callback. The callback was originally implemented as a separate async-function, which took a list of tasks and cancelled all of them. Then, the callback was replaced to a flag-setting. But the argument with a list of tasks went unnoticed.

This only affects the operators on its termination stage (Ctrl+C or pod deletion/restarting), and does not affect the behaviour itself.

Types of Changes

• Bug fix (non-breaking change which fixes an issue)

[zincr]

🤖 zincr found 0 problems , 0 warnings

✅ Large Commits
✅ Approvals
✅ Specification
✅ Dependency Licensing

[zincr]

🤖 zincr found 1 problem , 0 warnings

❌ Approvals
✅ Large Commits
✅ Specification
✅ Dependency Licensing

Details on how to resolve are provided below

---

Approvals

All proposed changes must be reviewed by project maintainers before they can be merged

Not enough people have approved this pull request - please ensure that 1 additional user, who have not contributed to this pull request approve the changes.

• ✅ Approved by PR author @nolar
• ❌ 1 additional approval needed
   

[codecov-io]

Codecov Report

Merging #151 into master will not change coverage.
The diff coverage is 0%.

@@           Coverage Diff           @@
##           master     #151   +/-   ##
=======================================
  Coverage   82.56%   82.56%           
=======================================
  Files          30       30           
  Lines        1572     1572           
  Branches      229      229           
=======================================
  Hits         1298     1298           
  Misses        229      229           
  Partials       45       45

Impacted Files	Coverage Δ
kopf/reactor/queueing.py	56% <0%> (ø)	⬆️