Request: Add option to show duplicate log headers (Android Studio 3.0 behavior) [78105884]

Duplicate

of 77305804

Feature Request

Regression

Status Update

No update yet.

Description

fa...@gmail.com

created issue #1

Apr 16, 2018 09:00PM

In Android Studio 3.1 and 3.2, duplicate log headers in logcat are filtered out and replaced with four spaces (changed as part of

https://issuetracker.google.com/issues/69886978). However, this change breaks the output of libraries such as

https://github.com/ihsanbal/LoggingInterceptor which rely on the Android Studio 3.0 behavior of having a consistent indent between logcat lines. This change also makes the logcat output difficult to read as lines in the logcat output have wildly different indentations with the duplicate headers removed.

Please add a checkbox in the Configure Logcat Header dialog to allow users to restore the duplicate headers, if desired.

Comments

uc...@google.com <uc...@google.com> #2Apr 17, 2018 05:48PM

Assigned to rp...@google.com.

Project: platform/frameworks/support
Branch: androidx-main
Author: Louis Pullen-Freilich <lpf@google.com>
Link: https://android-review.googlesource.com/3328184

Adds OverscrollEffect#withoutDrawing and OverscrollEffect#withoutEventHandling

Expand for full commit details

Adds OverscrollEffect#withoutDrawing and OverscrollEffect#withoutEventHandling 
 
These APIs allow overscroll to have events dispatched to it by one component, and rendered in a separate component. 
 
Fixes: b/266550551 
Fixes: b/204650733 
Fixes: b/255554340 
Fixes: b/229537244 
Test: OverscrollTest 
Relnote: "Adds OverscrollEffect#withoutDrawing and OverscrollEffect#withoutEventHandling APIs - these APIs create a wrapped instance of the provided overscroll effect that doesn't draw / handle events respectively, which allows for rendering  overscroll in a separate component from the component that is dispatching events. For example, disabling drawing the overscroll inside a lazy list, and then drawing the overscroll separately on top / elsewhere." 
Change-Id: Idbb3d91546b49c1987a041f959bce4b2b09a9f61

Files:

M compose/foundation/foundation/api/current.txt
M compose/foundation/foundation/api/restricted_current.txt
M compose/foundation/foundation/integration-tests/foundation-demos/src/main/java/androidx/compose/foundation/demos/OverscrollDemo.kt
M compose/foundation/foundation/samples/src/main/java/androidx/compose/foundation/samples/OverscrollSample.kt
M compose/foundation/foundation/src/androidInstrumentedTest/kotlin/androidx/compose/foundation/OverscrollTest.kt
M compose/foundation/foundation/src/commonMain/kotlin/androidx/compose/foundation/Overscroll.kt

Hash: f64e25b7a473c757d080521e7dd97b3f6670f60d
Date: Fri Nov 01 18:43:56 2024

rp...@google.com <rp...@google.com> Apr 17, 2018 06:12PM

Reassigned to ju...@google.com.

rp...@google.com <rp...@google.com> #3May 7, 2018 09:17PM

The following release(s) address this bug.It is possible this bug has only been partially addressed:

androidx.compose.foundation:foundation:1.8.0-alpha06
androidx.compose.foundation:foundation-android:1.8.0-alpha06
androidx.compose.foundation:foundation-jvmstubs:1.8.0-alpha06
androidx.compose.foundation:foundation-linuxx64stubs:1.8.0-alpha06

ju...@google.com <ju...@google.com> May 7, 2018 09:18PM

Status: Duplicate of

77305804

fa...@gmail.com <fa...@gmail.com> #4May 8, 2018 02:43AM

#3 I can't think of any reason to de-duplicate the headers. Looking at the duplicate bug (77305804) it looks like this behavior was reverted in the latest 3.2 Canary. I'll give that a try. Thanks!

kr...@gmail.com <kr...@gmail.com> #5Aug 2, 2018 07:01AM

I am strongly voting for removing this ugly mess caused by the grouping. It is very hard to read the logs after this kind of "improvement". I cannot imagine anyone benefiting from it. But anyways, at least make it optional, please please...

[Deleted User] <[Deleted User]> #6Aug 8, 2018 08:47PM

This "improvement" is a huge pain. The logs now lack any and all formatting, making them incredibly frustrating to utilize. Please undo this behavior or at least make it optional to toggle (those who enjoy chaos, agony and despair can enable it).

[Deleted User] <[Deleted User]> #7Aug 15, 2018 07:49AM

Yes, this is crap all the way through. At least let us have the option to turn grouping off!

re...@audioguidia.com <re...@audioguidia.com> #8Sep 7, 2018 01:48PM

Please solve this problem. When filtering logcat with a keyword, I want to have only the log containing this keyword in my log, not all the other logs with the same timestamp... Big problem to debug efficiently.

ta...@gmail.com <ta...@gmail.com> #9Sep 14, 2018 11:06PM

here we go again, Google breaking functionality with the so called improvements without even testing. when I am filtering with a tag, some logs are appended to others that I don't wanna see... and the filtering is broken. PLEASE FIX.