IssueTracker

Thanks for the feedback on the emulator. To help us troubleshoot this issue further, we will need more information. Please share detailed reproduction steps and as much as possible of the following information:

1. Emulator version
2. Run the emulator from command line with “$ANDROID_SDK_ROOT/emulator/emulator -avd <NameOfAVD> -verbose -show-kernel” and send the resulting logs
3. Any relevant Logcat logs
4. The results of running “adb shell top” in the command line.

For more information on what’s needed and how to obtain this information please read the guide at https://developer.android.com/studio/report-bugs#emulator-bugs.

Thanks for your request. We will investigate this issue and see if we can implement the behavior you've requested.

As an additional alternative, it should be possible to specify a label in the options for GmailApp.sendEmail().

A work-around is proposed in StackOverflow: http://stackoverflow.com/a/18727687/1677912

Are there any news on adding the ability to archive and add a label to specific emails (not threads)? From a corporate shared mailbox perspective auto threading emails by subject is a serious issue (eg. we recive two emails from the same person with same subject but with different description).

Since it's available in pure mailbox view is that such a big effort to make it available also in Google Script?

Looking forward to having this implemented. As has been mentioned automatic threading based on subject is a big no-no for our enterprise. We get automated reports and other documents sent to us by customers and suppliers and they are lumped together in threads making it very difficult for me to let Apps Script process them automatically since labels (i.e. outlook folders) have to be applied to entire threads (even though the messages in these threads often need to be treated differently).

Please add this function (and message.getlabel too) we need to scan message not only the thread.

Will there be any progress on this issue? Threading is great for humans, but if you are scripting, accessing and manipulating individual messages is MUCH more important, especially if it can be done from the normal user interface. Anything you can do to the thread you should be able to do at the message level.

Unassigning

Activate advanced google services/gmail api and use the gmail api functions.
I have resolved the same issue :)

Thanks!

kernel panic

    4.050109] NOHZ tick-stop error: Non-RCU local softirq work is pending, handler #10!!!
[    4.066103] NOHZ tick-stop error: Non-RCU local softirq work is pending, handler #10!!!
[    4.094936] traps: init[1] trap invalid opcode ip:7f2d60581262 sp:7ffdcb710a90 error:0 in libcrypto.so[7f2d60499000+10f000]
[    4.097003] libc: Fatal signal 4 (SIGILL), code 2 (ILL_ILLOPN), fault addr 0x7f2d60581262 in tid 1 (init), pid 1 (init)
[    4.100812] traps: init[1] trap invalid opcode ip:7f2d60581262 sp:7ffdcb710a90 error:0 in libcrypto.so[7f2d60499000+10f000]
[    4.103058] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004
[    4.104489] CPU: 0 PID: 1 Comm: init Tainted: G           O      5.10.66-android12-9-00041-gfa9c9074531e-ab7914766 #1
[    4.106531] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org 04/01/2014
[    4.108779] Call Trace:
[    4.109257]  panic+0x125/0x40b
[    4.109841]  do_exit+0xb9c/0xc20
[    4.110486]  do_group_exit+0x9a/0xe0
[    4.111162]  get_signal+0xd36/0xe50
[    4.111829]  ? send_signal+0x246/0x270
[    4.112616]  arch_do_signal+0x80/0x260
[    4.113334]  exit_to_user_mode_prepare+0xaa/0xe0
[    4.114205]  irqentry_exit_to_user_mode+0x9/0x20
[    4.115076]  irqentry_exit+0x12/0x60
[    4.115763]  exc_invalid_op+0x187/0x1d0
[    4.116488]  ? asm_exc_invalid_op+0xa/0x20
[    4.117269]  asm_exc_invalid_op+0x12/0x20
[    4.118070] RIP: 0033:0x7f2d60581262
[    4.118792] Code: 00 00 00 0f 84 8f 01 00 00 81 fe 80 00 00 00 0f 85 13 04 00 00 be 09 00 00 00 41 81 fa 00 00 00 10 0f 84 81 00 00 00 0f 11 02 <66> 0f 3a df c8 01 e8 2a 04 00 00 66 0f 3a df c8 02 e8 18 04 00 00
[    4.122298] RSP: 002b:00007ffdcb710a90 EFLAGS: 00010287
[    4.123281] RAX: 00007ffdcb7111f0 RBX: 0000000000000032 RCX: 00007ffdcb711500
[    4.124609] RDX: 00007ffdcb7111e0 RSI: 0000000000000009 RDI: 00007f2d60468b40
[    4.125954] RBP: 0000000000000020 R08: 0000000000000258 R09: 00007ffdcb711540
[    4.127293] R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffdcb711958
[    4.128626] R13: 00007ffdcb711908 R14: 00007f2d605b9610 R15: 00007f2d6051f300
[    4.130110] Kernel Offset: 0xb600000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)

Reply to #10: the checked was added by Frank, which seemed to have a valid reason. However, the check for EPT and UG is not perfect. See the comments below:
// For detecting that the cpu can run with fast virtualization
// without requiring workarounds such as resetting SMP=1.
//
// Technically, we need  rdmsr to detect ept/ug support,
// but that instruction is only available
// as root. So just say yes if the processor has features that were
// only introduced the same time as the feature.
// EPT: popcnt
// UG: aes + pclmulqsq
In a summary, we did not (or could not) check EPT and UG directly but using other CPU features as a best guess. Perhaps, the assumption is broken for the user's specific CPU model.

Later, there is a message showing WHPX is operational. From the log, it seems the WHPX is working fine.

Roman, I think chenqiao1104 is the original reported and now Yahan is talking with a different user.

For chenqiao1104's issue, this UD was actually the third occurrence of the AESNI being used (which should NOT be used). For the other two occurrence, one user said he fixed the issue by reinstalling the Windows. I cannot reach the other one.

For the issue Yahan is working on, I will assign it back. For chenqiao1104's issue, we already have open bugs to track it.