[git export] Zombie Files about django-robo-cjk HOT 7 CLOSED

Running it once solves today's problem, but doesn't solve the issue for the future.

So: should this issue be re-opened or should there be a new one?

Perhaps "tombstoning" glyphs is a better approach than to truly delete them from the DB (ie. have a marker that says "this glyph has been deleted").

from django-robo-cjk.

I now realize that tombstoning is the only good approach for #14 to work correctly for deleted glyphs: without it, Fontra will have no way of knowing whether a glyph was deleted.

from django-robo-cjk.

I see you closed this, but was it really solved? I still observe it. In GS/hanzi, uni6233.xxxk.glif does not exist in the DB anymore, but it is still there in the git repo.

from django-robo-cjk.

Actually a full-cleanup is not run during the export, but when removing a .glif it will be removed also from the file-system.

The incremental export is very fast now, I don't know the impact of adding a full check/cleanup at the end of each export.

This problem was resolved by the full export, but we decided to remove it entirely (I agree with that decision).

Running a full export on all projects would remove zombie files, so we can think to run a full export manually just once to solve this.

from django-robo-cjk.

This needs to be reopened, but I can't...

from django-robo-cjk.

So the issue is currently: zombie files aren't deleted soon enough. They are deleted once a day, but should be deleted with an incremental update triggered by the deletion from the DB. Maybe this should be a new issue instead?

from django-robo-cjk.

I think continuing on this issue is ok.

from django-robo-cjk.