(gnome-ssh-askpass:19421): Gtk-WARNING **: 17:12:29.794: cannot open display: localhost:10.0
error: unable to read askpass response from '/usr/libexec/openssh/gnome-ssh-askpass'
fatal: could not read Username for 'https://open-bitbucket.nrao.edu': No such device or address
Error response from daemon: No such container: wheel-container-test
Error response from daemon: No such container: wheel-container-test
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 6002k  100 6002k    0     0  22.4M      0 --:--:-- --:--:-- --:--:-- 22.7M
[19559] Failed to execute script 'atlutil' due to unhandled exception!
Traceback (most recent call last):
  File "atlutil.py", line 194, in <module>
  File "atlutil.py", line 112, in get_ticket_components
  File "json/__init__.py", line 354, in loads
  File "json/decoder.py", line 339, in decode
  File "json/decoder.py", line 357, in raw_decode
json.decoder.JSONDecodeError: Expecting value: line 12 column 1 (char 11)
[19625] Failed to execute script 'atlutil' due to unhandled exception!
Traceback (most recent call last):
  File "atlutil.py", line 200, in <module>
  File "atlutil.py", line 165, in has_fix_version
  File "json/__init__.py", line 354, in loads
  File "json/decoder.py", line 339, in decode
  File "json/decoder.py", line 357, in raw_decode
json.decoder.JSONDecodeError: Expecting value: line 12 column 1 (char 11)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable.It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
Switched to a new branch 'CAS-14611'
Switched to a new branch 'CAS-14611'
2025-07-09 21:22:41        SEVERE        MPICommandClient::stop_services::MPICommandClient::stop_services::casa        Aborting command request with id# 274: {'command': 'pow(a,b)', 'parameters': {'a': 10, 'b': 100000000000000000}, 'mode': 'eval', 'id': 274, 'server': 1, 'status': 'request sent'}
2025-07-09 21:22:45        SEVERE        MPICommandClient::stop_services::MPICommandClient::stop_services::casa        MPIServers with rank [1] are in timeout condition, skipping MPI_Finalize()
2025-07-09 21:22:45        SEVERE        MPICommandClient::stop_services::MPICommandClient::stop_services::casa        Not possible to finalize gracefully... calling Aborting MPI environment
--------------------------------------------------------------------------
MPI_ABORT was invoked on rank 0 in communicator MPI_COMM_WORLD
  Proc: [[57981,1],0]
  Errorcode: 0

NOTE: invoking MPI_ABORT causes Open MPI to kill all MPI processes.
You may or may not see output from other processes, depending on
exactly when Open MPI kills them.
--------------------------------------------------------------------------
--------------------------------------------------------------------------
prterun has exited due to process rank 0 with PID 5344 on node 8a7f429fa1a9 exiting
improperly. There are three reasons this could occur:

1. this process did not call "init" before exiting, but others in the
job did. This can cause a job to hang indefinitely while it waits for
all processes to call "init". By rule, if one process calls "init",
then ALL processes must call "init" prior to termination.

2. this process called "init", but exited without calling "finalize".
By rule, all processes that call "init" MUST call "finalize" prior to
exiting or it will be considered an "abnormal termination"

3. this process called "MPI_Abort" or "prte_abort" and the mca
parameter prte_create_session_dirs is set to false. In this case, the
run-time cannot detect that the abort call was an abnormal
termination. Hence, the only error message you will receive is this
one.

This may have caused other processes in the application to be
terminated by signals sent by prterun (as reported here).

You can avoid this message by specifying -quiet on the prterun command
line.
--------------------------------------------------------------------------