Bug 21513 - skrooge: unable to update shares history with Yahoo
Summary: skrooge: unable to update shares history with Yahoo
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: MGA6-64-OK
Keywords: advisory, validated_update
Depends on:
Blocks:
 
Reported: 2017-08-13 13:21 CEST by Yann Ciret
Modified: 2017-09-07 11:08 CEST (History)
4 users (show)

See Also:
Source RPM: skrooge-2.7.0-1.mga6.src.rpm
CVE:
Status comment:


Attachments

Description Yann Ciret 2017-08-13 13:21:06 CEST
Description of problem:
When I open skrooge, I have notification there is a problem with Yahoo to update history of shares I follow:
"Unable to find history for ^ FCHI on Yahoo"

The release 2.9.0 fixes this issue (Correction bug 380232: Yahoo api discontinued). Mageia current release is 2.7.0 and many issues and performance improvements are made in 2.8.0 (https://skrooge.org/node/217) and 2.9.0 (https://skrooge.org/node/219).

It would be nice if version 2.9.0 is proposed as an update for Mageia 6.

Version-Release number of selected component (if applicable):


How reproducible:
Add a share in Units and choose Yahoo as download source.
In skrooge configuration > units, choose daily values since last download.
When you open skrooge after one day ore more, you have the error message.

Steps to Reproduce:
1.
2.
3.
Comment 1 David GEIGER 2017-08-14 12:59:45 CEST
Fixed for Cauldron and also for mga6 in Core/Updates_testing repo!

Can you test this new 2.9.0 release if all is fine, thanks in advance.

CC: (none) => geiger.david68210

Comment 2 Yann Ciret 2017-08-14 14:38:48 CEST
Hello David,

tested with Cauldron and mga6. It works well here.
Thank you for your quick action.
Comment 3 David GEIGER 2017-08-14 14:55:30 CEST
Assigning to QA,


Advisory:
========================

When you open skrooge, you get a notification that there is a problem with Yahoo to update history of shares:
"Unable to find history for ^ FCHI on Yahoo"

The release 2.9.0 fixes this issue (Correction bug kde#380232: Yahoo api discontinued).

https://bugs.kde.org/show_bug.cgi?id=380232

========================

Packages in 6/core/updates_testing:
========================
skrooge-2.9.0-1.mga6.i586.rpm
libskgbankgui2-2.9.0-1.mga6.i586.rpm
libskgbankmodeler2-2.9.0-1.mga6.i586.rpm
libskgbasegui2-2.9.0-1.mga6.i586.rpm
libskgbasemodeler2-2.9.0-1.mga6.i586.rpm

skrooge-2.9.0-1.mga6.x86_64.rpm
lib64skgbankgui2-2.9.0-1.mga6.x86_64.rpm
lib64skgbankmodeler2-2.9.0-1.mga6.x86_64.rpm
lib64skgbasegui2-2.9.0-1.mga6.x86_64.rpm
lib64skgbasemodeler2-2.9.0-1.mga6.x86_64.rpm

Source RPM: 
========================
skrooge-2.9.0-1.mga6.src.rpm

Assignee: bugsquad => qa-bugs

Comment 4 Lewis Smith 2017-08-23 11:27:05 CEST
@Yann
Thanks for your rapid test of the update. Trying to follow it - lost in Skrooge! It has masses of possibilities everywhere.
Could you please give more specific instructions for the steps you outlined in Comment 0:
What sort of account to create?
> Add a share in Units and choose Yahoo as download source.
Steer a novice, please.
> In skrooge configuration > units, choose daily values since last download.
I imagine this is self-explanatory once the scenario has been defined.

CC: (none) => lewyssmith

Lewis Smith 2017-08-23 11:28:13 CEST

CC: (none) => mageia

Comment 5 Lewis Smith 2017-08-24 21:34:25 CEST
@Yann
Added you to CC list for your help re Comment 4 if possible.
Lewis Smith 2017-08-30 08:55:00 CEST

Whiteboard: (none) => advisory

Comment 6 Yann Ciret 2017-09-04 15:51:18 CEST
Hello Lewis,

You can create the type of account you want. The issue is not related to an account.

So there is more detailed instructions:
1. Go to Units
2. At the bottom, click on Manual / Share
3. Fill the forms with these values:
   Name: EDF, Symbol: FR:EDF, Type: Share, Country: FR, Internet Code: EDF.PA
4. Save with the Add button
5. Click on the new line (EDF) on the list
6. Make a long click on Download button and choose "download all daily values"

After that, you should have the last 3 month daily values of EDF share.
Comment 7 Lewis Smith 2017-09-05 11:55:02 CEST
Testing M6/64

@ Yann : Thank you for your pointers. Skrooge drives me mad: you (I) can create an account which does not show in the 'Accounts' tab! Searched the Help also, re Accounts, Shares, Units. Thanks again for your guidance.

BEFORE the update: skrooge-2.7.0-1.mga6 + the following at same version:
- lib64skgbankgui2
- lib64skgbankmodeler2
- lib64skgbasegui2
- lib64skgbasemodeler2
Following Yann's path in Comment 6 (download source already showed Yahoo), I get a pop-up:  "History for EDF.PA not found on Yahoo".
Which I suppose is the original fault.

UPDATE to:
- lib64skgbankgui2-2.9.0-1.mga6.x86_64
- lib64skgbankmodeler2-2.9.0-1.mga6.x86_64
- lib64skgbasegui2-2.9.0-1.mga6.x86_64
- lib64skgbasemodeler2-2.9.0-1.mga6.x86_64
- skrooge-2.9.0-1.mga6.x86_64
Launching Skrooge showed a message "The document has been migrated", which is encouraging.
Via Dashboard to get to the account, 'Units', the previously defined line showed below a box with Date=Today, Amount entered=9.29 - all by itself, so I wonder whether the Yahoo link is working.

To cross-check, deleted and re-defined the share thingy line to re-run the procedure. At step 6, the cursor turned a few seconds, and then showed a lengthy history list and a graph. Phew! Good update.

OKing, validating. At last.

Whiteboard: advisory => advisory MGA6-64-OK
Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs

Comment 8 Samuel Verschelde 2017-09-06 15:11:53 CEST
Moving 'advisory' from whiteboard to keywords now that madb has been updated to handle that keyword.

Keywords: (none) => advisory
Whiteboard: advisory MGA6-64-OK => MGA6-64-OK

Comment 9 Mageia Robot 2017-09-07 11:08:02 CEST
An update for this issue has been pushed to the Mageia Updates repository.

http://advisories.mageia.org/MGAA-2017-0076.html

Resolution: (none) => FIXED
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.