mdZddlZddlZddlZddlmZddlmZddlm Z m Z m Z m Z m Z mZmZddlmZmZej&ZdZiZe j,eZedd d edd d eddd eddd eddd eddd eddd eddd eddd eddd eddej. eddd eddd edd d edd!d edd"d edd#d$ edd%d edd&d edd'd Gd(d)ZGd*d+eZGd,d-eZGd.d/eZGd0d1ZGd2d3eej:ZGd4d5eej>Z Gd6d7eZ!Gd8d9e!Z"Gd:d;e#Z$Gd<d=eZ%Gd>d?Z&dAd@Z'y)Ba)hooks for integrating with the Bugzilla bug tracker This hook extension adds comments on bugs in Bugzilla when changesets that refer to bugs by Bugzilla ID are seen. The comment is formatted using the Mercurial template mechanism. The bug references can optionally include an update for Bugzilla of the hours spent working on the bug. Bugs can also be marked fixed. Four basic modes of access to Bugzilla are provided: 1. Access via the Bugzilla REST-API. Requires bugzilla 5.0 or later. 2. Access via the Bugzilla XMLRPC interface. Requires Bugzilla 3.4 or later. 3. Check data via the Bugzilla XMLRPC interface and submit bug change via email to Bugzilla email interface. Requires Bugzilla 3.4 or later. 4. Writing directly to the Bugzilla database. Only Bugzilla installations using MySQL are supported. Requires Python MySQLdb. Writing directly to the database is susceptible to schema changes, and relies on a Bugzilla contrib script to send out bug change notification emails. This script runs as the user running Mercurial, must be run on the host with the Bugzilla install, and requires permission to read Bugzilla configuration details and the necessary MySQL user and password to have full access rights to the Bugzilla database. For these reasons this access mode is now considered deprecated, and will not be updated for new Bugzilla versions going forward. Only adding comments is supported in this access mode. Access via XMLRPC needs a Bugzilla username and password to be specified in the configuration. Comments are added under that username. Since the configuration must be readable by all Mercurial users, it is recommended that the rights of that user are restricted in Bugzilla to the minimum necessary to add comments. Marking bugs fixed requires Bugzilla 4.0 and later. Access via XMLRPC/email uses XMLRPC to query Bugzilla, but sends email to the Bugzilla email interface to submit comments to bugs. The From: address in the email is set to the email address of the Mercurial user, so the comment appears to come from the Mercurial user. In the event that the Mercurial user email is not recognized by Bugzilla as a Bugzilla user, the email associated with the Bugzilla username used to log into Bugzilla is used instead as the source of the comment. Marking bugs fixed works on all supported Bugzilla versions. Access via the REST-API needs either a Bugzilla username and password or an apikey specified in the configuration. Comments are made under the given username or the user associated with the apikey in Bugzilla. Configuration items common to all access modes: bugzilla.version The access type to use. Values recognized are: :``restapi``: Bugzilla REST-API, Bugzilla 5.0 and later. :``xmlrpc``: Bugzilla XMLRPC interface. :``xmlrpc+email``: Bugzilla XMLRPC and email interfaces. :``3.0``: MySQL access, Bugzilla 3.0 and later. :``2.18``: MySQL access, Bugzilla 2.18 and up to but not including 3.0. :``2.16``: MySQL access, Bugzilla 2.16 and up to but not including 2.18. bugzilla.regexp Regular expression to match bug IDs for update in changeset commit message. It must contain one "()" named group ```` containing the bug IDs separated by non-digit characters. It may also contain a named group ```` with a floating-point number giving the hours worked on the bug. If no named groups are present, the first "()" group is assumed to contain the bug IDs, and work time is not updated. The default expression matches ``Bug 1234``, ``Bug no. 1234``, ``Bug number 1234``, ``Bugs 1234,5678``, ``Bug 1234 and 5678`` and variations thereof, followed by an hours number prefixed by ``h`` or ``hours``, e.g. ``hours 1.5``. Matching is case insensitive. bugzilla.fixregexp Regular expression to match bug IDs for marking fixed in changeset commit message. This must contain a "()" named group ``` containing the bug IDs separated by non-digit characters. It may also contain a named group ```` with a floating-point number giving the hours worked on the bug. If no named groups are present, the first "()" group is assumed to contain the bug IDs, and work time is not updated. The default expression matches ``Fixes 1234``, ``Fixes bug 1234``, ``Fixes bugs 1234,5678``, ``Fixes 1234 and 5678`` and variations thereof, followed by an hours number prefixed by ``h`` or ``hours``, e.g. ``hours 1.5``. Matching is case insensitive. bugzilla.fixstatus The status to set a bug to when marking fixed. Default ``RESOLVED``. bugzilla.fixresolution The resolution to set a bug to when marking fixed. Default ``FIXED``. bugzilla.style The style file to use when formatting comments. bugzilla.template Template to use when formatting comments. Overrides style if specified. In addition to the usual Mercurial keywords, the extension specifies: :``{bug}``: The Bugzilla bug ID. :``{root}``: The full pathname of the Mercurial repository. :``{webroot}``: Stripped pathname of the Mercurial repository. :``{hgweb}``: Base URL for browsing Mercurial repositories. Default ``changeset {node|short} in repo {root} refers to bug {bug}.\ndetails:\n\t{desc|tabindent}`` bugzilla.strip The number of path separator characters to strip from the front of the Mercurial repository path (``{root}`` in templates) to produce ``{webroot}``. For example, a repository with ``{root}`` ``/var/local/my-project`` with a strip of 2 gives a value for ``{webroot}`` of ``my-project``. Default 0. web.baseurl Base URL for browsing Mercurial repositories. Referenced from templates as ``{hgweb}``. Configuration items common to XMLRPC+email and MySQL access modes: bugzilla.usermap Path of file containing Mercurial committer email to Bugzilla user email mappings. If specified, the file should contain one mapping per line:: committer = Bugzilla user See also the ``[usermap]`` section. The ``[usermap]`` section is used to specify mappings of Mercurial committer email to Bugzilla user email. See also ``bugzilla.usermap``. Contains entries of the form ``committer = Bugzilla user``. XMLRPC and REST-API access mode configuration: bugzilla.bzurl The base URL for the Bugzilla installation. Default ``http://localhost/bugzilla``. bugzilla.user The username to use to log into Bugzilla via XMLRPC. Default ``bugs``. bugzilla.password The password for Bugzilla login. REST-API access mode uses the options listed above as well as: bugzilla.apikey An apikey generated on the Bugzilla instance for api access. Using an apikey removes the need to store the user and password options. XMLRPC+email access mode uses the XMLRPC access mode configuration items, and also: bugzilla.bzemail The Bugzilla email address. In addition, the Mercurial email settings must be configured. See the documentation in hgrc(5), sections ``[email]`` and ``[smtp]``. MySQL access mode configuration: bugzilla.host Hostname of the MySQL server holding the Bugzilla database. Default ``localhost``. bugzilla.db Name of the Bugzilla database in MySQL. Default ``bugs``. bugzilla.user Username to use to access MySQL server. Default ``bugs``. bugzilla.password Password to use to access MySQL server. bugzilla.timeout Database connection timeout (seconds). Default 5. bugzilla.bzuser Fallback Bugzilla user name to record comments with, if changeset committer cannot be found as a Bugzilla user. bugzilla.bzdir Bugzilla install directory. Used by default notify. Default ``/var/www/html/bugzilla``. bugzilla.notify The command to run to get Bugzilla to send bug change notification emails. Substitutes from a map with 3 keys, ``bzdir``, ``id`` (bug id) and ``user`` (committer bugzilla email). Default depends on version; from 2.18 it is "cd %(bzdir)s && perl -T contrib/sendbugmail.pl %(id)s %(user)s". Activating the extension:: [extensions] bugzilla = [hooks] # run bugzilla hook on every change pulled or pushed in here incoming.bugzilla = python:hgext.bugzilla.hook Example configurations: XMLRPC example configuration. This uses the Bugzilla at ``http://my-project.org/bugzilla``, logging in as user ``bugmail@my-project.org`` with password ``plugh``. It is used with a collection of Mercurial repositories in ``/var/local/hg/repos/``, with a web interface at ``http://my-project.org/hg``. :: [bugzilla] bzurl=http://my-project.org/bugzilla user=bugmail@my-project.org password=plugh version=xmlrpc template=Changeset {node|short} in {root|basename}. {hgweb}/{webroot}/rev/{node|short}\n {desc}\n strip=5 [web] baseurl=http://my-project.org/hg XMLRPC+email example configuration. This uses the Bugzilla at ``http://my-project.org/bugzilla``, logging in as user ``bugmail@my-project.org`` with password ``plugh``. It is used with a collection of Mercurial repositories in ``/var/local/hg/repos/``, with a web interface at ``http://my-project.org/hg``. Bug comments are sent to the Bugzilla email address ``bugzilla@my-project.org``. :: [bugzilla] bzurl=http://my-project.org/bugzilla user=bugmail@my-project.org password=plugh version=xmlrpc+email bzemail=bugzilla@my-project.org template=Changeset {node|short} in {root|basename}. {hgweb}/{webroot}/rev/{node|short}\n {desc}\n strip=5 [web] baseurl=http://my-project.org/hg [usermap] user@emaildomain.com=user.name@bugzilladomain.com MySQL example configuration. This has a local Bugzilla 3.2 installation in ``/opt/bugzilla-3.2``. The MySQL database is on ``localhost``, the Bugzilla database name is ``bugs`` and MySQL is accessed with MySQL username ``bugs`` password ``XYZZY``. It is used with a collection of Mercurial repositories in ``/var/local/hg/repos/``, with a web interface at ``http://my-project.org/hg``. :: [bugzilla] host=localhost password=XYZZY version=3.0 bzuser=unknown@domain.com bzdir=/opt/bugzilla-3.2 template=Changeset {node|short} in {root|basename}. {hgweb}/{webroot}/rev/{node|short}\n {desc}\n strip=5 [web] baseurl=http://my-project.org/hg [usermap] user@emaildomain.com=user.name@bugzilladomain.com All the above add a comment to the Bugzilla bug record of the form:: Changeset 3b16791d6642 in repository-name. http://my-project.org/hg/repository-name/rev/3b16791d6642 Changeset commit comment. Bug 1234. N)_)short)error logcmdutilmailpycompat registrarurlutil)procutil stringutilsships-with-hg-corebugzillaapikey)defaultbzdirs/var/www/html/bugzillabzemailbzurlshttp://localhost/bugzilla/bzuserdbbugs fixregexpsfix(?:es)?\s*(?:bugs?\s*)?,?\s*(?:nos?\.?|num(?:ber)?s?)?\s*(?P(?:#?\d+\s*(?:,?\s*(?:and)?)?\s*)+)\.?\s*(?:h(?:ours?)?\s*(?P\d*(?:\.\d+)?))? fixresolutionsFIXED fixstatussRESOLVEDhosts localhostnotifypasswordregexpsbugs?\s*,?\s*(?:#|nos?\.?|num(?:ber)?s?)?\s*(?P(?:\d+\s*(?:,?\s*(?:and)?)?\s*)+)\.?\s*(?:h(?:ours?)?\s*(?P\d*(?:\.\d+)?))?stripstyletemplatetimeoutuserusermapversionc4eZdZdZdZdZdZdZdZdZ y) bzaccessz"Base class for access to Bugzilla.c||_|jjdd}|r|jj|dgyy)Nrr%)sections)uiconfig readconfig)selfr+usermaps 2usr/lib/python3.12/site-packages/hgext/bugzilla.py__init__zbzaccess.__init__s>''..j9  GG  w*  > rc|jjdD]*\}}|j|jk(s(|cS|S)z,map name of committer to Bugzilla user name.r%)r+ configitemslower)r.user committerbzusers r0 map_committerzbzaccess.map_committersB!%!4!4Z!@ Iv DJJL0 "A rcy)7remove bug IDs that do not exist in Bugzilla from bugs.N)r.bugss r0filter_real_bug_idszbzaccess.filter_real_bug_idsrcy);remove bug IDs where node occurs in comment text from bugs.Nr;)r.noder<s r0filter_cset_known_bug_idsz"bzaccess.filter_cset_known_bug_idsr>rcy)update the specified bug. Add comment text and set new states. If possible add the comment as being from the committer of the changeset. Otherwise use the default Bugzilla user. Nr;)r.bugidnewstatetextr6s r0 updatebugzbzaccess.updatebugr>rcyzForce sending of Bugzilla notification emails. Only required if the access method does not trigger notification emails automatically. Nr;r.r<r6s r0notifyzbzaccess.notifyr>rN) __name__ __module__ __qualname____doc__r1r8r=rBrHrLr;rr0r(r(s%,? FJ  rr(cZeZdZdZedZdZdZdZdZ dZ dZ d Z d Z d Zd Zy) bzmysqlzSupport for direct MySQL access to Bugzilla. The earliest Bugzilla version this is tested with is version 2.16. If your Bugzilla is version 3.4 or above, you are strongly recommended to use the XMLRPC access method instead. cLddjtt|zdzS)z#return SQL-friendly list of bug ids(,))joinmapstr)idss r0 sql_buglistzbzmysql.sql_buglists#diiC ..55rNc " ddl}|t_tj|||jjdd}|jjdd}|jjdd}|jjdd}t|jjdd}|jjt d |||d t|zfztjj||||| |_|jj!|_|j#|_i|_d |_y#t$r&}t j t d|zd}~wwxYw) Nrs&python mysql support not available: %srrr$rrr"s'connecting to %s:%s as %s, password %s *)hostr5passwddbconnect_timeouts-cd %(bzdir)s && ./processmail %(id)s %(user)s)MySQLdbrR_MySQLdb ImportErrorrAbortrr(r1r+r,intnotelenconnectconncursorget_longdesc_id longdesc_iduser_idsdefault_notify) r.r+mysqlerrr^r5r_r`timeouts r0r1zbzmysql.__init__sQ  #$G  $#ww~~k73ww~~k73 [9 WW^^K /dggnn[*=>  9 :Rtc&k12 3 $$,,DB-  ii&&( //1 N- ++; [[))+ER GGNN>?uT{#$ R ,rc|jjtd|j|\}}|j D]6}|jjtd|z|jj dd|j }|jj dd} ||z}|jjtd|ztjd|zd } tj| j} | j} | s|jj| t!j"td tj$| z|jjtd y #t$r ||||dz}YwxYw) ztell bugzilla to send mail.stelling bugzilla to send mail: s bug %s rrr)ridr$srunning notify command %s s (%s) 2>&1srbsbugzilla notify command %ssdone N)r+rrget_bugzilla_userrr,ro TypeErrorrgr popenr fromnativeeolreadclosewarnrre explainexit) r.r<r6r5useridrcmdfmtbzdircmdfpoutrets r0rLzbzmysql.notify;sa q<=>// :v))+B GGNN1]+b0 1WW^^KD?8 kk**,s8q="4.(SVAY (#)DMM$ M s0 C 'CBB0-C/B00CCc||j|} |j|}||fS#t$r |jj dd}|s!t j td|z|j|}|}n0#t$r$t j td|fzwxYwY||fSwxYw)zSee if committer is a registered bugzilla user. Return bugzilla username and userid if so. If not, return default bugzilla username and userid.rrs#cannot find bugzilla user id for %ss)cannot find bugzilla user id for %s or %s)r8rrr+r,rrer)r.r6r5r defaultusers r0rzbzmysql.get_bugzilla_userjs!!), %%d+Ff~  "ggnn[)D "++@ADH))+6" kkBC[)*  f~ s'( B;ABB;-B22B;:B;cZt|dkDr$|jjtd|j |\}}t j d}|jd||||f|jd||||jf|jjy)zupdate bug state with comment text. Try adding comment as committer of changeset, otherwise as default bugzilla user.rs'Bugzilla/MySQL cannot update bug state z%Y-%m-%d %H:%M:%Szvinsert into longdescs (bug_id, who, bug_when, thetext) values (%s, %s, %s, %s)zfinsert into bugs_activity (bug_id, who, bug_when, fieldid) values (%s, %s, %s, %s)N) rhr+rrrtimestrftimerxrmrjcommit)r.rErFrGr6r5rnows r0rHzbzmysql.updatebugs x=1  GGLLFG H// :vmm/0  /FC &   / FC!1!1 2 r)rMrNrOrP staticmethodr[rcr1rxrlr=rBrLrrrHr;rr0rRrRsP66HO:  %4*.rrRceZdZdZdZy) bzmysql_2_18z!support for bugzilla 2.18 series.c>tj||d|_y)Ns>cd %(bzdir)s && perl -T contrib/sendbugmail.pl %(id)s %(user)s)rRr1ror.r+s r0r1zbzmysql_2_18.__init__sr" M rN)rMrNrOrPr1r;rr0rrs + rrceZdZdZdZdZy) bzmysql_3_0z support for bugzilla 3.0 series.c0tj||yN)rr1rs r0r1zbzmysql_3_0.__init__sdB'rc|jd|jj}t|dk7rt j t d|ddS)rzs0select id from fielddefs where name = "longdesc"r{r|rr}rs r0rlzbzmysql_3_0.get_longdesc_idsO DEkk""$ s8q=++a :;< <1vayrN)rMrNrOrPr1rlr;rr0rrs*(rrc"eZdZdZgZdZddZy)cookietransportrequestaA Transport request method that retains cookies over its lifetime. The regular xmlrpclib transports ignore cookies. Which causes a bit of a problem when you need a cookie-based login, as with the Bugzilla XMLRPC interface prior to 4.4.3. So this is a helper for defining a Transport which looks for cookies being set in responses and saves them to add to all future requests. cd|jr$|jD]}|jd|yy)NsCookie)cookies putheader)r. connectioncookies r0 send_cookiesz#cookietransportrequest.send_cookiess, <<,,$$Y7' rc||_d|_|j|}|r|jd|j ||||j |||j ||j||j|| |j}|jjdD]G}|jddd}|jddd} |jj!| I|j"dk7rCt$j'||z|j"|j(|jj*|j-} |j/\} } | j1| | j3| j3S#t$r|jj}Y1wxYw)NFr{s Set-Cookies: ;r)verboseaccept_gzip_encodingmake_connectionset_debuglevel send_request send_hostrsend_user_agent send_content getresponseAttributeError_connmsggetallmatchingheaderssplitrappendr xmlrpclib ProtocolErrorreasonheadersr getparserfeedr) r.r^handler request_bodyrhresponseheadervalrpayloadparser unmarshallers r0requestzcookietransportrequest.requests $)!   &   Q  !Wl3 q$ ! Q !\* -}}H ll88GF,,ua(+CYYtQ'*F LL   'H ??c !))w $$  --/#~~/  G !!##- -ww**,H -s F((#GGNr)rMrNrOrPrrrr;rr0rrs G8 ,$rrceZdZddZy)cookietransportctjtjdr!tjj ||yyNr1)r safehasattrr Transportr1r. use_datetimes r0r1zcookietransport.__init__s3   I// <    ( (| < =rNrrMrNrOr1r;rr0rrs=rrceZdZddZy)cookiesafetransportctjtjdr!tjj ||yyr)r rrr SafeTransportr1rs r0r1zcookiesafetransport.__init__s3   I// <  # # , ,T< @ =rNrrr;rr0rrsArrc4eZdZdZdZdZdZdZdZdZ y) bzxmlrpcznSupport for access to Bugzilla via the Bugzilla XMLRPC API. Requires a minimum Bugzilla version 3.4. c6tj|||jjdd}|j ddz}|jjdd}|jjdd}|jjdd|_|jjdd|_tjtj||j||_ |jjjd jd }t!|d |_t!|d |_|jj&j)||d d}|j+dd|_y)Nrr/s /xmlrpc.cgir$rrrr&.rr{T)loginrsrestrict_logintokenr)r(r1r+r,rstrip fixstatus fixresolutionr ServerProxyrstrurl transportbzproxyBugzillaversionrrf bzvermajor bzverminorUserlogingetbztoken)r.r+bzwebr5r_verrs r0r1zbzxmlrpc.__init__s8$#{H5 T"^3ww~~k73 [9 \B!WW^^K9IJ ,, OOE "DNN5$9  ll##++-j9??Ec!f+c!f+ !!''&T J yy3/ rcvtjj|dddk(r tSt S)Nshttprshttps)r urlrequrlparserr)r.uris r0rzbzxmlrpc.transport(s2 ;;  W -a 0H <&( ("$ $rc|jjj|gdg|jd}dj |dd|zdDcgc]}|d c}Scc}w)z0Return a string with all comment text for a bug.text)idsinclude_fieldsrrrs%dcomments)rBugcommentsrrW)r.rcts r0get_bug_commentszbzxmlrpc.get_bug_comments.sn LL   % %Twi4<< P xx!"7EBJ!7 !D E!DAQwZ!D E  Es A$c |jjjt|j gd|j d}|dD]1}|d}|j jtd|z||=3y)NT)rrs permissiversfaultsrr) rr rsortedrrr+rr)r.r<probebadbugrs r0r=zbzxmlrpc.filter_real_bug_ids7sx   $$tyy{+#%#,,   I&FB GGNN1782= >R'rct|jD]d}|j|jt |dk7s0|j j td|t |fz||=fy)Nr)rrr findrr+rrrs r0rBz"bzxmlrpc.filter_cset_known_bug_idsEsl%B$$R(--eDk:b@BC5;'(H &rci}d|vr|d|d<|jdk\rd|g|d<d|i|d<d|vr|j|d<|j|d <|j|d <|jj j |yd|vr$|jjtd ||d <||d<|jj j|y) Nhours work_timersbodycommentfixstatus resolutionrs?Bugzilla/XMLRPC needs Bugzilla 4.0 or later to mark bugs fixed r) rrrrrr updater+rr add_comment)r.rErFrGr6rvs r0rHzbzxmlrpc.updatebugNs x !)(!3D  ??a !7DL 'D !"&..Y&*&8&8]#!\\DN LL   # #D )! 0  DK#D  LL   ( ( .rN) rMrNrOrPr1rr r=rBrHr;rr0rr s% 0.%   /rrc(eZdZdZdZdZdZdZy) bzxmlrpcemailaRead data from Bugzilla via XMLRPC, send updates via email. Advantages of sending updates via email: 1. Comments can be added as any user, not just logged in user. 2. Bug statuses or other fields not accessible via XMLRPC can potentially be updated. There is no XMLRPC function to change bug status before Bugzilla 4.0, so bugs cannot be marked fixed via XMLRPC before Bugzilla 4.0. But bugs can be marked fixed via email from 3.4 onwards. ctj|||jjdd|_|jst j tdtj|jy)Nrrsconfiguration 'bzemail' missing) rr1r+r,bzemailrrerrvalidateconfigrs r0r1zbzxmlrpcemail.__init__|sV$#ww~~k:> ||++a BCD D DGG$rc|jdk\rd|tj|fzS|dk(rd}d|tj|fzS)Nrs@%s %srsbug_ids@%s = %s)rrbytestr)r. fieldnamevalues r0makecommandlinezbzxmlrpcemail.makecommandlinesQ ??a  8+;+;E+BCC CE!% )X-=-=e-D!EE Erc|j|}|jjj|g|jd}|dsu|j j dd}|jjj|g|jd}|ds!tjtd|z|ddd}|j|jd|d j|d z|z}tj|j }tj|j ||}tj|j |j |} tj"|j ||} || d <| | d <tj$|j d || d<tj&|j } | || | j)y)asend modification message to Bugzilla bug via email. The message format is documented in the Bugzilla email_in.pl specification. commands is a list of command lines, comment is the comment text. To stop users from crafting commit comments with Bugzilla commands, specify the bug ID via the message body, rather than the subject line, and leave a blank line after it. )smatchrsusersrr$s(default bugzilla user %s email not foundrsemailr s sFromsTosBug modificationsSubjectN)r8rrrrr+r,rrerrr(rWr _charsets addressencoder" mimeencode headencoderi as_string) r.rEcommandscommentr6r5matchesrGr+r"rsendmails r0send_bug_modify_emailz#bzxmlrpcemail.send_bug_modify_emails!!),,,##''v 6 x 77>>+w7Dll''++ 6T\\:G8$kkABTIx #H-,,UE:;zz(#g-7NN477+ !!$''4;$$TWWdllIFoodggtY7G E // GG() J<<(w 0rc4g}d|vr$|j|jd|dd|vrV|j|jd|j|j|jd|j|j ||||y)Nrrrs bug_statusr)rr(rrr4)r.rErFrGr6cmdss r0rHzbzxmlrpcemail.updatebugs x  KK,,\8H;MN O X  KK,,]DNNK L KK,,]D  \B!WW^^K9IJrNc dj|jg|Dcgc]}tj|c}z}i}|jr|j|d<n6|j r*|j r|j |d<|j |d<|r||d<|r$d|tjj|fz}|Scc}w)Nrsapi_keyrrrs%s?%s) rWr<rr%r=r5r_r r urlencode)r.targetsinclude_fieldsr r qvs r0apiurlzbzrestapi.apiurlsii g(Ng)9)9!).putrequestcy)NrSr;)r.s r0 get_methodz0bzrestapi._submit..putrequest.get_methods!rN)rMrNrOrWr;rr0 putrequestrUs"rrXs Content-Typesapplication/jsonrFrGrH)jsondumpsr rrr openerr+rIrrJrrKrLrMrrerr8) r.rNdatamethodrX request_typereqrOrPs r0_submitzbzrestapi._submitszz$ V  "T[[00 "&L;;..L49L'MN ::dgg&++C0D&&tyy{3 3{{$$ yyCkk!$;"<==yyCj   s(AB99D"ADD"ct}|D])}|jd|fd} |j|+|D]}||=y#t$r|j |YSwxYw)r:bugrrBN)setrDrQr8add)r.r<badbugsrErNs r0r=zbzrestapi.filter_real_bug_idssj%E;;y;ID # D! EU  # E" #sAA! A!cRt||jD]}|jd|dfd}|j|}|dt j |d}t fd|Ds]|jjtd|fz||=y ) r@rbrrrcrrc3,K|] }|dv yw)rNr;).0r sns r0 z6bzrestapi.filter_cset_known_bug_ids..s6X27#XsrN) rrrDrQrr%anyr+rr)r.rAr<rErNresultr rjs @r0rBz#bzrestapi.filter_cset_known_bug_idss 4[YY[E;; +GD[[&Fgx'7'7'>? LH6X66BCbk"K!rci}d|vr|d|d<d|vr|j|d<|j|d<|rO|ddd|d<|jd |f}|j||d |jj d |zy|jd |df}|j||ddd|jj d |zy)rDrrrrrF)rs is_privates is_markdownrrbrS)r]supdated bug %s sadded comment to bug %s N)rrrDr`r+debug)r.rErFrGr6bugmodrNs r0rHzbzrestapi.updatebugs  x #+H#5F< X  $F9 $($6$6F= ! !$ %"F:  ;;/D LLvfL 5 GGMM-5 6;;z:;D LL $#($)  GGMM6> ?rcyrJr;rKs r0rLzbzrestapi.notifyAs rr)sPOST) rMrNrOrPr1rDrQr`r=rBrHrLr;rr0r:r:s2K  .  @D rr:c6eZdZeeeeeedZ dZ dZ dZ dZ y)bugzilla)s2.16s2.18s3.0sxmlrpcs xmlrpc+emailsrestapicJ||_||_|jjdd} tj|}||j|_ tj|jjddtj|_ tj|jjddtj|_tjd|_y#t $r"t jtd|zwxYw)Nrr&s!bugzilla version %s not supportedrrs\D+)r+repor,rs _versionsrrrerbzdriverrecompile IGNORECASEbug_refix_resplit_re)r.r+ru bzversionbzclasss r0r1zbugzilla.__init__Vs GGNN; ;  ((3G  ( jj GGNN; 2BMM  jj GGNN; 5r}}   7+  ++67)C  s C77+D"c`d}i}|jj|j|}|jj|j|} i}|s|sn |s|}n+|s|}n&|j |j kr|}n|}|j }||ur2|jj|j|}d|vr3|d=n/|jj|j|}d|d< |j d} t|j d} | |d<|jj|D]} | s||t!| <|r|j"j%||r*|j"j'|j)||S#t$r|j d}YwxYw#t$rYt$rYt$r9|jjtd|j dzYwxYw)zreturn bugs dictionary created from commit comment. Extract bug info from changeset comments. Filter out any that are not known to Bugzilla, and any that already have a reference to the given changeset in their comments. rrNrr{rs%s: invalid hours )r{search descriptionr|startendgroup IndexErrorfloatrrr+rrr}rrfrwr=rBrA) r.ctxrr<bugmatchfixmatch bugattribsmrZhoursrs r0 find_bugszbugzilla.find_bugsks;;%%coo&7?;;%%coo&7?JH>>#hnn&66 A AEEGEH};;--coo.?GZ'"6*;;--coo.?G%) 6" !ggfo Naggh/0', 8$mm))#. *SW /IP  MM - -d 3  MM 3 3CHHJ E ) !ggaj !    Nq!781778;LLM Ns0F7G7GG H-"H-,>H-,H-c fd}d}jjdd}|sjjdd}|s |s td}tj||}tj jj |}jj|j||jtj|jjddj j|j j jj} jj||| t!j"|j%y) z0update bugzilla bug with reference to changeset.ctjjdd}tj|}|dkDr,|j d}|dk(r |S||dzd}|dz}|dkDr,|S)zJstrip leading prefix of repo root and turn into url-safe path.rrrrrr{N)rfr+r,r pconvertr)rootcountr r.s r0webrootz bugzilla.update..webroots{{H=>E==&D!)IIdO7KAEG}  !) KrNrr!r sUchangeset {node|short} in repo {root} refers to bug {bug}. details: {desc|tabindent}swebsbaseurl)changesbughgwebrr)r+r,rr templatespecchangesettemplaterru pushbuffershow changesetrr%r popbufferrwrHr emailr5) r.rErFrrmapfiletmplspecr r\s ` r0rzbugzilla.updates& ww~~k;7ggnn[(;Gt?D&&tW5  ) )$''499d C   MMO  '''..4DIINN+  ww  "  8T:#3#3CHHJ#? rc<|jj||y)z1ensure Bugzilla users are notified of bug change.N)rwrLrKs r0rLzbugzilla.notifys T9-rN)rMrNrOrRrrrr r:rvr1rrrLr;rr0rsrsJs3& I,*7r' R.rrsc |!tjtd|z t||}||}|j |}|rQ|D]}|j |||||j |tj|jyy#t$r9} tjtdtj| zd} ~ wwxYw)zadd comment to bugzilla for each changeset that refers to a bugzilla bug id. only add a comment once per bug, so same change seen multiple times does not fill bug with duplicate data.Ns)hook type %s does not pass a changeset idsBugzilla error: %s) rrerrsrrrLr rr5 Exception forcebytestr) r+ruhooktyperArwr>rr<res r0hookrs |kk : ;h F   Q b$ 4j||C   #tCy#. IIdJ,,SXXZ8 9  Qkk!12Z5L5LQ5OOPPQsA4B C$4CCr)(rPrYrxrmercurial.i18nrmercurial.noder mercurialrrrrr r r mercurial.utilsr r r testedwith configtable configitemdynamicdefaultr(rRrrrrrrrrr  LookupErrorr8r:rsrr;rr0rs[|   NN #  !Y ! !+ .     %      )         >             % %       >                     * * \shsl 7  , $C$C$T=,i.A.A= A0)2I2IA Z/xZ/zTAHTAn { D D NE.E.PQr