-
Notifications
You must be signed in to change notification settings - Fork 291
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
fix barge connection #1729
fix barge connection #1729
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Ignored Deployment
|
✅ Deploy Preview for market-oceanprotocol ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
Here some update on how barge is interacting with the market: We can run
To connect
To interact with If all it's correct you should see the the problem is that even though the tx goes throw successfully (on the market), on This error is only visible when transacting on the The goal is to make sure our configs are returned correctly from ocean.js (already fixing; everything should work under |
This seems redundant, most likely using |
Yes, that's how it should work. |
FYI: Configs compared Logs publishing from barge |
Code Climate has analyzed commit 6d83147 and detected 4 issues on this pull request. Here's the issue category breakdown:
The test coverage on the diff in this pull request is 27.7% (50% is the threshold). This pull request will bring the total coverage in the repository to 20.3% (0.0% change). View more on Code Climate. |
Just tried the features added by this branch merged into I started barge as instructed in the README. I suppose I also need to copy the addresses of the deployed contracts using
I cannot get past this. Am I missing something? |
Changes proposed in this PR:
development
network