Delay Agent, undefined method `payload' for nil:NilClass #3315
Comments
|
What's the URL to the RSS feed? |
|
If I can guess, the payload was empty. So, maybe the feed was unreachable? Or was malformed? |
|
I write to reopen this issue, because I ran again in the same error.
I can't get the "event in", should have been a RSS Agent output. Like this
This is an example of working payload {
"id": "https://www.rainews.it/video/2023/09/musk-apre-al-reclutamento-per-neuralink-chip-nel-cervello-volontari-db1285b5-d8dc-43ff-ab70-5100a957c326.html",
"url": "https://www.rainews.it/video/2023/09/musk-apre-al-reclutamento-per-neuralink-chip-nel-cervello-volontari-db1285b5-d8dc-43ff-ab70-5100a957c326.html",
"urls": [
"https://www.rainews.it/video/2023/09/musk-apre-al-reclutamento-per-neuralink-chip-nel-cervello-volontari-db1285b5-d8dc-43ff-ab70-5100a957c326.html"
],
"links": [
{
"href": "https://www.rainews.it/video/2023/09/musk-apre-al-reclutamento-per-neuralink-chip-nel-cervello-volontari-db1285b5-d8dc-43ff-ab70-5100a957c326.html"
}
],
"title": "Musk inizia il reclutamento per Neuralink: ai volontari sarà impiantato un chip nel cervello",
"description": "Il dispositivo, che registrerà e invierà i segnali cerebrali a un'applicazione, sarà inserito nell'area del cervello che controlla l'intenzione di muoversi",
"content": "Il dispositivo, che registrerà e invierà i segnali cerebrali a un'applicazione, sarà inserito nell'area del cervello che controlla l'intenzione di muoversi",
"image": "https://www.rainews.it/dl/img/2023/9/21/1695269994541_TZLOPRPRTRMADPBASEIMAGEXNEURALINKTRIAL.JPG",
"enclosure": null,
"authors": [
],
"categories": [
"Scienza e tecnologia",
"reclutamento per Neuralink",
"chip nel cervello",
"Stati Uniti",
"Neuralink",
"Elon Musk"
],
"date_published": "2023-09-21T04:14:00+00:00",
"last_updated": "2023-09-21T04:14:00+00:00"
} |
tassoman
changed the title
|
I just updated my installation on Heroku from a95c5cc to he newest commit 2d5fcaf and started seeing the same log messages regarding the Delay Agent. This error seems to occur when the agent's memory contains IDs of events that don't exist any more. After manually deleting the memory of the affected agent it started working normally again. Previously such IDs were simply ignored by the Delay Agent and didn't cause any issues. It would be great if that behaviour could be restored because currently any incoming events may be emitted 5 times before the job goes to "failed" status. |
|
OK, so I did a little bit more testing. The non-existent events weren't the problem after all. It actually looks like this error always occurs when the number of events in memory is lower than |
|
now I also struggle in such problem. Is there anyone who can fix this bug of Delay agent? |
|
Same here. Is there any way to work around? |
I have no clue what's happening, but RSS Agent dies throwing exception.
I'm running the latest docker image.
The text was updated successfully, but these errors were encountered: