# File Delay in VSCode GUI on HPC

**URL:** <https://discourse.julialang.org/t/file-delay-in-vscode-gui-on-hpc/102730>\
**Category:** Tooling\
**Tags:** hpc, vscode\
**Created:** [August 11, 2023, 6:20pm UTC](https://discourse.julialang.org/t/file-delay-in-vscode-gui-on-hpc/102730 "2023-08-11T18:20:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![TI36XPro](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ti36xpro/32/33658_2.png) [@TI36XPro](https://discourse.julialang.org/u/TI36XPro)\
**Post date:** [August 11, 2023, 6:20pm UTC](https://discourse.julialang.org/t/file-delay-in-vscode-gui-on-hpc/102730/1 "2023-08-11T18:20:21Z")

</div>

Hello,

I am running Julia simulations on an HPC that uses slurm. I usually connect and set up my slurm run scripts using the [VSCode remove development](https://code.visualstudio.com/docs/remote/remote-overview) and all that works fine. I can inspect the stdout and stderr in case a simulation goes sideways.

One practical annoyance though is that there seems to be a delay between when the stdout and stderr files are generated and when they show up in VSCode file explorer (on the left side of the VSCode GUI). I can see them immediately from the terminal (via `ls`) but the VSCode GUI has a delay displaying them. I can force them to show up by opening them with vim but that’s not practical when I have tens of simulation runs.

They do eventually show up in the VSCode GUI but its usually minutes later.

Does anyone have any experience with this? Or ideas on how to remove the delay?

---

<div class="post-metadata">

**Author:** ![jmair](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jmair/32/35117_2.png) [@jmair](https://discourse.julialang.org/u/jmair)\
**Post date:** [August 11, 2023, 9:03pm UTC](https://discourse.julialang.org/t/file-delay-in-vscode-gui-on-hpc/102730/2 "2023-08-11T21:03:56Z")

</div>

Yes it’s a pretty typical experience. There’s a refresh button in the top right hand corner (i think) of the explorer tab that let’s you force a refresh, which may help.