Open colindean opened 6 months ago
I have a different but related issue. Behind a company proxy, the error is quite clear
note: connecting to https://relay.fullyjustified.net/default_bundle_v33.tar
error: error sending request for url (https://relay.fullyjustified.net/default_bundle_v33.tar): error trying to connect: dns error: failed to lookup address information: Temporary failure in name resolution
caused by: error trying to connect: dns error: failed to lookup address information: Temporary failure in name resolution
caused by: dns error: failed to lookup address information: Temporary failure in name resolution
caused by: failed to lookup address information: Temporary failure in name resolution
Setting HTTPS_PROXY
gives this
note: resolved to https://data1.fullyjustified.net/tlextras-2022.0r0.tar
note: downloading index https://data1.fullyjustified.net/tlextras-2022.0r0.tar.index.gz
note: downloading SHA256SUM
warning: failure requesting "SHA256SUM" from network
caused by: unexpected HTTP response code 200 OK for URL https://data1.fullyjustified.net/tlextras-2022.0r0.tar
warning: failure requesting "SHA256SUM" from network
caused by: unexpected HTTP response code 200 OK for URL https://data1.fullyjustified.net/tlextras-2022.0r0.tar
warning: failure requesting "SHA256SUM" from network
caused by: unexpected HTTP response code 200 OK for URL https://data1.fullyjustified.net/tlextras-2022.0r0.tar
warning: failure requesting "SHA256SUM" from network
caused by: unexpected HTTP response code 200 OK for URL https://data1.fullyjustified.net/tlextras-2022.0r0.tar
error: failed to retrieve "SHA256SUM" from the network; this most probably is not Tectonic's fault -- please check your network connection.
I’m a bit surprised that "200" is unexpected. Maybe update the error message ? Also, I’m interested in a workaround :)
I’m a bit surprised that "200" is unexpected. Maybe update the error message ?
Tectonic is expecting a 206 Partial Content
response here. The bundle system is designed to only fetch the parts that are used on-the-fly and is issuing HTTP range requests. I guess it would be nice for tectonic
to handle this gracefully though and cache the entire response, but as a workaround you can download the full bundle manually and pass it to --bundle
.
Thanks for pointing me the --bundle
option. Unfortunately, it looks like downloading the archive manually does not work (or the archive is somehowe corrupted ?)
❯ tectonic --bundle tlextras-2022.0r0.tar.index.gz draft error: invalid Zip archive: Could not find central directory end
❯ tectonic --bundle tlextras-2022.0r0.tar draft error: invalid Zip archive: Could not find central directory end The advice give in #685 works though !
❯ tectonic -w https://ttassets.z13.web.core.windows.net/tlextras-2020.0r0.tar draft.tex
On Thursday, July 25th, 2024 at 16:49, Mrmaxmeier @.***> wrote:
I’m a bit surprised that "200" is unexpected. Maybe update the error message ?
Tectonic is expecting a
206 Partial Content
response here. The bundle system is designed to only fetch the parts that are used on-the-fly and is issuing HTTP range requests. I guess it would be nice fortectonic
to handle this gracefully though and cache the entire response, but as a workaround you can download the full bundle manually and pass it to--bundle
.— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.
I've been using tectonic for few years and just now encountered an unexpected error:
I couldn't find anything on the tectonic website about
fullyjustified.net
and that domain bare just redirects to the tectonic website… so clearly it's a project resource!Looking around, I found that
fullyjustified.net
appears in the source in a few places - it's where tectonic gets its packages. OK, that makes perfect sense.When I access those URLs in the error message directly with a browser, I can see that my corporate firewall is blocking the domain. It's been a while since I worked on the document I'm working on today and I'm aware of a more aggressive firewall policy lately, so it's unsurprising that I'd not encountered this until now.
What I'd expect is some kind of something — documentation somewhere — saying that tectonic may connect to this domain. I'm fully aware of tectonic retrieving packages on demand, but I thought they came from CTAN or something else with a more recognizably safe domain.