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

[Bug]: #808

Closed
mark-kramtest opened this issue Dec 4, 2024 · 4 comments · Fixed by #809 or #806
Closed

[Bug]: #808

mark-kramtest opened this issue Dec 4, 2024 · 4 comments · Fixed by #809 or #806
Assignees
Labels
bug Something isn't working

Comments

@mark-kramtest
Copy link

Describe the bug
Getting TypeError [TypeError: get() got an unexpected keyword argument 'proxies'] when running:

# Connect to Microsoft Sentinel with our QueryProvider and config details
qry_prov.connect(ws_config)

To Reproduce

New AML compute instance. Followed all steps to setup msticpy configuration.
config files present and properly loaded. All steps passing besides mentioned above.

Other compute instance with same settings works properly.

Expected behavior
Successfull connection to Sentinel provider.

Screenshots and/or Traceback

Image

Environment (please complete the following information):

  • Python Version: [3.10]
  • OS: [Ubuntu Linux 24.10.18 ]
  • Python environment: [Cloud Azure ML]
  • MSTICPy Version: [2.14.0]
@mark-kramtest mark-kramtest added the bug Something isn't working label Dec 4, 2024
@agahen
Copy link

agahen commented Dec 5, 2024

Looks like related to deprecation of 'proxies', ref: encode/httpx#2879

@mark-kramtest
Copy link
Author

thanks @agahen
I'm not a pro and thought I got all dependencies up to date. But already overcome this by removing all parts related with proxies from the connector itself.

@ianhelle
Copy link
Contributor

ianhelle commented Dec 5, 2024

Thanks @agahen for filing the issue and @mark-kramtest for diagnosing the cause.
I will update msticpy to replace the use of the deprecated proxies parameter

@ianhelle ianhelle self-assigned this Dec 13, 2024
@ianhelle
Copy link
Contributor

This should be fixed in the current release 2.15.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
3 participants