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
{{ message }}
Repository navigation
Stale errors for a few minutes after switching branches聽#44066
Clone and checkout https://github.com/unsplash/unsplash-web/tree/typescript-stale-errors-a, branch typescript-stale-errors-a. This is a private repository but I believe some members of the TS team already have access from debugging previous issues. If you don't have access, please send me your email address so I can provide access (TS team members only).
Run yarn
Open VS Code and navigate to app/routes/Users/components/UserStatsSubRoute/UserStatsSubRoute.tsx
Wait for VS Code to finish initialising TS (no errors)
Oliver Joseph Ash (@OliverJAsh) The branch is no longer available. Are you still seeing the issue. If yes can you please provide the steps to repro
Thanks
While investigating this the root cause of this is that we poll 32 files at a time every 2 seconds. Since your project has 2000+ files being watched it takes a while for it to show up. At this point this looks working as intended.
Is there anything that could be done to improve the user experience? It seems quite extreme to wait this long for TS to fully update. To workaround this I have to restart the TS server very often.
Note that if I add these VS Code settings the issue disappears, i.e. there are no stale errors when I switch branch:
I am trying to fix some of the issues with using file system watching since they are not reliable. After fix for #47466 , we could consider that but after we have tried it out. Eg. linux has some limit on number of file system watchers it can create.. Then there is non reliability because of watching inode.. though fix for #47466 will make it better but we will have to see how the experience is with that one.
Sheetal Nandi (@sheetalkamat) I just tested this again using TS 4.8 which includes #48997, the fix for #47466 which is mentioned above. Unfortunately the issue persists鈥攊t still takes 2 minutes for the stale errors to disappear. Do you think we could re-open this issue and discuss ways to improve the user experience?
As I mentioned above, if I add these VS Code settings the issue disappears, i.e. there are no stale errors when I switch branch. Do you think we could consider making these settings the default now that #47466 has been addresssed?
4.8 fix was more towards linux which was one of the blocker to make useFsEvents default.
useFsEvents is default now with #50366 and is in nightly. Daniel Rosenwasser (@DanielRosenwasser) is looking to see if we could get this as experiment in vscode for 4.8 users but it may take some time to get everything together or not work out at all. Mean time nightly will give you that experience.
Activity
sheetalkamat commentedon May 3, 2022
Oliver Joseph Ash (@OliverJAsh) The branch is no longer available. Are you still seeing the issue. If yes can you please provide the steps to repro
Thanks
5 remaining items
sheetalkamat commentedon May 4, 2022
Oliver Joseph Ash (@OliverJAsh) thank you for the repro.
While investigating this the root cause of this is that we poll 32 files at a time every 2 seconds. Since your project has 2000+ files being watched it takes a while for it to show up. At this point this looks working as intended.
OliverJAsh commentedon May 4, 2022
Is there anything that could be done to improve the user experience? It seems quite extreme to wait this long for TS to fully update. To workaround this I have to restart the TS server very often.
Note that if I add these VS Code settings the issue disappears, i.e. there are no stale errors when I switch branch:
Perhaps this should be the default?
sheetalkamat commentedon May 5, 2022
I am trying to fix some of the issues with using file system watching since they are not reliable. After fix for #47466 , we could consider that but after we have tried it out. Eg. linux has some limit on number of file system watchers it can create.. Then there is non reliability because of watching inode.. though fix for #47466 will make it better but we will have to see how the experience is with that one.
OliverJAsh commentedon May 5, 2022
In that case should we keep this issue open to track the user experience issue?
typescript-bot commentedon May 7, 2022
This issue has been marked 'Working as Intended' and has seen no recent activity. It has been automatically closed for house-keeping purposes.
OliverJAsh commentedon May 25, 2022
I understand this is working as intended but I think there is still a usability issue here. Can we re-open this to track that?
OliverJAsh commentedon Sep 9, 2022
Sheetal Nandi (@sheetalkamat) I just tested this again using TS 4.8 which includes #48997, the fix for #47466 which is mentioned above. Unfortunately the issue persists鈥攊t still takes 2 minutes for the stale errors to disappear. Do you think we could re-open this issue and discuss ways to improve the user experience?
As I mentioned above, if I add these VS Code settings the issue disappears, i.e. there are no stale errors when I switch branch. Do you think we could consider making these settings the default now that #47466 has been addresssed?
Let me know if you need an updated repro that uses TS 4.8.
sheetalkamat commentedon Sep 9, 2022
4.8 fix was more towards linux which was one of the blocker to make
useFsEventsdefault.useFsEventsis default now with #50366 and is in nightly.Daniel Rosenwasser (@DanielRosenwasser) is looking to see if we could get this as experiment in vscode for 4.8 users but it may take some time to get everything together or not work out at all. Mean time nightly will give you that experience.