Can’t build 2.27.0 with node 22 as recommended in documentation

20. huhtikuuta 2025 klo 18.24
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Mattermost, Node.js

The Developer setup documentation says ”We recommend using NodeJS v22”, but trying to build the app (release 2.27.0) with node 22 fails (after nvm install 22.14.0):

npm error code EBADENGINE
npm error engine Unsupported engine
npm error engine Not compatible with your version of node/npm: mattermost-mobile@2.27.0
npm error notsup Not compatible with your version of node/npm: mattermost-mobile@2.27.0
npm error notsup Required: {"node":"^18.18.0 || ^20.0.0","npm":"^9 || ^10"}
npm error notsup Actual:   {"npm":"10.9.2","node":"v22.14.0"}
npm error A complete log of this run can be found in: /home/jani/.npm/_logs/2025-04-20T11_20_48_320Z-debug-0.log

The build works if I install node 20.19.0 instead.

Vastaa viestiin sen kontekstissa (Github)

Lasinsirua ja muuta jätettä valunut pyörätielle tuosta viereiseltä rakennustyömaalta

19. huhtikuuta 2025 klo 18.01
Sijainti: Muut: Oulun Palautepalvelu

Lasinsirua ja muuta jätettä valunut pyörätielle tuosta viereiseltä rakennustyömaalta.

Vastaa viestiin sen kontekstissa (Oulun Palautepalvelu)

[QUESTION] Is showing the changelog at startup only a feature in the beta version, or in the final release as well?

17. huhtikuuta 2025 klo 9.23
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Keepass2Android, saavutettavuus

I was initially going to report this as a bug, but then I realized I’m in the beta program, so the issue could be specific to that. The unprompted version history at startup is an irritating interruption to using the app, and I could leave the beta program, if I knew that doing so gets rid of the interruption. (I’ve had no other issues with the beta AFAICR.)

What version of Keepass2Android are you using?
1.12-r5

Vastaa viestiin sen kontekstissa (Github)

Lasimurskaa tuossa mäessä kaupungin puoleisella reunalla melkein koko matkalta

7. huhtikuuta 2025 klo 16.29
Sijainti: Muut: Oulun Palautepalvelu

Lasimurskaa tuossa mäessä kaupungin puoleisella reunalla melkein koko matkalta.

Vastaa viestiin sen kontekstissa (Oulun Palautepalvelu)

Episode pages on the web now only contain JavaScript, without any HTML content about the episode

11. maaliskuuta 2025 klo 13.02
Sijainti: Muut: Pocket Casts
Avainsanat: Javascript, Pocket Casts

I just noticed that most episode pages on the web now only contain JavaScript, without any HTML content about the episode. Please tell me this is just temporary!

I’m using a custom piece of software that automatically titles all the links I post on my blog, and I list all the podcast episodes I’ve listened daily in my posts. The titles are parsed from the HTML, but the new JS-only pages don’t even have the episode title embedded in them!

For reference, here’s one episode where the page is just JavaScript: https://pca.st/nzceirq9

Here’s another one, which (as of this writing) still has actual episode-related content in the source code: https://pca.st/episode/b5553ab4-36d1-475e-bc30-b7fd4e0fe5e5

If this is a permanent change, it no longer makes sense for me to link to episode pages on Pocket Casts; I’ll have to go back to referring to various other podcast sites’ episode pages instead.

Vastaa viestiin sen kontekstissa (Pocket Casts)

That nitpick corner bookshelf almost @standupmaths levels of slantingness

6. maaliskuuta 2025 klo 14.36
Sijainti: Videosivustot: YouTube
Avainsanat: Matt Parker

That nitpick corner bookshelf almost @standupmaths levels of slantingness

Vastaa viestiin sen kontekstissa (YouTube)

Seems to occur when those posts get loaded after tapping ”Load missing posts”

26. helmikuuta 2025 klo 11.56
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Mastodon

At least in the mobile app this (showing of posts that should be filtered out completely) seems to occur when those posts get loaded after tapping ”Load missing posts”. So it’s like the filters don’t get applied to posts loaded on demand: I just had one shown to me earlier with the ”matches filter”, ”show anyway” preamble, but now that I went to check the timeline on the same device again, said post was now filtered out completely. (It hadn’t been deleted in the meantime, I checked.)

(I couldn’t remember if the example in my web UI screenshots above was similarly loaded with ”Load missing posts”.)

Vastaa viestiin sen kontekstissa (Github)

Tuhtotien ja Teljotien liittymät veden vallassa

23. helmikuuta 2025 klo 14.51
Sijainti: Muut: Oulun Palautepalvelu
Avainsanat: Koskelantie, liikenne, Sulfiittikatu, Teljotie, Tuhtotie

Tuhtotien ja Teljotien liittymät veden vallassa. Myös Koskelantiellä vähän ennen Sulfiittikatua klv:llä samanlainen allikko.

Vastaa viestiin sen kontekstissa (Oulun Palautepalvelu)

Valopylvään paneeli auki

22. helmikuuta 2025 klo 17.19
Sijainti: Muut: Oulun Palautepalvelu

Valopylvään paneeli auki. Ehkä aura rouhaissut ohi mennessään.

Vastaa viestiin sen kontekstissa (Oulun Palautepalvelu)

v2.25.1 FTBFS (Android)

21. helmikuuta 2025 klo 15.19
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Android, Mattermost

Trying to build v2.25.1 with `npm build:android` fails with what looks like a missing dependency. This was not an issue with v2.25.0, so the cause is some recent change.

The full log is below, but here’s what I think is the crucial part:

* What went wrong:
Could not determine the dependencies of task ':app:mergeReleaseNativeLibs'.
> Could not resolve all dependencies for configuration ':app:releaseRuntimeClasspath'.
> Could not resolve project :frameanimation.
Required by:
project :app > project :expo > project :expo-image
> No matching variant of project :frameanimation was found. The consumer was configured to find a library for use during runtime, preferably optimized for Android, as well as attribute 'com.android.build.api.attributes.AgpVersionAttr' with value '8.2.1', attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'release', attribute 'org.jetbrains.kotlin.platform.type' with value 'androidJvm' but:
- No variants exist.
> Could not resolve project :gif.
Required by:
project :app > project :expo > project :expo-image
> No matching variant of project :gif was found. The consumer was configured to find a library for use during runtime, preferably optimized for Android, as well as attribute 'com.android.build.api.attributes.AgpVersionAttr' with value '8.2.1', attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'release', attribute 'org.jetbrains.kotlin.platform.type' with value 'androidJvm' but:
- No variants exist.

fail.log

Vastaa viestiin sen kontekstissa (Github)

Vanhempia »