[CHORE] Enable debug in test profile #3135
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
CodSpeed Performance ReportMerging #3135 will not alter performanceComparing Summary
|
universalmind303
approved these changes
Oct 28, 2024
sagiahrac
pushed a commit
to sagiahrac/Daft
that referenced
this pull request
Nov 4, 2024
I'm using RustRover to code and debug Rust related code and I noticed the debug run in RustRover doesn't work out of box: there's no variable showing when breakpoint is hit. It turns out that the RustRover IDE will launch debug process with test profile, which is inherited from dev[^1] profile. I am not sure why the dev[^2] profile in this project is configured without debug enabled. I add the test profile with debug enabled in this PR. [^1]: https://doc.rust-lang.org/cargo/reference/profiles.html#test [^2]: https://github.com/Eventual-Inc/Daft/blob/main/Cargo.toml#L86
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.
I'm using RustRover to code and debug Rust related code and I noticed the debug run in RustRover doesn't work out of box: there's no variable showing when breakpoint is hit.
It turns out that the RustRover IDE will launch debug process with test profile, which is inherited from dev1 profile. I am not sure why the dev2 profile in this project is configured without debug enabled. I add the test profile with debug enabled in this PR.
Footnotes
https://doc.rust-lang.org/cargo/reference/profiles.html#test ↩
https://github.com/Eventual-Inc/Daft/blob/main/Cargo.toml#L86 ↩