Status Update
Comments
sm...@google.com <sm...@google.com>
pe...@google.com <pe...@google.com> #2
For example for first requests, there is always this message ("This request caused a new process to be started for your application, and thus..."), but in other cases, there can be such messages like (""While handling this request, the process that handled this request was found to be using too much memory...") In both cases my log messages (that should be correlated) are missing from the group, while in normal cases, they are there.
So rather than a "Feature Request", I'd rather classify this issue as a bug report, here is some motivation for that:
1. The correct, bug-free behavior is already described in the official docs without mentioning this issue:
2. This issue only comes up in edge cases, but debugging and reading logs might be more important in such edge cases.
3. This has already worked in Python 2 GAE.
pp...@gmail.com <pp...@gmail.com> #3
pp...@gmail.com <pp...@gmail.com> #4
pe...@google.com <pe...@google.com> #5
pp...@gmail.com <pp...@gmail.com> #6
pe...@google.com <pe...@google.com> #7
pp...@gmail.com <pp...@gmail.com> #8
This bug is the only thing that prevents us from updating for many years.
If it's not fixed by the Java8 deprecation date - we (and similar client) will likely get in trouble.
pe...@google.com <pe...@google.com> #9
pp...@gmail.com <pp...@gmail.com> #10
pe...@google.com <pe...@google.com> #11
pp...@gmail.com <pp...@gmail.com> #12
This should be fixed in production now.
I've verified this with Java17.
pp...@gmail.com <pp...@gmail.com> #13
se...@google.com <se...@google.com> #14
This is the cause. For context, Network Inspector assumes there is only ever one instance of the android Application, but clearly that is violated
well we shouldn't enforce that. It is possible for devs to write following val a = Application()
and we'll find multiple instances. NetworkInspector should do best effort: try to call with try-catch all applications that you've got and see if you can get at least one uid
pe...@google.com <pe...@google.com> #15
This should be fixed in CM beta 4 (March 3rd release) and Dolphin canary 5 (March 1st release).
pp...@gmail.com <pp...@gmail.com> #16
pe...@google.com <pe...@google.com> #17
Update: this will also be fixed in BB patch 3 (mid-late March release).
pp...@gmail.com <pp...@gmail.com> #18
de...@google.com <de...@google.com> #19
Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:
- Android Studio Dolphin Canary 5 (2021.3.1.5)
- Android Gradle Plugin 7.3.0-alpha05
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Thank you for taking the time to submit feedback — we really appreciate it!
pp...@gmail.com <pp...@gmail.com> #20
ko...@gmail.com <ko...@gmail.com> #21
Terima kasih atas masukkan dan kritikannya, kedepannya saya juga akan terus berusaha untuk memperbaiki masalah yang saya dapatkan.
Description
Build: AI-211.7628.21.2111.8139111, 202202012023,
AI-211.7628.21.2111.8139111, JRE 11.0.11+9-b60-7590822x64 JetBrains s.r.o, OS Windows 10(amd64) v10.0 , screens 1920.0x1080.0, 1920.0x1080.0
AS: Bumblebee | 2021.1.1 Patch 1; Kotlin plugin: 211-1.6.10-release-923-AS7442.40; Android Gradle Plugin: 7.0.4; Gradle: 7.0.2; Gradle JDK: version 11.0.11; NDK: 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)Source: user_sentiment_feedback
IMPORTANT: Please read