You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: Null metadata values cause NPEs when converting parts between v1.0 and v0.3 #1275
Hi, I'd like to investigate this bug and contribute a fix. My understanding of the report is that converting between v1.0 and v0.3 throws a NullPointerException when a part's metadata contains a null value, affecting both TextPart_v0_3 and DataPart_v0_3. I'll first reproduce this and add regression tests for both part types and conversion directions before proposing a minimal fix. Please let me know if I've misunderstood the report or if someone is already working on it.
changed the title [-][Bug]: v1.0和v0.3相互转换时,如果parts中的metadata中的值为null,会抛NPE异常[/-][+][Bug]: Null metadata values cause NPEs when converting parts between v1.0 and v0.3[/+]on Nov 4, 2026
Activity
kabir commentedon Nov 3, 2026
Hi, would you be able to put the text into English? Thanks!
Orcus01 commentedon Nov 4, 2026
Hi, I'd like to investigate this bug and contribute a fix. My understanding of the report is that converting between v1.0 and v0.3 throws a NullPointerException when a part's metadata contains a null value, affecting both TextPart_v0_3 and DataPart_v0_3. I'll first reproduce this and add regression tests for both part types and conversion directions before proposing a minimal fix. Please let me know if I've misunderstood the report or if someone is already working on it.
kabir commentedon Nov 4, 2026
@Orcus01 Yes, feel free. Just make sure that the behaviour is in line with the specs
kabir commentedon Nov 4, 2026
Also, if you are able to translate the header that would be great :-D
[-][Bug]: v1.0和v0.3相互转换时,如果parts中的metadata中的值为null,会抛NPE异常[/-][+][Bug]: Null metadata values cause NPEs when converting parts between v1.0 and v0.3[/+]test(compat-0.3): cover null part metadata conversions (#1289)
kabir commentedon Nov 4, 2026
Closing as I believe this was fixed by #1289 and #1261