Repository: vscode
Issue: Changing lettercase of directory causes unbound breakpoints as VSCode does not refresh path
Labels: bug,debug

Type: <b>Bug</b>

I have created a folder named "TimeSeriesData" and placed a .tsx file in it. I then later renamed it (in VSCode) "TimeseriesData" and placed a breakpoint in the .tsx file within. When I go to the debugger panel, under Breakpoints, I see the path to the breakpoint reflects the old "TimeSeriesData" folder and not the rename with a different lettercase, causing breakpoints to be unbound. 

Things I have tried to fix it:
- Deleting the folder and then created a brand new folder with the correct name "TimeseriesData" and placed a new .tsx file within (I did all these steps from VSCode). If I place a breakpoint, it still references the prior path with "TimeSeriesData" as the folder name. 
- Refreshing the explorer
- Quitting and restarting VSCode
- Running VSCode without any extensions
- Checking in Finder that the folder is correctly named/cased
- Checking that no import statements are using the incorrectly-cased folder name
- Originally this was happening in a NextJS project, so I tried it in a python project instead. I was able to reproduce the same problem

Steps to reproduce:
1) Open VSCode
2) Create a folder like `MyNewFolder`
3) Create some file within to set a breakpoint on
4) Set a breakpoint
5) Navigate to the debugger panel to look at the path and confirm it says it what you expect: `MyNewFolder`
6) Rename the folder `mynewfolder`
7) Set a breakpoint in your test file again
8) Navigate to the debugger panel and look at the path reflected in the Breakpoints section. Assuming this problem is reproducible by you, it will say `MyNewFolder` instead of `mynewfolder`.

**This solution did work, but it seems very roundabout:**
1) From Finder, move the problem folder elsewhere on your filesystem
3) Quit VSCode
4) Restart VSCode
5) Drag the problem folder from Finder back into VSCode
6) Set a breakpoint in your file and the correct path should be reflected in the debugger panel

VS Code version: Code 1.88.1 (Universal) (e170252f762678dec6ca2cc69aba1570769a5d39, 2024-04-10T17:42:52.765Z)
OS version: Darwin arm64 23.4.0
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Apple M2 (8 x 24)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled|
|Load (avg)|2, 2, 3|
|Memory (System)|16.00GB (1.52GB free)|
|Process Argv|--crash-reporter-id ed1ae916-3b9e-4a10-8233-59defebd71d7|
|Screen Reader|no|
|VM|0%|
</details>Extensions: none<details>
<summary>A/B Experiments</summary>

```
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscoreces:30445986
vscod805cf:30301675
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
2i9eh265:30646982
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
h48ei257:31000450
pythontbext0:30879054
accentitlementsc:30995553
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
d34g3935:30971562
fegfb526:30981948
bg6jg535:30979843
ccp2r3:30993541
dsvsc020:30976470
pythonait:31006305
jchc7451:30973076
gee8j676:31009558
dsvsc021:30996838
01bff139:31013167
pythoncenvpt:31022790

```

</details>

<!-- generated by issue reporter -->