Closed andrewcooke-isti closed 7 years ago
I started doing some of this in isti-refactor branch and will double check that it is done.
Dylan - There are few info log messages which old evalresp could spit out with the verbose logging. Could you please try to reproduce those in the new code
Could You provide an example, otherwise I see that all cases that were in her from the beginning of june have been taken care of.
ilya may be referring to the old code dumping SEED file fragments.
IIRC that includes calling some code that was problematic for some reason. how important is this?
this issue is ONLY for creation of a log that uses the flags.
Dylan - please organise your code and make a merge request for that functionality.
Ilya - if you want some other functionality make you own issue, don't hijack this one, and please try to keep things organised.
there's a couple of comments in (the new) evalresp.c indicating where a log that sends text to stderr should be created / freed. without this th everbose flag does nothing.
also, some debug / info message would be nice - perhaps one for each channel and response handled?