-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Missing component for share link tunneling for aarm64 #6053
Comments
The related code is at the top of tunneling.py Apparently the needed binaries for ARM we're never built, but presumably the existing Lenox code base can simply be cross-compiled in this case. Very strangely, in my specific instance, execution never reached line 52 of tunneling.py which would have yielded a much more informative error message and saved me half an hour of assembling a relatively convoluted ticket with what now seems to be unneeded detail. |
Hi @hillct I think you're right, we don't currently have the frpc compiled for this platform. We'll look into it. |
@abidlabs Is h source for frpc available, such that I can compile it myself? Are there significant changes relative to FRP? ie: https://gofrp.org/en ? I may in fact just be able to add a build stage to my Dockerfile https://github.com/fatedier/frp/blob/dev/dockerfiles/Dockerfile-for-frpc With this in mind, I'd recommend adding FRP as a submodule to the git repository, if for no other reason than to avoid dependency confusion. Similarly, the Gradio docs proclaim it's only dependency is Python (3.8+) but obviously there is an architecture-specific binary dependency. For what it's worth, I'd suggest distributing Gradio in architecture-specific .whl files including he frpc binary, rather than pulling the needed binary off the huggingFace CDN at runtime. UPDATE: I see now that the switch to frp was relatively recent, so it's understandable some of the docs mightt no have been updated... GHSA-3x5j-9vwr-8rr5 |
@abidlabs I went ahead and attempted to install a suitable frpc binary by modifying he Dockerfile as follows:
This test resulted in the following error displayed in he Jupyter notebook interface:
First, is that the correct I address for he gradio server? It neither responds to ping or is routable via traceroute, from docker, the host server, or any of several other machines accessible o me for testing. Presumably, either the frpc config file became corrupt and his is the wrong target server, or there may be a versioning issue between frpc and frps. What version of FRPS is currently in use on the gradio server? |
@abidlabs Just now saw the OSS release of the huggingface FRP branch. I determined that the aarm64 build of frpc works perfectly, and I recommend i's likely that you can safely push builds for all supported platforms to he hf-media CDN (contingan upon QA workflows). Referring to the upstream github workflows, https://github.com/fatedier/frp/blob/dev/.github/workflows/build-and-push-image.yml#L68 provides a potentially convenien build mechanism and would allow for publicaion of he clien builds, even if not on the HF-media CDN. Absent those builds, I resolved my issue by adding a hf-frp build stage to by development Docker container build, as follows:
Absent the additional platform builds, it may be worthwhile to add some version of this to the primary gradio assembly documentation so users aren' forced to follow the path through (3 or 4) github issues o arrive at this solution |
@abidlabs I got the same very issue running on root@101c6cc65e4a:/app# python server.py
Running on local URL: http://0.0.0.0:7860
Could not create share link. Missing file: /usr/local/lib/python3.9/site-packages/gradio/frpc_linux_aarch64_v0.2.
Please check your internet connection. This can happen if your antivirus software blocks the download of this file. You can install manually by following these steps:
1. Download this file: https://cdn-media.huggingface.co/frpc-gradio-0.2/frpc_linux_aarch64
2. Rename the downloaded file to: frpc_linux_aarch64_v0.2
3. Move the file to this location: /usr/local/lib/python3.9/site-packages/gradio
4. ``` |
Had a similar issue, @hillct suggestion was helpful. However, copying
|
This is how I did it:
|
The "make frpc" command yields a |
Fixed in: #9218 |
Describe the bug
When using Gradio within a Jupyter notebook running on an ARM64 based host, he following message is displayed when calling
.launch(share=True)
When visited, he CDN URL yields a 403 Forbidden response. Needless to say, the expected behavior is for the file to be where the messaging indicates it is located.
I see two possibilities. Either the component was never compiled for aarm64 (or uploaded) through some oversight, or it exists in a different location in which is merely an issue of documentation
Have you searched existing issues? 🔎
Reproduction
Below is a Dockerfile facilitating reproduction. It should be reproducabl on any ARM based hardware including Raspbry Pi and in my case an Nvidia Jetson AGX Orin dev kit.
share=True
It should be noted that I commented out the line in the Dockerfile that would otherwise retrieve the missing file because the file is no available at that URL and the docker image would not build with the error-yielding wget call left in.
Screenshot
No response
Logs
No response
System Info
Severity
Blocking usage of gradio
The text was updated successfully, but these errors were encountered: