You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Repro is with Brim commit 96a0951 which uses Zed commit 22f640e. This issue feels very similar to the existing JSON-related one in #2554.
A community zync user reported a problem reading CSV with Zui. In their own words:
Zui did not report any problem. It just stopped the CSV import without any message at all. I noticed because I compared count() to the wc.
maybe simply send a more comprehensive error message in Zed/Zui when CSV import fails before the EOF? line number and column number with last value parsed?
Indeed, as shown in the following video, reading the file bad.csv using CLI tooling does show an error, but the app just shows the data that parsed ok without any mention of the error. This is a data correctness hazard since it gives the user the impression they're working with all their data when it's actually truncated.
Repro.mp4
As we can see in Wireshark, the error message was returned from the backend, but just didn't make it all the way to the user.
The text was updated successfully, but these errors were encountered:
As shown in the attached video, now the user is shown a warning when this partial load occurs, then they can click this for further detail.
Verify.mp4
It's been pointed out that the "Load successful" pop-up does represent a contradictory message alongside the "Ingest failed with warnings" message, so #2660 has been opened to improve on that.
Repro is with Brim commit 96a0951 which uses Zed commit
22f640e
. This issue feels very similar to the existing JSON-related one in #2554.A community zync user reported a problem reading CSV with Zui. In their own words:
Indeed, as shown in the following video, reading the file bad.csv using CLI tooling does show an error, but the app just shows the data that parsed ok without any mention of the error. This is a data correctness hazard since it gives the user the impression they're working with all their data when it's actually truncated.
Repro.mp4
As we can see in Wireshark, the error message was returned from the backend, but just didn't make it all the way to the user.
The text was updated successfully, but these errors were encountered: