bug(MU): Missing Messages via EverVisison

[twilson63]

Problem

Messages are continuing to not be delivered!

jay young, [Jul 24, 2024 at 10:07:22 PM]:
hello, @twilson63 we have encouter messages deliver miss problem occasionally。

for example https://ao_marton.g8way.io/#/message/wo3CSe_K9TaINnyhsWYzvGeGNsiYI2sbeGKLAHhiYYQ

the result generate two message, and only deliver one

This issue is causing our dex to not function properly.
we have to use owner to resend this message, in this way we can not set owner = "" to make dex compelete decentralized.

will the message deliver missing problem still exist when mainnet?

I also read the ao whitepaper, in "5.2.2 Messages" section,

'''
The AO data protocol employs at-most-once delivery se- mantics, as detailed in [22], atop which additional guar- antees are provided by the maintenance of message logs on Arweave through its data persistence protocol. These guarantees ensure that undelivered messages that result from Pi may always been delivered later by re-computing Outbox(Pi) from its message log on Arweave.
'''

so how the redelivered mechanism works？ is it available？how we use it？

jay young, [Jul 25, 2024 at 6:38:08 AM]:
No, occasionally failed

here is another example https://ao_marton.g8way.io/#/message/NHTulqzunPQfwQ9YQF63ZO0PeFWiF3XTjdkXhotucCY

just a normal war transfer, but credit-notice/Debit-Notice is not delivered

@twilson63

[VinceJuliano]

After looking at logs it seems the result was sent to Arweave, we will look into making the logic that does this reliable

[twilson63]

RE Credit/Debit Notices One was a wallet the other was a process

…

On Thu, Jul 25, 2024 at 9:36 AM Vince Juliano ***@***.***> wrote: After looking at logs it seems the result was sent to Arweave, we will look into making the logic that does this reliable — Reply to this email directly, view it on GitHub <#913 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAFGLALYXDNBBWK5GE7UXDZOD5MNAVCNFSM6AAAAABLOMQ6B2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJQGM2DCMBQGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>