darcs

Issue 1969 darcs annotate fails

Title darcs annotate fails
Priority bug Status given-up
Milestone Resolved in
Superseder Nosy List dmitry.kurochkin, simonpj
Assigned To simonpj
Topics

Created on 2010-10-11.17:12:35 by simonpj, last changed 2016-04-04.14:52:55 by gh.

Files
File name Uploaded Type Edit Remove
unnamed simonpj, 2010-10-11.17:12:33 text/html
Messages
msg12685 (view) Author: simonpj Date: 2010-10-11.17:12:33
Hi darcs-ers

What does the error below mean? This is on a unix system.  Main repo is http://darcs.haskell.org/ghc.

thanks

Simon

simonpj@cam-04-unx:~/darcs/HEAD$ darcs --version
2.4.98.1 (beta 1)

simonpj@cam-04-unx:~/darcs/HEAD$ darcs annotate compiler/main/HscTypes.lhs
darcs: failed to read patch:
Thu Nov 19 14:24:22 GMT 2009  Simon Marlow <marlowsd@gmail.com>
  * Check upper/lower bounds on various RTS flags (#3633)

  Also, make K mean 1024 rather than 1000, in RTS flags (similarly for M
  and G).  The main reason I want to change it is that otherwise this
  might be confusing:

  exp3_8: error in RTS option -H4k: size outside allowed range (4096 - 18446744073709551615)

  And I think the original reason for using 1000 instead of 1024,
  worries about direct-mapped caches, is not an issue in this context
  (even if you can find a direct-mapped cache these days).
Couldn't fetch `0000005244-ade0cfb56476f9eb62552ab37f80a3e2c1e3808c8a5005eb2243ace5d74f323d'
in subdir patches from sources:

thisrepo:/home/simonpj/darcs/HEAD
cache:/home/simonpj/.darcs/cache
thisrepo:/home/simonpj/darcs/ghc
repo:http://darcs.haskell.org/ghc

simonpj@cam-04-unx:~/darcs/HEAD$
Attachments
msg13057 (view) Author: kowey Date: 2010-11-15.14:12:51
Sorry for the late reply, Simon.  It seems to mean that repo on cam-04-
unx was lazily fetched (is that correct?) which is fine, and that to do 
an annotate, darcs needed to fetch a patch file from 
http://darcs.haskell.org/ghc... which it failed to do so.

Out of curiosity, I tried fetching this file by hand, and it worked:
wget http://darcs.haskell.org/ghc/_darcs/patches/0000005244-
ade0cfb56476f9eb62552ab37f80a3e2c1e3808c8a5005eb2243ace5d74f323d

Was that a lazily fetched repository?  I wonder if this was some kind of 
intermittent network failure.  What happens if you repeat the annotate?

Thanks,
msg13071 (view) Author: simonpj Date: 2010-11-15.17:11:37
I think it was lazy.  I believe I was connected.  At least the error message could have been nicer!

I'm out of time at the moment, but I'll bleat if it happens again.

Simon

| -----Original Message-----
| From: Eric Kow [mailto:bugs@darcs.net]
| Sent: 15 November 2010 14:13
| To: dmitry.kurochkin@gmail.com; Simon Peyton-Jones
| Subject: [issue1969] darcs annotate fails
| 
| 
| Eric Kow <kowey@darcs.net> added the comment:
| 
| Sorry for the late reply, Simon.  It seems to mean that repo on cam-04-
| unx was lazily fetched (is that correct?) which is fine, and that to do
| an annotate, darcs needed to fetch a patch file from
| http://darcs.haskell.org/ghc... which it failed to do so.
| 
| Out of curiosity, I tried fetching this file by hand, and it worked:
| wget http://darcs.haskell.org/ghc/_darcs/patches/0000005244-
| ade0cfb56476f9eb62552ab37f80a3e2c1e3808c8a5005eb2243ace5d74f323d
| 
| Was that a lazily fetched repository?  I wonder if this was some kind of
| intermittent network failure.  What happens if you repeat the annotate?
| 
| Thanks,
| 
| ----------
| assignedto:  -> simonpj
| priority:  -> bug
| status: unknown -> waiting-for
| 
| __________________________________
| Darcs bug tracker <bugs@darcs.net>
| <http://bugs.darcs.net/issue1969>
| __________________________________
msg19136 (view) Author: gh Date: 2016-04-04.14:52:53
Annotate implementation is different now, and the ghc repository no
longer exists, I say we give up on this.
History
Date User Action Args
2010-10-11 17:12:35simonpjcreate
2010-11-15 14:12:51koweysetpriority: bug
status: unknown -> waiting-for
messages: + msg13057
assignedto: simonpj
2010-11-15 17:11:37simonpjsetmessages: + msg13071
2016-04-04 14:52:55ghsetstatus: waiting-for -> given-up
messages: + msg19136