GeezerVison

Hi @offbyone! Thanks for picking up the torch here!

Is this in a state that generates usable output, or does it still have some ways to go before being (manually) testable?

It generates useful input on first run, I'm still having some issues with caching. I expect to have time to dig into that this week.

Thank you @offbyone for the great work.
I'm not super well-versed with infra/devops kind of thing, but wondering if this is something we can like have deploy preview build kind of thing?

I'm also wishing we could automate the check for valid rss using GH actions or as part of CI. Would that be possible to add? Should I open an issue about it?

Opening the issue can't hurt; worst-case, it won't happen, but if it makes sense to do, we can.

Thanks. I've opened #579 and #580

Okay, I'd call this ready to review.

I don't know much about how it's currently running or deployed, although I can make some inferences based on the current code. I'm happy to sysadmin that shit if the owners of the host want me to.

Merging this into a new py3 branch to temporarily deploy it alongside the current deployment.

https://planetpython.org/3/ is now running and updating along side the main instance.

The initial result is a little confusing, I guess we'll see how it behaves over time?

No, I think I see what's happening there.

There are two things that I'll want to address, one is full text feeds and the other is something that's possibly stateful. The DB has a field - hidden -- that it seems to infer from something about how "new" the feed is. Since I don't have the original DB, it's possible there are feeds not showing up in the new one that might otherwise be there. If you can get me the contents of /srv/planetpython.org/ and /srv/cache from the old runner, I can see about getting things consistent.

Oh, man... yeah, there are some bugs in that output now that I can see it beside the current planet. I'll put together some fixes by the weekend (evenings are a bit slammed for me this week)

Archives of current state:

https://planetpython.org/cache-1728569965.tgz
https://planetpython.org/planetpython.org-1728569990.tgz

Can you tell me which version of python (and, possibly, OS version and dbm library version) are involved in generating that? I hope it won't matter, but I might need to spin up a replica of the original to use those caches.

@offbyone
Python3 is 3.12.2
Ubuntu 18.04.6 (behind due to Python2 impl)

@offbyone 3.12.2

That's the preview deploy, the state is from the original.

Ah, @offbyone do you want the cache/output for the new version or the original?

Honestly, "both is good" is even better. That way I can apples-to-apples it.

for the new thing: https://planetpython.org/cache3-1728570557.tgz

$ python3.12 
Python 3.12.2 (main, Oct 10 2024, 13:10:02) [GCC 7.5.0] on linux
Type "help", "copyright", "credits" or "license" for more information.

Okay, so I have some good news and some bad news.

The good news is that I can definitely get the ordering issues sorted.

The bad news is that as far as I can tell, I can't use the cache from the v2 version with v3, to retain the "hidden" state from the old feed cache. I'm looking into seeing how I can get that status, because it would radically change the feed if we lose it.

I'm going to see if I can figure that one out somehow. I suspect I'm missing something with the weird ways dbm loads files.