Bug: `"The requested file is not found."` Message

[MattePalte]

Hi,

Summary

One of my anonymized repo is experiencing a problem, multipel files (at random) consistently says: "The requested file is not found." however even forcing update it remains.

Background on the repository:

Last time I checked (a week ago), right after generation the problem seemed to be not there.

• I generate the repo under my user username/repoA
• I anonymized it with a link name https://anonymous.4open.science/r/repoA
• I shared that link for a conference submission
• I renamed username/repoA to username/beautifulRepoA
• I transferred the ownership of the same repo to an organization myLab/beautifulRepoA

I noticed the problem of seeing "The requested file is not found." message for some file (apparently at random). Then I tried to restore my repo in username/repoA so I recreated it in my username and used the same original name (because I cannot change the link I shared with the conference), and pushed the exact same files it had before. Then forced update on the anonymized repo platform. It still behaved similarly.

Observed Issues:

I experiences the message "The requested file is not found." in these scenarios:

• (a) a folder with multiple .txt files (all generated in the same commit), has some that are visible and some that are not. (My guess is that some are in cache and some aren't)
• (b) a folder with a ipynb file, says "The requested file is not found." however I can download it and see it. If I click view raw button I get {"error":"file_not_found"} but if I download it I can see it, same for the download repository button.

Suggested Workaround:

Since this could give the impression that the artifact is unavailable to conference organizers, would it be possible to add a red banner on the repository page instructing users to download the repository if they encounter the "The requested file is not found." message?

Thanks in advance I wish you a happy and productive day Matteo

[Kanat7]

I am facing the same problem with the same situation and would appreciate if the suggested workaround would be implemented, too.

Sincerely, the developer

[MattePalte]

@Kanat7 I have an update. Sharing with a colleague it turned out being a cache problem (probably). Since navigating in incognito mode did not show any problem. However this should be probably fixed in some way on the platform side, to avoid giving the false impression of a defective artifact to an unlucky user with a compromised cache. The message is consistent across refreshes, that is why I believe it is a cache problem.

[Kanat7]

I appreciate your helpful report and wish you success with your submission.

[Soumitra816]

Most unintelligent and effortless go around is:

Create a blank file with any name in your associated GitHub repo. Force update the anonymize repo to get the new file reflected in the anonymized repo. (: Voila. Worked for me!! :)