Weird "failed process" after upgrading pandas

I am new to using DL and I am testing it with a project that require pandas 1.5.x. Currently installed version was below 1.5.x, so I attempted to upgrade it to 1.5.2 (using pip on the Environment interface, without any edit to the I received a weird failure message following a long wait time after confirmation in logs that 1.5.2 was successfully installed. I was confused, thinking that the installation was not successful, so I attempted to upgrade a few more times, to different versions (2.0.0, 1.5.2, etc).

My last attempt was from 1.5.2 to 1.5.3, and the same weird message appeared after the same long wait time following the “Successfully installed” message. This time, I checked my code that require pandas 1.5.x and it worked. Below is the log:

Collecting pandas==1.5.3
Using cached pandas-1.5.3-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (12.2 MB)
Requirement already satisfied: numpy>=1.20.3 in /opt/python/envs/default/lib/python3.8/site-packages (from pandas==1.5.3) (1.23.5)
Requirement already satisfied: pytz>=2020.1 in /opt/python/envs/default/lib/python3.8/site-packages (from pandas==1.5.3) (2022.7.1)
Requirement already satisfied: python-dateutil>=2.8.1 in /opt/python/envs/default/lib/python3.8/site-packages (from pandas==1.5.3) (2.8.2)
Requirement already satisfied: six>=1.5 in /opt/python/envs/default/lib/python3.8/site-packages (from python-dateutil>=2.8.1->pandas==1.5.3) (1.16.0)
Installing collected packages: pandas
Attempting uninstall: pandas
Found existing installation: pandas 1.5.2
Uninstalling pandas-1.5.2:
Successfully uninstalled pandas-1.5.2
Successfully installed pandas-1.5.3
Invalid operation id: c69a7e0b-3a1d-447e-ab68-5c89bcdb481c

Now that I noticed the failure was for an operation after successful install, all my upgrade attempts might have been successful, but I was confused by that last process at the end that never succeeded. I’m thinking that this might be a problem or a bug.

This does not seem to be mission-critical, but I guess it will avoid confusions for the users.