public inbox for yew-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Dominik Csapak <d.csapak@proxmox.com>
To: yew-devel@lists.proxmox.com, Thomas Lamprecht <t.lamprecht@proxmox.com>
Subject: applied: [PATCH 0/2] fix listener teardown and loader cancellation
Date: Wed,  9 Sep 2026 10:24:12 +0200	[thread overview]
Message-ID: <178894214417.3174862.828430953403792784.b4-ty@b4> (raw)
In-Reply-To: <20260909010400.684482-1-t.lamprecht@proxmox.com>

On Wed, 09 Sep 2026 03:01:11 +0200, Thomas Lamprecht wrote:
> Fix borrow panics during listener removal and correct Loader request
> accounting and cancellation on last-owner drop.
> 
> Thomas Lamprecht (2):
>   shared state: avoid borrow panics when removing listeners
>   loader: fix stuck loading state and cancel loads without owners
> 
> [...]

Took me a bit to understand the code and commit message (it's not trivial!).
Thought about a simpler solution without splitting the loader type, but
i think that's not really possible without having to keep the request
alive when only change observers live on? (correct me if I'm wrong)

Applied, thanks!

[1/2] shared state: avoid borrow panics when removing listeners
      commit: 4b3af68bc6e48c41db945df9599f10a2ec8ed026
[2/2] loader: fix stuck loading state and cancel loads without owners
      commit: 025ba008d22b12451397448563029b880461b958




      parent reply	other threads:[~2026-09-09  8:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-09  1:01 [PATCH 0/2] fix listener teardown and loader cancellation Thomas Lamprecht
2026-09-09  1:01 ` [PATCH 1/2] shared state: avoid borrow panics when removing listeners Thomas Lamprecht
2026-09-09  1:01 ` [PATCH 2/2] loader: fix stuck loading state and cancel loads without owners Thomas Lamprecht
2026-09-09  8:24 ` Dominik Csapak [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=178894214417.3174862.828430953403792784.b4-ty@b4 \
    --to=d.csapak@proxmox.com \
    --cc=t.lamprecht@proxmox.com \
    --cc=yew-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal