Skip to content
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

Delivery: Project Aurras MVP - Phase 2 - Milestone 3 #1048

Merged
merged 5 commits into from
Nov 28, 2023

Conversation

MuhammedIrfan
Copy link
Contributor

Milestone Delivery Checklist

  • The milestone-delivery-template.md has been copied and updated.
  • This pull request is being made by the same account as the accepted application.
  • I have disclosed any and all sources of reused code in the submitted repositories and have done my due diligence to meet its license requirements.
  • In case of acceptance, an invoice must be submitted and the payment will be transferred to the BTC/ETH/fiat account provided in the application.
  • The delivery is according to the Guidelines for Milestone Deliverables.

Link to the application pull request: w3f/Grants-Program#814

@keeganquigley
Copy link
Contributor

Thanks for the delivery @MuhammedIrfan we have a bit of a backlog at the moment but an evaluator will be able to take a look in the next few days.

@MuhammedIrfan
Copy link
Contributor Author

Thanks for the delivery @MuhammedIrfan we have a bit of a backlog at the moment but an evaluator will be able to take a look in the next few days.

Sure @keeganquigley, No problem 😊

@MuhammedIrfan MuhammedIrfan marked this pull request as ready for review November 13, 2023 02:30
@keeganquigley keeganquigley self-assigned this Nov 17, 2023
@MuhammedIrfan
Copy link
Contributor Author

@keeganquigley, Hope you are doing well, I see that you have assigned the PR to you. I just wanted to check if you are facing any trouble with the milestone delivery. We are here to assist you in making the evaluation as smooth as possible.

@keeganquigley
Copy link
Contributor

Sorry for the delay @MuhammedIrfan I'm taking a look at this today!

@keeganquigley
Copy link
Contributor

Hi @MuhammedIrfan sorry again for the delay. I have a couple of questions:

  • The video doesn't seem to be matching up with the instructions for this milestone. Which branch should I be on? Right now I'm using the next branch. For example in the video I'm not seeing anything about updating the FIREBASE_API_KEY.
  • Some of these tests are from two years ago. Should I only be completing the tests for payout notification example?
  • Where should I be updating the FIREBASE_API_KEY? I'm not seeing any example .env files. Should I just be updating it in deploy.sh? Or in the PayoutNotification.yaml file? I don't see anywhere for it in there. Same goes for DEVICE_TEST_TOKEN.
  • When you say to "generate a server token", I'm guessing that means a web push certificate keypair?
keypair

This is my first time evaluating the project and I know there has been a lot of progress but I'm just catching up. Thanks for any assistance you can provide!

@Mr-Nobody21
Copy link

@keeganquigley Thank you for reviewing.

  • The video doesn't seem to be matching up with the instructions for this milestone. Which branch should I be on? Right now I'm using the next branch. For example in the video I'm not seeing anything about updating the FIREBASE_API_KEY.

The video is specific for polkadot payout, Firebase setup can be found in the video

  • Some of these tests are from two years ago. Should I only be completing the tests for payout notification example?

The tests in integration-testing-for-payout-notify are to tested Testing guide

  • Where should I be updating the FIREBASE_API_KEY? I'm not seeing any example .env files. Should I just be updating it in deploy.sh? Or in the PayoutNotification.yaml file? I don't see anywhere for it in there. Same goes for DEVICE_TEST_TOKEN.

For Firebase API key:- Firebase config location

  • When you say to "generate a server token", I'm guessing that means a web push certificate keypair?

Instead of Web Configurations in FCM we have to generate Cloud Messaging API (Legacy)
image

@keeganquigley
Copy link
Contributor

keeganquigley commented Nov 22, 2023

Thanks for the help @Mr-Nobody21 this video differs from the one in the deliverables, hence the reason for my confusion. Also, the video is 17 minutes long.

  • Could you point to where (in the video) the instructions are for setting the Firebase key? I'm not sure which steps in this video apply to this milestone. Understood that I need to use the legacy Cloud Messaging API.
  • I'm not sure you answered my question about the branch. Should I be using next branch (set as the default) or the master branch? Or feature/UI-for-polkadot-payout?
  • Am I supposed to have a local Aurras node running while completing these tasks?
  • Do I need to be running the deployment instructions for Kubernetes and Docker Compose, or were those from a previous milestone?

@keeganquigley
Copy link
Contributor

UPDATE: I was able to set the API server key and successfully run ./deploy.sh but it failed, I think because of my Apple ARM64 chip. I will have to try again on Ubuntu.

73d61506f446: Download complete
15518faa499b: Pull complete
73d61506f446: Pull complete
4f4fb700ef54: Pull complete
Digest: sha256:e706aab3cc002471008f31b0fe80b7003d8cdd2f66bd32dd6f122cd6adbb7816
Status: Downloaded newer image for hugobyte/openwhisk-runtime-rust:v0.3
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
2023/11/23 00:00:36 warning: profiles for the non root package will be ignored, specify profiles at the workspace root:
package:   /usr/src/action_loop/Cargo.toml
workspace: /usr/src/Cargo.toml
    Updating crates.io index
    Updating git repository `https://github.com/hugobyte/aurras`
warning: spurious network error (3 tries remaining): failed to create locked file '/usr/local/cargo/git/db/aurras-7a79c31b974d5a1e/objects/pack/pack_git2_43080ff061ceidx.lock': Read-only file system; class=Os (2)
warning: spurious network error (2 tries remaining): failed to create temporary file '/usr/local/cargo/git/db/aurras-7a79c31b974d5a1e/objects/pack/pack_git2_a9b249b199e400f7': Read-only file system; class=Os (2)
warning: spurious network error (1 tries remaining): failed to create temporary file '/usr/local/cargo/git/db/aurras-7a79c31b974d5a1e/objects/pack/pack_git2_2b47ecf3648617ff': Read-only file system; class=Os (2)
error: failed to get `actions-common` as a dependency of package `actions v0.1.0 (/usr/src/actions)`

Caused by:
  failed to load source for dependency `actions-common`

Caused by:
  Unable to update https://github.com/hugobyte/aurras?rev=1f7e117

Caused by:
  failed to clone into: /usr/local/cargo/git/db/aurras-7a79c31b974d5a1e

Caused by:
  failed to create temporary file '/usr/local/cargo/git/db/aurras-7a79c31b974d5a1e/objects/pack/pack_git2_a366568d220d2482': Read-only file system; class=Os (2)
ERRO[0206] Error waiting for container: container 8a98a5e9a3fb6eff3bcc0bb6b7e7ac1f539b5cf58a0c9eb40f56e9eb439c07f4: driver "overlay2" failed to remove root filesystem: unlinkat /var/lib/docker/overlay2/6afa21c1800a1ca9b7e1ac5f755536fbb00d3d660a1f4ec7b574865be566d4ed: read-only file system

@Mr-Nobody21
Copy link

Mr-Nobody21 commented Nov 23, 2023

@keeganquigley

  • I'm not sure you answered my question about the branch. Should I be using next branch (set as the default) or the master branch? Or feature/UI-for-polkadot-payout

code for this milestone is in next

  • Am I supposed to have a local Aurras node running while completing these tasks?

You can either run locally or run it on an linux server

  • Do I need to be running the deployment instructions for Kubernetes and Docker Compose, or were those from a previous milestone?

Yes, Recommended :- Docker as openwhisk is one of the dependencies needed to run Aurras

UPDATE: I was able to set the API server key and successfully run ./deploy.sh but it failed, I think because of my Apple ARM64 chip. I will have to try again on Ubuntu.

Please let me know if you face any issues

@keeganquigley
Copy link
Contributor

keeganquigley commented Nov 28, 2023

Thanks for the changes @MuhammedIrfan and sorry for the delay. I was new to this project, so it took me a while to configure Google Firebase, OpenWhisk, OpenWhisk CLI, and all the dependencies. I was able to run the notification example, with Ubuntu, and you can find my final evaluation here. The delivery has hereby been accepted. Congrats on finishing the grant!

@keeganquigley keeganquigley merged commit 4bf8b64 into w3f:master Nov 28, 2023
3 checks passed
Copy link

We noticed that this is the last milestone of your project. Congratulations on completing your grant! 🎊

So, where to from here? First of all, you should join our Grants Community chat, if you haven't already, so we can stay in touch.
If you are looking for continuative support for your project, there are quite a few options. The main goal of the W3F grants program is to support research as well as early-stage technical projects. If your project still falls under one of those categories, you might want to apply for a follow-up grant. However, depending on your goals and project status, there are other support programs in our ecosystem that might be better suited as the next step. For example, projects with a Business Case/Token should look into the Substrate Builders Program or VC Funding and Common Good projects have a good chance of receiving Treasury Funding. If you are looking for guidance, the team at https://substrate.io/ecosystem/square-one/ has compiled a list of ecosystem support sources and are happy to help you navigate it.

For a more comprehensive list, see our Alternative Funding page. Let us know if you have any questions regarding the above. We are more than happy to point you to additional resources and help you determine the best course of action.
Lastly, we hope your W3F grant was a success and we want to thank you for being part of the journey!

Copy link

🪙 Please fill out the invoice form in order to initiate the payment process. Thank you!

@MuhammedIrfan
Copy link
Contributor Author

Thanks for the changes @MuhammedIrfan and sorry for the delay. I was new to this project, so it took me a while to configure Google Firebase, OpenWhisk, OpenWhisk CLI, and all the dependencies. I was able to run the notification example, with Ubuntu, and you can find my final evaluation here. The delivery has hereby been accepted. Congrats on finishing the grant!

No problem @keeganquigley, Thank you very much for the support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants