Open enn-nafnlaus opened 1 year ago
The 3d inpainting code has a lot of pdb.set_trace() commands, which breaks into the debugger, often in places where it checks for a specific condition and tries to recover, sometimes probably left from debugging some interesting situation it got into ..
I've removed this line where it breaks for you above in the latest version. You can also type 'continue' to exit pdb and continue..
I had not encountered the specific conditions for it to run that code, and want to be cautious in just removing all of those commands, as some of them will lead to plain crashes or garbage output.
Great - let me know when I can pull the commit :) (I just checked, nothing to pull). For now, I'll type "continue" the next time it happens.
I made the commit around the same time as that post ..
This is a weird one. Just started this evening, but it's happened repeatedly (requires a restart each time):
_Running 3D Photo Inpainting .. Loading edge model .. Loading depth model .. Loading rgb model .. 0%| | 0/16 [00:00<?, ?it/s] Generating inpainted mesh .. (go make some coffee) ..
(The "asdasdas" just just me typing, to see if I'm in a shell, which I clearly am)
In case it has to do with the first file in the directory, so here it is:
... but I've generated videos from that image before, so... ?