-
Notifications
You must be signed in to change notification settings - Fork 91
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
Create new project problem. #512
Comments
I'll update the doc with clarification. So, here's how to fix your errors:
|
Hello, @yuetloo ! Thanks for the answering and careful teaching!!! I'm sorry for not able to solve this problem quickly, I will do my best to follow the steps! |
Hi, @yuetloo! Sorry for bothering you again, here is my new deploy try:
But in the step.7, the command
May I ask you for a help again😥 |
@ChiHaoLu , what branch of clrfund did you use? I used the Check to make sure you didn't accidentally modify some subgraph files and the changes were not complete. The error looks like some files are corrupt or has incomplete changes.. |
@yuetloo I am using
However the create project problem still here, the error in the inspect are: I have compared my hosted service with yours, it seems like I didn't fetch the right contract interface or schema? And in the inspect error:
seems not match my deploy contract address. |
It looks to me that the issue was the subgraph was deployed from the wrong folder. Try deploying it from the subgraph folder (not the “qf” folder)
… On Jun 27, 2022, at 11:25 PM, ChiHaoLu ***@***.***> wrote:
@yuetloo I am using develop branch, I have solve the problem because I didn't command the codegen in qf folder. But the create project stuck still happens. Here is my continue steps after above.
Revise subgraph/subgraph.yaml and deploy to IPFS:
$ npx mustache config/rinkeby.json subgraph.template.yaml > subgraph.yaml
$ cd qf
$ npm run codegen
$ npm run build
$ npx graph deploy --node https://api.thegraph.com/deploy/ --ipfs https://api.thegraph.com/ipfs/ chihaolu/clrfund
Deploy Subgraph(in subgraph/qf)
$ graph auth --product hosted-service 35b6af8330584ac6ab0cfaaad4cf6832
> Deploy key set for https://api.thegraph.com/deploy/
$ graph deploy --product hosted-service chihaolu/qf
Revise vue-app/.env
VUE_APP_SUBGRAPH_URL=https://api.thegraph.com/subgraphs/name/chihaolu/qf
# Comma-separated list of URLs
VUE_APP_GUN_PEERS=http://localhost:8765/gun
VUE_APP_CLRFUND_FACTORY_ADDRESS=0xaD841958a0B80105661A0E2Bf78D97190A45e820
# Supported values: simple, brightid
VUE_APP_USER_REGISTRY_TYPE=simple
# clr.fund (prod) or CLRFundTest (testing)
# Learn more about BrightID and context in /docs/brightid.md
VUE_APP_BRIGHTID_CONTEXT=clr.fund
# Supported values: simple, optimistic, kleros
VUE_APP_RECIPIENT_REGISTRY_TYPE=optimistic
VUE_APP_RECIPIENT_REGISTRY_POLICY=QmYmiHfAh7mGMFxRpP1pTNLv1pjuYNW8nmxsCAJU2XoAKF
# Comma-separated list of IPFS hashes
VUE_APP_EXTRA_ROUNDS=
# Operator of clr.fund instance
VUE_APP_OPERATOR=
# Google Service Account credentials in JSON format
GOOGLE_APPLICATION_CREDENTIALS=
# Spreadsheet ID to send recipients data
VUE_APP_GOOGLE_SPREADSHEET_ID=
Build & Deploy Vue-App(UI)
$ cd vue-app
$ yarn build
$ ipfs add -r vue-app/dist/
$ yarn start:web
However the create project problem still here, the error in the inspect is:
I have compared my hosted service with yours, it seems like I didn't fetch the right contract interface or schema?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.
|
I couldn't deploy the subgraph in subgraph folder... It return the error:
However I didn't change the any files except the |
Hmm.. you definitely cannot use the I would suggest getting a clean copy of the source code, e.g. Remove the Remove the I also usually use Here's the commands I used after creating the subgraph on the explorer
Give that a try, hope it works, because I tested the steps, and they work for me. I have never had an issue with subgraph and node versions, but just in case, here are my versions |
I have REDO all steps above with the new document in goerli network. After the deployment in georli, I make sure the file in Here is the same error when run
Here is my debug.log:
Does the problem come from the some |
@ChiHaoLu I just noticed you're running on windows. I have not deployed the instance on windows before and have not seen this error. I'm not sure but it looks like I would suggest deploying the instance from a Linux machine as that's the tested platform. Even if you can resolve all these issues and eventually be able to start the web app, you'll still need to run the |
I got it. I have redo the whole steps in my Linux VM, but after the
I guess this may be relative with the Edited: I solve the
If I upgrade the
|
Hmm. I have graph version 0.21.1. See if you can change your graph version.
But I would expect it to use 0.21.0 as you ran yarn and that’s the version of graph-cli, v0.21.0
… On Jul 11, 2022, at 7:37 PM, ChiHaoLu ***@***.***> wrote:
I got it. I have redo the whole steps in my Linux VM, but after the yarn codegen, the another problem appears:
***@***.***:~/blockchain/monorepo/subgraph$ yarn codegen
yarn run v1.22.19
$ graph codegen
The current version of graph-cli can't be used with mappings on apiVersion less than '0.0.5'
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
I guess this may be relative with the @graphprotocol/graph-cli version?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.
|
May I ask what is your
|
@ChiHaoLu , I have @graphprotocol/[email protected]. Also, what Linux flavor do you use? I tested the steps using |
Hi there, I have to tried to deploy the whole project to rinkeby with the document in repo, but after I open the website and try to create a new project, the final step is stucked.
.env
incontracts
:.env
invue-app
:Because I don't really know what
VUE_APP_RECIPIENT_REGISTRY_POLICY
,VUE_APP_SUBGRAPH_URL
andVUE_APP_GUN_PEERS
to do, I think there may be some network setting error here?The text was updated successfully, but these errors were encountered: