Skip to content
New issue

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

Fatal error: Uncaught Error: The SQLite3Result object has not been correctly initialised or is already closed #77

Closed
2 tasks done
lekoala opened this issue Jun 26, 2024 · 1 comment · Fixed by #78
Closed
2 tasks done

Comments

@lekoala
Copy link
Collaborator

lekoala commented Jun 26, 2024

Module version(s) affected

3

Description

I get this very odd error in my unit tests

Fatal error: Uncaught Error: The SQLite3Result object has not been correctly initialised or is already closed

Full stack

PHP Fatal error: Uncaught Error: The SQLite3Result object has not been correctly initialised or is already closed in ...\vendor\silverstripe\sqlite3\code\SQLite3Query.php:43
Stack trace:
#0 ...\vendor\silverstripe\sqlite3\code\SQLite3Query.php(43): SQLite3Result->finalize()
#1 [internal function]: SilverStripe\SQLite\SQLite3Query->__destruct()
#2 {main}
thrown in...\vendor\silverstripe\sqlite3\code\SQLite3Query.php on line 43

This seem due to ->finalize being called but the db is already closed

How to reproduce

I didn't manage to get an easily reproducible example, but i can assure the issue is real :)

Possible Solution

No response

Additional Context

No response

Validations

  • Check that there isn't already an issue that reports the same bug
  • Double check that your reproduction steps work in a fresh installation of silverstripe/installer (with any code examples you've provided)
@lekoala
Copy link
Collaborator Author

lekoala commented Jun 26, 2024

i've managed to fix the issue by doing this #78
i don't see any downside in doing so

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant