dkuehr

diff --git a/Cargo.toml b/Cargo.toml
index dc67426..0a55f9d 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -8,6 +8,7 @@ license = "Apache-2.0"
 serde = { version = "1.0", features = ["derive"], optional = true }
 fuzzcheck = { git = "https://github.com/openmina/fuzzcheck-rs.git", optional = true }
 enum_dispatch = "0.3.7"
+psm = "0.1.21"

nholland94

max_zkapp_account_updates = 6
max_zkapp_txns_per_block = 128
max_txns_per_block = 128
max_txn_pool_size = 3000
k = 290
est_blocks = 3*k # 2*k for best tip path, k for duplicate block producers
est_scan_states = 2*k # k for best tip path, k for duplicate block producers

payment_txn_size = 3072-1968
zkapp_txn_size_max_cost = 235312

renatoalencar

FROM alpine

RUN apk add opam git musl-dev make m4 gcc bubblewrap bash coreutils pkgconfig openssl-libs-static openssl-dev
RUN opam init --disable-sandboxing
RUN opam install -y ocaml-base-compiler lambda-runtime dune

WORKDIR /app

COPY . .

nikeasyanzi

-- Thank @sbengo to figure out foreign_keys constraints is defaults to false in sqlite
-- Enable to delete logs by cascading delete
PRAGMA foreign_keys = ON;

WITH n_build_ids_per_repo as (
  SELECT build_id
  FROM (
    SELECT
      build_id,
      build_repo_id,

Kestrer

How to Write Hygienic Rust Macros

Macro hygiene is the concept of macros that work in all contexts; they don't affect and aren't affected by anything around them. Ideally all macros would be fully hygienic, but there are lots of pitfalls and traps that make it all too easy to accidentally write unhygienic macros. This guide attempts to provide a comprehensive resource for writing the most hygienic macros.

Understanding the Module System

First, a little aside on the details of Rust's module system, and specifically paths; it is

Raynos

/**
 * A PromiseLock like object.
 *
 * Used to ensure that we only do one thing at a time on a shared resource.
 *
 * For example, with async iterator:
 *
 * this.readLock = new Mutex()
 * this.readLock.do(async () => {
 *    const data = await itr.next();

eliseumds

export function serializeServerDataToJsonString(data: Object): string {
  const jsonString = JSON.stringify(data);

  return jsonString
    .replace(/<\/script/gim, '</_escaped_script')
    .replace(/<!--/gm, '\\u003C!--')
    .replace(new RegExp('\u2028', 'g'), '\\u2028')
    .replace(new RegExp('\u2029', 'g'), '\\u2029')
    .replace(/\\/g, '\\\\')
    .replace(/\n/g, '\\n')

david-zw-liu

-- Thank @sbengo to figure out foreign_keys constraints is defaults to false in sqlite
-- Enable to delete logs by cascading delete
PRAGMA foreign_keys = ON;

WITH n_build_ids_per_repo as (
  SELECT build_id
  FROM (
    SELECT
      build_id,
      build_repo_id,

dlaehnemann

Flamegraphing in Rust can now be done with a new cargo subcommand. Please check this out before embarking on the legacy journey below: https://github.com/flamegraph-rs/flamegraph

flamegraphing rust binaries' cpu usage with perf

One-time setup

1. Install perf, using Brendan Gregg's guide: http://www.brendangregg.com/perf.html#Prerequisites
2. Install flamegraph from repo:

bvaughn

// This is an advanced example! It is not typically required for application code.
// If you are using a library like Redux or MobX, use the container component provided by that library.
// If you are authoring such a library, use the technique shown below.

// This example shows how to safely update subscriptions in response to props changes.
// In this case, it is important to wait until `componentDidUpdate` before removing a subscription.
// In the event that a render is cancelled before being committed, this will prevent us from unsubscribing prematurely.

// We also need to be careful about how we handle events that are dispatched in between
// `getDerivedStateFromProps` and `componentDidUpdate` so that we don't put stale values into the `state`.