ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2024-01-02T11:40:36-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/21125Strange behavior of Python multiprocessing package2024-01-02T11:40:36-05:00Sebastien JourdainStrange behavior of Python multiprocessing packageThe following lines works without issue inside a regular python but not inside pvpython.
```python
>>> import multiprocessing as mp
>>> p = mp.Process(target=print, args=["Hello"])
>>> p.start()
>>> Hello
>>>
```
With __pvpython__ we ...The following lines works without issue inside a regular python but not inside pvpython.
```python
>>> import multiprocessing as mp
>>> p = mp.Process(target=print, args=["Hello"])
>>> p.start()
>>> Hello
>>>
```
With __pvpython__ we get the following error
```python
>>> import multiprocessing as mp
>>> p = mp.Process(target=print, args=["Hello"])
>>> p.start()
/Applications/ParaView-5.10.0-RC1.app/Contents/Libraries/lib/python3.9/multiprocessing/resource_tracker.py:96: UserWarning: resource_tracker: process died unexpectedly, relaunching. Some resources might leak.
warnings.warn('resource_tracker: process died unexpectedly, '
```Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/21124Replace dataset option2022-02-02T13:41:32-05:00Boonthanome NouanesengsyReplace dataset optionWhen a user has created a pipeline, it would be nice to have the ability to switch out a dataset with another dataset quickly. It would be good to be able to right click on a dataset in the pipeline browser, then choose something like `R...When a user has created a pipeline, it would be nice to have the ability to switch out a dataset with another dataset quickly. It would be good to be able to right click on a dataset in the pipeline browser, then choose something like `Replace dataset`, so that a user can quickly load another dataset, and have the current pipeline applied to it.
There is the `Change Input` option when right clicking on a filter, but it's not as efficient as a `Replace dataset` feature would be.
@patchett2002 @ethan.stam @cory.quammen @utkarsh.ayachit5.11 (Spring 2022)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/21123Copy and paste filters in pipeline browser2023-10-18T11:26:24-04:00Boonthanome NouanesengsyCopy and paste filters in pipeline browserWe would like the ability to copy and paste filters in the pipeline browser, so that a user can easily replicate a pipeline on another dataset. A feature request for this is also at: https://gitlab.kitware.com/paraview/paraview/-/issues/...We would like the ability to copy and paste filters in the pipeline browser, so that a user can easily replicate a pipeline on another dataset. A feature request for this is also at: https://gitlab.kitware.com/paraview/paraview/-/issues/18771.
There is already a copy and paste option when right clicking items in the pipeline browser, but that is for values of a filter. It won't create new pipeline elements.
Another way to do this is to save the state, then load the state with another dataset. While this is nice, being able to copy and paste pipeline elements would be cleaner and faster.
@patchett2002 @ethan.stam @cory.quammen @utkarsh.ayachit5.12 (Winter 2023)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/21122Add min/max labels of a variable to the color bar2022-06-30T09:48:16-04:00Boonthanome NouanesengsyAdd min/max labels of a variable to the color barWe would like the ability to have the color bar list the minimum and maximum values of a variable, regardless of what limits the color bar is currently set to. This is so the user can easily see the min and max values of the variable, ev...We would like the ability to have the color bar list the minimum and maximum values of a variable, regardless of what limits the color bar is currently set to. This is so the user can easily see the min and max values of the variable, even though the color bar may be set differently. A check mark to enable this feature would be nice. Please see the screenshot below of Visit, where the min and max values of the variable are listed at the bottom of the color bar.
![image](/uploads/b076caddfac9e0a437882f9d233a9fbc/image.png)
Currently, there is a color bar option called `Add Range Annotations`, but that shows the min and max of the color bar range, not the min and max of the variable.
I know that with this can be achieved with `Python Annotation`, but we would like an easier way to do this.
@patchett2002 @ethan.stam @cory.quammen @utkarsh.ayachit5.11 (Spring 2022)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/21118RuntieDeviceTracker fails to build gcc 4.9.42021-12-07T08:11:44-05:00chart3388RuntieDeviceTracker fails to build gcc 4.9.4Using superbuild to build ParaView 5.10 fails on gcc 4.8.5 and gcc 4.9.4:
```
[4530/20529] Building CXX object VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/vtkm/cont/CMakeFiles/vtkm_cont.dir/RuntimeDeviceTracker.cxx.o
FAILED: VTK/ThirdParty/vtkm/v...Using superbuild to build ParaView 5.10 fails on gcc 4.8.5 and gcc 4.9.4:
```
[4530/20529] Building CXX object VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/vtkm/cont/CMakeFiles/vtkm_cont.dir/RuntimeDeviceTracker.cxx.o
FAILED: VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/vtkm/cont/CMakeFiles/vtkm_cont.dir/RuntimeDeviceTracker.cxx.o
/opt/jenkins/jenkins-tools/gcc-4.9.4/bin/g++ -DTBB_VERSION_MAJOR=2021 -DVTKMDIY_MPI_AS_LIB -DVTKMDIY_NO_THREADS -Dvtkm_cont_EXPORTS -I/opt/jenkins/workspace/source/oss-paraview/src/paraview-5.10.0/VTK/ThirdParty/vtkm/vtkvtkm/vtk-m -IVTK/ThirdParty/vtkm/vtkvtkm/vtk-m/include -I/opt/jenkins/workspace/source/oss-paraview/src/paraview-5.10.0/VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/vtkm/thirdparty/optionparser -I/opt/jenkins/workspace/source/oss-paraview/src/paraview-5.10.0/VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/vtkm/thirdparty/diy -I/opt/jenkins/workspace/source/oss-paraview/src/paraview-5.10.0/VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/vtkm/thirdparty/lcl/vtkmlcl -I/opt/jenkins/workspace/source/oss-paraview/src/paraview-5.10.0/VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/vtkm/thirdparty/loguru -isystem /opt/jenkins/workspace/cmb-build/install/include -isystem /opt/jenkins/workspace/source/oss-paraview/src/paraview-5.10.0/VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/vtkm/thirdparty/diy/vtkmdiy/include -isystem VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/vtkm/thirdparty/diy/vtkmdiy/include/vtkmdiy/mpi -march=core2 -mno-avx512f -fPIC -std=c++11 -O3 -DNDEBUG -fPIC -fvisibility=hidden -fvisibility-inlines-hidden -Wall -Wcast-align -Wextra -Wpointer-arith -Wformat -Wformat-security -Wshadow -Wunused -fno-common -Wno-unused-function -Wchar-subscripts -ffunction-sections -pthread -std=c++14 -MD -MT VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/vtkm/cont/CMakeFiles/vtkm_cont.dir/RuntimeDeviceTracker.cxx.o -MF VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/vtkm/cont/CMakeFiles/vtkm_cont.dir/RuntimeDeviceTracker.cxx.o.d -o VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/vtkm/cont/CMakeFiles/vtkm_cont.dir/RuntimeDeviceTracker.cxx.o -c /opt/jenkins/workspace/source/oss-paraview/src/paraview-5.10.0/VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/vtkm/cont/RuntimeDeviceTracker.cxx
/opt/jenkins/workspace/source/oss-paraview/src/paraview-5.10.0/VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/vtkm/cont/RuntimeDeviceTracker.cxx: In member function ‘void vtkm::cont::RuntimeDeviceTracker::CopyStateFrom(const vtkm::cont::RuntimeDeviceTracker&)’:
/opt/jenkins/workspace/source/oss-paraview/src/paraview-5.10.0/VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/vtkm/cont/RuntimeDeviceTracker.cxx:169:13: error: ‘cbegin’ is not a member of ‘std’
std::copy(std::cbegin(tracker.Internals->RuntimeAllowed),
^
/opt/jenkins/workspace/source/oss-paraview/src/paraview-5.10.0/VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/vtkm/cont/RuntimeDeviceTracker.cxx:170:13: error: ‘cend’ is not a member of ‘std’
std::cend(tracker.Internals->RuntimeAllowed),
^
```https://gitlab.kitware.com/paraview/paraview/-/issues/21116ButtonProperty do not trigger pipeline update correctly2021-12-01T09:08:48-05:00Mathieu Westphal (Kitware)ButtonProperty do not trigger pipeline update correctlyButtonProperty do not trigger pipeline update correctly, only RequestInformation is called on button clicks, RequestData and complete pipeline execution is only performed on interaction with the view
Steps to reproduce:
- build this m...ButtonProperty do not trigger pipeline update correctly, only RequestInformation is called on button clicks, RequestData and complete pipeline execution is only performed on interaction with the view
Steps to reproduce:
- build this modified "ElevationFilters" plugin: [ElevationFilter.tgz](/uploads/feedb9e9cc2229e91cb92f206e6c8dce/ElevationFilter.tgz)
- Open ParaView, load ElevationFilter plugin
- Wavelet, Apply
- MyElevation, Apply
- Press the "Reload Immediatly" button
- Only RequestInformation is done
- Interact with the view -> RequestData is done
Note: using `panel_widget="command_button"` fixes the issue, but this is a different feature. (that we may want to merge?)
Note2: This feature is used only in the tesselate filter in ParaViewhttps://gitlab.kitware.com/paraview/paraview/-/issues/21115Bug2021-12-02T07:38:28-05:00Peekarn TeerawathananonBugOS: Windows 10 Version 2009
ParaView Version: 5.10.0-RC1
Qt Version: 5.15.2
Description
Hi,
I have issue with connection to OneDrive file on Paraview. Seem like the program is offline. please help me to solve this. ThanksOS: Windows 10 Version 2009
ParaView Version: 5.10.0-RC1
Qt Version: 5.15.2
Description
Hi,
I have issue with connection to OneDrive file on Paraview. Seem like the program is offline. please help me to solve this. Thankshttps://gitlab.kitware.com/paraview/paraview/-/issues/21114Comment out traces of blocks and variable names2023-01-03T11:45:02-05:00W. Alan ScottComment out traces of blocks and variable namesPlease stop explicitly setting the loading of blocks and variables in a trace. As blocks and variables are loaded by default, this is not necessary. Further, it makes the trace significantly more restricted. Here is the discourse disc...Please stop explicitly setting the loading of blocks and variables in a trace. As blocks and variables are loaded by default, this is not necessary. Further, it makes the trace significantly more restricted. Here is the discourse discussion: https://discourse.paraview.org/t/explicitly-naming-variables-and-blocks-in-trace/8515.
So, for the trace of the load of can.exo, change
```
canex2 = IOSSReader(registrationName='can.ex2', FileName=['/Applications/PV/can.ex2'])
canex2.ElementBlocks = ['block_1', 'block_2']
canex2.NodeBlockFields = ['accl', 'displ', 'vel']
canex2.ElementBlockFields = ['eqps']
```
to
```
canex2 = IOSSReader(registrationName='can.ex2', FileName=['/Applications/PV/can.ex2'])
# canex2.ElementBlocks = ['block_1', 'block_2']
# canex2.NodeBlockFields = ['accl', 'displ', 'vel']
# canex2.ElementBlockFields = ['eqps']
```5.12 (Winter 2023)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/21111pvpython crash when creating Clip or Slice2021-12-22T15:20:52-05:00Aron Helserpvpython crash when creating Clip or SliceIn ParaView 5.9 and 5.10 (RC), `pvpython` and the internal python shell will segfault (and kill ParaView) if the first action taken is either of these:
```
c = Clip()
s = Slice()
```
Originally reported in a [discourse thread](https://d...In ParaView 5.9 and 5.10 (RC), `pvpython` and the internal python shell will segfault (and kill ParaView) if the first action taken is either of these:
```
c = Clip()
s = Slice()
```
Originally reported in a [discourse thread](https://discourse.paraview.org/t/segmentation-fault-when-no-keyword-arguments-are-passed/8469).
The backtrace points to:
```
VTKExtensions/FiltersGeneral/vtkPVMetaClipDataSet.cxx:210
209 if (vtkHyperTreeGrid::SafeDownCast(
210 inputVector[0]->GetInformationObject(0)->Get(vtkDataObject::DATA_OBJECT())))
```
where `inputVector[0]->GetInformationObject(0)` is `nullptr`. There's a similar problem with `vtkPVMetaSliceDataSet`Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/21109Source font sizes are wrong for save screenshot when scaled2022-07-06T18:17:59-04:00W. Alan ScottSource font sizes are wrong for save screenshot when scaledFont sizes are incorrect for Sources when a user uses save screenshot when increasing resolution. Here is how to replicate, with images.
There are three images that we want to compare. All three use can.exo and color legend, Sources -...Font sizes are incorrect for Sources when a user uses save screenshot when increasing resolution. Here is how to replicate, with images.
There are three images that we want to compare. All three use can.exo and color legend, Sources - Text, and Sources - Annotate Time. First image is just a screenshot, second is a 2X size screenshot (without scaled fonts), and the third is a 2X size screenshot with scaled fonts. For all three, we then display them, and make the image be the same size on screen. In other words, no matter what the pixel count, make them 9 inches wide X 6 inches tall. Here is how to create them.
* 5.9.1 (also 5.10.0-RC1), Linux (and Mac, as per bug listed at bottom), builtin server.
* load can.exo. All vars on. Apply.
* Paint by displ.
* Rescale to custom data range. 0.123 to 19.984.
* Move forward a few timesteps. Not needed, but it's prettier.
* Sources/ Text. "Text Text Text Text Text". Apply.
* Move to the bottom center.
* Sources/ Annotate Time. Apply.
* Move to the top center.
First Screenshot.
* File/ Save Screenshot. Save as screenshot screenshotNormal.png. OK.
* Advanced. (Not needed yet, but we will.)
* OK.
Second Screenshot - Large, not scaled.
* File/ Save Screenshot. Save as screenshot screenshot2X.png. OK.
* Advanced. Font Scaling: Do Not Scale Fonts.
* 2X.
* OK.
Third Screenshot - Large, scaled.
* File/ Save Screenshot. Save as screenshot screenshot2XScaled.png. OK.
* Advanced. Font Scaling: Scale Fonts.
* 2X.
* OK.
Description
* The first screenshot should match up perfectly with the ParaView renderview.
* The second screenshot should have the same size fonts as the first screenshot. The color legend (that is correctly elongated) has the correct size text. The Sources/ Text and Sources/ Annotate Time are 1/2 the size they should be. Change the size of second screenshot on screen to be the same size as first screenshot. Text should be 1/2 the correct size, but is actually 1/4th the correct size.
* The third screenshot should have fonts that are twice the size of the first screenshot, so that when the two images are seen the same size, they look the same. For the sources, the third screenshot actually has "correct" size fonts, which when scaled will be 1/2 correct size compared to the first screenshot. Again, the color legend has the correct font size.
This is impacting my users, thus I am marking for 5.11, showstopper. Please don't slip without asking me.
First reported in #21009, but I wanted detailed directions how to replicate.5.11 (Spring 2022)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/21105ParaView 5.10.0-RC2: SaveExtract volumetric cinema database crash2022-03-03T20:58:54-05:00Jean M. FavreParaView 5.10.0-RC2: SaveExtract volumetric cinema database crashSteps to reproduce:
0) download ParaView-5.10.0-RC2-MPI-Linux-Python3.9-x86_64.tar.gz
1) Create a simple source (Superquadric). Apply
2) Create an Extractor (Cinema Volumetric PNG). Apply
3) Click on Save Extracts. Apply.
4) the applica...Steps to reproduce:
0) download ParaView-5.10.0-RC2-MPI-Linux-Python3.9-x86_64.tar.gz
1) Create a simple source (Superquadric). Apply
2) Create an Extractor (Cinema Volumetric PNG). Apply
3) Click on Save Extracts. Apply.
4) the application seg-faults
this explains perhaps the issue documented in https://discourse.paraview.org/t/createextractor-cinemavolumetricpng-crash/84895.10.1 (Winter 2022)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/21103ParaView 5.10.0-RC2: arm64 .dmg does not mount2022-05-12T16:10:42-04:00Cory Quammencory.quammen@kitware.comParaView 5.10.0-RC2: arm64 .dmg does not mountIt reports the following error message:
![image](/uploads/628d710e12db78fda6c20379c19d56f8/image.png)It reports the following error message:
![image](/uploads/628d710e12db78fda6c20379c19d56f8/image.png)5.10 (Fall 2021)https://gitlab.kitware.com/paraview/paraview/-/issues/21101Windows: Example of the Can crashes ParaView 5.10.0-RC22021-12-03T13:25:57-05:00Vicente Boleavicente.bolea@kitware.comWindows: Example of the Can crashes ParaView 5.10.0-RC2Version: ParaView 5.10.0-RC2 (Binary from superbuild)
Flavor: Every flavor
GL: MESA
Steps to recreate it:
- Open paraview.exe
- Help / Example Visualizations
- Click the first example (Top-left, the Can)
- Crash happens
It silently c...Version: ParaView 5.10.0-RC2 (Binary from superbuild)
Flavor: Every flavor
GL: MESA
Steps to recreate it:
- Open paraview.exe
- Help / Example Visualizations
- Click the first example (Top-left, the Can)
- Crash happens
It silently crashes so I could not get any error message/backtrace, I will explore how to get more hint of what is happening
Other examples work as expected
@cory.quammen5.10 (Fall 2021)https://gitlab.kitware.com/paraview/paraview/-/issues/21100Trace bad for directories starting with n on Windows2022-05-18T21:10:28-04:00W. Alan ScottTrace bad for directories starting with n on WindowsTraces are bad for directories with a leading n in the name on Windows. Here is how to replicate:
* Must be Windows, (post) 5.10.0-RC1 master (and 5.9.1, and 5.8.0), builtin server.
* In a file explorer, create a dirctory that starts wi...Traces are bad for directories with a leading n in the name on Windows. Here is how to replicate:
* Must be Windows, (post) 5.10.0-RC1 master (and 5.9.1, and 5.8.0), builtin server.
* In a file explorer, create a dirctory that starts with 'n'. I created c:\alan\nutsDeleteMe. Copy a multifile datset in here, such as g1s1.
* Tools/ Start Trace. OK.
* File/ Open/ g1s1. Apply.
* Tools/ Stop Trace.
Now, look at the trace. The wrong output, which we have looks like this. Notice that the folder name for nutsDeleteMe is truncated. Further, notice that we should have a list, but don't. Last, '\n' carriage control's have been placed in the text.
g1s110fpse16 = IOSSReader(registrationName='g1s1-10fps.e.16.*', FileName="""'D:\\alan\\work\
utsDeleteMe\\g1s1-10fps.e.16.00', 'D:\\alan\\work\
utsDeleteMe\\g1s1-10fps.e.16.01', 'D:\\alan\\work\
utsDeleteMe\\g1s1-10fps.e.16.02', 'D:\\alan\\work\
utsDeleteMe\\g1s1-10fps.e.16.03', 'D:\\alan\\work\
utsDeleteMe\\g1s1-10fps.e.16.04', 'D:\\alan\\work\
utsDeleteMe\\g1s1-10fps.e.16.05', 'D:\\alan\\work\
utsDeleteMe\\g1s1-10fps.e.16.06', 'D:\\alan\\work\
utsDeleteMe\\g1s1-10fps.e.16.07', 'D:\\alan\\work\
utsDeleteMe\\g1s1-10fps.e.16.08', 'D:\\alan\\work\
utsDeleteMe\\g1s1-10fps.e.16.09', 'D:\\alan\\work\
utsDeleteMe\\g1s1-10fps.e.16.10', 'D:\\alan\\work\
utsDeleteMe\\g1s1-10fps.e.16.11', 'D:\\alan\\work\
utsDeleteMe\\g1s1-10fps.e.16.12', 'D:\\alan\\work\
utsDeleteMe\\g1s1-10fps.e.16.13', 'D:\\alan\\work\
utsDeleteMe\\g1s1-10fps.e.16.14', 'D:\\alan\\work\
utsDeleteMe\\g1s1-10fps.e.16.15'""")
A correct reader (with a non 'n' directory) would look like this:
g1s110fpse16 = ExodusIIReader(registrationName='g1s1-10fps.e.16.*', FileName=['D:\\alan\\demos\\g1s1\\g1s1-10fps.e.16.00', 'D:\\alan\\demos\\g1s1\\g1s1-10fps.e.16.01', 'D:\\alan\\demos\\g1s1\\g1s1-10fps.e.16.02', 'D:\\alan\\demos\\g1s1\\g1s1-10fps.e.16.03', 'D:\\alan\\demos\\g1s1\\g1s1-10fps.e.16.04', 'D:\\alan\\demos\\g1s1\\g1s1-10fps.e.16.05', 'D:\\alan\\demos\\g1s1\\g1s1-10fps.e.16.06', 'D:\\alan\\demos\\g1s1\\g1s1-10fps.e.16.07', 'D:\\alan\\demos\\g1s1\\g1s1-10fps.e.16.08', 'D:\\alan\\demos\\g1s1\\g1s1-10fps.e.16.09', 'D:\\alan\\demos\\g1s1\\g1s1-10fps.e.16.10', 'D:\\alan\\demos\\g1s1\\g1s1-10fps.e.16.11', 'D:\\alan\\demos\\g1s1\\g1s1-10fps.e.16.12', 'D:\\alan\\demos\\g1s1\\g1s1-10fps.e.16.13', 'D:\\alan\\demos\\g1s1\\g1s1-10fps.e.16.14', 'D:\\alan\\demos\\g1s1\\g1s1-10fps.e.16.15'])
Although this one has been around a while, it is so bad I am marking it as required for 5.10.1. If it slips to 5.11, make it a showstopper.5.11 (Spring 2022)Jaswant Panchumarti (Kitware)Jaswant Panchumarti (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/21093Release ParaView 5.10.0-RC22021-12-01T11:55:14-05:00Vicente Boleavicente.bolea@kitware.comRelease ParaView 5.10.0-RC2# Preparatory steps
- Update ParaView guides
- User manual
- [x] Rename to ParaViewGuide-5.10.0.pdf
- [x] Upload to www.paraview.org/files/v5.10
- Catalyst Guide
- [x] Rename to ParaViewCatalystGuide-5.10.0.p...# Preparatory steps
- Update ParaView guides
- User manual
- [x] Rename to ParaViewGuide-5.10.0.pdf
- [x] Upload to www.paraview.org/files/v5.10
- Catalyst Guide
- [x] Rename to ParaViewCatalystGuide-5.10.0.pdf
- [x] Upload to www.paraview.org/files/v5.10
- Getting Started Guide
- [x] Rename to ParaViewGettingStarted-5.10.0.pdf
- [x] Upload to www.paraview.org/files/v5.10
# Update ParaView
- Update the local copy of `release`.
- If `0-RC2` is `0-RC1`, update `master`
- Otherwise, update `release`
```
git fetch origin
git checkout release
git merge --ff-only origin/release # if this fails, there are local commits that need to be removed
git submodule update --recursive --init
```
- If `release` is not `master`, ensure merge requests which should be
in the release have been merged. The [`backport-mrs.py`][backport-mrs]
script can be used to find and ensure that merge requests assigned to the
associated milestone are available on the `release` branch.
- Integrate changes.
- Make a commit for each of these `release`-only changes on a single topic
(suggested branch name: `update-to-v5.10.0`):
- Assemble release notes into `Documentation/release/ParaView-5.10.0.md`.
- [x] If `PATCH` is greater than 0, add items to the end of this file.
- [x] Update `version.txt` and tag the commit (tag this commit below)
```
git checkout -b update-to-v5.10.0-RC2 1c3e416213f78b61f6d7dce0adfb4c7aced1cbdb
echo 5.10.0-RC2 > version.txt
git commit -m 'Update version number to 5.10.0-RC2' version.txt
```
- [x] Update VTK's `paraview/release` branch. The
[`release-mr`][release-mr] script should be used to do this. Pass
`-c .kitware-release-paraview.json` to use the appropriate
configuration file.
- [x] Merge the VTK `paraview/release` update MR
- [x] Update kwrobot with the new `paraview/release` branch rules (@ben.boeckel)
- [x] `.gitmodules` to track the `paraview/release` branch of VTK
- [x] Update `.gitlab/ci/cdash-groups.json` to track the `release` CDash
groups
- Create a merge request targeting `release`
- [x] Obtain a GitLab API token for the `kwrobot.release.paraview` user
(ask @ben.boeckel if you do not have one)
- [x] Add the `kwrobot.release.paraview` user to your fork with at least
`Developer` privileges (so it can open MRs)
- [x] Use [the `release-mr`][release-mr] script to open the create the
Merge Request (see script for usage)
- Pull the script for each release; it may have been updated since it
was last used
- The script outputs the information it will be using to create the
merge request. Please verify that it is all correct before creating
the merge request. See usage at the top of the script to provide
information that is either missing or incorrect (e.g., if its data
extraction heuristics fail).
- [x] Get positive review
- [x] `Do: merge`
- [x] Create tag: `git tag -a -m 'ParaView 5.10.0-RC2' v5.10.0-RC2 commit-that-updated-version.txt`
- Create tarballs
- [x] ParaView (`Utilities/Maintenance/create_tarballs.bash --txz --tgz --zip -v v5.10.0-RC2`)
- Upload tarballs to `paraview.org`
- [x] `rsync -rptv $tarballs user@host:ParaView_Release/v5.10/`
[backport-mrs]: https://gitlab.kitware.com/utils/release-utils/-/blob/master/backport-mrs.py
[release-mr]: https://gitlab.kitware.com/utils/release-utils/-/blob/master/release-mr.py
[cdash-update-groups]: https://gitlab.kitware.com/utils/cdash-utils/-/blob/master/cdash-update-groups.py
# Update ParaView-Superbuild
- [x] Update release branch for **paraview-superbuild**
```
git fetch origin
git checkout release
git merge --ff-only origin/release
git submodule update --recursive --init
```
- [x] Update `version.txt` and tag the commit
```
git checkout -b update-to-v5.10.0-RC2 1c3e416213f78b61f6d7dce0adfb4c7aced1cbdb
```
- Integrate changes.
- Create a new branch `git checkout -b update-to-v5.10.0-RC2`
- Update versions
- [x] Guide selections in `versions.cmake`
- [x] `paraview_SOURCE_SELECTION` version in `README.md`
- [x] Docker: update default tag strings (in `Scripts/docker/ubuntu/development/Dockerfile`)
- [x] ARG PARAVIEW_TAG=v5.10.0-RC2
- [x] ARG SUPERBUILD_TAG=v5.10.0-RC2
- [x] ARG PARAVIEW_VERSION_STRING=paraview-5.10
- [x] Commit changes and push to GitLab
- [x] `git add versions.cmake CMakeLists.txt Scripts/docker/ubuntu/development/Dockerfile`
- [x] `git commit -m "Update the default version to 5.10.0-RC2"`
- Create a commit which will be tagged:
- [x] `git commit --allow-empty -m "paraview: add release 5.10.0"`
- [x] Created tag: `git tag -a -m 'ParaView superbuild 5.10.0-RC2' v5.10.0-RC2 HEAD`
- Force `5.10.0-RC2` in CMakeLists.txt
- [x] Append to the top of CMakeLists.txt (After project...) The following
```
# Force source selection setting here.
set(paraview_SOURCE_SELECTION "5.10.0-RC2" CACHE STRING "Force version to 5.10.0-RC2" FORCE)
set(paraview_FROM_SOURCE_DIR OFF CACHE BOOL "Force source dir off" FORCE)
```
- [x] Create fixup commit `git commit -a --fixup=@`
- Create a merge request targeting `release`
- [x] Obtain a GitLab API token for the `kwrobot.release.paraview` user
(ask @ben.boeckel if you do not have one)
- [x] Add the `kwrobot.release.paraview` user to your fork with at least
`Developer` privileges (so it can open MRs)
- [x] Use [the `release-mr`][release-mr] script to open the create the
Merge Request (see script for usage)
- Pull the script for each release; it may have been updated since it
was last used
- [x] Build binaries
- [x] Build binaries (start all pipelines)
- [x] Download the binaries that have been generated from the Pipeline
build products. They will be deleted within 24 hours.
- [x] Remove fixup commit: `git reset --hard @^`
- [x] Force push `git push -f gitlab`
- [x] Get positive review
- [x] `Do: merge`
# Sign macOS binaries
- [x] Upload to signing server, run script, download resulting .pkg and .dmg files
- [x] Install from .pkg and verify that it is signed with `codesign -dvvv /Applications/ParaView-5.10.0-RC2.app/`
- [x] Install from .dmg and verify that it is signed with `codesign -dvvv /Applications/ParaView-5.10.0-RC2.app/`
# Validating binaries
For each binary, open the Python shell and run the following:
```python
import numpy
s = Show(Sphere())
ColorBy(s, ('POINTS', 'Normals', 'X'))
Show(Text(Text="$A^2$"))
```
Check that
- Getting started guide opens
- Examples load and match thumbnails in dialog
- Python. Open the Python shell and run
- Plugins are present and load properly
- OSPRay raycasting and pathtracing runs
- OptiX pathtracing runs
- IndeX runs
- AutoMPI
Binary checklist
- [x] macOS arm64
- [x] macOS x86\_64
- [x] Linux
- [x] Linux osmesa
- [x] Windows MPI (.exe)
- [x] Windows MPI (.zip)
- [x] Windows no-MPI (.exe)
- [x] Windows no-MPI (.zip)
# Upload binaries
- [x] Upload binaries to `paraview.org` (`rsync -rptv $binaries paraview.release:ParaView_Release/v5.10/`)
- [x] Ask @utkarsh.ayachit to regenerate `https://www.paraview.org/files/listing.txt` and `md5sum.txt` on the website
```
buildListing.sh
updateMD5sum.sh v5.10
```
- [x] Test download links on https://www.paraview.org/download
# Push tags
- [x] In the `paraview` repository, run `git push origin v5.10.0-RC2`.
- [x] In the `paraview-superbuild` repository, run `git push origin v5.10.0-RC2`.
# Spack
- [x] Update Spack package: https://github.com/spack/spack/blob/develop/var/spack/repos/builtin/packages/paraview/package.py
# Post-release
- [x] Post an announcement in the Announcements category on
[discourse.paraview.org](https://discourse.paraview.org/).
- [ ] Request DoD vulnerability scan
/cc @ben.boeckel
/cc @cory.quammen
/cc @utkarsh.ayachit
/cc @charles.gueunetVicente Boleavicente.bolea@kitware.comVicente Boleavicente.bolea@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/21091Block numbering issue with ioss reader remote server2022-04-20T20:57:21-04:00W. Alan ScottBlock numbering issue with ioss reader remote serverWe have an error with block counts with the IOSS reader, remote server. This does not show up in the Exodus reader.
* Linux, master as of November 16 2021, remote server (16 ranks). Does not show up local server.
* Load g1s1. Turn o...We have an error with block counts with the IOSS reader, remote server. This does not show up in the Exodus reader.
* Linux, master as of November 16 2021, remote server (16 ranks). Does not show up local server.
* Load g1s1. Turn off block_1. So, block_2 and block_3 are selected. Apply.
* Right click on block_2, i.e., the upper block, i.e., the red block. it will show as block_3. This is a bug.
* To see what it should show, turn on block_1, and right click on block_2.5.11 (Spring 2022)https://gitlab.kitware.com/paraview/paraview/-/issues/21090PythonShell broken by any custom filter2022-03-11T08:58:19-05:00Mathieu Westphal (Kitware)PythonShell broken by any custom filterHaving a custom filter in the settings break the PythonShell.
Steps to reproduce:
- Open ParaView
- Wavelet, Apply
- Tools -> CreateCustomFilter
- Give it a name, next, next, next, next, finish
- View -> PythonShell
- Click in the pytho...Having a custom filter in the settings break the PythonShell.
Steps to reproduce:
- Open ParaView
- Wavelet, Apply
- Tools -> CreateCustomFilter
- Give it a name, next, next, next, next, finish
- View -> PythonShell
- Click in the python shell
```
[glow@gamma ~/work/paraview/pv1/build]$ ./bin/paraview
Traceback (most recent call last):
File "<console>", line 1, in <module>
File "/home/glow/work/paraview/pv1/build/lib/python3.9/site-packages/paraview/simple.py", line 2918, in <module>
_add_functions(globals())
File "/home/glow/work/paraview/pv1/build/lib/python3.9/site-packages/paraview/simple.py", line 2752, in _add_functions
for key in dir(m):
File "/home/glow/work/paraview/pv1/build/lib/python3.9/site-packages/paraview/servermanager.py", line 2703, in __dir__
s.add(self._getPyName(xml=item["xml"]))
File "/home/glow/work/paraview/pv1/build/lib/python3.9/site-packages/paraview/servermanager.py", line 2681, in _getPyName
assert name
AssertionError
```
FYI @nicolas.vuaille5.10.1 (Winter 2022)https://gitlab.kitware.com/paraview/paraview/-/issues/21089Widget colors should be changeable so they are visible when background is white2022-11-01T21:48:02-04:00Cory Quammencory.quammen@kitware.comWidget colors should be changeable so they are visible when background is whitehttps://gitlab.kitware.com/paraview/paraview/-/issues/21088Server-side timeout command2021-12-21T17:57:01-05:00Thomas GallandServer-side timeout commandpvserver supports a `--timeout=N` argument. This timeout will be shown in the pipeline browser, and count is made the client side. The downside of this method is that the client is unaware of potential resources changes (available time) ...pvserver supports a `--timeout=N` argument. This timeout will be shown in the pipeline browser, and count is made the client side. The downside of this method is that the client is unaware of potential resources changes (available time) on the server side, potentially implying a wrong timeout displayed on the application.
The purpose of this issue is to implement a `--timeout_command=COMMAND` argument for pvserver, which will be regularly executed on the server side. The result of this command will be then send to the client in order to keep updated the timeout value.Thomas GallandThomas Gallandhttps://gitlab.kitware.com/paraview/paraview/-/issues/21087plot over line bug in 5.10rc12022-03-03T22:40:16-05:00Yohann Bearzi (Kitware)plot over line bug in 5.10rc1I'm creating this issue to make sure we test the bug posted [here](plot over line bug in 5.10rc1) once the fix is merged in. Very good instructions are given on the discourse on how to reproduce the issue.I'm creating this issue to make sure we test the bug posted [here](plot over line bug in 5.10rc1) once the fix is merged in. Very good instructions are given on the discourse on how to reproduce the issue.5.10 (Fall 2021)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)