Zach Daniel

I checked, and its not the call to `:zip.create/3` causing the slowness its the call to `Elixlsx.Writer.create_files/2`

This is the error that I get: ``` ==> ex_termbox cd c_src/termbox && CFLAGS=-fPIC ./waf configure --prefix=. && ./waf env: python: No such file or directory make: *** [c_src/termbox/build/src/libtermbox.a] Error...

@tsloughter Two PRs to opencensus_phoenix that I believe brings it to parity: https://github.com/opencensus-beam/opencensus_phoenix/pull/4 https://github.com/opencensus-beam/opencensus_phoenix/pull/5

Vince made this and linked to it in the minutes google doc, but I'm posting it here so everyone can see it: https://github.com/binaryseed/seq_trace_intro

That’s a good point. If we went this route, we’d be forcing all messages sent from a traced process to include additional data, as opposed to having to “manually” propagate...

I suspect you are right, but it would be a new side effect that we would probably want to make very clear. I think your point in our meeting was...

Any updates here? I'm experiencing a similar issue. Some kind of information on the syntax error would be immensely helpful.

yep, you're correct. Perhaps what we can do for now is make an explicit allowance for `BREAKING CHANGE: ...` in the commit parser, i.e the subject line of a "nested"...

AFAIK, `BREAKING CHANGE:` is the only special prefix. Either way, I rely on that behavior regularly because I squash commits on all my projects. We can push to fix that...

I don't know if its possible to fix the parser w/o removing the feature of allowing nested commit messages. There is no way to tell the difference between a "footer"...