microsoftgraph / microsoftgraph/microsoft-graph-comms-samples

PolicyRecordingBot return to me exception when request log URL

Open
#748 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
253
Forks
275
Avg merge
1d 5h
Merged PRs (30d)
1

Description

Describe the issue
I upload the PolicyRecordingBot in the Azure cloud service (extend support) and it working fine also i create Azure bot and i configured the microsoft teams and add webhock

when i try to make test call the notification bar it appear (Recording is started).
but when i try to requrest logs url : https://bot.globitel.com:10101/logs it return to me this exception

$>2024-08-14T15:42:25.4750320Z Error: ExceptionLogger.cs:37 LogAsync
Exception processing HTTP request.
exception: Bytes to be written to the stream exceed the Content-Length bytes size specified.
StackTrace: at System.Net.HttpResponseStream.BeginWrite(Byte[] buffer, Int32 offset, Int32 size, AsyncCallback callback, Object state)
at Microsoft.Owin.Host.HttpListener.RequestProcessing.ExceptionFilterStream.BeginWrite(Byte[] buffer, Int32 offset, Int32 count, AsyncCallback callback, Object state)
at System.Threading.Tasks.TaskFactory1.FromAsyncImpl[TArg1,TArg2,TArg3](Func6 beginMethod, Func2 endFunction, Action1 endAction, TArg1 arg1, TArg2 arg2, TArg3 arg3, Object state, TaskCreationOptions creationOptions)
at System.Net.Http.HttpContent.CopyToAsync(Stream stream, TransportContext context)
at System.Web.Http.Owin.HttpMessageHandlerAdapter.d__33.MoveNext()

the same thing in calls url : https://bot.globitel.com:10101/calls
it does not return any call.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the request against the deployed /logs and /calls endpoints and inspect the reported Content-Length exception in the response path. No source files or tests are named; done means /logs returns its request log URL successfully and /calls returns the expected calls without the stream-size error.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
api, backend, cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.