Problems with IPNIsync

Checklist

• This is not a question or a support request. If you have any boost related questions, please ask in the discussion forum.
• This is not a new feature request. If it is, please file a feature request instead.
• This is not an enhancement request. If it is, please file a improvement suggestion instead.
• I have searched on the issue tracker and the discussion forum, and there is no existing related issue or discussion.
• I am running the 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.
• I did not make any code changes to boost.

Boost component

• boost daemon - storage providers
• boost client
• boost UI
• boost data-transfer
• boost index-provider
• Other

Boost Version

Latest master of 13 nov 2023

Describe the Bug

Boost generates an error regenerated link from multihash lister did not match the original link; multihashes returned by the lister for the same key are not consistent causing IPNIsync to halt on Indexer side.

Logging Information

2023-11-13T12:46:10.588Z	DEBUG	index-provider-wrapper	indexprovider/wrapper.go:575	returning piece iterator	{"propCid": "bafyreicpfl4qsu4y723rhdu3njkrvvx3uh74tlpxmwr56v4mzehphz242e", "piece": "baga6ea4seaqkljwlwpcjsyol3bxudck5wvzwo3zsnxfocg6ctbgk3xdlljyseiy", "err": null}
2023-11-13T12:46:17.534Z	ERROR	provider/engine	engine/linksystem.go:129	Regeneration of entries link from multihash iterator did not match the original link. Check that multihash iterator consistently returns the same entries for the same key.	{"want": "baguqeera4v4fm56ddi4hrytmkwn2e64hd6wgwmcze4s6fph36ldv55gsvnya", "got": "baguqeeraclox2bkja373gehvxzflg2nvere6dtjagf4arhfdlzlq6mas57gq"}
2023-11-13T12:46:17.535Z	ERROR	dagsync/ipnisync	ipnisync/publisher.go:235	Failed to load requested block	{"err": "regenerated link from multihash lister did not match the original link; multihashes returned by the lister for the same key are not consistent", "cid": "baguqeera4v4fm56ddi4hrytmkwn2e64hd6wgwmcze4s6fph36ldv55gsvnya"}

Repo Steps

1. Run '...'
2. Do '...'
3. See error '...'
   ...

Start with engine/linksystem.go:129 and the log context in indexprovider/wrapper.go:575, then trace the failure through dagsync/ipnisync/publisher.go:235. Use the supplied error and CIDs to investigate why repeated multihash listing for one key differs; done means IPNIsync loads the block without the regenerated link mismatch.