jlouvel authored Nov 30, 2023 and Romain Bignon committed Jan 11, 2024

URL to get bnp's investments details has been crashing
randomly for years with random 503. This is still the
case except that now, on the website, this 503 takes
up to two minutes to be triggered. The module's timeout
set at 60 isn't even enough for this. Rather than making
very long synchronization, we now assume that 30 seconds
timeout on this specific request is enough to consider
the details as unavailable.

lbellebouche authored Jul 04, 2023 and Romain Bignon committed Jul 12, 2023

Update baseurl and raise an ActionNeed
with the message displayed on the website,
telling that users must now go to
www.esalia.com with their new credentials
to retrieve their PEE.

Yacine BOUHALA authored May 17, 2023 and Quentin Defenouillere committed Jun 01, 2023

The URL:
'https://www.comgest.com//fr/fr/professionnel/...&tab=12'
is automatically opened when we try to retrieve
the investments of certain accounts.
However, this URL leads us to an error page
with a 500 status code.
Since there is no useful information on the
Comgest website, we ignore this URL.

kmartins authored Mar 23, 2023 and Romain Bignon committed Mar 28, 2023

Erehsbc and Esalia browser with `BASEURL`, `LANG`
and `SLUG` are now moved to their respective browsers

jlouvel authored Feb 16, 2023 and Romain Bignon committed Mar 04, 2023

For bnppere "personeo" connections using s2e browser, we are now
redirected to a new URL for bnp_investments page. This made the browser
think it was not logged if we called for history after investments for
example, since it was unable to handle the page (and it did not crash
because we did nothing with that unhandled page). The browser trying to
relogin while it was already logged triggered a strange bug on the
website where it made us land on a page asking the user to accept his
terms of conditions (but nowhere on the user space this page really
exists, plus if we get on this page, we can just go on any other page
without problem and the page never appears again). Added the new URL
in new_bnp_investments since the old one is still needed
for investments details matching (the "home" of bnp_investments is
now "personeo.epargne..." but to get the details we have to go through
some "optimiser.epargne..." URLs like before). Also added some details
about a 401 that was already here when requesting investment details,
this happen randomly on any given investment, couldn't find a way to
prevent this.

Thomas Toumeyragues authored Jul 13, 2022 and ntome committed Aug 08, 2022

Some accounts are bugged, we cannot access them on the
account page.
In that case, the website returns an error message
that is now handled.
Also, when the account is bugged or when there
are no accounts there is no form on the page which
caused a bug on our side.
Now we first verify if there is a form on the page.
If there is not, we display the corresponding exception

kmartins authored Jun 21, 2022 and ntome committed Jun 27, 2022

This is a specific case for amundi (highlighted
by a task on creditdunordpee), on some invest
there's no more details and despite of that we
still try to build and reach this url

nvergnac authored Mar 17, 2022 and ntome committed Mar 29, 2022

The OTP was not sent anymore.

Update capeasi, erehsbc, esalia, federalfinancees, creditdunordpee

sfartit authored Mar 02, 2022 and ntome committed Mar 09, 2022

Currently, for each transaction we make a request to get the list of
investments related to it. These requests make up a huge percentage of
the total requests we make during synchros. If we stop doing this it
will drastically reduce the load on s2e servers.

This also fix a navigation problem, currently we don't press the return
button after going to the details page. This causes us to keep getting
the same html for almost all transactions.

- current iter_history:
	- for each transaction, we get the list of investments
	- the amount = sum(investments.valuations)
	- no return to previous page

- next iter_history:
	- the amount = net_amount + net_employer_contribution_amount
	- we drop the transaction.investments attribute
	- return after visiting details page

Note:
      - this will only impact "monoaccount" connections and "monoaccount"
        spaces, in multispaces connections.
      - for connections with multiple accounts, we will still need
        to visit the details page, to know which transaction is
        related to which account.

nvergnac authored Feb 03, 2022 and ntome committed Mar 09, 2022

s2e complained about our sessions not logging off

our activity takes too much bandwidth on their servers

the logout has no impact on the 2FA authentications

basestring, range, long, url*, parse*, unicode, html_unescape
also, remove some obsolete sys.version checks

Jerome Berthier authored Feb 01, 2022 and ntome committed Feb 18, 2022

Works only with children browsers supporting request_information
in their CONFIG, so currently only Bnppere browser.

Christophe François authored Jun 10, 2021 and ntome committed Feb 02, 2022

We have no creds but the website uses s2e, it should work like other
children of the module.

sfartit authored Jan 24, 2022 and ntome committed Jan 26, 2022

Sometimes we get redirected to `/portal/setcontrolcookie`
which returns a 404, that needs to be handled. A retry do the trick.

We also handle a new url: `/pagesdedelestage/BNPP/index.html`
which say that the server has a big load and is sometimes not
responding. Also a retry does the trick.

We also increase the number of tries of the retry, because there are
more things that could cause it and two tries may not be enough anymore.

In some modules that inherit from s2e and in some particular connections,
we get redirected by default to a page that contains stock markets.
we remove the redirect key from the forms to restore the normal behaviour.

The previous checks are not needed anymore. I deleted them.

In some connections we get redirected to an unhandled url:
portal/salarie-bnp/monepargne/mesblocages

For now, if we land on this page, we skip it.

jlouvel authored Dec 14, 2021 and ntome committed Dec 18, 2021

Tested for every child module, the error was present in all of them.

sfartit authored Aug 19, 2021 and hydrargyrum committed Aug 27, 2021

We encounter a case where 2 accounts are listed but are actually the
same.

nvergnac authored Aug 04, 2021 and hydrargyrum committed Aug 13, 2021

ignore accounts without ids

nvergnac authored Aug 02, 2021 and hydrargyrum committed Aug 13, 2021

some ids were wrongly matched, causing crash during iter_investments

Louise Zanier authored Jul 27, 2021 and hydrargyrum committed Aug 13, 2021

Apparently they got really creative.