监控任务执行异常
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 877
- Forks
- 107
- PR merge metrics
- No merged PRs in 30d
Description
经常会报这个错误,不知道什么原因
coolmonitor-1 | 监控检查异常 cmgq7ae3w002frz01154lrv7s: Error [PrismaClientKnownRequestError]:
coolmonitor-1 | Invalid prisma.monitorStatus.create() invocation:
coolmonitor-1 |
coolmonitor-1 |
coolmonitor-1 | Operations timed out after N/A. Context: The database failed to respond to a query within the configured timeout — see https://pris.ly/d/sqlite-connector for more details. Database: /app/prisma/../data/coolmonitor.db
coolmonitor-1 | at async nv (.next/server/chunks/6971.js:87:152)
coolmonitor-1 | at async ny (.next/server/chunks/6971.js:81:1640)
coolmonitor-1 | at async h.fn (.next/server/chunks/6971.js:66:359)
coolmonitor-1 | at async h._trigger (.next/server/chunks/1043.js:1:33561) {
coolmonitor-1 | code: 'P1008',
coolmonitor-1 | meta: [Object],
coolmonitor-1 | clientVersion: '6.6.0'
coolmonitor-1 | }
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the monitoring check that calls Prisma's monitorStatus.create() and inspect the SQLite database at data/coolmonitor.db. Trace the P1008 timeout from the reported operation and determine the conditions that cause the database not to respond within the configured timeout. Done means the cause is identified and the monitoring task no longer reports this failure under the affected conditions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sqlite, typescript
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100