Bastien Boutonnet

Hi @donttrickrick I'm sorry you're experiencing an issue. In order for us to help more efficiently can you make sure you provide us with the full log of the scan...

It would also be helpful to see how you defined the check that is currently not working, so a copy of the SodaCL for this check is what we need.

I think the best at this stage would be to follow your intuition and see if indeed you can make it work, then we'll gladly welcome a PR. At this...

I'll see how to do that. I'm not aware of OpenVSX registry

@JCZuurmond is that something you might want to look into once the PR you currently have is merged?

@JCZuurmond at this stage we simply want to ingest the **select** statement and show it to users. We're not going to be retrieving these failed rows (at least for now)....

@JCZuurmond by the info you mean the select statement right? We have a "Failed Rows" section in which we can generate a message. Check the Slite page link I shared...

Ok, and what do you think about the proposal?

I see your points @JCZuurmond here are some counter points that I think should help us make a final call: > we can benefit from the stored failures by not...

Awesome! And down the line we might consider pumping the failed rows from that select into the UI but I would see it as a separate exercice.