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

Error: "Could not find commit data for root "957" and commit 2" #18804

Closed
rohanvachheta opened this issue May 2, 2020 · 2 comments
Closed

Error: "Could not find commit data for root "957" and commit 2" #18804

rohanvachheta opened this issue May 2, 2020 · 2 comments

Comments

@rohanvachheta
Copy link

Describe what you were doing when the bug occurred:
1.
2.
3.


Please do not remove the text below this line

DevTools version: 4.6.0-6cceaeb67

Call stack: at n.value (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:173658)
at p (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:359968)
at Zc (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:360183)
at ci (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:59620)
at nl (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:69923)
at Ll (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:110996)
at qc (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:102381)
at Hc (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:102306)
at Vc (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:102171)
at Tc (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:98781)

Component stack: in Zc
in div
in div
in So
in Unknown
in n
in Unknown
in div
in div
in rl
in Ze
in fn
in Ga
in _s

@49-22
Copy link

49-22 commented May 4, 2020

It would be better if you provide more details on the question.

@bvaughn
Copy link
Contributor

bvaughn commented May 7, 2020

Hi @rohanvachheta!

Sorry about the inconvenience!

This looks like a duplicate of #18010 so I'm going to close it.

It's possible that PR #18862 fixes this issue, but that remains to be seen. If you can reproduce this issue, we would greatly appreciate if you left a comment with repro instructions so we could test that PR and see!

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

No branches or pull requests

3 participants