监控任务执行异常
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- sqlite, typescript
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.
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 | }
- Dominant language
- TypeScript
- Stars
- 877
- Forks
- 107
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from star7th/coolmonitor
-
首页的响应时间趋势，可以多扩张一点么？Open
Difficulty 3/5 1-2 days Newbie friendliness 55/100
star7th/coolmonitor#68 · 2 comments ·
-
可以加 网站被攻击 的监控吗Open
Difficulty 5/5 Over a week Newbie friendliness 35/100
star7th/coolmonitor#67 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
star7th/coolmonitor#66 · 6 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
star7th/coolmonitor#65 · 1 comment ·
-
站点状态显示有误Open
Difficulty 3/5 1-2 days Newbie friendliness 35/100
star7th/coolmonitor#64 · 3 comments ·
All issues in star7th/coolmonitor
Similar issues
-
bug via-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pingdotgg/t3code#14452 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
solana-foundation/program-examples#747 · 1 comment ·
Maintainers usually reply within 9 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
remotion-dev/remotion#11847 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
openwatersio/slackwater#355 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
melgarafael/DeskcommCRM#1998 · 3 comments ·
Maintainers usually reply within 1 day