You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Storage isn't returning the last version of the texts if the texts happens to have been added to the cache prior to the update.
The issue is noticable in altinn.studio during deploy, if a developer performs two (or more) deploys within 1 hour.
Steps To Reproduce
Create a new App in altinn.studio
Deploy the App to any environment
Make any change to texts
Deploy the App to the same environment. This must be done after no more than 1 hour. That is the lifetime of the cache.
This results in an exception in studio
In Storage we should find a few 409 responses and maybe some "row already exists" errors
Additional Information
The issue here occure because Storage is caching a sort of dummy/empty text representation when there are no texts matching the input criterias. We can keep returning NotFound for an entire hour even though the texts have been added in the mean time.
The text was updated successfully, but these errors were encountered:
SandGrainOne
changed the title
Storage needs to invalidate Text Cache on POST or PUT requests.
Reposotory classes should NOT have caching. It must be possible to access data directly.
Jan 22, 2024
SandGrainOne
changed the title
Reposotory classes should NOT have caching. It must be possible to access data directly.
Reposotory classes should NOT have caching. It must be possible to access uncached data
Jan 22, 2024
Description of the bug
Storage isn't returning the last version of the texts if the texts happens to have been added to the cache prior to the update.
The issue is noticable in altinn.studio during deploy, if a developer performs two (or more) deploys within 1 hour.
Steps To Reproduce
Additional Information
The issue here occure because Storage is caching a sort of dummy/empty text representation when there are no texts matching the input criterias. We can keep returning NotFound for an entire hour even though the texts have been added in the mean time.
The text was updated successfully, but these errors were encountered: