Maximilian Langenfeld
Maximilian Langenfeld
## Abstract The e.g. `GET /channels/` endpoint provides an endpoint for a set of all channels the node is connected to. It provides further filtering with `token` and `partner_address` URI...
During #7162 we discovered that the integration tests related to sending PFS-updates were flaky: https://app.circleci.com/pipelines/github/raiden-network/raiden/11997/workflows/db4fb64c-fe35-4a98-ab96-e4c53fb55802/jobs/197868/tests#failed-test-0 https://app.circleci.com/pipelines/github/raiden-network/raiden/12007/workflows/dd43e248-f81e-466c-955e-401a8727e876/jobs/198232/tests#failed-test-0 - here it seems like the apps have not queued up all expected PFS-updates...
Due to the inheritance model of the state-changes for mediated transfers there is quite some redundancy when initiating the "leaf" classes in the inheritance tree, e.g. `ActionInitMediator` or `ActionInitTarget`. Because...
## Meta-issue As users are developing against the Raiden API v1, they will have feature requests or might notice design-flaws of the current API. This meta-issue will be a place...
Since quite some time, the integration tests show logging errors of WebRTC / asyncio related task failures (e.g. [in this CI run](https://app.circleci.com/pipelines/github/raiden-network/raiden/10729/workflows/90d36dcd-7e96-4df1-9557-35433ccbce09/jobs/161377/parallel-runs/20/steps/20-108) ) This seems to happen in teardown of...
The reveal timeout is a node-local configuration parameter, that is firstly important to check the sanity of incoming transfers. **But this parameter is never communicated to our partner, the potential...
## Problem Definition We experienced some failing scenarios due to missing or slow broadcast messages (#6723, #6756, #2483). Investigation on the production transport servers showed http request times for the...
## Abstract The semantic of the 409 error code is different for different REST endpoints. This is fine as long as the error only represents one specific internal cause of...
The API specifications in the documentation don't seem to reflect the current status of the API properly: e.g. > > GET /api/1/channels doesn't return: > Example Response > 200 OK...
For µRaiden installation, also add the system wide dependencies for different OSes to the installation instruction. For reference, here is a working procedure to install µRaiden on a Raspberry Pi...