Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Verify Email::MIME raw-body quoted-printable serialization

已關閉
#1,835 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
3/5
預估耗時
1-2 天
新手友好度
48/100
Issue 類型
缺陷
描述清晰度
描述清楚
活躍度
活躍
技術堆疊
java
領域
testing

研究方向

Start with assertion 18 ('quoted-printable + body_set raw works') in t/encoding.t of Email::MIME 1.954, and check whether PR #1817's change to MIME::QuotedPrint::encode_qp EOL handling affects it. Run that test file on system Perl, the JVM backend and the interpreter to compare results. Done means assertion 18 passes on all three, or a focused regression test is added and the raw-body quoted-printable path is fixed.

由索引模型根據 Issue 內容生成。

描述

area:backend area:cpan-port area:runtime bug

Summary

Recheck the Email::MIME 1.954 raw-body quoted-printable assertion reported in issue #1341 after the MIME::QuotedPrint::encode_qp EOL fix from PR #1817.

Evidence

CPAN random-tester run 20260924-085657-82687 reported that Email::MIME 1.954 fails assertion 18 in t/encoding.t, quoted-printable + body_set raw works, on both JVM and interpreter backends. The system-Perl oracle passed the complete Email::MIME suite.

PR #1817 fixes the requested EOL handling and verifies Email::MIME::Encodings 1.317 t/basic.t on both backends. The raw-body assertion itself was not rerun, so it is not yet known whether that change resolves this path. This issue tracks that remaining verification separately from #1141, which covers RFC 2047 header decoding and address parsing.

Acceptance criteria

  • Run Email::MIME 1.954 t/encoding.t on system Perl, JVM, and interpreter.
  • Confirm whether assertion 18 passes with PR #1817 merged.
  • If it still fails, add a focused project-owned regression and fix the underlying raw-body quoted-printable behavior.
主要語言
Perl
星號
65
分支
8
平均合併
6 小時 1 分鐘
30 天內合併 PR
189

環境準備

  • 提供 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

fglock/PerlOnJava 的其他 Issue

查看 fglock/PerlOnJava 的全部 Issue

相似的 Issue

更多 Perl Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。