shuppy

one alternative i’ve seen in things like graphical installers with a /? option is to show the help output in a [MessageBoxW](https://learn.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-messageboxw), though that would only help with --help, not...

More documentation about the interaction between threads and sources: https://firefox-source-docs.mozilla.org/devtools/backend/protocol.html#interacting-with-thread-like-actors

- finished reading https://firefox-source-docs.mozilla.org/devtools/backend/actor-hierarchy.html - started reading https://firefox-source-docs.mozilla.org/devtools/backend/protocol.html#interacting-with-thread-like-actors - servo BrowsingContextActor = firefox WindowGlobalTargetActor? https://searchfox.org/mozilla-central/rev/b22ec3f983078ff98b04cee7dafe4b90342a42bf/devtools/server/actors/targets/window-global.js - “actors inheriting from WindowGlobalTargetActor” → ParentProcessTargetActor https://searchfox.org/mozilla-central/rev/b22ec3f983078ff98b04cee7dafe4b90342a42bf/devtools/server/actors/targets/parent-process.js - ? our BrowsingContextActor has threadActor property,...

`.traits.worker == true` seems to be required in the `getWatcher` response: - [cap-firefox3.json](https://github.com/user-attachments/files/19514961/cap-firefox3.json) - [cap-firefox3-0bad.json](https://github.com/user-attachments/files/19514962/cap-firefox3-0bad.json) - [cap-firefox3-1good.json](https://github.com/user-attachments/files/19514963/cap-firefox3-1good.json) - [cap-firefox3-2good.json](https://github.com/user-attachments/files/19515025/cap-firefox3-2good.json) - [cap-firefox3-3bad.json](https://github.com/user-attachments/files/19515061/cap-firefox3-3bad.json)

Handling `getBreakpointListActor` from `getWatcher` is required, because it blocks later `watchResources` for `source`: - [cap-firefox3-2good-0good.json](https://github.com/user-attachments/files/19531243/cap-firefox3-2good-0good.json) - [cap-firefox3-2good-1bad.json](https://github.com/user-attachments/files/19531244/cap-firefox3-2good-1bad.json)

Thanks for the advice! I haven’t had time to try it yet sorry, hopefully that will change at some point next month.

these devtools parser tests are not the same as the devtools tests (mach test-devtools); they only test [etc/devtools_parser.py](https://github.com/servo/servo/blob/493acd7e43100a5449828017fc906aeec51e5657/etc/devtools_parser.py), so they don’t require a servo build.

that sounds compelling! in what cases would we still need to have dependent workflows (`needs`)? i guess for building servo once and sharing it with the wpt jobs, and self-hosted...

> I want to keep them in same repo, to make changing CI easier, but I have idea how to do this with rust, by simply having one prejob that...

i’ve started prototyping a tool in [delan/servo-ci](https://github.com/delan/servo-ci) + #38389. for now, it just buys us some time by eliminating self-hosted-runner-select and self-hosted-runner-timeout, and it lives in an external repo. >...