-
Notifications
You must be signed in to change notification settings - Fork 36
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
wip: socks 5 test #132
Closed
Closed
wip: socks 5 test #132
Changes from 12 commits
Commits
Show all changes
18 commits
Select commit
Hold shift + click to select a range
e10f6ad
enable test and extract vars
mario-s 3fc43a9
pattern matching for vars
mario-s ed8a0ee
add test-with
mario-s aaf0a90
reduce ws
mario-s 31c4e06
rename VAR
mario-s f1fabac
add doc
mario-s a07e758
typo
mario-s 63cfd4d
formart
mario-s fd50a51
ws
mario-s a95dacd
take formart from main
mario-s 8e714f0
remove redundant clone
mario-s 3a044e5
remove obsolete comment
mario-s a512ba9
replace lib with macro
mario-s 0248157
fmt
mario-s e5e171f
revert accidently renaming of file
mario-s 1a3fe85
tryout proxy
mario-s c88c64e
use proxy-tools as forward
mario-s 01f6fb1
add hint for proxy in README
mario-s File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
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
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
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.
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.
I consider that a pretty major drawback. This is the reason why we use some custom macro for the other environment variables. Would be great if you could use a similar approach.
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.
Sure, I changed that to use a macro. However the drawback of this approach is, that you don't see that the test is skipped.
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.
Yeah, the macro is not ideal. My hope is that rust-lang/rfcs#3221 will be accepted and we can get the best of both worlds. But until then the skipping won't be reported properly.
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.
Hi,
this is something you may want to use for this scenario.
https://crates.io/crates/test-with
If you are using CI tool for testing, or under development with source code changing, you do not need cargo clean before testing.
Besides, the test report from cargo will change to the following format for a better understanding.
If there is any issue on the crate, an issue is always welcome. :)
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.
By the way, there is more than one issue in
#[ignore(if)]
, so it might not be the better solution to solve. It is good to keep ignoring in runtime and ignoring under conditions separately.The following are related PR and issues in Rust, for you to know more about these if you are interested.
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.
I'm not to worried about the CI and the env variable handling there. Ignoring tests and build time instead of runtime is IMHO a messy DX (developer experience). Rskafka is already a somewhat complicated crate -- especially when you consider the integration tests. Sure, not having a proper "ignore" status for skipped tests is bad DX as well, but I consider this the lesser evil.
So let's wait until Rust implements the required feature. I've created #139 to track this on our side.
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.
You could assign the #139 to me as well, I would be more than happy to integrate the feature, when Rust is ready.