Upcoming Servo issue triage meeting on September 30 2024

[gterzian]

Where: https://meet.jit.si/ServoTriage.

When: 10:00 AM GMT (Europe and Asia friendly, we can later alternate with a US friendly time if needed).

What: any issue one wishes to triage.

Who: anyone is welcome, but if there are no issues to discuss the meeting will be canceled.

Please express your interest to attend and note the issue(s) you would like to triage(which can be one someone else already brought up).

Last meeting at https://github.com/servo/project/issues/100

Action points:

• [ ] @jdm and @gterzian keep looking into https://github.com/servo/servo/issues/31973 (and the partner issue https://github.com/servo/servo/issues/31982). @gterzian can look again into this now we're reached a point where the event-loop/update the rendering stuff looks stable for now.
• [ ] Anyone interested can look into https://github.com/servo/servo/issues/31182
• [ ] Same for https://github.com/servo/servo/issues/30822
• [ ] Re readablestream: let's try to merge https://github.com/servo/servo/pull/33160 and then try to merge the default reader struff into main, because on current main we are only running tests for the default stuff; the bytestream can be done after in a second batch to keep it manageable.
• [ ] @taym95 wants to start looking into https://github.com/servo/servo/issues/31022
• [ ] @gterzian to look into fixing the intermittency of https://github.com/servo/servo/issues/33028 via an update of the at https://github.com/web-platform-tests/wpt/issues/48153

[msub2]

I think this could be worth looking into, there's a parsing error during the mimesniff WPT tests that prevent Servo from running any of the subtests, despite having mimesniff capabilities https://github.com/servo/servo/issues/33467 Was fixed!