search

plnkr / feedback

Feedback on Plunker
19 stars 11 forks source link

Cannot use Fetch API after 30 seconds #561

Closed Egauon closed 1 year ago

Egauon commented 2 years ago

The Fetch API cannot be used in my Plunker Project 30 seconds after the project preview has started. I can reload the preview and it works fine... again until 30 seconds later.

Here is a Plunk that describes the issue:

https://plnkr.co/plunk/OIHKMRQHqbzZYYE5

The Second by Second button calls the fetch API every .2 seconds and the 30 Second one delays the fetch API until the 30 second mark.

I included both to show that it's not a call quantity issue, seemingly purely time based???

On Google Chrome Windows 10

<<<<<<< EDIT >>>>>>>>

Okay okay so apparently it is only an issue in the editor?????

I previewed the Plunk from a public standpoint and it works fine

Maybe that helps narrow the issue?

Also the Fetch API error code is 500 if that helps as well

ggoodman commented 2 years ago

Hi, what's happening here is that in-editor previews store their data in an ephemeral storage as a cost-saving measure. Perhaps the TTL or size of this storage is out of tune with current usage patterns.

Unlike previews, saved Plunks are backed by durable storage.

Egauon commented 2 years ago

So I'm assuming then there's no way to 'fix' it as it's purposeful?

ggoodman commented 2 years ago

There is no fix that is available to users but from the platform perspective I'll take a look later tonight to see what can be done.

guest271314 commented 1 year ago

Works as expected on Chromium 113 on Linux.

ggoodman commented 1 year ago

Hello @guest271314, that should indeed be the case. I bumped the TTL this year, as noted in https://github.com/plnkr/feedback/issues/261#issuecomment-1409617626.