fix: num_dir_sectors #53
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
francisdb
force-pushed
the
fix/num_dir_sectors
branch
2 times, most recently
from
ef72c7e
to
d60e00d
Compare
francisdb
commented
Apr 5, 2024
francisdb
force-pushed
the
fix/num_dir_sectors
branch
from
d60e00d
to
4ef929c
Compare
|
Looks like the linter is unhappy, so the tests didn't run. I just fixed the config (I think) so that next time the tests can still run even if the linter fails. |
|
@mdsteele applied cargo fmt |
|
Can I get a CI approval? |
|
Thanks for the fix! |
|
Any plans for a release? |
|
Published as v0.10.0. |
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Correctly update file header
num_dir_sectorswhen new directory sectors are added.fixes #52