feed.tasks parse_feed not working as expected

RESOLVED FIXED

Status

RESOLVED FIXED
7 years ago
4 years ago

People

(Reporter: boozeniges, Assigned: boozeniges)

Tracking

Details

(Assignee)

Description

7 years ago
I've had a bit of a look into matter and found:

I'm guessing that there is a problem in-bewteen lines 83 to 96 in /apps/feeds/tasks - possibly more specifically line 85 where it checks if an entry with the current checksum already exists; seems that they generally do.
(Assignee)

Updated

7 years ago
Assignee: nobody → paul
(Assignee)

Updated

7 years ago
Blocks: 668102
(Assignee)

Updated

7 years ago
No longer blocks: 668102

Comment 1

7 years ago
Hey there,

Friendly ping to make sure this goes out with 668102 today.

Cheers!
Ben
(In reply to comment #1) 
> Friendly ping to make sure this goes out with 668102 today.

Got a fix ready, will be deploying later on today.

Comment 3

7 years ago
We seem to have reverted back to 1 post getting parsed. Can we look into it?

Cheers,
Ben
(Assignee)

Updated

7 years ago
Assignee: paul → ross
(Assignee)

Comment 4

7 years ago
Fixed this, will commit in the morning.
(Assignee)

Comment 5

7 years ago
Heya guys,

I've got the code I updated onto the live site and currently it's looking good. We have the 4 most up to date feeds.

Can we all check tomorrow morning to ensure that it's not deleted itself again and then either Dan or Ben close this.

Cheers!
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED

Comment 6

7 years ago
Works. I don't want to show my noob stripes by confessing that I don't know how to close...

Do I need to be QA contact?

Thanks!
(Assignee)

Comment 7

7 years ago
We can probably leave it like this for now. If it starts playing up again re-open this bug.

Glad to hear that it is actually working though :)
Product: Websites → Websites Graveyard
You need to log in before you can comment on or make changes to this bug.