Discord artifact 이미지 첨부 전송 경로 수정 / Fix Discord artifact image attachm…#136
Open
min9538p wants to merge 1 commit into
Open
Discord artifact 이미지 첨부 전송 경로 수정 / Fix Discord artifact image attachm…#136min9538p wants to merge 1 commit into
min9538p wants to merge 1 commit into
Conversation
…ents 한국어: - data/artifacts 아래 생성된 PNG가 Discord 파일 첨부로 업로드되도록 허용 경로를 추가합니다. - 텍스트 본문에만 있는 마크다운 이미지도 attachmentBaseDirs를 전달받아 검증/업로드될 수 있게 합니다. - artifact 이미지 첨부 회귀 테스트를 추가합니다. English: - Allow generated PNG files under data/artifacts to be uploaded as Discord file attachments. - Pass attachmentBaseDirs for text-only markdown image outputs so extracted images can be validated and uploaded. - Add regression coverage for artifact image attachment delivery.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
증상 / Symptom
한국어:
Discord paired room에서
!... 형태의 PNG 캡처를 보내면, 이미지 마크다운 줄은 본문에서 제거되지만 Discord 파일 첨부로 업로드되지 않았습니다. 그 결과 사용자는 캡처 이미지가 있어야 할 위치에서 빈 공간만 보게 되었습니다.English:
When a PNG capture was sent from a Discord paired room using !...`, the markdown image line was removed from the message body but the file was not uploaded as a Discord attachment. As a result, users only saw an empty gap where the screenshot should have appeared.
원인 / Root Cause
한국어:
본문 안의 마크다운 이미지는 outbound 처리 과정에서 구조화 첨부로 추출되지만, work item에 명시적인 attachments 배열이 없으면 deliverOpenWorkItem이 attachmentBaseDirs를 sendMessage로 전달하지 않았습니다. 또한 /home/ejclaw/EJClaw/data/artifacts 경로가 기본 첨부 허용 경로에 포함되어 있지 않아 생성된 캡처 파일을 안전한 업로드 대상으로 인정하지 못했습니다.
English:
Markdown images in the message body are extracted as structured attachments during outbound processing, but deliverOpenWorkItem did not pass attachmentBaseDirs to sendMessage when the work item did not include an explicit attachments array. In addition, /home/ejclaw/EJClaw/data/artifacts was not part of the default attachment allowlist, so generated capture files were not accepted as safe upload targets.
조치내역 / Changes
한국어:
English:
dMessage even when markdown images only exist in the text body.
반영사항 / Impact
한국어:
Playwright/Chromium으로 생성한 웹 화면 캡처나 디자인 테스트 산출물을 /home/ejclaw/EJClaw/data/artifacts/ 아래에 저장한 뒤 마크다운 이미지로 보내면 Discord 첨부로 정상 표시됩니다. 기존 명시 첨부 전송 경로는 유지됩니다.
English:
Web screenshots and design test artifacts generated by Playwright/Chromium can now be stored under /home/ejclaw/EJClaw/data/artifacts/ and sent as markdown images that appear as Discord file attachments. Existing explicit attachment delivery behavior is preserved.
검증 / Verification
한국어:
English: