UNVERIFIED: fix nil panic due to nil msBuilder #6184
Draft
+7
−6
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.
admin kafka rereplicate
is hitting nil panics on some workflows, and this appears to be the source: a nil mutablestate builder.I've added it here and am running tests and it may be the fix, but I am NOT yet sure:
An example of the panic:
This appears to be a nil mutable state builder at service/history/execution/history_builder.go:345, which looks like it can only come from
HistoryBuilder
instances created byNewHistoryBuilderFromEvents
because it doesn't set that field.I have not yet figured out why that function doesn't set that field though.