- Feb 27, 2021
-
-
hydrargyrum authored
-
hydrargyrum authored
-
hydrargyrum authored
-
hydrargyrum authored
Since the launcher can run any of them, and they have names with a common prefix, it's not needed to have dedicated commands.
-
hydrargyrum authored
The main command, woob, now takes a name from weboob.applications.* (instead of capability name) and runs it with the other given arguments.
-
hydrargyrum authored
-
hydrargyrum authored
-
hydrargyrum authored
Use woob-{name} where name is most often the cap name. E.g. boobank -> woob-bank
-
- Feb 26, 2021
-
-
hydrargyrum authored
-
hydrargyrum authored
After years of controversy around the project name and content because of poor-taste jokes, the project and its apps will be renamed and the offensive content be removed. We are sorry for the past offensive content and we apologize for any harm that has been caused by it. In the next release, everything will be in the woob namespace. In the meantime, we keep both packages, so apps can test the transition. This is the first step of many towards full renaming of the project.
-
In this particular case, if we get the "unavailable website" message, we want to try to fetch invests on the other life insurance page.
-
The input value can differ slightly from the investment label (the number of spaces between words can vary for example), so we use the form param directly. Also, sometimes there is no form input for a given invest, so we don't try to fetch its details.
-
to avoid doing things twice we are not sure yet if it's possible since orange like to put some data in some URL but not other sometimes
-
because this wonderful website isn't able to provide same data in json and html sometimes you get data just in html, sometimes both
-
-
There could be stock without an available isin. In that case, the parsed url will have an empty isin arg and be like: <li><a href="/priv/mobilalert.php?isin=&page=Events"> We change the regexp to consider the "empty" isin a valid value. And in the caller, the is_isin_valid will be False, and so inv.code will keep the NotAvailable value for this entry.
-
Sometimes it looks like that the login was successful but we are still not connected.
-
Despite the webpage meta charset declaring to be UTF-8, some pages content is not UTF-8 valid content. Ex.: iso 8859 é (0xe9). In fact, most of the content is simple uppercase ascii, but sometimes accounts name could be missing and be replaced by the string: "Compte non trouvé". The encoding in the response header content-type looks like to be correct.
-
Because "Erreur d'authentification" appears in the case of a blocked account as it is the title. Also, as we do a retry on "BrowserUnavailable" errors, we were uselessly retrying.
-
The quantity is not directly on the investment page, but in the cases where we fetch invests from this page, we can easily go to the detailed view and get the quantity there.
-
Invalid credential cases were not handled properly, so wrongpass error would not be raised.
-
Make module pyflakes compliant
-
Seems to occur every morning around 6 am.
-
Some stocks are present in several investments in the json. On the website, they are combined in js.
-
The name part of the request that is extracted, could be very very long, and then the har-to-old.py script will fail because the filename is longer than what is allowed by the file system.
-
When we use the same form for all investments, even if we clean it each time, we arrive on the same page (the first one we got to using the form), so all investments and pockets had the same additional info, like quantity for example. We don't have the issue when we re-fetch the form each time.
-
The error message appears when the user is trying to do a transfer of the amount of a check that was received in the 10 previous days.
-
one occurence of Tile was missing in a previous commit
-
There are 3 different way described in a comment to get a prompt message for the otp. I have chosen to go for the third way since the first message is not clear enough, the second message is only in ascii and so, full of misspelling since it's french.
-
-
-
when there are no loans, it's useless to try again and again and again...
-
`condition()` methods are usually defined at the beginning of an item processing. It was all the way down which can confuse the readers.
-
Split sub-transactions are filtered out by `condition`. However the current XPath to get the `obj_amount`, matches multiple element (the global transaction and the split sub-transactions) causing an AssertionError using the `CleanDecimal.French` filter. To solve this, we first check if the transaction is split. If it is we only use the first matched element (which corresponds to the transaction's total amount)
-
Some market orders have no quantity and are instead some sort of subscription. The amount label in the table is also a bit different so I adapted that as well.
-
-
Usually, with Boursorama, otp was only encountered when adding recipients. But, an otp could be needed at confirmation step for some transfers (ex. big amounts, unregistered foreign bank accounts). In addition, a check was added to ensure that a transfer is really confirmed before returning successfully from execute_transfer.
-
-
When reloading state and requesting the last page visited, we are usally logged out. If that page was EasyTransferPage, in that case, it is now a JSON, instead of the regular HTML when already logged. This is now handled with a special logged property.
-
When the otp step was not completed or failed, a recipient was still created on the bnp website with the "to be activated state". It was not possible to do more than a single otp code attempt without going into an unexpected state. And trying to add again the recipient would fail with the following error: "Bénéficiaire en doublon. Code bic / iban / compte déjà présent en base." This change will detect if the recipient already exists in a "to be validated" state, and in that case will just trigger the activation otp or decoupled instead of trying to add the recipient again.
-