Fix bug where backends:list and backends:get command fails when no backends exists. #6600
Conversation
This file contains hidden or 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
|
Current dependencies on/for this PR:
This stack of pull requests is managed by Graphite. |
fb40e82 to
e84bf5e
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #6600 +/- ##
=======================================
Coverage 54.28% 54.28%
=======================================
Files 347 347
Lines 24077 24077
Branches 4971 4971
=======================================
+ Hits 13069 13071 +2
+ Misses 9807 9806 -1
+ Partials 1201 1200 -1 ☔ View full report in Codecov by Sentry. |
e84bf5e to
ef23437
Compare
Yuangwang
approved these changes
Dec 8, 2023
When no backends resource exists, the CLI expects the API to respond as:
{ backends: [] }However, the API actually responds with
{}Also including small updates on how the outputs are logged to the screen.