Kaasuko
commented
4 years ago Your "Problem" is that the string of the debug-node's output is cut short. It's too long to be displayed, you can see this at the end of the string as it ends with "zQy..."
Closed ozett closed 4 years ago
Kaasuko
commented
4 years ago Your "Problem" is that the string of the debug-node's output is cut short. It's too long to be displayed, you can see this at the end of the string as it ends with "zQy..."
ozett
commented
4 years ago i thought it a good idea to view elementary videos from node-red and used this handling information to use this "copy from debug-node". from min 01:45 onward..
https://youtu.be/TDxL02SInps?t=109
as i now searched this video again, i heard it now! more understandably saying about the second-debug.button:
"..truncated value - if its over a certain (??) size"
this is a very "sublime" information of less value, if i cannot copy it from there an dont know beforehand what a "certain" value it might be to be truncated...
seems a design bug. i think there should be an button to copy the whole value or to get a significant symbol that the value is truncated or changed...
or not?
dceejay
commented
4 years ago three dots - or ellipsis - is the standard to indicate missing or superfluous text.
It is a deliberate choice - sending data to debug uses bandwidth - and if you send a lot of fast moving data - it all has to be sent even if the tree is not expanded (in the case of a complex object) - and on small devices it can consume significant cpu just to shift that data. The size of truncation can be set in your settings.js file - debugMaxLength: 1000, so you can alter it if you wish.
If you set the debug to send to the console (server side) as well (or instead) then you can see the full content.
ozett
commented
4 years ago thx for the longer explanation. it helps much to deal with my example flows. 👍 👌
as i am testing some things i observed the following: using the base64 example produces output in debug node as a base64 string. (image node works fine).
if i use this string on the inject-node it fails. if i use another base64-image-string it works.
i cannot figure out whats wrong with the base64 output on debug from your example. a base64 online-checker says its "malformatted".
a bug?
my test flow: