Horus | The keeper of the keys | Cryptocurrency library

I think you can use colspan

I used selenium for python and had a similar problem when using driver = Webdriver.Firefox() The problem was that the program couldnt find the path of the searching machine of the browser and it did not work. I solved it by either add the path in the bracket of Webdriver.Firefox("path here") or copy the engine, incase of firefox it was geckodriver, inside the folder where the script is. Another possibility is, that the site or the browser is just slow, and therefore you get that error. Also make sure that the link is 100% correct If nothing helps, maybe think about choosing another browser, which is a bit more common like firefox or chrome

Not sure if this helps, but those are my experiences and i hope it somehow helps

• It is not required to use await to UrlFetchApp and the response.
• I think that in your script, each object and value from the top of response values are retrieved by temp.push(responseJson[rows[0][i]]);. responseJson.connections, responseJson.elements and responseJson.name are retrieved. By this, when =fetchdata("https://sum-app.net/projects/14312620200623668/download_data/kumu_json") is put to a cell, only test222 is shown. I think that this is the reason of your issue. For example, when temp.push(responseJson[rows[0][i]]); is modified to temp.push(JSON.stringify(responseJson[rows[0][i]]));, all values can be seen. But I think that this it not the result you expect.
• In your goal, when you want to use the custom function, it is required to separate the script for "elements" sheet and "Connections" sheet.

When above points are reflected to your script, it becomes as follows.

Please copy and paste the folloiwng scripts. When you use this, please put =GETCONNECTIONS("https://sum-app.net/projects/14312620200623668/download_data/kumu_json") and =GETELEMENTS("https://sum-app.net/projects/14312620200623668/download_data/kumu_json") to the sheet of "connections" and "elements", respectively.

As far as I see, the battle should continue

The problem is that your server is binding to "127.0.0.1:30043". You say that you are running the docker images using the default bridge network. In that mode the docker image has a different (virtual) network than the host machine has, so its loopback address is different from the host machine's loopback address. To fix that, you can instead bind the server to 0.0.0.0:30043 or [::]:30043to bind to other network interfaces that the client can connect to from outside of the docker container.

For the same reason, connecting the client to localhost:30043 will not work: its "localhost" address also refers to the loopback interface within the docker container. You should instead replace "localhost" with the IP address of the server container.

Alternatively, as described in this question, you can network the docker containers in "host" mode so that they share the same network with the host machine.