### repeats x times ### ...What?

Solar2D Daily Builds and Public Releases
#1

I just jumped from v2850 to v2873 to check what is ‘safe’ to build with before a major release of our software.

Apart from various other problems I’m having with Corona suddenly implementing app breaking changes in the name of ‘good practice’, I’m getting a new message in my console that says:

repeats 2 times

or whatever.

Except the only thing it seems to care about is that the previous line printed to the console was the same result.

The trouble is, that it appears to be suppressing things it deems to be repeated.

e.g., I am printing a ‘map’ of the binary values of a table representing a grid. Now it doesn’t bother to show me lines in that grid where the result is the same as the previous line. Really useful… now I can’t debug my grid.

Also, if two entirely seperate functions output the same line, it deems that a repeat, too. Really useful… now I can’t debug my program flow.

I can’t find any documentation anywhere on what this is or why its happening, but I’m imagining it’s supposed to be a ‘helpful’ message pre-warning you of stuff that could lead to stack overflows or something. As it is, it’s just plain wrong and it’s breaking my console output, which also happens to be my in-app debugging.

For example, the output of the following ‘app’:

for i = 1, 10 do print ("THIS SUCKS") end

is:

May 03 03:20:54.285 THIS SUCKS May 03 03:20:54.285 ### repeats 5 times ### May 03 03:20:54.294 THIS SUCKS May 03 03:20:54.294 ### repeats 3 times ###

Which is absolutely no use whatsoever. Nor does it even make any sense.

So… what is this, and how do I turn it off???

#2

I believe that’s an OS feature of how console logging works. Let me ask Engineering about it.

Rob

#3

I don’t think so. The current public release doesn’t do it. The latest daily build does it.

Actually, I might not even be on the current public release. But the point is, I’m running two Coronas on the very same machine at the very same time running the very same code and getting very different results. One, what I asked it to do, and the other, some weird summarised version of what it interpreted that I wanted it to do.

I mean seriously, in a for loop where you’re asking it to print 10 times, have a guess what I’d like it to do?!?! :stuck_out_tongue:

#4

It is intended to be a feature :slight_smile:  For some reason it doesn’t trigger for me nearly as much as it does for you (i.e. I rarely see it even when printing the same message many times per second).  I find it particularly useful when something goes haywire and you get “### repeats 3421 times ###”.

I’ll look at adding an option to suppress the behavior.

In the meantime, you can always go back to Corona Terminal which doesn’t have the “feature” (it’s in the CoronaSDK folder next to Corona Simulator ).

#5

If it was implemented in a useful way, then it probably would be a useful feature.

Useful would be that it’s not just blindly looking at the console output and comparing like for like and making a huge assumption.

You cannot imagine how jarring it is to go from a simple binary map where you can see at a two second glance where your data is and if it’s correct to a bunch of lines punctuated by ### repeats 5 times ###

It really, really needs a toggle to turn it off.

As does your new implementation that breaks all my overridden system globals. You simply can’t go round breaking mature apps if you expect us to take Corona seriously. Fine, your intentions are good for new coders, but the way you are going about it is making us question using Corona at all going forward.

Honestly, the main reason I’m testing the latest daily builds and finding all these game breaking issues is because every time we have to build our app it’s a case of “right, done! now what version of Corona is safe to use this time? what have they broken now?”

#6

I believe that’s an OS feature of how console logging works. Let me ask Engineering about it.

Rob

#7

I don’t think so. The current public release doesn’t do it. The latest daily build does it.

Actually, I might not even be on the current public release. But the point is, I’m running two Coronas on the very same machine at the very same time running the very same code and getting very different results. One, what I asked it to do, and the other, some weird summarised version of what it interpreted that I wanted it to do.

I mean seriously, in a for loop where you’re asking it to print 10 times, have a guess what I’d like it to do?!?! :stuck_out_tongue:

#8

It is intended to be a feature :slight_smile:  For some reason it doesn’t trigger for me nearly as much as it does for you (i.e. I rarely see it even when printing the same message many times per second).  I find it particularly useful when something goes haywire and you get “### repeats 3421 times ###”.

I’ll look at adding an option to suppress the behavior.

In the meantime, you can always go back to Corona Terminal which doesn’t have the “feature” (it’s in the CoronaSDK folder next to Corona Simulator ).

#9

If it was implemented in a useful way, then it probably would be a useful feature.

Useful would be that it’s not just blindly looking at the console output and comparing like for like and making a huge assumption.

You cannot imagine how jarring it is to go from a simple binary map where you can see at a two second glance where your data is and if it’s correct to a bunch of lines punctuated by ### repeats 5 times ###

It really, really needs a toggle to turn it off.

As does your new implementation that breaks all my overridden system globals. You simply can’t go round breaking mature apps if you expect us to take Corona seriously. Fine, your intentions are good for new coders, but the way you are going about it is making us question using Corona at all going forward.

Honestly, the main reason I’m testing the latest daily builds and finding all these game breaking issues is because every time we have to build our app it’s a case of “right, done! now what version of Corona is safe to use this time? what have they broken now?”