Error "... does not exist (The system cannot find the file specified.)"

[cja-github]

I ran $OutputEncoding = [console]::InputEncoding = [console]::OutputEncoding = New-Object System.Text.UTF8Encoding

And then .\kept -t C:\Users\cja\Downloads\takeout-20230305T104856Z-001\Takeout\Keep

It wrote a load of files and then errored:

kept.exe: C:\Users\cja\Downloads\takeout-20230305T104856Z-001\Takeout\Keep\16870f5d424.b8e0ea45ca8777dd.png: copyFileWithMetadata:CopyFile "\\\\?\\C:\\Users\\cja\\Downloads\\takeout-20230305T104856Z-001\\Takeout\\Keep\\16870f5d424.b8e0ea45ca8777dd.png" "\\\\?\\C:\\Users\\cja\\Downloads\\kept-0.3.0-win64\\kept-0.3.0\\kept-output\\media\\16870f5d424.b8e0ea45ca8777dd.png": does not exist (The system cannot find the file specified.)

Happy to send you details if you say what you need. Don't want to paste full program output here cos it contains names of my files.

[keithfancher]

Thank you for reporting this!

One quick thing to check: does the 16870f5d424.b8e0ea45ca8777dd.png file exist in your Keep export? (In C:\Users\cja\Downloads\takeout-20230305T104856Z-001\Takeout\Keep, that is.)

The error message looks like perhaps that file is referenced in a Keep export JSON, but the referenced file is not actually present? In either case, I should certainly handle those errors more gracefully.

One other question: were any of your other notes with media attachments successfully exported? Just wondering if this is an issue with a particular file, or some broader issue.

If it is an issue with a single note, by the way, a temporary workaround could be to move the offending JSON file out of your Keep export and run kept again. Then later, after finding the issue, you can migrate any leftovers piecemeal. (To find which note the image belongs to, you can just do a text search for that file name in your export directory. I should also include the note name in the error message!)

Sorry for the hiccup, and thanks again for taking the time to report!

[keithfancher]

Oh, one other thing I just noticed: that \\\\?\\ bit in the path is sure funky. One quick thing to try might be to run kept using a relative path. For example, stick kept.exe somewhere in your PATH, or just stick it in C:\Users\cja\Downloads. Then try running it like ./kept -t takeout-20230305T104856Z-001\Takeout\Keep.

Obviously still something funky going on, but curious whether it could be a path issue...

[rahji]

Same problem for me. Yes the file exists in the same folder as the json files.

...
Writing file to kept-output/pinned/2023-2024.md
Writing file to kept-output/untagged/grant spending!.md
Writing file to kept-output/archive/Modela set screw replacements.md
kept: Keep/152cc157b7e.8f48f05fbe7f47c8.png: copyFileWithMetadata:getFileStatus: does not exist (No such file or directory)
> ls -l Keep/152cc157b7e.8f48f05fbe7f47c8.jpg
-rw-r--r-- 1 robduarte robduarte 895443 May 14  2018 Keep/152cc157b7e.8f48f05fbe7f47c8.jpg

I see the problem - the file is actually a jpg and kept is looking for a png. I have verified that the .md file that is referencing the image says PNG and not JPG as it should.

[rahji]

More trouble - I can find that Kept has used .png instead of .jpg in the markdown but when I search the before-suffix part of the filename in all of the files that Kept has created, I find that some of the images are not referenced at all in the output files. (They are referenced in the original Keep dump though) This is true for both jpg and png files. It seems like keep notes that only contain an image are not being converted by Kept?

Here is an example of a json file that is an image-only Keep note (and seems to be ignored by Kept):

{"attachments":[{"filePath":"185bfca183e.bb816c85cd3b0634.png","mimetype":"image/png"}],"color":"DEFAULT","isTrashed":false,"isPinned":false,"isArchived":false,"textContent":"","title":"","userEditedTimestampUsec":1673960026505000,"createdTimestampUsec":1673960024034000,"labels":[{"name":"modular"}]}

[rahji]

Sorry, the plot thickens: Upon further examination, the Keep export from Google is what's wrong. There are json files that reference PNG files (even showing their mime type as image/png) when the file that is part of the export is a JPG instead (in both name and contents). I guess Kept is off the hook and Google as at fault! Still might be good for you to address the problem on the Kept end.