Skip to content
This repository has been archived by the owner on Jun 6, 2023. It is now read-only.

Add log messages for significant events #1060

Closed
anorth opened this issue Aug 31, 2020 · 3 comments
Closed

Add log messages for significant events #1060

anorth opened this issue Aug 31, 2020 · 3 comments
Labels
good first issue Good for newcomers P2 Medium priority, beneficial for network functionality and growth

Comments

@anorth
Copy link
Member

anorth commented Aug 31, 2020

The runtime API exposes a logging hook, which we currently make scarce use of. Log messages could be extremely helpful when debugging actor behaviour in the wild, especially if something unexpected is happening.

Add informational log messages around significant events.

Note that the Runtime will know which the receiving actor is, so it's not necessary to add that information into the message body. The runtime will also know the method number, parameters etc.

Be very careful that log message formatting does not alter the actor behaviour (e.g. by dereferencing a nil that otherwise would be ignored).

@anorth anorth added good first issue Good for newcomers P2 Medium priority, beneficial for network functionality and growth labels Aug 31, 2020
@wadealexc
Copy link

Cron

Market

Power

VerifReg

  • RestoreBytes: Log if this method is invoked

Miner

  • burnFunds: Log if this method is invoked with nonzero amt
  • RepayDebtsOrAbort: Log if this method is invoked and succeeds
  • SubmitWindowedPoSt:
    • Log if all sectors are faults (if len(sectorsInfos) == 0):
      // Skip verification if all sectors are faults.
      // We still need to allow this call to succeed so the miner can declare a whole partition as skipped.
      if len(sectorInfos) > 0 {
  • OnDeferredCronEvent: Add a default case, and log if it's reached
  • processEarlyTerminations:
  • scheduleEarlyTerminationWork: Log if this method is invoked

@anorth
Copy link
Member Author

anorth commented Oct 14, 2020

We've determined this is not critical for network launch. It will greatly aid troubleshooting, but does not itself resolve or reduce any specific risk.

cc @wadealexc

@ZenGround0 ZenGround0 added this to the 🧡 v3 milestone Oct 28, 2020
@anorth anorth modified the milestones: 🧡 v3 , v4 Jan 21, 2021
@ZenGround0
Copy link
Contributor

#1288 can be done as part of this work.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
good first issue Good for newcomers P2 Medium priority, beneficial for network functionality and growth
Projects
None yet
Development

No branches or pull requests

4 participants