Comments (3)
Our infrastructure is now running with our forks of bolero (for finite-wasm) and clusterfuzz, though the upstream PRs have not landed yet. So the non-aspirational part of the milestone is now complete :)
from nearcore.
Actually I just thought that I can use this to also use this issue to document the other stuff (outside of what’s listed here) I’ve worked on during August, so that it’s easier to find than in the zulip weekly sync meeting history only:
- Switched finite-wasm to using cargo-bolero on clusterfuzz
- Madrid offsite
- Hacked on zkwasm
- Enabled github merge queues on nearcore
- Worked on CI RTT, thought of our dual use of buildkite and GHA
- Thought about our security release process
- Discussed the best communication patterns with Hacken
from nearcore.
This is a cool idea. Maybe others in @near/contract-runtime might be interested in doing something similar as well.
from nearcore.
Related Issues (20)
- Improve split archival node migration
- Remove `is_chunk_producer_for_epoch` from EpochManagerAdapter
- Lychee lints CI check failing HOT 1
- [Forknet] Pre-release testing of resharding
- Remove pieces of code which index slices by shard id
- Remove witnesses which are no longer needed from OrphanStateWitnessPool
- Make size limit of orphan witnesses configurable
- Guidelines for handling unexpected errors HOT 4
- Statelessnet validator crashed because of `Option::unwrap()` on a `None` value HOT 7
- Make ChunkStateWitness a Tier1 network message HOT 4
- bugger
- Remove KeyValueRuntime
- Introduce receipt depth in broadcast_tx endpoint
- congestion-model: add new workload with peaks HOT 2
- congestion-model: new workload with transactions in uncongested shards HOT 1
- congestion-model: strategy with one outgoing buffer for each other shard HOT 3
- congestion-model: strategy with delayd receipts having priority over new transactions HOT 1
- Unable to compile `core/chain-configs/src/client_config.rs` HOT 1
- near-vm: the `LimitedMemoryPool` should allocate an appropriate number of memories for the maximum concurrency HOT 2
- [Documentation] Instructions in "Run a Node" page for local development inconsistent with near-cli
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from nearcore.