Lunie: reload on mock server error

[okwme]

UI Version: 0.7.0

Description: Reloading on testnet server works now thanks to https://github.com/cosmos/voyager/pull/940 but it still doesn't work on the mock server

[ricburton]

This was my experience trying to go on a bold voyage. ⚓️

[faboweb]

@ricburton do these error relate to reloading on the mocked network?
The encoding already has an issue: #926
The "Couldn't create account" is fixed in the latest version.
We will very probably release a new version on the new testnet this week.

[ricburton]

Not sure how to do that. This is what happens: https://cl.ly/3k220x1O3d0x

Richard

On Wed, Jul 18, 2018 at 12:57:33, Fabian < [email protected] > wrote:

@ ricburton ( https://github.com/ricburton ) do these error relate to
reloading on the mocked network?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub (
https://github.com/cosmos/voyager/issues/948#issuecomment-406002225 ) , or
mute the thread (
https://github.com/notifications/unsubscribe-auth/AAavkCDIUEY9k9GYuE9EtwuZcBlEKxxNks5uH2j9gaJpZM4VJQ8o
).

[faboweb]

On which Voyager version are you?

[NodeGuy]

I can't test the mock server because Voyager crashes on startup.

[ricburton]

I was on the latest version when I tried. Is there anything else I can do to help you debug?

Richard

On Thu, Jul 19, 2018 at 18:21:35, Fabian < [email protected] > wrote:

On which Voyager version are you?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub (
https://github.com/cosmos/voyager/issues/948#issuecomment-406432331 ) , or
mute the thread (
https://github.com/notifications/unsubscribe-auth/AAavkIPOQWbFUfCHTmfLnnaQm3kNyTefks5uIQZvgaJpZM4VJQ8o
).

[jbibla]

@NodeGuy there was once a way - may have been removed. @faboweb will know.

@ricburton that was most likely an issue with the previous testnet - unrelated to the mock server. we'll have a new version of voyager out for the (hopefully more stable 🤞) gaia-7002 very soon.

[faboweb]

Using the env flag "COSMOS_MOCKED=true" should start Voyager in mocked mode.

[NodeGuy]

@okwme What do you mean by "reloading"? Do you mean "Refresh"? Refreshing works for me on the mock server.

[NodeGuy]

Blocked: the request is unclear

[ricburton]

Great—thanks!

Richard

On Thu, Jul 26, 2018 at 15:24:05, David Braun < [email protected] > wrote:

Blocked: the request is unclear

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub (
https://github.com/cosmos/voyager/issues/948#issuecomment-408207595 ) , or
mute the thread (
https://github.com/notifications/unsubscribe-auth/AAavkEhiM_98ADWx6-te_78UZZxLNJZpks5uKhdVgaJpZM4VJQ8o
).

[faboweb]

I can confirm that this is an issue:

[NodeGuy]

What is it that you're doing? Just switching back and forth between the Live Testnet and the Mock Testnet? I can do that without error.

[faboweb]

Switching to a mock network and then refreshing the view.

David Braun [e-mail] schrieb am Fr., 27. Juli 2018, 18:41:

What is it that you're doing? Just switching back and forth between the
Live Testnet and the Mock Testnet? I can do that without error.

—
You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub
https://github.com/cosmos/voyager/issues/948#issuecomment-408474221, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AFmO2frHb4AU5JHON7QaS-JpmoNWWasMks5uK0LBgaJpZM4VJQ8o
.

[NodeGuy]

I can't reproduce it:

[faboweb]

Refreshing the view with CMD+R ;)

[NodeGuy]

When I type CMD+R nothing happens. I don't see it in any of the menus.

Are you starting with yarn start?

[faboweb]

CMD+R is refreshing chrome. You have to type it while focussing the dev-tools.

[NodeGuy]

Thank you, now I can recreate the problem.

The bug is caused by the mock setting not being persisted. Why are we not persisting all of the Vuex state in localStorage?

[faboweb]

Hmm, If we persistent the mocked config, Voyager would also be mocked mode on the next start. Do we want that?

[NodeGuy]

Yes, why wouldn't we? To me that would be consistent with the principle of least surprise.

[faboweb]

The sign-in flow sucks in this case, as the user reopens Voyager and then needs to signin and then switch to the live network to then sign in again.

[faboweb]

I would expect Voyager "to just work" again when reopening it again.

[faboweb]

Idea how to implement:

• tell the main thread that we are running in mocked mode
• on booting, the main thread tells the view thread we are running in mocked mode

But: For simplicity I agree that we just store it as well as balances.et Al. We can then later check if this is confusing for users.