*this issue is not new and did happen on older versions
using 0.7.22 removes the issue
log
#2 /usr/local/app/http.php(78): Utopia\Http\Http->start()
#3 [internal function]: {closure:/usr/local/app/http.php:72}()
#4 {main}
thrown in /usr/local/vendor/utopia-php/http/src/Http/Http.php on line 500
Fatal error: Uncaught Utopia\DI\Exceptions\NotFoundException: Dependency response not found in /usr/local/vendor/utopia-php/di/src/DI/Container.php:75
Stack trace:
#0 /usr/local/vendor/utopia-php/http/src/Http/Http.php(734): Utopia\DI\Container->get('response')
#1 /usr/local/vendor/utopia-php/http/src/Http/Http.php(497): Utopia\Http\Http->getArguments(Object(Utopia\Servers\Hook), Array, Array)
#2 /usr/local/vendor/utopia-php/http/src/Http/Adapter/SwooleCoroutine/Server.php(74): Utopia\Http\Http->{closure:Utopia\Http\Http::start():483}(Object(Utopia\Http\Adapter\SwooleCoroutine\Server))
#3 /usr/local/vendor/utopia-php/http/src/Http/Http.php(507): Utopia\Http\Adapter\SwooleCoroutine\Server->start()
#4 /usr/local/app/http.php(78): Utopia\Http\Http->start()
#5 [internal function]: {closure:/usr/local/app/http.php:72}()
#6 {main}
Next Utopia\Http\Exception: Error handler had an error: Dependency response not found in /usr/local/vendor/utopia-php/http/src/Http/Http.php:500
Stack trace:
#0 /usr/local/vendor/utopia-php/http/src/Http/Adapter/SwooleCoroutine/Server.php(74): Utopia\Http\Http->{closure:Utopia\Http\Http::start():483}(Object(Utopia\Http\Adapter\SwooleCoroutine\Server))
#1 /usr/local/vendor/utopia-php/http/src/Http/Http.php(507): Utopia\Http\Adapter\SwooleCoroutine\Server->start()
#2 /usr/local/app/http.php(78): Utopia\Http\Http->start()
#3 [internal function]: {closure:/usr/local/app/http.php:72}()
same issue i faced as well, reverted ro 0.7.22
Could you guys share more information ?
- When does it happen ?
- Did you change some things in the configurations ?
- If possible share your compose for the executor
between 0.7.22 and 0.25.1 there was some changes, even in the envs, so maybe that could be the cause
changed nothing, even in composer run dev it happens
that's strange, i'm running 0.25.1 fine, the only issue i had was related to S3 storage, but i fixed it
and if you kept the old env that might be why
that's why i asked thoses questions, so it's easier for us to see where is the root cause of the issue.
because a simple error trace without knowing what you did or your configuration is mostly useless
Recommended threads
- MariaDB refuses to connect to appwrite
Earlier, I tried updating my Appwrite version from 18.1.x to the latest release because my Flutter package required it to function properly. I used the official...
- executeFunction intermittently throws Fo...
Environment: Flutter app using the Appwrite Flutter SDK, calling executeFunction for [describe endpoint, e.g. live-stream-related function]. *Description*: Int...
- Console display all Databases as TablesD...
While looking at an issue with <@1231860789355347971> we saw that the console was displaying ALL databases as `TablesDB` even if the real type in the API is `le...