feat(django): Instrument database commits

[alexander-alderman-webb]

Description

Issues

Reminders

• Please add tests to validate your changes, and lint your code using tox -e linters.
• Add GH Issue ID & Linear ID (if applicable)
• PR title should use conventional commit style (feat:, fix:, ref:, meta:)
• For external contributors: CONTRIBUTING.md, Sentry SDK development docs, Discord community

[codecov]

❌ 11 Tests Failed:

Tests completed	Failed	Passed	Skipped
28879	11	28868	2260

View the top 3 failed test(s) by shortest run time

tests.integrations.django.test_db_query_data::test_db_no_autocommit_execute

Stack Traces | 0.761s run time

.tox/py3.7-django-v1.11.29/lib/python3.7.../management/commands/flush.py:69: in handle
    savepoint=connection.features.can_rollback_ddl):
.tox/py3.7-django-v1.11.29/lib/python3.7.../django/db/transaction.py:165: in __enter__
    "Your database backend doesn't behave properly when "
E   django.db.transaction.TransactionManagementError: Your database backend doesn't behave properly when autocommit is off. Turn it on before using 'atomic'.

During handling of the above exception, another exception occurred:
.tox/py3.7-django-v1.11.29/lib/python3.7.../django/test/testcases.py:925: in _post_teardown
    self._fixture_teardown()
.tox/py3.7-django-v1.11.29/lib/python3.7.../django/test/testcases.py:960: in _fixture_teardown
    inhibit_post_migrate=inhibit_post_migrate)
.tox/py3.7-django-v1.11.29/lib/python3.7.../core/management/__init__.py:131: in call_command
    return command.execute(*args, **defaults)
.tox/py3.7-django-v1.11.29/lib/python3.7.../core/management/base.py:330: in execute
    output = self.handle(*args, **options)
.tox/py3.7-django-v1.11.29/lib/python3.7.../management/commands/flush.py:82: in handle
    six.reraise(CommandError, CommandError(new_msg), sys.exc_info()[2])
.tox/py3.7-django-v1.11.29/lib/python3.7.../django/utils/six.py:685: in reraise
    raise value.with_traceback(tb)
.tox/py3.7-django-v1.11.29/lib/python3.7.../management/commands/flush.py:69: in handle
    savepoint=connection.features.can_rollback_ddl):
.tox/py3.7-django-v1.11.29/lib/python3.7.../django/db/transaction.py:165: in __enter__
    "Your database backend doesn't behave properly when "
E   django.core.management.base.CommandError: Database file:memorydb_default?mode=memory&cache=shared couldn't be flushed. Possible reasons:
E     * The database isn't running or isn't configured correctly.
E     * At least one of the expected database tables doesn't exist.
E     * The SQL was invalid.
E   Hint: Look at the output of 'django-admin sqlflush'. That's the SQL this command wasn't able to run.
E   The full error: Your database backend doesn't behave properly when autocommit is off. Turn it on before using 'atomic'.

tests.integrations.django.test_db_query_data::test_db_atomic_execute

Stack Traces | 0.762s run time

.../integrations/django/test_db_query_data.py:661: in test_db_atomic_execute
    assert len(commit_spans) == 1
E   assert 0 == 1
E    +  where 0 = len([])

tests.integrations.django.test_db_query_data::test_db_atomic_execute

Stack Traces | 0.781s run time

.../integrations/django/test_db_query_data.py:661: in test_db_atomic_execute
    assert len(commit_spans) == 1
E   assert 0 == 1
E    +  where 0 = len([])

tests.integrations.django.test_db_query_data::test_db_atomic_execute

Stack Traces | 0.839s run time

.../integrations/django/test_db_query_data.py:661: in test_db_atomic_execute
    assert len(commit_spans) == 1
E   assert 0 == 1
E    +  where 0 = len([])

tests.integrations.django.test_db_query_data::test_db_atomic_execute

Stack Traces | 0.893s run time

.../integrations/django/test_db_query_data.py:661: in test_db_atomic_execute
    assert len(commit_spans) == 1
E   assert 0 == 1
E    +  where 0 = len([])

tests.integrations.django.test_db_query_data::test_db_atomic_execute

Stack Traces | 0.928s run time

.../integrations/django/test_db_query_data.py:661: in test_db_atomic_execute
    assert len(commit_spans) == 1
E   assert 0 == 1
E    +  where 0 = len([])

tests.integrations.django.test_db_query_data::test_db_atomic_execute

Stack Traces | 0.937s run time

.../integrations/django/test_db_query_data.py:661: in test_db_atomic_execute
    assert len(commit_spans) == 1
E   assert 0 == 1
E    +  where 0 = len([])

tests.integrations.django.test_db_query_data::test_db_atomic_execute

Stack Traces | 0.948s run time

.../integrations/django/test_db_query_data.py:661: in test_db_atomic_execute
    assert len(commit_spans) == 1
E   assert 0 == 1
E     +0
E     -1

tests.integrations.django.test_db_query_data::test_db_atomic_execute

Stack Traces | 0.969s run time

.../integrations/django/test_db_query_data.py:661: in test_db_atomic_execute
    assert len(commit_spans) == 1
E   assert 0 == 1
E    +  where 0 = len([])

tests.integrations.django.test_db_query_data::test_db_atomic_execute

Stack Traces | 0.982s run time

.../integrations/django/test_db_query_data.py:661: in test_db_atomic_execute
    assert len(commit_spans) == 1
E   assert 0 == 1
E    +  where 0 = len([])

tests.integrations.django.test_db_query_data::test_db_atomic_execute

Stack Traces | 1.13s run time

.../integrations/django/test_db_query_data.py:661: in test_db_atomic_execute
    assert len(commit_spans) == 1
E   assert 0 == 1
E    +  where 0 = len([])

To view more test analytics, go to the Test Analytics Dashboard
_{📋 Got 3 mins? Take this short survey to help us improve Test Analytics.}