Graphene GUI testing and feedback

[JonnyB]

This Graphene GUI doesn't seem ready yet. seems very buggy. I think the 2.0 launch should be cancelled personally.

[wuyanren]

https://graphene.bitshares.org/#/markets  There seems to be a bit of a mess.

[jakub]

In the settings

Please be more specific. In FF settings?

Haha I just realized you can't access the settings if the app doesn't initialize correctly, chicken and egg problem...

I mean the wallet settings, where you can enter the WS Api you want to use. I'll push a commit in a bit that removes the / from the default ws connection, guess you'll have to be patient until that reaches the server. If you're running locally then you simply need to edit ApiInstances.js, uncomment line 27 and replace it with the correct ws url.

@svk, has this been pushed yet? I still get a blank screen in my Firefox...

[jakub]

We used to have an account's open collateral positions listed in the account's overview page with an option to update them.
This is list is no longer there.
How is the user supposed to manage or close their collateral positions?

EDIT: It turns out the open collateral position list is there but I needed to reload the URL in the browser to get it. Seems like the overview page fails to update itself automatically.
I've already reported the bug here: https://github.com/cryptonomex/graphene-ui/issues/317

But part of the question still remains: how do I close a collateral position?

EDIT: I can see that the latest update has solved this problem as well.

[svk]

looks like graphene.bitshares.org / light wallet died.

not sure if it's connected, but I just imported my main keys + tried to claim balances

Yep, looks like the backend (witness node) crashed, I'll tell Valentine once he's online. It needs to be updated anyway..

[fav]

looks like graphene.bitshares.org / light wallet died.

not sure if it's connected, but I just imported my main keys + tried to claim balances

[svk]

I was using that new explorer from window10 (edge?). Also on Opera goes really slow and has graphic glitchs. Will give it a try on Firefox.
It seems using chromodo the transaction went fine but for some reason i am missing 108198 Core (bitshares) although the keys.json were exported after a total sync on 0.9.3c and after sending my total amount of bitshares to myself.

Any idea? Should i worry?

Thanks.

When did you send it to yourself? The current testnet uses a snapshot state from October 5th, if your transfer was after that you won't see it in the testnet.

[coiner]

I was using that new explorer from window10 (edge?). Also on Opera goes really slow and has graphic glitchs. Will give it a try on Firefox.
It seems using chromodo the transaction went fine but for some reason i am missing 108198 Core (bitshares) although the keys.json were exported after a total sync on 0.9.3c and after sending my total amount of bitshares to myself.

Any idea? Should i worry?

Thanks.

[coiner]

Testing on graphene.bitshares.org i am getting a now <= trx.expiration. Also i am missing 108000 bitshares from the total i have on bitshares 0.9.3c (totally syncronized) oh and i sent to myself all the funds previously to export the keys.json

Please advice,

[Troglodactyl]

The functionality was only added a few days ago, we just need to figure out the kinks. I'll see if I can add access to it in the connection failure screen.
It's stored in localStorage so you can clear it by clearing that, in Chrome its under resources in the dev tools.

In the online version (i.e. in the GUI accessed by https://graphene.bitshares.org) - what possible reason would I have to want to change it??
I think it should be completely removed (or disabled) in the online version.

No, it can be useful, say you're on OpenLedger but their backend servers go down, you could switch it to another api provider, like BunkerDEX or Banx, or even one you provide yourself.

I see. So you can have the html/js served by domain A and at the same time have the blockchain support (i.e. wss) served by domain B.
OK, that makes sense and it's great.

But this definitely requires a fool-proof implementation in the GUI so that people do not become cut off when they mess it up.
Maybe a drop-down offering a choice of available wss domains plus and advanced option to add your own wss URL.

The connection failure page should list the web socket connection information and allow the user to alter it before retrying, possibly buried behind an "Advanced" expander.

Yea I've gone and added this, I also refactored the whole thing so you now choose the websocket using a dropdown menu. In the settings you can add AND remove websockets to the list, while on the init-error page you can choose from the list, or add a new one then pick it.

Awesome!  Looking good.

[svk]

The functionality was only added a few days ago, we just need to figure out the kinks. I'll see if I can add access to it in the connection failure screen.
It's stored in localStorage so you can clear it by clearing that, in Chrome its under resources in the dev tools.

In the online version (i.e. in the GUI accessed by https://graphene.bitshares.org) - what possible reason would I have to want to change it??
I think it should be completely removed (or disabled) in the online version.

No, it can be useful, say you're on OpenLedger but their backend servers go down, you could switch it to another api provider, like BunkerDEX or Banx, or even one you provide yourself.

I see. So you can have the html/js served by domain A and at the same time have the blockchain support (i.e. wss) served by domain B.
OK, that makes sense and it's great.

But this definitely requires a fool-proof implementation in the GUI so that people do not become cut off when they mess it up.
Maybe a drop-down offering a choice of available wss domains plus and advanced option to add your own wss URL.

The connection failure page should list the web socket connection information and allow the user to alter it before retrying, possibly buried behind an "Advanced" expander.

Yea I've gone and added this, I also refactored the whole thing so you now choose the websocket using a dropdown menu. In the settings you can add AND remove websockets to the list, while on the init-error page you can choose from the list, or add a new one then pick it.

[spartako]

How do you close a 'usd-collateral-holder' position?

When I 'Update Position' and 'Collateral change   -424.46933 CORE' the CORE asset is displayed in the 'usd-collateral-holder' balance

Then when I try to transfer the 'CORE' to my account name, the GUI says 'usd-collateral-holder' is 'Not your account'

Also, all my collateral-holders Memo Keys says 'Not a valid public key'

Same problem here

[Troglodactyl]

The functionality was only added a few days ago, we just need to figure out the kinks. I'll see if I can add access to it in the connection failure screen.
It's stored in localStorage so you can clear it by clearing that, in Chrome its under resources in the dev tools.

In the online version (i.e. in the GUI accessed by https://graphene.bitshares.org) - what possible reason would I have to want to change it??
I think it should be completely removed (or disabled) in the online version.

No, it can be useful, say you're on OpenLedger but their backend servers go down, you could switch it to another api provider, like BunkerDEX or Banx, or even one you provide yourself.

I see. So you can have the html/js served by domain A and at the same time have the blockchain support (i.e. wss) served by domain B.
OK, that makes sense and it's great.

But this definitely requires a fool-proof implementation in the GUI so that people do not become cut off when they mess it up.
Maybe a drop-down offering a choice of available wss domains plus and advanced option to add your own wss URL.

The connection failure page should list the web socket connection information and allow the user to alter it before retrying, possibly buried behind an "Advanced" expander.

[jakub]

The functionality was only added a few days ago, we just need to figure out the kinks. I'll see if I can add access to it in the connection failure screen.
It's stored in localStorage so you can clear it by clearing that, in Chrome its under resources in the dev tools.

In the online version (i.e. in the GUI accessed by https://graphene.bitshares.org) - what possible reason would I have to want to change it??
I think it should be completely removed (or disabled) in the online version.

No, it can be useful, say you're on OpenLedger but their backend servers go down, you could switch it to another api provider, like BunkerDEX or Banx, or even one you provide yourself.

I see. So you can have the html/js served by domain A and at the same time have the blockchain support (i.e. wss) served by domain B.
OK, that makes sense and it's great.

But this definitely requires a fool-proof implementation in the GUI so that people do not become cut off when they mess it up.
Maybe a drop-down offering a choice of available wss domains plus and advanced option to add your own wss URL.

[svk]

The functionality was only added a few days ago, we just need to figure out the kinks. I'll see if I can add access to it in the connection failure screen.
It's stored in localStorage so you can clear it by clearing that, in Chrome its under resources in the dev tools.

In the online version (i.e. in the GUI accessed by https://graphene.bitshares.org) - what possible reason would I have to want to change it??
I think it should be completely removed (or disabled) in the online version.

No, it can be useful, say you're on OpenLedger but their backend servers go down, you could switch it to another api provider, like BunkerDEX or Banx, or even one you provide yourself.