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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix two code scanning alerts #186

Merged
merged 2 commits into from Apr 30, 2023
Merged

Conversation

AmoebeLabs
Copy link
Owner

These were actual for loop bugs...

Description

For some reason, som of the older LGTM alerts were actually bugs. Two of them had the for loop wrong, the parameters were mixed 馃槩

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

@AmoebeLabs AmoebeLabs added this to the Release v2.4.1 milestone Apr 30, 2023
@AmoebeLabs AmoebeLabs self-assigned this Apr 30, 2023
@AmoebeLabs AmoebeLabs added bug Something isn't working Code Quality labels Apr 30, 2023
@AmoebeLabs AmoebeLabs merged commit a670dc7 into master Apr 30, 2023
4 checks passed
@AmoebeLabs AmoebeLabs deleted the fix-some-code-scanning-alerts branch May 6, 2023 12:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Code Quality
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant