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
There is a warning: Undefined array key "timestamp" during the execution of a Neo4j transaction using the Neo4jBundle for Symfony.
To Reproduce
Steps to reproduce the behavior:
Create a client using the Neo4j schema.
Open a transaction.
Commit the transaction.
See the error in the logs: "Warning: Undefined array key 'timestamp'".
Expected behavior
The transaction should complete successfully without any warnings or errors, especially regarding undefined array keys like "timestamp".
A Docker container running PHP version 8.2 with the following additional extensions: intl, opcache, pdo_mysql, zip, apcu, xdebug, amqp, sockets, pcntl.
I'll include the following diagnostics:
Neo4j version used in Docker: 5.24.1.
Framework: Symfony via neo4j/neo4j-bundle.
Please advise if further context or logging details are required for replication.
This issue template should be ready to report the bug to the relevant maintainers on GitHub.
The text was updated successfully, but these errors were encountered:
Describe the bug
There is a warning: Undefined array key "timestamp" during the execution of a Neo4j transaction using the Neo4jBundle for Symfony.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The transaction should complete successfully without any warnings or errors, especially regarding undefined array keys like "timestamp".
Error Message
Screenshots
If applicable, provide screenshots demonstrating the issue.
Desktop (please complete the following information):
dev-master
5.24.1
8.2.21
php:8.2-fpm-bullseye
.Additional context
The issue is observed while using the following software environment:
I'll include the following diagnostics:
5.24.1
.neo4j/neo4j-bundle
.Please advise if further context or logging details are required for replication.
This issue template should be ready to report the bug to the relevant maintainers on GitHub.
The text was updated successfully, but these errors were encountered: