Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Sealing: Include worker name/id in sealing errors #6147

Closed
magik6k opened this issue Apr 30, 2021 · 1 comment
Closed

Sealing: Include worker name/id in sealing errors #6147

magik6k opened this issue Apr 30, 2021 · 1 comment
Labels
area/sealing dif/medium Prior development experience with lotus is likely helpful effort/hours Effort: Hours help wanted Extra attention is needed kind/enhancement Kind: Enhancement P3 P3: Might get resolved

Comments

@magik6k
Copy link
Contributor

magik6k commented Apr 30, 2021

No description provided.

@Shekelme
Copy link

It's a good idea to add add a pointer to the specific worker on which sealing error occurred in the log entries. The sector can walk in circles all night, and Iit's hard to identify on which worker this problem is.

@magik6k magik6k added area/sealing dif/medium Prior development experience with lotus is likely helpful effort/hours Effort: Hours help wanted Extra attention is needed kind/enhancement Kind: Enhancement P3 P3: Might get resolved labels Apr 30, 2021
@llifezou llifezou mentioned this issue Dec 23, 2021
Merged
magik6k added a commit that referenced this issue Mar 2, 2022
@magik6k
Merge pull request #7844 from llifezou/add_workerName_in_sealing_err
a6892f9 
feat: #6147: Include worker name in sealing errors
@magik6k magik6k closed this as completed Mar 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/sealing dif/medium Prior development experience with lotus is likely helpful effort/hours Effort: Hours help wanted Extra attention is needed kind/enhancement Kind: Enhancement P3 P3: Might get resolved
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@magik6k @Shekelme