raulk
Follow
Create your own GitHub profile
Sign up for your own profile on GitHub, the best place to host code, manage projects, and build software alongside 50 million developers.
Sign up
Pinned
1,538 contributions in the last year
Activity overview
Contributed to
testground/testground,
filecoin-project/oni,
libp2p/go-libp2p
and 5 other
repositories
Contribution activity
August 2020
Created a pull request in filecoin-project/oni that received 6 comments
unified `tvx` tool; end-to-end MVP for extracting+running msg-class vectors
tvx is the test vector management tool. This PR contains a bunch of refactor, and it's an MVP of and end to end message-class vector extraction, an…
+3,265
−1
•
6
comments
- fix two disabled tests
- payment channel suite
- input from stdin functionality for `exec-lotus` ; initial test suites in ci
- generate test-vectors based on tests from chain-validation project
- parse multiple test cases per file /2
- unified `tvx` tool; end-to-end MVP for extracting+running msg-class vectors
Created an issue in filecoin-project/oni that received 1 comment
extract msg: apply preceding messages from the same sender included in the same tipset when populating prestate (edge case)
If tipset A includes message Z from sender S, it is possible that that tipset also includes preceding messages X and Y from sender S. If we extract…
1
comment
- templating API for message-class test vectors
- analyse and define schema for block sequence-class test vectors
- analyse and define schema for chain-class test vectors
- analyse and define schema for tipset-class test vectors
- analyse and define schema for block-class test vectors
- controlled randomness
- verification syscalls must be able to fail (VerifyPoSt, VerifySeal, VerifySignature)
- block-class test vectors: `miner` field on preconditions
- chainable DSL for message, block, tipset, chain building
- batch runner for test vector generation scripts
- chain validation port: cross-check if message builders are up to date
- deduplicate state trees in test vectors
- switch test vector state binary fields to gzip + base64; try brotli
- use Chainwatch and Sentinel to identify worthy real-life test vectors
- trim system actors state
- introduce block sequence test vector class
- port chain validation builders to spit out test vectors