mako | A lightweight Wayland notification daemon | Video Utils library

I am not expert enough to explain what happened, but I suspect it was because the y-axis ticks were set in the heatmap and then the y-axis ticks were set again. So I think we can remove the tick settings in the heatmap and add a new y-axis and x-axis.

You can use a macro for that.

As described in the manual:

Macros are comparable with functions in regular programming languages. They are useful to put often used idioms into reusable functions to not repeat yourself (“DRY”).

^{Source: https://jinja.palletsprojects.com/en/3.0.x/templates/#macros}

So, given:

After trying for a few days and just found out that pip and python in the project are not pointing to .venv but to anaconda due to an update. when error

no module stdnum

actually there is a problem with pip so make sure your pip path with which pip or which python

1. to solve .venv that doesn't work by deleting the .venv folder, create venv in python, and install all requirements again

Is this the expected behavior or it has something to do with my architecture?

This is the expected behavior. Command alembic revision --autogenerate always creates a new migration file. If no changes exist than it creates an empty one.

You can use alembic-autogen-check to check if your migrations is in sync with models.

Are you sourcing your venv before running test.py?

If so, then try this,

After carefully reading log file, here's what I recommend to do for clean deploy.

While venv is activated and you're in project directory (where manage.py live), do the following:

• Open requirements.txt
• Delete unneeded modules from requirements.txt
• Uninstall unneeded modules with pip uninstall module
• Now run pip freeze requirements.txt
• Deactivate venv
• Then add requirements.txt to source control git add -A
• Commit your changes git commit -m "deleted unneeded modules"
• If you have existed Heroku app, connect to it with heroku git:remote -a myapp, else pass this step
• Deploy, git push heroku master

If you are unsure which modules your project need and I can't determin exactly the project's requirements but if you have basic project, you only need 3 modules which are Django, psycopg2-binary, gunicorn, so do the following for clean deploy:

• Delete venv
• Outside project directory, create new one
• Activate venv
• Install the modules you need, probably Django, psycopg2-binary, gunicorn
• Now run pip freeze requirements.txt
• Deactivate venv
• Then add requirements.txt to source control git add -A
• Commit your changes git commit -m "deleted unneeded modules"
• If you have existed Heroku app, connect to it with heroku git:remote -a myapp, else pass this step
• Deploy, git push heroku master

After Three days of debugging i can tell that there is two steps for the solution to work:

firstly: Try to reinstall pwntools package by removing it firstly and then install it

Searching for the exception, leads to the corresponding eventlet issue: https://github.com/eventlet/eventlet/issues/687

The summary is that eventlet (0.32.0) is currently not compatible with Python 3.10 because it tries to patch types that have become immutable in Python 3.10.

Like with your requirements, it is good practice to be more specific with your Docker dependencies too. Today using the tag 3 for the Python Docker image will give you 3.10.0, unless it is using a cache. In the future it could be a different version. Since there is a compatibility issue with Python 3.10, use Python 3.9 - the currently latest Python 3.9 Docker tag is 3.9.7.

i.e. it should work once you change your first line of the Dockerfile to:

If you have a look for the base image, you could see it just be updated 27hours ago.