-
Hello to all, Firstly, I'd like to express my sincere gratitude to all those involved in developing and maintaining this invaluable tool. It's been instrumental in the creation of my AI chatbot. I have, however, come across an unusual issue. My application, which uses the OpenAI API, works flawlessly on my own machine. Yet, when run on a different machine, it returns unreadable responses. These responses consist of a jumble of English and nonsensical terms, regardless of the input language. This leads me to suspect that the problem may be with the library I'm using for the API calls - Betalgo.OpenAI (7.0.0) - or potentially an encoding/decoding issue that varies between machines. Are there any known issues with this library, or are there specific precautions to consider when deploying on various machines? Any advice would be greatly appreciated. |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 1 reply
-
|
Beta Was this translation helpful? Give feedback.
-
I replicated your GPT-4 example in the OPENAI Playground, but couldn't reproduce the error. I would suggest you try testing your use case in your environment using methods other than Betalgo.OpenAI, such as directly invoking the OPENAI API via the OPENAI Playground or Postman, and see if you find anything. |
Beta Was this translation helpful? Give feedback.
-
Hello everyone, I'm pleased to report that I've identified the cause of the problem I was facing and I'd like to share the solution with the community. The root of the issue was the difference in regional settings between my development machine and the client machines. On my machine, the decimal separator was '.', while on the client machines it was ','. This discrepancy affected how the temperature parameter was interpreted in the API request. When client machines sent the request, due to the different decimal separator, the temperature setting of 0.2 was misinterpreted as 2. This resulted in the received gibberish responses. I was able to identify this issue by monitoring the requests and responses using Fiddler. Once I adjusted the regional settings to ensure the consistent use of the decimal separator across the machines, the issue was resolved, and the chatbot responses returned to normal. I appreciate everyone who contributed and provided valuable insights during this troubleshooting process. I hope this solution might assist others facing a similar issue in the future. |
Beta Was this translation helpful? Give feedback.
-
Great, I'm glad to see your problem has been solved. I tried your case, and indeed, when the temperature is set to 2, a bunch of gibberish appears. Thanks for pointing out a gap in my understanding - I've always thought the temperature value could only be between 0 and 1! |
Beta Was this translation helpful? Give feedback.
Hello everyone,
I'm pleased to report that I've identified the cause of the problem I was facing and I'd like to share the solution with the community.
The root of the issue was the difference in regional settings between my development machine and the client machines. On my machine, the decimal separator was '.', while on the client machines it was ','. This discrepancy affected how the temperature parameter was interpreted in the API request.
When client machines sent the request, due to the different decimal separator, the temperature setting of 0.2 was misinterpreted as 2. This resulted in the received gibberish responses.
I was able to identify this issue by monitoring the requests a…