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
reload on mock server error #948
Comments
@ricburton do these error relate to reloading on the mocked network? |
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 < ***@***.*** > 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 (
#948 (comment) ) , or
mute the thread (
https://github.com/notifications/unsubscribe-auth/AAavkCDIUEY9k9GYuE9EtwuZcBlEKxxNks5uH2j9gaJpZM4VJQ8o
).
|
On which Voyager version are you? |
I can't test the mock server because Voyager crashes on startup. |
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 < ***@***.*** > wrote:
On which Voyager version are you?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub (
#948 (comment) ) , or
mute the thread (
https://github.com/notifications/unsubscribe-auth/AAavkIPOQWbFUfCHTmfLnnaQm3kNyTefks5uIQZvgaJpZM4VJQ8o
).
|
@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. |
Using the env flag "COSMOS_MOCKED=true" should start Voyager in mocked mode. |
@okwme What do you mean by "reloading"? Do you mean "Refresh"? Refreshing works for me on the mock server. |
Blocked: the request is unclear |
Great—thanks!
Richard
…On Thu, Jul 26, 2018 at 15:24:05, David Braun < ***@***.*** > wrote:
Blocked: the request is unclear
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub (
#948 (comment) ) , or
mute the thread (
https://github.com/notifications/unsubscribe-auth/AAavkEhiM_98ADWx6-te_78UZZxLNJZpks5uKhdVgaJpZM4VJQ8o
).
|
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. |
Switching to a mock network and then refreshing the view.
David Braun <notifications@github.com> 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
<#948 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AFmO2frHb4AU5JHON7QaS-JpmoNWWasMks5uK0LBgaJpZM4VJQ8o>
.
|
Refreshing the view with CMD+R ;) |
When I type CMD+R nothing happens. I don't see it in any of the menus. Are you starting with |
CMD+R is refreshing chrome. You have to type it while focussing the dev-tools. |
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 |
Hmm, If we persistent the mocked config, Voyager would also be mocked mode on the next start. Do we want that? |
Yes, why wouldn't we? To me that would be consistent with the principle of least surprise. |
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. |
I would expect Voyager "to just work" again when reopening it again. |
Idea how to implement:
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. |
UI Version: 0.7.0
Description: Reloading on testnet server works now thanks to #940 but it still doesn't work on the mock server
The text was updated successfully, but these errors were encountered: