Thorben Thuermer

`nagstamon --help` prints the help of nagstamon-cli, which has completely different invocation than nagstamon gui.

2

i was trying to run two nagstamon instances with different configs, and wondering why it was not working... then, by conincidence, i noticed this: ``` $ nagstamon --config=$HOME/.nagstamon_dev/ 2>&1 An...

remove manual confirmation after each batch (or make it optional)

2

both `query` and `upsert` interactively ask the user for confirmation after each batch of entries: https://github.com/nshmura/dsio/blob/bd941641acb0201322c8a789acee77a3b7a584d5/action/query.go#L310 https://github.com/nshmura/dsio/blob/bd941641acb0201322c8a789acee77a3b7a584d5/action/upsert.go#L79 this is kind of silly, especially when batch-processing (large amounts of) data. it...

query output duplicates 'entities' header for each batch

1

one would expect that '''query''' produces an output file that can be read back by '''upsert'''. this does **not** work, because query will duplicate the '''entities:'' key for each batch,...

log output clobbers data output.

1

the code in ```core/log.go``` writes log messages to stdout, which is where the tool also writes the output of queries. when redirecting the data to a file or parsing it,...

requests are sent without content-type header

3

since ES 5.3, every request without content-type header triggers a warning. Content type detection for rest requests is deprecated. Specify the content type using the [Content-Type] header. just look at...

we are seeing lots of: ```[WARN][RestController ] Content type detection for rest requests is deprecated. Specify the content type using the [Content-Type] header.``` from elasticsearch. it is probably a general...