-
-
Notifications
You must be signed in to change notification settings - Fork 749
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
Unknown encoding cp437 #689
Comments
@vogt31337 sounds like you might need to define custom http probes for your endpoints. You can use the Additional info for others when you have non-server CLI apps: For a CLI app you need to configure the slim command to run the app in the container. There are a few options for that. You can use the You can also use the |
@kcq, thanks for the answer, but I realized that my description wasn't clear enough: The software is running, the webserver is working and processing requests. But when it tries to read an xml file it crashes with this "unknown encoding error". My idea is that slim removes codepages (I have no clue where in linux they are stored) and therefore reading and processing a file not in utf-8 produces such errors. Since the software is running non dockerized and in a fat container, it must be due to the slimification process... |
@vogt31337 are you using FastAPI for your python server app by any chance? If so, it exposes an openapi spec that can be used to generate additional interactions with the app. |
Yeah I am using fastapi, but again that ist Not the Problem (the swagger Style documentation works). Reading an XML File from a mounted storage fails with this encoding Error. |
Expected Behavior
I've built a python web server application which reads zip and xml files, modifies and writes them. Everything works fine until a slimified version is created.
Actual Behavior
Application crashes with - ERROR - unknown encoding: cp437
Without slimification it works fine.
Maybe slim did remove the codepage. This behaviour is nowhere mentioned or documented.
Specifications
The text was updated successfully, but these errors were encountered: