mistercrunch commented on issue #28259: URL: https://github.com/apache/superset/issues/28259#issuecomment-2084130662
This is pointing towards a backend/frontend being out of sync. The backend is made aware of a manifest at /static/assets/manifest.json , and there many reasons why this can/could get out of sync (though it's not common AFAIK). But normally if you're on a clean `npm run build` where manifest is defined and published, and a fresh backend that read the latest manifest, you should be fine. I'm unclear what happens if the client (browser is out of sync) as it may ask for an old/expired asset (?). I'm guessing at Preset we may persist the older build chunks on the CDN or have some other way to tell the client to refresh its manifest In your cast does a client force-refresh fix the issue? Could you have zombie pods serving an older version of the app? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
