The message broker server that backs the feed system is currently non-responsive, and I'm waiting on the server host to perform an actual, physical intervention.
I'm not sure when things will be fixed, but things may be down for a day or two.
Ok, normal feeds should be resuming now. The issue should be resolved.
For the technically inclined, the problems resulted from the combination of a bug in RabbitMQ (the message brokeer the feeds use), and an issue with the linux tool
mountall. The RabbitMQ issue (specifically the fact that the "Shovel" plugin caused it to get stuck on exiting) caused me to simply decide to reboot the server. The issue with
mountall then caused the server to not start up properly after reboot (it was stuck waiting for a partition that doesn't exist to mount).
I've removed the shovel plugin entirely, and added a work-around to
fstab to prevent the reboot blocker issue, and it shouldn't reoccur.
I need to do some large schema changes on the backend of the feed feeder system, which requires taking it offline for a bit periodically PostgreSQL churns.
Unfortunately, the size of the tables in the database make this a many hour, or possibly multi-day process, so things may be shut down for a little while.
Ok, database updates are done, normal service should resume.
Some of the RSS feeds have been getting stuck this week, due to a combination of a software bug and the fact that I've been away for work and not had time to do any maintenance.
I've been restarting the feed scraper manually when I can, but the issue will probably persist until I have a chance to fix it properly this weekend, when I get back from my trip.
EDIT: I think I've fixed it using SSH.
EDIT EDIT: Ok, it was a priority inversion in the page fetch queue. It looks to be working correctly now
Logged in users can now edit releases.
This is done by right-clicking on the right hand columns of the release row (vol/chap/extra/group columns). Then, just select the "Edit Release" option on the right-click menu.
The custom right-click dialog also includes some extra information on the release, such as when it was added, who added the release, and whether the release is included in the algorithm for determining what the "newest" chapter is (this is generally used to exclude chapters that are miss-tagged in the source, and as such will be re-added by the feed parsing system if simply deleted).
Questions and comments are welcome on the forum!
A number of minor, but nice new additions to the site are going to be rolled out over the next few days. Let me know what you think on the forums!