Job dependencies separated by "?" (OR'ed) should make the dependant job
be independent as soon as any of the dependencies are resolved to be
satisfied. Without this patch, if an invalid (non satisfiable)
dependency was resolved before a satisfiable one, then the dependant job
would never become independent, even after the satisfiable one got
eventually resolved.

Bug 5851.

Bug 6750.

Bug 6710.

Change to %pJ identifier while here and merge different partition
priorities into a single log message line.

Bug 6663.

Bug 6723

Regression from enhancement 4506.

Bug 6680

Bug 6662

Previously the state reason could remain as WAIT_NO_REASON even after
backfill evaluation. This should improve system feedback/responsiveness
user perception.

Bug 6594.

Continuation of 69d78159

Bug 6500

Issue was from ade9101e.

The problem was an over simplified if statement which when ran multiple
times would set the start time incorrectly.

Bug 6697

Even if main scheduler doesn't allocate resources for hetjobs, the
queue list should be composed by all types of jobs. Otherwise, lower
priority regular jobs could be allocated resources by main scheduler
while higher priority hetjobs are waiting for a backfill cycle.

Bug 6593.

Bug 6679

Instruct the backfill scheduler to attempt to start a heterogeneous job
as soon as all of its components are determined able to do so.

Bug 5579.

There are at least two points where this can return a false positive
error message which can be confusing for users.

Continuation dc583bd1

Bug 6437

Backport of 21b9a39b

Bug 6625

Print error: for each new line.

Bug 6142

Bug 6142

Bug 6584

response_cluster_rec stored a pointer to data in the controller config
that gets freed when the controller is reconfigured.

Bug 6584

This should never happen, but is a nice safeguard.

Bug 6566

Bug 6612

All of the buffers are 24 characters, require the input string is
less than 23 characters and null combined to be parsed.

Remove regression added in b9699c2f

Bug 6636.

What was happening in a maintenance reservation was every 5 seconds
the slurmctld was sending a message to the slurmdbd telling it the
node's down/drain state was in a maintenance state as well.  We really
only needed to know about this once.

Bug 6487

(DRAIN+MAINT+IDLE) Before it would just print MAINT
Bug 6487

Bug 4296

to avoid having to send alias list for cloud nodes that exist in DNS.
This is especially important for large cloud environments (e.g.
thousands of nodes) as the alias list environment will be too large for
execve().

Bug 6589

Bug 6587

This is useful in a cloud environment where the nodes come and go out of
DNS.

Bug 6592

Bug 6519.

Continuation of 324404de

Bug 6433

Continuation of c2cdde85

Bug 6433

Same as salloc/sbatch --gres option.

Bug 6582.

salloc --no-shell jobs aren't interactive, and won't respond to pings
from the slurmctld, so they were previously getting killed after
InactiveLimit seconds, even when they had a running step. InactiveLimit
no longer applies for salloc --no-shell jobs.

Bug 6560.

Fixes smail to handle change in slurmctld/agent.c#mail_job_info() output
introduced in commit 5f1cc8a8.
seff has incomplete job array support, but if one happens to come through
smail, at least let it print out what it can (i.e. the last array task in
the job array).

Bug 6536

Allow sites to use hostname as given by libc gethostname() instead of
the first domain used globally as hostname.

Bug 6532.

Co-authored-by: Nate Rini <nate@schedmd.com>

Causes x11_delete_xauth() to be called on a successfully unlink()'d
file if using local_xauthority causing an extra error message in the
logs.

Bug 3647.

Also set canonical links in the man pages while here.

Bug 6573.