[skrooge] [Bug 524292] New: Wrong values downloaded for stock symbols

Christoph Vogtländer <[email protected]>
Newsgroups gmane.comp.kde.devel.bugs
Message-ID <[email protected]/>
https://bugs.kde.org/show_bug.cgi?id=524292

            Bug ID: 524292
           Summary: Wrong values downloaded for stock symbols
    Classification: Applications
           Product: skrooge
      Version First 26.4.0
       Reported In:
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: 25.1.0

DESCRIPTION
With the skrooge-boursorama.py backend, using a stock symbol like "AAPL" will
actually download values for "1rPCAC". The symbol is not detected as a direct
symbol. Using the ISIN US0378331005 does not work either.

STEPS TO REPRODUCE
1a. skrooge-boursorama.py AAPL 2026-08-13 1d
1b. skrooge-boursorama.py US0378331005 2026-08-13 1d

OBSERVED RESULT
date,price
2026-08-14,8657.59
2026-08-13,8702.54

EXPECTED RESULT
date,price
2026-08-14,305.93
2026-08-13,305.26

SOFTWARE/OS VERSIONS
Operating System: EndeavourOS 
KDE Plasma Version: 6.7.4
KDE Frameworks Version: 6.28.0
Qt Version: 6.11.1
Kernel Version: 7.1.5-arch1-2 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 8700G w/ Radeon 780M Graphics
Memory: 16 GiB of RAM (14.8 GiB usable)
Graphics Processor: AMD Radeon 780M Graphics
Manufacturer: LENOVO
Product Name: 12TACTO1WW
System Version: ThinkCentre M75s Gen 5

ADDITIONAL INFORMATION
After a brief inspection of skrooge-boursorama.py i think the problem is that
the symbol does not match BROKER_SYMBOL_RE and then in
extract_symbol_from_payload() it seems that the other symbols which are also
found are rated with a higher priority.

My current workaround is to add my symbol to BROKER_SYMBOL_RE (which of course
is not a valid fix, but works for me)

Note: i also tried the latest version of skrooge-boursorama.py from current 
26.8.0 release and had been able to reproduce the issue.

-- 
You are receiving this mail because:
You are watching all bug changes.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.