No problem; like I said, using node 20 works fine. I only noticed this issue recently, when I rebuilt my build environment, and tried doing so by the book (i.e. according to the docs).
If there’s something I can do to try to further narrow this down, let me know. I’m doing the build in an Ubuntu 24.04 VM, which I can restore to a working snapshot if testing causes it to break.
Tämä sotilasalueesta varoittava kyltti joutanee kai jo museoon, kun se aiheuttaa hämmennystä uusissa kävijöissä tuolla kuntoradan varrella.
Jollei siis tuota metsänplänttiä vielä oikeasti pv valvo.
Is it safe to update mongod* packages outside the script (directly with apt)? I prefer to leave security updates (and only those) to unattended upgrades, but it doesn’t cover these since they’re from the mongodb repository. AFAICT, the script would only allow me to update all packages (with ”Update the Operating System”), but I don’t want non-security updates.
mongod-amd64/noble 8.0.8 amd64 [upgradable from: 8.0.4]
mongodb-database-tools/noble/mongodb-org/8.0 100.12.0 amd64 [upgradable from: 100.10.0]
mongodb-mongosh-shared-openssl3/noble/mongodb-org/8.0 2.5.0 amd64 [upgradable from: 2.4.2]
mongodb-org-database-tools-extra/noble/mongodb-org/8.0 8.0.8 amd64 [upgradable from: 8.0.5]
mongodb-org-shell/noble/mongodb-org/8.0 8.0.8 amd64 [upgradable from: 8.0.5]
mongodb-org-tools/noble/mongodb-org/8.0 8.0.8 amd64 [upgradable from: 8.0.5]After the app has been updated, the next time it’s opened it shows the changelog (version history).
(See #2852)
I expect opening the app to have it authenticate me to give me access to my passwords. The changelog is a needless detour.
I appreciate the work that goes into developing the app without seeing the changelog. I can find the changelog myself, should I feel the need to read it.
1.12-r5
15
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.
Lasinsirua ja muuta jätettä valunut pyörätielle tuosta viereiseltä rakennustyömaalta.
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
Lasimurskaa tuossa mäessä kaupungin puoleisella reunalla melkein koko matkalta.
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.
That nitpick corner bookshelf almost @standupmaths levels of slantingness