microsoftgraph / microsoftgraph/msgraph-sdk-python
Move email with static graph ID for email results in duplication of emails
還沒有人認領這個 Issue。
- 主要語言
- Python
- 星號
- 630
- 分支
- 96
- 平均合併
- 15 小時 20 分鐘
- 30 天內合併 PR
- 3
描述
Describe the bug
Using the move mail endpoint with immutable graph ids for mail creates duplicate mails
headers = HeadersCollection()
headers.add("Prefer", 'IdType="ImmutableId"')
was used to get the immutable graph id
-
Place email in test inbox ("Invoice processor test inbox"):
-
Move email manually in OWA to another folder ("Invoice processor test cannot process")
-
Call the move email endpoint to move email to ("Invoice processor test done"):
Email is moved out of inbox ("Invoice processor test inbox"):
Test emails moves to target folder ("Invoice processor test done")
Test email unexpectedly also stays in ("Invoice processor test cannot process")
I now have a duplicate of the email. This should not happen if you call move on a email right? Is this intended behavior because of the use of immutable graph IDs or is this a bug?
Expected behavior
Email should be moved not duplicated
How to reproduce
See bug description
SDK Version
1.12.0
Latest version known to work for scenario above?
No response
Known Workarounds
Use non static graph ID
Debug output
No response
Configuration
Ubuntu 22.04
Other information
No response
貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
研究方向
從報告中所示的 move mail endpoint 和 immutable Graph ID 請求開始。使用 SDK 1.12.0 重現該序列,然後將其與已記錄的非靜態 ID workaround 進行比較,以確定重複是源於 SDK 還是 Graph 服務。完成的標準是確定原因,並記錄或測試一個可在不產生重複的情況下進行移動的 fix。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- python
- 領域
- api
- Issue 類型
- 缺陷
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 活躍度
- 冷清
- 描述清晰度
- 需要釐清
- 新手友好度
- 35/100