Skip to content

Change assert in ringbuffer to a return code#492

Merged
chrissie-c merged 1 commit intoClusterLabs:mainfrom
chrissie-c:noassert
Nov 15, 2023
Merged

Change assert in ringbuffer to a return code#492
chrissie-c merged 1 commit intoClusterLabs:mainfrom
chrissie-c:noassert

Conversation

@chrissie-c
Copy link
Copy Markdown
Contributor

Why just this one?

There are LOADS of asserts in libqb, some are OK and some may be overkill. This one in particular is causing CI failures and so annoys me more than the rest.

Why just this one?

There are LOADS of asserts in libqb, some are OK and some may be
overkill. This one in particular is causing CI failures
and so annoys me more than the rest.
Copy link
Copy Markdown
Member

@jfriesse jfriesse left a comment

Choose a reason for hiding this comment

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

ACK - very specific conditions must be met to make this assert happen, but it is weird when user app asserts unexpectedly.

@chrissie-c chrissie-c merged commit 9297df4 into ClusterLabs:main Nov 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants