TogetherCrew milestone2 #1047
TogetherCrew milestone2 #1047
Conversation
|
@keeganquigley the check failed because of an error updating the google sheet (Error: Range (Evaluation!A1034) exceeds grid limits. Max rows: 1033, max columns: 40) is there something I can do on my end to fix this? |
|
Thanks @katerinabc it looks like they are all passing now. We have a bit of a backlog at the moment but someone will be able to take a look in the next few days. |
There was a problem hiding this comment.
Hi @katerinabc. Thanks for the delivery. I tried running the bot using Docker, but it failed with the following message. Can you tell me what's missing?
> docker-compose -f docker-compose.example.yml up
Building with native build. Learn about native build in Compose here: https://docs.docker.com/go/compose-native-build/
Creating network "twitter-bot_default" with the default driver
Building server
[+] Building 80.0s (10/10) FINISHED docker:default
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 372B 0.0s
=> [internal] load .dockerignore 0.0s
=> => transferring context: 92B 0.0s
=> [internal] load metadata for docker.io/library/python:3.10-bullseye 1.6s
=> [auth] library/python:pull token for registry-1.docker.io 0.0s
=> [base 1/4] FROM docker.io/library/python:3.10-bullseye@sha256:4baee739b4a2bda53e0c477b7a71b96535462fc95b924da03c1cbd375fba5c91 37.7s
=> => resolve docker.io/library/python:3.10-bullseye@sha256:4baee739b4a2bda53e0c477b7a71b96535462fc95b924da03c1cbd375fba5c91 0.0s
=> => sha256:4baee739b4a2bda53e0c477b7a71b96535462fc95b924da03c1cbd375fba5c91 1.65kB / 1.65kB 0.0s
=> => sha256:1a28f256af277c7df95552190030c90c68633996917ad116c63e3f0981d95c33 7.52kB / 7.52kB 0.0s
=> => sha256:de448b80f06437f3025dcaa9285d40c9c81e4be00df1b04bd5a26fd6b9447fc8 15.76MB / 15.76MB 4.0s
=> => sha256:a627e8796be016fef6ff8e3f2627b6f4bd51cecc2d4a3790f03b6cb44a143556 2.01kB / 2.01kB 0.0s
=> => sha256:2f088d622efd8dbaa13d01eafd0aac8f9f33bb335edd3be897ae8059338c7bf7 55.06MB / 55.06MB 13.8s
=> => sha256:24e5da9a0e1f93fa4f1a07ca9a691e0d941bab6927f80157ffc14b478815f95b 54.60MB / 54.60MB 14.3s
=> => sha256:6d61681290435197504d4cdaa3724700bd66544d064d068e837f70e5abede255 196.88MB / 196.88MB 31.6s
=> => extracting sha256:2f088d622efd8dbaa13d01eafd0aac8f9f33bb335edd3be897ae8059338c7bf7 1.8s
=> => sha256:7a2e41faea6921507ceb141678128fe6b0446edb77d7834510917c061affcbfe 6.29MB / 6.29MB 15.6s
=> => sha256:26ebd1023baa57a926a4c43cb015c40be73634472a8b521c1e905872c6c3be09 17.34MB / 17.34MB 19.0s
=> => sha256:c432c5a4fe2f5053c5508eb8b8bbe706697bfd61cf761972dfd1db814aaefb77 244B / 244B 15.7s
=> => extracting sha256:de448b80f06437f3025dcaa9285d40c9c81e4be00df1b04bd5a26fd6b9447fc8 0.4s
=> => sha256:7a99ddf8c557230ac7173f7b23c4d12d8baf0c1afe322a6a86d695a5b5e2956f 3.08MB / 3.08MB 16.8s
=> => extracting sha256:24e5da9a0e1f93fa4f1a07ca9a691e0d941bab6927f80157ffc14b478815f95b 1.9s
=> => extracting sha256:6d61681290435197504d4cdaa3724700bd66544d064d068e837f70e5abede255 4.4s
=> => extracting sha256:7a2e41faea6921507ceb141678128fe6b0446edb77d7834510917c061affcbfe 0.2s
=> => extracting sha256:26ebd1023baa57a926a4c43cb015c40be73634472a8b521c1e905872c6c3be09 0.4s
=> => extracting sha256:c432c5a4fe2f5053c5508eb8b8bbe706697bfd61cf761972dfd1db814aaefb77 0.0s
=> => extracting sha256:7a99ddf8c557230ac7173f7b23c4d12d8baf0c1afe322a6a86d695a5b5e2956f 0.4s
=> [internal] load build context 0.0s
=> => transferring context: 764.00kB 0.0s
=> [base 2/4] WORKDIR /project 0.4s
=> [base 3/4] COPY . . 0.1s
=> [base 4/4] RUN pip3 install -r requirements.txt 37.4s
=> exporting to image 2.7s
=> => exporting layers 2.7s
=> => writing image sha256:40891b895a3217a55b895cf6209c444974a2e101a25cdb2802e173e952410b22 0.0s
=> => naming to docker.io/library/twitter-bot_server 0.0s
Successfully built 40891b895a3217a55b895cf6209c444974a2e101a25cdb2802e173e952410b22
WARNING: Image for service server was built because it did not already exist. To rebuild this image you must use `docker-compose build` or `docker-compose up --build`.
Building worker
[+] Building 0.5s (9/9) FINISHED docker:default
=> [internal] load .dockerignore 0.0s
=> => transferring context: 92B 0.0s
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 372B 0.0s
=> [internal] load metadata for docker.io/library/python:3.10-bullseye 0.5s
=> [base 1/4] FROM docker.io/library/python:3.10-bullseye@sha256:4baee739b4a2bda53e0c477b7a71b96535462fc95b924da03c1cbd375fba5c91 0.0s
=> [internal] load build context 0.0s
=> => transferring context: 14.49kB 0.0s
=> CACHED [base 2/4] WORKDIR /project 0.0s
=> CACHED [base 3/4] COPY . . 0.0s
=> CACHED [base 4/4] RUN pip3 install -r requirements.txt 0.0s
=> exporting to image 0.0s
=> => exporting layers 0.0s
=> => writing image sha256:40891b895a3217a55b895cf6209c444974a2e101a25cdb2802e173e952410b22 0.0s
=> => naming to docker.io/library/twitter-bot_worker 0.0s
Successfully built 40891b895a3217a55b895cf6209c444974a2e101a25cdb2802e173e952410b22
WARNING: Image for service worker was built because it did not already exist. To rebuild this image you must use `docker-compose build` or `docker-compose up --build`.
Creating twitter-bot_worker_1 ... done
Creating twitter-bot_server_1 ... done
Attaching to twitter-bot_worker_1, twitter-bot_server_1
worker_1 | Traceback (most recent call last):
worker_1 | File "/usr/local/lib/python3.10/site-packages/redis/connection.py", line 707, in connect
worker_1 | sock = self.retry.call_with_retry(
worker_1 | File "/usr/local/lib/python3.10/site-packages/redis/retry.py", line 46, in call_with_retry
worker_1 | return do()
worker_1 | File "/usr/local/lib/python3.10/site-packages/redis/connection.py", line 708, in <lambda>
worker_1 | lambda: self._connect(), lambda error: self.disconnect(error)
worker_1 | File "/usr/local/lib/python3.10/site-packages/redis/connection.py", line 974, in _connect
worker_1 | for res in socket.getaddrinfo(
worker_1 | File "/usr/local/lib/python3.10/socket.py", line 955, in getaddrinfo
worker_1 | for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
worker_1 | socket.gaierror: [Errno -2] Name or service not known
worker_1 |
worker_1 | During handling of the above exception, another exception occurred:
worker_1 |
worker_1 | Traceback (most recent call last):
worker_1 | File "/project/worker.py", line 28, in <module>
worker_1 | worker = Worker(
worker_1 | File "/usr/local/lib/python3.10/site-packages/rq/worker.py", line 204, in __init__
worker_1 | connection.client_setname(self.name)
worker_1 | File "/usr/local/lib/python3.10/site-packages/redis/commands/core.py", line 707, in client_setname
worker_1 | return self.execute_command("CLIENT SETNAME", name, **kwargs)
worker_1 | File "/usr/local/lib/python3.10/site-packages/redis/client.py", line 1266, in execute_command
worker_1 | conn = self.connection or pool.get_connection(command_name, **options)
worker_1 | File "/usr/local/lib/python3.10/site-packages/redis/connection.py", line 1461, in get_connection
worker_1 | connection.connect()
worker_1 | File "/usr/local/lib/python3.10/site-packages/redis/connection.py", line 713, in connect
worker_1 | raise ConnectionError(self._error_message(e))
worker_1 | redis.exceptions.ConnectionError: Error -2 connecting to :6379. Name or service not known.
twitter-bot_worker_1 exited with code 1
server_1 | ERROR:root: Something went wrong with RabbitMQ host must be a str or unicode str, but got None
server_1 | INFO:root:Error: was not connected to RabbitMQ broker!
twitter-bot_server_1 exited with code 0Regarding the frontend: you linked to a merged PR, but write that you didn't commit the changes. I understand that you didn't want to pay for the API, but is there a way I can use or at least test what was built?
|
pinging @katerinabc |
About the front-end: There isn't much that you can test, as without data it's just like a static website. This link shows you the figma dashboard we created to represent the data: https://www.figma.com/file/cxii1lDO2rv6nARDJML995/Twitter-Dashboard(web3-foundation?type=design&node-id=0%3A1&mode=design&t=wm9x3KtXkdjW5cwJ-1 |
|
@semuelle The docker file has been updated. Same link than before (https://github.com/TogetherCrew/twitter-bot/tree/main) |
Thanks, the bot is working now.
I understand, but there might be people willing to pay for the data, and a frontend was part of the grant agreement. So, unless you want to remove the frontend from this milestone as a deliverable, I would like to see that it would - at least theoretically - work. It also probably wouldn't be too hard to get your hands on some mock data to use and test the frontend with. |
Regarding the front-end, could you let me know what exactly you want to theoretically test if it works? I agree that there might be some people willing to pay for the data. However, to run the social network analysis we had designed, we would need to pay for the Enterprise plan which is $5000/month. As mentioned before, Twitter changed a lot which endpoint are included for which trier level. |
I would like to see that it is able to process Twitter data into community health metrics, as was proposed in the application:
I don't expect you to pay for the API, especially at 5000 USD per month, but it should still be possible to provide the code and a tutorial with some mock data (Kaggle lists numerous Twitter datasets) so that others are able to pick it up. If you are unable or unwilling to provide that, please adjust the grant application accordingly. |
We will have to adjust the code for the analysis. The metrics are based on the last 7 days of posts. Hence any post that is older than that would be excluded. Thus, you would only see 0s in the dashboard. I'll check with the team what we can do. |
Also making sure that the correct design for the Twitter dashboard is the one below 
|
|
@semuelle You wanted to test
This can be done using the CLI, described in the readme file. https://github.com/TogetherCrew/twitter-bot/blob/main/README.md#running-the-cli |
|
As I suggested earlier, if you want to exclude this deliverable, please amend the grant agreement and adjust the price correspondingly. I'm sure the committee will be understanding. |
What we can do is turn the front-end into a small react-app that can be run locally. Would that be sufficient for you to test the front-end (Twitter dashboard)? |
Does it include mock data or would I be able to add data to it somehow? Then yes, that would work. |
|
@semuelle We're planning to split milestone 2 into 2a (everything else) and 2b (Twitter dashboard + optional workshop). I checked the FAQ for milestone amendments and it stated to get in touch with the foundation. Do you have more information on the process?
|
|
Hi @katerinabc. You can modify the merged application document and submit a pull request. Approving an amendment is basically the same process as the original application, except it's not a new document but changes to the existing one. That means it also needs the same amount of approvals from the committee. |
|
amendment to project: Split milestone 2 into 2 parts: Project changes: w3f/Grants-Program#2195 |
|
The requested changes to milestone 2 passed. I'm gonna close this pull request and open a new one for the new milestone 2. |
|
For reference: conversation has moved here #1124 |
Milestone Delivery Checklist
Link to the application pull request: w3f/Grants-Program#1482 < please fill this in with the PR number of your application.