Network errors on OEIS sequences lead to bad sequences being cached

[katestange]

As far as I can tell, sequence A002487 is returning this.seq.first as +Infinity which is probably not good.

https://oeis.org/A002487

[gwhitney]

As with #409, this sequence is seeming fine here. Changing the title of the bug to reflect that it is likely a caching error.

[katestange]

Ok, I opened a different browser and cleared all browser history for all time, and then this sequence worked. But A003462 doesn't. Even with totally cleared browser history. Am I going nuts?

[katestange]

Also A000225 and A007583 fail.

But these new-to-me ones work: A115067, A000326, A003463

This is after repeatedly clearing all browser history and restarting frontscope.

The error is as reported: seq.first is Infinity and seq.last is NaN

[gwhitney]

Did you pull my latest PR? It supposedly has a fix, which is to say I made a change I think will help.Let me know if it does or does not.

[katestange]

Tried -- same result.

[gwhitney]

OK, on new browser with cleared cache and my latest PR, when you get a sequence mess up like this, open a new tab and try the same sequence and let me know if the same sequence fails twice in a row in different tabs. Thanks!

[katestange]

Yes, still happening in multiple tabs (with cleared cache, reloaded browser and latest PR).

[katestange]

FWIW, it's not working at the old scope at numberscope.colorado.edu either.

[katestange]

Is it working for you?!

[katestange]

For example, go to numberscope.colorado.edu, add OEIS sequence A000225 and then try Differences -- it reports too few terms. Which is not the case on the OEIS. Or try ModFill, it pops up an error.