5 Commits (appveyorfix)

Author	SHA1	Message	Date
willian.eth	52ed3570c4	cmd: migrate to urfave/cli/v2 (#24751) ... This change updates our urfave/cli dependency to the v2 branch of the library. There are some Go API changes in cli v2: - Flag values can now be accessed using the methods ctx.Bool, ctx.Int, ctx.String, ... regardless of whether the flag is 'local' or 'global'. - v2 has built-in support for flag categories. Our home-grown category system is removed and the categories of flags are assigned as part of the flag definition. For users, there is only one observable difference with cli v2: flags must now strictly appear before regular arguments. For example, the following command is now invalid: geth account import mykey.json --password file.txt Instead, the command must be invoked as follows: geth account import --password file.txt mykey.json	2 years ago
Felix Lange	9244d5cd61	all: update license headers and AUTHORS from git history (#24947)	3 years ago
Felix Lange	5d20fbbb6f	cmd/devp2p, internal/utesting: implement TAP output (#21760) ... TAP is a text format for test results. Parsers for it are available in many languages, making it easy to consume. I want TAP output from our protocol tests because the Hive wrapper around them needs to know about the test names and their individual results and logs. It would also be possible to just write this info as JSON, but I don't want to invent a new format. This also improves the normal console output for tests (when running without --tap). It now prints -- RUN lines before any output from the test, and indents the log output by one space.	4 years ago
Felix Lange	524aaf5ec6	p2p/discover: implement v5.1 wire protocol (#21647) ... This change implements the Discovery v5.1 wire protocol and also adds an interactive test suite for this protocol.	4 years ago
Felix Lange	b7394d7942	p2p/discover: add initial discovery v5 implementation (#20750) ... This adds an implementation of the current discovery v5 spec. There is full integration with cmd/devp2p and enode.Iterator in this version. In theory we could enable the new protocol as a replacement of discovery v4 at any time. In practice, there will likely be a few more changes to the spec and implementation before this can happen.	5 years ago