-
Notifications
You must be signed in to change notification settings - Fork 321
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
Uniswap doesn't have the required data to calculate yield #775
Comments
Hey @dmatora! The reason for the error is that the tests take place in a local blockchain environment where Uniswap (more specifically its subgraph) isn't available. The same error can be seen in the browser console if you try to use the frontend on any of the Ethereum testnets. We should have probably made this a warning instead, as it's actually harmless. For example see this passing CI run where the same error is present: |
Shouldn't happen if i checkout mainnet-coverage branch, right? |
The error is expected to show up regardless of branch when running |
Switching branch does solve the issue for me (at least when using fresh Linux box for new build), but the person who asked me for help (running windows) says he is still getting the issue even when using specified branch |
Ah, so on the main branch, the tests are failing for you? Can you show the last 100 or so lines of output? I double checked by running the tests locally just now (on main branch), and they are passing on my end, even though the Uniswap error is visible:
|
Well, it says |
The frontend checks for an optional config.json (looks like this: https://devui.liquity.org/config.json), however when running the frontend in React Testing Library, this file won't be present; in fact the frontend assets aren't even served via HTTP. So when the frontend checks for the config file (happens here) there isn't even an HTTP server to connect to, hence Ideally, we should have mocked out any network requests from the test. However, the error isn't fatal, and the frontend proceeds with the default configuration, which is fine for the purpose of this test. If in the end it says |
I'm using |
No workaround is needed. Both the Uniswap yield error and ECONNREFUSED are expected to show up during a successful run of the tests. They can be ignored. It would be nice if they didn't, but since they are harmless, we didn't prioritize eliminating them. |
Getting
Uniswap doesn't have the required data to calculate yield
error when runningyarn test
The text was updated successfully, but these errors were encountered: