Plunks Fail to Fetch Files after Some Inactivity (Status Code '500')

[boghyon]

I often observe single page applications failing to fetch resources on-demand after some inactivity.

URL

• https://embed.plnkr.co/F3t6gI8TPUZwCOnA?show=preview
• https://next.plnkr.co/edit/F3t6gI8TPUZwCOnA

Steps to reproduce the problem

1. Open one of the above plunks (preferably the first one)
2. When the preview is loaded, wait for about a minute.
3. Click on one of the items within the app, e.g: Lufthansa               EUR > The app tries to show some more content but fails to do so.
4. Check the network tab in the dev tools

Result

Error: resource demo/view/Detail.view.xml could not be loaded from ./view/Detail.view.xml. Check for 'file not found' or parse errors.

The fetch fails with 500 even though the file exists in the project folder and doesn't contain any invalid syntax that could result in parse errors.

Workarounds

• Interact with the app as soon as possible. In the above case, reload the plunk and click on the Lufthansa item immediately. The app successfully retrieves the requested view and displays it on the right side.
• Use one of the links (same plunk, different links).
  • https://plnkr.co/edit/F3t6gI8TPUZwCOnA?p=preview
  • https://next.plnkr.co/plunk/F3t6gI8TPUZwCOnA No matter how long you wait, files can be retrieved anytime.

[boghyon]

@ggoodman Please, let me know if you need more information. Otherwise, it would be nice if this could be fixed soon..

[ggoodman]

Interesting. Sounds like the preview assets might be dropping from the cache too quickly. Can you confirm that the issue is not reproduced on https://run.plnkr.co/plunks/F3t6gI8TPUZwCOnA/?

[boghyon]

Thank you for the reply. So far, I couldn't reproduce it on https://run.plnkr.co/plunks/F3t6gI8TPUZwCOnA/.