#48 closed enhancement (fixed)
cavern: Errors do not say 'ERROR'
| Reported by: | Wookey | Owned by: | Olly Betts |
|---|---|---|---|
| Priority: | minor | Milestone: | 1.2.18 |
| Component: | cavern | Version: | 1.2.16 |
| Keywords: | Cc: | speleology.erin@… |
Description
On cavern runs the warnings say 'WARNING' but the errors (which prevent a 3d file being output) do not say 'ERROR', so it can be very hard to find the actual offending issue in the output, especially when there is a lot of it.
This is noticeable in a project with backbearings for example, where a lot of 'mismatched backbearing' warnings can obscure the important ERROR lines.
Can we please just mark errors explicitly with something greppable? (probably 'ERROR:')
This could be described as an enhancement or a bug, but I'm going to file it as a bug as it seems wrong, given the WARNING output.
Change History (2)
comment:1 Changed 10 years ago by
| Cc: | speleology.erin@… added; Erin Lynch <speleology.erin@…> removed |
|---|---|
| Component: | Other → cavern |
| Milestone: | → 1.2.18 |
| Status: | new → assigned |
| Type: | defect → enhancement |
comment:2 Changed 10 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Implemented in [5a45706b].
Version 0, edited 10 years ago
by
(next)
Note: See
TracTickets for help on using
tickets.
If the mismatched backbearing warnings are that noisy, that ought to be addressed somehow. The warnings are meant to be useful, and if they're drowning out useful information they aren't helping.
I've not done much work with data containing backsights myself, so this needs feedback from people who use them.