Skip to content

v0.2.5

Latest

Choose a tag to compare

@sshaplygin sshaplygin released this 09 Aug 22:32
· 6 commits to main since this release

All six crates released together at 0.2.5. The version is the workspace's, so they move as one.

Crate
ytsaurus-yson YSON codec, text and binary
ytsaurus-job job runtime
ytsaurus-client HTTP API v4 launcher
ytsaurus-helpers #[derive(TableRow)]first release
ytsaurus-skiff Skiff schema and codec — first release, pre-release
ytsaurus-format DataFormatfirst release, pre-release

ytsaurus-skiff and ytsaurus-format carried publish = false until now. They are on the registry because ytsaurus-job and ytsaurus-client depend on them and could not be published otherwise; the Skiff ship gates are still not all green and their API may change in a patch release.

What is in it

Making a managed installation runnable from the environment (#50) — nine issues found by running the whole example suite against a real multi-node cluster instead of a local Docker one.

  • Client::with_heavy_proxies_under(domains) — the configured address's domain plus the ones named. An installation that publishes its heavy proxies in a zone of its own had every one of them refused, and the only answers were writing all 79 names out or removing the rule.
  • Four new Client::from_env variablesYT_PROXY_SUFFIX, YT_HEAVY_PROXY_DOMAINS, YT_HEAVY_PROXIES_ANYWHERE, YT_FILE_CACHE — each inert when unset. Every example builds its client with from_env, so a policy settable only in Rust is a policy an example cannot be run under.
  • invalid peer certificate: UnknownIssuer now names the two things that fix it, YT_CA_BUNDLE and the platform-verifier feature.
  • Both /hosts refusals offer all three settings with their environment spellings, and name a domain that could not be used rather than dropping it in silence.
  • cached_upload brings its own file cache; profile builds its caption from the run and defaults to five rounds.
  • Docs: a runbook for a cluster that is not the local one, a full environment-variable table, --features tls for selfrun against https, and the decoding share recorded as open — 10.6 % on a local cluster against 36.2 % on a production one, either side of the 30 % threshold the Skiff question turns on.

Full detail in each crate's CHANGELOG.