-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Can not edit order: "No value present' #2210
Comments
|
Just to verify my assumption: Could you please tell me the market/asset of your offer? I think it has something to do with an offer of an asset that was removed from the client because of trading inactivity. |
@clashicly Can you please update to the latest version v0.9.3 to see if your problem is fixed? I tried to simulate it in a test, but wasn't able to cause this exception within the lastest code on master. |
BCHC/BTC |
Same issue with v0.9.3 |
BCHC (Bitcoin Clashic) has probably been delisted from Bisq due to too low activity. And I don't find BTCC (Bitcoin Classic ?) anymore on Bisq v0.9.3 |
Isn't everything low activity besides XMR? |
No
Bisq is open-source, is always lacking devs to implement so many things, and welcomes contributors. |
@clashicly Could you please post the error log you get in version 0.9.3. I think it must be something else. Just so I'm able to simulate it in a test probably. The exception you posted shouldn't exist in v0.9.3. |
@ripcurlx I have since cancelled the orders that I was unable to modify. I am no longer able to reproduce error messages at this time. I can confirm that I received what appeared to be the same error after upgrading to 0.9.3, but did not save the log to compare vs 0.9.1 errors. |
@clashicly Thanks for the update. If it occurs again feel free to re-open this issue or create a new one. |
v0.9.1 win64
Steps to reproduce:
Portfolio (tab), My Open Offers (sub tab), click green pencil on right. Get a dialog "No Value Present"
Subsequent attempts at editing have no action/error.
Two Orders originated 3-4 months ago and Bisq was upgraded from v0.8 to v0.9.1 since.
The text was updated successfully, but these errors were encountered: