This repository was archived by the owner on Apr 9, 2020. It is now read-only.
respect timeout value in config file #482
Closed
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
ayanamist
changed the title
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Since
ss.UpdateConfigwill merge non-zero value innew, butcmdConfigfromflag.Parsewill always has a default value (300) fromflag.IntVar(&cmdConfig.Timeout, ....), so thetimeoutvalue from config file will always be overwritten until explicit specify-t xxxin cmd line.This PR fix this issue and respect
timeoutvalue in config file if no-t xxxis specified in cmd line.