dotnet / dotnet/aspnetcore

Components.AI: Integrate attachment lifetime with queued follow-ups

Open
#68,403 0 comments 0 reactions 0 assignees View on GitHub
area-blazor cost: M feature-blazor-builtin-components Priority:0
Dominant language
C#
Stars
38.4k
Forks
10.9k
Avg merge
2d 10h
Merged PRs (30d)
281

Description

### Is your feature request related to a problem? Please describe the problem.

Queued messages may carry attachments whose transfer and disposal lifetime must survive composer clearing and handle removal or Stop correctly.

### Describe the solution you'd like

Implement the approved attachment ownership semantics for enqueue, per-message removal, atomic drain, failure, and full-queue cancellation without leaks or accidental reuse.

### Additional context

Leaf task for #68227 requirement C11 and attachment requirements D1-D8. Depends on queue semantics and the attachment pipeline.

Contributor guide

Open the contributing guide

Research direction

The issue names no files, tests, or entry points. Start by tracing the queue semantics and attachment pipeline referenced in the issue and the linked requirements, then verify enqueue, per-message removal, atomic drain, failure, and full-queue cancellation against the approved ownership semantics without leaks or accidental reuse.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.