Fix: Resource: Make set_path() resilient to stale cache entries #112328
      
        
          +17
        
        
          −2
        
        
          
        
      
    
  
  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.
  
    
  
    
Fixes #112164
Fixes an editor error when a file moved outside the editor is moved back inside the editor. Resource::set_path() is made tolerant of harmless cache collisions so the reassignment doesn’t fail with:
ERROR: Another resource is loaded from path 'res://1.gd' (possible cyclic resource inclusion).What changed:
External moves can leave a stale ResourceCache entry for the old path. Reassigning the path then collides with that stale entry. The above rules safely evict stale entries (and, in editor builds, resolve transient references) to avoid false errors.