[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnu-arch-users] [HEY TOM!] unhelpful error for unreadable directori

From: Aaron Bentley
Subject: Re: [Gnu-arch-users] [HEY TOM!] unhelpful error for unreadable directories
Date: Sun, 25 Apr 2004 19:42:47 -0400
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031205 Thunderbird/0.4

Matthieu Moy wrote:

Aaron Bentley <address@hidden> writes:

No, since this error will typically happen during or before their tla
import, these will tend to be new users.  And they'll conclude that
tla is borked and chuck it.

I was a beginner with arch a few weeks ago, and I confirm:

tla's error messages are really confusing.

They  often refer  to tla's  internal implementation,  which  the user
doesn't want to know  about. The distinction between assertion failure
(error message for developers) and  user error message is not clear. I
often get assertion  failures with tla for something  that should be a
real error message.

Example (not the worst, but the first I found):

$ rm xxxyyyzzz
rm: cannot remove `xxxyyyzzz': No such file or directory
$ tla file-diffs xxxyyyzzz
error finding file id (2: No such file or directory)
 path: ./xxxyyyzzz
PANIC: arch_inventory_id

Which is the best?

What's the use of "PANIC: arch_inventory_id" for the final user?

I didn't drop  tla, but this is  in my opinion one of  the reasons why
tla  has the  reputation  of being  complex  to use.  I  can give  you
examples of people that stopped using arch because it was too complex.

This is acceptable since tla is still young, but this should change in
the future.

Yep, and I'm working on it, but feel free to pitch in; it's not hard, but there are lots of commands yet to cover. My current errors tree is:


Helper functions are in cmdutils. arch_determine_revision and arch_check_for should be especially useful.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]