Attested computation (§10): wire bundles/acme_retail to a real runtime (BigQuery executor)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- csharp, google-cloud
- Domain
- backend-api-design, data-engineering
Research direction
Start by reading ROADMAP.md and the issue-mentioned OKF4net.Attestation.Containers, samples/attestation-containers-demo/, and samples/acme-retail-agent/. Trace how the demo runs a bundle computation and how the agent currently inspects bundles/acme_retail; identify the BigQuery execution path and how receipts are produced. Done means the agent runs those computations through a BigQuery executor and the receipt contains a real BigQuery job_id.
Written by the indexing model from the issue text.
Description
Extracted from ROADMAP.md (Later).
The container runtime exists. OKF4net.Attestation.Containers runs a bundle's sanctioned script or SQL, and its attester, in a real container, and samples/attestation-containers-demo/ drives it end to end.
What is missing is pointing it at bundles/acme_retail. Today samples/acme-retail-agent only inspects Attested Computation concepts (okf_get_computation); it never runs them (okf_run_computation).
A faithful run needs more than wiring:
- those computations target BigQuery, so they need a BigQuery executor;
- the receipt must carry a real
job_id.
That job_id is also what would make the provenance check meaningful. The demo's executed_sql is echoed back by our own wrapper, so it proves only what the wrapper sent.
- Dominant language
- C#
- Stars
- 4
- Forks
- 1
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 32
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from jchable/okf4net
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
.NET bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
test
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area/backend type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
umbraco/Umbraco-CMS#24668 · 1 comment ·
Maintainers usually reply within 1 day
-
Pri3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
MicrosoftDocs/windows-dev-docs#6205 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
area-ai untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
dotnet/extensions#7956 ·
Maintainers usually reply within 1 day