-
Notifications
You must be signed in to change notification settings - Fork 439
[FS] Frame not being read correctly #170
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
Comments
Just a random number, The message extraction logic is much much simpler if the message length is predictable |
I've never run into this but it could still be a bug. |
Can confirm that if I change my message by a few characters it works as expected, so guess I was just unlucky, but yeah sounds like a bug. |
Could you post a message that causes it? |
This is the one I was running into issues with, changed ids to x's but kept the length the same. If you change {
"body": "{\"consumerId\":\"user:xxxxxx\",\"producerId\":\"user:xxxxxx\",\"type\":\"unsubscribe\"}",
"properties": {
"enqueue.topic_name": "__command__",
"enqueue.command_name": "updateConsumerNetwork",
"enqueue.processor_name": "enqueue.client.router_processor",
"enqueue.processor_queue_name": "default"
},
"headers": {
"content_type": "text\/plain",
"message_id": "9cb6dcb9-8b6c-402a-ae61-3cd6b321c150",
"timestamp": 1502689812,
"reply_to": null,
"correlation_id": ""
}
} |
What about a new file for each message? I think that's what bernard does but haven't had time to look into properly https://github.com/bernardphp/bernard/blob/master/src/Driver/FlatFileDriver.php |
It failed on message size equal to 24. the queue must not be empty
|
Not sure if this is a bug or if I've done something not quite right, but I get the following error when certain messages are attempted to be consumed:
Digging into it, the frames seem to be getting split between a
|
and a{
meaning the following isn't getting hit and thus the message isn't read from the file correctly.https://github.com/php-enqueue/enqueue-dev/blob/master/pkg/fs/FsConsumer.php#L172
Is there a reason 64 was chosen? Was it just a random number and I've been desperately unlucky?
The text was updated successfully, but these errors were encountered: