We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Sometimes the bot sends a message "⚠️ Something went wrong" and the console shows the following output:
26/11/24 21:05:59 [ERROR] (PRISMA) ticket.update Invalid `prisma.ticket.update()` invocation: Error occurred during query execution: ConnectorError(ConnectorError { user_facing_error: None, kind: ConnectionError(Timed out during query execution.), transient: false }) 26/11/24 21:05:59 [ERROR] (BUTTONS) 67463837M0 26/11/24 21:05:59 [ERROR] (MODALS) "feedback" modal execution error: PrismaClientUnknownRequestError: Invalid `prisma.ticket.update()` invocation: Error occurred during query execution: ConnectorError(ConnectorError { user_facing_error: None, kind: ConnectionError(Timed out during query execution.), transient: false }) at Rn.handleRequestError (/app/node_modules/.pnpm/@[email protected][email protected]/node_modules/@prisma/client/runtime/library.js:174:7499) at Rn.handleAndLogRequestError (/app/node_modules/.pnpm/@[email protected][email protected]/node_modules/@prisma/client/runtime/library.js:174:6754) at Rn.request (/app/node_modules/.pnpm/@[email protected][email protected]/node_modules/@prisma/client/runtime/library.js:174:6344) at async module.exports (/app/src/lib/middleware/prisma-sqlite.js:44:15) at async FeedbackModal.run (/app/src/modals/feedback.js:34:18) { clientVersion: '4.16.2' }
Working
Could not reliably reproduce. But often happens when using the /claim and /close command (which soft locks the ticket)
- OS: Docker image
I use the sqlite database, because it's easier for me to manage
The text was updated successfully, but these errors were encountered:
This might indicate that your bot is too active for SQLite to keep up, and you should switch to MySQL or PostgreSQL.
Sorry, something went wrong.
No branches or pull requests
Is there an existing issue for this?
Current Behavior
Sometimes the bot sends a message "⚠️ Something went wrong" and the console shows the following output:
Expected Behavior
Working
Steps To Reproduce
Could not reliably reproduce. But often happens when using the /claim and /close command (which soft locks the ticket)
Environment
- OS: Docker image
Anything else?
I use the sqlite database, because it's easier for me to manage
The text was updated successfully, but these errors were encountered: