-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WaitForPublishDeals getting deal info errored: Deal proposals for publish message bafy... did not match #1992
Comments
The issue is due to label field in proposal, I tried putting label as bytes in the above cases leading to eternal wait for |
The issue seems to be the market state and the deal state being returned from Lotus. The message https://calibration.filfox.info/en/message/bafy2bzacebjz4lyzadhznktgroddnm6l7mdk52mbtgmzhry4axxmqs7b6jsew?t=4 has correct params and can be verified that DealLabel is indeed bytes. But once PSD is sent and we get back the dealID, if I lookup the Code to verify. Using manual params instead of StateSearchMessage to avoid failure as Gateway allows upto 2000 epoch look back only.
|
Checklist
Latest release
, or the most recent RC(release canadiate) for the upcoming release or the dev branch(master), or have an issue updating to any of these.Boost component
Boost Version
Describe the Bug
https://calibration.filfox.info/en/message/bafy2bzacebjz4lyzadhznktgroddnm6l7mdk52mbtgmzhry4axxmqs7b6jsew?t=4
this msg seems to go on chain fine but it fails to be recognized by boost. we suspect its the hex encoding oif the params.
(the only visible thing different from other msgs, eg. https://calibration.filfox.info/en/message/bafy2bzacea67ocy4ex373mmlkza735tn3mtf4yrg3a7jstvlvmfq4mdbooipo?t=4)
Logging Information
The text was updated successfully, but these errors were encountered: