Open charliettaylor opened 10 months ago
Hey @charliettaylor this issue hasn't been reported by any other customers and thus isn't a priority for us right now. If this is still preventing you from using Fern, let me know!
@dannysheridan Online development environments like GitHub codespaces, GitPod.io, etc will throw this error, could Fern echo the opening URL to console for accessing manually? Just like npm login
or vercel login
?
It's so important for those users who has a bad Internet connection locally, we can use GitPod-like IDE normally, but disconnected from local CLI:
$ fern init --openapi http://localhost:8080/docs/spec
Failed.
Request timed out // This isn't my `localhost`, it's `fern login`...
@TechQuery I've reopened this issue based on your feedback. Interested in contributing this change?
@dannysheridan I would be down to take a look at it, seems like the issue is using the npm open package to automatically open the URL in browser. We could wrap those calls in a try-catch and log the URL when an exception is thrown, I'm not sure if there is a way to detect if someone is in a headless env, would be nice to do that instead of having to catch an exception.
@charliettaylor sounds great. Feel free to post in our Slack community if you have questions while making this contribution.
Describe the bug I attempted to run
fern init
on my development server and had an exception thrown when it asked me to loginTo Reproduce Steps to reproduce the behavior:
fern login
Expected behavior Normal login behavior should proceed
Screenshots
Installing
xdg-utils
onto my system does not resolve the issue, as nowfern login
hangs forever. Also, users in headless environments should still be able to login without needing desktop utils.Desktop: