Could we stop linting from being a failure when on...
# tools
s
Could we stop linting from being a failure when only one part of a channel snapshot is empty? For instance:
Copy code
[
   "test_output_search.0:md5,e85671ec77d822e9b952110e7f87ef93",
   "test_output_search.1:md5,d41d8cd98f00b204e9800998ecf8427e",
   "test_output_search.dbtype:md5,cbe23d9655fccd4311acdd6261c81bd8",
   "test_output_search.index:md5,c9323312ba44d0a8bb44136d7d5b951f"
]
This fails linting because
test_output_search.1
is an empty file, but the rest of the output is fine
s
that lint check is useful to know which output files are empty. how about you do an exists or assert the md5 == d41d8cd98f00b204e9800998ecf8427e ?
s
It is useful, but this channel is a folder that happens to contain 4 files. I tried to exclude it using https://nf-co.re/docs/contributing/nf-test/assertions#snapshot-sorted-list--exclude-a-specific-file but couldn't manage to get it to work (it was trying to snapshot the entire workspace....)
s
ya i can understand.....so you are capturing entire
.out
currently ?
s
Was trying to yes
s
and can you share how you tried the exclude ?
s
Copy code
{ assert snapshot(
                    process.out.db_search.get(0).get(1).findAll { file(it).name != "test_output_search.1" },
                    path(process.out.versions[0]).yaml
                    ).match() }