Ask coding questions

← Back to all posts
ZIP archive contains old (removed!) files
RafaSikora (1)

Hi, I found that after removing files from the repl through the console commands like "rm oldfile.xyz" they are still present in the ZIP archive downloaded from the repl through "Download as ZIP" button. These files are not visible in the console through "ls -la". Is there any way to completely remove the files in the console so that they would not appear in a ZIP archive? Thanks

Answered by RayhanADev (2514) [earned 5 cycles]
View Answer
Comments
hotnewtop
RayhanADev (2514)

I would believe that the files should be completely gone, but since you did it through the console there may or may not have been a server-side error in deleting your file and thus the file may appear to have been deleted by is actually still there. Have you tried refreshing the page and checking to see if the file still exists in the Repl?

RafaSikora (1)

@RayhanADev Refreshing does not help, nor deleting browser cache etc.

RayhanADev (2514)

@RafaSikora So the file is still visible in the Repl?

RafaSikora (1)

@RayhanADev Not in the repl, but in the ZIP archive downloaded through "Download as ZIP".

RayhanADev (2514)

@RafaSikora That is interesting. Ok I would like you to try something:

  • Fork your current Repl
  • Try downloading that ZIP file

Tell me how it goes...

RafaSikora (1)

@RayhanADev After forking and downloading a ZIP file from the forked repl, the files (which were removed in the original repl through 'rm') are still there (in the ZIP archive).

RayhanADev (2514)

@RafaSikora Is it possible for you to add me to this project. I would like to get a look at what’s going on.

awdimmick (5)

I have this same problem - has a solution been found?

RafaSikora (1)

@awdimmick No, unfortunately not. The repl team haven't implemented the correction, yet...

GoldenWither (0)

This has still not entirely been fixed, but I found a way that could fix the problem. If you create a new file and name it exactly what the old file was called then delete it again, it seemed to stop the bug from happening.