search

axelclark / ex338

Web application to manage the 338 Challenge fantasy sports league
https://the338challenge.com
MIT License
22 stars 7 forks source link

Bump oban from 2.17.7 to 2.17.8 #1304

Closed dependabot[bot] closed 6 months ago

dependabot[bot] commented 6 months ago

Bumps oban from 2.17.7 to 2.17.8.

Changelog

Sourced from oban's changelog.

v2.17.8 — 2024-04-07

Enhancements

  • [Backoff] Backoff retry on DBConnection and Postgrex errors from GenServer calls.

    GenServer calls that result in a ConnectionError or Postgrex.Error should also be caught and retried rather than crashing on the first attempt.

Bug Fixes

  • [Notifier] Check for a live notifier process and propagate notify errors.

    The Notifier.notify/1 spec showed it would always return :ok, but that wasn't the case when the notifier was disconnected or the process was no longer running. Now an error tuple is returned when a notifier process isn't running.

    This situation happened most frequently during shutdown, particularly from external usage of the Notifier like an application or the oban_met package.

    In addition, the errors bubble up through top level Oban functions like scale_queue/1, pause_queue/1, etc. to indicate that the operation can't actually succeed.

  • [Peers.Postgres] Rescue DBConnection.ConnectionError in peer leadership check.

    Previously, only Postgrex.Error exceptions were rescued and other standard connection errors were ignored, crashing the Peer. Because leadership is checked immediately after the peer initializes, any connection issues would trigger a crash loop that could bring down the rest of the supervision tree.

Commits
  • 2fbf4e2 Release v2.17.8
  • a732e9f Ensure a unique name in isolated notifier test
  • 5743f21 Rescue ConnectionError in peer leadership check
  • 181780f Add Lite engine usage to the installation guide
  • a5aa0a8 Check process and propagate notify errors
  • fa67438 Mention Sentry and AppSignal integration (#1062)
  • c875bfd Backoff retry on db errors from GenServer calls
  • See full diff in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)