Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

CLI leaves a mess behind from time to time

See original GitHub issue

Untracked files:
  (use "git add <file>..." to include in what will be committed)

        bg.zip
        de.zip
        el.zip

I have no clue under what conditions those files are popping up, but it seems that even after successful CLI run, one can find temporary zip files with updated translation lying around not being deleted.

This is not easily reproducable bug, I couldn’t reproduce it with already pre-built translations. CLI version 2.0.14, I’ve just updated to latest 2.0.15, but I didn’t see any commit mentioning this problem.

Thank you in advance.

Issue Analytics

State:
Created 6 years ago
Comments:10 (4 by maintainers)

Top GitHub Comments

1reaction

ihor-popykcommented, Jun 7, 2017

Hey @JustArchi , Did some manipulation with CLI. Can you try to test this CLI version, please? https://drive.google.com/file/d/0B9m3jUOiOAGLaE5NZzUyNXJHMkE/view?usp=sharing

1reaction

JustArchicommented, May 31, 2017

I can but I don’t think that’s the case, I have around ~40 target languages and only 3 zips out of at least 20 that are being compiled and deployed are left, while all other ones are being removed successfully.

Maybe you can add small debug of catching I/O exceptions around deleting the file, and add some basic info about them to stdout/stderr (maybe even with stacktrace), so when issue happens I can simply copy/paste what CLI writes. Personally I believe it has something to do with Windows Defender scanning the file and making it impossible to remove right away (file in use), but that’s only my theory.

Thanks for looking into this issue!