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
After running google-drive-ocamlfuse -id xxxxxxxxxx.apps.googleusercontent.com -secret XXX-YYY-ZZZ an error in the shell came up with the following text: Thread 1 killed on uncaught exception Unix.Unix_error(50, "bind", ""). The OAuth browser window did open, but auth failed because the process for retrieving the callback never started.
I see two ways of solving this:
Warn the user that port 8080 must be available
Use a distinct port for the OAuth callback
I actually think that using options 1 & 2, where a different, obscure port number is used, and also a warning is given to the user that the chosen new port number must be available.
The text was updated successfully, but these errors were encountered:
I have a process running that occupied port
8080
.After running
google-drive-ocamlfuse -id xxxxxxxxxx.apps.googleusercontent.com -secret XXX-YYY-ZZZ
an error in the shell came up with the following text:Thread 1 killed on uncaught exception Unix.Unix_error(50, "bind", "")
. The OAuth browser window did open, but auth failed because the process for retrieving the callback never started.I see two ways of solving this:
I actually think that using options 1 & 2, where a different, obscure port number is used, and also a warning is given to the user that the chosen new port number must be available.
The text was updated successfully, but these errors were encountered: