Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

restore-file: GraphQL:A path was requested for deletion which does not exist as of commit oid 4ec33cf263e0a086bffb40f15b39a7de3c5044b8 #7312

Open
govindrai opened this issue Mar 21, 2024 · 3 comments

Comments

@govindrai
Copy link

govindrai commented Mar 21, 2024

Description

Error: GraphQL:
A path was requested for deletion which does not exist as of commit oid `4ec33cf263e0a086bffb40f15b39a7de3c5044b8`
    at v4uncached (chrome-extension://hlepfoohegkhhmjieoechaddaejaokhf/assets/refined-github.js:4392:60)
    at async chrome-extension://hlepfoohegkhhmjieoechaddaejaokhf/assets/refined-github.js:8471:11
    at async showToast (chrome-extension://hlepfoohegkhhmjieoechaddaejaokhf/assets/refined-github.js:5378:40)
    at async HTMLHtmlElement.handleClick (chrome-extension://hlepfoohegkhhmjieoechaddaejaokhf/assets/refined-github.js:8454:9)

How to replicate the issue + URL

I had a large PR (270 files). I discarded changes on two files. It worked beautifully. Upon restoring my third file, I started getting this error. A this point I had to do the discards manually via git. This is a private repo, so I will try to create a public scenario for this.

Extension version

24.3.20

Browser(s) used

Chrome Version 123.0.6312.59 (Official Build) (arm64)

@govindrai govindrai added the bug label Mar 21, 2024
@fregante
Copy link
Member

I think this happens when you delete multiple files in a row. Refreshing the page should work

@govindrai
Copy link
Author

I tried that multiple times, Even tried to clear cache/exit browser. It would always give the same error.

@fregante
Copy link
Member

fregante commented Jun 3, 2024

This is likely a caching issue, all of our API calls are cached until the next page refresh. If that doesn't do it, it's likely that GitHub is also caching the request.

const response = await api.v3(`compare/${base.relative}...${head.relative}`);

We should either:

I think the latter is easier and safer, if the caching issue is actually on GitHub's side

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants