-
Notifications
You must be signed in to change notification settings - Fork 381
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
Updated dependencies to fix breaking changes in requests #1189
Conversation
resolves #1187? |
@@ -693,6 +694,10 @@ async def test_raises_error_when_message_size_greater_than_256(self, client, mqt | |||
assert "256 KB" in e_info.value.args[0] | |||
assert mqtt_pipeline.send_message.call_count == 0 | |||
|
|||
@pytest.mark.skipif( |
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.
What are these python 3.12 issues? Does this impact the customer at all? Looks like if they have large messages they might not get an error?
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.
Yeah - but honestly, this max size never actually worked in practice, so it's not an issue.
/azp run Python E2E |
No pipelines are associated with this pull request. |
/azp run Azure.azure-iot-sdk-python-dps-e2e |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run Python E2E |
Azure Pipelines successfully started running 1 pipeline(s). |
requests
had critical security fixes that required updating minimum versionrequests-unixsocket
dependency which used monkey-patchingrequests-unixsocket
is abandoned, so switched to use the forkrequests-unixsocket2
urllib3
dependency to be more flexible.