This repository has been archived by the owner on Jan 8, 2024. It is now read-only.
Backport of fix: Catch panic when null value defined in string variable into release/0.10.x #4069
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.
Backport
This PR is auto-generated from #4067 to be assessed for backporting due to the inclusion of the label backport/0.10.x.
The below text is copied from the body of the original PR.
This commit allows for us to emit a more helpful error message when a null value is passed into a variable where we were expecting a string.
Fixes #4051