Skip to content
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

Merged
merged 5 commits into from
Dec 12, 2022
Merged

Fix to query_update(None) #792

merged 5 commits into from
Dec 12, 2022

Conversation

dereckt
Copy link
Contributor

@dereckt dereckt commented Dec 4, 2022

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

  • I think the code is well written
  • Unit tests for the changes exist
  • Documentation reflects the changes
  • Add a new news fragment into the CHANGES folder
    • name it <issue_id>.<type> (e.g. 588.bugfix)
    • if you don't have an issue_id change it to the pr id after creating the PR
    • ensure type is one of the following:
      • .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.
    • Make sure to use full sentences with correct case and punctuation, for example: Fix issue with non-ascii contents in doctest text files.

@psf-chronographer psf-chronographer bot added the bot:chronographer:provided There is a change note present in this PR label Dec 4, 2022
@dereckt dereckt changed the title Query update Fix to query_update(None) Dec 7, 2022
@asvetlov
Copy link
Member

asvetlov commented Dec 8, 2022

The linter error is not related to your PR.
Please let me fix it first separately.

@codecov
Copy link

codecov bot commented Dec 8, 2022

Codecov Report

Merging #792 (99ffcc0) into master (d703adb) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           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           
Flag Coverage Δ
unit 99.60% <100.00%> (+<0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
yarl/_url.py 99.65% <100.00%> (+<0.01%) ⬆️

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@dereckt
Copy link
Contributor Author

dereckt commented Dec 10, 2022

The linter error is not related to your PR. Please let me fix it first separately.

Any progress on the linter?

@dereckt
Copy link
Contributor Author

dereckt commented Dec 12, 2022

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.
image

Copy link
Member

@asvetlov asvetlov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@asvetlov asvetlov merged commit dd86b34 into aio-libs:master Dec 12, 2022
Ferenc- added a commit to instana/python-sensor that referenced this pull request May 15, 2023
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>
Ferenc- added a commit to instana/python-sensor that referenced this pull request May 15, 2023
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>
Ferenc- added a commit to instana/python-sensor that referenced this pull request May 15, 2023
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>
Ferenc- added a commit to instana/python-sensor that referenced this pull request May 15, 2023
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bot:chronographer:provided There is a change note present in this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants