binaryage/dirac

Error: uiSourceCode expected to have scriptFile associated

binarykitchen opened this issue · 0 comments

Here too, a similar error always thrown when I want to debug CLJS code within an iFrame that appears only very briefly:

Dirac v1.2.34, Chrome/68.0.3429.0, Mac/10.13.4, Backend API/external/554, Backend CSS/external/442

DevTools code has thrown an unhandled exception:
Error: uiSourceCode expected to have scriptFile associated
uiSourceCode: name=XFrame.js url=https://swx.cdn.skype.com/jLync/XFrame/XFrame.js project=network

    at getScriptFromSourceCode (chrome-extension://kbkdngfljkchidcjpnfcgcokkbhlkogi/devtools/front_end/dirac_lazy/dirac_lazy_module.js:100:113)
    at getSourceCodeNamespaceDescriptorsAsync (chrome-extension://kbkdngfljkchidcjpnfcgcokkbhlkogi/devtools/front_end/dirac_lazy/dirac_lazy_module.js:71:14)
    at extractSourceCodeNamespacesAsync (chrome-extension://kbkdngfljkchidcjpnfcgcokkbhlkogi/devtools/front_end/dirac_lazy/dirac_lazy_module.js:87:8)
    at extractAndMergeSourceCodeNamespacesAsync (chrome-extension://kbkdngfljkchidcjpnfcgcokkbhlkogi/devtools/front_end/dirac_lazy/dirac_lazy_module.js:90:38)
    at Object.handleSourceCodeAdded (chrome-extension://kbkdngfljkchidcjpnfcgcokkbhlkogi/devtools/front_end/dirac_lazy/dirac_lazy_module.js:127:1)
    at Workspace.Workspace.dispatchEventToListeners (chrome-extension://kbkdngfljkchidcjpnfcgcokkbhlkogi/devtools/front_end/shell.js:490:23)
    at Bindings.ContentProviderBasedProject.addUISourceCode (chrome-extension://kbkdngfljkchidcjpnfcgcokkbhlkogi/devtools/front_end/shell.js:8624:170)
    at Bindings.ContentProviderBasedProject.addUISourceCodeWithProvider (chrome-extension://kbkdngfljkchidcjpnfcgcokkbhlkogi/devtools/front_end/shell.js:9127:281)
    at Bindings.ResourceScriptMapping._parsedScriptSource (chrome-extension://kbkdngfljkchidcjpnfcgcokkbhlkogi/devtools/front_end/shell.js:8774:389)
    at SDK.DebuggerModel.dispatchEventToListeners (chrome-extension://kbkdngfljkchidcjpnfcgcokkbhlkogi/devtools/front_end/shell.js:490:23)
---
To inspect the problem in internal DevTools => https://goo.gl/0FkZ1o
Consider reporting the issue here: https://github.com/binaryage/dirac/issues