Graph error : <Message id > has to be unique in a batch

Offen
#1,679 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
35/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Veraltet
Tech-Stack
node.js, typescript
Bereich
api

Rechercherichtung

Start with the batch request handling in the @microsoft/microsoft-graph-client package and reproduce the POST to Graph’s $batch endpoint using the two message IDs from the report. Trace where the duplicate-ID error is produced and add a regression test for distinct IDs that differ only by case. Done means the batch request is accepted without the uniqueness error.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Bug - P1 TODO TypeScript

Bug Report

Prerequisites

  • Can you reproduce the problem?
  • Are you running the latest version?
  • Are you reporting to the correct repository?
  • Did you perform a cursory search?

For more information, see the CONTRIBUTING guide.

Description

Batch api/@microsoft/microsoft-graph-client throws an error even when you have 2 different strings

In my outlook inbox there were 2 different emails with message ids: AQMkADI1NjdjOTA3LTA2MDctNDljNS1iM2JjLWI0YzFmOGVjYjEzMABGAAADaFuLVZilDkGMRMEras84mwcAJoSf1ZrISEGDUfN0NvJ3fgAAAgEMAAAAJoSf1ZrISEGDUfN0NvJ3fgACvV-2EAAAAA== & AQMkADI1NjdjOTA3LTA2MDctNDljNS1iM2JjLWI0YzFmOGVjYjEzMABGAAADaFuLVZilDkGMRMEras84mwcAJoSf1ZrISEGDUfN0NvJ3fgAAAgEMAAAAJoSf1ZrISEGDUfN0NvJ3fgACvV-2eAAAAA==

the only discernible difference between these 2 strings is the eAAA and EAAA but they are different nonetheless

Console Errors: [Is there any console error]
Batch err GraphError: Request Id AQMkADI1NjdjOTA3LTA2MDctNDljNS1iM2JjLWI0YzFmOGVjYjEzMABGAAADaFuLVZilDkGMRMEras84mwcAJoSf1ZrISEGDUfN0NvJ3fgAAAgEMAAAAJoSf1ZrISEGDUfN0NvJ3fgACvV-2EAAAAA== has to be unique in a batch.

Steps to Reproduce (roughly)

It seems like a message which is undeliverable sometimes produces a message id which is similar to the undelivered email

  1. Have an email in the inbox
  2. Reply to that email with imaginary recipients
  3. You should now receive an undelivered email message in the same email thread
  4. Extract the message ids on this thread
  5. Batch them into an array with a structure like so
[    {
       id: '<Msg_id1>',
       url: '/me/messages/<MSG id 1/$value',
       method: 'GET'
     },
     {
       id: '<Msg id 2>',
       url: '/me/messages/<MSG id 2/$value',
       method: 'GET'
     }
]

  1. Pass this as a POST request to graph's $batch endpoint via the @microsoft/microsoft-graph-client npm library
    Expected behavior: The batch request should be executed

Actual behavior: Library throws a message id should be unique error

Additional Context

Add any other context about the problem here..

Usage Information

Request ID - 9ecfb982-93c9-4f64-9d2e-331ffdefd6fe

SDK Version - 3.0.7

  • [x ] Node (Check, if using Node version of SDK)

Node Version - [The version of Node you are using]

  • Browser (Check, if using Browser version of SDK)

Browser Name - [The name of Browser that you are using for SDK]

Version - [The version of the browser you are using]

Vorherrschende Sprache
TypeScript
Sterne
833
Forks
240
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus microsoftgraph/msgraph-sdk-javascript

Alle Issues in microsoftgraph/msgraph-sdk-javascript

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.