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
ValueError: ('All parsers failed to parse', b'06-07-22 12:55PM 334976 opencv_frame_2.png\r\n', [KeyError('6-'), ValueError("time data '06-07-22 12:55PM' does not match format '%m/%d/%Y %I:%M %p'")])
I can replicate it with this simple test application.
parse_list_line_custom is a good and relatively simple workaround, however it would be even more convenient if we could simply pass in an expected timestamp format through init, then one would not need to re-implement the entire line parsing function.
I'm all for implementing MLSx commands but having a quick workaround would also be much appreciated.
Would you be willing to accept a pull request that adds a way to override the default timestamp format in aioftp.Client via either an init parameter or an attribute?
Would you be willing to accept a pull request that adds a way to override the default timestamp format in aioftp.Client via either an init parameter or an attribute?
Not sure this is a good idea to have multiple ways to do same thing. As I said above «All LIST outputs are for humans, they have no standard and they will be broken somehow all the time». So the most powerfull and common solution is available already.
I get the following error:
I can replicate it with this simple test application.
My suspicion is that it is because the parser expect a US date and not a european date?
The text was updated successfully, but these errors were encountered: