summaryrefslogtreecommitdiffstats
path: root/test/expected/test_format_loader.sh_5992e2695b7e6cf1f3520dbb87af8fc2b8f27088.err
blob: 578c06f7fcc77f4d3c4da994ce0e1b15a74f1ba9 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
✘ error: invalid value for option “/bad_json_log/line-format#/timestamp-format”
 reason: empty values are not allowed
 --> {test_dir}/bad-config/formats/invalid-json-format/format.json:11
 |                 "timestamp-format": ""  
 = help: Property Synopsis
           /bad_json_log/line-format#/timestamp-format <string>
         Description
           The strftime(3) format for this field
⚠ warning: unexpected value for property “/bad-name-log/title”
 --> {test_dir}/bad-config/formats/invalid-name/format.json:4
 |         "title": "bad-format",          
 =   help: Available Properties
           $schema The URI of the schema for this file
           (\w+)/
⚠ warning: unexpected value for property “/bad-name-log/description”
 --> {test_dir}/bad-config/formats/invalid-name/format.json:5
 |         "description": "Log format with a name that has invalid characters",
 =   help: Available Properties
           $schema The URI of the schema for this file
           (\w+)/
⚠ warning: unexpected value for property “/bad-name-log/json”
 --> {test_dir}/bad-config/formats/invalid-name/format.json:6
 |         "json": true                    
 =   help: Available Properties
           $schema The URI of the schema for this file
           (\w+)/
✘ error: “invalid(abc” is not a valid regular expression
 reason: missing closing parenthesis
 --> /invalid_props_log/tags/badtag3/pattern
 | invalid(abc                             
 |            ^ missing closing parenthesis
 --> {test_dir}/bad-config/formats/invalid-properties/format.json:36
 |                 "pattern": "invalid(abc"
 = help: Property Synopsis
           /invalid_props_log/tags/badtag3/pattern <regex>
         Description
           The regular expression to match against the body of the log message
         Example
           \w+ is down
✘ error: “abc(def” is not a valid regular expression
 reason: missing closing parenthesis
 --> /invalid_props_log/search-table/bad_table_regex/pattern
 | abc(def                                 
 |        ^ missing closing parenthesis    
 --> {test_dir}/bad-config/formats/invalid-properties/format.json:41
 |                 "pattern": "abc(def"    
 = help: Property Synopsis
           /invalid_props_log/search-table/bad_table_regex/pattern <regex>
         Description
           The regular expression for this search table.
✘ error: “^(?<timestamp>\d+: (?<body>.*)$” is not a valid regular expression
 reason: missing closing parenthesis
 --> /bad_regex_log/regex/std/pattern
 | ^(?<timestamp>\d+: (?<body>.*)$                             
 |                                ^ missing closing parenthesis
 --> {test_dir}/bad-config/formats/invalid-regex/format.json:6
 |                 "pattern": "^(?<timestamp>\\d+: (?<body>.*)$"
 = help: Property Synopsis
           /bad_regex_log/regex/std/pattern <message-regex>
         Description
           The regular expression to match a log message and capture fields.
✘ error: “(foo” is not a valid regular expression
 reason: missing closing parenthesis
 --> pattern
 | (foo                                    
 |     ^ missing closing parenthesis       
 --> {test_dir}/bad-config/formats/invalid-regex/format.json:13
 |             "error": "(foo"             
 = help: Property Synopsis
           /bad_regex_log/level/error <pattern|integer>
         Description
           The regular expression used to match the log text for this level.  For JSON logs with numeric levels, this should be the number for the corresponding level.
✘ error: “abc(” is not a valid regular expression
 reason: missing closing parenthesis
 --> /bad_regex_log/highlights/foobar/pattern
 | abc(                                    
 |     ^ missing closing parenthesis       
 --> {test_dir}/bad-config/formats/invalid-regex/format.json:25
 |                 "pattern": "abc("       
 = help: Property Synopsis
           /bad_regex_log/highlights/foobar/pattern <regex>
         Description
           A regular expression to highlight in logs of this format.
⚠ warning: format file is missing “$schema” property
 --> {test_dir}/bad-config/formats/invalid-regex/format.json
 =   note: the schema specifies the supported format version and can be used with editors to automatically validate the file
 =   help: add the following property to the top-level JSON object:
             "$schema": "https://lnav.org/schemas/format-v1.schema.json",
✘ error: “foo” is not a valid value for option “/bad_sample_log/value/pid/kind”
 --> {test_dir}/bad-config/formats/invalid-sample/format.json:24
 |                 "kind": "foo"           
 = help: Property Synopsis
           /bad_sample_log/value/pid/kind <data-type>
         Description
           The type of data in the field
         Allowed Values
           string, integer, float, boolean, json, struct, quoted, xml
✘ error: 'bad' is not a supported log format $schema version
 --> {test_dir}/bad-config/formats/invalid-schema/format.json:2
 |     "$schema": "bad"                    
 = note: expecting one of the following $schema values:
           https://lnav.org/schemas/format-v1.schema.json
 = help: Property Synopsis
           /$schema The URI of the schema for this file
         Description
           Specifies the type of this file
✘ error: SQL expression is invalid
 reason: unrecognized token: "'foobar"
 --> /bad_file_format1/converter/header/expr/default
 | :header REGEXP 'foobar                  
✘ error: A command is required when a converter is defined
 --> {test_dir}/bad-config/formats/invalid-file-format/format.json:4
 = help: The converter command transforms the file into a format that can be consumed by lnav
✘ error: invalid line format element “/bad_json_log/line-format/0/field”
 reason: “” is not a defined value
 --> {test_dir}/bad-config/formats/invalid-json-format/format.json:7
✘ error: invalid pattern: “incomplete-match”
 reason: pattern does not match entire message
 --> {test_dir}/bad-config/formats/invalid-regex/format.json:20
 | 1428634687123; foo                      
 |               ^ matched up to here      
 = note: incomplete-match = ^(?<timestamp>\d+);
 = help: update the regular expression to fully capture the sample message
✘ error: invalid sample log message: "abc: foo"
 reason: unrecognized timestamp -- abc
 --> {test_dir}/bad-config/formats/invalid-sample/format.json:34
 = note: the following custom formats were tried:
           abc
           ^ “%i” matched up to here
 = help: If the timestamp format is not supported by default, you can add a custom format with the “timestamp-format” property
✘ error: invalid sample log message: "1428634687123| debug hello"
 reason: “debug” does not match the expected level of “info”
 --> {test_dir}/bad-config/formats/invalid-sample/format.json:37
 = note: matched regex = with-level
         captured level = “debug”
         level regular expression match results:
           /bad_sample_log/level/debug = debug
             debug
             ^---^
           /bad_sample_log/level/info = info
             no match
 = help: Level regexes are not anchored to the start/end of the string.  Prepend “^” to the expression to match from the start of the string and append “$” to match up to the end of the string.
✘ error: invalid pattern: “with-level”
 reason: pattern does not match entire multiline sample message
 --> {test_dir}/bad-config/formats/invalid-sample/format.json:41
 = note: with-level = ^(?<timestamp>\d+)\| (?<level>\w+) (?<body>\w+)$
 = help: use “.*” to match new-lines
✘ error: invalid sample log message: "1428634687123; foo bar"
 reason: sample does not match any patterns
 --> {test_dir}/bad-config/formats/invalid-sample/format.json:45
 = note: the following shows how each pattern matched this sample:
            1428634687123; foo bar
                         ^ bad-time matched up to here
                              ^ semi matched up to here
                         ^ std matched up to here
                         ^ with-level matched up to here
 = note: bad-time   = “^(?<timestamp>\w+): (?<body>\w+)$”
         semi       = “^(?<timestamp>\d+); (?<body>\w+)$”
         std        = “^(?<timestamp>\d+): (?<pid>\w+) (?<body>.*)$”
         with-level = “^(?<timestamp>\d+)\| (?<level>\w+) (?<body>\w+)$”
         
⚠ warning: invalid pattern: “/bad_sample_log/regex/semi”
   reason: pattern does not match any samples
 --> {test_dir}/bad-config/formats/invalid-sample/format.json:10
 =   help: every pattern should have at least one sample that it matches
⚠ warning: invalid pattern: “/bad_sample_log/regex/std”
   reason: pattern does not match any samples
 --> {test_dir}/bad-config/formats/invalid-sample/format.json:7
 =   help: every pattern should have at least one sample that it matches
✘ error: invalid pattern: “/invalid_props_log/regex/std”
 reason: no timestamp capture found in the pattern
 --> {test_dir}/bad-config/formats/invalid-properties/format.json:4
 = help: all log messages need a timestamp
⚠ warning: invalid value “/invalid_props_log/value/non-existent”
   reason: no patterns have a capture named “non-existent”
 --> {test_dir}/bad-config/formats/invalid-properties/format.json:4
 =   note: the following captures are available:
             body, pid, timestamp
 =   help: values are populated from captures in patterns, so at least one pattern must have a capture with this value name
✘ error: invalid tag definition “/invalid_props_log/tags/badtag”
 reason: tag definitions must have a non-empty pattern
 --> {test_dir}/bad-config/formats/invalid-properties/format.json:4
✘ error: invalid tag definition “/invalid_props_log/tags/badtag2”
 reason: tag definitions must have a non-empty pattern
 --> {test_dir}/bad-config/formats/invalid-properties/format.json:4
✘ error: invalid tag definition “/invalid_props_log/tags/badtag3”
 reason: tag definitions must have a non-empty pattern
 --> {test_dir}/bad-config/formats/invalid-properties/format.json:4
✘ error: “invalid_props_log” is not a valid log format
 reason: “subsecond-unit” must be set when “subsecond-field” is used
 --> {test_dir}/bad-config/formats/invalid-properties/format.json:4
✘ error: invalid value for property “/invalid_props_log/timestamp-field”
 reason: “ts” was not found in the pattern at /invalid_props_log/regex/std
 --> {test_dir}/bad-config/formats/invalid-properties/format.json:4
 = note: the following captures are available:
           body, pid, timestamp
✘ error: “not a color” is not a valid color value for property “/invalid_props_log/highlights/hl1/color”
 reason: Unknown color: 'not a color'.  See https://jonasjacek.github.io/colors/ for a list of supported color names
 --> {test_dir}/bad-config/formats/invalid-properties/format.json:24
✘ error: “also not a color” is not a valid color value for property “/invalid_props_log/highlights/hl1/background-color”
 reason: Unknown color: 'also not a color'.  See https://jonasjacek.github.io/colors/ for a list of supported color names
 --> {test_dir}/bad-config/formats/invalid-properties/format.json:25
✘ error: “no_regexes_log” is not a valid log format
 reason: no regexes specified
 --> {test_dir}/bad-config/formats/no-regexes/format.json:4
✘ error: “no_regexes_log” is not a valid log format
 reason: log message samples must be included in a format definition
 --> {test_dir}/bad-config/formats/no-regexes/format.json:4
✘ error: “no_sample_log” is not a valid log format
 reason: log message samples must be included in a format definition
 --> {test_dir}/bad-config/formats/no-samples/format.json:4
✘ error: invalid sample log message: "gitea  | 2023/09/24 22:15:55 cmd/web.go:223:runWeb() [I] Starting Gitea on PID: 7"
 reason: timestamp was not captured
 --> {test_dir}/bad-config/formats/invalid-no-tscap/format.json:25
 = help: A timestamp needs to be captured in order for a line to be recognized as a log message
✘ error: failed to compile SQL statement
 reason: near "TALE": syntax error
 --> {test_dir}/bad-config/formats/invalid-sql/init.sql:4
 | -- comment test                         
 | CREATE TALE invalid (x y z);            
 |        ^ near "TALE": syntax error      
✘ error: failed to execute SQL statement
 reason: ✘ error: “abc(” is not a valid regular expression
 |        reason: missing closing parenthesis
 |        --> arg
 |        | abc(                                    
 |        |     ^ missing closing parenthesis
 --> {test_dir}/bad-config/formats/invalid-sql/init2.sql
 | SELECT regexp_match('abc(', '123')      
 | FROM sqlite_master;