You are reading content from Scuttlebutt
@Daan %cStAPIpCjTVLSt/wdGxvv1XAGrPfAxApD4kddHKxzy4=.sha256

Progress update on patchwork modernization

I recently started updating the dependencies for patchwork. Since there are no automatic builds, tests, or anything else, I've just been doing it manually so far. That is, I've been batching dependabot's bump PRs together based on which ones are easy to merge and seem like they should not require code changes. I've been deciding this by studying the changelogs, commit messages, and sometimes the diffs. Non-ssb dependencies went first, and an hour ago I merged the first bunch of ssb-related dependency bumps.
For every batch of commits I selected, I ran patchwork with the patches for about a day, also trying out some code paths depending on which ones should be touched by the updates (hence the pub follow to @gossip.noisebridge.info earlier, to test that invites work). As I said, most of these PRs are not changing behaviour at all, so I'm kinda comfortable with that.

If anyone is interested and comfy with npm ci && npm start and wants to take it through its paces, feel free.

There are two more small version bumps that I can probably do quickly, and then I'll get into #secret-stack and finally #electron which is gonna be.... funfunfun... We're running on electron 7, and the last version is 11. And those changelogs are... not the same size as in the ssb ecosystem. 😆

Anyhow, that's it. Just merrily grinding along here.

User has chosen not to be hosted publicly
User has chosen not to be hosted publicly
@Daan %FajlN4ohsik7tfuRAMR1T04bVPv6DyiDLpUOzGj0cX0=.sha256

#ssb-search should be an easy upgrade, but do I have time for it to rebuild the full-text index on 1GB of offset log? 🤔

User has chosen not to be hosted publicly
@Daan %CEMTWJsAS+oV5xrbMqxqTyBIfRVq2nDLFAjfydcT17c=.sha256

@alanz that's great to hear! Do tell me (here or on github) if anything breaks!

If not now, when?

Overnight? 😆
But who am I kidding, I want to see this thing purrrrrrr. 👈 "purrrrrr" is the sound of my laptop's fans when rebuilding ssb indexes.

User has chosen not to be hosted publicly
User has chosen not to be hosted publicly
@Daan %aA94BkK/I6HeBbJPb1mVCq/uh4KQNMFf0VDVvUO5KFA=.sha256

Hmmm... I'm still good after re-indexing and restart.

Did you get any terminal output?

@Daan %9TE7ghjF+6T3QSOZYV/HCiFtn37HKZTPNYSeHARWMas=.sha256

Also, what does ssb-server status give you?

User has not chosen to be hosted publicly
@Daan %d8FdVhZteTI8yd0kze68hN16HVOu5ASbnspSeFiXLqQ=.sha256

Ugh, that's... depressing... the worst kind of bug... 😐

User has chosen not to be hosted publicly
@Daan %P+iXuKlaJX/WLt6JsNxnEONy/JZWhwvCexBUOAAHw4Y=.sha256

@alanz and with "what it was before" you mean everything works, or "no avatars"?

User has chosen not to be hosted publicly
User has chosen not to be hosted publicly
User has not chosen to be hosted publicly
@Daan %YIVF0+lUoTreJGujTNC6ME3rjdNJWxCKWL9mLJEzLd0=.sha256

@be kind it's very kind of you to call patchwork progressive. It is the oldest client we have around, really. 😛
As for the automatic builds, that is on my list, but after thinking about it I'm unsure how much it would contribute. It would allow non-technical users to try out new builds, but then those users are more likely to get stuck if they encounter problems, and less likely to be able to provide detailed, technical feedback. So that'd be a bummer.

That being said, if you want to build patchwork yourself in a useful manner, you should get familiar with git, nodejs/npm, and you can follow the build instructions which are fairly default for the node ecosystem.

@alanz thanks for raising the flag!
I just checked out 48c618c104942250d31e7373405910ccd16963f2 ("bump ssb-markdown") and rebuilt (took forever...) and everything seemed fine, also after restart.
Then I proceeded to 88ceb2bc2e0746eb7b037ca58c1eb4dcce0b24a2 (bump ssb-backlinks) and rebuilt again, everything seemed fine. Restarted... looked fine at first but turned out that it didn't have the correct indexes to retrieve replies to threads. So every thread was shown as just its root.
I just deleted the backlinks index & restarted, and now it works after reindexing.
Now I'll restart again and see....

@Daan %O2fUiADvYLH4ez9JSCmCl5qFU62fcwNEPYLRCdlf8XA=.sha256

Okay now it works....

User has chosen not to be hosted publicly
@Linas %JbJmKLL1QcN5c79MeRD5shsKwzebpXVKZSqGW2BrcCY=.sha256
Voted # Progress update on patchwork modernization I recently started updating t
@cel-desktop %A2MEhAqcHZkA0ZtWtzWRucQJi/4ZgZIj3HTRQs89wRY=.sha256

Nice work.

deleted the backlinks index & restarted, and now it works after reindexing

I also encountered this recently:
https://github.com/ssbc/ssb-backlinks/issues/20

didn't have the correct indexes to retrieve replies to threads

seems consistent with what I encountered too.

User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
Join Scuttlebutt now