fix(slashsvc): reduce block not found error logs

[rjan90]

Related Issues

#12906

Proposed Changes

Reduces log level for ipld: could not find logs to DEBUG.

Checklist

Before you mark the PR ready for review, please make sure that:

• Commits have a clear commit message.
• PR title conforms with contribution conventions
• Update CHANGELOG.md or signal that this change does not need it per contribution conventions
• New features have usage guidelines and / or documentation updates in
  • Lotus Documentation
  • Discussion Tutorials
• Tests exist for new functionality or change in behavior
• CI is green

[rvagg]

Do we know why this is throwing up not found errors though? Is it reasonable behaviour?

[rjan90]

Do we know why this is throwing up not found errors though? Is it reasonable behaviour?

My hunch is that this is somewhat related to other behaviours seen by Magik for example here in the lotus-dev channel.

While everyone usually points to SplitStore as a potential source for "removing" these messages, I think @ZenGround0 latest adventures into the SplitStore code in: #12803 made him convinced that these cases are not SplitStore issues at all, because messages are not stored in the splitstore but the metadata store.

I do not think it is great that we do not have a understanding of why people are excessively seeing these logs, but I´m not sure if we have bandwidth to dive into it at this moment in time. I will create a tracking/investigation ticket for the overarching issue of ipld: could not find logs/issues.

[rjan90]

I will reuse/add more comments to this ticket here: #10260 as it seems somewhat related