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
In another post, I mentioned having to rebuild things after trying to delete a project. When I did rebuilt things, the volume of console output increased significantly, and types of information -- primarily warnings -- were produced that hadn't been generated by prior runs of buildandRUN.ps1. When I did that, the volume of console output understandably increased significantly, and types of information were produced that hadn't been by prior runs of buildandRUN.ps1.
These included repetitive instances of
==========
Cautions pertaining to the'numba.jit' decorator:
==========
Information on importing extensions. I note that an 'Import Error' message is produced if extensions are not present that one might consider changing to a 'warning' if that's feasible.
ImportError: No app.py found in '/extension/ExampleExtension/src'.
(for any extension folder that is empty)
==========
And isolated unexpected behavior about where the server is running:
Finished loading extensions, server is running...
Debugger is active!
Debugger PIN: 179-176-362
Running on all addresses.
WARNING: This is a development server. Do not use it in a production deployment.
Even after 'venv' is rebuilt, the same output is produced on subsequent runs of buildandRUN.ps1.
Can this be toned down to generate the level of output that was present upon initial installation of VRNetzer / DataDiVR?
The text was updated successfully, but these errors were encountered:
ClaytonCurtis1947
changed the title
ISSUE - Addressing output generated when rebuilding the environment
ISSUE - Addressing output generated when rebuilding the environment (moved to \DataDiDVR 2023-09-21)
Sep 21, 2023
In another post, I mentioned having to rebuild things after trying to delete a project. When I did rebuilt things, the volume of console output increased significantly, and types of information -- primarily warnings -- were produced that hadn't been generated by prior runs of buildandRUN.ps1. When I did that, the volume of console output understandably increased significantly, and types of information were produced that hadn't been by prior runs of buildandRUN.ps1.
These included repetitive instances of
==========
Cautions pertaining to the'numba.jit' decorator:
c:\users\XXX\desktop\vrnetzer\datadivr_webapp-main\venv\lib\site-packages\umap\distances.py:1063: NumbaDeprecationWarning: The 'nopython' keyword argument was not supplied to the 'numba.jit' decorator. The implicit default value for this argument is currently False, but it will be changed to True in Numba 0.59.0. See https://numba.readthedocs.io/en/stable/reference/deprecation.html#deprecation-of-object-mode-fall-back-behaviour-when-using-jit for details.
@numba.jit()
==========
Information on importing extensions. I note that an 'Import Error' message is produced if extensions are not present that one might consider changing to a 'warning' if that's feasible.
ImportError: No app.py found in '/extension/ExampleExtension/src'.
(for any extension folder that is empty)
==========
And isolated unexpected behavior about where the server is running:
Finished loading extensions, server is running...
WARNING: This is a development server. Do not use it in a production deployment.
Even after 'venv' is rebuilt, the same output is produced on subsequent runs of buildandRUN.ps1.
Can this be toned down to generate the level of output that was present upon initial installation of VRNetzer / DataDiVR?
Regards,
Clayton Curtis
New duplicative and voluminous output when rebuilding.txt
The text was updated successfully, but these errors were encountered: