RuntimeError: generator raised StopIteration -- Tutorial no longer works? #3
Comments
|
@lawsie I'm planning on running through the project to test this issue, but if you have an insight / resolution that you can see at a glance, it might save me some time. No worries if you don't have capacity at the moment. |
|
I don't know what version of Raspbian this was used on (likely Buster?) but this resource was written for Jessie (I think) and so it's very likely that what has happened is that asyncoro (which dispy relies upon) does not now work with current Raspbian. We had to put in the line to install dispy v 4.7.1 because of another problem at the time of writing where higher versions of dispy used a different middleware that wasn't compatible with Raspbian either. I don't know anything about the way dispy works with Raspbian, but my first port of call if I were you @MarcScott would be to find out whether dispy is even compatible with Raspbian any more and go from there? |
|
Sorry for the delay: I managed to get this working by simply changing all python3 references to python2. Which obviously is not ideal, but as a novice with both linux and python, this was a lucky shot in the dark that worked for me. I kept using dispy==4.7.1 and otherwise dropped the '3' from all python3 references, and everything works. On an unrelated note, the cluster_action.sh could really use: Additionally, for anyone who comes across this ahead of the install. I (mr. smarty-pants) thought it was smart to get a headless version of Raspbian with the intent to use the command line for everything. Works great, save for the Client/Master would have really benefit from a GUI to allow using dispy's built in web admin panel more easily. (I am sure there is a way, but knowing what I do now, a month later, I would have started with a full install for the Client/Master node. As they say: RTFM.) I'll work on figuring it out the cluster_action.sh items, but adding bash to the learning list wasn't immediately on the game plan. haha |
|
@jwest75674 I currently have a working version and will be updating the project instructions. |
|
Sounds great! I was actually in the process of switching my octa-pi to Python 3.7, so I am confident your updates will help me along the path too! I can contribute to the readme too at this point as I've learned lots. Will send a pull request with some useful info. |
|
I've actually noted a handful of bugs being run into with dispy 4.7.1 which is pushing me down the path for upgrading. Looking at the commits over the last few weeks, has the primary update to get dispy working on the latest version simply been the need to pass the client/head ip_addr when creating the job cluster, or have there been other changes/considerations that need to be taken into account? |
|
From my testing, it's just getting the client IP that has changed in the cluster, which can be achieved with the hacky 8.8.8.8 call. |
|
Fixed last year and forgot to close the issue |
Basically, I am just following the tutorial at:
https://projects.raspberrypi.org/en/projects/build-an-octapi/
No Unicorn hats :'(
At the "Check that it works" stage, which, apparently not....?
Running on a dedicated router, not connected to the net.
Been through the wpa_supplicant.conf to clean it up, and have the server running dispy as a daemon, etc.
(Followed the instruction very closely)
I suspect the issue is related to some change in either Python, or raspbian since the tutorial was written, but not really sure how to address...
Here's my full SSH dump:
(I am on windows 10, if that matters, using putty)
The text was updated successfully, but these errors were encountered: