-
-
Notifications
You must be signed in to change notification settings - Fork 131
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
Serialize lists to comma delimited string in PaymentAccount.toJson()
#1620
base: master
Are you sure you want to change the base?
Conversation
Getting this error testing your PR with "Can validate payment account form":
It would be best if you're able to run the test to avoid back and forth testing. |
@woodser How exactly are you able to run the tests? When I tried running |
A small suggestion: why don't we add tests to a workflow or create one that runs all the tests using github actions? |
monerod1-local needs to be run with monerod2-local. Here are complete instructions to run a local testnet, then run API tests.
The real end-to-end tests are run as part of haveno-ts CI, but it’s based on what’s committed to haveno repo's master. Here's the last run: https://github.com/haveno-dex/haveno-ts/actions/runs/13392206971 |
@woodser It's struck at this stage. It's the same on Windows. I'm currently on Linux Mint |
@woodser I have tried forking haveno-ts repo and modifying the original repo link to my fork in the Dockerfile in haveno directory. Will this be a reliable method to test the fork and its changes? |
I wonder why there are exceptions like UPDATE: the workflow has failed and I cannot identify any errors (can't differentiate between errors and find their origin). |
Many errors will appear as the tests are running, to test proper error handling, so that's expected. You can run only the needed test with:
You should be able to confirm this test passes without any changes. |
@woodser I am not able to get the detailed log of the error in the program like this:
@woodser All I see in the ts fork is that the test has failed, it doesn't exactly tell which part of the code failed. See |
You should see the exception if you scroll up through through the logs running the tests locally. Or using GitHub's runner, you can see the error last under Collect Docker Logs > docker-user1, from your link. You can confirm this test will pass without any changes. |
As the title suggests, it tries to approach and fix issue 1549.
This is a newly created PR, the old PR was deleted because it was having some problems and it was not mergeable.