Zillion: webhost config fix #2145
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I've deployed the fix to the webhost, on first glance it seems to work. |
black-sliver
approved these changes
Sep 9, 2023
ThePhar
added
the
is: bug/fix
FlySniper
pushed a commit
to FlySniper/Archipelago
that referenced
this pull request
Nov 14, 2023
Jouramie
pushed a commit
to Jouramie/Archipelago
that referenced
this pull request
Feb 28, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is this fixing or adding?
Zillion generation on archipelago.gg is failing.
https://discord.com/channels/731205301247803413/1147772247562534996
How was this tested?
I can't reproduce this with my own webhost. Generation works when I run
WebHost.pyI don't know how the archipelago.gg webhost is configured to make this happen.This seems like it should fix it based on the error message I see, but without being able to reproduce the webhost configuration, I don't see a way to test whether this fixes the problem.
I made sure it didn't cause any new generation problems with my configuration.