Shawn Hartsell

Makes sense, and yes, something like `NewClientWithError` would work. Specifically, I'm instrumenting a business critical service and want to have the option to not spin it up if initialization fails...

I imagine we could also do what we needed if https://github.com/aws/aws-sdk-go-v2/issues/941 is implemented as well

> Hi @shawnHartsell thanks for reaching out. Can you provide sample of reproducible code to help us investigate this behavior? The tricky bit is that this isn't reproducible by client...

> Do you still have the test code you mentioned above? Unfortunately I don't. I discovered the issue while debugging into the library on a separate issue.

> On v1.10.x we made the decision into de-coupling the go and ruby versions for that particular reason, as doing major changes in ruby, should not need a bump into...

> Thanks. That inconsistency should be fixed. Until then, detailed documentation about this behavior will help us. I am porting a service over from V1 to V2 and noticed that...

Below is the exact error message from one of our failing builds. We are currently using `1.10.0` of `twirp-ruby` ``` An error occurred while installing json (2.7.2), and Bundler cannot...