You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MarkusMeyer13 opened this issue
Oct 18, 2023
· 2 comments
Labels
bugSomething isn't workingfollow upIssues that require a follow up from the community.kernelIssues or pull requests impacting the core kernel.NETIssue or Pull requests regarding .NET code
I'm using Microsoft.SemanticKernel version="1.0.0-beta2"
The InvokeAsync method raises an exception:
The operation was cancelled because it exceeded the configured timeout of 0:01:40. Network timeout can be adjusted in ClientOptions.Retry.NetworkTimeout.
StackTrace:
at Azure.Core.Pipeline.ResponseBodyPolicy.ThrowIfCancellationRequestedOrTimeout(CancellationToken originalToken, CancellationToken timeoutToken, Exception inner, TimeSpan timeout)
at Azure.Core.Pipeline.ResponseBodyPolicy.d__5.MoveNext()
at Azure.Core.Pipeline.RedirectPolicy.d__7.MoveNext()
at Azure.Core.Pipeline.RetryPolicy.d__5.MoveNext()
at Azure.Core.Pipeline.RetryPolicy.d__5.MoveNext()
at Azure.Core.HttpPipelineExtensions.d__0.MoveNext()
at System.Threading.Tasks.ValueTask1.get_Result() at Azure.AI.OpenAI.OpenAIClient.<GetChatCompletionsAsync>d__17.MoveNext() at Microsoft.SemanticKernel.Connectors.AI.OpenAI.AzureSdk.ClientBase.<RunRequestAsync>d__291.MoveNext()
at Microsoft.SemanticKernel.Connectors.AI.OpenAI.AzureSdk.ClientBase.d__19.MoveNext()
at Microsoft.SemanticKernel.Connectors.AI.OpenAI.AzureSdk.ClientBase.d__22.MoveNext()
at Microsoft.SemanticKernel.SemanticFunction.d__36.MoveNext()
at Microsoft.SemanticKernel.SemanticFunction.d__17.MoveNext()
To Reproduce
Steps to reproduce the behavior:
This is the C# code which produces the exception:
staticasyncTask<string?>Summarize(stringopenAiDeploymentName,stringopenAiEndPoint,stringopenAiKey,stringprompt,stringdata){try{varbuilder=newKernelBuilder();builder.WithAzureChatCompletionService(openAiDeploymentName,openAiEndPoint,openAiKey);varkernel=builder.Build();varsummarize=kernel.CreateSemanticFunction(prompt,requestSettings:newOpenAIRequestSettings(){Temperature=0.1});// 'data' has a length of 8993varresult=awaitsummarize.InvokeAsync(data,kernel).ConfigureAwait(false);returnresult.GetValue<string>();}catch(Exceptione){awaitConsole.Out.WriteLineAsync(e.Message);throw;}}
Used model:
Model name: gpt-35-turbo-16k
Model version: 0613
Version update policy: Once a new default version is available.
Deployment type: Standard
Content Filter: Default
Tokens per Minute Rate Limit (thousands): 5
Rate limit (Tokens per minute): 5000
Rate limit (Requests per minute): 60
The data to summarize has a length of 8993 characters.
The timeout does not happen if the length is e.g. 4000 characters.
Run code
Wait for the result
TimeOut exception occurs
Expected behavior InvokeAsync shall return a valid result also for longer strings.
Screenshots
Platform
OS: Windows
IDE: Visual Studio
Language: C#
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
github-actionsbot
changed the title
The operation was cancelled because it exceeded the configured timeout of 0:01:40
.Net: The operation was cancelled because it exceeded the configured timeout of 0:01:40
Oct 18, 2023
bugSomething isn't workingfollow upIssues that require a follow up from the community.kernelIssues or pull requests impacting the core kernel.NETIssue or Pull requests regarding .NET code
Describe the bug
I'm using Microsoft.SemanticKernel version="1.0.0-beta2"
The
InvokeAsync
method raises an exception:StackTrace:
To Reproduce
Steps to reproduce the behavior:
This is the C# code which produces the exception:
Used model:
The data to summarize has a length of 8993 characters.
The timeout does not happen if the length is e.g. 4000 characters.
Expected behavior
InvokeAsync
shall return a valid result also for longer strings.Screenshots
Platform
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: