dosubot[bot]
commented
1 year ago 🤖
Hello,
I understand that you're having trouble with the "AzureOpenAI Content Filter Error" causing your NestJS process to terminate. This error is likely being thrown because the input to the OpenAI API is triggering Azure's content management policy.
To catch and handle this error, you can use a try-catch block around the function that is causing the error. In the LangChain codebase, it seems like the error might be coming from the completionWithRetry function in the ChatOpenAI class.
Here's how you can modify the completionWithRetry function to catch and handle the error:
async completionWithRetry(
request: CreateChatCompletionRequest,
options?: StreamingAxiosConfiguration
) {
try {
// existing code...
return this.caller
.call(
this.client.createChatCompletion.bind(this.client),
request,
axiosOptions
)
.then((res) => res.data);
} catch (error) {
// Handle the error here
console.error("Caught AzureOpenAI Content Filter Error: ", error);
// You can also re-throw the error if you want it to be handled further up the call stack
throw error;
}
}This modification will catch the error and log it to the console. You can replace the console.error line with your own error handling logic. If you want the error to be handled further up the call stack, you can re-throw the error after logging it.
Please let me know if this helps or if you need further assistance.
Sources
- langchain/src/llms/openai-chat.ts
- langchain/src/chat_models/openai.ts
- langchain/src/callbacks/manager.ts
This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.
Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.
If you want to continue the conversation, start your reply with @dosu-bot.
xMHW
jacoblee93
alexechoi
Langchain version 0.0.131 OpenAI version 3.3.0
AzureOpenAI Chat model keeps faults with the above no matter how I wrap call functions with error handlers(try catch, promise.catch, ...) It keeps causing my NestJS process to die.
I have no clue where to debug this. Just don't recommend me to try with other input(I knew it worked well for the other cases). I need help with how I can catch this error.