Some VTRANSFER_IBC_EVENT actions do not have txHash / msgIdx in context

[mhofman]

Describe the bug

We're currently seeing some logs on mainnet where pushAction is not able to extract the txHash and msgIdx from the context for VTRANSFER_IBC_EVENT actions, seemingly for acknowledgement (both writeAcknowledgement and acknowledgementPacket)

The error is benign beyond lack of context attribution.

To Reproduce

https://cloudlogging.app.goo.gl/y8rSawpwGB6edu4S9

Expected behavior

No error in the logs

Platform Environment

• mainnet upgrade-18a

Screenshots

2025/02/28 20:23:47 error while extracting context for action &{%!q(*vm.ActionHeader=&{VTRANSFER_IBC_EVENT 18571923 1740774217}) "acknowledgementPacket" "agoric1zcqu6ug37luep6eq6hd8jzl478ku9mg9jyvtmuvaqfv39qe5j58qhz8ydx" {'ب' "transfer" "channel-62" "transfer" "channel-21" "{\"amount\":\"1158200\",\"denom\":\"transfer/channel-62/uusdc\",\"receiver\":\"noble1jndsjwk2uwyd2xvhzcrh9jurnuvltse73408k2\",\"sender\":\"agoric1zcqu6ug37luep6eq6hd8jzl478ku9mg9jyvtmuvaqfv39qe5j58qhz8ydx\"}" "0-0" '�'} "{\"result\":\"AQ==\"}" 4E51D0B6B2C47320650FCF232B56EC1FAB746B4F}

I am somewhat confused because this particular log entry is referencing a block (18571923) that had no activity whatsoever (no cosmos tx, nor any swingset execution, including this action that should have gotten pushed)