Experiment with Console Finds Red Text

[AlanAgnew]

@MikePreston17

Okay, so the results of the console are long. Since you preferred the red text, this is all I obtained the below red text when I uploaded the document that you can download here: https://s.nimbusweb.me/attachment/3235268/rre5hlhci1clss6o0zu5/R77JLk8oWUGjq8Se/Work%20Genna%2C%20Jon%2C%20Three%20Questions%20docx.docx?dw

Bigger issue: There is an extensive amount of drop down menus all nested within each other in the console. Whoa. What do I do?

[mobx] Encountered an uncaught exception that was thrown by a reaction or observer component, in: 'Reaction[Reaction@19]' 
Error
​
columnNumber: 404518
​
fileName: "https://tpot.netlify.com/static/js/2.0e48509f.chunk.js"
​
lineNumber: 1
​
message: "[serializr] this value is not primitive: [object Object]"
​
stack: "o@https://tpot.netlify.com/static/js/2.0e48509f.chunk.js:1:404518\nserializer@https://tpot.netlify.com/static/js/2.0e48509f.chunk.js:1:405990\nR/<@https://tpot.netlify.com/static/js/2.0e48509f.chunk.js:1:408215\nR@https://tpot.netlify.com/static/js/2.0e48509f.chunk.js:1:407939\nx@https://tpot.netlify.com/static/js/2.0e48509f.chunk.js:1:407785\nt.create/</<@https://tpot.netlify.com/static/js/2.0e48509f.chunk.js:1:156527\ng/<@https://tpot.netlify.com/static/js/2.0e48509f.chunk.js:1:24633\nge@https://tpot.netlify.com/static/js/2.0e48509f.chunk.js:1:15883\nPe</e.prototype.track@https://tpot.netlify.com/static/js/2.0e48509f.chunk.js:1:20838\ng@https://tpot.netlify.com/static/js/2.0e48509f.chunk.js:1:24608\ntt/m<@https://tpot.netlify.com/static/js/2.0e48509f.chunk.js:1:24532\nPe</e.prototype.runReaction@https://tpot.netlify.com/static/js/2.0e48509f.chunk.js:1:20636\nje@https://tpot.netlify.com/static/js/2.0e48509f.chunk.js:1:22357\nUe@https://tpot.netlify.com/static/js/2.0e48509f.chunk.js:1:21995\nUe/<@https://tpot.netlify.com/static/js/2.0e48509f.chunk.js:1:22491\nks@https://tpot.netlify.com/static/js/2.0e48509f.chunk.js:1:867638\nUe@https://tpot.netlify.com/static/js/2.0e48509f.chunk.js:1:22471\nXe@https://tpot.netlify.com/static/js/2.0e48509f.chunk.js:1:22051\nMe@https://tpot.netlify.com/static/js/2.0e48509f.chunk.js:1:18514\n$@https://tpot.netlify.com/static/js/2.0e48509f.chunk.js:1:9503\nJ@https://tpot.netlify.com/static/js/2.0e48509f.chunk.js:1:9455\nQe@https://tpot.netlify.com/static/js/2.0e48509f.chunk.js:1:23370\ne/<@https://tpot.netlify.com/static/js/main.0b82f7c9.chunk.js:1:77552\nE@https://tpot.netlify.com/static/js/2.0e48509f.chunk.js:1:1414695\nb/o._invoke</<@https://tpot.netlify.com/static/js/2.0e48509f.chunk.js:1:1414485\nT/</e[t]@https://tpot.netlify.com/static/js/2.0e48509f.chunk.js:1:1414871\nr@https://tpot.netlify.com/static/js/2.0e48509f.chunk.js:1:146438\ns@https://tpot.netlify.com/static/js/2.0e48509f.chunk.js:1:146644\n"
​
__proto__: Object { … }
mobx.module.js:1939
Pe</e.prototype.reportExceptionInDerivation
mobx.module.js:1939
Pe</e.prototype.track
mobx.module.js:1914
g
mobx.module.js:2323
tt/m<
mobx.module.js:2311
Pe</e.prototype.runReaction
mobx.module.js:1869
je
mobx.module.js:2033
Ue
mobx.module.js:2008
Ue/<
mobx.module.js:2047
ks
react-dom.production.min.js:5990
Ue
mobx.module.js:2046
Xe
mobx.module.js:2014
Me
mobx.module.js:1666
$
mobx.module.js:726
J
mobx.module.js:689
Qe
mobx.module.js:2221
e/<
session.js:63:12
E
runtime.js:63
b/o._invoke</<
runtime.js:282
T/</e[t]
runtime.js:116
r
asyncToGenerator.js:3
s
asyncToGenerator.js:25

Image of it:

Therefore, I am thinking of finding a way to just export the entire console so that things can be figured out.

[Braden-Preston]

Hey Alan, a lot of this is normal stuff.

We are currently printing out a bunch of info and warnings so that we can see specific sets of data from MobX, Firebase, Draft, etc. There are all microservices that are part of Toolbox. You don't have to worry yourself with what they are, but you can always Google them if you are curious. So if you see these things, even if they show up as red text warnings in the console, it's all expected.

A critical issue can occur, but it may not affect the front-facing user experience. That is perfectly fine for us right now. An example of this is MobX will complain that it is "unable to serialize data". This occurs because it is trying to store user preferences between browser sessions. But one of the things I have it attempting to store right now is a function for editing user color themes. But functions aren't easily serialized (that is, making them a string that can be saved to disk). Which is why MobX thinks there is an error. This is just a small example of why you may get a message like that in the console.

What we do want to hear about are issues that cause an unexpected problems for the user when they are completing a task and something goes unexpectedly. Report those as you have been and if something you think is related to it happens to up in the console, you can send us the first line of that error as well. You don't have to send us the full stack trace. We will take the first message you give us and replicate the problem on our end. We will be able to dig further into the console logs if needed at that point.

We did have two issues Saturday that affected user experience and they also showed up in the console. We fixed those straight away.

On a side note, we have the development URL up and in testing. We will share it with you when we are ready. You can see the fruits of your labor and the progress of the issues you have mentioned in the latest version of Toolbox (and other cool stuff as well). ;)

[AlanAgnew]

Okay, so if I can do an action and find the issue in the console, then I should post that!

[nickpreston24]

B:

What we do want to hear about are issues that cause an unexpected problems... You don't have to send us the full stack trace.

A:

Okay, so if I can do an action and find the issue in the console, then I should post that!

Only the stack trace under the conditions outlined. A good example is the save button not doing anything. That should arouse suspicion, in which case you would look to the console.

You can also change the details the console gives, here (firefox and chrome juxtaposed):

[AlanAgnew]

Thanks, Michael, let's see what comes up now in other issues.

[AlanAgnew]

As for this issue, this is all that is left after removing "logs"