profile
viewpoint

raiden-network/raiden 1774

Raiden Network

ulope/django-reversetag 46

A new, improved (and renamed) implementation of Django's 'url' template tag.

raiden-network/workshop 25

Tools and instructions for Raiden workshops

raiden-network/spec 6

Spec of the Raiden Network protocol

raiden-network/raiden-service-bundle 4

Configuration and instructions for running the Raiden Service Bundle

ulope/django-careful-forms 3

Security minded forms extension for django

raiden-network/homebrew-raiden 2

Homebrew Tap for Raiden

ulope/django-snippets-collection 2

Some snippets from djangosnippets & co. that I like to use in some projects

ulope/django-stdimage 2

Fork of http://django-stdimage.googlecode.com/svn/trunk/

issue commentethereum/tests

EXTCODECOPY edge case

Many thanks.

chfast

comment created time in an hour

issue commentethereum/tests

EXTCODECOPY edge case

Solved by https://github.com/ethereum/tests/pull/761 and https://github.com/ethereum/tests/pull/765

chfast

comment created time in 2 hours

push eventethereum/tests

Ori Pomerantz

commit sha a7b0403a87da040f9864287251fe1c5589065fa3

Test for the source offset (in opcodes that have it) and length. Most of these fail only for negative length. RETURNDATACOPY is the exception - it has real bounds checking

view details

Ori Pomerantz

commit sha 5f2fcff621d866589afd04b2fb7905d219e5b803

Added a test for potential wraparound values (2^31, 2^32, 2^63, 2^64)

view details

winsvega

commit sha f700678ec364943ba8e66052742ae7b1e279c1ba

Merge pull request #765 from qbzzt/bufferSrcOffset Test for the source offset (in opcodes that have it) and length. Most…

view details

push time in 2 hours

PR merged ethereum/tests

Test for the source offset (in opcodes that have it) and length. Most…

… of these

fail only for negative length. RETURNDATACOPY is the exception - it has real bounds checking

+32558 -0

0 comment

3 changed files

qbzzt

pr closed time in 2 hours

push eventethereum/tests

Ori Pomerantz

commit sha efb78dbb57db9cb1183f460e5a2b6f91bb428800

The Solidity self destruct tests, as requested in https://github.com/ethereum/tests/issues/431 Note that selfdestruct(<contract's own address>) burns the balance.

view details

Ori Pomerantz

commit sha 294e7860a03e8539563673756ee4f14de740e2e0

Ran with --filltests and --fillchain, this commit contains both.

view details

winsvega

commit sha af987876ae7444f7316ba53103f86b7938b568ca

Merge pull request #764 from qbzzt/solidity_ff The Solidity self destruct tests, as requested in #431

view details

push time in 2 hours

PR merged ethereum/tests

The Solidity self destruct tests, as requested in https://github.com/…

…ethereum/tests/issues/431

Note that selfdestruct(<contract's own address>) burns the balance.

+1512 -0

2 comments

3 changed files

qbzzt

pr closed time in 2 hours

push eventethereum/tests

Ori Pomerantz

commit sha c341ab3874151de63bcfdff467507ab385ecf539

The buffer test

view details

Ori Pomerantz

commit sha eb9ac6b7c927f59b8890962387e69e719170f890

Added a REVERT test

view details

Ori Pomerantz

commit sha b0f2e3195324bb602e6623e4a6bc5f6499013bfd

Added the Blockchain/GeneralStateTests version

view details

Ori Pomerantz

commit sha d2720a9b9e55bf36824cf957a45c881ad93c0000

Added documentation to the meaning of each buffer type Ran with --fillchain as well as --filltest

view details

Ori Pomerantz

commit sha e850a9794be8c2261a27b5cc9e9fe428676ff776

Added test cases for 2^31-1, 2^31, 2^32-1, 2^32, 2^63-1, 2^63, 2^64-1, and 2^64 If the memory address is cast to a type with less bits (32 or 64, signed or unsigned), these test cases will fail.

view details

winsvega

commit sha cc5213a13e96e116fa792177e59ddbffe7227b16

Merge pull request #761 from qbzzt/buffer Buffer tests, argument extremums

view details

push time in 2 hours

PR merged ethereum/tests

Buffer tests

For every opcode with a buffer, check:

  1. That it is successful with buffer length 10
  2. That it is successful with buffer length 0
  3. That it fails with buffer length -10

Try this with different offsets, etc.

+115196 -0

3 comments

3 changed files

qbzzt

pr closed time in 2 hours

issue closedethereum/tests

Add selfdestruct test cases

Add these 3 test cases. They are HF independent, except for pricing. Use optimized runtime code from solidity.

pragma solidity ^0.4.21;

contract DoubleSelfdestructTest {

    address constant B1 = 0x1;
    address constant B2 = 0x2;

    function remoteSelfdestruct() external {
        selfdestruct(B2);
    }

    function() external payable {
        this.remoteSelfdestruct();
        selfdestruct(B1);
    }
}

contract DoubleSelfdestructTest2 {

    address constant B = 0x3;

    function remoteSelfdestruct() external {
        selfdestruct(this);
    }

    function() external payable {
        this.remoteSelfdestruct();
        selfdestruct(B);
    }
}

contract DoubleSelfdestructTest3 {

    function remoteSelfdestruct() external {
        selfdestruct(this);
    }

    function() external payable {
        this.remoteSelfdestruct();
        selfdestruct(this);
    }
}

closed time in 2 hours

chfast

issue closedethereum/tests

Use randomStatetest647 as basis for more RETURNDATACOPY tests

"randomStatetest647" : {
        "_info" : {
            "comment" : "Malicious bytecode found by fuzztest tool: returndatacopy(0,-1)"
        },

This is the only test that detects problems with RETURNDATACOPY in EVMJIT. We should have more tests like that and they should not be in "random" suite.

closed time in 2 hours

chfast

Pull request review commentethereum/tests

Buffer tests

 buffer:     - :label ok   :abi f(uint,uint) 0x3c 10   # Valid buffer length     - :label ok   :abi f(uint,uint) 0x3c 11   # Buffer length zero     - :label fail :abi f(uint,uint) 0x3c 12   # Negative buffer length+    - :label fail :abi f(uint,uint) 0x3c 20

i think this need coments too. 20/21/22 the meaning

qbzzt

comment created time in 3 hours

Pull request review commentethereum/aleth

Dynamic predicting of external IP and UDP port

+// Aleth: Ethereum C++ client, tools and libraries.+// Copyright 2019 Aleth Authors.+// Licensed under the GNU General Public License, Version 3.++#pragma once++#include "Common.h"++namespace dev+{+namespace p2p+{+// Class for keeping track of our external endpoint as seen by our peers.+// Keeps track of what external endpoint is seen by every peer+// and finds which endpoint is reported most often+class EndpointTracker+{+public:+    // Register the statement about endpoint from one of the peers.+    // Returns number of currently kept statements in favor of _externalEndpoint+    size_t addEndpointStatement(+        bi::udp::endpoint const& _sourceEndpoint, bi::udp::endpoint const& _externalEndpoint);++    // Find endpoint with max number of statements+    bi::udp::endpoint bestEndpoint() const;++    // Remove statements older than _timeToLive+    void garbageCollectStatements(std::chrono::seconds const& _timeToLive);++private:+    using EndpointAndTimePoint =+        std::pair<bi::udp::endpoint, std::chrono::steady_clock::time_point>;+    using SourceToStatementMap = std::map<bi::udp::endpoint, EndpointAndTimePoint>;

Resurrecting this from the dead, just to say that I'm surprised that boostorg/asio#245 got no responses so far. We have been carrying custom hashing support for these types in rippled so it's been "out of sight, out of mind" for our codebase, but this really is something that boost should provide.

I'm happy to have Ripple sponsor a bounty to get the supported coded up, or to do it myself if nobody else is interested.

gumb0

comment created time in 17 hours

issue commentethereum/tests

Use randomStatetest647 as basis for more RETURNDATACOPY tests

Also https://github.com/ethereum/tests/pull/765

chfast

comment created time in a day

PR opened ethereum/tests

Test for the source offset (in opcodes that have it) and length. Most…

… of these

fail only for negative length. RETURNDATACOPY is the exception - it has real bounds checking

+21758 -0

0 comment

3 changed files

pr created time in a day

pull request commentethereum/tests

The Solidity self destruct tests, as requested in https://github.com/…

have you traced with --vmtrace that execution goes well ?

Now I have. I didn't go opcode by opcode, but I used grep to see the SELFDESTRUCT opcodes and every test case has two of them with the correct address in the top of the stack:

selfdestructs.txt

qbzzt

comment created time in a day

Pull request review commentethereum/tests

Buffer tests

+# Check what happens with weird buffer lengths, 0 or negative.++buffer:++  env:+    currentCoinbase: 2adc25665018aa1fe0e6bc666dac8fc2697ff9ba+    currentDifficulty: 0x20000+    currentGasLimit: 100000000+    currentNumber: 1+    currentTimestamp: 1000+    previousHash: 5e20a0453cecd065ea59c37ac63e079ee08998b6045136a8ce6635c7912ec0b6++  _info:+    comment: Ori Pomerantz qbzzt1@gmail.com++  pre:++    000000000000000000000000000000000000c0de:+      balance: '0x0ba1a9ce0ba1a9ce'+      code: |+        {+              (return 0 0x120)+        }+      nonce: 0+      storage: {}++    # To check return. If it reverts the goat survives+    000000000000000000000000000000000f30c0de:+      balance: '0x0ba1a9ce0ba1a9ce'+      code: |+        {+               ; We get length from the caller+               (def 'length $0)+               (def 'offset $0x20)++               [[0]] 0    ; capricide+               (return offset length) +        }+      nonce: 0+      storage:+        0: 0x60A7+++    # To check revert.+    000000000000000000000000000000000ff0c0de:+      balance: '0x0ba1a9ce0ba1a9ce'+      code: |+        {+               ; We get length from the caller+               (def 'length $0)+               (def 'offset $0x20)++               (revert offset length) +        }+      nonce: 0+      storage: {}++++    cccccccccccccccccccccccccccccccccccccccc:+      balance: '0x0ba1a9ce0ba1a9ce'+      code: |+        {+           (def 'opcode $4)+           (def 'bufferType $36)+           (def 'NOP 0)++           ; Variables           +           (def 'length     0x20)+           (def 'offset     0x40)+         +           ; bufferType 0 is normal, 1 is length zero, 2 is negative length+           ; bufferType 3 is excessively long, for opcodes with bounds checking+           ; Add 0 for offset 0x100, 10 for offset 0x0+           (if (= bufferType 0) {+                   [length] 10+                   [offset] 0x100+             } NOP)+           (if (= bufferType 1) {+                   [length] 0 +                   [offset] 0x100+             } NOP)+           (if (= bufferType 2) {+                   [length] (- 0 10) +                   [offset] 0x100+             } NOP)+           (if (= bufferType 3) { +                   [length] 0x1000 +                   [offset] 0x100+             } NOP)+           (if (= bufferType 10) {+                   [length] 10+                   [offset] 0x0+             } NOP)+           (if (= bufferType 11) {+                   [length] 0 +                   [offset] 0x0+             } NOP)+           (if (= bufferType 12) {+                   [length] (- 0 10) +                   [offset] 0x0+             } NOP)+           (if (= bufferType 13) { +                   [length] 0x1000 +                   [offset] 0x0+             } NOP)+           ; bufferType 20 is offset 2^256-10, length 5+           ; this causes an out of gas error because the gas cost+           ; is around 2^251 (memory is priced in 32 byte chunks)+           (if (= bufferType 20) { +                   [length] 5+                   [offset] (- 0 10)+             } NOP)++           (if (= opcode 0x20) (sha3 @offset @length) NOP)+           (if (= opcode 0x37) (calldatacopy @offset 0 @length) NOP)+           (if (= opcode 0x39) (codecopy @offset 0 @length) NOP)+           (if (= opcode 0x3C) (extcodecopy 0xc0de @offset 0 @length) NOP)+           (if (= opcode 0x3E) (returndatacopy @offset 0 @length) NOP)+           (if (= opcode 0xA0) (log0 @offset @length) NOP)+           (if (= opcode 0xA1) (log1 @offset @length 1) NOP)+           (if (= opcode 0xA2) (log2 @offset @length 1 2) NOP)+           (if (= opcode 0xA3) (log3 @offset @length 1 2 3) NOP)+           (if (= opcode 0xA4) (log4 @offset @length 1 2 3 4) NOP)+           (if (= opcode 0xF0) (create 0 @offset @length) NOP)+           (if (= opcode 0xF1)  (call 0x1000 0xc0de 0 @offset @length 0 0) NOP)+           (if (= opcode 0x1F1) (call 0x1000 0xc0de 0 0 0 @offset @length) NOP)+           (if (= opcode 0xF2)  (callcode 0x1000 0xc0de 0 @offset @length 0 0) NOP)+           (if (= opcode 0x1F2) (callcode 0x1000 0xc0de 0 0 0 @offset @length) NOP)+           (if (= opcode 0xF4)  (delegatecall 0x100000 0xc0de @offset @length 0 0) NOP)+           (if (= opcode 0x1F4) (delegatecall 0x100000 0xc0de 0 0 @offset @length) NOP)+           (if (= opcode 0xF5) (create2 0 @offset @length 0x5A17) NOP)+           (if (= opcode 0xFA)  (staticcall 0x100000 0xc0de @offset @length 0 0) NOP)+           (if (= opcode 0x1FA) (staticcall 0x100000 0xc0de 0 0 @offset @length) NOP)++           ; RETURNDATACOPY, after making sure there is return data+           (if (= opcode 0x13E) {+               (call 0x1000 0xc0de 0 0 0 0x100 0x100)+               (returndatacopy @offset 0 @length) +           } NOP)++           ; check return, requires special handling+           (if (= opcode 0xF3)  (call 0x100000 0xf30c0de 0 length 0x40 0 0) NOP)+++           ; check revert, requires special handling+           (if (= opcode 0xFF)  {+              (call 0x100000 0xff0c0de 0 length 0x40 0 0)+              [[0]] (returndatasize)+           } NOP)++           ; Kill the goat+           [[0x100]] 0+        }+      nonce: '0'+      storage:+        # Sacrificial goat to tell reverts apart from successes+        0x100: 0x60A7+++    a94f5374fce5edbc8e2a8697c15331677e6ebf0b:+      balance: '0x0ba1a9ce0ba1a9ce'+      code: '0x'+      nonce: '0'+      storage: {}+      +  transaction:+    data:+    # SHA3       +    - :label ok   :abi f(uint,uint) 0x20 0   # Valid buffer length

Sorry, the last one was supposed to be 13. I fixed the comment.

qbzzt

comment created time in a day

pull request commentethereum/tests

The Solidity self destruct tests, as requested in https://github.com/…

have you traced with --vmtrace that execution goes well ?

qbzzt

comment created time in a day

Pull request review commentethereum/tests

Buffer tests

+# Check what happens with weird buffer lengths, 0 or negative.++buffer:++  env:+    currentCoinbase: 2adc25665018aa1fe0e6bc666dac8fc2697ff9ba+    currentDifficulty: 0x20000+    currentGasLimit: 100000000+    currentNumber: 1+    currentTimestamp: 1000+    previousHash: 5e20a0453cecd065ea59c37ac63e079ee08998b6045136a8ce6635c7912ec0b6++  _info:+    comment: Ori Pomerantz qbzzt1@gmail.com++  pre:++    000000000000000000000000000000000000c0de:+      balance: '0x0ba1a9ce0ba1a9ce'+      code: |+        {+              (return 0 0x120)+        }+      nonce: 0+      storage: {}++    # To check return. If it reverts the goat survives+    000000000000000000000000000000000f30c0de:+      balance: '0x0ba1a9ce0ba1a9ce'+      code: |+        {+               ; We get length from the caller+               (def 'length $0)+               (def 'offset $0x20)++               [[0]] 0    ; capricide+               (return offset length) +        }+      nonce: 0+      storage:+        0: 0x60A7+++    # To check revert.+    000000000000000000000000000000000ff0c0de:+      balance: '0x0ba1a9ce0ba1a9ce'+      code: |+        {+               ; We get length from the caller+               (def 'length $0)+               (def 'offset $0x20)++               (revert offset length) +        }+      nonce: 0+      storage: {}++++    cccccccccccccccccccccccccccccccccccccccc:+      balance: '0x0ba1a9ce0ba1a9ce'+      code: |+        {+           (def 'opcode $4)+           (def 'bufferType $36)+           (def 'NOP 0)++           ; Variables           +           (def 'length     0x20)+           (def 'offset     0x40)+         +           ; bufferType 0 is normal, 1 is length zero, 2 is negative length+           ; bufferType 3 is excessively long, for opcodes with bounds checking+           ; Add 0 for offset 0x100, 10 for offset 0x0+           (if (= bufferType 0) {+                   [length] 10+                   [offset] 0x100+             } NOP)+           (if (= bufferType 1) {+                   [length] 0 +                   [offset] 0x100+             } NOP)+           (if (= bufferType 2) {+                   [length] (- 0 10) +                   [offset] 0x100+             } NOP)+           (if (= bufferType 3) { +                   [length] 0x1000 +                   [offset] 0x100+             } NOP)+           (if (= bufferType 10) {+                   [length] 10+                   [offset] 0x0+             } NOP)+           (if (= bufferType 11) {+                   [length] 0 +                   [offset] 0x0+             } NOP)+           (if (= bufferType 12) {+                   [length] (- 0 10) +                   [offset] 0x0+             } NOP)+           (if (= bufferType 13) { +                   [length] 0x1000 +                   [offset] 0x0+             } NOP)+           ; bufferType 20 is offset 2^256-10, length 5+           ; this causes an out of gas error because the gas cost+           ; is around 2^251 (memory is priced in 32 byte chunks)+           (if (= bufferType 20) { +                   [length] 5+                   [offset] (- 0 10)+             } NOP)++           (if (= opcode 0x20) (sha3 @offset @length) NOP)+           (if (= opcode 0x37) (calldatacopy @offset 0 @length) NOP)+           (if (= opcode 0x39) (codecopy @offset 0 @length) NOP)+           (if (= opcode 0x3C) (extcodecopy 0xc0de @offset 0 @length) NOP)+           (if (= opcode 0x3E) (returndatacopy @offset 0 @length) NOP)+           (if (= opcode 0xA0) (log0 @offset @length) NOP)+           (if (= opcode 0xA1) (log1 @offset @length 1) NOP)+           (if (= opcode 0xA2) (log2 @offset @length 1 2) NOP)+           (if (= opcode 0xA3) (log3 @offset @length 1 2 3) NOP)+           (if (= opcode 0xA4) (log4 @offset @length 1 2 3 4) NOP)+           (if (= opcode 0xF0) (create 0 @offset @length) NOP)+           (if (= opcode 0xF1)  (call 0x1000 0xc0de 0 @offset @length 0 0) NOP)+           (if (= opcode 0x1F1) (call 0x1000 0xc0de 0 0 0 @offset @length) NOP)+           (if (= opcode 0xF2)  (callcode 0x1000 0xc0de 0 @offset @length 0 0) NOP)+           (if (= opcode 0x1F2) (callcode 0x1000 0xc0de 0 0 0 @offset @length) NOP)+           (if (= opcode 0xF4)  (delegatecall 0x100000 0xc0de @offset @length 0 0) NOP)+           (if (= opcode 0x1F4) (delegatecall 0x100000 0xc0de 0 0 @offset @length) NOP)+           (if (= opcode 0xF5) (create2 0 @offset @length 0x5A17) NOP)+           (if (= opcode 0xFA)  (staticcall 0x100000 0xc0de @offset @length 0 0) NOP)+           (if (= opcode 0x1FA) (staticcall 0x100000 0xc0de 0 0 @offset @length) NOP)++           ; RETURNDATACOPY, after making sure there is return data+           (if (= opcode 0x13E) {+               (call 0x1000 0xc0de 0 0 0 0x100 0x100)+               (returndatacopy @offset 0 @length) +           } NOP)++           ; check return, requires special handling+           (if (= opcode 0xF3)  (call 0x100000 0xf30c0de 0 length 0x40 0 0) NOP)+++           ; check revert, requires special handling+           (if (= opcode 0xFF)  {+              (call 0x100000 0xff0c0de 0 length 0x40 0 0)+              [[0]] (returndatasize)+           } NOP)++           ; Kill the goat+           [[0x100]] 0+        }+      nonce: '0'+      storage:+        # Sacrificial goat to tell reverts apart from successes+        0x100: 0x60A7+++    a94f5374fce5edbc8e2a8697c15331677e6ebf0b:+      balance: '0x0ba1a9ce0ba1a9ce'+      code: '0x'+      nonce: '0'+      storage: {}+      +  transaction:+    data:+    # SHA3       +    - :label ok   :abi f(uint,uint) 0x20 0   # Valid buffer length

what is the meaning of 0 1 2 10 11 12 12 ?

qbzzt

comment created time in a day

startedulope/pyformat.info

started time in a day

issue commentethereum/tests

Add selfdestruct test cases

Solves the PR https://github.com/ethereum/tests/pull/764

chfast

comment created time in 2 days

PR opened ethereum/tests

The Solidity self destruct tests, as requested in https://github.com/…

…ethereum/tests/issues/431

Note that selfdestruct(<contract's own address>) burns the balance.

+382 -0

0 comment

2 changed files

pr created time in 2 days

issue openedethereum/tests

The recent tests changes

The recent tests changes: The Berlin tests

EIP2929 (https://eips.ethereum.org/EIPS/eip-2929) PR https://github.com/ethereum/tests/pull/760 PR https://github.com/ethereum/tests/pull/756

EIP2537 (https://eips.ethereum.org/EIPS/eip-2537) PR https://github.com/ethereum/tests/pull/713

created time in 2 days

issue commentethereum/tests

Berlin ModExp tests need YOLOv3 update

https://github.com/hyperledger/besu/issues/1611

shemnon

comment created time in 2 days

issue openedraiden-network/raiden

Is the correct participant doing the unlock?

@mauricioirace in gitter:

Let's assume we have a channel between A and B. There is a locked amount of X tokens from A to B, and the secret has been registered on chain. What the documentation says is that after the channel has been settled, B will unlock the tokens on chain, and they we'll be transferred to it But debugging the code we note that A is the one which calls the unlock method of the contract, instead of B (granting the tokens to B, anyway). Indeed, we saw that both restore the channel_state to an state when the secret was not yet registered, forcing A and B to think B cannot claim the tokens (What it actually can). Is this correct or we're missing something? Is that the expected behaviour?

To have nodes act to their on benefit, I would expect the following behavior:

  • When the secret is registered on-chain, the receiver (B) should call unlock
  • When the secret is not registered, the locked amount can be reclaimed by the sender (A), so the sender should call unlock

We have tests checking that the unlocks happen, but I could not find a check which node calls the unlock. So we might miss cases where the wrong node calls unlock.

created time in 2 days

issue commentraiden-network/explorer

Show node status

We might also want to think about extending the PFS to provide the data required.

My thinking is that the explorer backend is kind of an old version of the PFS, and most of the stuff we implement now is already implemented in the PFS. Adding the required API endpoint would allow us to get rid of the extra codebase for the explorer backend.

palango

comment created time in 2 days

issue openedraiden-network/raiden

Nightly builds failing

See https://app.circleci.com/pipelines/github/raiden-network/raiden/10458/workflows/e6c73aec-de67-4911-ae01-6158e3ac704f/jobs/156348

created time in 2 days

push eventraiden-network/explorer

manuelwedler

commit sha d712c37f2afa6b1fab27a8d262435ad1054e7519

frontend: Fix network visualization when there are channels without nodes

view details

manuelwedler

commit sha 2f7b174435365b2009d5a50167a8e57ab2482056

Downgrade to zone.js 0.10.3

view details

manuelwedler

commit sha 7795729b13a7a306b5998661962adc4691a6deec

Update Angular to v11

view details

manuelwedler

commit sha e41299483ccb3ed62edc4f2d77eb47c7ce7e3545

Update Angular Material to v11

view details

manuelwedler

commit sha 9624ebb9fc2d8295cb35c40d7ed55ec6c95cd344

Add tsconfig option to ngcc postinstall script

view details

Renovate Bot

commit sha 356921f3b2c69ab57e85d2c3a74d654fcdb624b5

dependencies: Pin dependencies

view details

push time in 2 days

push eventraiden-network/explorer

manuelwedler

commit sha 2f7b174435365b2009d5a50167a8e57ab2482056

Downgrade to zone.js 0.10.3

view details

manuelwedler

commit sha 7795729b13a7a306b5998661962adc4691a6deec

Update Angular to v11

view details

manuelwedler

commit sha e41299483ccb3ed62edc4f2d77eb47c7ce7e3545

Update Angular Material to v11

view details

manuelwedler

commit sha 9624ebb9fc2d8295cb35c40d7ed55ec6c95cd344

Add tsconfig option to ngcc postinstall script

view details

push time in 2 days

PR merged raiden-network/explorer

Update Angular to v11

just updates to the latest Angular. Somehow the Angular CLI does not accept the newest zone.js version.

Something in the typing of the DecimalPipe changed. I could not fix it, so I added a ts-ignore to our deriving class SmallNumberPipe.

+284 -686

0 comment

18 changed files

manuelwedler

pr closed time in 2 days

pull request commentethereum/py_ecc

Setup towncrier to generate release notes

@pipermerriam Should I create a docs/index.rst file similar to what's present in other repos? If so, what introduction/description/quickstart information should I include? Also for docs/release_notes.rst, I put v0.1.0-alpha.1 as the first version. Is this okay?

tmckenzie51

comment created time in 3 days

more