Deleting a comment on a niche approval page can cause the broken robot of doom

Service: Narrative

Deleting a comment on a niche approval page can cause the broken robot of doom

Service: Narrative

Trying to access that niche's approval page after a comment has been deleted, or even trying to access the page of listed approvals on which that approval sits... brings the robot of doom.

This problem tends to resolve itself after a while: I don't know if it is because the @Narrative Network Team are fixing the issue as it arises, or whether some aspect of the system periodically corrects the condition that causes the error...

Either way, I thought I would make sure that the Team is aware that deleting comments is causing problems.

Original Post

Activity Stream

Addendum - it is Saturday evening so I doubt anyone will attend to this until Monday, but just thought I'd point out the niche approval that is currently suffering from this problem: it is The Beatles.  And because that approval currently lists on page 3 of niche approvals, that page is completely inaccessible right now, at least for me.

So a pretty disruptive problem since anyone trying to access the approvals on that entire page of approvals, will be whacked with the robot of doom.

Another observation.  The robot of doom kindly proposes that we submit a support ticket, and I can tell from the URL it points us to that it will allow you to track error data internally and correlate it with the comments of what the user was doing when the error occurred.  Right now, clicking that link leads to a "Uh oh, there's nothing there." page.

The link I used when I experienced this was:

https://alpha.narrative.org/ge...4574-khgxj%3C%2Fp%3E

Hi @Malkazoid,

Thanks for the report! We are indeed aware of this issue (and other similar errors related to the same root cause). It's a problem we've been actively pursuing that is proving to be rather tricky to solve. We'll definitely use your report to help further trying diagnose the issue, so thank you for reporting and providing all of the details 

Have a good weekend,

Brian

Brian Lenz posted:

Hi @Malkazoid,

Thanks for the report! We are indeed aware of this issue (and other similar errors related to the same root cause). It's a problem we've been actively pursuing that is proving to be rather tricky to solve. We'll definitely use your report to help further trying diagnose the issue, so thank you for reporting and providing all of the details 

Have a good weekend,

Brian

You too Brian - and good luck!

Add Reply

×
×
×
×