venkatamandavilli-code commented on issue #39951: URL: https://github.com/apache/superset/issues/39951#issuecomment-4471319631
Thanks for reporting this issue and sharing the details. This looks like it may be related to how Superset is handling state or metadata refresh after the update is applied. One thing that might help is checking whether the backend response already contains the expected updated value, but the UI is still rendering an older cached version. If that is the case, the issue may be more on the frontend state refresh side than the actual update operation. It may also be useful to verify: * whether the issue happens after a hard refresh * whether it is reproducible in a different browser/session * whether the API response returns the expected updated data * whether any cached metadata is being reused after the save action A small regression test around the save/update flow could help prevent similar behavior in future releases. Thanks again for documenting the issue clearly. -- 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]
