Getting undefined in my river feed

[Skinny On Sports]

Setup:  River5 install on Digital Ocean Node.js droplet, fresh installed April 2019

I've been getting some of the feeds showing up as "undefined" in my rivers.

It seems to self-correct after the feeds get updated.

I have been unable to reproduce this reliably but it happens ~ once/week currently.  It was more frequent before I started a new Droplet in April

Attached is a screenshot of what I see:

I'd prefer not to post publicly the link to the river here since it's a personal domain name.

Thanks for any suggestions.  I know River6 is coming along so this probably isn't a huge priority for anyone right now.  But it has been suggested that I should post the error publicly to see if anyone has any ideas.

Sorry I don't have any more details / reproducing steps.

[Skinny On Sports]

It's doing it right now on multiple rivers I run off the same installation:

Here is a link to one of the rivers:  http://www.skinnyonsports.com/strength/

Thanks.

[Dave Winer]

I did a little digging and found your river -- 

http://www.skinnyonsports.com/rivers2/strength2.js

The feeds in question, in the river, don't have titles. 

Also looking at the actual feeds they do appear to have titles.

Dave

--
Repo: https://github.com/scripting/river5
---
You received this message because you are subscribed to the Google Groups "river5" group.
To unsubscribe from this group and stop receiving emails from it, send an email to river5+un...@googlegroups.com.
To post to this group, send email to riv...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/river5/4cf108e2-1bf1-4427-8c22-52e2d039ab93%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Skinny On Sports]

Correct, and as I mentioned, it seems like after this happens, once these feeds update again, then the titles will re-appear.  So if is is a river with many frequently updated feeds, I may not even notice since it corrects itself quickly.

For example, this river has already "self-corrected" but at one point yesterday or the day before, many of the items in the river were also undefined.

http://www.skinnyonsports.com

Maybe it's one bad feed that knocks all the titles out?  Because this happens across multiple rivers at the same time.  (like the other one on my personal domain that I sent you via email).

Thanks.

On Saturday, June 15, 2019 at 11:16:58 AM UTC-7, Dave Winer wrote:

I did a little digging and found your river -- 

http://www.skinnyonsports.com/rivers2/strength2.js

The feeds in question, in the river, don't have titles. 

Also looking at the actual feeds they do appear to have titles.

Dave

On Sat, Jun 15, 2019 at 1:55 PM Skinny On Sports wrote:

It's doing it right now on multiple rivers I run off the same installation:

Here is a link to one of the rivers:  http://www.skinnyonsports.com/strength/

Thanks.

On Saturday, June 15, 2019 at 10:47:40 AM UTC-7, Skinny On Sports wrote:

Setup:  River5 install on Digital Ocean Node.js droplet, fresh installed April 2019

I've been getting some of the feeds showing up as "undefined" in my rivers.

It seems to self-correct after the feeds get updated.

I have been unable to reproduce this reliably but it happens ~ once/week currently.  It was more frequent before I started a new Droplet in April

Attached is a screenshot of what I see:

I'd prefer not to post publicly the link to the river here since it's a personal domain name.

Thanks for any suggestions.  I know River6 is coming along so this probably isn't a huge priority for anyone right now.  But it has been suggested that I should post the error publicly to see if anyone has any ideas.

Sorry I don't have any more details / reproducing steps.

--
Repo: https://github.com/scripting/river5
---
You received this message because you are subscribed to the Google Groups "river5" group.

To unsubscribe from this group and stop receiving emails from it, send an email to river5+unsubscribe@googlegroups.com.

[Skinny On Sports]

I'm posting this river file here (the one Dave linked to above, since in a day or two, it will be self-corrected and then anyone looking at it from the link may not be seeing the same thing.