- May 22, 2020
-
-
-
-
The iter_history was only returning the last month of history whereas 3 months are available in the JSON. Besides, there was no 'dayfirst=True' so all the dates were completely wrong.
-
-
Less granularity but job overhead is paid less times.
-
-
On some websites we observe 3 dates: validity_date, creation date and execution date. The 'date' attribute is set to the creation_date since all market orders have one, whereas some market orders (that are still ongoing, or that have been refused or cancelled) have no execution_date, and the date is often used to sort the orders chronologically.
-
- May 10, 2020
-
-
- May 08, 2020
-
-
hydrargyrum authored
-
hydrargyrum authored
-
hydrargyrum authored
-
hydrargyrum authored
-
hydrargyrum authored
-
- May 07, 2020
-
-
-
-
This was rejected: [ (a), ] because last token of last element is "a", not ")". So we have to skip closing parentheses before reaching the trailing comma. Also, simply use "generic_visit" instead of calling "visit" on sub nodes ourselves.
-
-
-
-
-
-
-
-
-
-
New checks will be applied on files containing a comment such as "# flake8: compatible".
-
-
-
Some Market Orders have no indicated quantity and have a total amount instead.
-
Sometimes there is not information on the quantity of stocks that has been bought or sold, only the total amount that has been bought or sold.
-
To do transfers, the website now requires that the 'country' should be with the 'creditAccount' instead of being at the root of the json. Closes: 19113@sibi
-
keep only the transaction of swile card Closes: 18595@zendesk
-
In python3 the str.isalpha() (same for str.isalnum()) method returns True if every symbol in the string is defined as "Letter" in the unicode character database. It includes non "ASCII alphabetical" characters, leading to a virtual keyboard crash. We set a regexp in module.py to solve this issue.
-
-
-
Closes: 75201@sibi 66425@sibi
-
-
NSS uses a certificate database that is empty by default and not updated automatically when new CAs are added in /etc/ssl/certs. So we are forced to recreate the database from scratch and since it takes about 1 minute, due to "certutil" command being slow, we can't do it everytime. By implementing an update operation that only adds new certificates and removes obsolete ones, we run certutil much less, so the update is significantly faster. In order to detect changes to certificates, and because NSS databases and PEM data are very shitty to introspect, we will base ourselves mostly on NSS cert "nicknames". As /etc/ssl/certs contains a lot of duplicates, we will rely on PEM data hashing instead instead of filenames to detect different certificates, and they will be the nicknames. Simplified, an update operation goes like this: - list all db cert hashes (the nicknames) - hash all system certs - add in db all system certs for which the nickname was missing - remove from db the nicknames if the hash wasn't in system list For migrating to new nicknames format, basically we will have to purge the db and recreate it.
-
When adding a non-french recipient we get sent back on the NewRecipientPage with an error message. The `self.page.get_error()` in continue_sms_recipient crashed because the NewRecipientPage did not have a get_error method because it was not expected to be here. Closes: 72427@sibi
-
Sometimes, after going to the lifeinsurance page, we would get an error 500 when going back to the other pages. Also, the request that goes from the new website to the old website often timed out so I increased the delay. Closes: 60445@sibi, 64287@sibi, 64337@sibi, 64397@sibi, 65064@sibi, 61668@sibi
-