-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Rename SQLPanel context var to control SQL access. #1615
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
Rename SQLPanel context var to control SQL access. #1615
Conversation
The current build started failing for py3.8+ because the inner exception SQLQueryTriggered was raised in the test test_cursor_wrapper_asyncio_ctx. This was identified as being caused by sql.tracking.recording being set to false. The name recording made it seem as if this context var was controlling whether recording was occurring or not. However, it's true functionality was preventing SQL queries from being sent during the template panel's processing. Renaming that context var to allow_sql is more indicative of its purpose and makes the fixed test change clearer.
@matthiask if you're good with this name change, I'll merge this and #1614 and release a new version today. |
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.
Good find! Yes, please create a release if you find the time to do so.
if you are kind enough to look and shred some light into this probably unsupported issue... I'm trying to update it NixOS/nixpkgs#171764 from 3.2.4 to 3.4
i don't have familiarity with this from the python perspective, so i'm not sure what I'm supposed to do here other than disabling this test, even though i tried some things patching the code itself... |
@yuuyins sorry, I don't have nix installed and I don't have the availability to dive into it. However, I don't think disabling this test is the right move since it's there to verify the functionality. If it's breaking, then there's a problem somewhere. |
The current build started failing for py3.8+ because the inner
exception SQLQueryTriggered was raised in the test
test_cursor_wrapper_asyncio_ctx.
This was identified as being caused by sql.tracking.recording
being set to false. The name recording made it seem as if
this context var was controlling whether recording was occurring
or not. However, it's true functionality was preventing SQL
queries from being sent during the template panel's processing.
Renaming that context var to allow_sql is more indicative of
its purpose and makes the fixed test change clearer.