This diff upgrades the probe-engine dependency to the last published
commit, which allows us to...

See https://github.com/ooni/probe/issues/2505.

Noticed while working on https://github.com/ooni/probe/issues/2502

Part of https://github.com/ooni/probe/issues/2502

By making it explicit that we want to include the HTTP body into a
measurement we highlight tha...

Required by https://github.com/ooni/probe/issues/2502

This diff deals the fallback from
https://github.com/ooni/probe-cli/pull/1168 and is related to...

This change simplifies writing filters and possibly makes the ErrSkip
functionality redundant b...

Otherwise, it indents too much to the right and it's unreadable.

Part of https://github.com/oon...

Part of https://github.com/ooni/probe/issues/2494

This commit removes the code we used as milestones to reach the
stage where we implemented the p...

This diff improves the DSL for writing nettests introduced in
https://github.com/ooni/2023-05-r...

This diff commits work in progress where we've refactored unruntime to
use explicit types, which...

Part of https://github.com/ooni/probe/issues/2494

Part of https://github.com/ooni/probe/issues/2494

This pull request redesigns the composable mini-nettests implementation
as follows:

1. *Laye...

Part of https://github.com/ooni/probe/issues/2493

This change is fundamental to ensuring we can provide conditional
support for options implemente...

While there, remove the previous implementation of the better DSL (./pkg/x/dslx)
because it has ...

Part of https://github.com/ooni/probe/issues/2494

This diff improves upon #1 to provide a better implementation of mini
nettests. The reference i...

Part of https://github.com/ooni/probe/issues/2494

This commit adds convenience python scripts that generically
manipulate the check-in response.

...

This diff implements max-runtime for the `runx` subcommand
and fixes all the bugs discovered whi...

This is probably poised to change in a later iteration of this
specification, but there is no ne...

As we did in the previous commit, clarify what we're running
and what is the type of the arguments.

This diff changes the syntax of the script to explicitly clarify
we're running a command with th...

It seems the "command" term is a better term to use considering
that we're dealing with a script...

This diff solves another issue that we identified during the
v0.1.0 design review with @Federico...

The interface describes the way in which the interpreter interfaces
with the view, so its name s...

That interface is the interpreter's specific view of how to save
measurements rather than a more...

This diff modifies the runner to implement location invalidation
as discussed in the DESIGN.md d...

This diff implements what we agreed to do with @FedericoCeratto
during the design review of the ...

The runner is responsible of running nettests. The interpreter
is the core type of the runner in...

This change addresses one of the TODOs we identified during the
previous design review with @Fed...

Writing

```JSONC
{
"run": "foo:bar"
}
```

stutters when compared to

```JSONC
{
"run": "fo...

With @FedericoCeratto we determined that we want to have
a global configuration rather than per-...

This change clarifies that what we consider settings are actually
the interpreter specific view ...

The interpreter now updates view parameters and the view
periodically refreshes and writes the s...

When you only run a single nettest within a suite and the nettest
is not the last, you still wan...

While there, make sure we use more accurate names to describe
the actions we're telling the inte...

By binding this kind of instructions to a suite, we can ignore all the
messages we don't care ab...

Use the same consistent naming pattern for all instructions.

The view will need to keep state for updating the progress bar and the
interpreter will forward ...

The https://github.com/ooni/probe/issues/2381 issue advocates for each
experiment _fetching_ its...

* https://github.com/ooni/ooni.org/issues/1291;
* https://github.com/ooni/ooni.org/issues/1292;
...

Based on a conversation with @hellais.

Based on feedback from @hellais

We said the file is written by the user. If so, the explanation cannot mention the check-in API....