You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
After upgrading to v3, if Deckboard runs in touch mode, there's a good chance the error message below will pop up after Windows wakes up from sleep:
A JavaScript error occurred in the main process
Uncaught Exception:
Error [ERR_INTERNAL_ASSERTION]: This is caused by either a bug in Node.js or incorrect
usage of Node.js internals.
Please open an issue with this stack trace at https://github.com/nodejs/node/issues
at new NodeError (node:internal/errors:406:5)
at assert (node:internal/assert:14:11)
at internalConnectMultiple (node:net:1118:3)
at afterConnectMultiple (node:net:1667:5)
I never saw this error with version 2.x.
To Reproduce
Steps to reproduce the behavior:
Run deckboard in touch mode on Windows
Sleep and wake up Windows
See the error at a probability.
Expected behavior
No error occurs.
Screenshots
Server App (please complete the following information):
OS: Windows 11
Version 3.0.0
Client App (please complete the following information):
Not applicable
Required files
database.db (located in C:\Users%USER%\deckboard)
log.log (located in located in C:\Users%USER%\AppData\Roaming\Deckboard) database and log.zip
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
After upgrading to v3, if Deckboard runs in touch mode, there's a good chance the error message below will pop up after Windows wakes up from sleep:
I never saw this error with version 2.x.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
No error occurs.
Screenshots
Server App (please complete the following information):
Client App (please complete the following information):
Not applicable
Required files
C:\Users%USER%\deckboard
)C:\Users%USER%\AppData\Roaming\Deckboard
)database and log.zip
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: