[ENG-8048] Remove caching to avoid incorrect results for ascendants #11169
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose
When user adds a component to a node that has addons with files and registers it, the node doesn't have any archived files. It happens because the child nodes are the first ones to be registered and if a child doesn't have any addons, this empty list would be saved in
request.gv_addons
attribute that is reused for all other parents and children to avoid making redundant requests to GV. However each child and parent may have its own collection of addons.Changes
Removed caching
QA Notes
Would be nice to test what happens when a child node has addons with files, but its parent hasn't. Will the parent inherit archived addons files or not?
Ticket
https://openscience.atlassian.net/browse/ENG-8048?atlOrigin=eyJpIjoiMzk1Yjc2MTIyNzQzNDVmYzg4OGE1ODViYjM1NGEyMWIiLCJwIjoiaiJ9