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
Possibly related to #2450 . I've only verified the crash on MacOS since I don't have access to Linux or Windows right now.
I tested on 0.6.7, 0.6.8, 0.6.9, and 0.7.0 and verified that the file path is correct by using parse_csv() with the same parameters. Parse_csv() outputs the expected file contents and does not crash on the tested versions.
To reproduce, query "SELECT * from watch_csv(filename='path/to/file')". On 0.6.8 and above, the client will panic:
The panic occurs whether the file path is correct or not. On 0.6.7, the client does not crash, but it also does not fire events when a file in the provided path is edited.
The text was updated successfully, but these errors were encountered:
Possibly related to #2450 . I've only verified the crash on MacOS since I don't have access to Linux or Windows right now.
I tested on 0.6.7, 0.6.8, 0.6.9, and 0.7.0 and verified that the file path is correct by using parse_csv() with the same parameters. Parse_csv() outputs the expected file contents and does not crash on the tested versions.
To reproduce, query "SELECT * from watch_csv(filename='path/to/file')". On 0.6.8 and above, the client will panic:
The panic occurs whether the file path is correct or not. On 0.6.7, the client does not crash, but it also does not fire events when a file in the provided path is edited.
The text was updated successfully, but these errors were encountered: