<commit_before>%%%      PLEASE RUN A SPELL CHECKER BEFORE COMMITTING YOUR CHANGES!
%%%      PLEASE RUN A SPELL CHECKER BEFORE COMMITTING YOUR CHANGES!
%%%      PLEASE RUN A SPELL CHECKER BEFORE COMMITTING YOUR CHANGES!
%%%      PLEASE RUN A SPELL CHECKER BEFORE COMMITTING YOUR CHANGES!
%%%      PLEASE RUN A SPELL CHECKER BEFORE COMMITTING YOUR CHANGES!

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{\label{sec:History-7-9}Development Release Series 7.9}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

This is the development release series of HTCondor.
The details of each version are described below.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\subsection*{\label{sec:New-7-6-0}Version 7.9.5}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

\noindent Release Notes:

\begin{itemize}

\item HTCondor version 7.9.5 not yet released.
%\item HTCondor version 7.9.5 released on Month Date, 2013.

\end{itemize}


\noindent New Features:

\begin{itemize}

\item Allow the number of bits in a delegated proxy to be specified
by the receiving side using \Macro{GSI\_DELEGATION\_KEYBITS}
\Ticket{3503}

\item When there are multiple users
waiting to transfer files within the limits set by
configuration variables
\Macro{MAX\_CONCURRENT\_UPLOADS} and/or
\Macro{MAX\_CONCURRENT\_DOWNLOADS}, the scheduling algorithm
now gives the users
an equal share of the transfer slots.  How shares are counted can be
configured with \Macro{TRANSFER\_QUEUE\_USER\_EXPR}.
\Ticket{3487}

\item When using the \Opt{-remote} or \Opt{-spool} options to
\Condor{submit}, the job owner will be set by the \Condor{schedd} based
on how you were authenticated. This will make it easier to submit jobs
to a remote \Condor{schedd} where your credentials may map to a different
account name.
\Ticket{3370}

\end{itemize}

\noindent Configuration Variable and ClassAd Attribute Additions and Changes:

\begin{itemize}

\item When using file transfer concurrency limits, additional I/O
  usage statistics are now published in the ClassAd of the
  \Condor{schedd}.  This includes the sum and rate of bytes
  transferred as well as time spent reading and writing to files and
  to the network.  These statistics are reported for the sum of all
  users and individually for recently active users.  The ClassAd
  attributes are described below.  Each of these may be prefixed by a
  username (e.g. \AdAttr{username\_FileTransferUploadBytes}).  In this
  case, it represents activity by the specified user.  The published
  username is actually the file transfer queue name, as defined by
  \Macro{TRANSFER\_QUEUE\_USER\_EXPR}.  This expression defaults to
  the name of the job owner.  The attributes that are rates have a
  suffix that specifies the timespan of the exponential moving
  average.  By default the timespans that are published are 1m, 5m,
  1h, and 1d.  This can be changed by configuring
  \Macro{TRANSFER\_IO\_REPORT\_TIMESPANS}.  These attributes are only
  reported once a full timespan has accumulated.

\begin{description}

\item[\AdAttr{FileTransferUploadBytes}] Total number of bytes uploaded
  as input to jobs since this \Condor{schedd} was started.

\item[\AdAttr{FileTransferUploadBytesPerSecond\_<timespan>}]
  Exponential moving average over the specified timespan of the rate
  at which bytes have been uploaded as input to jobs.

\item[\AdAttr{FileTransferDownloadBytes}] Total number of bytes
  downloaded as output from jobs since this \Condor{schedd} was
  started.

\item[\AdAttr{FileTransferDownloadBytesPerSecond\_<timespan>}]
  Exponential moving average over the specified timespan of the rate
  at which bytes have been downloaded as output from jobs.

\item[\AdAttr{FileTransferFileReadSeconds}] Total number of
  submit-side transfer process seconds spent reading from files to be
  transferred as input to jobs since this \Condor{schedd} was started.

\item[\AdAttr{FileTransferFileReadLoad\_<timespan>}] Exponential
  moving average over the specified timespan of the rate at which
  submit-side file transfer processes have spent time reading from
  files to be transferred as input to jobs.  One file transfer process
  spending nearly all of its time reading files will generate a load
  close to 1.0.

\item[\AdAttr{FileTransferFileWriteSeconds}] Total number of
  submit-side transfer process seconds spent writing to files
  transferred as output from jobs since this \Condor{schedd} was
  started.

\item[\AdAttr{FileTransferFileWriteLoad\_<timespan>}]
  Exponential moving average over the specified timespan of the rate
  at which submit-side file transfer processes have spent time writing to files
  transferred as output from jobs.  One file transfer process spending
  nearly all of its time writing to files will generate a load close
  to 1.0.

\item[\AdAttr{FileTransferNetReadSeconds}] Total number of submit-side
  transfer process seconds spent reading from the network when
  transferring output from jobs since this \Condor{schedd} was
  started.

\item[\AdAttr{FileTransferNetReadLoad\_<timespan>}] Exponential moving
  average over the specified timespan of the rate at which submit-side
  file transfer processes have spent time reading from the network
  when transferring output from jobs.  One file transfer process
  spending nearly all of its time reading from the network will
  generate a load close to 1.0.

\item[\AdAttr{FileTransferNetWriteSeconds}] Total number of
  submit-side transfer process seconds spent writing to the network
  when transferring input to jobs since this \Condor{schedd} was
  started.

\item[\AdAttr{FileTransferNetWriteLoad\_<timespan>}] Exponential
  moving average over the specified timespan of the rate at which
  submit-side file transfer processes have spent time writing to the
  network when transferring input to jobs.  One file transfer process
  spending nearly all of its time writing to the network will generate
  a load close to 1.0.

\end{description}

\item \Macro{NOT\_RESPONDING\_TIMEOUT} now internally adds some random skew
to avoid synchronization of heartbeat messages, which can lead to UDP
buffer overflow and incorrect determination that daemons are hung.
\Ticket{3510}

\end{itemize}

\noindent Bugs Fixed:

\begin{itemize}

\item The EC2 GAHP now correctly parses XML namespaces (as returned, for
instance, by some installations of Eucalyptus).  A related bug, which could
cause HTCondor to put the job on hold, incorrectly believing that the cloud
service had purged it, was also fixed.
\Ticket{3492}

\item The \Condor{negotiator} now checks to see if \Macro{MAX\_TIME\_PER\_SUBMITTER}
has been exceeded while negotiating with single \Condor{schedd}. This configuration
variable used to only be effective if a submitter used multiple schedds.
\Ticket{3504}

\item \Condor{dagman} will now recover correctly in a DAG where a node has been 
skipped because of a \Macro{PRE\_SKIP} has triggered.
\Ticket{2966}

\item Fixed a bug in the \Condor{gridmanager} and \Condor{ft-gahp} that
can cause a crash when transferring files for grid-type batch jobs going
to a remote cluster.
\Ticket{3529}

\end{itemize}

\noindent Known Bugs:

\begin{itemize}

\item None.

\end{itemize}

\noindent Additions and Changes to the Manual:

\begin{itemize}
<commit_msg>edit 7.9.5 version history item ===GT=== #3492<commit_after>%%%      PLEASE RUN A SPELL CHECKER BEFORE COMMITTING YOUR CHANGES!
%%%      PLEASE RUN A SPELL CHECKER BEFORE COMMITTING YOUR CHANGES!
%%%      PLEASE RUN A SPELL CHECKER BEFORE COMMITTING YOUR CHANGES!
%%%      PLEASE RUN A SPELL CHECKER BEFORE COMMITTING YOUR CHANGES!
%%%      PLEASE RUN A SPELL CHECKER BEFORE COMMITTING YOUR CHANGES!

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{\label{sec:History-7-9}Development Release Series 7.9}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

This is the development release series of HTCondor.
The details of each version are described below.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\subsection*{\label{sec:New-7-6-0}Version 7.9.5}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

\noindent Release Notes:

\begin{itemize}

\item HTCondor version 7.9.5 not yet released.
%\item HTCondor version 7.9.5 released on Month Date, 2013.

\end{itemize}


\noindent New Features:

\begin{itemize}

\item Allow the number of bits in a delegated proxy to be specified
by the receiving side using \Macro{GSI\_DELEGATION\_KEYBITS}
\Ticket{3503}

\item When there are multiple users
waiting to transfer files within the limits set by
configuration variables
\Macro{MAX\_CONCURRENT\_UPLOADS} and/or
\Macro{MAX\_CONCURRENT\_DOWNLOADS}, the scheduling algorithm
now gives the users
an equal share of the transfer slots.  How shares are counted can be
configured with \Macro{TRANSFER\_QUEUE\_USER\_EXPR}.
\Ticket{3487}

\item When using the \Opt{-remote} or \Opt{-spool} options to
\Condor{submit}, the job owner will be set by the \Condor{schedd} based
on how you were authenticated. This will make it easier to submit jobs
to a remote \Condor{schedd} where your credentials may map to a different
account name.
\Ticket{3370}

\end{itemize}

\noindent Configuration Variable and ClassAd Attribute Additions and Changes:

\begin{itemize}

\item When using file transfer concurrency limits, additional I/O
  usage statistics are now published in the ClassAd of the
  \Condor{schedd}.  This includes the sum and rate of bytes
  transferred as well as time spent reading and writing to files and
  to the network.  These statistics are reported for the sum of all
  users and individually for recently active users.  The ClassAd
  attributes are described below.  Each of these may be prefixed by a
  username (e.g. \AdAttr{username\_FileTransferUploadBytes}).  In this
  case, it represents activity by the specified user.  The published
  username is actually the file transfer queue name, as defined by
  \Macro{TRANSFER\_QUEUE\_USER\_EXPR}.  This expression defaults to
  the name of the job owner.  The attributes that are rates have a
  suffix that specifies the timespan of the exponential moving
  average.  By default the timespans that are published are 1m, 5m,
  1h, and 1d.  This can be changed by configuring
  \Macro{TRANSFER\_IO\_REPORT\_TIMESPANS}.  These attributes are only
  reported once a full timespan has accumulated.

\begin{description}

\item[\AdAttr{FileTransferUploadBytes}] Total number of bytes uploaded
  as input to jobs since this \Condor{schedd} was started.

\item[\AdAttr{FileTransferUploadBytesPerSecond\_<timespan>}]
  Exponential moving average over the specified timespan of the rate
  at which bytes have been uploaded as input to jobs.

\item[\AdAttr{FileTransferDownloadBytes}] Total number of bytes
  downloaded as output from jobs since this \Condor{schedd} was
  started.

\item[\AdAttr{FileTransferDownloadBytesPerSecond\_<timespan>}]
  Exponential moving average over the specified timespan of the rate
  at which bytes have been downloaded as output from jobs.

\item[\AdAttr{FileTransferFileReadSeconds}] Total number of
  submit-side transfer process seconds spent reading from files to be
  transferred as input to jobs since this \Condor{schedd} was started.

\item[\AdAttr{FileTransferFileReadLoad\_<timespan>}] Exponential
  moving average over the specified timespan of the rate at which
  submit-side file transfer processes have spent time reading from
  files to be transferred as input to jobs.  One file transfer process
  spending nearly all of its time reading files will generate a load
  close to 1.0.

\item[\AdAttr{FileTransferFileWriteSeconds}] Total number of
  submit-side transfer process seconds spent writing to files
  transferred as output from jobs since this \Condor{schedd} was
  started.

\item[\AdAttr{FileTransferFileWriteLoad\_<timespan>}]
  Exponential moving average over the specified timespan of the rate
  at which submit-side file transfer processes have spent time writing to files
  transferred as output from jobs.  One file transfer process spending
  nearly all of its time writing to files will generate a load close
  to 1.0.

\item[\AdAttr{FileTransferNetReadSeconds}] Total number of submit-side
  transfer process seconds spent reading from the network when
  transferring output from jobs since this \Condor{schedd} was
  started.

\item[\AdAttr{FileTransferNetReadLoad\_<timespan>}] Exponential moving
  average over the specified timespan of the rate at which submit-side
  file transfer processes have spent time reading from the network
  when transferring output from jobs.  One file transfer process
  spending nearly all of its time reading from the network will
  generate a load close to 1.0.

\item[\AdAttr{FileTransferNetWriteSeconds}] Total number of
  submit-side transfer process seconds spent writing to the network
  when transferring input to jobs since this \Condor{schedd} was
  started.

\item[\AdAttr{FileTransferNetWriteLoad\_<timespan>}] Exponential
  moving average over the specified timespan of the rate at which
  submit-side file transfer processes have spent time writing to the
  network when transferring input to jobs.  One file transfer process
  spending nearly all of its time writing to the network will generate
  a load close to 1.0.

\end{description}

\item \Macro{NOT\_RESPONDING\_TIMEOUT} now internally adds some random skew
to avoid synchronization of heartbeat messages, which can lead to UDP
buffer overflow and incorrect determination that daemons are hung.
\Ticket{3510}

\end{itemize}

\noindent Bugs Fixed:

\begin{itemize}

\item Two EC2 GAHP bugs are fixed.
It now correctly parses XML namespaces as returned for
some installations of Eucalyptus.
The second bug caused HTCondor to put the job on hold, 
as it incorrectly believed that the cloud
service had purged it.
\Ticket{3492}

\item The \Condor{negotiator} now checks to see if \Macro{MAX\_TIME\_PER\_SUBMITTER}
has been exceeded while negotiating with single \Condor{schedd}. This configuration
variable used to only be effective if a submitter used multiple schedds.
\Ticket{3504}

\item \Condor{dagman} will now recover correctly in a DAG where a node has been 
skipped because of a \Macro{PRE\_SKIP} has triggered.
\Ticket{2966}

\item Fixed a bug in the \Condor{gridmanager} and \Condor{ft-gahp} that
can cause a crash when transferring files for grid-type batch jobs going
to a remote cluster.
\Ticket{3529}

\end{itemize}

\noindent Known Bugs:

\begin{itemize}

\item None.

\end{itemize}

\noindent Additions and Changes to the Manual:

\begin{itemize}

{'fraction_non_alphanumeric': 0.09452668749151161, 'fraction_numerical': 0.0093032731223686, 'mean_word_length': 4.580522925350512, 'pattern_counts': {'":': 0, '<': 15, '<?xml version=': 0, '>': 15, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 10, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4133635', 'n_tokens_mistral': 4116, 'n_tokens_neox': 3999, 'n_words': 1829}