For tasks like T351449, it would be useful to include some context from the batch file used in the query when an exception occurs. This can be done with e.g. grep -C 5 to get 5 lines of context around an IP address in a batch file. I am not sure what the ideal number of lines would be, but some amount of context would be better than nothing.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | None | T351430 Epic: Improve logging for ipoid app | |||
| Declined | None | T351746 Include batch file context lines when throwing an error |
Event Timeline
Comment Actions
Would the context be useful? Are you saying that when a particular IP fails we should grep around that IP from the sql file? From my experience, the IP failing on an import is normally a one-off (eg. duplicate IP) and knowing the IPs around it wouldn't affect anything. If it fails on an import, context around the statement that failed (which is returned) and context around the job (not returned) have been the most useful pieces of information.