Skip to content
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

Handle situations when a Paratime is unavailable #619

Merged
merged 1 commit into from
Jul 9, 2023

Conversation

csillag
Copy link
Contributor

@csillag csillag commented Jun 28, 2023

Before it was a silent failure

@github-actions
Copy link

github-actions bot commented Jun 28, 2023

Deployed to Cloudflare Pages

Latest commit: 6a3ccdccd8076ce93265789c0cc51d929047e349
Status:✅ Deploy successful!
Preview URL: https://94071b19.oasis-explorer.pages.dev

@csillag csillag force-pushed the csillag/handle-unavailable-paratime branch from c17af98 to 9236b7f Compare June 28, 2023 15:55
@csillag csillag marked this pull request as ready for review June 28, 2023 15:55
@csillag csillag requested review from lukaw3d and buberdds June 28, 2023 15:55
@csillag csillag force-pushed the csillag/handle-unavailable-paratime branch from 9236b7f to a78c56a Compare June 28, 2023 16:01
const target = getNameForScope(t, scope)
return (
<StickyAlert severity="warning">
{lastUpdate
{unavailable
? t('home.runtimeUnavailable', { target })
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would reuse home.apiOffline

but also, this should not be possible on backend. Can we get backend not to do this, instead?

Copy link
Contributor Author

@csillag csillag Jun 28, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would reuse home.apiOffline

I considered that, but the scope of that warning is too wide to correctly describe this situation. (After all, we can get info about other runtimes...)

but also, this should not be possible on backend. Can we get backend not to do this, instead?

You are certainly welcome to try to pursue them! I have already brought up the topic on the relevant slack channel, and got the answer that this is more or less considered to be normal... in any case, I think it doesn't hurt to have multiple lines of defense here.

@csillag csillag force-pushed the csillag/handle-unavailable-paratime branch from a78c56a to 6a3ccdc Compare July 9, 2023 13:59
@csillag csillag merged commit dbbeaa1 into master Jul 9, 2023
7 checks passed
@csillag csillag deleted the csillag/handle-unavailable-paratime branch July 9, 2023 14:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants