WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content

fix: when setMaxDetailRow() but not use AddDetail(), cause index out of range. #214

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
Merged
schollz merged 1 commit into from
Jan 24, 2025
Merged

fix: when setMaxDetailRow() but not use AddDetail(), cause index out of range. #214

schollz merged 1 commit into from
Jan 24, 2025

Conversation

@chengxilo
Copy link
Contributor

@chengxilo chengxilo commented Jan 24, 2025

fix: #212
when user do not add detail, the progress bar will panic because index out of range.

@schollz schollz merged commit d367bcc into schollz:main Jan 24, 2025
1 check passed
@chengxilo chengxilo deleted the fix_index_out_of_range_when_no_details branch January 24, 2025 22:41
@chengxilo
Copy link
Contributor Author

chengxilo commented Jan 24, 2025

Thanks.🥰

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.

bar.Finish() cause panic: runtime error: index out of range [-1]

2 participants

@chengxilo @schollz