tomaka
Follow
tomaka
Follow
Highlights
- Pro
Pinned
3,029 contributions in the last year
Activity overview
Contributed to
paritytech/smoldot,
paritytech/substrate-connect,
paritytech/json-rpc-interface-spec
and 31 other
repositories
Contribution activity
June 2022
Created 57 commits in 4 repositories
Created 1 repository
- tomaka/api TypeScript
Created a pull request in paritytech/smoldot that received 12 comments
Add fake out requests system in peers.rs
Fix #2361
This PR solves a tricky problem in peers.rs.
A connection can be in three phases: handshaking, established, or shutting down (and, later,…
+117
−38
•
12
comments
Opened 52 other pull requests in 3 repositories
paritytech/smoldot
38
merged
2
open
- Print the request ID on error in a JSON-RPC call
- Clarify parameter index in error messages
- Only use database if it's more recent than checkpoint
- Properly save justifications and GrandPa commits for later
- Reduce algorithmic complexity of verifying commits and justifications
- Update Rococo chain spec
- Differentiate errors during handshake phases
- Rename "Disjoint" to "StoredForLater"
- Use block in handshake to initialize network_known_best
- Publish v0.6.19
- Fix panic with unpinning pruned blocks
- Update Rust to v1.61
- Publish v0.6.18
- Remove obsolete comment in service.rs
- DRY in RequestsSubscriptions::add_client
- Fix missing PR number in CHANGELOG
- Add support for state_call JSON-RPC function
- Change max number of pinned blocks to max number of finalized pinned blocks
- Add experimental WebRTC support to multiaddr
- Fix OptimisticSync::remove_source not removing obsolete requests
- Update README content regarding Wasm demo
- Accept relayChain and paraId as alternative spellings
- Add experimental warning at full node initialization
- Improve full node error message when JSON-RPC port is already busy
- Add Acala and Karura to the chain specs list
- Some pull requests not shown.
paritytech/substrate-connect
11
merged
- It's not null but undefined
- Fix calls to chainHead_unstable_unpin again
- Fix missing parameter when calling chainHead_unstable_header
- Fix deploy script
- Fix error about unpinning null block
- Fixes to the changelog
- Last block -> Latest block
- Slim down Rococo chain spec
- Update smoldot to version 0.6.19
- Fix messages from the extension being potentially missed
- Add the latest block height to the chain information provided by the manager
polkadot-js/api
1
merged
Reviewed 29 pull requests in 3 repositories
paritytech/substrate-connect
17 pull requests
- Extension bump to 0.1.7
- remove non-used variables that was resulting to warnings
- Update Landing Page
- Bump versions (Substrate connect to 0.7.7, Extension to 0.1.6)
- Apply name and email in deploy script
- add dependencies in extension
- Update checkpoints in chain specifications
- Bump versions
- minor fixes in deploy script and demo app
- Fix messages from the extension being potentially missed
- Fix 'invalidated context' bug
- Update checkpoints in chain specifications
- Add bootnodes in localstorage
- Alter Options page based on Figma
- improve info about chainspecs on landing page
- Fix bugs on popup
- Alter manifest for more icons in extension
paritytech/smoldot
8 pull requests
- Rename "Disjoint" to "StoredForLater"
- CI: fix spellcheck
- Fix panic with unpinning pruned blocks
- Add support for "multi-stream connections"
- Add fake out requests system in peers.rs
- Allow forcing backend with ExecHint
- Improve Display implementation of most errors
- Properly log the block requests in the full node
paritytech/substrate
4 pull requests
Created an issue in paritytech/smoldot that received 2 comments
Flood of chainHead_unstable_follow notifications
Something I've noticed on substrate-connect:
Substrate-connect subscribes to chainHead_unstable_follow, then smoldot immediately sends back a resp…
2
comments
Opened 9 other issues in 2 repositories
paritytech/smoldot
5
closed
3
open
- Failed to verify warp sync fragment on Rococo
- Infinite loop in GrandPa warp syncing
- Internet connectivity and finality gap
- Spellcheck CI step doesn't fail even if there are spelling mistakes
- Consider adding a "shutting down" phase in the API of peers.rs
- Add ExecHint::ForceWasmtime and ForceWasmi for testing purposes
- Panic in decode_block_request
- Panic when decoding header