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

profile_name field ignored for Amazon Bedrock Chat Models in jupyter-ai Extension #1007

Open
Naveen-Annam-CMA opened this issue Sep 20, 2024 · 1 comment · May be fixed by #1125
Open

profile_name field ignored for Amazon Bedrock Chat Models in jupyter-ai Extension #1007

Naveen-Annam-CMA opened this issue Sep 20, 2024 · 1 comment · May be fixed by #1125
Labels
bug Something isn't working

Comments

@Naveen-Annam-CMA
Copy link

Description:

We are using Amazon Bedrock Chat models as completion models within the jupyter-ai extension. The profile_name field in the UI appears to be ignored when we try to set our SSO profiles. It defaults to the personal profile (we have configured) from the credentials file, even though we manually specify a different SSO profile.

We typically use AWS_PROFILE to set our SSO profiles, and we would like to understand why the profile_name field does not seem to apply the manually entered values.

Environment:

  • Platform: JupyterLab running on AWS with SSO profiles
  • Issue: profile_name field is ignored, and the extension defaults to the personal profile in the credentials file.

Request for Assistance:

  • Please clarify how the extension handles profiles and why the profile_name field in the UI is not functioning as expected for Bedrock Chat models.
@Naveen-Annam-CMA Naveen-Annam-CMA added the bug Something isn't working label Sep 20, 2024
@dlqqq
Copy link
Member

dlqqq commented Nov 27, 2024

@Naveen-Annam-CMA

Sorry this issue went undiscovered by our team for so long. We've identified a bug (#1118) that causes the model fields set from the UI to not be applied until after the server is restarted. This almost certainly explains the issue you were experiencing.

I've opened a new PR to fix this: #1125. We hope to have this issue patched by early next week after folks return from Thanksgiving in the US.

I sincerely appreciate your patience. Thank you for using Jupyter AI!

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
Development

Successfully merging a pull request may close this issue.

2 participants