q2: "remote code execution provider"
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 255
- Forks
- 17
- Avg merge
- 6h 20m
- Merged PRs (30d)
- 109
Description
Just like q2 preview can request execution from the q2 binary, q2 render could request execution from any remote server. This could be really useful for CI deployments that don't have all the available dependencies; it could be a thing that Workbench/Connect/Connect Cloud offers, etc etc.
Contributor 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.
Research direction
Start by reading how q2 preview requests execution from the q2 binary and how q2 render currently performs execution. Define the remote-server interface and the CI deployment use case described in the issue, including how Workbench, Connect, or Connect Cloud could provide it. Done means an agreed design and an implemented remote execution path, but the issue does not name files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cloud, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100