Known issue with an Unresolved Resolution state is an active problem under investigation; a temporary workaround may be available.
A known issue with a Resolved (workaround) Resolution state is an ongoing problem; a permanent workaround is available which may include using different software or hardware.
A known issue with Resolved Resolution state has been corrected.
| Title | Category | Resolution | Description | Posted | Updated |
|---|---|---|---|---|---|
| Python version mismatch in Jupyter + Spark instance | Software |
Resolved (workaround) |
You may encounter the following error message when running a Spark instance using a custom kernel in the Jupyter + Spark app: 25/04/25 10:49:01 WARN TaskSetManager: Lost task 0.0 in... Read more |
1 month 2 weeks ago | 1 month 2 weeks ago |
| WARN SparkSession in Jupyter + Spark instance | Software |
Resolved (workaround) |
You may encounter the following warning message when running a Spark instance using the default PySpark kernel in a Jupyter + Spark application: WARN SparkSession: Using an... Read more |
1 month 2 weeks ago | 1 month 2 weeks ago |
| Singularity: failed to run a container directly or pull an image from Singularity or Docker hub | Software |
Resolved (workaround) |
You might encounter an error while run a container directly from a hub: [pitzer-login01]$ apptainer run shub://vsoch/hello-world Progress |===================================| 100.0%... Read more |
1 month 2 weeks ago | 1 month 2 weeks ago |
| Singularity: failed to pull a large Docker image | Software |
Resolved (workaround) |
You might encounter an error while pulling a large Docker image: [pitzer-login01]$ apptainer pull docker://qimme2/core FATAL: Unable to pull docker://qiime2/core While running... Read more |
1 month 2 weeks ago | 1 month 2 weeks ago |
| Singularity: reached your pull rate limit | Software |
Resolved (workaround) |
You might encounter an error while pulling a large Docker image: ERROR: toomanyrequests: Too Many Requests. or You have reached your pull rate limit. You may... Read more |
4 years 2 weeks ago | 1 month 2 weeks ago |
| MPI-IO issues on home directories with Intel MPI 2019.3 | Pitzer, Software |
Resolved (workaround) |
Certain MPI-IO operations with |
1 month 2 weeks ago | 1 month 2 weeks ago |
| Using mpiexec/mpirun with Intel MPI on Slurm | Software |
Resolved (workaround) |
Intel MPI on Slurm batch system is configured to support PMI process manager. It is recommended to use |
1 month 2 weeks ago | 1 month 2 weeks ago |
| A partial-node MPI job failed to start using Intel MPI mpiexec | Owens, Pitzer, Software |
Resolved (workaround) |
A partial-node MPI job may fail to start using [mpiexec@o0439.ten.osc.... Read more |
4 years 8 months ago | 1 month 2 weeks ago |
| GCC 13 compilation errors due to missing headers | Cardinal, Pitzer, Software |
Resolved (workaround) |
Users may encounter the following errors when compiling a C++ program with GCC 13: error: 'uint64_t' in namespace 'std' does not name a type or error: 'std::... Read more |
8 months 2 weeks ago | 1 month 2 weeks ago |
| starccm/15.02.007 with intelmpi after Mar 22, 2022 |
Resolved (workaround) |
STAR-CCM+ 15.02.007 and 15.02.007-mixed with intelMPI would fail on multiple node jobs after the downtime on Mar 22, 2022. Please use openmpi instead. You can find more... Read more |
3 years 3 months ago | 1 month 2 weeks ago |
