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] Chat Repsonse cutoff with Azure Configured #5474

Open
itsamejoshab opened this issue Sep 19, 2024 · 2 comments
Open

[Bug] Chat Repsonse cutoff with Azure Configured #5474

itsamejoshab opened this issue Sep 19, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@itsamejoshab
Copy link

📦 Deployment Method

Official installation package

📌 Version

2.15.2

💻 Operating System

macOS

📌 System Version

14.5

🌐 Browser

Chrome

📌 Browser Version

128.0.6613.138

🐛 Bug Description

Configuring NextChat packaged client to work with Azure makes the response text get cutoff in the chat.

This was not an issue with prior older versions of the client, but this happens to me after I upgraded to 2.15.2

image

📷 Recurrence Steps

Model Provider: Azure
Azure Endpoint: https://{resource-url}/openai
Custom Models: -all,{modelname}@Azure={deploymentName}
Max Tokens: 4000
Attached Message Count: 5
History Compression Threshold: 5000
Memory Prompt: yes

🚦 Expected Behavior

The entire response should be shown instead of only about 10-15 tokens

📝 Additional Information

No response

@itsamejoshab itsamejoshab added the bug Something isn't working label Sep 19, 2024
@nextchat-manager
Copy link

Please follow the issue template to update description of your issue.

@Issues-translate-bot
Copy link

Bot detected the issue body's language is not English, translate it automatically.


Title: [Bug]

@itsamejoshab itsamejoshab changed the title [Bug] [Bug] Chat Repsonse cutoff with Azure Configured Sep 19, 2024
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

No branches or pull requests

2 participants