The git sidepanel does not refresh on file changes/autorefresh interval too long
See original GitHub issueref: https://github.com/jupyterlab/jupyterlab-git/pull/448#issuecomment-554193273
Currently, when you make changes to a file on disk in a git repo, it takes a significant lag period before said changes show up in the git sidepanel UI. One quick fix would be to shorten the autorefresh interval. Even better though would be to listen for some flavor of “file changed” signal and trigger a refresh then.
Not sure exactly which signal to listen to, but I assume there’s something relevant somewhere in one of:
@jupyterlab/docmanager
@jupyterlab/docregistry
@jupyterlab/filebrowser
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
Visual Studio Code: Auto-refresh file changes - Stack Overflow
Solved in version 0.3.0 of Visual Studio Code. The file will be updated from disk if there is no changes through the editor....
Read more >Set refresh interval (Map Viewer Classic) - ArcGIS Online
A refresh interval keeps your maps in sync with the latest data while the map is open. For example, you may have an...
Read more >Git Hooks - Git SCM
To enable a hook script, put a file in the hooks subdirectory of your .git directory that is named appropriately (without any extension)...
Read more >VS Code : Browser Auto Refresh On Save ( Not Live Server )
VX Code Extension Name: VSCode Browser Sync- jasonlhy.vscode-browser-syncAuthor : jasonlhyGIT Repo ...
Read more >Settings — GitExtensions 3.4 documentation
The status is updated if Show number of changed files for artificial commits is ... Git Extensions will not allow you to checkout...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
And yeah, I saw that the file browser is configurable; however, that is not exposed to the end user. I think if orgs are concerned about performance, by adding a refresh interval to settings, we can allow them to adjust to taste. We can just provide a sensible default (maybe 4-5s) and tell them they can adjust accordingly.
Submitted a PR. 😃