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
On data-point-service we currently do not run the entity's outputType reducer before storing the new key, this means that if the outpuType was to fail, a key would be stored anyways causing the entry to be corrupted and served/stored for as long as the cache is configured.
Suggested solution:
Run outputType reducer right before attempting to store the entry key, if it fails the entry will not be executed and it will be handled as an error.
Environment:
data-point version: all
node version: all
npm version: all
The text was updated successfully, but these errors were encountered:
Problem description:
On
data-point-service
we currently do not run the entity'soutputType
reducer before storing the new key, this means that if theoutpuType
was to fail, a key would be stored anyways causing the entry to be corrupted and served/stored for as long as the cache is configured.Suggested solution:
Run
outputType
reducer right before attempting to store the entry key, if it fails the entry will not be executed and it will be handled as an error.Environment:
data-point
version: allnode
version: allnpm
version: allThe text was updated successfully, but these errors were encountered: