DE
Comment by ~shrik3 on ~rjarry/aerc
Ha, I just realized I forgot to redact the pin code but it's fine, unless whatsapp has a totally broken algorithm.
Ticket created by ~shrik3 on ~rjarry/aerc
aerc failed to render a list entry or open the email.
ERROR 2024/11/07 13:52:09.196119 worker.go:451: [mailbox] could not emit message info: could not get MessageInfo: could not get structure: multipart: NextPart: EOFaerc version
$aerc -v aerc 0.18.2-95-g2da30735c17c +notmuch-5.6.0 (go1.23.2 amd64 linux 2024-10-28)aerc is built on top of commit
434ca29c(master branch).this is a confirmation email from whatsapp. below the raw message from notmuch
Return-Path: <noreply@support.whatsapp.com> Delivered-To: <my_email_address> Received: from director-03.heinlein-hosting.de ([80.241.60.212]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by dobby37a.heinlein-hosting.de with LMTPS id aJEdNFCCLGeTpB8AaGESyw (envelope-from <noreply@support.whatsapp.com>) for <my_email_address>; Thu, 07 Nov 2024 10:03:12 +0100 Received: from mx1.mailbox.org ([80.241.60.212]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by director-03.heinlein-hosting.de with LMTPS id yIKXMVCCLGdfNAAAlScrYA (envelope-from <noreply@support.whatsapp.com>) for <my_email_address>; Thu, 07 Nov 2024 10:03:12 +0100 X-Amavis-Alert: BAD HEADER SECTION, MIME error: error: part did not end with expected boundary; ; error: unexpected end of parts before epilogue Authentication-Results: spamfilter06.heinlein-hosting.de (amavisd-new); dkim=pass (2048-bit key) header.d=support.whatsapp.com Received: from 69-171-232-147.mail-mail.facebook.com (69-171-232-147.mail-mail.facebook.com [69.171.232.147]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mx1.mailbox.org (Postfix) with ESMTPS id 4FD0141567 for <my_email_address>; Thu, 7 Nov 2024 10:03:02 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=support.whatsapp.com; s=s2048-2018-q2; t=1730970169; bh=1UBFsGaAQHCNboqnc1ovdVuPc0Y7KCnPb/nOQsd3EQg=; h=Mime-Version:To:From:Subject:Content-Type:Date; b=XOklAyFVGBaTot8CYUSWMq2LXkKDm4G25bvAGCMh8/RGpXfB93xWWZILX91yYr8jx axVBQwYoxRX5ENiQ6p33TYuPFDXbThxaVaCSz8Q09jfHq3P5KV0L+YJYU/8antsSE1 WuJkdjRT7qwkqnYBZ1LhWEN7DByIxh/nsObumkZ+Eb3rJ9L0neiUkL13jUiAFIaWlm LzIHzChSk218gPMU+qaDNmaQ0b02wpyM4p313hzWletsUJK+g83Ff87sN94vTFbJMC Xnom7TYcyC6G8olUbHU3XNzsgIvxuxxfReqlFppfxGi5a7oA10OVgMrUPVyNEtB6J2 HFPb1H2Kxmj6Q== Mime-Version: : 1.0 To: my_email_address From: "WhatsApp" <noreply@support.whatsapp.com> Subject: WhatsApp Verification Code: 238-820 Content-Type: Multipart/alternative; boundary="--Next_Part(7509458211b958410724e06bcf531f0a)--" Content-Transfer-Encoding: 7bit Date: Thu, 07 Nov 2024 01:02:49 -0800 Message-ID: <106e0246-9ce7-11ef-a512-f9b591d3da99@support.whatsapp.com> X-Rspamd-Queue-Id: 4FD0141567 X-MBO-SPAM-Probability: X-Rspamd-Score: -16.81 / 15.00 / 15.00 X-TUID: Zm6ig3dRPAxj ----Next_Part(7509458211b958410724e06bcf531f0a)-- Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format="flowed" Content-Transfer-Encoding: quoted-printable We received a request to add my_email_address to your WhatsApp account. To verify your email: Open WhatsApp on your phone Go to Settings > Account > Email address Enter this code: 238-820 This code will expire in 4 hours. Don't share this code or email with anyone. If you didn't request verification, you can safely ignore this. ----Next_Part(7509458211b958410724e06bcf531f0a)-- Mime-Version: 1.0 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable <html>We received a request to add my_email_address to your WhatsApp account. To verify your email: <br><br> Open WhatsApp on your phone <br> Go to Settings > Account > Email address <br> Enter this code: <br><br> REDACTED <br><br> This code will expire in 4 hours. <br><br> Don't share this code or email with anyone. If you didn't request verification, you can safely ignore this.</html>
Ticket created by ~shrik3 on ~shrik3/rustubs
something to do with the GDT? I'm not setting that up for user (yet). Also the
gofunction is not following any calling convention to set up the stack and registers for the user task entry
Ticket created by ~shrik3 on ~rockorager/vaxis
On Sat Jun 15, 2024 at 5:54 PM CEST, Runxi Yu wrote:
I was reading an email with interwoven English and Chinese via
aercand I noticed that CJK text (which is usually double the width of latin characters) is handled incorrectly. If I have a line full of测试proceeded a blank line followed by lines ofAAAAAA, and I scroll down, sometimes the blank line will have ghostAs floating around, usually aligned with the right half of each CJK character. [...] Screencast: https://www.andrewyu.org/aerc.mkv (link may expire) Demo file: https://paste.sr.ht/blob/838a040bcd13a511a88e3910c4eeba7927f68058Hi,
I think the is the same issue I reported earlier..
https://lists.sr.ht/~rjarry/aerc-discuss/%3CD17U7S2YO9OV.10YADIV3NLRGL@mailbox.org%3E
btw. I just realized when writing this reply that the CJK text is also broken in the editor. I'm using neovim inside of aerc, neovim on its own has no issue.
cheers, wth
Ticket created by ~shrik3 on ~shrik3/rustubs
as a ringbuffer, the VecDeque should be bounded for some usecases e.g. the epilogue queue and key buffer. Here it's okay to lose unfetched objects. Also we need to have a max value for semaphore.
A bonus point would be using a lock free ring buffer.
Comment by ~shrik3 on ~shrik3/rustubs
REPORTED RESOLVED CLOSED
Ticket created by ~shrik3 on ~shrik3/rustubs
gdt reserved in asm startup code is mapped to low physical address. This is still usable in the higher half kernel because we still have the provisional id mapping. As soon as this mapping is removed (because low address belongs to userspace), the gdt will become unavailable and trigger page faults ... meh. We move the gdt to higher memory (by creating another mapping in the kernel VMAs).
Comment by ~shrik3 on ~shrik3/rustubs
REPORTED RESOLVED CLOSED
Comment by ~shrik3 on ~shrik3/rustubs
REPORTED RESOLVED FIXED
Comment by ~shrik3 on ~sircmpwn/lists.sr.ht
sorry I misclicked. please delete.