The integration tests were previously just copied over from the
token-bridge directory and not changed at all (they still referenced the
token-bridge crate).
Clean up the files and add tests for basic functionality like sending
and receiving native + wrapped NFTs.
Refactor the solana Dockerfile so that the solana release installation
is a separate stage and have the builder stage derive from it. Add a
new "ci_tests" stage that also derives from the solana stage but runs
the integration tests instead.
Invoke the solana ci_tests stage from the Tiltfile when ci_tests are
enabled.
Fix all the tests for the solana bridge program so that we can start
running it in CI.
Use the `solana-program-test` crate as the test framework. Previously,
running the tests required spinning up a test validator and manually
deploying the program there. Now developers can just do `cargo test-bpf`
to run the tests without needing any additional setup (beyond installing
the solana tools). This also lets us split out the tests so that they
can be run separately rather than having to run everything sequentially
in a single integration test.
* sdk/js: improve type safety + add documentation
* sdk/js: add support for chain names
* sdk/js: fix boolean conditional bug in transferFromSolana
* sdk/js: remove unsafe ChainId coercions in sdk
* sdk/js: Chain id 0
This is a legit chain id that some governance VAAs target
* sdk/js: Add mainnet and testnet contract addresses
* sdk/js: bump version to 0.3.0
* sdk/js: limit minor version changes
* sdk/js: update contracts and add devnet
Co-authored-by: Csongor Kiss <ckiss@jumptrading.com>
Co-authored-by: Evan Gray <battledingo@gmail.com>
* algo/tests: enable relayer test
* algo/tests: increase timeout
* algo/tests: split tests into unit and integration
* algo/tests: move tests around
* algo/tests: remove file
* algo/tests: make it not optimize in dev mode @ gusc1a-ossdev-jsl5
* algo/tests: another test fix @ gusc1a-ossdev-jsl5
Co-authored-by: Josh Siegel <jsiegel@jumptrading.com>
Added two entry points: ComputeTvlCumulative and TvlCumulative.
The first computes the result and writes it to the results cache -
intended to be invoked periodically by a scheduled task.
The second reads from the results cache and returns it as the response.
* Added the `User-Agent` header to all requests to the block explorer
so cloudflare's browser check is happier.
* Add an option to sleep between loops hitting the block explorer. More
than 1 / second on polygonscan gets you blocked temporarily.
These changes are required to repair missed messages on polygon.
* Initial Celo support
Change-Id: Iee98ee29a8b09af9ca76945792b750d96a170702
* Watcher support
* Fix high level make file
* Remove node binary committed by mistake
* Port change from EthWatcher to CeloWatcher
* Use docker to build ABIs
* Refactor watcher to eliminate massive redunancy
* Fix lint-and-tests to handle multiple defs on link
* Minor code cleanup
* Celo should use ganache in devnet
* Prep for mainnet deploy
* Code review rework
* Remove celo from sdk package.json
* node/hack/repair_eth: use a cookiejar for http
Otherwise, explorers like polygonscan, which implement a cloudflare WAF,
will block all requests.
* node/hack/repair_eth: add -showError flag
When an explorer is having problems or blocks a repair http request, it returns an error like:
Failed to get current height: failed to decode response: invalid character '<' looking for beginning of value
This allows showing the actual response body to better troubleshoot the problem.