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

[pull] main from schollz:main #11

Merged
merged 8 commits into from
May 20, 2024
Merged

[pull] main from schollz:main #11

merged 8 commits into from
May 20, 2024

Conversation

pull[bot]
Copy link

@pull pull bot commented May 20, 2024

See Commits and Changes for more details.


Created by pull[bot]

Can you help keep this open source service alive? 💖 Please sponsor : )

black-night-heron and others added 8 commits April 20, 2024 18:40
The Go Race Detector pointed out a data race between
the methods ChangeMax64 and State or GetMax64.
State already takes the lock, but others did not.
Display elapsed time at the end of the bar when elapsedTime is enabled
while predictTime is set to false.

Demo:
```
70% |███████   |  [0s]
```
…ent-bytes

Finish() should update state.currentBytes
fix race condition when changing max
fix: make elapsedTime option work in non-spinner mode
@pull pull bot added the ⤵️ pull label May 20, 2024
@pull pull bot merged commit fe6592d into oerlikon:main May 20, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants