Server Mode about massmine HOT 12 OPEN

I can confirm your error and should be able to take a look at the problem soon.

from massmine.

from massmine.

I believe everything should be working now. I've pushed a new version to reflect these (and other) changes. I'm building a new binary release now and will confirm once it's ready for download. Thanks for your patience!

from massmine.

The updated version (1.3.0) is now available for download. This should hopefully fix all of your issues.

One important point, however: When passing JSON strings to MassMine server, stick with double quotes for strings. So your example above {"task":"twitter-stream", "geo":'-74,40,-73,41',"count":10} should be {"task":"twitter-stream", "geo":"-74,40,-73,41","count":10}

Thanks for reaching out regarding this bug!

from massmine.

Hi, I tried with the updated version(1.3.0) of massmine.

I am trying the following commands
massmine --server=4242
netcat localhost 4242
{"task":"twitter-stream", "geo":"-74,40,-73,41","count":10}

Still I am getting "bad argument type error"

from massmine.

Copying and pasting your example causes no error for me. Can you confirm that you're not accidentally running a previously installed version (massmine allows for multiple versions to be installed side-by-side... perhaps the old version is on your path and is getting called?).

from massmine.

Just to verify I installed the latest version(1.3.0) of massmine in different path. In spite of that I am seeing the same error as "Bad Argument Type".

from massmine.

This is strange indeed. Can you report the output of:

massmine -v
uname -srv

from massmine.

massmine 1.3.0
Linux 5.8.0-generic

from massmine.

I believe I found the problem. Try grabbing the installation files from massmine.org again. However, two things:

1. While the downloadable zip file has been updated, the MD5 checksum on the massmine.org website has not been updated yet. I'll do that soon. The MD5 checksum should be: d3f5a5050eeb72b1162cdd1a96c8ac84
2. There appears to be a new problem with both streaming API endpoints. In other words, not only is twitter-stream and twitter-sample not working in server mode, they're not working period (at least for me currently). From what I can tell, Twitter is slowly moving everything over to their V2 setup. However, they claim that the legacy API is still available, so I'm not sure why this isn't working for me. If it works for you, please let me know. Otherwise, I'll update this conversation when I have a sense of what's going on.

from massmine.

The streaming endpoints (twitter-stream and twitter-sample) appear to be working for me now. Perhaps there was an authentication issue temporarily on Twitter's end. In any case, can you confirm if your twitter-stream example is working for you now?

from massmine.

I downloaded latest version again and checked. Still the twitter-stream is not working for me.

from massmine.