Spelling mistake in Japanese display

[Shima-Nao]

[公開してったダッシュボード] is mistaken,

[公開されたダッシュボード] is correct.

[Shima-Nao]

@rickmcgeer @merryman
Please fix it asap. Thank you.

[rickmcgeer]

@Shima-Nao thanks to @merryman there is a fix. I am testing on my local system and should deploy tomorrow

[rickmcgeer]

@Shima-Nao this should now be fixed. Please verify

[Shima-Nao]

@rickmcgeer @merryman
I'm confirm using a Japanese environment (7 May JST), but the messages are still in English.
Deployed not yet?

[merryman]

@rickmcgeer It seems like 4b53c78 broke the dispatch to the dashboard object that originally was handling the publish prompt. Is there a reason for why you decoupled that? Thats why the changes I did to the component do not propagate through.

[rickmcgeer]

It was my error, fixing today. This has led to some issues which I've gone into in some detail with the Lively repo.
@Shima-Nao I expect to have this sorted out by tomorrow. It's a minor change

[rickmcgeer]

Fixed on the development system, will build and deploy

[Shima-Nao]

@rickmcgeer
I've tried several times, but it always times out and fails to start. Could you please review the config?

[rickmcgeer]

@Shima-Nao according to the logs the cluster looks fine, but I am replicating this. I will need to look into it with Google tomorrow morning Pacific time,

[rickmcgeer]

@Shima-Nao a quick update. This appears to be a Google issue. We've brought up a clean copy of the Hub and can transfer the kct-free accounts to it, but the storage is tied to the old Hub. We're working to recover that. I've asked that we bring this up tomorrow.

[Shima-Nao]

@rickmcgeer I got it. I understand that you are currently troubleshooting. thank you so much.

[Shima-Nao]

@rickmcgeer @merryman

The wording revisions have been completed, so this ticket can be closed.
*Any other issues will be addressed in a separate ticket.