Skip to content

3.8.2: fix how duplicate events are identified

Latest
Latest

Choose a tag to compare

View all tags
@dwilding dwilding released this 31 Aug 04:37
· 10 commits to main since this release
Immutable release. Only release title and notes can be modified.
3.8.2
0d7fbd2
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

This release fixes a bug in deferred event handling. If an event MyEmitter[foo]/evt1 was deferred, subsequent events MyEmitter[foo]/evt2 and MyEmitter[bar]/evt1 would be incorrectly identified as duplicate events, and then skipped. Thank you @Ali-932 for the fix!

What's Changed

Fixes

  • Compare full event paths when skipping duplicate notices in #2684
  • In ops.testing, don't pass a message when converting an unknown status by name in #2700

Documentation

  • Give each best-practice admonition a stable anchor in #2524
  • Reword text that vale 3.17 flags as misspelled in #2695
  • Stop styling page references as blockquotes in #2666
  • Make the custom-endpoint-name sample test actually test something in #2664
  • Replace requests by urllib in K8s tutorial integration tests in #2687
  • Recommend spread directly, rather than charmcraft test in #2706
  • Extract sections in "how to write integration tests" to their own how-to guide in #2662

CI

  • Point DB charm CI at the moved mysql-operators repo in #2551
  • Switch example charm integration tests to Concierge k8s preset in #2696
  • Use the upstream concierge presets again in #2699

Full Changelog: 3.8.1...3.8.2

Contributors

Ali-932
Assets 3
Loading