Logic error in canIDeploy when using -Platest=tag
See original GitHub issueThere appears to be a logic error in the canIDeploy
task: when using -Platest=TAG
, the task always fails. The task should fail when neither a version nor latest
was specified. The instanceof
term should probably have been negated:
As is, whenever a tag is specified, latest
will be an instance of Latest.UseLatestTag
, and the LHS of the &&
operator evaluates to true
, throwing an exception.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Incorrect error message for canIDeploy failed gradle task #1393
I am unable to replicate this. Can you provide the versions of Pact-JVM, Gradle and the Pact broker you are using? I have...
Read more >Auto Layout Guide: Logical Errors - Apple Developer
Describes the constraint-based system for laying out user interface elements.
Read more >PM51402: MESSAGE DFS3178E MSC DETECTED AN ... - IBM
MSC detected an internal logic error when a /RST LINK command was issued for a TCP/IP link. Error message DFS3178E with RETCODE=00000000, RSNCODE=000007C ......
Read more >Can I Deploy | Pact Docs
How to use Pact + the can-i-deploy tool to ensure that you are safe to deploy your application.
Read more >2.9.1. Logical Errors And Using The Debugger
Compare the calculated results with those produced by the program to locate where the error is in the code. Steps for locating a...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ideally, your pipeline would have it as a property, even if it got generated by the application.
Any chance this bug can still be fixed, to match the logic in the Ruby client?