-
Notifications
You must be signed in to change notification settings - Fork 11
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
2 changed files
with
6 additions
and
1 deletion.
There are no files selected for viewing
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
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
96236cc
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello, has this version been published to the registry? Cargo cant' seem to find
0.1.17+minimap2.2.27
96236cc
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
96236cc
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Got it, thank you!
96236cc
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Ge0rges Minimap 2.27 has introduced a strange bug, that only occurs in --release mode
So cargo test works, cargo test --release fails. This may take a bit of time to debug, although hopefully it's solved in a day or two!
"process didn't exit successfully:
/mnt/data/development/minimap2-rs/minimap2-sys/target/release/deps/minimap2_sys-39c0cae99373aa42
(signal: 11, SIGSEGV: invalid memory reference)"96236cc
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Ge0rges nevermind, it was an issue with mm2-fast headers overwriting minimap2 headers, and being incompatible (now). Fixed, and release has been pushed out!
96236cc
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great glad you caught it, I was just sitting down to look at this and the Async feature. Will get back to the latter in a sec.