Releases: tzConnectBerlin/que-pasa
v1.2.6: --main-schema feature fix
v1.2.5: point ithacanet->ghostnet, and add jakartanet support
Merge pull request #59 from tzConnectBerlin/ghostnet-and-jakartanet point ithacanet->ghostnet, and add jakartanet support
v1.2.4
v1.2.3
v1.2.2: _live derived tables bugfix
When a multi-element datatype was erased (emptied), _live remained unupdated. This has been fixed now.
For more info, see the related PR: #53
V1.2.1: indexing of contract call parameters
Que Pasa now also indexes the parameters of contract calls, and writes them into new tables under entry.<entrypoint> (plus potential child tables, if the entrypoint has a datatype that folds into multiple tables).
For more details, see the related PR: #44
v1.1.4: add mode for only applying migrations
Merge branch 'main' of github.com:tzConnectBerlin/que-pasa
v1.1.3: allow retrying seemingly non-transient errors (like 404, 500, 400)
1). Added a CLI argument (--node-comm-retries) that allows to define number of retries on any kind of node communication error (that is not transient like a rate limit error, those are already retried by default).
This is useful for when a node url is used where multiple nodes are behind, each may be at different block heights which can result in a 404 from time to time.
2). Fixed a query that potentially was very slow in a specific corner case: when bootstrapping a contract with --bcd-enable, and this contract was created a long time ago, and this contract has had barely any activity. New query is practically instant, also in this corner case.
v1.1.2: 2 fixes related to bootstrap
For details see this PR: #46
v1.1.1: improved db and node communication issues recovery
A few new features for increased que pasa resilience to node and database communication issues:
- Added application of a db pool library (r2d2), for managing retry on temporary connection issues logic.
- Added possibility to specify multiple node urls, the first one being primary, the subsequent ones being fallback nodes in case of non-recoverable issues with the primary node.
- Added curl code 56 to the list of transient node communication errors.
- Don't retry empty body responses, because this does not necessarily mean it's a temporary issue with the node. It can also be due to an incorrect specified contract address, which will never succeed. Instead, replaced this with checking the http status code, and retrying when it is a rate limit issue (http code 429)
Unfortunately, adding r2d2 mend that we lost the capability of connecting to the database with --ssl natively. As a replacement we've added a little script in script/ that applies stunnel. If ssl is required to connect to the database, this script should be called now which will setup an ssl tunnel. Then que pasa can simply target the local end of this tunnel without ssl.