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.

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

Aggressive Asserts in Runtime lead to un-necessary server shutdowns #260

Open
ifadams opened this issue Dec 18, 2024 · 0 comments
Open

Aggressive Asserts in Runtime lead to un-necessary server shutdowns #260

ifadams opened this issue Dec 18, 2024 · 0 comments
Assignees
Labels
Bug Indicates unexpected or undesired behaviors Priority: Backlog Tasks that are not pressing, but to be tracked and revisited

Comments

@ifadams
Copy link
Contributor

ifadams commented Dec 18, 2024

Describe the bug

Currently, there are asserts in the runtime path (e.g. within the descriptor set commands) to verify certain return values are present in metadata queries. However, the use of these asserts can lead to abrupt server shutdowns, disrupting client use.

It looks like the intent of this was to prevent data corruption, however its use in later parts of the query flow means that any opportunity to prevent metadata inconsistency (in particular, for PMGD based handlers) has already passed, or is not actually relevant as it we are only returning information, not creating any new entries within VDMS.

To Reproduce

Create a FindDescriptor query with an aggressive set of constraints to limit the number of returned entities to zero. This will potentially trigger the assert failure, despite not actually leading to the system being in a dangerous state.

Expected behavior

VDMS should return a relevant error to the client, instead of fully shutting down the server in response.

@ifadams ifadams added Bug Indicates unexpected or undesired behaviors Priority: Backlog Tasks that are not pressing, but to be tracked and revisited labels Dec 18, 2024
@ifadams ifadams self-assigned this Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Indicates unexpected or undesired behaviors Priority: Backlog Tasks that are not pressing, but to be tracked and revisited
Projects
None yet
Development

No branches or pull requests

1 participant