DR6}:dZddlZddlmZdZGddZdZy)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. N)procutilsships-with-hg-corec"eZdZdZdZdZdZy) processloggerz_Map log events to external commands Arguments are passed on as environment variables. cBt|jd|_yNs logtoprocess)dict configitems_scripts)selfuis 6usr/lib/python3.12/site-packages/hgext/logtoprocess.py__init__zprocesslogger.__init__5sR^^O<= cJt|jj|S)N)boolr get)r events r trackedzprocesslogger.tracked8sDMM%%e,--rc(|j|}d}t||kDr|d|dz}|tj|d}|j d|j Dt j|}t j||dy)Nis (truncated))sEVENTsHGPIDsMSG1c3LK|]\}}d|jz|fyw)sOPT_%sN)upper).0keyvalues r z$processlogger.log..Js( ?KeY $e ,|s"$T)shell) r lenosgetpidupdateitemsr shellenviron runbgcommand) r r rmsgoptsscriptmaxmsgenvfullenvs r logzprocesslogger.log;su% s8f  gv,0Ciik   ?Czz|  '',fgT:rN)__name__ __module__ __qualname____doc__rrr*rr rr/s >.;rrc:|jdt|yr) setloggerr)r s r uipopulater2QsLL-"34r)r.rmercurial.utilsr testedwithrr2r/rr r5s): $ # ;;D5r