-
Notifications
You must be signed in to change notification settings - Fork 405
refactor(tui): extract attachments from document parts in session #3484
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -2,12 +2,11 @@ package messages | |
|
|
||
| import "github.com/docker/docker-agent/pkg/session" | ||
|
|
||
| // Attachment represents content attached to a message. It is either a reference | ||
| // to a file on disk (FilePath is set) or inline content already in memory | ||
| // (Content is set, e.g. pasted text). When FilePath is set the consumer reads | ||
| // and classifies the file at send time; when only Content is set the consumer | ||
| // uses it directly as inline text. This design lets us add binary-file support | ||
| // (images, PDFs, …) in the future by extending the struct with a MimeType hint. | ||
| // Attachment represents content attached to a message. It can be a reference | ||
| // to a file on disk (FilePath is set), inline text content (Content is set), | ||
| // or inline binary content (Data and MimeType are set). When FilePath is set, | ||
| // the consumer reads and classifies the file at send time; inline content | ||
| // is used directly. | ||
| type Attachment struct { | ||
| // Name is the human-readable label (e.g. "paste-1", "main.go"). | ||
| Name string | ||
|
|
@@ -18,6 +17,10 @@ type Attachment struct { | |
| // backing temp file is cleaned up before the message reaches the app layer. | ||
| // Empty for file-reference attachments that are read from disk. | ||
| Content string | ||
| // MimeType is the MIME type of the binary data, if Data is present. | ||
| MimeType string | ||
| // Data holds raw binary content for non-text inline attachments. | ||
| Data []byte | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The struct's doc comment at the top of this file is now stale. It still states that the value is either |
||
| } | ||
|
|
||
| // Session lifecycle messages control session state and persistence. | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -785,8 +785,8 @@ func (p *chatPage) handleInlineEditCancelled(msg messages.InlineEditCancelledMsg | |
| } | ||
|
|
||
| // extractAttachmentsFromSession extracts attachments from a session message at the given position. | ||
| // Attachments are stored as text parts in MultiContent with format "Contents of <filename>: <dataURL>". | ||
| // TODO(krisetto): meh we can store and retrieve attachments better in the session itself | ||
| // Legacy attachments are stored as text parts in MultiContent with format "Contents of <filename>: <dataURL>". | ||
| // New attachments are stored as Document parts. | ||
| func (p *chatPage) extractAttachmentsFromSession(position int) []msgtypes.Attachment { | ||
| sess := p.app.Session() | ||
| if sess == nil || position < 0 || position >= len(sess.Messages) { | ||
|
|
@@ -805,20 +805,37 @@ func (p *chatPage) extractAttachmentsFromSession(position int) []msgtypes.Attach | |
| } | ||
|
|
||
| var attachments []msgtypes.Attachment | ||
| const prefix = "Contents of " | ||
| const legacyPrefix = "Contents of " | ||
|
|
||
| // Skip the first part (main text content), look for attachment parts | ||
| for i := 1; i < len(msg.MultiContent); i++ { | ||
| part := msg.MultiContent[i] | ||
|
|
||
| if part.Type == chat.MessagePartTypeDocument && part.Document != nil { | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. No regression test accompanies this change, and this is the exact path that previously shipped the context-overflow bug. A unit test on |
||
| content := part.Document.Source.InlineText | ||
| data := part.Document.Source.InlineData | ||
| mimeType := part.Document.MimeType | ||
|
|
||
| if content != "" || len(data) > 0 { | ||
| attachments = append(attachments, msgtypes.Attachment{ | ||
| Name: part.Document.Name, | ||
| Content: content, | ||
| MimeType: mimeType, | ||
| Data: data, | ||
| }) | ||
| } | ||
| continue | ||
| } | ||
|
|
||
| if part.Type != chat.MessagePartTypeText { | ||
| continue | ||
| } | ||
| text := part.Text | ||
| if !strings.HasPrefix(text, prefix) { | ||
| if !strings.HasPrefix(text, legacyPrefix) { | ||
| continue | ||
| } | ||
| // Parse "Contents of <filename>: <dataURL>" | ||
| rest := text[len(prefix):] | ||
| rest := text[len(legacyPrefix):] | ||
| before, after, ok := strings.Cut(rest, ": ") | ||
| if !ok { | ||
| continue | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,83 @@ | ||
| package chat | ||
|
|
||
| import ( | ||
| "testing" | ||
|
|
||
| "github.com/stretchr/testify/assert" | ||
| "github.com/stretchr/testify/require" | ||
|
|
||
| "github.com/docker/docker-agent/pkg/app" | ||
| "github.com/docker/docker-agent/pkg/chat" | ||
| "github.com/docker/docker-agent/pkg/session" | ||
| ) | ||
|
|
||
| func TestExtractAttachmentsFromSession(t *testing.T) { | ||
| t.Parallel() | ||
|
|
||
| sess := session.New() | ||
| p := newTestChatPage(t) | ||
| p.app = app.New(t.Context(), queueTestRuntime{}, sess) | ||
|
|
||
| msg := session.Message{ | ||
| Message: chat.Message{ | ||
| Role: chat.MessageRoleUser, | ||
| MultiContent: []chat.MessagePart{ | ||
| {Type: chat.MessagePartTypeText, Text: "main user prompt"}, | ||
| // 1. Document with InlineText | ||
| { | ||
| Type: chat.MessagePartTypeDocument, | ||
| Document: &chat.Document{ | ||
| Name: "text_doc.txt", | ||
| Source: chat.DocumentSource{ | ||
| InlineText: "text content", | ||
| }, | ||
| }, | ||
| }, | ||
| // 2. Document with InlineData | ||
| { | ||
| Type: chat.MessagePartTypeDocument, | ||
| Document: &chat.Document{ | ||
| Name: "binary_doc.png", | ||
| MimeType: "image/png", | ||
| Source: chat.DocumentSource{ | ||
| InlineData: []byte("binary data"), | ||
| }, | ||
| }, | ||
| }, | ||
| // 3. Legacy Text Contents | ||
| { | ||
| Type: chat.MessagePartTypeText, | ||
| Text: "Contents of legacy_doc.txt: legacy content", | ||
| }, | ||
| // 4. Empty Document | ||
| { | ||
| Type: chat.MessagePartTypeDocument, | ||
| Document: &chat.Document{ | ||
| Name: "empty_doc.txt", | ||
| }, | ||
| }, | ||
| }, | ||
| }, | ||
| } | ||
| sess.Messages = append(sess.Messages, session.Item{Message: &msg}) | ||
|
|
||
| attachments := p.extractAttachmentsFromSession(0) | ||
| require.Len(t, attachments, 3, "expected exactly 3 extracted attachments") | ||
|
|
||
| // 1. Document with InlineText | ||
| assert.Equal(t, "text_doc.txt", attachments[0].Name) | ||
| assert.Equal(t, "text content", attachments[0].Content) | ||
| assert.Empty(t, attachments[0].Data) | ||
|
|
||
| // 2. Document with InlineData | ||
| assert.Equal(t, "binary_doc.png", attachments[1].Name) | ||
| assert.Equal(t, "image/png", attachments[1].MimeType) | ||
| assert.Equal(t, []byte("binary data"), attachments[1].Data) | ||
| assert.Empty(t, attachments[1].Content) | ||
|
|
||
| // 3. Legacy Text Contents | ||
| assert.Equal(t, "legacy_doc.txt", attachments[2].Name) | ||
| assert.Equal(t, "legacy content", attachments[2].Content) | ||
| assert.Empty(t, attachments[2].Data) | ||
| assert.Empty(t, attachments[2].MimeType) | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Routing binary payloads back through
ProcessAttachmentWithMetadatais the right call and keeps the size and decompression-bomb guards. Worth a test for the resend path: an already-processed image re-entersResizeImage, which returnsResized:falsewhen it already fits within limits, soFormatDimensionNoteyields no duplicate dimension note. A test would document that idempotence.