[Bug] Error reporting that does not affect project operation

[hurcaguari]

📦 Environment

Docker

📌 Version

lobehub/lobe-chat-database:v1.44.0

💻 Operating System

Linux debian 6.1.0-28-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.119-1 (2024-11-22) x86_64

🌐 Browser

Chrome

🐛 Bug Description

logto + minio deploy

{
allowDangerousEmailAccountLinking: true,
clientId: undefined,
clientSecret: undefined,
platformType: 'WebsiteApp',
profile: [Function: profile]
}
(node:28) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.
(Use node --trace-deprecation ... to show where the warning was created)
{
allowDangerousEmailAccountLinking: true,
clientId: undefined,
clientSecret: undefined,
platformType: 'WebsiteApp',
profile: [Function: profile]
}
{"level":30,"time":1736460505752,"pid":28,"hostname":"3c5c060d26a0","msg":"Error in tRPC handler (lambda) on path: message.countToday, type: unknown"}
Error [TRPCError]: No procedure found on path "message.countToday"
at <unknown> (.next/server/chunks/67588.js:1:7390)
at Array.map (<anonymous>)
at g (.next/server/chunks/67588.js:1:7317)
at async n (.next/server/chunks/92347.js:1:401) {
cause: undefined,
code: 'NOT_FOUND'
}
{"level":30,"time":1736460516693,"pid":28,"hostname":"3c5c060d26a0","msg":"Error in tRPC handler (lambda) on path: message.countToday, type: unknown"}
Error [TRPCError]: No procedure found on path "message.countToday"
at <unknown> (.next/server/chunks/67588.js:1:7390)
at Array.map (<anonymous>)
at g (.next/server/chunks/67588.js:1:7317)
at async n (.next/server/chunks/92347.js:1:401) {
cause: undefined,
code: 'NOT_FOUND'
}

📷 Recurrence Steps

An error will appear directly after startup, but the service is running normally and the connection between the database and the authentication service is normal

🚦 Expected Behavior

It's just annoying to see an error message.

📝 Additional Information

No response

[lobehubbot]

👀 @hurcaguari

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]

@hurcaguari 你好! 我是Dosu，我是一个可以帮助你解决 bug、回答问题并成为贡献者的机器人。如果你有任何问题，我会在等待人类维护者的时候帮助你。

The issues you're encountering seem to be related to two main problems: the deprecation warning for the punycode module and the "No procedure found" error for the message.countToday path in the tRPC handler.

1. Deprecation Warning for punycode: The punycode module is deprecated, and it's recommended to use a userland alternative. Unfortunately, I couldn't find specific guidance in the repository on how to resolve this warning. You might consider checking if any dependencies in your project are using punycode and updating them to versions that no longer rely on it.

2. "No procedure found" Error for message.countToday: This error indicates that the message.countToday procedure is not defined in the tRPC handler. Common causes for this error include:

   • The procedure name might not match any defined routes in the edgeRouter.
   • The procedure could be defined in a different router not included in the edgeRouter.
   • There might be a typo or incorrect path when invoking the procedure.
   • Required middleware might not be correctly applied or configured ^[1].

To resolve the "No procedure found" error, you should verify that the message.countToday procedure is correctly defined and included in the appropriate router. Additionally, ensure that any necessary middleware is properly configured.

To continue talking to Dosu, mention @dosu.

---

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

[dosubot]

The error message you're encountering indicates that the message.countToday procedure is not found in the tRPC handler. This could be due to several reasons:

1. Procedure Not Defined: The message.countToday procedure might not be defined in the codebase. You should check if this procedure is implemented and correctly registered in the tRPC router.

2. Incorrect Path: Ensure that the path used to call the procedure matches exactly with the defined path in the router. Any mismatch can lead to a "No procedure found" error.

3. Router Configuration: Verify that the router where message.countToday is supposed to be defined is included in the main tRPC router configuration. If it's defined in a separate module, it needs to be imported and included properly.

4. Middleware Issues: If the procedure requires specific middleware, ensure that it is correctly applied. Missing or misconfigured middleware can also cause such errors.

Regarding the deprecation warning for the punycode module, this is a Node.js warning indicating that the punycode module is deprecated. You should consider using a userland alternative or updating any dependencies that might be using this module.

For the clientId and clientSecret being undefined, ensure that these values are correctly set in your environment variables or configuration files. They are typically required for authentication purposes, and missing values might lead to further issues.

If these suggestions don't resolve the issue, you might need to look deeper into the codebase or configuration files to ensure everything is set up correctly.

To continue talking to Dosu, mention @dosu.

---

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