From: "Vignesh Kumar Nadar (BLOOMBERG/ 731 LEX)" <vnadar4@bloomberg.net>
To: ammarfaizi2@gnuweeb.org
Cc: tkureishi@bloomberg.net, schang394@bloomberg.net,
edemers8@bloomberg.net, ssharma1074@bloomberg.net,
alviro.iskandar@gnuweeb.org, gwml@vger.gnuweeb.org
Subject: Re:Follow up on Heatmap Bug with Multi-Currency Watchlist
Date: Tue, 19 Aug 2025 14:18:13 -0000 [thread overview]
Message-ID: <68A487A400017D8B0A120001@message.bloomberg.net> (raw)
In-Reply-To: <20250818170817.GA288084-ammarfaizi2@gnuweeb.org>
[-- Attachment #1: Type: text/plain, Size: 2684 bytes --]
Hi Ammar
It was great talking to you at the user interview yesterday.Thanks for flagging and sharing detailed reproduction steps along with JSON payload.
This is very helpful.
In the meantime, we'll keep you posted as we investigate further and let you know
once we have a fix.
Best,
Vignesh
From: ammarfaizi2@gnuweeb.org At: 08/18/25 13:08:27 UTC-4:00To: Vignesh Kumar Nadar (BLOOMBERG/ 731 LEX ) , Emma Demers (BLOOMBERG/ NEWSROOM/ ) , Srishti Sharma (BLOOMBERG/ 731 LEX )
Cc: Tanya Kureishi (BLOOMBERG/ NEWSROOM/ ) , Serena Chang (BLOOMBERG/ 731 LEX ) , alviro.iskandar@gnuweeb.org, gwml@vger.gnuweeb.org
Subject: Follow up on Heatmap Bug with Multi-Currency Watchlist
Hi Vignesh, Emma, Srishti,
It was nice to meet you guys. Thanks for the Zoom meeting.
This is the follow up on the heatmap bug.
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.
I think a heatmap tile is now calculated by multiplying the number
of shares with the current price without caring about the currency
difference. That's probably the problematic part.
For now, the heatmap feature in the watchlist section completely messes
my visual up and not much useful because of this bug.
To be more specific for the Engineering team, I've included a JSON
payload for the watchlist creation endpoint:
HTTP POST
https://login.bloomberg.com/watchlist-service/create/36DBC7EAF256426ABFB0F8F8D21
B2A98
{
"portMeta": {
"name": "ABC",
"currency": "USD",
"isDefault": false
},
"holdings": [
{
"security": "XETUSD:CUR",
"buydate": 1755534614182,
"shares": 1,
"buyprice": 4000,
"torder": 0
},
{
"security": "XBTUSD:CUR",
"buydate": 1755534575189,
"shares": 1,
"buyprice": 116000,
"torder": 1
},
{
"security": "USDIDR:CUR",
"buydate": 1755534551554,
"shares": 100,
"buyprice": 16000,
"torder": 2
}
]
}
Let me know if you need further details to resolve this issue.
Thank you!
Best regards,
--
Ammar Faizi
[-- Attachment #2: Type: text/html, Size: 5385 bytes --]
next prev parent reply other threads:[~2025-08-19 14:18 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) [this message]
2025-08-20 21:34 ` Alviro Iskandar Setiawan
2025-08-20 21:45 ` 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=68A487A400017D8B0A120001@message.bloomberg.net \
--to=vnadar4@bloomberg.net \
--cc=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 \
/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