ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2018-08-28T09:39:50-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/12126Prism Slow performance for large SESAME files2018-08-28T09:39:50-04:00Kitware RobotPrism Slow performance for large SESAME files**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12126). Further discussion may take place here.**
---
I loaded a sesame file with 1000x1000 density x temperature points and the...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12126). Further discussion may take place here.**
---
I loaded a sesame file with 1000x1000 density x temperature points and the interactive response was much slower. In addition, it seems each frame in a time series was slow; does this mean that the sesame file is being reread at each time? SESAME files do not have time, so it would be better to read it just once.https://gitlab.kitware.com/paraview/paraview/-/issues/12123bug importing raw data when multicore support enabled2020-04-24T19:23:32-04:00Kitware Robotbug importing raw data when multicore support enabled**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12123). Further discussion may take place here.**
---
Importing a RAW dataset (binary) fails silently when Multi-Core support is...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12123). Further discussion may take place here.**
---
Importing a RAW dataset (binary) fails silently when Multi-Core support is enabled i both 3.10.0 and 3.10.1 (32 bit). i.e. load operation appears to have succeeded (no error messages) but dataset is identically zero.https://gitlab.kitware.com/paraview/paraview/-/issues/12120To allow plugin to add item in the contextual menu2019-03-05T10:37:57-05:00Kitware RobotTo allow plugin to add item in the contextual menu**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12120). Further discussion may take place here.**
---
the pqPipelineContextMenuBehaviour implements a buildMenu() function. This...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12120). Further discussion may take place here.**
---
the pqPipelineContextMenuBehaviour implements a buildMenu() function. This a protected, virtual function as well as the QMenu Menu member variable. Thus it is possible to override the buildMenu function in a child class in order to manipulate the context Menu.
However, buildMenu is called only when right-clicking on a mesh (because of the pqView picker). Attached is a patched that makes buildMenu called at each right click in a view. The existing pqDataRepresentation's checks are performed inside the new buildMenu function.https://gitlab.kitware.com/paraview/paraview/-/issues/12118Certain CMake options yield "IceT 2.0.1" in CPackConfig.cmake instead of "Par...2019-03-05T10:37:57-05:00Kitware RobotCertain CMake options yield "IceT 2.0.1" in CPackConfig.cmake instead of "ParaView 3.10.1"**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12118). Further discussion may take place here.**
---
Linux x86_64, CMake 2.8.4, minimal test case:
wget http://www.paraview....**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12118). Further discussion may take place here.**
---
Linux x86_64, CMake 2.8.4, minimal test case:
wget http://www.paraview.org/files/v3.10/ParaView-3.10.1.tar.gz
tar -xvzf ParaView-3.10.1.tar.gz
mkdir build && cd build
cmake ../ParaView-3.10.1 \
-DPARAVIEW_BUILD_QT_GUI:BOOL=OFF \
-DPARAVIEW_USE_MPI:BOOL=ON
grep IceT CPackConfig.cmake
yields
CPackConfig.cmake:SET(CPACK_NSIS_DISPLAY_NAME "IceT 2.0.1")
CPackConfig.cmake:SET(CPACK_NSIS_PACKAGE_NAME "IceT 2.0.1")
CPackConfig.cmake:SET(CPACK_PACKAGE_DESCRIPTION_FILE "/prefix/build/ParaView-3.10.1/Utilities/IceT/README")
CPackConfig.cmake:SET(CPACK_PACKAGE_FILE_NAME "IceT-2.0.1-Linux")
CPackConfig.cmake:SET(CPACK_PACKAGE_INSTALL_DIRECTORY "IceT 2.0.1")
CPackConfig.cmake:SET(CPACK_PACKAGE_INSTALL_REGISTRY_KEY "IceT 2.0.1")
CPackConfig.cmake:SET(CPACK_PACKAGE_NAME "IceT")
Admittedly, one is supposed to run either one of
cpack --config Servers/Executables/CPackParaViewServersConfig.cmake
cpack --config Applications/ParaView/CPackParaViewConfig.cmake
and not just 'cpack', so it does not harm. But IceT shouldn't be putting it's cpack info in the root of the PV tree. That's just confusing.https://gitlab.kitware.com/paraview/paraview/-/issues/12117EyeDomeLighting plugin can't be built if Qt support is disabled2019-03-05T10:37:57-05:00Kitware RobotEyeDomeLighting plugin can't be built if Qt support is disabled**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12117). Further discussion may take place here.**
---
Configuring ParaView 3.10.1 with -DPARAVIEW_BUILD_QT_GUI:BOOL=OFF and
-DP...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12117). Further discussion may take place here.**
---
Configuring ParaView 3.10.1 with -DPARAVIEW_BUILD_QT_GUI:BOOL=OFF and
-DPARAVIEW_BUILD_PLUGIN_EyeDomeLighting:BOOL=ON (for e.g. OSMesa server-only builds) leads to the following error
-- Plugin: EyeDomeLighting enabled
CMake Error at CMake/ParaViewPlugins.cmake:635 (QT4_WRAP_CPP):
Unknown CMake command "QT4_WRAP_CPP".
Call Stack (most recent call first):
Plugins/EyeDomeLighting/ParaViewPlugin/CMakeLists.txt:27
(ADD_PARAVIEW_AUTO_START)
This is due to Plugins/EyeDomeLighting/ParaViewPlugin/CMakeLists.txt
invoking the macro ADD_PARAVIEW_AUTO_START which internally calls
QT4_WRAP_CPP - which is not available in case Qt is purposely disabled.https://gitlab.kitware.com/paraview/paraview/-/issues/12112Possibility to enable/disable rendering ( en then stay in brute mesh mode/sty...2020-04-10T17:30:22-04:00Kitware RobotPossibility to enable/disable rendering ( en then stay in brute mesh mode/style )**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12112). Further discussion may take place here.**
---
When moving a mesh, the NonInteractiveRenderDelay timer begin to decrease....**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12112). Further discussion may take place here.**
---
When moving a mesh, the NonInteractiveRenderDelay timer begin to decrease.
If we could set the NonInteractiveRenderDelay to -1 and then have infinite time to move the mesh and then use a force-render button that will make the mesh to render.
Once disabled, the widget must update when making modification of the mesh ( like points representation, changing color ) but the render must stay in brute state ).
I ask for this features because my mesh are big > 10Go and it's hard to work when it try to render the mesh each time.
Paraview Mailing list subject : http://comments.gmane.org/gmane.comp.science.paraview.user/11741 https://gitlab.kitware.com/paraview/paraview/-/issues/12111Applying a texture to a plane source does not work any more2019-03-05T10:37:57-05:00Kitware RobotApplying a texture to a plane source does not work any more**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12111). Further discussion may take place here.**
---
The collaboration branch merge introduced the following regression:
Par...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12111). Further discussion may take place here.**
---
The collaboration branch merge introduced the following regression:
ParaView nightly build (pv commit f82a7ac1c57632fdace0cfa32ae20d98af281ebc), local server, Linux 64-bit.
* Sources / Plane. Apply
* Display / Apply Texture / Load / just any jpg/png file
=> nothing.
Earlier PV versions did apply the texture.https://gitlab.kitware.com/paraview/paraview/-/issues/12109Fix ObjectBuilder server-creation time-out2020-04-10T22:40:25-04:00Kitware RobotFix ObjectBuilder server-creation time-out**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12109). Further discussion may take place here.**
---
When creating a server 60.0 seconds are hard-coded in vtkProcessModuleConn...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12109). Further discussion may take place here.**
---
When creating a server 60.0 seconds are hard-coded in vtkProcessModuleConnectionManager.cxx
Would be nice to have a static set/get TimeOut in second or ms.
Have a sleep delay that do not stop the current thread to avoid program freeze.https://gitlab.kitware.com/paraview/paraview/-/issues/12108Hang when resizing window with text2019-03-05T10:37:57-05:00Kitware RobotHang when resizing window with text**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12108). Further discussion may take place here.**
---
This one is really hard to track down, but I think I have a case that repl...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12108). Further discussion may take place here.**
---
This one is really hard to track down, but I think I have a case that replicates.
ParaView 3.10.1. Local client is Linux, remote server is Mesa. Mesa version seems to have this problem with 7.4.2 and 7.10.2. I replicated it with 7.10.2. I am using 16 pvserver processes.
Default settings (I believe). One thing I did do is change remote rendering size to 0.
Open 32 file Whipple Shield. All variables On. Apply.
Sources/ Text. Apply.
Make sure that your window can be resized (i.e., isn't full screen.). Now, grab the window at the bottom right and drag that corner up and left. Drag it back where it was. If necessary, go back and forth.
Within one or two itterations, it will freeze, without dying.
Upon killing the server, the client prints out that the server connection has closed, followed by the following line:
VTK/Parallel/vtkSyncronizeRenderers.cxx line 617
Only 3 or 4 component images are handled.
Server death output looks as follows:
slurmd[rs1748]: *** JOB 4009534 CANCELLED AT 2011-04-19T20:23:36 ***
mpiexec: killing job...
[rs1748:27781] [[39288,0],0]-[[39288,0],1] mca_oob_tcp_msg_recv: readv failed: Connection reset by peer (104)
pvserver:27790 terminated with signal 11 at PC=2af11bf82f77 SP=7fff0a7d48a0. Backtrace:
pvserver:27791 terminated with signal 11 at PC=2b6c7b861522 SP=7fffb659e6b8. Backtrace:
pvserver:27792 terminated with signal 11 at PC=2adadbacff77 SP=7fffa8ad56a0. Backtrace:
pvserver:27796 terminated with signal 11 at PC=2aaab0604000 SP=7fff7c022df8. Backtrace:
pvserver:27795 terminated with signal 11 at PC=2aaab065c000 SP=7fff8e4fba08. Backtrace:
--------------------------------------------------------------------------
mpiexec was unable to cleanly terminate the daemons on the nodes shown
below. Additional manual cleanup may be required - please refer to
the "orte-clean" tool for assistance.
--------------------------------------------------------------------------
rs1749
pvserver:2378 terminated with signal 11 at PC=2b9db795436f SP=7fffea402510. Backtrace:
/apps/x86_64/mpi/openmpi/intel-11.1-f064-c064/openmpi-1.4.2_oobpr/lib/libopen-pal.so.0(opal_memory_ptmalloc2_int_free+0xbf)[0x2b9db795436f]
/apps/x86_64/mpi/openmpi/intel-11.1-f064-c064/openmpi-1.4.2_oobpr/lib/libopen-pal.so.0[0x2b9db7958a40]
/lib64/libc.so.6(cfree+0xd1)[0x2b9dc11137f1]
/projects/viz/support/Linux-redsky-x86_64/install/Mesa-7.4.2/lib/libGL.so.1(_mesa_delete_texture_object+0x44)[0x2b9db4ee6ea4]
/projects/viz/support/Linux-redsky-x86_64/install/Mesa-7.4.2/lib/libGL.so.1(_mesa_HashDeleteAll+0x4d)[0x2b9db4eb51cd]
/projects/viz/support/Linux-redsky-x86_64/install/Mesa-7.4.2/lib/libGL.so.1[0x2b9db4e91c1a]
/projects/viz/support/Linux-redsky-x86_64/install/Mesa-7.4.2/lib/libGL.so.1(_mesa_free_context_data+0x181)[0x2b9db4e92dc1]
/projects/viz/support/Linux-redsky-x86_64/install/Mesa-7.4.2/lib/libOSMesa.so.7(OSMesaDestroyContext+0x61)[0x2b9db3d52c51]
/projects/viz/paraview/ParaView/3.10.1-Mesa/Linux-redsky-x86_64/lib/paraview-3.10/libvtkRendering.so.pv3.10(_ZN22vtkXOpenGLRenderWindow22DestroyOffScreenWindowEv+0x73)[0x2b9db9bfb943]
/projects/viz/paraview/ParaView/3.10.1-Mesa/Linux-redsky-x86_64/lib/paraview-3.10/libvtkRendering.so.pv3.10(_ZN22vtkXOpenGLRenderWindow21ResizeOffScreenWindowEii+0x38)[0x2b9db9bfe358]
/projects/viz/paraview/ParaView/3.10.1-Mesa/Linux-redsky-x86_64/lib/paraview-3.10/libvtkRendering.so.pv3.10(_ZN22vtkXOpenGLRenderWindow7SetSizeEii+0xd1)[0x2b9db9bfe481]
/projects/viz/paraview/ParaView/3.10.1-Mesa/Linux-redsky-x86_64/lib/paraview-3.10/libvtkPVFilters.so(_ZN30vtkPVSynchronizedRenderWindows18UpdateWindowLayoutEv+0x317)[0x2b9db17a0237]
/projects/viz/paraview/ParaView/3.10.1-Mesa/Linux-redsky-x86_64/lib/paraview-3.10/libvtkPVFilters.so(_ZN30vtkPVSynchronizedRenderWindows15RootStartRenderEP15vtkRenderWindow+0x5d)[0x2b9db17a26bd]
/projects/viz/paraview/ParaView/3.10.1-Mesa/Linux-redsky-x86_64/lib/paraview-3.10/libvtkCommon.so.pv3.10(_ZN16vtkSubjectHelper11InvokeEventEmPvP9vtkObject+0x3b4)[0x2b9dbf8b0dd4]
/projects/viz/paraview/ParaView/3.10.1-Mesa/Linux-redsky-x86_64/lib/paraview-3.10/libvtkRendering.so.pv3.10(_ZN15vtkRenderWindow6RenderEv+0x69)[0x2b9db9b0f1d9]
/projects/viz/paraview/ParaView/3.10.1-Mesa/Linux-redsky-x86_64/lib/paraview-3.10/libvtkRendering.so.pv3.10(_ZN22vtkXOpenGLRenderWindow6RenderEv+0x40)[0x2b9db9bfabd0]
/projects/viz/paraview/ParaView/3.10.1-Mesa/Linux-redsky-x86_64/lib/paraview-3.10/libvtkPVFilters.so(_ZN30vtkPVSynchronizedRenderWindows6RenderEj+0x42)[0x2b9db179fbd2]
/projects/viz/paraview/ParaView/3.10.1-Mesa/Linux-redsky-x86_64/lib/paraview-3.10/libvtkPVFilters.so[0x2b9db179fc46]
/projects/viz/paraview/ParaView/3.10.1-Mesa/Linux-redsky-x86_64/lib/paraview-3.10/libvtkParallel.so.pv3.10(_ZN25vtkMultiProcessController10ProcessRMIEiPvii+0x88)[0x2b9db924f6b8]
/projects/viz/paraview/ParaView/3.10.1-Mesa/Linux-redsky-x86_64/lib/paraview-3.10/libvtkParallel.so.pv3.10(_ZN25vtkMultiProcessController11ProcessRMIsEii+0x8d)[0x2b9db924f8ad]
/projects/viz/paraview/ParaView/3.10.1-Mesa/Linux-redsky-x86_64/lib/paraview-3.10/libvtkPVServerCommon.so(_ZN19vtkRemoteConnection20ProcessCommunicationEv+0x26)[0x2b9db12009e6]
/projects/viz/paraview/ParaView/3.10.1-Mesa/Linux-redsky-x86_64/lib/paraview-3.10/libvtkPVServerCommon.so(_ZN33vtkProcessModuleConnectionManager18MonitorConnectionsEm+0x21a)[0x2b9db11a877a]
/projects/viz/paraview/ParaView/3.10.1-Mesa/Linux-redsky-x86_64/lib/paraview-3.10/libvtkPVServerCommon.so(_ZN16vtkProcessModule11StartServerEm+0x76)[0x2b9db11adc76]
/projects/viz/paraview/ParaView/3.10.1-Mesa/Linux-redsky-x86_64/lib/paraview-3.10/libvtkPVServerCommon.so(_ZN16vtkProcessModule5StartEiPPc+0x22e)[0x2b9db11adbde]
/projects/viz/paraview/ParaView/3.10.1-Mesa/Linux-redsky-x86_64/lib/paraview-3.10/libvtkPVFilters.so(_ZN9vtkPVMain3RunEP12vtkPVOptions+0x59)[0x2b9db177a5a9]
/projects/viz/paraview/ParaView/3.10.1-Mesa/Linux-redsky-x86_64/lib/paraview-3.10/pvserver(main+0x8d)[0x40145d]
/lib64/libc.so.6(__libc_start_main+0xf4)[0x2b9dc10be994]
/projects/viz/paraview/ParaView/3.10.1-Mesa/Linux-redsky-x86_64/lib/paraview-3.10/pvserver(__gxx_personality_v0+0xb9)[0x4012b9]
slurmd[rs1746]: *** JOB 4009544 CANCELLED AT 2011-04-19T20:30:42 ***
mpiexec: killing job...
pvserver:2381 terminated with signal 11 at PC=2b0e98c39522 SP=7fffeae84858. Backtrace:
pvserver:2383 terminated with signal 11 at PC=2b386acd4522 SP=7fff590f5538. Backtrace:
pvserver:2379 terminated with signal 11 at PC=2b2db24abf77 SP=7fffa046e7f0. Backtrace:
--------------------------------------------------------------------------
mpiexec noticed that process rank 0 with PID 2378 on node rs1746 exited on signal 0 (Unknown signal 0).
--------------------------------------------------------------------------
--------------------------------------------------------------------------
mpiexec was unable to cleanly terminate the daemons on the nodes shown
below. Additional manual cleanup may be required - please refer to
the "orte-clean" tool for assistance.
--------------------------------------------------------------------------
rs1747
pvserver:2380 terminated with signal 11 at PC=2aaab05d0000 SP=7fff28657218. Backtrace:
pvserver:2384 terminated with signal 11 at PC=2b34a385b726 SP=7fffae94dc60. Backtrace:
pvserver:2384 terminated with signal 11 at PC=2b34a50c5621 SP=40d21650. Backtrace:
/lib64/libc.so.6(__cxa_finalize+0x21)[0x2b34a50c5621]
/projects/viz/paraview/ParaView/3.10.1-Mesa/Linux-redsky-x86_64/lib/paraview-3.10/libavtdatabase_par.so[0x2b34a0158dc6]
pvserver:2385 terminated with signal 11 at PC=2abd74be6726 SP=7fff27b32830. Backtrace:
pvserver:2385 terminated with signal 11 at PC=2abd76450621 SP=40f50650. Backtrace:
/lib64/libc.so.6(__cxa_finalize+0x21)[0x2abd76450621]
I don't have either in a debugger, but could fairly easily if desired.
This is a showstopper for us. If possible, and if found, I would take a patch to apply on the 3.10.1 release.
https://gitlab.kitware.com/paraview/paraview/-/issues/12107GUI plugins loaded twice2019-03-05T10:37:57-05:00Kitware RobotGUI plugins loaded twice**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12107). Further discussion may take place here.**
---
Load "ExampleDockPanel" plugin from the examples. Enable "AutoLoad". Resta...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12107). Further discussion may take place here.**
---
Load "ExampleDockPanel" plugin from the examples. Enable "AutoLoad". Restart ParaView. You'll see two dock panels.https://gitlab.kitware.com/paraview/paraview/-/issues/12106RFE: Add ability to compile against system VTK library2020-04-21T09:25:41-04:00Kitware RobotRFE: Add ability to compile against system VTK library**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12106). Further discussion may take place here.**
---
I package ParaView for Fedora. Fedora has a restriction against packages ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12106). Further discussion may take place here.**
---
I package ParaView for Fedora. Fedora has a restriction against packages containing copies of libraries that are separately packaged. So, the ParaView package really should not be building and shipping its own copy of VTK. Now, I know ParaView can be tightly coupled to specific revisions of the VTK library, but we have full control over what revision of VTK is in Fedora as well (I'm essentially maintaining that package at the moment as well).
How feasible does this seem to be?https://gitlab.kitware.com/paraview/paraview/-/issues/12105Loading state file that references an unstructured grid or uniform rectilinea...2019-03-05T10:37:57-05:00Kitware RobotLoading state file that references an unstructured grid or uniform rectilinear grid pops up error message**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12105). Further discussion may take place here.**
---
The collaboration branch merge introduced the following regression:
Par...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12105). Further discussion may take place here.**
---
The collaboration branch merge introduced the following regression:
ParaView nightly build (pv commit 0e9d5b392add10f16dd76c21c90aad50b09b6048), local server, Linux 64-bit.
* Sources / Wavelet. Apply
* File / Save State / filename: foo.pvsm
* File / Disconnect
* File / Load State / filename: foo.pvsm
=> the following error message is raised:
VTK/Filtering/vtkDemandDrivenPipeline.cxx, line 727
vtkCompositeDataPipeline (0x34e4ef0): Input port 0 of algorithm vtkOpenGLGPUVolumeRayCastMapper(0x364b000) has 0 connections but is not optional.
A similar error message is raised if the state file references an unstructured grid (Apply "Clean to Grid" before saving state):
VTK/Filtering/vtkDemandDrivenPipeline.cxx, line 727
vtkCompositeDataPipeline (0x4142e60): Input port 0 of algorithm vtkUnstructuredGridVolumeZSweepMapper(0x30b4e20) has 0 connections but is not optional.
This does not happen for e.g. a polygonal mesh.
Neither of these errors were raised with PV 3.11.0.https://gitlab.kitware.com/paraview/paraview/-/issues/12104Outline mode is broken in print color palette.2019-03-05T10:38:03-05:00Kitware RobotOutline mode is broken in print color palette.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12104). Further discussion may take place here.**
---
ParaView 3.10.0, local server, Windows.
* Sources/ Sphere. Apply.
* Cha...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12104). Further discussion may take place here.**
---
ParaView 3.10.0, local server, Windows.
* Sources/ Sphere. Apply.
* Change to outline mode.
* Edit/ Settings/ Colors/ Choose Palette/ Print.
Notice that the outline is still white, and cannot be seen. This was correct for ParaView 3.8.1.
https://gitlab.kitware.com/paraview/paraview/-/issues/12103xdmf writer is broken2019-03-05T10:38:03-05:00Kitware Robotxdmf writer is broken**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12103). Further discussion may take place here.**
---
3.10.1 and 3.11 can not write xdmf files
They fail with message like:
W...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12103). Further discussion may take place here.**
---
3.10.1 and 3.11 can not write xdmf files
They fail with message like:
Writing 0x28ca0490 a vtkPolyData
XDMF Error in /Source/ParaView/devel/ParaView/Utilities/Xdmf2/libsrc/XdmfHDF.cxx line 604 (Source and Target Spaces specify different sizes for path: /Data2)
XDMF Error in /Source/ParaView/devel/ParaView/Utilities/Xdmf2/libsrc/XdmfHDF.cxx line 605 (Source = 150 items)
XDMF Error in /Source/ParaView/devel/ParaView/Utilities/Xdmf2/libsrc/XdmfHDF.cxx line 606 (Target = 288 items)
XDMF Error in /Source/ParaView/devel/ParaView/Utilities/Xdmf2/libsrc/XdmfValuesHDF.cxx line 175 (Error Writing /Users/demarle/Desktop/foo.h5:/Data2)
XDMF Error in /Source/ParaView/devel/ParaView/Utilities/Xdmf2/libsrc/XdmfDataItem.cxx line 790 (Writing Values Failed)
ERROR: In /Source/ParaView/devel/ParaView/VTK/Filtering/vtkDemandDrivenPipeline.cxx, line 827
vtkPVPostFilterExecutive (0x2763db00): Input for connection index 0 on input port index 0 for algorithm vtkPVPostFilter(0x28cd9d70) is of type vtkDataObject, but a vtkDataSet is required.
https://gitlab.kitware.com/paraview/paraview/-/issues/12100A "Reload data" button would be nice.2019-03-05T10:38:03-05:00Kitware RobotA "Reload data" button would be nice.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12100). Further discussion may take place here.**
---
When finding the best parameters for a simulation, I often do repeated run...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12100). Further discussion may take place here.**
---
When finding the best parameters for a simulation, I often do repeated runs with small modifications, and then wish to see the effect on the data as visualized in Paraview.
For such a cycle, it would be very helpful if there was a simple (one-click) way of telling Paraview to re-load all data files for the current pipeline into memory, and then to execute that pipeline based on the new data.
As far as I can see, currently one has to erase the contents of the pipelien browser, then explicitly do File->Recent Files and select the desired file, and re-build the pipeline from scratch.https://gitlab.kitware.com/paraview/paraview/-/issues/12094Incorrect command line arguments no longer results in paraview quitting with ...2019-03-05T10:38:03-05:00Kitware RobotIncorrect command line arguments no longer results in paraview quitting with errors**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12094). Further discussion may take place here.**
---
Incorrect command line arguments no longer results in paraview quitting wi...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12094). Further discussion may take place here.**
---
Incorrect command line arguments no longer results in paraview quitting with errors
All the following commands result in ParaView starting just fine!!!
> paraview --deere
> pvserver --sdsered
https://gitlab.kitware.com/paraview/paraview/-/issues/12091Problem with ld and colon after --export-dynamic option2020-04-08T04:18:43-04:00Kitware RobotProblem with ld and colon after --export-dynamic option**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12091). Further discussion may take place here.**
---
I downloaded 3.10.1 today and started compiling it. The compilation failed...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12091). Further discussion may take place here.**
---
I downloaded 3.10.1 today and started compiling it. The compilation failed fairly soon with
$ make
Linking C executable ../../bin/vtkWrapHierarchy
[ 0%] Built target vtkWrapHierarchy
Linking C executable ../../bin/vtkWrapPython
[ 0%] Built target vtkWrapPython
Linking C executable ../../bin/vtkWrapPythonInit
[ 0%] Built target vtkWrapPythonInit
Linking CXX shared library ../../../bin/libvtksys.so
[ 0%] Built target vtksys
Linking C shared library ../../../bin/libvtkzlib.so
[ 1%] Built target vtkzlib
Linking C executable ../../../../bin/H5detect
/usr/bin/ld: unrecognized option '--export-dynamic;'
/usr/bin/ld: use the --help option for usage information
collect2: ld returned 1 exit status
make[2]: *** [bin/H5detect] Error 1
make[1]: *** [VTK/Utilities/vtkhdf5/src/CMakeFiles/H5detect.dir/all] Error 2
make: *** [all] Error 2
Reason for this is the colon after --export-dynamic:
$ grep -inR "Wl,--export" *
CMakeCache.txt:476:MPI_LINK_FLAGS:STRING=-Wl,--export-dynamic
VTK/Utilities/vtkhdf5/src/CMakeFiles/H5make_libsettings.dir/link.txt:1:/usr/bin/gcc -std=c99 -fomit-frame-pointer -finline-functions -fno-common -w -fmessage-length=0 -O3 -DNDEBUG -Wl,--export-dynamic; CMakeFiles/H5make_libsettings.dir/H5make_libsettings.c.o -o ../../../../bin/H5make_libsettings -rdynamic
VTK/Utilities/vtkhdf5/src/CMakeFiles/H5detect.dir/link.txt:1:/usr/bin/gcc -std=c99 -fomit-frame-pointer -finline-functions -fno-common -w -fmessage-length=0 -O3 -DNDEBUG -Wl,--export-dynamic; CMakeFiles/H5detect.dir/H5detect.c.o -o ../../../../bin/H5detect -rdynamic
If I remove the colon in the two files above everything works fine.https://gitlab.kitware.com/paraview/paraview/-/issues/12089Assertion failure2020-04-08T04:18:26-04:00Kitware RobotAssertion failure**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12089). Further discussion may take place here.**
---
martinal@martinal-vm:~/Work/adhd/vtk-tests/MeshConversionTools/build$ para...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12089). Further discussion may take place here.**
---
martinal@martinal-vm:~/Work/adhd/vtk-tests/MeshConversionTools/build$ paraview --data=../data/output.vtk &
[2] 8163
martinal@martinal-vm:~/Work/adhd/vtk-tests/MeshConversionTools/build$ X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 5 (Unknown request)
Resource id: 0x3800273
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 1 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 112 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 116 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 116 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 1 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 1 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 1 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 1 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 1 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 1 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 1 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 1 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 1 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 1 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 1 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 1 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 1 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 1 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 1 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 1 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 1 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 1 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 1 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 1 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 1 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 1 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 1 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 1 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 1 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 1 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 1 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 1 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 1 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 1 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 1 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 1 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 1 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 1 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 1 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 1 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 1 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 1 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 1 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 11 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 1 (Unknown request)
Resource id: 0x9d0005
X Error: GLXBadContextTag 173
Extension: 157 (Uknown extension)
Minor opcode: 117 (Unknown request)
Resource id: 0x9d0005
paraview: ../../src/xcb_io.c:183: process_responses: Assertion `!(req && current_request && !(((long) (req->sequence) - (long) (current_request)) <= 0))' failed.
[2]+ Aborted paraview --data=../data/output.vtk
https://gitlab.kitware.com/paraview/paraview/-/issues/12087vtkSocket does not restart interupted call2019-03-05T10:38:03-05:00Kitware RobotvtkSocket does not restart interupted call**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12087). Further discussion may take place here.**
---
Hi,
While installing ParaView on Nautilus,
http://www.nics.tennessee....**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12087). Further discussion may take place here.**
---
Hi,
While installing ParaView on Nautilus,
http://www.nics.tennessee.edu/computing-resources/nautilus, I hit a bug
in vtkSocket that prevents ParaView from running on this machine. While
tracking this down I uncovered a couple related issues.
The main issue is that vtkSocket does not handle EINTR. EINTR occurs
when a signal is caught by the application during a blocking socket
call. While ParaView does not make use of signals they are used for
asynchronous communication by some SGI specific libraries on Nautilus
that are linked in with SGI MPI. Because Rank 0 pvserver spends quite a
bit of its time blocked in socket calls it only takes a few 10s of
seconds for EINTR to occur. When faced with EINTR ParaView silently
exits leaving the user wondering what the heck happened. Which brings me
to the second issue, a lack of error reporting in vtkSocket.
To solve the first issue vtkSocket has to handle EINTR. How EINTR should
be handled depends on the specific socket call. For all calls except
connect the call can simply be restarted. For EINTR during connect one
can't restart the call on all unix, so instead one must block in a
select call when connect fails with EINTR. To be portable across Unix
one should handle EINTR in all socket calls, even simple ones like
set/getsockopt.
The second issue of error reporting applies to all socket related errors
in general, my feeling is that when a socket call fails vtkSocket should
print a message using vtkErrorMacro, errno, and strerror(or windows
equivalent) at the point of failure. I think this should be done inside
vtkSocket because this is the only place one can safely assume errno has
relevant information and vtkSocket has been implemented returning a
single error code, -1, so that returning the real error code would
change the API and break existing code, including ParaView. Not to
mention that the values for error codes are apparently different on
windows and unix.
I took a stab at fixing these issues, patches attached. I tested them on
my workstation, nautilus, and laptop running xp. I ran a dashboard on my
linux workstation and didn't see any related issues. Would someone at KW
mind taking a look at the changes and see if it could be made permanent?
By the way after testing all socket calls for error returns I uncovered
a third bug, vtkSocket::Close didn't set the descriptor ivar to -1 which
resulted in vtkSocket::~vtkSocket calling close on a closed socket. Not
a disasterous error, but this reinforces my opinion that the returns
should be tested and error messages printed.
Thanks
Burlen
https://gitlab.kitware.com/paraview/paraview/-/issues/12085Auto load plugin does not work properly2019-03-05T10:38:03-05:00Kitware RobotAuto load plugin does not work properly**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12085). Further discussion may take place here.**
---
When used in an install context auto-load plugin do not work properly
T...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12085). Further discussion may take place here.**
---
When used in an install context auto-load plugin do not work properly
This start happening after the merge of Collaboration branch