Skip to content

TeX Servers Down results in hidden unexpected behaviors #28

@xronosuf

Description

@xronosuf

When trying to build the ximeraManuals server, I got some weird missing package errors that prevented a build. After some investigating I discovered a bunch of the TeX archive servers were down and so a bunch of the packages that should have been installed as part of the container building weren't.

If possible, it would be good to detect if something like this happens and output as an error when the container builds or something, so that new users don't think they have messed up something, resulting in the manual not building. I realize this is a somewhat niche problem, but I think the greater take-away is that it would be ideal to have some sort of "sanity check" at the end of the container building, that can determine if everything executed as expected, or if anything went awry in the process, then output that as a notification. This could also serve as a way to tell a user when the container is fully built, instead of telling them to wait until button appear and spinning wheels finish, or whatnot.

This is merely a suggestion, as I don't know the complexities of this setup process to know how feasible this is - I'm tagging @wiobber to see if he has thoughts.

Metadata

Metadata

Assignees

Labels

enhancementNew feature or requestquestionFurther information is requested

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions