Timber.debugTree splite lose word

[imcloud]

// Split by line, then ensure each line can fit into Log's maximum length.
      for (int i = 0, length = message.length(); i < length; i++) {
        int newline = message.indexOf('\n', i);
        newline = newline != -1 ? newline : length;
        do {
          int end = Math.min(newline, i + MAX_LOG_LENGTH);
          String part = message.substring(i, end);
          if (priority == Log.ASSERT) {
            Log.wtf(tag, part);
          } else {
            Log.println(priority, tag, part);
          }
          i = end;
        } while (i < newline);
      }

// the beginning index, inclusive.
// the ending index, exclusive
// while i == 0
message.substring(0, 4000);
// while i == 1
message.substring(4001, 8001);

// lost 4000

[imcloud]

and, android studio 3.2 default line size less then 4000
MAX_LOG_LENGTH should be set 3000 or other

[JakeWharton]

4023 is the max (prior to 24 or whatever) which is why it's set at 4000. You can file an Android Studio bug if it cannot properly display more than 3000.

…

On Mon, Oct 22, 2018 at 10:19 PM Victor ***@***.***> wrote: and, android studio 3.2 default line size less then 4000 MAX_LOG_LENGTH should be set 3000 or other — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#339 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAEEEVmF3pq-otHQalpeon57tp0I5Bspks5unnzFgaJpZM4Xy4ki> .

[taichushouwang]

Now the latest version of Android Studio is 4.1.1。It still can't properly display more than 3000. I hope the MAX_LOG_LENGTH should change to 3000 or make it can change.

Now in my project, I extend the DebugTree, only change the MAX_LOG_LENGTH, and copy and paste the fun of log

[JakeWharton]

Sounds like a Studio bug then. File it on their project?

[imcloud]

Now the latest version of Android Studio is 4.1.1。It still can't properly display more than 3000. I hope the MAX_LOG_LENGTH should change to 3000 or make it can change.

Now in my project, I extend the DebugTree, only change the MAX_LOG_LENGTH, and copy and paste the fun of log

class MyDebugTree : Timber.DebugTree() {

    private val MAX_LOG_LENGTH = 2048

    override fun log(priority: Int, tag: String?, message: String, t: Throwable?) {
        if (message.length < MAX_LOG_LENGTH) {
            if (priority == Log.ASSERT) {
                Log.wtf(tag, message)
            } else {
                Log.println(priority, tag, message)
            }
            return
        }

        // Split by line, then ensure each line can fit into Log's maximum length.
        var i = 0
        val length = message.length
        while (i < length) {
            var newline = message.indexOf('\n', i)
            newline = if (newline != -1) newline else length
            do {
                val end = Math.min(newline, i + MAX_LOG_LENGTH)
                val part = message.substring(i, end)
                if (priority == Log.ASSERT) {
                    Log.wtf(tag, part)
                } else {
                    Log.println(priority, tag, part)
                }
                i = end
            } while (i < newline)
            i = if (i == newline) i + 1 else i
        }
    }
}

我做了一些改动，这样就没问题了

[imcloud]

I think I know the reason. It should be the Chinese character problem. The three byte Chinese makes the calculation error

[JakeWharton]

You're saying the kernel header is in utf-8(?) bytes but Timber is erroneously counting chars? That sounds like a plausible explanation!

[gmk57]

The same happens for Cyrillic text, approximately half of it is lost. :(