-
Notifications
You must be signed in to change notification settings - Fork 367
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: port in use #6887
feat: port in use #6887
Conversation
nforms the user that this could be from a netlify function opening ports Co-authored-by: Thomas Lane <[email protected]>
Co-authored-by: Thomas Lane <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, just a small nit about any
types.
Co-authored-by: Will <[email protected]>
This has been updated with a new type. |
Head branch was pushed to by a user without write access
5d92bbe
to
34b6bb4
Compare
The tests have been fixed. Ready for re-review |
Look like this might be a flakey test. It passed in every single other environment, and passes the test locally. The tests were passing until I merged the latest version of main. |
🎉 Thanks for submitting a pull request! 🎉
Summary
This pull request addresses these issues found below
netlify dev
#6840We (@tlane25) outline the problem in the comments in #6840.
This pull request adds better error handling for users who open a port for a serverless function.
For us to review and ship your PR efficiently, please perform the following steps:
passes our tests.
A picture of a cute animal (not mandatory, but encouraged)