a +b] @sDdZddlmZddlZddlmZdZGdddeZdd Z dS) a:send ui.log() data to a subprocess (EXPERIMENTAL) This extension lets you specify a shell command per ui.log() event, sending all remaining arguments to as environment variables to that command. Positional arguments construct a log message, which is passed in the `MSG1` environment variables. Each keyword argument is set as a `OPT_UPPERCASE_KEY` variable (so the key is uppercased, and prefixed with `OPT_`). The original event name is passed in the `EVENT` environment variable, and the process ID of mercurial is given in `HGPID`. So given a call `ui.log('foo', 'bar %s ', 'baz', spam='eggs'), a script configured for the `foo` event can expect an environment with `MSG1=bar baz`, and `OPT_SPAM=eggs`. Scripts are configured in the `[logtoprocess]` section, each key an event name. For example:: [logtoprocess] commandexception = echo "$MSG1" > /var/log/mercurial_exceptions.log would log the warning message and traceback of any failed command dispatch. Scripts are run asynchronously as detached daemon processes; mercurial will not ensure that they exit cleanly. )absolute_importN)procutilsships-with-hg-corec@s(eZdZdZddZddZddZdS) processloggerz_Map log events to external commands Arguments are passed on as environment variables. cCst|d|_dSNs logtoprocess)dictZ configitems_scripts)selfuir 8/usr/lib64/python3.9/site-packages/hgext/logtoprocess.py__init__6szprocesslogger.__init__cCst|j|S)N)boolrget)reventr r r tracked9szprocesslogger.trackedc Csp|j|}d}t||kr*|d|d}|t|d}|dd|Dt|}tj||dddS)Nis (truncated))sEVENTsHGPIDsMSG1css"|]\}}d||fVqdS)sOPT_%sN)upper).0keyvaluer r r Ksz$processlogger.log..T)shell) rlenosgetpidupdateitemsrZ shellenvironZ runbgcommand) rr rmsgZoptsZscriptZmaxmsgenvZfullenvr r r log<s    zprocesslogger.logN)__name__ __module__ __qualname____doc__r rrr r r r r0srcCs|dt|dSr)Z setloggerr)r r r r uipopulateRsr#) r"Z __future__rrZmercurial.utilsrZ testedwithobjectrr#r r r r s   "