Closed krassowski closed 4 years ago
Hmm ... well, I'm not very sure how to debug these issues in detail, but I've tried submitting an updated build (labeled 0.1.12 h...._2
) that should make it to the servers soon. Can you please try it and see if it fixes your problem?
The newer build is looking even stranger, as it apparently has a bunch of python in it, and maybe git (this is the output of diffoscope
):
Weird! Those stray files seem to represent an issue recent versions of the Python package. Reported as conda-forge/python-feedstock#384.
I will check for a workaround.
OK, we have marked those Python packages as broken and I have just merged a recipe for a new package, build number 3, that should hopefully fix those issues. Please let me know if it works for you.
Many thanks @pkgw for a very quick reply and the fixes! It seems that the original problem with missing libraries was fixed in h4f32bc4_3
but overall it still does not work great on Windows (while working on Linux and MacOs), failing with error: Zlib error
, see below for details.
@krassowski Yikes, I'm not sure what that would be — that's a shouldn't-happen kind of bug. Unfortunately I don't have a ton of bandwidth to investigate these days ... any chance that you would be able to use a debugger to investigate what's going on? I know that's a big ask.
We have a (usually) working binder for that downstream, but perhaps I can PR a more thorough test on this feedstock that will exercise the machinery a bit more, and give us some more detailed info.
Adding a sanity check build to this feedstock over on https://github.com/conda-forge/tectonic-feedstock/pull/24 also demonstrates the windows issue... I'll do some more google trawling, now that we have something reproducible...
by the by: it's really a bummer to have conda do all the "hard" stuff of fulfilling the binary dependencies... to then have to grab seemingly a few hundred files off archive.org the first time tectonic
is invoked. Do you think some of this could be pre-cached during the build, and made available as a tectonic-base-deps
or something? Pre-activate scripts are the devil, but being able to set the tectonic cache path seems like it would be a big win.
@bollwyvl Thanks for working on this! All of the data handling should be quite cross-platform so I'm not sure why this problem is only showing up on Windows, but ... that's what debugging is for.
As for your other comment: yes, it's not ideal. My preferred solution would be to create a new Tectonic CLI that has what I call a "Swiss Army knife" style, with subcommands like git
, and then implement a command like tectonic bootstrap
or tectonic import-cache
that could enable a pre-warm of the cache .... as well as many other useful functions that I can't really provide right now because I don't want the CLI to be one of those --activate-totally-bizarre-other-mode --with-strange-info
ones. The only barrier to making this happen is just a lack of time on my part. (edit: FWIW if someone else wanted to prototype this I would be ecstatic!)
Oh, this issue has been fixed for a while, I believe.
Issue: We are using tectonic for LSP-latex integration testing with Azure Pipelines. It worked well so far, but a recent change of conda environment seem to have broken the jobs on Windows. Linux and MacOS worked ok. On Windows, it returns 3221225785 exit status, which seem to suggest missing dlls.
Since the previous successful run on Windows the tectonic version did not change, but the build version did:
success:
failure:
The h11def9f_0 binary is bigger (2.9 MB) than h87e793b_1 (2.8 MB) and is labelled with
cf202003
:It could be related to this rebuild: https://github.com/conda-forge/tectonic-feedstock/pull/20
I changed the channel specifier to get the build 0 (labelled
cf202003
) as:in a pull request https://github.com/krassowski/jupyterlab-lsp/pull/320, which made all work again. This was the only change in the environment.
For the details of the run, please see: https://dev.azure.com/krassowskimichal/jupyterlab-lsp/_build/results?buildId=742&view=logs&j=c1ff525e-18e3-5932-41ad-b3b1d5f9697a
Environment (
conda list
):Details about
conda
and system (conda info
):