Debugging Randomly Failing Tests with Reproducible Random Seeds
There are two things I despise in this world: dealing with printers that don’t work and debugging randomly failing tests.
Web development with epic service!
There are two things I despise in this world: dealing with printers that don’t work and debugging randomly failing tests.
At DjangoCon 2024, I gave a lightning talk about improving the experience for new Django developers. While Django is an incredibly powerful framework, there’s one aspect of the initial developer experience that I believe we can significantly enhance. Let’s explore the current onboarding experience and how we might make it more intuitive for newcomers.
When running Docker Compose for our project, which has a service for serving Python processes and another service for running Node processes, we started getting random permission errors like the following.
Since Heroku no longer has a free plan, I wanted to try out fly.io that I’ve heard about as an alternative to Heroku. For me there is no better way to try it than to use my Django Base Site. In the past, I made sure that my starter template project worked with Heroku, so it makes sense that I should try it out with a new and up and coming PaaS.
I was working on my Django Base Site project when I discovered a test was failing in a GitHub Action when trying to run Django’s collectstatic manager command. It was failing in Python with the error, PermissionError: [Errno 13] Permission denied: '/srv/app/collected_static'.
Serializing Django view context data for use in Javascript is something I’ve always thought should be extremely easy, but any time you have data that is more then a simple data type like a string or an integer, it can get complicated pretty quickly and can end up causing hard-to-solve bugs.