More descriptive error messages

Question

More descriptive error messages

Opened this issue 9 years ago · 12 comments

amikhalev commented 9 years ago

Some errors we have encountered that are annoying to debug

Missing config key
Wrong type for config node
Missing command

zachjs commented 9 years ago

Status?

Answer 1 · 2015-02-09T17:09:46.000Z

Proposal: add an "Expecting" log level. This would be for when something is expecting something else, and will crash when it does not exist. Examples include config and Kremlin.

Answer 2 · 2015-02-09T23:59:51.000Z

So we are going to clutter the log with a bunch of those messages?

Answer 3 · 2015-02-10T00:04:29.000Z

They can be hidden in TatorTool by default

Answer 4 · 2015-02-10T00:05:17.000Z

There are better solutions than that

Answer 5 · 2015-02-10T00:06:37.000Z

I think my solution solves other problems too, and generally helps with debugging.

Answer 6 · 2015-02-10T00:07:28.000Z

Also, doing anything with YAML will be a pain.

Answer 7 · 2015-02-12T07:54:45.000Z

@PlasmaPower Bump

Answer 8 · 2015-02-12T15:26:21.000Z

@amikhalev Why don't you do this? I barely know where to begin.

Answer 9 · 2015-02-25T15:27:38.000Z

Missing command: done
All things yaml: not done

Answer 10 · 2015-03-03T07:14:11.000Z

@PlasmaPower Another thing that would help is better stack traces, but I'm not sure if that is possible

Answer 11 · 2015-03-16T22:04:27.000Z

@amikhalev For one thing, we could preload /lib/libSegFault.so for better seg fault messages.