Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
AWS Lambda integration - Improve error message & allow for port change
See original GitHub issueProblem Statement
Currently our lambda integration is running on port 8000. If there is an another service running on that port, the user will see ERROR: bind to interface failed caused by: Address already in use (os error 98)
a) we should improve the error message to make it more informative b) we can consider allowing port switch to avoid the above issue
Solution Brainstorm
Posssible solution: a) start relay on an obscure port. b) start by default on 8000, but make it configurable via env variable (needs changes in sdk and relay, can be complicated to work on all different js frameworks.
So better go with a)
Issue Analytics
- State:
- Created a year ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@AbhiPrasad it’s already on our backlog, you can remove it from yours.
We will just pick an obscure port here, exposing this as config doesn’t hold much value. Will update issue when fixed/shipped.