Open muschellij2 opened 3 years ago
The print out error is a cosmetic bug via print S3 method here:
The instance object itself will still be valid if you view it via str()
- but it should also make sure the zone is valid - I guess if the API didn't error it ignroed it?
Yeah the error is spurious, it’s the underlying call that is problematic and surprising it doesn’t return an error message. I added some validation in my Frankenstein PR.
On Thu, Sep 2, 2021 at 4:36 AM Mark @.***> wrote:
The print out error is only the print S3 method here:
The instance object itself will still be valid if you view it via str() - but it should also make sure the zone is valid - I guess if the API didn't error it ignroed it?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/cloudyr/googleComputeEngineR/issues/180#issuecomment-911390312, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAIGPLSXWB6OZXPO2XWUIMDT74ZRJANCNFSM5DHTFXMA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
-- Best, John
Describe the bug I accidentally sent a bad zone and
gce_get_instance
didn't fail. This affectsgce_vm
in the error catching. It didn't cause an error. It errors only when you go to show the object:Created on 2021-09-01 by the reprex package (v2.0.0)