[Bug] Error in tRPC handler (lambda) on path: message.updateTTS, type: mutation when try to use TTS function

[sunrisewestern]

📦 Environment

Docker

📌 Version

v1.45.5

💻 Operating System

macOS

🌐 Browser

Chrome

🐛 Bug Description

Error when try to use TTS function.

Error Log:

{"level":30,"time":1736482729810,"pid":28,"hostname":"b922e7c2a77d","msg":"Error in tRPC handler (lambda) on path: message.updateTTS, type: mutation"}
Error [TRPCError]: No values to set
    at h (.next/server/chunks/2915.js:23:41110)
    at L.set (.next/server/chunks/2915.js:17:36832)
    at et.updateTTS (.next/server/chunks/17836.js:1:29886)
    at async a.middlewares (.next/server/chunks/12620.js:1:5567)
    at async f (.next/server/chunks/12620.js:4:68)
    at async f (.next/server/chunks/12620.js:4:68)
    at async f (.next/server/chunks/12620.js:4:68)
    at async f (.next/server/chunks/12620.js:4:68)
    at async r (.next/server/chunks/12620.js:1:5799) {
  code: 'INTERNAL_SERVER_ERROR',
  [cause]: Error: No values to set
      at h (.next/server/chunks/2915.js:23:41110)
      at L.set (.next/server/chunks/2915.js:17:36832)
      at et.updateTTS (.next/server/chunks/17836.js:1:29886)
      at async a.middlewares (.next/server/chunks/12620.js:1:5567)
      at async f (.next/server/chunks/12620.js:4:68)
      at async f (.next/server/chunks/12620.js:4:68)
      at async f (.next/server/chunks/12620.js:4:68)
      at async f (.next/server/chunks/12620.js:4:68)
      at async r (.next/server/chunks/12620.js:1:5799)
}

📷 Recurrence Steps

No response

🚦 Expected Behavior

No response

📝 Additional Information

No response

[lobehubbot]

👀 @sunrisewestern

Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible.
Please make sure you have given us as much context as possible.
非常感谢您提交 issue。我们会尽快调查此事，并尽快回复您。 请确保您已经提供了尽可能多的背景信息。

[dosubot]

Hey @sunrisewestern! I'm here to help you with any bugs, questions, or contributions you have. Let's squash this bug together!

The error message "No values to set" in the message.updateTTS mutation suggests that the input provided to the mutation might be missing or incorrectly formatted. The updateTTS function expects an input object with an id and a value that can either be an object containing optional contentMd5, file, and voice fields, or a literal false to delete the TTS data ^[1].

Here are a few things to check and try:

1. Ensure Correct Input Format: Verify that the input to the updateTTS mutation is correctly formatted. It should look something like this:

   {
     id: "your-message-id",
     value: {
       contentMd5: "your-md5",
       file: "your-file",
       voice: "your-voice"
     }
   }

   Or, if you intend to delete the TTS data:

   {
     id: "your-message-id",
     value: false
   }

2. Check for Missing Fields: Make sure that at least one of the fields (contentMd5, file, or voice) is provided in the value object if you are not deleting the TTS data. An empty object might trigger the "No values to set" error.

3. Review Recent Changes: If there have been recent changes to the codebase, ensure that they haven't affected the expected input structure or the handling of the updateTTS mutation.

By ensuring the input is correctly structured and contains the necessary fields, you should be able to resolve the error. If the issue persists, further investigation into the specific implementation details of the updateTTS function might be necessary.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}