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
Even after an explicit conversion to utf8 binary, the string does not look good.
{ok, Db} =cozo:open(),
(fun({error, E}) -> io:format("~s~n", [<< <<X/utf8>> || X<-E >>]) end)(cozo:run(Db, "?[] <- [[1,2,3,,]]")),
cozo:close(Db).
{"causes":[],"code":"parser::pest","display":"\u001b[31mparser::pest\u001b[0m\n\n\u001b[31mÃ\u001b[0m The query parser has encountered unexpected input / end of input at 15..15\n âââââ\n\u001b[2m1\u001b[0m â ?[] <- [[1,2,3,,]] \n · \u001b[35;1m â²\u001b[0m\n â°ââââ \n","filename":"","labels":[{"span":{"length":0,"offset":15}}],"message":"The query parser has encountered unexpected input / end of input at 15..15","ok":false,"related":[],"severity":"error"}
After filtering, colors code are still present.
Filter=fun(X) whenX>255 -> false; (_) -> trueend,
{ok, Db} =cozo:open(),
(fun({error, E}) -> io:format("~p~n", [lists:filter(Filter, E)]) end)(cozo:run(Db, "?[] <- [[1,2,3,,]]")),
cozo:close(Db).
"{\"causes\":[],\"code\":\"parser::pest\",\"display\":\"\\u001b[31mparser::pest\\u001b[0m\\n\\n \\u001b[31m×\\u001b[0m The query parser has encountered unexpected input / end of input at 15..15\\n \\n \\u001b[2m1\\u001b[0m ?[] <- [[1,2,3,,]] \\n · \\u001b[35;1m \\u001b[0m\\n \\n\",\"filename\":\"\",\"labels\":[{\"span\":{\"length\":0,\"offset\":15}}],\"message\":\"The query parser has encountered unexpected input / end of input at 15..15\",\"ok\":false,\"related\":[],\"severity\":\"error\"}"
It could be due to supports_color crate, to termcolor crate or another configuration somewhere. Even after setting NO_COLOR_TERM=1 environment variable, color tags are still printed.
The text was updated successfully, but these errors were encountered:
When executing a query, data returned by the interfaces are not correctly parsed
Even after an explicit conversion to utf8 binary, the string does not look good.
After filtering, colors code are still present.
It could be due to
supports_color
crate, totermcolor
crate or another configuration somewhere. Even after settingNO_COLOR_TERM=1
environment variable, color tags are still printed.The text was updated successfully, but these errors were encountered: