Comment on Tuesday SOTD Thread - March 25th, 2025 (#651)
djundjila@sub.wetshaving.social 1 week ago
Tue 25 Mar 2025: Day 13 of March Madness
- Brush: Simpson Chubby 2 Super Badger
- Razor: Thiers Issard – 69 Médaille Argi (frame back)
- Lather: Spearhead Shaving Company – Seaforth! Black Watch
- Post Shave: Spearhead Shaving Company – Seaforth! Black Watch
- Fragrance: Spearhead Shaving Company – Seaforth! Black Watch
Let’s go for one more round of who gets cut before TSF with a solid Spearhead lead:
Scrape time: Tue 25 Mar 2025, 07:00:10 GMT
Artisan Brand | ∑ |
---|---|
Spearhead Shaving Co. | 1 |
Barrister and Mann | 0 |
Catie’s Bubbles | 0 |
Talent Soap Factory | 0 |
Total: | 1 |
I honed the frame back yesterday, and it cuts well, but something about it doesn’t feel good. It feels a bit empty? I’ll give it a few more tries before making decisions.
Black Watch++;
walden@sub.wetshaving.social 1 week ago
I’m surprised you had to make the post again… I thought I fixed it yesterday. Did a test post and everything!
djundjila@sub.wetshaving.social 1 week ago
No worries!
Do we have logs of the failure? Something we can use to debug the issue?
walden@sub.wetshaving.social 1 week ago
I’ve narrowed it down to me compulsively updating things… I’ll click to update the schedule stack, and there won’t be an update for the scheduling stuff, but it’ll update redis. Without fail, updating redis gives problems afterwards.
I changed the stack now (as of yesterday) to use a fixed versio of redis, so when I compulsively look for an update, redis won’t change.
To fix it, I just delete the local folders/databases/etc. (leaving the folder with the scheduled events) and start from scratch. I did that yesterday and a test post worked. This time I’ll add in a step of logging out and recreating the jobs from scratch. There are only two jobs so it’s easy.
As far as logs go, there isn’t anything unusual from 00:05Z. The logs are empty going back further than that… probably some sort of log setting I should fix to make it go further back.