-
Notifications
You must be signed in to change notification settings - Fork 16
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
For Cycle 27 #887
Comments
ErrorsUSD amount not specified in summary section |
InfoRead BSQ amount from summary: 283.49 ErrorsIncorrect BSQ rate specified: 2.18, expected: 1.23
|
Reference: #819 |
InfoRead BSQ amount from summary: 283.49 ErrorsIncorrect BSQ rate specified: 2.18, expected: 1.23
|
Reference: #887 (comment) |
Tx ID: b7676812f3b62f274b6cb06cddf64c49fe23568f8a830ca8d4b2a878b70ff7c5 |
@wallclockbuilder Sorry for my late review as I had personal issues. Unfortunately I won't be able to complete the review for this cycle. Still I'll respond to this issue for documentation purpose latest tomorrow. I saw that you published your CR already so I'll try to review it in-time for everyone else to vote on. But worst-case you have to re-submit it in the next cycle. |
@wallclockbuilder For your v1.6.0 release test report. Could you please post here the export of your test payment accounts (fiat and alt) as you tested all of them. It would help other devs setting up all of them manually. Also in this test report it says you tested all trading test cases on Testnet (which is not possible, as it is not running anymore). How did you test this? |
Code Reviews: @ bisq-network/bisq#5365: For contributors without a track record I don't think it is a good precedent to compensate a utACK. In general I think to ask for code review compensation without contributing to the codebase first (more than fixing typos) would send the wrong signal for future CR code reviews (what would prevent someone just to utACK/ACK every PR and ask for compensation without doing anything) |
Closed as rejected. |
Summary
502.44
Contributions delivered
Cycle 23
Contributions in progress
The text was updated successfully, but these errors were encountered: