-
-
Notifications
You must be signed in to change notification settings - Fork 156
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
test/core-connectors #380
test/core-connectors #380
Conversation
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
This reverts commit 18e46d5.
Followed the steps for setting up gateway including copying the
Steps to reproduce:
|
@rapcmia I remove the Larp code since it was mainly for reference, so you don't need the |
No more changes in this branch. I'm making changes slated for v2.4 in another branch https://github.com/hummingbot/gateway/tree/core-2.4 |
gw a72ea11 + Client Steps:
Actual: a72ea11 logs etc.zip
6 orders filled on jupiter solana side (only one recorded by bot) |
gw a72ea11 + Client Steps to reproduce:
Actual:
|
this issue and the ones that @rapcmia reported should be fixed after you pull the latest commits in the client PR: hummingbot/hummingbot#7367 |
Hi @fengtality
Will finalize tests on meteora and approve later today if all ok, thank you 🙇🏼 |
PR updated: Review uniswap_ethereum_avalanche and meteora endpoints Review uniswap_ethereum_avalanche / okx arbitrage
Run API test for Meteora connector using fastify
We are able to opened a position on the sample pool MEME/USDC and use its pooladdress to open position successfully. However getting status code 503 (service unavailable) on some endpoints which can be found on the gateway log file below |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Setup this gateway PR with hummingbot PR test / gateway-core-connectors hummingbot#7367
- Fresh installation on source build on every new commit
- Found issues and compare to development: Not compatible
- Issues reported on initial tests has been addressed by developer
- Run tests on arbitrage_controller config on following connectors:
- jupiter_solana_mainnet-beta
- uniswap_ethereum_avalanche
- uniswap_ethereum_polygon
- Run API tests
- Watch Mike's demo of gateway for meteora
- Run tests on postman and fastify
- Compare endpoint and controller test results ok
- Run tests on Meteora endpoints (Most worked, others return status code 503)
- Tests done:
- Most tests are done with quicknode for SOLANA and infura for ethereum
- Setup CEX/DEX and DEX/CEX on controller-config
- Review arbitrage event:
- Trade data on gateway, executor table and hummingbot matched
- Behavior when suddenly insufficient balance
- Review txhash generated
- Observe behavior on different node providers
- Run postman tests on jupiter and uniswap connectors (arbitrum, avalanche and polygon)
- Run fastify for meteora endpoints
- Fetch prices and active trading bins
- Swapped and open position ok
- Reported found issues on other requests (ongoing)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Cloned [a72ea11](a72ea11) + Client [13fc657](hummingbot/hummingbot@13fc657)
- connected jupiter, uniswap arbitrum, avalanche, bsc, celo, polygon
- checked balance successfully
- created/started amm_arb successfully on uniswap
- arbitrage controller script on jupiter / binance: ok
No description provided.