# -*- text -*-
#
# Copyright (c) 2016      Intel, Inc. All rights reserved.
# Copyright (c) 2024-2025 Nanook Consulting  All rights reserved.
# $COPYRIGHT$
#
# Additional copyrights may follow
#
# $HEADER$
#
#
#
[listener-thread-start]
The PMIx server's listener thread failed to start. We cannot
continue.
#
[collection-mismatch]
Collection strategy during a collective operation (e.g., PMIx_Fence)
is not homogeneous - at least one participating node has a
collection strategy (i.e., collect vs non-collect) that differs
from the other nodes. This must be corrected in order for us
to proceed.
#
[bad-singleton]
The PMIx server was given a malformed value for the PMIX_SINGLETON
directive:

  Value: %s

The value must be a string of the form "nspace.rank", where "rank"
is a valid (non-negative) rank - for example, "singleton.0". The
server cannot register the singleton and is unable to continue.
#
[bad-singleton-type]
The PMIx server was given a PMIX_SINGLETON directive of the wrong
data type:

  Given type:    %s
  Required type: PMIX_STRING

The value must be a string of the form "nspace.rank" - for example,
"singleton.0". The server cannot register the singleton and is
unable to continue.
#
[atomic-completion-unsupported]
The host environment answered a request with PMIX_OPERATION_SUCCEEDED,
which is not a permitted return for this operation:

  Operation:   %s

This operation reports a result - the namespace of a job that was
launched, or the data that was requested - and the only channel for
that result is the callback function the PMIx server library supplied.
That library always supplies one. There is therefore no way to return
a result alongside PMIX_OPERATION_SUCCEEDED, and no way for the
requesting process to learn the answer.

A host that has completed the work immediately should invoke the
callback function - it may do so before returning - and return
PMIX_SUCCESS. The request has been failed to its requestor.
