-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Implement PoSt scheduler #205
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Getting there
return ts, nil | ||
} | ||
|
||
pts, err := cs.LoadTipSet(ts.Parents()) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Optimization: we could use chain/events.tipSetCache
here, but that can be done later
Make events subsystem work on top of API
I'm not seeing the out of bounds panic you pointed out, but I do see this:
|
refactor to use 'randomness' as input to new vm creation
log.Warnf("not restarting listenHeadChanges: context error: %s", ctx.Err()) | ||
return | ||
} | ||
time.Sleep(time.Second) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why the sleep?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This only happens when there is a critical error in the event handling loop, which in most cases would be API connection timing out / disconnecting, and this sleep prevents unnecessarily spamming the logs
This is still a bit of a WIP, and won't be done done until the actor methods are implemented.
However, I think theres room for some review already.