these 4 derivations will be built:
  /nix/store/35lxnrk6khirdrzyzgzsshv5rdrwmr8x-omnigraph-server-wait-ready.drv
  /nix/store/4ikab5d6iqqdn7yc4fx8zv0ilgynai0w-omnigraph-server-wait-ready.drv
  /nix/store/mjrr3c31p4l4ycqy3i76z7xwdpbml220-omnigraph-server-wait-ready.drv
  /nix/store/y6pgbcr90bmff36g7jc0xinrxid1xjq8-omnigraph-readiness-rehearsal.drv
this path will be fetched (0.0 KiB download, 1.1 KiB unpacked):
  /nix/store/x4fwz14gnllclf9pa32m4241329d4dl0-readyz-stub.py
building '/nix/store/35lxnrk6khirdrzyzgzsshv5rdrwmr8x-omnigraph-server-wait-ready.drv'
building '/nix/store/4ikab5d6iqqdn7yc4fx8zv0ilgynai0w-omnigraph-server-wait-ready.drv'
building '/nix/store/mjrr3c31p4l4ycqy3i76z7xwdpbml220-omnigraph-server-wait-ready.drv'
omnigraph-server-wait-ready> structuredAttrs is enabled
omnigraph-server-wait-ready> structuredAttrs is enabled
omnigraph-server-wait-ready> structuredAttrs is enabled
building '/nix/store/y6pgbcr90bmff36g7jc0xinrxid1xjq8-omnigraph-readiness-rehearsal.drv'
omnigraph-readiness-rehearsal> --- dead MAINPID fails fast without polling
omnigraph-readiness-rehearsal> omnigraph-server exited during startup before serving; see `journalctl -u omnigraph-server`. A fresh or never-applied storage root needs `systemctl restart omnigraph-cluster-apply` (or the bootstrap unit) before the server can start.
omnigraph-readiness-rehearsal> elapsed 0s, requests: 0
omnigraph-readiness-rehearsal> --- served equals expected with a live MAINPID is ready
omnigraph-readiness-rehearsal> elapsed 0s, requests: 1
omnigraph-readiness-rehearsal> --- served below expected fails fast
omnigraph-readiness-rehearsal> omnigraph-server serves 1 of 2 declared graphs. Graphs are opened only at startup, so waiting will not help: run `systemctl restart omnigraph-cluster-apply` (or the bootstrap unit) to apply them, then restart omnigraph-server.
omnigraph-readiness-rehearsal> elapsed 0s, requests: 1
omnigraph-readiness-rehearsal> --- a quarantined graph fails fast
omnigraph-readiness-rehearsal> omnigraph-server quarantined 1 graph(s) during startup and will not serve them until it restarts; see `journalctl -u omnigraph-server` ('graph quarantined during startup' lines) and `omnigraph-cluster status`.
omnigraph-readiness-rehearsal> elapsed 0s, requests: 1
omnigraph-readiness-rehearsal> --- no expected count accepts zero served graphs
omnigraph-readiness-rehearsal> elapsed 0s, requests: 1
omnigraph-readiness-rehearsal> --- 503 then 200 is transient
omnigraph-readiness-rehearsal> elapsed 4s, requests: 3
omnigraph-readiness-rehearsal> --- 200 that is not a readiness report fails fast
omnigraph-readiness-rehearsal> omnigraph-server answered http://omnigraph.rehearsal.invalid:8090/readyz with a body that is not a readiness report: {}
omnigraph-readiness-rehearsal> elapsed 0s, requests: 1
omnigraph-readiness-rehearsal> --- 200 with ready false keeps polling, then times out
omnigraph-readiness-rehearsal> omnigraph-server did not answer http://omnigraph.rehearsal.invalid:8090/readyz within 3 seconds
omnigraph-readiness-rehearsal> elapsed 4s, requests: 4
omnigraph-readiness-rehearsal> --- never ready within the timeout fails with the timeout message
omnigraph-readiness-rehearsal> omnigraph-server did not answer http://omnigraph.rehearsal.invalid:8090/readyz within 3 seconds
omnigraph-readiness-rehearsal> curl: (22) The requested URL returned error: 503
omnigraph-readiness-rehearsal> elapsed 4s, requests: 4

upload niks3: ok