Skip to content

Conversation

zanieb
Copy link
Member

@zanieb zanieb commented Aug 28, 2024

Consistency etc. when debugging a deadlock

@zanieb zanieb added the tracing Verbose output and debugging label Aug 28, 2024
@zanieb zanieb requested a review from charliermarsh August 28, 2024 21:59
@zanieb zanieb enabled auto-merge (squash) August 29, 2024 20:30
@zanieb zanieb merged commit 206b136 into main Aug 29, 2024
56 checks passed
@zanieb zanieb deleted the zb/lock-debug branch August 29, 2024 20:35
err
);
} else {
debug!("Released lock at `{}`", self.0.path().display());
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be trace! like the above?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe since it comes after all the other output.

)
})?;

debug!("Acquired lock for `{resource}`");
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be trace! like the above?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think so — the acquired lock message above is debug level. The trace logs are for the acquire lock error message and the check message.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It still feels like a lot for --verbose IMO.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's fine with me I think, but we'll want to change both.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

tracing Verbose output and debugging

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants