[tahoe-lafs-trac-stream] [tahoe-lafs] #1519: trac: revision log doesn't always see commits

[tahoe-lafs]

#1519: trac: revision log doesn't always see commits
------------------------------------+--------------------------------
     Reporter:  davidsarah          |      Owner:  somebody
         Type:  defect              |     Status:  closed
     Priority:  major               |  Milestone:  soon (release n/a)
    Component:  dev-infrastructure  |    Version:  1.9.0a1
   Resolution:  fixed               |   Keywords:  trac darcs
Launchpad Bug:                      |
------------------------------------+--------------------------------
Changes (by daira):

 * status:  new => closed
 * resolution:   => fixed
 * milestone:  undecided => soon (release n/a)


Old description:

> I committed a patch to [source:docs/write_coordination.rst], with
> description "docs/write_coordination.rst: fix formatting and add more
> specific warning about access via sshfs." The revision immediately before
> this commit was r5236. The trac source browser shows the effect of the
> patch on the file, but it does not show the commit, either in the
> revision log (global or per-file) or in the annotated rendering of the
> file.
>
> I suspect that the trac notification posthook sometimes fails, although
> there is no indication that it did in the {{{darcs push}}} output:
> {{{
> [...]
> Thu Sep  1 00:21:48 BST 2011  david-sarah at jacaranda.org
>   * docs/write_coordination.rst: fix formatting and add more specific
> warning about access via sshfs.
> Shall I push this patch? (10/10)  [ynWsfvplxdaqjk], or ? for help: y
> Enter passphrase for key '/home/davidsarah/.ssh/id_rsa':
> Note: if you want to change the default remote repository to
> source at tahoe-lafs.org:darcs/tahoe-lafs/trunk,
> quit now and issue the same command with the --set-default flag.
> now in tahoe-lafs.orgs generic-posthook.sh
> about to sh notify-trac.sh
> Finished applying...
> Posthook ran successfully.
> Finished applying...
> Posthook ran successfully.
> sending 1 change to buildmaster:
>  20110831232148-93fa1-7405c0ec191575e135f61093ee2fe45dc45b4ce5.gz
> change sent successfully
> Push successful.
> }}}

New description:

 I committed a patch to [source:docs/write_coordination.rst], with
 description "docs/write_coordination.rst: fix formatting and add more
 specific warning about access via sshfs." The revision immediately before
 this commit was r5236. The trac source browser shows the effect of the
 patch on the file, but it does not show the commit, either in the revision
 log (global or per-file) or in the annotated rendering of the file.

 I suspect that the trac notification posthook sometimes fails, although
 there is no indication that it did in the {{{darcs push}}} output:
 {{{
 [...]
 Thu Sep  1 00:21:48 BST 2011  david-sarah at jacaranda.org
   * docs/write_coordination.rst: fix formatting and add more specific
 warning about access via sshfs.
 Shall I push this patch? (10/10)  [ynWsfvplxdaqjk], or ? for help: y
 Enter passphrase for key '/home/davidsarah/.ssh/id_rsa':
 Note: if you want to change the default remote repository to
 source at tahoe-lafs.org:darcs/tahoe-lafs/trunk,
 quit now and issue the same command with the --set-default flag.
 now in tahoe-lafs.orgs generic-posthook.sh
 about to sh notify-trac.sh
 Finished applying...
 Posthook ran successfully.
 Finished applying...
 Posthook ran successfully.
 sending 1 change to buildmaster:
  20110831232148-93fa1-7405c0ec191575e135f61093ee2fe45dc45b4ce5.gz
 change sent successfully
 Push successful.
 }}}

--

Comment:

 Replying to [comment:3 zooko]:
 > This will probably be fixed by our move to git -- #1644.

 I think it was.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1519#comment:4>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage