Fixed
Status Update
No update yet.
Comments
uc...@google.com
Reproduced in
Android Studio 3.1
Build #AI-173.4670197, built on March 21, 2018
JRE: 1.8.0_152-release-1024-b01 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Linux 4.9.0-6-amd64
Android Studio 3.1
Build #AI-173.4670197, built on March 21, 2018
JRE: 1.8.0_152-release-1024-b01 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Linux 4.9.0-6-amd64
ju...@braze.com
Just jumping on this thread, this de-duplication seems to happen when the logcat header (date & time, tag, pid, etc.) matches the previous logcat line. If they match, then the header gets trimmed.
Tested with Pixel 2 XL on API 27
Android Studio 3.1
Build #AI-173.4670197, built on March 21, 2018
JRE: 1.8.0_152-release-1024-b01 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Mac OS X 10.13.3
Tested with Pixel 2 XL on API 27
Android Studio 3.1
Build #AI-173.4670197, built on March 21, 2018
JRE: 1.8.0_152-release-1024-b01 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Mac OS X 10.13.3
rp...@google.com
jo...@gmail.com
To summarize, in AS3.1 there are 2 cases where a fixed 4-space indentation is now used:
- On duplicate timestamp (or perhaps duplicate of "date and time + process and thread IDs + package name + tag").
- On subsequent lines of a multi-line trace.
In AS 3.0.x, an indentation with n spaces was used, where n = length("date and time + process and thread IDs + package name + tag).
In AS 3.1, a fixed indentation of 4 spaces is used.
See the attached logcat file for a comparison of how a stacktrace appears.
If this new behaviour is a design decision, it should be consistent across the Run/Debug and Logcat windows, since both can display logcat traces, and it should be mentioned in the Release Notes.
- On duplicate timestamp (or perhaps duplicate of "date and time + process and thread IDs + package name + tag").
- On subsequent lines of a multi-line trace.
In AS 3.0.x, an indentation with n spaces was used, where n = length("date and time + process and thread IDs + package name + tag).
In AS 3.1, a fixed indentation of 4 spaces is used.
See the attached logcat file for a comparison of how a stacktrace appears.
If this new behaviour is a design decision, it should be consistent across the Run/Debug and Logcat windows, since both can display logcat traces, and it should be mentioned in the Release Notes.
ju...@google.com
1. Are you seeing message header (the "03-30 13:52:06.199 17777-17777/com.google.myapplication W/MainActivity: " part of a message) deduplication in the Logcat tool window? That's odd to me as I never consciously do that. Do you have explicit reproduction steps?
2. The multiline message indentation was a conscious decision of mine, and that was to fix
https://issuetracker.google.com/69886978 . Are you OK with that new behavior?
I do agree that the Logcat and Run windows should be consistent. And I do see that they're not. I'm going to use this issue to track that problem. If you feel that the first two things are real problems please file separate issues for them. Thank you.
2. The multiline message indentation was a conscious decision of mine, and that was to fix
I do agree that the Logcat and Run windows should be consistent. And I do see that they're not. I'm going to use this issue to track that problem. If you feel that the first two things are real problems please file separate issues for them. Thank you.
ju...@braze.com
1. Yes, attached is a screenshot of the logcat tool window deduplication. I'll file a separate issue for this one.
jo...@gmail.com
I was unaware that the "multiline message indentation" change in 3.1 was to fix https://issuetracker.google.com/69886978 .
I wouldn't say the former way of displaying traces was in a "comic manner". In my opinion, it is simply a cleaner way to display traces that form kind of a block.
2. I think I can live with the 4-space fixed indentation for multiline traces. To me it's OK.
I wouldn't say the former way of displaying traces was in a "comic manner". In my opinion, it is simply a cleaner way to display traces that form kind of a block.
2. I think I can live with the 4-space fixed indentation for multiline traces. To me it's OK.
Description
In AS version 3.0.1 (and in 2.x AFAICR), additional lines of a multiline log trace (i.e. exception with stacktrace) were vertically aligned with the first line and they appeared correctly forming a block. The timespamp for the trace was displayed in the first line and additional lines were left-aligned with spaces with the first line, forming a block.
Also, when several traces had the same timestamp, the timestamp was displayed for all the traces.
With AS 3.1, it seems that log traces are displayed using a "feature" that replaces duplicate timestamps with spaces, breaking correct alignment in the Logcat window. Curiously, logcat traces in the Debug window appear correctly aligned, but also with duplicate timestamps replaced with spaces.
* Attachment 1: logcat traces as they appear in the Logcat window.
* Attachment 2: logcat traces as they appear in the Debug window.
Can this "remove duplicate timestamps from logcat traces" feature be disabled?
Thanks
Jose Aladro
Build: 3.1, AI-173.4670197, 201803220120, AI-173.4670197, JRE 1.8.0_152-release-1024-b01x64 JetBrains s.r.o, OS Linux(amd64) v4.9.0-3-amd64 unknown, screens 1920x1080Android Gradle Plugin: 3.1.0Gradle: 4.4NDK: from local.properties: (not specified); latest from SDK: (not found); LLDB: pinned revision 3.1 not found; latest from SDK: (package not found); CMake: from local.properties: (not specified); latest from SDK: (not found); from PATH: (not found); IMPORTANT: Please read