ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2021-12-22T19:11:08-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/21069Pipeline source gets stuck in broken state when REQUEST_DATA_OBJECT fails (v5...2021-12-22T19:11:08-05:00Lutz HofmannPipeline source gets stuck in broken state when REQUEST_DATA_OBJECT fails (v5.10.0-RC1)When the REQUEST_DATA_OBJECT request fails once for a filter in the pipeline, the pipeline source seems to get stuck in some invalid state where it is never updated again, even if its input is changed.
This does not seem happen for any ...When the REQUEST_DATA_OBJECT request fails once for a filter in the pipeline, the pipeline source seems to get stuck in some invalid state where it is never updated again, even if its input is changed.
This does not seem happen for any other request (REQUEST_INFORMATION, REQUEST_UPDATE_EXTENT, etc), where the pipeline source keeps working as expected even if such a request fails.
I originally discovered this bug when using "Extract Subset" on a filter that can change its output data object (e.g. Programmable Source), where the output data type changed from vtkImageData to vtkTable and back.
A "constructed" example is attached below.
Tested with v5.10.0-RC1. The issue is not present in v5.9.1.
### To Reproduce
(see screen capture below)
1. Load the following Python plugin: [MyFilter.py](/uploads/ff7418c97e0f3de866bbe96e63aaa0be/MyFilter.py)
<details><summary>My Filter</summary>
```python
from vtkmodules.vtkCommonDataModel import vtkDataObject, vtkDataSet
from vtkmodules.util.vtkAlgorithm import VTKPythonAlgorithmBase
from paraview.util.vtkAlgorithm import smproxy, smproperty, smdomain
from datetime import datetime
@smproxy.filter(label="My Filter")
@smproperty.input(name="Input")
class MyFilter(VTKPythonAlgorithmBase):
def __init__(self):
self._request_data_object_fail = False
self._dummy = False
VTKPythonAlgorithmBase.__init__(self)
@smproperty.intvector(label='RequestDataObject Fail', default_values=0)
@smdomain.xml('<BooleanDomain name="bool"/>')
def SetRequestDataObjectFail(self, b):
self._request_data_object_fail = b
self.Modified()
@smproperty.intvector(label='Dummy', default_values=0)
@smdomain.xml('<BooleanDomain name="bool"/>')
def SetDummy(self, b):
self._dummy = b
self.Modified()
def RequestDataObject(self, request, inInfo, outInfo):
if self._request_data_object_fail:
return 0
inp = vtkDataSet.GetData(inInfo[0], 0)
if not inp:
return 0
for i in range(self.GetNumberOfOutputPorts()):
output = vtkDataSet.GetData(outInfo, i)
if not output or not output.IsA(inp.GetClassName()):
outInfo.GetInformationObject(i).Set(
vtkDataObject.DATA_OBJECT(), inp.NewInstance())
return 1
def RequestData(self, request, inInfo, outInfo):
input0 = vtkDataSet.GetData(inInfo[0])
output = vtkDataSet.GetData(outInfo)
output.ShallowCopy(input0)
print('RequestData', datetime.now())
return 1
```
</details>
2. Create a few sources, attach "My Filter" to one of them
3. Checking/unchecking the "Dummy" property updates the filter as expected
4. Checking "RequestDataObject Fail" causes REQUEST_DATA_OBJECT to fail
5. Unchecking "RequestDataObject Fail" does not execute the filter anymore; changing the "Dummy" property also does not update it
6. Changing the filter's input does not recover its state (so far I have found no method that returns to a valid state)
![Peek_2021-10-29_10-49](/uploads/e4ee65f2cb046a627b00c5df0442c871/Peek_2021-10-29_10-49.gif)https://gitlab.kitware.com/paraview/paraview/-/issues/15880Command line help is broken2021-12-22T20:07:31-05:00Kitware RobotCommand line help is broken**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15880). Further discussion may take place here.**
---
Command line help is broken for ParaView, especially on Windows. There re...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15880). Further discussion may take place here.**
---
Command line help is broken for ParaView, especially on Windows. There really are three issues. - one Windows specific, the other two are general.
* On Windows, a user should be able to open a Command Prompt, cd to the ParaView executable, and run paraview --help. This should show in the command prompt window OR in a window that opens up and stays open. Currently, help is written to a ParaView window, and immediately ParaView will close, also closing this help window.
* The ParaView command line arguments are confusing. If an input does not have a command associated with it (such as -dr or --help), we assume it is a file. Thus, if you try to get help, and don't know the command, ParaView just assumes it is a file to open. It says no such file. For instance, 'paraview -h' will fail loading the -h file. Please change this to either always require a file command (maybe -f), or if the file is read in from the command line, and doesn't exist (or starts with a -), print out the command line help.
* We are inconsistent with ParaView command line arguments. Help is the most obvious example. Please add a -h command for help.5.11 (Spring 2022)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19327FXAA has no effect on Eye dome lighting2021-12-23T13:05:10-05:00Jonathan BorduasFXAA has no effect on Eye dome lightingDear users/devs of the Eye Dome Lighting plugin: @patchett2002 @ethan.stam @demarle @utkarsh.ayachit,
The FXAA seems to have no effects on the hard edge anti-aliasing of an Eye Dome Lighting View port.
When zooming out, the aliasing e...Dear users/devs of the Eye Dome Lighting plugin: @patchett2002 @ethan.stam @demarle @utkarsh.ayachit,
The FXAA seems to have no effects on the hard edge anti-aliasing of an Eye Dome Lighting View port.
When zooming out, the aliasing effects can be quite important (opaque purple surface on transparent grey surface).
![image](/uploads/1748e72854fca17869da94d9f3f57aa9/image.png)
The same setup using a screenshot export in 4K resolution creates a good result:
![image](/uploads/137047f49c0b9094cb46c954c4540c82/image.png)
If both surface are opaque, the anti-aliasing is acceptable:
![image](/uploads/8de47147b485f0aaca8e798c5a6c9f95/image.png)
Is it normal that a opaque/transparent combination increase drastically the aliasing effects ?
Is there a setting to reduce the aliasing ?
I am testing on ParaView-latest-MPI-Windows-Python3.7-msvc2015-64bit.exeSankhesh JhaveriSankhesh Jhaverihttps://gitlab.kitware.com/paraview/paraview/-/issues/20013Set View Direction icons don't show direction2021-12-23T17:07:41-05:00Dan LipsaSet View Direction icons don't show directionThe Set View Directions -Z and +Z don't show the direction of the Z axis.
While you can see that both -Z and +Z are parallel with the viewing direction (perpendicular on the screen) you don't know which is pointing toward the user and wh...The Set View Directions -Z and +Z don't show the direction of the Z axis.
While you can see that both -Z and +Z are parallel with the viewing direction (perpendicular on the screen) you don't know which is pointing toward the user and which is pointing toward the screen.
This can be fixed by having the X and Y axes overlap the Z axis when Z is pointing toward that screen (+Z).
The same issue is true for -X, +X and -Y, +Y icons.https://gitlab.kitware.com/paraview/paraview/-/issues/20571ParaView Python Script Editor tab issues on macos2021-12-27T04:57:15-05:00Cory Quammencory.quammen@kitware.comParaView Python Script Editor tab issues on macosThere are some issues with the multi-tab Python script editor on macos.
1. Go to Tools -> Python Script Editor. Default new tab has a strange X that isn't needed. Hovering over the X, a tooltip that says "Close Tab" pops up.
![image](/...There are some issues with the multi-tab Python script editor on macos.
1. Go to Tools -> Python Script Editor. Default new tab has a strange X that isn't needed. Hovering over the X, a tooltip that says "Close Tab" pops up.
![image](/uploads/5627e06ed961d448024ed9c70e3d7e22/image.png)
2. When you save a file, the Python Script Editor is moved behind the main window. It is still open, it just disappears. Very unexpected.
3. Open the Python Script Editor. Type some text in the first tab and save it to a file. Now click the + sign to add a new tab. Try to go back and click on the tab for the file that was just saved. Clicking on top of the text with the file path does nothing. You need to click on the space between the file path and the close button for the tab to be activated. If you haven't saved the text in an editor, you can click on the "New File" text and that tab is made active. Very unexpected
![image](/uploads/72698add4055b52269f0fd69b2151893/image.png)Mathieu Westphal (Kitware)Mathieu Westphal (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/20693Reset Camera Closest is broken2021-12-27T06:04:47-05:00W. Alan ScottReset Camera Closest is brokenZoom close to data is way broken. Here is how to replicate it:
* Master, Linux, builtin server.
* Make ParaView's renderview window about twice as wide as it is tall. In File/ Save Screenshot, I have 1842X897.
* Sources/ Cylinder. App...Zoom close to data is way broken. Here is how to replicate it:
* Master, Linux, builtin server.
* Make ParaView's renderview window about twice as wide as it is tall. In File/ Save Screenshot, I have 1842X897.
* Sources/ Cylinder. Apply.
* Reset. +Y.
* Adjust Camera. Elevation = 35. Azimuth = 35.
* Reset Camera Closest.
![Screen_Shot_2021-05-04_at_4.53.13_PM](/uploads/7bfc9c015ebcebccc2441e2c428ef432/Screen_Shot_2021-05-04_at_4.53.13_PM.png)5.11 (Spring 2022)https://gitlab.kitware.com/paraview/paraview/-/issues/21154Incremental Trace Scroll to Bottom Not Working2022-01-04T17:18:03-05:00Theodore BaltisIncremental Trace Scroll to Bottom Not WorkingApplies to 5.10
Incremental Trace window no longer scrolls to the bottom as code is added. It seems to always reset to about 60% of the way down.
Was behaving as expected in 5.10 RC2.Applies to 5.10
Incremental Trace window no longer scrolls to the bottom as code is added. It seems to always reset to about 60% of the way down.
Was behaving as expected in 5.10 RC2.https://gitlab.kitware.com/paraview/paraview/-/issues/20864Saving screenshot with transparent background not working2022-01-06T13:21:43-05:00Utkarsh AyachitSaving screenshot with transparent background not workingSaving screenshot with transparent background not workingSaving screenshot with transparent background not working5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/21160CMake error 'cmake_path' not found when PARAVIEW_USE_PYTHON=ON2022-01-07T07:41:25-05:00Menno Deij - van RijswijkCMake error 'cmake_path' not found when PARAVIEW_USE_PYTHON=ONI'm using CMake version 3.18. When I configure paraview with CMake and use `PARAVIEW_USE_PYTHON=ON`, I get an error about missing `cmake_path`. This command was added in CMake 3.20.
```
CMake Error at VTK/CMake/patches/3.23/FindPython/S...I'm using CMake version 3.18. When I configure paraview with CMake and use `PARAVIEW_USE_PYTHON=ON`, I get an error about missing `cmake_path`. This command was added in CMake 3.20.
```
CMake Error at VTK/CMake/patches/3.23/FindPython/Support.cmake:3053
```https://gitlab.kitware.com/paraview/paraview/-/issues/17343Icons are too small2022-01-10T06:15:11-05:00W. Alan ScottIcons are too smallWith ParaView 5.3.0, icons became much smaller. Users are complaining (and I agree) that they are now hard to find. Please increase their size to what we had before. Further, the icons for selection really are an eye test for anyone o...With ParaView 5.3.0, icons became much smaller. Users are complaining (and I agree) that they are now hard to find. Please increase their size to what we had before. Further, the icons for selection really are an eye test for anyone older than 40. Could we increase their size somewhat?
Related issues: #15922, #18235.5.10 (Fall 2021)Shawn WaldonShawn Waldonhttps://gitlab.kitware.com/paraview/paraview/-/issues/21179QtTesting QToolButton isn't supported2022-01-18T04:45:35-05:00Lucas GivordQtTesting QToolButton isn't supportedIt seems that QtTesting play event doesn't really support QToolButton.
How to reproduce :
- Create a xml test on 'Toggle column visibility' in spreadSheet
![Screenshot_from_2022-01-17_11-06-06](/uploads/bf39ccfe87e4d63411c91276d4a89dec/...It seems that QtTesting play event doesn't really support QToolButton.
How to reproduce :
- Create a xml test on 'Toggle column visibility' in spreadSheet
![Screenshot_from_2022-01-17_11-06-06](/uploads/bf39ccfe87e4d63411c91276d4a89dec/Screenshot_from_2022-01-17_11-06-06.png)
- play this test or used ctest, the test will not end until the user clicks somewhere or the timeout is reached.https://gitlab.kitware.com/paraview/paraview/-/issues/19832Enhancement Request: Remember Last Values in Generate Number Series Dialog2022-01-18T09:27:56-05:00Joel A. KuleszaEnhancement Request: Remember Last Values in Generate Number Series Dialog# Summary
The "Generate Number Series" dialog that is used, for example, to define contour levels should remember the last-entered values for range minimum, range maximum, type, and number of samples. This will permit a user to easily...# Summary
The "Generate Number Series" dialog that is used, for example, to define contour levels should remember the last-entered values for range minimum, range maximum, type, and number of samples. This will permit a user to easily iterate toward a set of levels appropriate to their need without undue rework to specify values unlikely to change (e.g., type) or recall of previously tried values.
# Example
The dialog window attached below repeatedly defaults to the given range, type, and number of samples despite specifying different values.
Note that the contour level preview is *excellent*; however, it displays poorly on my system (specs follow).
Screenshot from ParaView 5.8.0 on macOS 10.14.6 13" MacBookPro 2560x1600 display scaled to "More Space" in the display properties.
![Screen_Shot_2020-04-07_at_11.30.02](/uploads/272fb699605ca002d1ff7acb793d880c/Screen_Shot_2020-04-07_at_11.30.02.png)
CC: @patchett2002 @ethan.stam5.9 (Fall 2020)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/15037Wiki - show how to start a remote server2022-01-18T17:31:12-05:00Kitware RobotWiki - show how to start a remote server**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15037). Further discussion may take place here.**
---
Please update the wiki to show the very common case where a local client c...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15037). Further discussion may take place here.**
---
Please update the wiki to show the very common case where a local client connects to a remote server. This remote server should be automatically started (not manually started by the user). Further, the server actually gets started from a login node. Use reverse connect, since this is very common. Add a second example, where ports are forwarded. (This one is complex.) Ask me for details, if needed.
The executive summary is as follows:
* A local script will ssh into the remote cluster login node, and run a server script. The local script will then start paraview, waiting for a connection.
* The remote script (running on the login node) will write an auto-generated script, written into /tmp. It then does a qsub, with this auto-gen script as input.
* The auto-gen script is now being run on the compute nodes, and starts pvserver with correct arguments.
For the case of port forwarding reverse connect, the only way I have ever gotten this to work is to have the cluster side script start an ssh back to the client machine. The issue here is that the client doesn't know what the compute node names will be when it starts - only the compute nodes know their names.
For the case of port forwarding forward connect, it is crazy. The client doesn't know the name of compute node 0, so you have to start the servers first. That cluster script then figures out it's node 0 name, and sends that back to the client side (I have done this as s scp file). After waiting an appropriate number of seconds (or some type of polling loop), have the client side read the compute node 0 name, and connect to it.5.10 (Fall 2021)https://gitlab.kitware.com/paraview/paraview/-/issues/21177ParaView CRASH when %s is used in automatic label format2022-01-19T04:39:03-05:00Menno Deij - van RijswijkParaView CRASH when %s is used in automatic label formatI was trying to see if I could get strings instead of numbers on legends, so I tried to fill in `%s` in the Edit Color Legend Properties dialog, in the Field for 'Automatic label format'. When I did that, ParaView v5.9.1 crashed.
Now, I...I was trying to see if I could get strings instead of numbers on legends, so I tried to fill in `%s` in the Edit Color Legend Properties dialog, in the Field for 'Automatic label format'. When I did that, ParaView v5.9.1 crashed.
Now, I still do not know if I can get a string label for a categorical color legend, and if so how to do that. But ParaView shouldn't crash when %s is used.https://gitlab.kitware.com/paraview/paraview/-/issues/21138Release ParaView 5.10.02022-01-27T20:32:56-05:00Vicente Boleavicente.bolea@kitware.comRelease ParaView 5.10.0# 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`.
- 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] Update `version.txt` and tag the commit (tag this commit below)
```
git checkout -b update-to-v5.10.0 af5a2d82e9
echo 5.10.0 > version.txt
git commit -m 'Update version number to 5.10.0' 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
- [ ] ~~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 '5.10.0' v5.10.0 @BRANCHPOINT@`
- Create tarballs
- [x] ParaView (`Utilities/Maintenance/create_tarballs.bash --txz --tgz --zip -v v5.10.0`)
- 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
git checkout -b update-to-v5.10.0
```
- Integrate changes.
- 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
- [x] ARG SUPERBUILD_TAG=v5.10.0
- [x] ARG PARAVIEW_VERSION_STRING=paraview-5.10
- [x] Commit changes
- [x] `git add versions.cmake CMakeLists.txt Scripts/docker/ubuntu/development/Dockerfile`
- [x] `git commit -m "Update the default version to 5.10.0"`
- [x] Created tag: `git tag -a -m 'ParaView superbuild 5.10.0' v5.10.0 HEAD`
- Force `5.10.0` 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" CACHE STRING "Force version to 5.10.0" FORCE)
set(paraview_FROM_SOURCE_DIR OFF CACHE BOOL "Force source dir off" FORCE)
```
- [x] Create fixup commit `git commit -a --fixup=@`
- Make a commit for each of these `release`-only changes
- [ ] ~~Update `.gitlab/ci/cdash-groups.json` to track the `release` CDash
groups (if `release` is `master`)~~
- 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] Get positive review
- [x] Remove fixup commit: `git reset --hard @^`
- [x] Force push `git push -f gitlab`
- [x] `Do: merge`
- Software process updates (these can all be done independently)
- [ ] ~~Update kwrobot with the new `release` branch rules (@ben.boeckel)~~
- [ ] ~~Run [this script][cdash-update-groups] to update the CDash groups~~
- This must be done after a nightly run to ensure all builds are in the
`release` group
- See the script itself for usage documentation
- [ ] ~~Add (or update if `release` is `release`) version selection entry
in paraview-superbuild~~
# 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.app/`
- [x] Install from .dmg and verify that it is signed with `codesign -dvvv /Applications/ParaView-5.10.0.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 @sebastien.jourdain
- [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`.
- [x] In the `paraview-superbuild` repository, run `git push origin v5.10.0`.
# Spack
- [x] Update Spack package: https://github.com/spack/spack/blob/develop/var/spack/repos/builtin/packages/paraview/package.py
- https://github.com/spack/spack/pull/28121
# Update documentation
- [x] Submit a Merge Request that updates the version to 5.10.0 in https://gitlab.kitware.com/paraview/paraview-docs/-/blob/master/doc/source/conf.py` for `paraview-docs`
- [x] Upload versioned documentation to `https://github.com/kitware/paraview-docs` (see `https://github.com/Kitware/paraview-docs/blob/master/README.md`)
- [x] Tag the [ParaView docs](https://gitlab.kitware.com/paraview/paraview-docs/-/tags) with v5.10.0.
- [x] Activate the tag on [readthedocs](https://readthedocs.org/projects/paraview/versions/) and build it [here](https://readthedocs.org/projects/paraview/)
- [x] Go to readthedocs.org and activate
- [x] Write and publish blog post with release notes.
- [x] Update release notes
(https://www.paraview.org/Wiki/ParaView_Release_Notes)
# Post-release
- [x] Post an announcement in the Announcements category on
[discourse.paraview.org](https://discourse.paraview.org/).
- [x] Request DoD vulnerability scan
- [x] Request update of version number in "Download Latest Release" text on www.paraview.org
- [x] Request update of link to ParaView Guide PDF at https://www.paraview.org/paraview-guide/
- [x] Move unclosed issues to next release milestone in GitLab
/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/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/21221ParaView crashes on load state with shorter file series2022-02-04T10:48:08-05:00Martin Leonhard KliemankParaView crashes on load state with shorter file seriesI hope I'm doing this right, sorry if not:
When choosing load state and selecting the files manually, ParaView will try to load as many files as there were in the original file series. If the new file series is of shorter length (fewer ...I hope I'm doing this right, sorry if not:
When choosing load state and selecting the files manually, ParaView will try to load as many files as there were in the original file series. If the new file series is of shorter length (fewer files) then ParaView will become unresponsive and then crash.
Manually editing the state file to expect fewer files (for example 10) circumvents this issue, but it would be great if ParaView could check the lenght of the new file series itself and adjust the state accordingly. This would make it easier to reuse state files, especially when the original dataset has been deleted.https://gitlab.kitware.com/paraview/paraview/-/issues/21215Crash on PIO reader when resetting session (sometimes)2022-02-07T18:33:20-05:00Yohann Bearzi (Kitware)Crash on PIO reader when resetting session (sometimes)When resetting the session, the PIO reader sometimes crash. Here's how to reproduce:
* Load `simple.pio`
* Apply
* Reset Sessiom
* Load `simple.pio`
* Apply
-> Sometimes crashesWhen resetting the session, the PIO reader sometimes crash. Here's how to reproduce:
* Load `simple.pio`
* Apply
* Reset Sessiom
* Load `simple.pio`
* Apply
-> Sometimes crashesCaitlin RossCaitlin Rosshttps://gitlab.kitware.com/paraview/paraview/-/issues/20986Link to examples incorrect on MacOS2022-02-08T08:09:55-05:00W. Alan ScottLink to examples incorrect on MacOSThe link to examples is wrong on MacOS in the nightly.
* Download from paraview.org today's nightly for MacOS.
* File/ Open/ Examples. This directory does not exist.
The reason is that this download (today, anyway) is called 5.9.1-...The link to examples is wrong on MacOS in the nightly.
* Download from paraview.org today's nightly for MacOS.
* File/ Open/ Examples. This directory does not exist.
The reason is that this download (today, anyway) is called 5.9.1-1912-g7b0eaa52aa, thus downloads into /Applications/ParaView-5.9.1-1912-g7b0eaa52aa/, but is looking for the examples directory in /Applications/ParaView-5.9.1-1834-gdb1a226a72.app/Contents/examples/. The version is not being updated.
Marking as showstopper. If RC1 is good, showstopper can be replaced with required for the 5.11 release.5.10 (Fall 2021)https://gitlab.kitware.com/paraview/paraview/-/issues/21142Doxygen job does not upload in new tagged commits2022-02-09T20:28:54-05:00Vicente Boleavicente.bolea@kitware.comDoxygen job does not upload in new tagged commitsThis can be seen in the past RC release and the last release for 5.10.0This can be seen in the past RC release and the last release for 5.10.0Vicente Boleavicente.bolea@kitware.comVicente Boleavicente.bolea@kitware.com