2018-01-16T20:22:10Z

The Flask Mega-Tutorial Part VII: Error Handling

This is the seventh installment of the Flask Mega-Tutorial series, in which I'm going to tell you how to do error handling in a Flask application.

For your reference, below is a list of the articles in this series.

Note 1: If you are looking for the legacy version of this tutorial, it's here.

Note 2: If you would like to support my work on this blog, or just don't have patience to wait for weekly articles, I am offering the complete version of this tutorial packaged as an ebook or a set of videos. For more information, visit courses.miguelgrinberg.com.

In this chapter I'm taking a break from coding new features into my microblog application, and instead will discuss a few strategies to deal with bugs, which invariably make an appearance in any software project. To help illustrate this topic, I intentionally let a bug slip in the code that I've added in Chapter 6. Before you continue reading, see if you can find it!

The GitHub links for this chapter are: Browse, Zip, Diff.

Error Handling in Flask

What happens when an error occurs in a Flask application? The best way to find out is to experience it first hand. Go ahead and start the application, and make sure you have at least two users registered. Log in as one of the users, open the profile page and click the "Edit" link. In the profile editor, try to change the username to the username of another user that is already registered, and boom! This is going to bring a scary looking "Internal Server Error" page:

Internal Server Error

If you look in the terminal session where the application is running, you will see a stack trace of the error. Stack traces are extremely useful in debugging errors, because they show the sequence of calls in that stack, all the way to the line that produced the error:

(venv) $ flask run
 * Serving Flask app "microblog"
 * Running on http://127.0.0.1:5000/ (Press CTRL+C to quit)
[2017-09-14 22:40:02,027] ERROR in app: Exception on /edit_profile [POST]
Traceback (most recent call last):
  File "/home/miguel/microblog/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1182, in _execute_context
    context)
  File "/home/miguel/microblog/venv/lib/python3.6/site-packages/sqlalchemy/engine/default.py", line 470, in do_execute
    cursor.execute(statement, parameters)
sqlite3.IntegrityError: UNIQUE constraint failed: user.username

The stack trace indicates what is the bug. The application allows a user to change the username, and does not validate that the new username chosen does not collide with another user already in the system. The error comes from SQLAlchemy, which tries to write the new username to the database, but the database rejects it because the username column is defined with unique=True.

It is important to note that the error page that is presented to the user does not provide much information about the error, and that is good. I definitely do not want users to learn that the crash was caused by a database error, or what database I'm using, or what are some of the table and field names in my database. All that information should be kept internal.

There are a few things that are far from ideal. I have an error page that is very ugly and does not match the application layout. I also have important application stack traces being dumped on a terminal that I need to constantly watch to make sure I don't miss any errors. And of course I have a bug to fix. I'm going to address all these issues, but first, let's talk about Flask's debug mode.

Debug Mode

The way you saw that errors are handled above is great for a system that is running on a production server. If there is an error, the user gets a vague error page (though I'm going to make this error page nicer), and the important details of the error are in the server process output or in a log file.

But when you are developing your application, you can enable debug mode, a mode in which Flask outputs a really nice debugger directly on your browser. To activate debug mode, stop the application, and then set the following environment variable:

(venv) $ export FLASK_DEBUG=1

If you are on Microsoft Windows, remember to use set instead of export.

After you set FLASK_DEBUG, restart the server. The output on your terminal is going to be slightly different than what you are used to see:

(venv) microblog2 $ flask run
 * Serving Flask app "microblog"
 * Forcing debug mode on
 * Running on http://127.0.0.1:5000/ (Press CTRL+C to quit)
 * Restarting with stat
 * Debugger is active!
 * Debugger PIN: 177-562-960

Now make the application crash one more time to see the interactive debugger in your browser:

Flask Debugger

The debugger allows you expand each stack frame and see the corresponding source code. You can also open a Python prompt on any of the frames and execute any valid Python expressions, for example to check the values of variables.

It is extremely important that you never run a Flask application in debug mode on a production server. The debugger allows the user to remotely execute code in the server, so it can be an unexpected gift to a malicious user who wants to infiltrate your application or your server. As an additional security measure, the debugger running in the browser starts locked, and on first use will ask for a PIN number, which you can see in the output of the flask run command.

Since I am in the topic of debug mode, I should mention the second important feature that is enabled with debug mode, which is the reloader. This is a very useful development feature that automatically restarts the application when a source file is modified. If you run flask run while in debug mode, you can then work on your application and any time you save a file, the application will restart to pick up the new code.

Custom Error Pages

Flask provides a mechanism for an application to install its own error pages, so that your users don't have to see the plain and boring default ones. As an example, let's define custom error pages for the HTTP errors 404 and 500, the two most common ones. Defining pages for other errors works in the same way.

To declare a custom error handler, the @errorhandler decorator is used. I'm going to put my error handlers in a new app/errors.py module.

app/errors.py: Custom error handlers

from flask import render_template
from app import app, db

@app.errorhandler(404)
def not_found_error(error):
    return render_template('404.html'), 404

@app.errorhandler(500)
def internal_error(error):
    db.session.rollback()
    return render_template('500.html'), 500

The error functions work very similarly to view functions. For these two errors, I'm returning the contents of their respective templates. Note that both functions return a second value after the template, which is the error code number. For all the view functions that I created so far, I did not need to add a second return value because the default of 200 (the status code for a successful response) is what I wanted. In this case these are error pages, so I want the status code of the response to reflect that.

The error handler for the 500 errors could be invoked after a database error, which was actually the case with the username duplicate above. To make sure any failed database sessions do not interfere with any database accesses triggered by the template, I issue a session rollback. This resets the session to a clean state.

Here is the template for the 404 error:

app/templates/404.html: Not found error template

{% extends "base.html" %}

{% block content %}
    <h1>File Not Found</h1>
    <p><a href="{{ url_for('index') }}">Back</a></p>
{% endblock %}

And here is the one for the 500 error:

app/templates/500.html: Internal server error template

{% extends "base.html" %}

{% block content %}
    <h1>An unexpected error has occurred</h1>
    <p>The administrator has been notified. Sorry for the inconvenience!</p>
    <p><a href="{{ url_for('index') }}">Back</a></p>
{% endblock %}

Both templates inherit from the base.html template, so that the error page has the same look and feel as the normal pages of the application.

To get these error handlers registered with Flask, I need to import the new app/errors.py module after the application instance is created:

app/__init__.py: Import error handlers

# ...

from app import routes, models, errors

If you set FLASK_DEBUG=0 in your terminal session and then trigger the duplicate username bug one more time, you are going to see a slightly more friendly error page.

Custom 500 Error Page

Sending Errors by Email

The other problem with the default error handling provided by Flask is that there are no notifications, stack trace for errors are printed to the terminal, which means that the output of the server process needs to be monitored to discover errors. When you are running the application during development, this is perfectly fine, but once the application is deployed on a production server, nobody is going to be looking at the output, so a more robust solution needs to be put in place.

I think it is very important that I take a proactive approach regarding errors. If an error occurs on the production version of the application, I want to know right away. So my first solution is going to be to configure Flask to send me an email immediately after an error, with the stack trace of the error in the email body.

The first step is to add the email server details to the configuration file:

config.py: Email configuration

class Config(object):
    # ...
    MAIL_SERVER = os.environ.get('MAIL_SERVER')
    MAIL_PORT = int(os.environ.get('MAIL_PORT') or 25)
    MAIL_USE_TLS = os.environ.get('MAIL_USE_TLS') is not None
    MAIL_USERNAME = os.environ.get('MAIL_USERNAME')
    MAIL_PASSWORD = os.environ.get('MAIL_PASSWORD')
    ADMINS = ['your-email@example.com']

The configuration variables for email include the server and port, a boolean flag to enable encrypted connections, and optional username and password. The five configuration variables are sourced from their environment variable counterparts. If the email server is not set in the environment, then I will use that as a sign that emailing errors needs to be disabled. The email server port can also be given in an environment variable, but if not set, the standard port 25 is used. Email server credentials are by default not used, but can be provided if needed. The ADMINS configuration variable is a list of the email addresses that will receive error reports, so your own email address should be in that list.

Flask uses Python's logging package to write its logs, and this package already has the ability to send logs by email. All I need to do to get emails sent out on errors is to add a SMTPHandler instance to the Flask logger object, which is app.logger:

app/__init__.py: Log errors by email

import logging
from logging.handlers import SMTPHandler

# ...

if not app.debug:
    if app.config['MAIL_SERVER']:
        auth = None
        if app.config['MAIL_USERNAME'] or app.config['MAIL_PASSWORD']:
            auth = (app.config['MAIL_USERNAME'], app.config['MAIL_PASSWORD'])
        secure = None
        if app.config['MAIL_USE_TLS']:
            secure = ()
        mail_handler = SMTPHandler(
            mailhost=(app.config['MAIL_SERVER'], app.config['MAIL_PORT']),
            fromaddr='no-reply@' + app.config['MAIL_SERVER'],
            toaddrs=app.config['ADMINS'], subject='Microblog Failure',
            credentials=auth, secure=secure)
        mail_handler.setLevel(logging.ERROR)
        app.logger.addHandler(mail_handler)

As you can see, I'm only going to enable the email logger when the application is running without debug mode, which is indicated by app.debug being True, and also when the email server exists in the configuration.

Setting up the email logger is somewhat tedious due to having to handle optional security options that are present in many email servers. But in essence, the code above creates a SMTPHandler instance, sets its level so that it only reports errors and not warnings, informational or debugging messages, and finally attaches it to the app.logger object from Flask.

There are two approaches to test this feature. The easiest one is to use the SMTP debugging server from Python. This is a fake email server that accepts emails, but instead of sending them, it prints them to the console. To run this server, open a second terminal session and run the following command on it:

(venv) $ python -m smtpd -n -c DebuggingServer localhost:8025

Leave the debugging SMTP server running and go back to your first terminal and set export MAIL_SERVER=localhost and MAIL_PORT=8025 in the environment (use set instead of export if you are using Microsoft Windows). Make sure the FLASK_DEBUG variable is set to 0 or not set at all, since the application will not send emails in debug mode. Run the application and trigger the SQLAlchemy error one more time to see how the terminal session running the fake email server shows an email with the full stack trace of the error.

A second testing approach for this feature is to configure a real email server. Below is the configuration to use your Gmail account's email server:

export MAIL_SERVER=smtp.googlemail.com
export MAIL_PORT=587
export MAIL_USE_TLS=1
export MAIL_USERNAME=<your-gmail-username>
export MAIL_PASSWORD=<your-gmail-password>

If you are using Microsoft Windows, remember to use set instead of export in each of the statements above.

The security features in your Gmail account may prevent the application from sending emails through it unless you explicitly allow "less secure apps" access to your Gmail account. You can read about this here, and if you are concerned about the security of your account, you can create a secondary account that you configure just for testing emails, or you can enable less secure apps only temporarily to run this test and then revert back to the default.

Logging to a File

Receiving errors via email is nice, but sometimes this isn't enough. There are some failure conditions that do not end in a Python exception and are not a major problem, but they may still be interesting enough to save for debugging purposes. For this reason, I'm also going to maintain a log file for the application.

To enable a file based log another handler, this time of type RotatingFileHandler, needs to be attached to the application logger, in a similar way to the email handler.

app/__init__.py: Logging to a file

# ...
from logging.handlers import RotatingFileHandler
import os

# ...

if not app.debug:
    # ...

    if not os.path.exists('logs'):
        os.mkdir('logs')
    file_handler = RotatingFileHandler('logs/microblog.log', maxBytes=10240,
                                       backupCount=10)
    file_handler.setFormatter(logging.Formatter(
        '%(asctime)s %(levelname)s: %(message)s [in %(pathname)s:%(lineno)d]'))
    file_handler.setLevel(logging.INFO)
    app.logger.addHandler(file_handler)

    app.logger.setLevel(logging.INFO)
    app.logger.info('Microblog startup')

I'm writing the log file with name microblog.log in a logs directory, which I create if it doesn't already exist.

The RotatingFileHandler class is nice because it rotates the logs, ensuring that the log files do not grow too large when the application runs for a long time. In this case I'm limiting the size of the log file to 10KB, and I'm keeping the last ten log files as backup.

The logging.Formatter class provides custom formatting for the log messages. Since these messages are going to a file, I want them to have as much information as possible. So I'm using a format that includes the timestamp, the logging level, the message and the source file and line number from where the log entry originated.

To make the logging more useful, I'm also lowering the logging level to the INFO category, both in the application logger and the file logger handler. In case you are not familiar with the logging categories, they are DEBUG, INFO, WARNING, ERROR and CRITICAL in increasing order of severity.

As a first interesting use of the log file, the server writes a line to the logs each time it starts. When this application runs on a production server, these log entries will tell you when the server was restarted.

Fixing the Duplicate Username Bug

I have exploited the username duplication bug for too long. Now that I have showed you how to prepare the application to handle this type of errors, I can go ahead and fix it.

If you recall, the RegistrationForm already implements validation for usernames, but the requirements of the edit form are slightly different. During registration, I need to make sure the username entered in the form does not exist in the database. On the edit profile form I have to do the same check, but with one exception. If the user leaves the original username untouched, then the validation should allow it, since that username is already assigned to that user. Below you can see how I implemented the username validation for this form:

app/forms.py: Validate username in edit profile form.

class EditProfileForm(FlaskForm):
    username = StringField('Username', validators=[DataRequired()])
    about_me = TextAreaField('About me', validators=[Length(min=0, max=140)])
    submit = SubmitField('Submit')

    def __init__(self, original_username, *args, **kwargs):
        super(EditProfileForm, self).__init__(*args, **kwargs)
        self.original_username = original_username

    def validate_username(self, username):
        if username.data != self.original_username:
            user = User.query.filter_by(username=self.username.data).first()
            if user is not None:
                raise ValidationError('Please use a different username.')

The implementation is in a custom validation method, but there is an overloaded constructor that accepts the original username as an argument. This username is saved as an instance variable, and checked in the validate_username() method. If the username entered in the form is the same as the original username, then there is no reason to check the database for duplicates.

To use this new validation method, I need to add the original username argument in the view function, where the form object is created:

app/routes.py: Validate username in edit profile form.

@app.route('/edit_profile', methods=['GET', 'POST'])
@login_required
def edit_profile():
    form = EditProfileForm(current_user.username)
    # ...

Now the bug is fixed and duplicates in the edit profile form will be prevented in most cases. This is not a perfect solution, because it may not work when two or more processes are accessing the database at the same time. In that situation, a race condition could cause the validation to pass, but a moment later when the rename is attempted the database was already changed by another process and cannot rename the user. This is somewhat unlikely except for very busy applications that have a lot of server processes, so I'm not going to worry about it for now.

At this point you can try to reproduce the error one more time to see how the new form validation method prevents it.

213 comments

  • #201 Avner said 2020-07-10T06:56:03Z

    Miguel, sorry for the third email in a row.

    One thing I notice is the different behavior between running in DEBUG (FLASK_DEBUG=1) vs non debug mode I removed the condition on non-debug in init.py and I always set mail_handler. In debug mode if I log an error message e.g. "current_app.logger.error('foo')" I do get a message in the smtp server, just like in the non-debug mode - good!

    But if I trigger an error (e.g. by dividing by 0), I don't get a message in the smtp server. Only if in non-debug mode, a message with the stack trace appears. Why is this?

  • #202 Miguel Grinberg said 2020-07-10T08:53:11Z

    @Avner: the emails are intended to be sent for a production deployment. It would not make sense to send emails when you are running the app in your own machine during development. Note the if not app.debug conditional under which all this is done. If you remove that then the emails will be sent in debug mode as well.

  • #203 Avner said 2020-07-10T21:36:26Z

    Yes, eventually, I will only apply the email only in production mode. But until I get it right, I want the emails to be sent also in debug mode. In microblog code, I removed the "if not app.debug" conditional, and I do get emails for log messages in debug mode as well. But I'm do not get emails with stack traces when exception occurs (e.g. division by 0, without any logging).

  • #204 Avner said 2020-07-11T01:50:54Z

    Ok, I found out. In development mode, the default for app.config['PROPAGATE_EXCEPTIONS'] is True In this case, the stack trace can be viewed by tailing the log of the container, but an email is not sent.

    In production mode, the default for app.config['PROPAGATE_EXCEPTIONS'] is False In this case, the stack trace is not viewed by tailing the log of the container, but an email is sent.

    To get the same behavior in development mode, like in production mode, app.config['PROPAGATE_EXCEPTIONS'] needs to be set to False

    https://flask.palletsprojects.com/en/1.1.x/config/

  • #205 Miguel Grinberg said 2020-07-11T08:48:38Z

    @Avner: Yes. The behavior on errors is different in debug vs. production mode.

  • #206 Olivia said 2020-07-14T02:27:27Z

    Hi Miguel! Thanks for the tutorial. Not sure if you're still updating this tutorial but I wasn't able to turn on debug mode by setting FLASK_DEBUG to 1 on windows. After a little bit of research, it appears that in Flask1.0 and above we need to do $env:FLASK_ENV = "development" to turn on debug mode for flask on windows.

  • #207 Miguel Grinberg said 2020-07-14T14:17:32Z

    @Olivia: I just tested this here, and FLASK_DEBUG continues to work as documented in this tutorial. Not sure why it did not work for you.

  • #208 Edward Friesema said 2020-07-14T23:58:11Z

    I tried the email handler and it worked. But while the system creates a microblog.log file there is nothing in it. Even after I've started up the server and done some operations several times.. Will this only write to a log when I am running on a WSGI production server, not on the current development server? I added file_handler to the app logger even though this wasn't a step in the tutorial. I'm running Python 3.8 on a windows 10 machine here is my init code. no crashing errors occur when I ran the app

    if not app.debug: if app.config['MAIL_SERVER']: auth = None if app.config['MAIL_USERNAME'] or app.config['MAIL_PASSWORD']: auth = (app.config['MAIL_USERNAME'], app.config['MAIL_PASSWORD']) secure = None if app.config['MAIL_USE_TLS']: secure = () mail_handler = SMTPHandler( mailhost = (app.config['MAIL_SERVER'], app.config['MAIL_PORT']), fromaddr = 'no-reply@' + app.config['MAIL_SERVER'], toaddrs = app.config['ADMINS'], subject = 'Microblog Failure', credentials = auth, secure = secure) mail_handler.setLevel(logging.ERROR) app.logger.addHandler(mail_handler) if not os.path.exists('logs'): os.mkdir('logs') file_handler = RotatingFileHandler('logs/microblog.log', maxBytes=10240, backupCount=10) file_handler.setFormatter(logging.Formatter('%(asctime)s %(levelname)s: %(message)s [in %(pathname)s :%(lineno)d]')) file_handler.setLevel(logging.INFO)

    app.logger.addHandler(file_handler) app.logger.info('Microblog startup')
  • #209 Miguel Grinberg said 2020-07-15T13:48:45Z

    @Edward: this whole block of code you copied is enclosed in an if not app.debug conditional. That means that it will only be used when you run without debug mode.

  • #210 Avner said 2020-07-17T21:48:50Z

    Hi Miguel,

    In the legacy edition, there are chapters Unit Testing - https://blog.miguelgrinberg.com/post/the-flask-mega-tutorial-part-vii-unit-testing-legacy Debugging, testing and profiling - https://blog.miguelgrinberg.com/post/the-flask-mega-tutorial-part-xvi-debugging-testing-and-profiling

    These chapters have sub-sections that I cannot find in the new edition: In the Unit Testing chapter: - Unit testing framework - uses the python module unittest and a file tests.py

    In the Debugging, testing and profiling chapter: - Using the Python Debugger - Regression Testing - Test Coverage - Profiling for performance - Database Performance

    I'm curious: Did I miss them in the new edition? Why were they omitted? Is there new technology (e.g. new python packages, Jenkins), for testing, that you recommend?

  • #211 Miguel Grinberg said 2020-07-18T14:04:48Z

    @Avner: I decided to re-organize the content and make it more relevant. I haven't removed the old content, so if you find that useful you can still get it.

  • #212 Avner Moshkovitz said 2020-08-07T17:04:21Z

    Miguel, thank you (once again) for putting this thorough tutorial. The organization of the tutorial is great. I can tap in and out to various sections as needed, and each section stands for itself and can be addressed separately. I have a logging question.

    I have a webapp that is running flask within docker. In flask, I am using a logger. I set the logger with several handlers (e.g. file_handler, stream_handler, etc..) For sake of testing I then remove all the handlers. I also remove the default_handler (see (here)) https://flask.palletsprojects.com/en/1.1.x/logging/#removing-the-default-handler

    According to (here) If the root logger has no handlers configured, Werkzeug adds a StreamHandler to its logger https://flask.palletsprojects.com/en/1.1.x/logging/#werkzeug So I also remove handler to the Werkzeug logger

    But I'm still seeing print-outs in stdout (e.g. INFO:app:foo3) How can this happen?

    Thanks, Avi

    p.s. note1 If I do not remove the StreamHandler I do see another line (formatted) in stdout as expected: 2020-08-06 19:03:11,708 INFO: foo4 [in /usr/src/app/web/app/api/sites.py:274] (and the line "INFO:app:foo4" still shows up)

    note2 the print of "foo1" which uses the exact same logger command: "current_app.logger.info('foo1')" is filtered out, when called from app/init.py, from create_app() but not when called from the file app/api/sites.py

    cat app/init.py import logging from logging.handlers import SMTPHandler, RotatingFileHandler from flask.logging import default_handler ...

    def create_app(config_class=Config): ... formatter = logging.Formatter('%(asctime)s %(levelname)s: %(message)s ' '[in %(pathname)s:%(lineno)d]') stream_handler = logging.StreamHandler() stream_handler.setFormatter(formatter) stream_handler.setLevel(logging.INFO) app.logger.addHandler(stream_handler)

    print( 'app.logger.handlers', app.logger.handlers ) app.logger.removeHandler(app.logger.handlers[0]) app.logger.removeHandler(app.logger.handlers[0]) app.logger.removeHandler(app.logger.handlers[0]) app.logger.removeHandler(default_handler) print( 'app.logger.handlers after removal of handlers', app.logger.handlers ) app.logger.setLevel(logging.DEBUG)

    ...

    app.app_context().push() current_app.logger.info('foo1')

    cat app/api/sites.py ... @bp.route('/api/v1_2/foo3', methods=['POST']) def foo3(group_id = 1): print( 'current_app.logger.handlers', current_app.logger.handlers ) current_app.logger.info('foo3')

    werkzeug_logger = logging.getLogger('werkzeug') werkzeug_logger.setLevel(logging.ERROR) print( 'werkzeug_logger.handlers', werkzeug_logger.handlers ) werkzeug_logger.removeHandler(werkzeug_logger.handlers[0]) print( 'werkzeug_logger.handlers2', werkzeug_logger.handlers ) current_app.logger.info('foo4')

    docker logs -f webserver_web_1 ... app.logger.handlers [<NullHandler (NOTSET)>, <SSLSMTPHandler (ERROR)>, <StreamHandler <stderr> (INFO)>] app.logger.handlers after removal of handlers [] ...

    current_app.logger.handlers [] INFO:app:foo3 werkzeug_logger.handlers [<StreamHandler <stderr> (NOTSET)>] werkzeug_logger.handlers2 [] INFO:app:foo4

  • #213 Miguel Grinberg said 2020-08-07T18:27:23Z

    @Avner: I can't really tell you what's wrong, but this is easy enough to debug for you, right? Why don't you inspect the loggers to see what other handlers you missed to remove?

Leave a Comment