-
Notifications
You must be signed in to change notification settings - Fork 911
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error converting NULL to string is unsupported after upgrade to v1.27.0 #7376
Comments
@yycptt : Any update on this, I am facing same issue after upgrade. |
Temporal history Error: {"level":"info","ts":"2025-02-24T09:55:48.092Z","msg":"none","shard-id":205,"address":"10.11.82.208:7234","lifecycle":"Started","component":"shard-context","logging-call-at":"/home/runner/work/docker-builds/docker-builds/temporal/service/history/shard/context_impl.go:1631"} Temporal matching error: {"level":"info","ts":"2025-02-24T09:58:52.737Z","msg":"history client encountered error","service":"matching","error":"assertCurrentExecution failed. Unable to load current record. Error: sql: Scan error on column index 10, name "data_encoding": converting NULL to string is unsupported","service-error-type":"serviceerror.Unavailable","logging-call-at":"/home/runner/work/docker-builds/docker-builds/temporal/client/history/metric_client.go:103"} Also there is spike in database wait time and CPU, sharing screenshot for reference, below screenshot is for 90 minute, I have updated temporal 75 minute ago. ![]() |
We're seeing the same error in our testing environment. I believe it was introduced with #7080 as it adds the However, the model in Go uses a Pausing the upgrade to 1.27 for now. |
There's a PR to resolve this issue. |
Expected Behavior
Actual Behavior
Steps to Reproduce the Problem
Specifications
The text was updated successfully, but these errors were encountered: