These are chat archives for nextflow-io/nextflow

26th
Sep 2016
Paolo Di Tommaso
@pditommaso
Sep 26 2016 07:58
@mes5k Thanks for giving a try to improvement however the solution you are proposing is not convincing me. The TraceRecord is meant to track runtime information and I would really like to avoid to bloat it with debugging data which will add an unnecessary overhead to the serialised/deserialisation process of those objects.
I think that hashes should go into the log file or even in a separate file. Also because a similar need is starting to arise for other nextflow's subsystems.
Paolo Di Tommaso
@pditommaso
Sep 26 2016 08:03
Ideally it should be managed by the logging mechanism. It would be interesting to understand if Slf4j allows custom logging levels and categories.
Mokok
@Mokok
Sep 26 2016 09:54
(just found out that the best Google result for "Nexflow doc" is "docs.nextflow.io" and i get no response.
I don't know if it's just my proxy/firewall or not. I'm just saying.
"https://www.nextflow.io/docs/latest/index.html" still works fine)
Paolo Di Tommaso
@pditommaso
Sep 26 2016 10:05
um weird, is docs.nextflow.io a http or https url?
Emilio Palumbo
@emi80
Sep 26 2016 10:31
@pditommaso I tried the same as @Mokok. It is a https url, but it works for me.
Paolo Di Tommaso
@pditommaso
Sep 26 2016 10:32
same here
Emilio Palumbo
@emi80
Sep 26 2016 10:32
I looked for "Nextflow doc" on google.com
Paolo Di Tommaso
@pditommaso
Sep 26 2016 10:33
but https://docs.nextflow.io/ does not work
@emi80 sure that you have https://docs.nextflow.io in the google result?
Emilio Palumbo
@emi80
Sep 26 2016 10:40
@pditommaso, you are right. Actually I get a http url in the search result url=http%3A%2F%2Fdocs.nextflow.io. It is then rewritten to https://www.nextflow.io/docs/latest/index.html once I go to the link.
Paolo Di Tommaso
@pditommaso
Sep 26 2016 10:57
Just released version 0.22.1
Mokok
@Mokok
Sep 26 2016 11:51
@pditommaso @emi80 Google result is an http, But as i said, it may be due to my network (IT company). I've no way to check it out.
It may also be caused by the redirection. If it works for you, then it's fine for common people. ^^
Gratz' about the new version Paolo !
Paolo Di Tommaso
@pditommaso
Sep 26 2016 11:53
Thanks for your feedback, I've removed any link to docs.nextflow.io thus, soon or relater it should removed from google as well.
Mokok
@Mokok
Sep 26 2016 11:56
welcome.
Mike Smoot
@mes5k
Sep 26 2016 16:04
Thanks for the feedback @pditommaso, I'm glad I asked! I'll take a look at producing a separate "input_hashes" log file. The code already logs the hash values normally, which I found challenging to use, so if you're open to producing a separate log file for just the trace values, I think that would probably work fine. Can you explain the "similar needs in other subsystems" that you mentioned? Just for me to ponder as I work on a design.
Paolo Di Tommaso
@pditommaso
Sep 26 2016 17:33
@mes5k If you look at the logging in the new scheduler classes or the autoscaling your will find that I've marked them with a +++ or ### or something similar to distinguish them
for example here or here
what about having a coloured log instead of separate files ?
Mike Smoot
@mes5k
Sep 26 2016 17:43
I've only looked into this for a few minutes, but if we're using the Marker interface then I think we can get both coloring and filtering.
Anyway, I'll see if I can put something together and we can experiment!
Paolo Di Tommaso
@pditommaso
Sep 26 2016 17:44
that would be cool
:+1: