Block or Report
Block or report rphmeier
Report abuse
Contact GitHub support about this user’s behavior. Learn more about reporting abuse.
Report abusePinned
-
-
-
openethereum/parity-ethereum Public archive
The fast, light, and robust client for Ethereum-like networks.
-
912 contributions in the last year
Less
More
Activity overview
Contributed to
paritytech/polkadot,
paritytech/substrate,
paritytech/cumulus
and 5 other
repositories
Contribution activity
March 2022
Created 11 commits in 3 repositories
Created 1 repository
Created a pull request in paritytech/polkadot that received 21 comments
strengthen signals-received atomics
I think atomic races here could lead to a bug where messages could get stuck unprocessed for a few seconds. Or to bugs where messages are processed…
+5
−3
•
21
comments
Opened 16 other pull requests in 4 repositories
paritytech/polkadot
6
open
7
merged
- enable disputes on all chains
- Improve approval-distribution's usage of the grid topology.
- add a metric for report events in network bridge
- fix freshness calculations in statement distribution
- have some lenience on outdated messages in statement distribution
- make more subsystems blocking, fix blocking subsystem spawning
- Some small log improvements
- Prepare for network protocol version upgrades
- Check signatures as "Compact" in statement distribution
- Async Backing Statement Distribution
- Finish migration to v2 primitives
- Asynchronous Backing MegaPR
- Revert "req/resp: use IfDisconnected::ImmediateError (#4253)"
paritytech/cumulus
1
merged
w3f/staking-rewards-collector
1
closed
ordian/kuddelmuddel
1
merged
Reviewed 20 pull requests in 1 repository
paritytech/polkadot
20 pull requests
- Improve approval-distribution's usage of the grid topology.
- approval dist imrpo
- Extract MAX_FINALITY_LAG constant from relay_chain_selection
- track tof for inter subsystem messages
- provisioner logs minor janitor duties
- strengthen signals-received atomics
- Additional tracing in provisioner
- Collator protocol debug
- StatementDistributionMessage::get_metadata is a footgun and should be removed
- Rococo rm uneeded migrations, as network reset to "2.1"
- Update Rococo chainspec to v2_1
-
Add metrics timer for the
PerRequeststructure lifetime - Prospective Parachains Subsystem
- Prepare for network protocol version upgrades
- runtime/westend: add disputes
- Finish migration to v2 primitives
- Add babe randomness to well known keys
- Runtime changes for Asynchronous Backing
- Improve parachain liveness by reducing required number of backing votes
- dispute-distribution: downgrade a warn
Created an issue in paritytech/polkadot that received 4 comments
Collation request timeout too aggressive
polkadot/node/network/collator-protocol/src/validator_side/mod.rs Line 87 in c1a8115 We get quite a lot of logs in practice on Kusama va…
4
comments
Opened 13 other issues in 1 repository
paritytech/polkadot
11
open
2
closed
- Remove dummy dispute-coordinator implementation
- Optimize Approval-Distribution to more effectively use the grid topology
- Histogram tracking the amount of time inter-subsystem messages are in-flight
- Av-store may request validator set with wrong size at session boundaries
- Histogram metric for collator-protocol indicating collation fetch times and failures
- StatementDistributionMessage::get_metadata is a footgun and should be removed
- Collators don't clear connection requests until they produce another collation
- Update candidate-backing for asynchronous backing
- Update collation-generation for asynchronous backing
- Update statement-distribution for asynchronous backing
- Update collator-protocol for asynchronous backing
- Update provisioner for asynchronous backing
- Runtime API Subsystem should not do version negotiation internally
1
contribution
in private repositories
Mar 3