Questions

[ ] Which operating system are you using (if Linux, please provide flavour of it, i.e RedHat, CentOS or Ubuntu), is it 32-bit, or 64-bit?
```
Void Linux
```
[ ] Which version of PyQ are you running? Please provide output of pyq --versions, if PyQ isn't operational, please provide Python interpreter version and PyQ version python -V; python3 -V; pip list | grep pyq:
```
PyQ 5.0.0
KDB+ 4f (2022.10.26) l64
Python 3.9.16 (main, Jan  5 2023, 06:43:45) 
[GCC 12.2.0]
```
[ ] Which version of kdb+ are you using, is it 32-bit or 64-bit?
```
32 bit
```
- [ ] If on 64-bit, is your QLIC set? Please provide output env | grep QLIC on linux/macOS, or set|grep QLIC on Windows.
[ ] Did you use virtual environment to install PyQ? If not, why?
- I've used pyenv virtual env
[ ] Where is your QHOME? Please provide output env | grep QHOME on linux/macOS, or set|grep QHOME on Windows.
```
/opt/q/
```
[ ] Do you use Conda? If so, what version?
```
I don't use Conda
```

Steps to reproduce the issue

Send asynchronous request using pyq. Q process accepting requests:

.z.ps:{show "Async"} Python code:

from pyq import q
h = q.hopen('::5001')
h.neg('a')

Q process receives request and print "Async"

For some reason all async requests are placed in some sort of queue and until you make sync reuest, they are not sent.

h.neg('a') # nothing happens
h('b') # you get error since no sync message handler is defined, but the message above gets sent

You could send sync message every time you've prepared async message, but at this point you could just switch to sync messages