Invalid watcher exception

[brstgt]

We updated the amphp/mysql from f077c40 to 419279e. Now we get the following exception from time to time.
I guess it could be related to connections closed by mysql server due to an idle timeout.

And it would be really cool if you tag your releases so one can use composer version deps.

Cannot reference an invalid watcher identifier: 'pk' (File: /home/ci-php2/builds/e0553b41/0/jaumo/jaumo/vendor/amphp/amp/lib/Loop/Driver.php:476) (Class: Amp\Loop\InvalidWatcherError)
[#1] Amp\Loop\Driver->reference in /home/ci-php2/builds/e0553b41/0/jaumo/jaumo/lib/Sensphere/Amp/Loop/DecoratableDriver.php on line 141
[#2] Sensphere\Amp\Loop\DecoratableDriver->reference in /home/ci-php2/builds/e0553b41/0/jaumo/jaumo/vendor/amphp/amp/lib/Loop.php on line 288
[#3] Amp\Loop::reference in /home/ci-php2/builds/e0553b41/0/jaumo/jaumo/vendor/amphp/byte-stream/lib/ResourceInputStream.php on line 204
[#4] Amp\ByteStream\ResourceInputStream->reference in /home/ci-php2/builds/e0553b41/0/jaumo/jaumo/vendor/amphp/socket/src/Socket.php on line 88
[#5] Amp\Socket\Socket->reference in /home/ci-php2/builds/e0553b41/0/jaumo/jaumo/vendor/amphp/mysql/src/Internal/Processor.php on line 184
[#6] Amp\Mysql\Internal\Processor->addDeferred in /home/ci-php2/builds/e0553b41/0/jaumo/jaumo/vendor/amphp/mysql/src/Internal/Processor.php on line 300
[#7] Amp\Mysql\Internal\Processor->Amp\Mysql\Internal\{closure} in /home/ci-php2/builds/e0553b41/0/jaumo/jaumo/vendor/amphp/mysql/src/Internal/Processor.php on line 276
[#8] Amp\Mysql\Internal\Processor->appendTask in /home/ci-php2/builds/e0553b41/0/jaumo/jaumo/vendor/amphp/mysql/src/Internal/Processor.php on line 302
[#9] Amp\Mysql\Internal\Processor->startCommand in /home/ci-php2/builds/e0553b41/0/jaumo/jaumo/vendor/amphp/mysql/src/Internal/Processor.php on line 337
[#10] Amp\Mysql\Internal\Processor->query in /home/ci-php2/builds/e0553b41/0/jaumo/jaumo/vendor/amphp/mysql/src/Connection.php on line 98
[#11] Amp\Mysql\Connection->Amp\Mysql\{closure} in  on line 
[#12] Generator->current in /home/ci-php2/builds/e0553b41/0/jaumo/jaumo/vendor/amphp/amp/lib/Coroutine.php on line 39
[#13] Amp\Coroutine->__construct in /home/ci-php2/builds/e0553b41/0/jaumo/jaumo/vendor/amphp/amp/lib/functions.php on line 61
[#14] Amp\call in /home/ci-php2/builds/e0553b41/0/jaumo/jaumo/vendor/amphp/mysql/src/Connection.php on line 109
[#15] Amp\Mysql\Connection->query in /home/ci-php2/builds/e0553b41/0/jaumo/jaumo/vendor/amphp/mysql/src/Pool.php on line 268
[#16] Amp\Mysql\Pool->Amp\Mysql\{closure} in  on line 
[#17] Generator->current in /home/ci-php2/builds/e0553b41/0/jaumo/jaumo/vendor/amphp/amp/lib/Coroutine.php on line 39
[#18] Amp\Coroutine->__construct in /home/ci-php2/builds/e0553b41/0/jaumo/jaumo/vendor/amphp/amp/lib/functions.php on line 61
[#19] Amp\call in /home/ci-php2/builds/e0553b41/0/jaumo/jaumo/vendor/amphp/mysql/src/Pool.php on line 283
[#20] Amp\Mysql\Pool->query in /home/ci-php2/builds/e0553b41/0/jaumo/jaumo/lib/Sensphere/DB/MySql/AsyncPool.php on line 58
[#21] Sensphere\DB\MySql\AsyncPool->Sensphere\DB\MySql\{closure} in  on line 
[#22] Generator->throw in /home/ci-php2/builds/e0553b41/0/jaumo/jaumo/vendor/amphp/amp/lib/Coroutine.php on line 71
[#23] Amp\Coroutine->Amp\{closure} in /home/ci-php2/builds/e0553b41/0/jaumo/jaumo/vendor/amphp/amp/lib/Failure.php on line 26
[#24] Amp\Failure->onResolve in /home/ci-php2/builds/e0553b41/0/jaumo/jaumo/vendor/amphp/amp/lib/Internal/Placeholder.php on line 122
[#25] Amp\Coroutine->resolve in /home/ci-php2/builds/e0553b41/0/jaumo/jaumo/vendor/amphp/amp/lib/Internal/Placeholder.php on line 151
[#26] Amp\Coroutine->fail in /home/ci-php2/builds/e0553b41/0/jaumo/jaumo/vendor/amphp/amp/lib/Coroutine.php on line 93
[#27] Amp\Coroutine->Amp\{closure} in /home/ci-php2/builds/e0553b41/0/jaumo/jaumo/vendor/amphp/amp/lib/Failure.php on line 26
[#28] Amp\Failure->onResolve in /home/ci-php2/builds/e0553b41/0/jaumo/jaumo/vendor/amphp/amp/lib/Internal/Placeholder.php on line 122
[#29] Amp\Coroutine->resolve in /home/ci-php2/builds/e0553b41/0/jaumo/jaumo/vendor/amphp/amp/lib/Internal/Placeholder.php on line 151
[#30] Amp\Coroutine->fail in /home/ci-php2/builds/e0553b41/0/jaumo/jaumo/vendor/amphp/amp/lib/Coroutine.php on line 93
[#31] Amp\Coroutine->Amp\{closure} in /home/ci-php2/builds/e0553b41/0/jaumo/jaumo/vendor/amphp/amp/lib/Failure.php on line 26
[#32] Amp\Failure->onResolve in /home/ci-php2/builds/e0553b41/0/jaumo/jaumo/vendor/amphp/amp/lib/Internal/Placeholder.php on line 122
[#33] class@anonymous/home/ci-php

[brstgt]

The issue was not caused by mysql itself. However, proper release tags would be helpful.

[kelunik]

@brstgt Are you waiting on a bugfix release or the new major release? (currently on mobile, so can't look up the linked commits)

[brstgt]

The last tag is quite a while ago. Would be great to know what's considered stable Niklas Keller <notifications@github.com> schrieb am Di., 31. Juli 2018, 20:39:

…

@brstgt <https://github.com/brstgt> Are you waiting on a bugfix release or the new major release? (currently on mobile, so can't look up the linked commits) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#76 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAUQZ6ePRznetDFZ4ffJfQiAki9kJPYDks5uMKRmgaJpZM4VoGvK> .

[kelunik]

Stable is considered what's tagged. The new interfaces need some time and coordination to properly work for MySQL and Postgres.