Closed MecuSorin closed 2 years ago
Do you have the error on https://fable.io/repl2/ or https://fable.io/repl/ or both?
This is a long bug that we are experimenting from time to time since we tried to add worker to cache resources and it didn't goes well... We have a very hard time understanding the source of the problem and replicate it...
Sorry for the annoyance
I was using the links from the twitter thread https://twitter.com/alfonsogcnunez/status/1428597656385769479
Ok, so this is on https://fable.io/repl/ which we tough to have fixed. 😅
@alfonsogarciacaro Any new ideas? ^^
There is no way to invalidate that cache? To timestamp it at the last action in site and if is older than 5 days to just wipe it out?
Well, in theory we should not have the cache system anymore.
It was introduce in this PR https://github.com/fable-compiler/repl/pull/17/files but we removed the service-worker
in a later version because it was causing problem.
Can you please check if you have a service-worker installed when navigating to https://fable.io/repl/
For example, me I don't:
If you use Firefox here are the instruction on how to find it: https://developer.mozilla.org/en-US/docs/Tools/Application/Service_workers
If you use another browser I found the instruction by searching "see service worker firefox" on google.
Found one just in Edge:
Scope: https://fable.io/repl/
Registration ID: 15 (unregistered)
Navigation preload enabled: false
Navigation preload header length: 4
Active worker:
Installation Status: ACTIVATED
Running Status: RUNNING
Fetch handler existence: EXISTS
Script: https://fable.io/repl/service-worker.js
Version ID: 41
Renderer process ID: 10784
Renderer thread ID: 2
DevTools agent route ID: 6
Client:
ID: 647c1488-8771-4efa-8a9f-37bd410b566f
URL: https://fable.io/repl/#?code=PYBwpgdgBAygngZwC5gLYFgBQpJQGICGARgDZgB0AwsAE5hY7SGkXV3kBSCAkhCjaAbhoAIQEB3BGBpDcY4JOnkAKnHAJZ0AKIlUASwQALLFgD0pqNQAmYKEmBQCVgiCRQOMO2hAkCKBHYOeADEUABmtKh+KFZQyDR6EADmGpiowFYArmRQyt6+KFAAvFhQdmq2ygRJADwA5MoAfMVQNmRJfrbAYXFINAgAXL0JyQDaALpQAFRQozUACgQ0BKgAgjTLcI2TSylDwEQAVhNQALTNDSaYZWRuAMZ0nVAAFEjVQ1W1DY0AlC9hqCQQzwkWixDIMD6iSSfyGDWKpTKUFuwwCRVyYAAHkhyAAlMBJbJLLSYkB0BAIPTACAIPEErHPAACACIAN4AHSsAGoAL7Mn7kGA+PRIZ4AnEgmhRJA-RE3MBuXZo8KA8gAcQV60JqEgSAQz1l1yRbyS5F4ADdgABrMDPeIIAA0jhoKUNZgsABkRVAiIkrNDUuksjkvW4SkakBUoAAJJCoEh5VA+J7oxL8MIEO62SCxcxQea+LOGYAkGwyTCIlGGOMkD75Toqao1WPxxPJlDNVNJ2hIACyaCI0igzOrSBAg3MmQgICtpruwFQphIItO1fjAH4g9kwMzKwqoHQIGWXkCYzW2wUwH9nmBazHlL2PTo0LqfkMp96uyAe-3UIOaMOo7jgMk7TrO5Dzouy5IKuNabhk267hWmB5jo+hGFA4gioYUChlgW45PMAhJMsqAIkaKJYUghihi8ehWEM8TQteZLACRKxDERbGkfUuxOnUQa3vxqAIEkTqhuQLYJvWHZvvmxE8XUfFQAJGRCSpIlibhIqSeeMlgJ2cpIiit4tPIig0OQAAiC7kFYwB3JkOp8OQSQKs+zlICIcDcFYzz0W6RpIsi+5SEgkJPIJJCtAYIB+HcOHhsFyUhW4KBJpe+IINkYbydxKzkOaehgOIUCsexZFRTFCBxUgCVGSlEmHse6XtmAWU5VAt5XClXEVeQVGGDACoRYUYWjbY5WkVcea8CKegEMuABetjUat+mOEejhQIYt7gOWVY1i0F4Ng8YBPBJa4kFckbgFAWjmrqVQuvug2Ijqf5DtRBjkAAaotmS2OiryGAYUADOuzTRg+Hq8CAmRIB5r6FQD9DIXmqwgCAWC3bYvZqdFSVIqyUD-SQgPg8M0JQDyN1Rr2onkcFAA+liGAQyRgGTFPdFTyRXCiiTegaLQk9zQPDgA6rQpbMjTTqUKgVjkBA1Jo1gKKZCAziFM8mkDAzMIvFFBsE38RNlNKCVQJpmHYUZrOUOznPi1AEAla75wNcTNsE3b1Gk6jLTu+Irs8grSsq2rAv7kVJW+201W1dbRNXVAAAkzJZ1gNT+uaUB3L4FJFMyUSJKc858AQiTSMyjSIjUiTw-cRcICXTcI0hwXmqjRSslFf2o7TQVQIyNpwFrfdhFOLxgOaQwPa+Zz1yPZRz+QbwvTi4ve8zzROxzbk76vUB70n8WGDyK8NzVHONNGt4kA4-cE4P5NgDyACENSmLfEArz-POK8s5ISwH1Ui5BUBWnASsKAQs3Bax1rYOO4gsBnxgagAa2FaLMlvOhQwpwXAgCQughSBUaBTiwEAA&html=DwCwLgtgNgfAUHUBTAhgE3gAm54ElgqbhgAOAtEgI4CuAlgG4C8A5AMID2AdmEj+QBUAnqSQtMAY268erXgA8wAenDQA3JJAoATgGcCTGmABm5ABwt4wFagwJgAIw5ohkqCl26mAIhSkKUjwodFxI2t5YOMBojJh0aD5IUBB0uiDkfqQR1jEMVkpOLvCIKpCwcEA&css=BYFwtgNgNAsAUAIwPYBMCeACA3vDeMBmSAdiALQDOAlgF4CmAXBgIwBsADgB4Dc8AvvHgA6MAEMqxMgGMSIccToAnbLnwoqFdhFFomBCHR6q8AdyooQwJswAMNgKS84+DMDpUA5qGt3HxjABWAK4UIFQEaNKydKRMUjEgSk4uohCeklSJYBRxCUn++oZk6op0UmEkcUgQQWDETgJwwhLsQSAqzvjsoijqxB5MQgBMAKylYMn4RKSUtIwsHEadpuaWTKM2XJN4YooeEmTIICBIYNbjDfBAA
Log:
Hum, you should delete it because we don't use it anymore.
But then it doesn't explain why the other browsers broke. Next time, it happens could you please take a look at the console and see what error is reported.
Because we don't know if this is a cache problem or something else then.
@MecuSorin If you didn't visit the repl for a while, it may have happened the service worker was still active in your browser. We removed it some months ago because of these issues. Hopefully the next time we update the repl you won't have the same issue, could you please report if you see it again?
Closing this as we removed the service worker some time ago. Please feel free to reopen if you still have problems. Thanks!
I was navigating to the site using this link . The solution for me was to delete the Cache Storage data for Fable.io