Empty replies

[haayman]

I'm seeing empty replies in 0.17.1

https://social.ayco.io/@ayo/115588357835638239

The same reply in phanpy.social:

However: not all replies appear empty

This one is empty:
https://mastodon.social/@Fiederels/115588957659322977

This one is fine:

https://mastodon.social/@B123/115592288348511247

[shuuji3]

Does this issue happen on home timeline, status page, or notification page (or all of them)? I can see those replies on my end.

[haayman]

It's not just replies, also 'original' toots

https://mastodon.social/@donni/115534855858194530

I don't see any logic to it. It's both in the timeline and in notification page. It doesn't matter where it appears, but once it's empty it's empty everywhere.

Also: they are empty both in the canary branch as in 0.17.1

Maybe it's instance related?

[haayman]

For this user @LoganFive@beige.party everything disappears. It's so bad I can't even take a screenshot, because on his page not only are the posts empty, but the also are replaced with blank space

[shuuji3]

Possibly, but I don't have any idea causing this yet. If both version has the same error, it was not caused by major update of masto.js.

[haayman]

Maybe it's because on my own instance https://todon.nl/ we've upgraded to the latest mastodon version

404 ?

[haayman]

no, the 404 is unrelated to the original issue

[shuuji3]

Yes, /v1/push/subscription endpoint is usually used to register the push notification. That might be a separate issue caused by Mastodon update.

And I was able to reproduced the second issue, empty space in the profile timeline. I guess this is also a separate issue. Let me create a separate GitHub issue.

[haayman]

This is where the text should appear I think

This is how it should look:

So the 3rd v-if evaluates to false

[haayman]

So, the StatusBody is empty.

In StatusBody.vue it fails on

const { translation } = await useTranslation(status, getLanguageCode())

I never get to

const emojisObject = useEmojisFallback(() => status.emojis)

The debugger won't go into getLanguageCode() or useTranslation(), but this is what I see in the console

[haayman]

Alright, I've narrowed it down to line 126 in translate.ts.

elk/app/composables/masto/translate.ts

Line 126 in e521bad

shouldTranslate = shouldTranslate && (await (globalThis as any).Translator.availability({

this is where it throws.

elk/app/composables/masto/translate.ts

Line 132 in e521bad

const enabled = /*! !useRuntimeConfig().public.translateApi && */ shouldTranslate

is never reached

In my case status.language = "nl" and to = "en"

[haayman-imagem]

I'm no longer seeing the issue anymore. Neither in main nor in canary

[shuuji3]

Oh, that's a good news! 🙂 I also upgraded masto.js to the latest version (#3447) this morning.

If you encounter the same issue again, please feel free to reopen the issue.