@chenura999 Do you have a link to where this produced an error during WPT import?

@mrobinson
The error occurred in Job ID 57413047323.

The failure log showed a TypeError: argument of type 'NoneType' is not iterable in servo/python/wpt/export.py. This happens when the PR body is null (e.g. an empty description), which causes pull_data.get("body") to return None even if a default value is provided to .get() (because the key exists, it just has a null value).

I verified this behavior locally with a reproduction script and the fix ensures we default to an empty string in that case.

@chenura999 Can you provide a link to that job? I'm not sure which run it was a part of.

@chenura999 Can you provide a link to that job? I'm not sure which run it was a part of.

I tried to access the run again, but the link seems to be expired or invalid now (404).

However, I can confirm the error was a TypeError: argument of type 'NoneType' is not iterable in
servo/python/wpt/export.py
. It happened because the PR body was None (empty), and the script didn't handle that case safely.

The fix I pushed ensures we default to an empty string so this doesn't happen again.

I think this is the run with that job - https://github.com/servo/servo/actions/runs/20022685522/job/57412925025

I think this is the run with that job - https://github.com/servo/servo/actions/runs/20022685522/job/57412925025

Thanks for the log! That confirms it was the NoneType error in the WPT export script caused by an empty PR body.

I've pushed a fix for that script to this branch as well, so the CI should pass now.

I think this is the run with that job - https://github.com/servo/servo/actions/runs/20022685522/job/57412925025

Thanks for the log! That confirms it was the NoneType error in the WPT export script caused by an empty PR body.

I've pushed a fix for that script to this branch as well, so the CI should pass now.

This looks was written using AI.

I have rewritten the PR description in case it was written via LLM. @chenura999, we really appreciate the contributions, but please avoid using AI tools to generate commits or descriptions. It's nothing personal -- just the policy we currently have in place. If you aren't confident about the PR description your write yourself, feel free to ask a reviewer to look it over and make edits. Thank you!

I have rewritten the PR description in case it was written via LLM. @chenura999, we really appreciate the contributions, but please avoid using AI tools to generate commits or descriptions. It's nothing personal -- just the policy we currently have in place. If you aren't confident about the PR description your write yourself, feel free to ask a reviewer to look it over and make edits. Thank you!

Thank you really appreciate it ❤️