PressForward Feed Reader hung up on TLC feed; won't retrieve other feed items
The PF Feed reader on the pftest.commons.gc.cuny.edu site seems to be hanging up on the TLC site and won't move on to retrieve items from feeds that have been added to the list of "subscribed feeds." From the user perspective, when I go to Dashboard -> PressForward -> Tools, and select the Retrieval Status tab, the status seems to hang at the TLC RSS feed item 3 out of 4. I've added other feeds, deleted feeds, and tried to interrupt the process, but nothing seems to have worked. Screenshot attached.
#2 Updated by Boone Gorges 7 months ago
- Status changed from New to In Progress
Thanks for the report and the screenshots, Lisa. It's hard to pin down what might be happening asynchronously, so I've enabled PressForward's debug log tools. This will allow us to gather some information over the next day or two, which should help collect info about what's happening. I'll check back tomorrow to see if there's more info available.
#8 Updated by Boone Gorges 6 months ago
I was seeing lots of instances of this fatal in the error logs, so I've applied the fix from the PressForward repo as a hotfix in production https://github.com/cuny-academic-commons/cac/commit/e084a794a764b141988f4243e1a456b14e18f3d4 Let's see if this helps clear things up.
#9 Updated by Lisa Rhody 6 months ago
Thanks, Boone and Ray. We have a couple projects waiting on the fix, and I'm glad to hear that there's a short term solution! I think Aram updated the issue #1022 on GitHub here: https://github.com/PressForward/pressforward/issues/1022#issuecomment-437371935. I'm not able to test the changes without updating the PF plugin on the commons. Do you all have a work around for that? thanks!
#14 Updated by Boone Gorges 6 months ago
- Status changed from In Progress to Resolved
Thanks, Paul. Not sure what I can do about the slowness of fetching. Latency is likely due to the slowness of fetching feeds, which is why it happens in the background - so you shouldn't notice the slowness in your everyday work.
As the immediate problem here appears to be solved, I'm going to close the ticket. Please report back if there are more reproducible problems.