Page MenuHomePhabricator

[lib] start tracking progress of DM messages on `processDMOpsActionType` action
ClosedPublic

Authored by kamil on Aug 23 2024, 5:38 AM.
Tags
None
Referenced Files
F3366534: D13154.id43639.diff
Mon, Nov 25, 11:58 AM
F3361415: D13154.id.diff
Sun, Nov 24, 5:17 PM
Unknown Object (File)
Fri, Nov 22, 9:59 PM
Unknown Object (File)
Sat, Nov 9, 7:53 PM
Unknown Object (File)
Fri, Nov 8, 11:06 PM
Unknown Object (File)
Fri, Nov 8, 2:29 AM
Unknown Object (File)
Oct 25 2024, 2:37 AM
Unknown Object (File)
Oct 19 2024, 2:33 PM
Subscribers

Details

Summary

ENG-8423.

This is explained in code comments.

Depends on D13153

Test Plan

Check if text message has all outboundP2PMessages ids in LocalMessageInfo.

Note: This stack is tested end-to-end according to the process described here.

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

kamil held this revision as a draft.
kamil published this revision for review.Aug 23 2024, 7:26 AM
tomek added inline comments.
lib/shared/dm-ops/process-dm-ops.js
169–170 ↗(On Diff #43611)

I'm wondering if we should move this to the spec level. At least, we could have a function that takes the dm operation and returns an optional message ID for messageIDWithoutAutoRetry. But it seems we can go one step further, and more supportsAutoRetry entirely to the spec level. We would then have a coupling between supportsAutoRetry and the operation type.

This revision is now accepted and ready to land.Aug 26 2024, 4:05 AM