Error on different workspace: TypeError: Converting circular structure to JSON
up vote
0
down vote
favorite
/code/server/Chat.js:34
let stringToWrite = JSON.stringify(game, null, 2);
^
TypeError: Converting circular structure to JSON
at JSON.stringify (<anonymous>)
at /code/server/Chat.js:34:46
at FSReqWrap.oncomplete (fs.js:135:15)
[nodemon] app crashed - waiting for file changes before starting...
This functionality works fine in workspace A and production server. But I'm getting this error in workspace B. Both workspaces are macbooks and server is linux. I don't know how this could be circular structure in one computer while not on the other one, any ideas?
The functionality of this method is to turn Game State into a log that can be saved as a 2000 line .log file. Purpose is for production future debugging.
Here is how the log looks like. I removed all elements related to the game, because I'm pretty sure there is no circular structure there.
https://pastebin.com/dF8PsZKS
Tested:
- I researched what circular structure is, I haven't done anything like this
- I looked inside GameController, couldn't find a circular structure
- I looked at subclasses inside GameController, couldn't find a circular structure
- This works in the server & my machine
- Tried console.log(util.inspect(myObject))
javascript node.js typescript circular-dependency stringify
add a comment |
up vote
0
down vote
favorite
/code/server/Chat.js:34
let stringToWrite = JSON.stringify(game, null, 2);
^
TypeError: Converting circular structure to JSON
at JSON.stringify (<anonymous>)
at /code/server/Chat.js:34:46
at FSReqWrap.oncomplete (fs.js:135:15)
[nodemon] app crashed - waiting for file changes before starting...
This functionality works fine in workspace A and production server. But I'm getting this error in workspace B. Both workspaces are macbooks and server is linux. I don't know how this could be circular structure in one computer while not on the other one, any ideas?
The functionality of this method is to turn Game State into a log that can be saved as a 2000 line .log file. Purpose is for production future debugging.
Here is how the log looks like. I removed all elements related to the game, because I'm pretty sure there is no circular structure there.
https://pastebin.com/dF8PsZKS
Tested:
- I researched what circular structure is, I haven't done anything like this
- I looked inside GameController, couldn't find a circular structure
- I looked at subclasses inside GameController, couldn't find a circular structure
- This works in the server & my machine
- Tried console.log(util.inspect(myObject))
javascript node.js typescript circular-dependency stringify
5
It looks like you're storing a socket object, is that right? Pretty sure that's where the problem would be.
– Andy
Nov 11 at 13:09
Yes I am storing a socket object:socket: any
. What should I do about this? Wouldn't that object be helpful in debugging? Also how does this explain why sockets make the code crash in 1 workspace but not the other 2?
– Esqarrouth
Nov 14 at 2:30
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
/code/server/Chat.js:34
let stringToWrite = JSON.stringify(game, null, 2);
^
TypeError: Converting circular structure to JSON
at JSON.stringify (<anonymous>)
at /code/server/Chat.js:34:46
at FSReqWrap.oncomplete (fs.js:135:15)
[nodemon] app crashed - waiting for file changes before starting...
This functionality works fine in workspace A and production server. But I'm getting this error in workspace B. Both workspaces are macbooks and server is linux. I don't know how this could be circular structure in one computer while not on the other one, any ideas?
The functionality of this method is to turn Game State into a log that can be saved as a 2000 line .log file. Purpose is for production future debugging.
Here is how the log looks like. I removed all elements related to the game, because I'm pretty sure there is no circular structure there.
https://pastebin.com/dF8PsZKS
Tested:
- I researched what circular structure is, I haven't done anything like this
- I looked inside GameController, couldn't find a circular structure
- I looked at subclasses inside GameController, couldn't find a circular structure
- This works in the server & my machine
- Tried console.log(util.inspect(myObject))
javascript node.js typescript circular-dependency stringify
/code/server/Chat.js:34
let stringToWrite = JSON.stringify(game, null, 2);
^
TypeError: Converting circular structure to JSON
at JSON.stringify (<anonymous>)
at /code/server/Chat.js:34:46
at FSReqWrap.oncomplete (fs.js:135:15)
[nodemon] app crashed - waiting for file changes before starting...
This functionality works fine in workspace A and production server. But I'm getting this error in workspace B. Both workspaces are macbooks and server is linux. I don't know how this could be circular structure in one computer while not on the other one, any ideas?
The functionality of this method is to turn Game State into a log that can be saved as a 2000 line .log file. Purpose is for production future debugging.
Here is how the log looks like. I removed all elements related to the game, because I'm pretty sure there is no circular structure there.
https://pastebin.com/dF8PsZKS
Tested:
- I researched what circular structure is, I haven't done anything like this
- I looked inside GameController, couldn't find a circular structure
- I looked at subclasses inside GameController, couldn't find a circular structure
- This works in the server & my machine
- Tried console.log(util.inspect(myObject))
javascript node.js typescript circular-dependency stringify
javascript node.js typescript circular-dependency stringify
asked Nov 11 at 13:04
Esqarrouth
24k11117129
24k11117129
5
It looks like you're storing a socket object, is that right? Pretty sure that's where the problem would be.
– Andy
Nov 11 at 13:09
Yes I am storing a socket object:socket: any
. What should I do about this? Wouldn't that object be helpful in debugging? Also how does this explain why sockets make the code crash in 1 workspace but not the other 2?
– Esqarrouth
Nov 14 at 2:30
add a comment |
5
It looks like you're storing a socket object, is that right? Pretty sure that's where the problem would be.
– Andy
Nov 11 at 13:09
Yes I am storing a socket object:socket: any
. What should I do about this? Wouldn't that object be helpful in debugging? Also how does this explain why sockets make the code crash in 1 workspace but not the other 2?
– Esqarrouth
Nov 14 at 2:30
5
5
It looks like you're storing a socket object, is that right? Pretty sure that's where the problem would be.
– Andy
Nov 11 at 13:09
It looks like you're storing a socket object, is that right? Pretty sure that's where the problem would be.
– Andy
Nov 11 at 13:09
Yes I am storing a socket object:
socket: any
. What should I do about this? Wouldn't that object be helpful in debugging? Also how does this explain why sockets make the code crash in 1 workspace but not the other 2?– Esqarrouth
Nov 14 at 2:30
Yes I am storing a socket object:
socket: any
. What should I do about this? Wouldn't that object be helpful in debugging? Also how does this explain why sockets make the code crash in 1 workspace but not the other 2?– Esqarrouth
Nov 14 at 2:30
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53249014%2ferror-on-different-workspace-typeerror-converting-circular-structure-to-json%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
5
It looks like you're storing a socket object, is that right? Pretty sure that's where the problem would be.
– Andy
Nov 11 at 13:09
Yes I am storing a socket object:
socket: any
. What should I do about this? Wouldn't that object be helpful in debugging? Also how does this explain why sockets make the code crash in 1 workspace but not the other 2?– Esqarrouth
Nov 14 at 2:30