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

list of errorss reported by yarn dev server #509

Open
duncdrum opened this issue Sep 10, 2021 · 2 comments
Open

list of errorss reported by yarn dev server #509

duncdrum opened this issue Sep 10, 2021 · 2 comments

Comments

@duncdrum
Copy link
Contributor

duncdrum commented Sep 10, 2021

node 14, api 1.2,

I repeatedly see both errors, haven't been able to tie them to a specific operation, but they seem to occur anytime i bring up the dev server

root ERROR Child node 'open-editors:root' does not belong to this 'open-editors:root' tree.

this might explain our troubles with tree updating when an editor window is open.

root ERROR not caught: SyntaxError: JSON.parse: unexpected end of data at line 1 column 1 of the JSON data

this is an upstream bug related to how node writes to the filesystem, see eclipse-theia/theia#8384 .

duncdrum added a commit that referenced this issue Sep 14, 2021
@duncdrum
Copy link
Contributor Author

duncdrum commented Sep 14, 2021

part 2:

root ERROR Error during serialization of layout data TypeError: Converting circular structure to JSON
    --> starting at object with constructor 'Object'
    |     property 'children' -> object with constructor 'Array'
    |     index 0 -> object with constructor 'Object'
    --- property 'connectionNode' closes the circle
    at JSON.stringify (<anonymous>)
    at ShellLayoutRestorer.__webpack_modules__.../node_modules/@theia/core/lib/browser/shell/shell-layout-restorer.js.ShellLayoutRestorer.deflate (http://localhost:3000/bundle.js:52836:21)
    at ShellLayoutRestorer.__webpack_modules__.../node_modules/@theia/core/lib/browser/shell/shell-layout-restorer.js.ShellLayoutRestorer.convertToDescription (http://localhost:3000/bundle.js:52872:44)
    at Object.<anonymous> (http://localhost:3000/bundle.js:52839:41)
    at JSON.stringify (<anonymous>)
    at ShellLayoutRestorer.__webpack_modules__.../node_modules/@theia/core/lib/browser/shell/shell-layout-restorer.js.ShellLayoutRestorer.deflate (http://localhost:3000/bundle.js:52836:21)
    at ShellLayoutRestorer.__webpack_modules__.../node_modules/@theia/core/lib/browser/shell/shell-layout-restorer.js.ShellLayoutRestorer.storeLayout (http://localhost:3000/bundle.js:52789:49)
    at http://localhost:3000/bundle.js:40891:34
    at http://localhost:3000/bundle.js:67649:33
    at CallbackList.__webpack_modules__.../node_modules/@theia/core/lib/common/event.js.CallbackList.invoke (http://localhost:3000/bundle.js:67664:39)
root ERROR not caught: TypeError: Failed to fetch

see #508 this sounds about fitting to the non-happening fetch for restxq endpoint

root ERROR Error: [UriError]: Scheme contains illegal characters.
    at _validateUri (http://localhost:3000/bundle.js:148357:15)
    at _URI.URI (http://localhost:3000/bundle.js:148448:13)
    at new _URI (http://localhost:3000/bundle.js:148669:47)
    at Function.URI.parse (http://localhost:3000/bundle.js:148560:16)
    at ResourceContextKey.__webpack_modules__.../node_modules/@theia/core/lib/browser/resource-context-key.js.ResourceContextKey.set (http://localhost:3000/bundle.js:50037:66)
    at updateContextKeys (http://localhost:3000/bundle.js:36535:38)
    at http://localhost:3000/bundle.js:67649:33
    at CallbackList.__webpack_modules__.../node_modules/@theia/core/lib/common/event.js.CallbackList.invoke (http://localhost:3000/bundle.js:67664:39)
    at Emitter.__webpack_modules__.../node_modules/@theia/core/lib/common/event.js.Emitter.fire (http://localhost:3000/bundle.js:67791:29)
    at SelectionService.set (http://localhost:3000/bundle.js:72004:44)

huh?

root ERROR caught: { code: 0, data: [ {} ] }

see #508 this about fits the restxq issue

@duncdrum
Copy link
Contributor Author

Wrong commit message. My mistake. these errors still need investigating.

@duncdrum duncdrum reopened this Sep 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant