don't try to use token if it is falsy
#234
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
Today it checks specifically if `token` is `None`. It might as well check that it's not `""` either.
Codecov Report
@@ Coverage Diff @@
## master #234 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 6 6
Lines 291 291
=========================================
Hits 291 291 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
albi3ro
approved these changes
Nov 16, 2022
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.
Today it checks specifically if
tokenisNone. It might as well check that it's not""either.Context: if you have the
IBMQX_TOKENenvironment variable set to the empty string (rather than just not set), it tries to connect and you get an ugly HTTP error instead of the expected "no token provided" error. This fixes that. This was caught on PennyLane Cloud, where that would happen by default.