inspector.open(0, undefined, /* wait */true) won't allow communicating inspector.url()

[pavelfeldman]

I'd like to open the first available debugging port and wait for client to attach before I continue execution, so I do:

inspector.open(0, undefined, /* wait */ true);

This results in a logical deadlock though: in order to get the inspector.url(), I need to continue execution. But execution only continues when connection is established over that exact URL I can't get. It makes me think that inspector.open does not really make sense with the wait === true.

Could this API be changed to something like below instead?

inspector.open(0, undefined, true, ({url}) => {
  clientPipe.send(url);  // <-- reports url
});
// <-- blocks execution.

@eugeneo, @ak239

[eugeneo]

I believe, this will help once it lands: #28453

[pavelfeldman]

Yes, it does seem to help! Should it deprecate / remove wait in the inspector.open as well? That api is stability 1, can we fix it?

[eugeneo]

I do not feel strongly either way.

[jasnell]

Any @nodejs/inspector ...is there anything further actionable here or can this be closed?

[benjamingr]

James - looks like Pavel is right no one just felt strongly enough about it

[github-actions]

This issue has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.

[github-actions]

This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 120 days).
If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.