mirror of
https://github.com/outbackdingo/firezone.git
synced 2026-01-27 18:18:55 +00:00
Currently, after the refresh timeout the gateway or client starts looping forever, since after the refresh timeout is reached the `poll_timeout` will always return `ALLOCATION_LIFETIME/2`(which would be "now"), since `allocation_lifetime` is never updated. To fix this, we need to check whether we currently have a refresh request in flight before queuing a new one. Additionally, we need to abort refreshing as soon as the lifetime of the allocation expires. Related: #3617. Related: #3631. --------- Co-authored-by: Thomas Eizinger <thomas@eizinger.io>