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
msgpack Exception: OverflowError: long too big to convert #12185
Comments
Sorry, it hasn't occured on a |
This is quite interesting. The stacktrace is clearly coming from inside msgpack and so this may end up becoming an upstream bug with the msgpack folks but we'll investigate. |
We're converting the jid to int right from the CLI when parsing args. As a workaround we could try not to pass jid as an int for this specific platform? Pedro Algarvio @ Phone ----- Reply message ----- — |
@s0undt3ch That might work, though we'll have to catch it on the other side and make sure we have it cast it back correctly or we'll run into more problems potentially. |
Do you want me to test something to help with this issue? |
@bbinet We're not yet in agreement on the right approach here, I think. Once we figure out the best way to solve this we'll definitely appreciate your help in testing this thoroughly. Thanks! |
I have the same issue with the same version. Although I am running Ubuntu 12.04. Why not keep the jids as strings for all platforms as a solution? |
@aryanet on which platform are you on? ARM? |
TL;DR: x86_64 |
This is due to a change we made with argument parsing. I think @terminalmage already fixed it, if I remember correctly. He took long types out of the list of things we wanted to convert to. |
(I may be wrong, because I think his fix was in 2014.1.3, which is what you're running.) |
Can confirm this bug in 2014.1.3 on x86_64 when doing a |
Is there a quick fix for this I can apply to my own branch while the debate continues on what the proper fix is? :) |
Yes, the temporary fix is to double quote your jid:
This will ensure that it is consumed as a string. |
@terminalmage's fix definitely made it in, so there must be an additional problem here. The double quoting should work for now, but we'll investigate an actual fix. |
@basepi doh! Yup that did the trick. FYI it does seem to be via the command line only as it works via the API. |
This has been found and fixed in #12460, and the fix will be in 2014.1.4. Here's an example of the now-fixed behavior:
And in the terminal that originally ran the command:
|
Awesome! |
I have the same bug still in 2014.7.0 (but want to mention i could workaround this by wrapping it in quotes as mentioned above ...):
|
Is your minion also on 2014.7.0, @7oku? |
This is also a problem with custom grains. If a grain returned is long int, it breaks salt. ''' |
Running salt-minion on Debian on a cubieboard v2 board, when running
saltutil.kill_job
function I get the following exception (this has also appeared once on astate.highstate
run):I suppose this is because salt-minion is running on an armhf Debian system?
Is salt/msgpack supposed to work on armhf architectures?
Please tell me how can I help provide more information to investigate this issue.
For information, here are the versions reports for salt-minion:
And salt-master:
The text was updated successfully, but these errors were encountered: