-
-
Notifications
You must be signed in to change notification settings - Fork 167
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 to query_update(None) #792
Conversation
…d corresponding test file as well.
The linter error is not related to your PR. |
Codecov Report
@@ Coverage Diff @@
## master #792 +/- ##
=======================================
Coverage 99.73% 99.73%
=======================================
Files 4 4
Lines 750 752 +2
Branches 208 209 +1
=======================================
+ Hits 748 750 +2
Misses 2 2
Flags with carried forward coverage won't be shown. Click here to find out more.
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
Any progress on the linter? |
I believe the pylint error is due to libenchant-dev no longer being listed in the ubuntu packages. I believe a fix to this would be to change it the github action to "libenchant-2-dev," since that appears to be the replacement, but I don't believe I can run the linter on github to test it. |
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.
LGTM
Apparently the parameter passing in our `aiohttp` tests were incorrect, and was depending on a `yarl` bug [1] that was fixed [2] in `1.9.0`, and with this new yarl version, our tests started to fail. This fix corrects the parameter passing, so we can use the latest `yarl`. [1] aio-libs/yarl#723 [2] aio-libs/yarl#792 Signed-off-by: Ferenc Géczi <ferenc.geczi@ibm.com>
Apparently the parameter passing in our `aiohttp` tests were incorrect, and was depending on a `yarl` bug [1] that was fixed [2] in `1.9.0`, and with this new yarl version, our tests started to fail. This fix corrects the parameter passing, so we can use the latest `yarl`. [1] aio-libs/yarl#723 [2] aio-libs/yarl#792 Signed-off-by: Ferenc Géczi <ferenc.geczi@ibm.com>
Apparently the parameter passing in our `aiohttp` tests were incorrect, and was depending on a `yarl` bug [1] that was fixed [2] in `1.9.0`, and with this new yarl version, our tests started to fail. This fix corrects the parameter passing, so we can use the latest `yarl`. [1] aio-libs/yarl#723 [2] aio-libs/yarl#792 Signed-off-by: Ferenc Géczi <ferenc.geczi@ibm.com>
Apparently the parameter passing in our `aiohttp` tests were incorrect, and was depending on a `yarl` bug [1] that was fixed [2] in `1.9.0`, and with this new yarl version, our tests started to fail. This fix corrects the parameter passing, so we can use the latest `yarl`. [1] aio-libs/yarl#723 [2] aio-libs/yarl#792 Signed-off-by: Ferenc Géczi <ferenc.geczi@ibm.com>
This fixes the query_update() function special case where the None argument should clear query.
The query_update() function now works when None is passed to the function.
Related issue number
#723
Checklist
CHANGES
folder<issue_id>.<type>
(e.g.588.bugfix
)issue_id
change it to the pr id after creating the PR.feature
: Signifying a new feature..bugfix
: Signifying a bug fix..doc
: Signifying a documentation improvement..removal
: Signifying a deprecation or removal of public API..misc
: A ticket has been closed, but it is not of interest to users.Fix issue with non-ascii contents in doctest text files.