-
Notifications
You must be signed in to change notification settings - Fork 24
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
Unavailable external font resource #68
Comments
On the following day, I was able to successfully generate reports using the same data and code. Upon running a third attempt, again the same error as above was displayed. I suspected that the website may be tracking external users with the user's IP address. I exited RStudio and used a VPN to connect to a university network, then started RStudio and re-ran the code. The code that had failed three minutes before completed successfully. If the fontawesome site is blocking users, or imposing a quota limit, due to the demand generated by generateReport(), it would be useful to find a different way to meet font requirements that arise during report generation. |
Hi Peter,
Wow, thanks for this update. Definitely something we'll have to look into.
Howard - I guess there should be ways that we can package up all the fonts
we need inside our package, and avoid attempts to download fonts?
Though it seems odd to me (naively) that the package would want to keep
downloading the fonts over and over. I'm ignorant as to how that part works
though.
Rob
…On Tue, 20 Apr 2021 at 23:16, Peter B. Pearman ***@***.***> wrote:
On the following day, I was able to successfully generate reports using
the same data and code. Upon running a third attempt, again the same error
as above was displayed. I suspected that the website may be tracking
external users with the user's IP address. I exited RStudio and used a VPN
to connect to a university network, then started RStudio and re-ran the
code. The code that had failed three minutes before completed successfully.
If the fontawesome site is blocking users due to the demand generated by
generateReport(), it would be useful to find a different way to meet font
requirements that arise during report generation.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#68 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAG2SE4X7XPHGME32VAFQQ3TJV5CDANCNFSM43GMKNNA>
.
--
Rob Lanfear
Division of Ecology and Evolution,
Research School of Biology,
The Australian National University,
Canberra
www.robertlanfear.com
|
I have been using SangerAlignment(), launchApp() and generateReport() all afternoon. Suddenly I started getting the following error, which appears to indicate that an external resource is not available:
....a lot of standard knitr output as before.... (followed by)
pandoc: Could not fetch https://pro.fontawesome.com/releases/v5.10.0/css/../webfonts/fa-regular-400.eot
FailedConnectionException2 "pro.fontawesome.com" 443 True sendBuf: resource vanished (Broken pipe)
Error: pandoc document conversion failed with error 67
I have tried closing and restarting RStudio,and loading the library again. In any case, code that was functioning 15 minutes ago now produces this error. Is this really a failure to connect to an external resource, or does it only look that way?
If so, it would be great if generateReport() were not vulnerable to the whims of other websites. Is this really the issue, or is something else going on? How can I determine that?
--Peter
The text was updated successfully, but these errors were encountered: