ܤdZddlmZddlmZddlZddlZddl Z ddl Z ddl m Z ddl mZmZmZmZmZmZmZmZmZddlmZmZdZiZej8eZeddd edd d edd d edd d eddd eddd eddd eddd eddd eddd eddd eddd eddd eddd eddd eddd eddd edd d edd!d edd"d d#j;Zd$ZdeiZ Gd%d&Z!d)d'Z"d(Z#y)*ahooks for sending email push notifications This extension implements hooks to send email notifications when changesets are sent from or received by the local repository. First, enable the extension as explained in :hg:`help extensions`, and register the hook you want to run. ``incoming`` and ``changegroup`` hooks are run when changesets are received, while ``outgoing`` hooks are for changesets sent to another repository:: [hooks] # one email for each incoming changeset incoming.notify = python:hgext.notify.hook # one email for all incoming changesets changegroup.notify = python:hgext.notify.hook # one email for all outgoing changesets outgoing.notify = python:hgext.notify.hook This registers the hooks. To enable notification, subscribers must be assigned to repositories. The ``[usersubs]`` section maps multiple repositories to a given recipient. The ``[reposubs]`` section maps multiple recipients to a single repository:: [usersubs] # key is subscriber email, value is a comma-separated list of repo patterns user@host = pattern [reposubs] # key is repo pattern, value is a comma-separated list of subscriber emails pattern = user@host A ``pattern`` is a ``glob`` matching the absolute path to a repository, optionally combined with a revset expression. A revset expression, if present, is separated from the glob by a hash. Example:: [reposubs] */widgets#branch(release) = qa-team@example.com This sends to ``qa-team@example.com`` whenever a changeset on the ``release`` branch triggers a notification in any repository ending in ``widgets``. In order to place them under direct user management, ``[usersubs]`` and ``[reposubs]`` sections may be placed in a separate ``hgrc`` file and incorporated by reference:: [notify] config = /path/to/subscriptionsfile Notifications will not be sent until the ``notify.test`` value is set to ``False``; see below. Notifications content can be tweaked with the following configuration entries: notify.test If ``True``, print messages to stdout instead of sending them. Default: True. notify.sources Space-separated list of change sources. Notifications are activated only when a changeset's source is in this list. Sources may be: :``serve``: changesets received via http or ssh :``pull``: changesets received via ``hg pull`` :``unbundle``: changesets received via ``hg unbundle`` :``push``: changesets sent or received via ``hg push`` :``bundle``: changesets sent via ``hg unbundle`` Default: serve. notify.strip Number of leading slashes to strip from url paths. By default, notifications reference repositories with their absolute path. ``notify.strip`` lets you turn them into relative paths. For example, ``notify.strip=3`` will change ``/long/path/repository`` into ``repository``. Default: 0. notify.domain Default email domain for sender or recipients with no explicit domain. It is also used for the domain part of the ``Message-Id`` when using ``notify.messageidseed``. notify.messageidseed Create deterministic ``Message-Id`` headers for the mails based on the seed and the revision identifier of the first commit in the changeset. notify.style Style file to use when formatting emails. notify.template Template to use when formatting emails. notify.incoming Template to use when run as an incoming hook, overriding ``notify.template``. notify.outgoing Template to use when run as an outgoing hook, overriding ``notify.template``. notify.changegroup Template to use when running as a changegroup hook, overriding ``notify.template``. notify.maxdiff Maximum number of diff lines to include in notification email. Set to 0 to disable the diff, or -1 to include all of it. Default: 300. notify.maxdiffstat Maximum number of diffstat lines to include in notification email. Set to -1 to include all of it. Default: -1. notify.maxsubject Maximum number of characters in email's subject line. Default: 67. notify.diffstat Set to True to include a diffstat before diff content. Default: True. notify.showfunc If set, override ``diff.showfunc`` for the diff content. Default: None. notify.merge If True, send notifications for merge changesets. Default: True. notify.mbox If set, append mails to this mbox file instead of sending. Default: None. notify.fromauthor If set, use the committer of the first changeset in a changegroup for the "From" field of the notification mail. If not set, take the user from the pushing repo. Default: False. notify.reply-to-predecessor (EXPERIMENTAL) If set and the changeset has a predecessor in the repository, try to thread the notification mail with the predecessor. This adds the "In-Reply-To" header to the notification mail with a reference to the predecessor with the smallest revision number. Mail threads can still be torn, especially when changesets are folded. This option must be used in combination with ``notify.messageidseed``. If set, the following entries will also be used to customize the notifications: email.from Email ``From`` address to use if none can be found in the generated email content. web.baseurl Root repository URL to combine with repository paths when making references. See also ``notify.strip``. N)_) encodingerror logcmdutilmailobsutilpatchpycompat registrarutil)dateutil stringutilsships-with-hg-corenotify changegroup)defaultconfigdiffstatTdomain messageidseed fromauthorsincomingmaxdiffi, maxdiffstat maxsubjectCmboxmergeoutgoingreply-to-predecessorFsourcessserveshowfuncstripstyletemplatetests Subject: changeset in {webroot}: {desc|firstline|strip} From: {author} changeset {node|short} in {root} details: {baseurl}{webroot}?cmd=changeset;node={node|short} description: {desc|tabindent|strip} sx changeset {node|short} in {root} details: {baseurl}{webroot}?cmd=changeset;node={node|short} summary: {desc|firstline} cBeZdZdZdZdZdZdZdZdZ dZ d d Z y ) notifierzemail notification class.c||_|jjdd}|r|jj|ddg||_t |jjdd|_|j |jj|_|jjdd|_|jjdd|_ |jjdd |_ tj|j|_|j|_|jjdd |_|jjdd |_|jjdd |_|jjdd |_|j(r*|j&st+j,t/d|j$!|jjdd |_d}|jjd|xs|jjdd}|s|jjdd}|s|st0j3|xst4}t7j8||}t7j:|j|j||_y)Nrrusersubsreposubs)sectionsr"rrr%rr!rrs=notify.reply-to-predecessor used without notify.messageidseedsdiffr$r#)uiconfig readconfigrepoint stripcountstriprootdomainmbox configbooltestr _charsetscharsets subscriberssubsmergeshowfunc messageidseedreplyrAbortr deftemplatesgetsingle_templater templatespecchangesettemplatert)selfr,r/hooktypecfgmapfiletemplatespecs 0usr/lib/python3.12/site-packages/hgext/notify.py__init__znotifier.__init__@s%ggnnY 2  GG  sk;-G  H dggnnYABJJtyy~~. ggnnY : GGNN9g6 GG&&y': tww/ $$& WW'' 8< **9kB !WW^^I7GHWW'' 3JK ::d00++,  ==  GG..w DDM77>>)X6 $''.. {; ggnnY9Gx#''1D_H&&x9..tww 4Hctj|}|j}|dkDr,|jd}|dk(r |S||dzd}|dz}|dkDr,|S)z?strip leading slashes from local path, turn into web-safe path.r/rN)r pconvertr1find)rGpathcountcs rMr2znotifier.striphsj}}T"ai $ABw A=D QJE ai  rOctj|j}|jr1|j d}|dk7r|d|}d|vr|dz|jzS|S)z try to clean up email addresses. @localhostrN@)remailr2r4rT)rGaddras rMfixmailznotifier.fixmailusa - ;; -(ABwBQx4d{T[[00 rOc nt}|jjdD]\}}|jdD]y}d|vr|jdd\}}nd}t j|j j |jsX|j|j||f{|jjdD]\}}d|vr|jdd\}}nd}t j|j j |sM|jdD]$}|j|j||f&t|Dcgc]=\}}tj|j||j|j|f?c}}Scc}}w)z;return list of email addresses of subscribers to this repo.r),#rRNr*)setr, configitemssplitfnmatchr/r3r2addr^sortedr addressencoder9r7) rGr;userpatspatrevsuserssrs rMr:znotifier.subscriberssbu''--k:JD$zz$'3; # $ 2ICD??499>>399;?HHdll40$78 (;''--k:JCs{IIdA. Ttyy~~s3!KK-DHHdll40$78. ;t  $1  DMM499 Eq I$   s+AF1c &|jst|jdkDry|jj|f|j |j jdd|jj|jd|y)z6format one changeset, unless it is a suppressed merge.rRFswebsbaseurl)changesbaseurlr3webrootT) r<lenparentsrFshow changesetr,r-r/r3)rGctxpropss rMnodez notifier.nodestzzc#++-014  MMOGGNN6:6II    rOc^|jjddj}||vS)zznotifier.send.. s rO)keyz In-Reply-Toz, Tos*notify: sending %d subscribers %d changes )r5)Arbr;rfr/rlrrRepoLookupErrorrtr,debugr parsebytes emailerrorsMessageParseErrorr@r forcebytestr headdecode is_multipartitems get_payload mimeencoder9r7r strfromlocalr datestrrr3 descriptionlstriprdrstripr0r-ellipsis headencodeusernamer^rh messageidr4r>r? unfiltered changelogindexhas_noderallpredecessorsobsstorerzminjoinrgas_byteswriteendswithstatussendmail emailutils parseaddrr5)rGrxrVdatar;subrLrlmsginstsendersubjectheaderspayloadkvrn maxsubjectunfirctx2 predecessorspredmsgtexts rMsendz notifier.sendsuIC|  yy~~mT3779E4y # t9> GGMMG   =//$'C Vi.  __V,F  oog.G KY!iikGooTo2G//$''7DMM499MC1A ++   $A B F qy45E8JJOO%,,.44UA>qAHHJ#tyy!n4 =AB  ))':>G GGWdmmTYY I WW^^Hg6L$'':J:J:LF v &!8\\&)F(( GGVT]]DII F $2C#7  < )#t{{D a<  q[S^g5CDC GGMM#Y 99 :!(7+I  GGMM!67#i.H I  ejj+,rOr) __name__ __module__ __qualname____doc__rNr2r^r:rzr~rrrOrMr'r'=s1#&IP   0 ( sj#-rOr'c t|||}|j|}|js|jd|jzy|j |r|jd|zy|j d}d} d} |dk(s|dk(r|jj|jD]} |j|| r| d z } | r|| j} 3||jz }|jtd | || jdd fz|j | r|j!||d n|j|vr|j|sO|j|jtd |j|jdd fzy| d z } |j!|| s|j} ||jz }|j#d d} | r| rdj%d| z|g}| r|j'|| |yy)zsend email notifications to interested subscribers. if used as changegroup hook, send one email for all changesets in changegroup. else send one email per changeset.s(notify: no subscribers to repository %s Ns,notify: changes have source "%s" - skipping rOrrr)startrRs1notify: suppressing notification for merge %d:%s stiprrrsFrom: %s)r'rr;rr3r~ pushbufferrrlrrzri popbuffernoterhexrr-rr) r,r/rHrzr|kwargsnrxrrVauthorr fromauthors rMhookrGs T8$A // D !C 66 =FG||F AFJKMMO D E F>!X%<>>&&SWWY&7Cvvd3i  !#Y^^-F &KLDIMMOCR012 8  FF3V % d vvc{ LLN GGGH779cggin-.     s XXZFBLLND9m4J *zz;/67  sE4  rOc|r|r|}n'tjtj}|rRt j |j |z}dtj|jdd|fz}nEd|ttjt|jj|fz}tj|S)Ns @s)r strtolocalsocketgetfqdnhashlibsha512rr sysbytes hexdigestr0timehashr/r3r)rxr4r>host messagehashrs rMrrs -""6>>#34nnSWWY%>? !   k335cr: ; %  (     !  +    ++rO)NN)$r email.errorserrorsr email.utilsutilsrrerrrmercurial.i18nr mercurialrrrrrr r r r mercurial.utilsr r testedwith configtable configitemrrCmultiple_templaterAr'rrrrOrMrsTl#     #  !Y ! !+ .                                                                                FH% G-G-T6!r,rO