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.

Sign up for GitHub

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

Jump to bottom

Fix regression #239

Merged
merged 2 commits into from
May 31, 2024
Merged

Fix regression #239

merged 2 commits into from
May 31, 2024

Conversation

mindflayer
Copy link
Owner

I managed to fix #237 and make it work for all the use-cases.

@coveralls
Copy link

Coverage Status

coverage: 98.706% (+0.2%) from 98.537%
when pulling 547eb56 on fix/237
into 501088e on main.

2 similar comments
@coveralls
Copy link

Coverage Status

coverage: 98.706% (+0.2%) from 98.537%
when pulling 547eb56 on fix/237
into 501088e on main.

@coveralls
Copy link

Coverage Status

coverage: 98.706% (+0.2%) from 98.537%
when pulling 547eb56 on fix/237
into 501088e on main.

@coveralls
Copy link

coveralls commented May 31, 2024 •
edited
Loading

Coverage Status

coverage: 98.824% (+0.3%) from 98.537%
when pulling e56fead on fix/237
into 501088e on main.

@sonarcloud SonarCloud
Copy link

sonarcloud bot commented May 31, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@mindflayer mindflayer merged commit 0c5c07a into main May 31, 2024
7 checks passed
@mindflayer mindflayer deleted the fix/237 branch May 31, 2024 08:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Regression in 3.12.7
2 participants
@mindflayer @coveralls