-
-
Notifications
You must be signed in to change notification settings - Fork 328
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
fix: DataCollector sql_queries model not found on filter(request=self… #476
Conversation
Codecov Report
@@ Coverage Diff @@
## master #476 +/- ##
==========================================
- Coverage 82.83% 82.82% -0.01%
==========================================
Files 50 50
Lines 2051 2050 -1
==========================================
- Hits 1699 1698 -1
Misses 352 352
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you please add a test for the changes?
I currently don't know exactly for what reason this issue happens. Should check it out further. |
Fairly insignificant code coverage change, and I don't believe tests are needed for just changing how the variable is assigned. Will merge. |
Reverted this merge due to this issue with meta profiling
|
you should not have merge this on the first place. |
I agree with you, my mistake. |
Closes #475
After digging into silk DataCollector, I figured out in the second line of this section of the code no sql query is returned. So the part where adds model to query dictionaries, can't do it's job and we face the error issued in #475
By changing these 2 lines to
sql_queries = models.SQLQuery.objects.bulk_create(sql_queries)
, sql_queries is no longer empty and the rest of the system can function correctly.