Closed jgough closed 3 years ago
I want to point out that it isn't simply just the presence of an empty file that does this, if you move the output{}
section into the new file the issue still occurs. Just found it odd that the presence of an empty file alters the behaviour! Thanks!
@jgough Thanks again for your detailed bug report. I can confirm the existence of this bug in beta1. In current master, this bug is gone. So look forward to the next beta release. I verified this with the altered integration tests in #140.
In Beta 1, sometimes the codec does not get transferred when running the tests.
For example I have the following file in my pipeline:
And the test
Then the tests pass. The input generator created by lfv in
/tmp/lfv-*/session/*/lfv_inputs/1/input.conf
correctly looks like this:If I create simply an empty file called
99-output.conf
and place it in the same directory and run again then strangely it fails. It reverts to the plain codec and it looks like this:Here is a Dockerfile that can be used to repro this issue, if that is of any help:
Build and run with:
Am I doing something wrong here? As an aside, is there a better way of testing using the CSV codec here where multiple separate lines are required to get the headers?