Skip to content

Python: Bug: AzureRealtimeWebsocket does not pass api_key for superclass constructor #11003

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

Closed
bbence84 opened this issue Mar 17, 2025 · 1 comment · Fixed by #11056
Closed
Assignees
Labels
ai connector Anything related to AI connectors bug Something isn't working python Pull requests for the Python Semantic Kernel

Comments

@bbence84
Copy link

Describe the bug
The class AzureRealtimeWebsocket does not pass api_key for superclass constructor, so using .env file based API authentication does not work.

To Reproduce
Use .env file for AzureRealtimeWebsocket with the env_file_path param.

Expected behavior
.env file should work. :) In the super().init call, the api_key should be passed.

Platform

  • Language: Python
  • Source: latest pip version
  • AI model: gpt-4o-realtime-preview
  • IDE: VS Code
  • OS: Windows
@bbence84 bbence84 added the bug Something isn't working label Mar 17, 2025
@markwallace-microsoft markwallace-microsoft added python Pull requests for the Python Semantic Kernel triage labels Mar 17, 2025
@moonbox3 moonbox3 added ai connector Anything related to AI connectors and removed triage labels Mar 18, 2025
@moonbox3 moonbox3 assigned moonbox3 and unassigned eavanvalkenburg Mar 19, 2025
@moonbox3
Copy link
Contributor

@bbence84 thanks for filing - PR raised to fix this: #11056.

github-merge-queue bot pushed a commit that referenced this issue Mar 20, 2025
### Motivation and Context

In creating the `AzureRealtimeWebsocket` object, one can use an api key
as part of `AzureOpenAISettings`. This api_key is not getting passed to
the `AzureOpenAIConfigBase`.

<!-- Thank you for your contribution to the semantic-kernel repo!
Please help reviewers and future users, providing the following
information:
  1. Why is this change required?
  2. What problem does it solve?
  3. What scenario does it contribute to?
  4. If it fixes an open issue, please link to the issue here.
-->

### Description

Pass the api key to the config base.
- Closes #11003

<!-- Describe your changes, the overall approach, the underlying design.
These notes will help understanding how your code works. Thanks! -->

### Contribution Checklist

<!-- Before submitting this PR, please make sure: -->

- [X] The code builds clean without any errors or warnings
- [X] The PR follows the [SK Contribution
Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
and the [pre-submission formatting
script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts)
raises no violations
- [X] All unit tests pass, and I have added new tests where possible
- [X] I didn't break anyone 😄
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ai connector Anything related to AI connectors bug Something isn't working python Pull requests for the Python Semantic Kernel
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

4 participants