Unable to see full log of long data

🐛 Bug Report

Flipper only logs limited number of lines even after > and n more is pressed. I tried logging array with length of 200, but it only shows maximum of 161. (also have no idea why it’s saying 618 more) I’m expecting to see another > and n more button if there’re more lines to show.

To Reproduce

Run:

const testArray: number[] = [...Array(200)].map((_, index: number) => index);
console.log(testArray);

Environment

Flipper: 0.137.0 iOS: 15.2 Android: haven’t tested

[mweststrate]

The logs plugin is basically the stdout/stderr or your application, a single direction stream that shows everything you dump into it, nothing more, nothing less, just a bunch of characters. It doesn’t know about objects, arrays, or JavaScript at all for that matter.

The hermes debugger is a tool that connects to the JavaScript engine itself, and is hence not technology agnostic. So it won’t capture any info coming from the native world for example. But since it is a specialised bidirectional protocol, it can do things as expanding objects as long as they are kept in the JS memory of the client. Note that this is just a boxed chrome developers tool, so we don’t really influence its behavior. That your object doesn’t further expand might mean that is already garbage collected for example, by the time you expand it. Or it has been shortened in the mean time. Etc.

[thisisgit]

After posting above comment, I noticed and 618 more button doesn’t do anything unlike the first post, where it should show “little more” lines.

So I created fresh RN project, tested there, and was able to reproduce the first issue:

https://user-images.githubusercontent.com/13231564/157032212-8a0ba0f1-3f88-424c-b847-861ebe4ec62b.mp4

The only difference between this and above record is the version of RN, above is 0.66.4 and this one is 0.67.3.