From: Alviro Iskandar Setiawan <alviro.iskandar@gnuweeb.org>
To: Ammar Faizi <ammarfaizi2@gnuweeb.org>
Cc: "Vignesh Kumar Nadar (731 Lexington Avenue)"
<vnadar4@bloomberg.net>, Emma Demers <edemers8@bloomberg.net>,
Srishti Sharma <ssharma1074@bloomberg.net>,
Tanya Kureishi <tkureishi@bloomberg.net>,
Serena Chang <schang394@bloomberg.net>,
gwml@vger.gnuweeb.org
Subject: Re: Follow up on Heatmap Bug with Multi-Currency Watchlist
Date: Thu, 21 Aug 2025 04:34:27 +0700 [thread overview]
Message-ID: <CAOG64qOCG8GMoRh8gVzH9xcOjGx7Zy6qOtwjczr+nOzpFd99hw@mail.gmail.com> (raw)
In-Reply-To: <20250818170817.GA288084-ammarfaizi2@gnuweeb.org>
On Tue, Aug 19, 2025 at 12:08 AM Ammar Faizi wrote:
> The bug occurs when a watchlist includes assets priced in different
> currencies. Below is a step-by-step reproduction of the bug:
>
> 1) Create a new watchlist with USD as the base currency.
>
> 2) Add the following trades:
>
> - Buy 1 Ethereum (XETUSD:CUR) at price 4,000 USD.
> - Buy 1 Bitcoin (XBTUSD:CUR) at price 116,000 USD.
> - Buy 100 USD (USDIDR:CUR) at price 16,000 IDR (Indonesian Rupiah).
>
> In this scenario, Bitcoin should be my largest holding in USD terms.
> However, the heatmap incorrectly displays USDIDR as the largest holding,
> despite its value being only 100 USD.
BTW, a temporary solution for this, instead of using USDIDR:CUR, use
USD:CUR. So the adjusted trades will be:
- Buy 1 XETUSD:CUR at 4K USD.
- Buy 1 XBTUSD:CUR at 116K USD.
- Buy 100 USD:CUR at 1 USD.
You can't track your rupiah to US dollar changes though, but at least
it shows the correct heatmap tiles when you have USD in your holding.
I suggest using that temporarily until the Bloomberg Engineering team
fixes the multicurrency issue.
tq
--
Software Engineer & ITPM Officer
Alviro Iskandar Setiawan
next prev parent reply other threads:[~2025-08-20 21:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 17:08 Follow up on Heatmap Bug with Multi-Currency Watchlist Ammar Faizi
2025-08-19 14:18 ` Vignesh Kumar Nadar (BLOOMBERG/ 731 LEX)
2025-08-20 21:34 ` Alviro Iskandar Setiawan [this message]
2025-08-20 21:45 ` Follow " Ammar Faizi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAOG64qOCG8GMoRh8gVzH9xcOjGx7Zy6qOtwjczr+nOzpFd99hw@mail.gmail.com \
--to=alviro.iskandar@gnuweeb.org \
--cc=ammarfaizi2@gnuweeb.org \
--cc=edemers8@bloomberg.net \
--cc=gwml@vger.gnuweeb.org \
--cc=schang394@bloomberg.net \
--cc=ssharma1074@bloomberg.net \
--cc=tkureishi@bloomberg.net \
--cc=vnadar4@bloomberg.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox