Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

[BUG] Enqueue message from NodeJS #278

Closed
acgfbr opened this issue Jun 8, 2021 · 2 comments
Closed

[BUG] Enqueue message from NodeJS #278

acgfbr opened this issue Jun 8, 2021 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@acgfbr
Copy link

acgfbr commented Jun 8, 2021

Describe the bug
My system enqueue all of messages in nodejs, just route to micro service enqueuer, example:
i have multi queue system in sqs, php and im trying to rollout all of this systems to go, but i want to enqueue in node to sqs and golang

I'm queuing a payload from nodejs and asynq can't remove the message

To Reproduce
Steps to reproduce the behavior (Code snippets if applicable):

NodeJS code
image

Payload in redis by NodeJS
Payload in redis by Golang asynq enqueue

image

The golang message enqueued by go proccess normally, nodejs message not removed from queue
image

Message stuck:
image

The payload as 100% matching, what can i be doing wrong?
Can u help me ?

My go code from server:
image

Job:
image

@acgfbr acgfbr added the bug Something isn't working label Jun 8, 2021
@crossworth
Copy link
Contributor

Hi, maybe this is related to this: #109 (comment)

Which should be fixed when the API uses a byte slice as payload (#253).

@acgfbr
Copy link
Author

acgfbr commented Jun 8, 2021

Oh great, i change the order of json and now working, thanks man!
image

@acgfbr acgfbr closed this as completed Jun 8, 2021
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants