Skip to content
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.

Sign up for GitHub

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

Jump to bottom

NaN in a sent message becomes null when received #199

Open
erezh16 opened this issue Feb 24, 2019 · 0 comments
Open

NaN in a sent message becomes null when received #199

erezh16 opened this issue Feb 24, 2019 · 0 comments

Comments

@erezh16
Copy link

erezh16 commented Feb 24, 2019

Hi folks,

It seems that when a worker sends to a master a message containing fields with NaN values, the master receives those fields with null values. Is anyone aware of this issue? Can this be fixed without writing a bypass (e.g., to avoid NaN)?

Regards,
-- Erez Hadad
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@erezh16