Added timeout and error handling for frpc tunnel

[cansik]

Description

As discussed in #3677, the current implementation for sharing gradio services does not handle frpc errors well. The error message is not displayed and the while loop to check for success runs forever.

Technical fix

This PR adds the ability to set a timeout (in seconds) for tunneling. This allows all the logs from frpc to be collected and printed in the error stream when an error occurs. It also fixes the possibility of an infinite loop. If possible, the error or success is handled before the timeout by parsing the current logs (as in the actual implementation).

Usability

Since creating a tunnel can take a long time (default: 30 seconds), I would suggest showing a message that the shared link is being created. Otherwise it is not clear to the user that gradio is still doing something. Printing Running on local URL may give the user the impression that gradio is finished and only running locally. This PR prints the message Creating shared link... as user feedback.

Example

Here is an example when the firewall blocks the request:

Running on local URL:  http://127.0.0.1:7860
Creating shared link...
2023/09/28 10:56:04 [W] [service.go:132] login to server failed: dial tcp 44.237.78.176:7000: i/o timeout

Could not create share link. Please check your internet connection or our status page: https://status.gradio.app.

Closes: #3677

[gradio-pr-bot]

🪼 branch checks and previews

•	Name	Status	URL
🦄	Changes	detected!	Details

[gradio-pr-bot]

🦄 change detected

This Pull Request includes changes to the following packages.

Package	Version
gradio	patch

• Maintainers can select this checkbox to manually select packages to update.

With the following changelog entry.

Added timeout and error handling for frpc tunnel

Maintainers or the PR author can modify the PR title to modify this entry.

Something isn't right?

• Maintainers can change the version label to modify the version bump.
• If the bot has failed to detect any changes, or if this pull request needs to update multiple packages to different versions or requires a more comprehensive changelog entry, maintainers can update the changelog file directly.

[abidlabs]

made some small tweaks -- stripping the log lines was breaking the regex to identify the url for example -- but otherwise tested and looks good to me. Thanks @cansik!

[cansik]

Ok, that sounds great, I may have overlooked this mistake. But I guess it would make sense to add the strip for the messages that are added to the log, otherwise we have unnecessary empty lines in there.

The line usually contained a \n, which is basically treated as no output. That's why I stripped it. Have you tried it with a blocked firewall as well? Otherwise I would do that just to see if it prints correctly now.

And thanks for the adjustments!

[abidlabs]

Ok, that sounds great, I may have overlooked this mistake. But I guess it would make sense to add the strip for the messages that are added to the log, otherwise we have unnecessary empty lines in there.

Yup makes sense, will add that back in

[meihao5631]

I have perfectly solved the problem where "share=true" does not work. You need to add two lines of code to this location in the "tunneling.py" file.
the location of "tunneling.py" file: /home/[your anaconda virtual environment
]/lib/python3.11/site-packages/gradio/tunneling.py

[cansik]

@abidlabs Should we include tls enforcement into the tunneling call?