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
Here is my scenario:
Host machine: Ubuntu 24.04
Guest machine: Windows 10
We put a host machine's directory, e.g. development in to the guest machine, and it is appeared as Z:\development in guest machine. We have a git repo called PythonSnippet in the directory. When we use the installed git-statistic to analyze the git repo Z:\development\PythonSnippet, an error occured, which reads
When we copy the PythonSnippet repo into the guest machine's native directory, then git-statistic could do the analysis properly.
A log tracing can be added into the application, and then we coud provide you the error log information for further analysis.
The text was updated successfully, but these errors were encountered:
We've checked the log file, there are two lines which read
[2024-10-21][12:25:20][tao::platform_impl::platform::event_loop::runner][WARN] NewEvents emitted without explicit RedrawEventsCleared
[2024-10-21][12:25:20][tao::platform_impl::platform::event_loop::runner][WARN] RedrawEventsCleared emitted without explicit MainEventsCleared
And the red alarm "Error Message" is still there. Maybe an explicit log out should be written in the program.
Here is my scenario:
Host machine: Ubuntu 24.04
Guest machine: Windows 10
We put a host machine's directory, e.g. development in to the guest machine, and it is appeared as Z:\development in guest machine. We have a git repo called PythonSnippet in the directory. When we use the installed git-statistic to analyze the git repo Z:\development\PythonSnippet, an error occured, which reads
When we copy the PythonSnippet repo into the guest machine's native directory, then git-statistic could do the analysis properly.
A log tracing can be added into the application, and then we coud provide you the error log information for further analysis.
The text was updated successfully, but these errors were encountered: