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
Thanks for making this awesome debugger extension! Launching tests work out of the box, which is cool, although attaching to our servers don't have a ideal developer experience.
Problem
The default behaviour of the VSCode extension is to list all process and pick only one. Our setup uses 12 puma process to ensure a good developer experience. What happens now is that to debug properly, we needed to manually click and attach them 1-by-1 🥲
Proposal
In this fork, I send custom events attachSingleSocket and the listener will start the debug just for the socket paths 4441cbc
I wonder if this capability interest other folks? If yes, we can add env variable or config (eg. SUPPORT_ATTACH_MULTI_SOCKETS or supportAttachMultiSockets) where when multiple sockets are detected, we use the multi session instead
// extension.ts; attach() method
...
constlist=awaitthis.getSockList(config);outputChannel.appendLine(JSON.stringify(list));switch(list.length){case0:
vscode.window.showErrorMessage("Can not find attachable Ruby process.");returnnewDebugAdapterInlineImplementation(newStopDebugAdapter);case1:
sockPath=list[0];break;default:
// The new behaviour controller by the new config// --startif(this.supportAttachMultiSockets){constadapter=newMultiSessionDebugAdapter(list);returnnewDebugAdapterInlineImplementation(adapter);}// --end constsock=awaitvscode.window.showQuickPick(list);if(sock){sockPath=sock;}else{returnnewDebugAdapterInlineImplementation(newStopDebugAdapter);}
...
Happy to help implementing the new capabilities if this has interests 👍
The text was updated successfully, but these errors were encountered:
Thanks for making this awesome debugger extension! Launching tests work out of the box, which is cool, although attaching to our servers don't have a ideal developer experience.
Problem
The default behaviour of the VSCode extension is to list all process and pick only one. Our setup uses 12 puma process to ensure a good developer experience. What happens now is that to debug properly, we needed to manually click and attach them 1-by-1 🥲
Proposal
In this fork, I send custom events
attachSingleSocket
and the listener will start the debug just for the socket paths4441cbc
I wonder if this capability interest other folks? If yes, we can add env variable or config (eg.
SUPPORT_ATTACH_MULTI_SOCKETS
orsupportAttachMultiSockets
) where when multiple sockets are detected, we use the multi session insteadHappy to help implementing the new capabilities if this has interests 👍
The text was updated successfully, but these errors were encountered: