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
I don't think this is really "issue" material so I didn't want to file it as a bug report, but I do want to help anyone else that comes across this, so hopefully Google will pick it up. Basically setting Prefork to true stops debugging from working in VS Code for any handlers you might have. I noticed that the entrypoint is debuggable, the file where I have the server configuration is debuggable, but the handlers for all routes are not.
Just something to keep in mind. Having prefork on during development is completely unnecessary anyway, but I had forgotten that I enabled it for testing purposes and then spent well over an hour figuring out why debugging wasn't working.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I don't think this is really "issue" material so I didn't want to file it as a bug report, but I do want to help anyone else that comes across this, so hopefully Google will pick it up. Basically setting Prefork to true stops debugging from working in VS Code for any handlers you might have. I noticed that the entrypoint is debuggable, the file where I have the server configuration is debuggable, but the handlers for all routes are not.
Just something to keep in mind. Having prefork on during development is completely unnecessary anyway, but I had forgotten that I enabled it for testing purposes and then spent well over an hour figuring out why debugging wasn't working.
Beta Was this translation helpful? Give feedback.
All reactions