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

Bugfix/207 incorrect playbook initialisation can lead to segfaults #208

Conversation

MaartendeKruijf
Copy link
Collaborator

No description provided.

@MaartendeKruijf MaartendeKruijf linked an issue Aug 8, 2024 that may be closed by this pull request
@MaartendeKruijf MaartendeKruijf marked this pull request as ready for review August 8, 2024 07:38
@MaartendeKruijf
Copy link
Collaborator Author

@lucamrgs, @RabbITCybErSeC NOTE: this update does not fix this issue in the Mongo database. But for that we need to rework the database code see #209

Copy link
Collaborator

@lucamrgs lucamrgs left a comment

Choose a reason for hiding this comment

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

Looks good to me, more explicit playbook data definition and more predictable behaviour. Good catch.

@MaartendeKruijf MaartendeKruijf merged commit 5f7ccd5 into development Aug 8, 2024
9 checks passed
@MaartendeKruijf MaartendeKruijf deleted the bugfix/207-incorrect-playbook-initialisation-can-lead-to-segfaults branch August 8, 2024 09:08
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.

Incorrect playbook initialisation can lead to segfaults
2 participants