Skip to content

Clarify security; state that [] is undefined behaviour #4011

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

Closed
wants to merge 1 commit into from

Conversation

rvedotrc
Copy link

Port of #4007 to v3.2.0-dev

@rvedotrc rvedotrc force-pushed the v3.2.0-dev-clarify-security branch 2 times, most recently from 8259a02 to 182de52 Compare August 12, 2024 17:29
@handrews handrews added security security: config The mechanics of severs and structure of security-related objects labels Aug 12, 2024
@rvedotrc rvedotrc changed the title Clarify security; state that [] is undefined behaviour Clarify security; state that [] is undefined behaviour Aug 12, 2024
@handrews handrews added this to the v3.2.0 milestone Aug 22, 2024
@rvedotrc rvedotrc force-pushed the v3.2.0-dev-clarify-security branch from 182de52 to 7543a25 Compare August 25, 2024 09:49
@handrews
Copy link
Member

In today's TDC we agreed to re-try this based on @mikekistler 's "open world" view, so closing these three attempts.

@rvedotrc thank you for your contributions here- it is far from the first topic where we've had to go through multiple approaches, attempts, and PRs. Regardless of who writes the final PR, this has helped us immensely in figuring the problem out.

@handrews handrews closed this Aug 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
security: config The mechanics of severs and structure of security-related objects security
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants