And would prevent transmission of a file.

Bug 4787.

Used in a single location, and the code without it is simpler
when its removed anyways. Remove awkwardly named and presumably
unused slurm_xslurm_strerrorcat() API function as well.

These calls are apparently quite expensive on larger databases,
and nothing requires that the association id number not have any
skipped values. So stop doing this.

Performance problems first reported by Jessica Nettelblad.

Bug 4785.

Bug 4736
Bug 4784

Partial write can happen under high system load, leading to step
termination when finishing the write would let the step launch
properly instead.

Fix suggested by Matthieu Hautreux.

Bug 4778.

See GoogleDoc for current information

Add a privilege check for when an unprivileged user tries to modify
a resource. Min level set to Operator.

Bug 4735.

Bug 4747.

Default --list_reasons format is "%20E %9u %19H %N"

Bug 4762

Fixes some issues around differences in lua package naming.

Bug 4568.

Reformat comment blocks to respect 80-columns
and /* comment */ format conventions.

bug 3445

in jobid2str when debuglevel >= debug

Bug 4603

Bug 4681.

Bug 4709.

Bug 4646

Change function name from node_features_p_changible_feature() to
    node_features_p_changeable_feature in node_features plugin.
bug 4744

Report all SPANK validations that fail, not just the first one
Log local and remote plugstack.conf file checksum to identify
  possible file system delay issues
bug 4694

Previously it was taking the MIN, without respecting the order.

Also add a note to the resource_limits.html page to clarify the
exception for Max[Wall|Time] and/or [Max|Min]Nodes limits, where
the default is that the Partition is the king with regards of
precedence, unless the respective job's QOS flags
Partition[Min|Max|Time]Limit are set.

Bug 4681.

This prevents a hard-to-diagnose issue where slurmstepd may fail
to start due to a missing library. This now ensures slurmd will
fail, and keep the node down until the library issue can be fixed.

Bug 4645, 4644.

fatal() calls exit(1) which precludes getting a backtrace.
That's fine on configuration issues and other types of problem,
but for hitting "impossible" edge cases getting a core dump may
be the only way to isolate the issue.

Adding to 17.11 so we can easily provide diagnostic patches without
needing users to back-port this implementation. Further use will
come in 18.08.

Bug 4599.