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
Occasional 500 instead of 404 #525
Comments
Hey @pawamoy! Thanks for reporting this! Sad to hear about the struggle and sorry for the inconvenience. Looking at the error output, it's linked to the internal workings of the Intuitively, it looks like an internal hiccup with error templates, and the way it performs lookups, with our built-in What would be very interesting: could you somehow log the exact routes that are being called on the Thanks and sorry once again ✌️ |
Thank you for your help @dee-me-tree-or-love! And no need to apologize 🙇 If/when it happens again, I'll post the routes that are hit by pip/pdm! |
Great, thank you so much @pawamoy. Happy to hear this helps, and thank you for your understanding 🌟
Great! This is good to know, and indeed, if you run into this again, please do let me know.
Awesome! I will keep this issue in mind still, it only further supports my intuition that it's about time to start moving towards (replacing or supporting) something other than bottle too! 😁 |
Sometimes I have to restart pypi-server becauses it sends error 500 instead of 404. For example a tool (PDM or pip) is querying pytest on it, and it doesn't have pytest, so it should answer with a 404, but instead I get this in the logs (it's pypi-server's HTML output):
If I stop and restart pypi-server, the error goes away.
I'm running the server like this, from Python directly (part of another project):
....where
dist_dir
is an existing directory.The text was updated successfully, but these errors were encountered: