Summary

stdweb is unmaintained

The author of the stdweb crate is unresponsive.

Maintained alternatives:

• wasm-bindgen
• js-sys
• web-sys

See advisory page for additional details.

cpuid-bool has been renamed to cpufeatures

Please use the `cpufeatures`` crate going forward:

<https://github.com/RustCrypto/utils/tree/master/cpufeatures>

There will be no further releases of cpuid-bool.

See advisory page for additional details.

Be able to re-use receipts for incremental computation within a workflow.

ETA: 2023-08-15

In the current proof of concept, we only have support for i32s. This needs to be generalized to a much broader set of types, at least those available in IPLD. This both needs a clear ABI (e.g. C conventions) and/or support for the Wasm component model & WIT.

mach is unmaintained

Last release was almost 4 years ago.

Maintainer(s) seem to be completely unreachable.

Possible Alternative(s)

These may or may not be suitable alternatives and have not been vetted in any way;

• mach2 - direct fork

See advisory page for additional details.

Summary

We want to be able to calculate and properly meter fuel & memory usage on wasm functions within a workflow, dependent on workflow settings.

Goals

• Test and showcase fuel decreasing over a computation workflow
• Test and showcase memory decreasing over a computation workflow

ETA: 2023-09-30

Summary

Browser (host) support via (jco)

Components

• TBD

ETA: 2024-05-14

Summary

Summary

Nodes need to bootstrap with information and share that information with other homestar nodes in a peer group. This opens up distributed scheduling and coordination.

Components

• What to capture for the capability matrix per node:
  • System metrics I: (available) CPU, memory, disk, etc
  • System metrics II: (available) GPU
• Gossiping information to a subset of peers, a "peer group", on a windowed interval.
• TBD

ETA: 2024-02-19

Summary

TBD

ETA: 2023-08-15

Summary

We want to be able to run a Homestar (runtime) node and deploy it as a binary and a Docker container.

Goals

• Docker build (homestar/server start)
• *-nix binary
• Deployment workflows/examples

ETA: 2023-09-30

Summary

We need to move to the current spec view on a Task and work with sub-tasks vs batching.

https://github.com/ucan-wg/invocation

json is unmaintained

Last release was almost 3 years ago.

The maintainer is unresponsive with outstanding issues.

One of the outstanding issues include a possible soundness issue.

Possible Alternative(s)

The below list has not been vetted in any way and may or may not contain alternatives;

• serde_json
• json-deserializer
• simd-json

See advisory page for additional details.

Summary

We want to have a first-party effect (i.e. Wasm/Wasi) for HTTP calls.

Components

• TBD

ETA: 2024-02-19

Summary

"Instruction" Invocations are content-addressed as given, which can/will typically include promise pipelined CIDs that must be resolved during execution. However, once resolved (before the actual execution of the function itself), we don't currently have a way to equate the resolved instruction (i.e. resolved with values) with the one given CIDs initially.

Essentially, the instructions given CIDs should be treated the same as those substituted with values from the output of those other task/instruction CIDs.

This will involve tracking pre/post-deferred instruction Cids for lookup on receipt checking.

Note:
Relates to:

• ipvm-wg/spec#26

ETA: 2023-12-31

Summary

TBD

Components

• TBD

ETA: 2024-02-19

Summary

Problem / Need / Opportunity

Success Scenario

ETA: 2023-06-30

Dependency

• Discovery has to be completed before #88 and #89

ETA: 2023-11-03

Summary

Problem / Need / Opportunity

Success Scenario

ETA: 2024-03-31

ETA: 2023-11-03

ETA: 2023-10-30

Summary

• Failure Handling, Traces
• Virtual Resiliency
  • a mechanism in a (possibly distributed) programming and
    execution environment, typically employing a log, which exploits the replayably
    deterministic nature and serializilbility of an application to automatically mask
    failure.

ETA: 2023-12-31

Dependencies

• This task has to be completed after #84 and #88

Note:
Relates to ipvm-wg/spec#24

ETA: 2023-12-31

Summary

• Include Task Types

Problem / Need / Opportunity

ETA: AAAA-MM-DD

Summary

We want to leverage Ucans to authorize and validate task invocations and workflow execution. The current Ucan invocation spec has this at the task level, but we'd direct this information from workflows at the top level, pushing information into individual tasks, and use it at the receipt level as well.

Components

• TBD

ETA: 2023-12-20

aes-soft has been merged into the aes crate

Please use the aes crate going forward. The new repository location is at:

<https://github.com/RustCrypto/block-ciphers/tree/master/aes>

AES-NI is now autodetected at runtime on i686/x86-64 platforms.
If AES-NI is not present, the aes crate will fallback to a constant-time
portable software implementation.

To force the use of a constant-time portable implementation on these platforms,
even if AES-NI is available, use the new force-soft feature of the aes
crate to disable autodetection.

See advisory page for additional details.

Summary

For the MVP, Workflows will be rendered as JSON and need to be loading, parsed, and then executed---really queued for execution. Eventually, we'll allow for other input formats, and #103 for generating workflow configuration and translation.

Goals

• Make sure workflows are convertible to JSON and back.
• Run multiple workflows over CLI.
• Load workflows from CLI .json files.

ETA: 2023-08-15

Summary

Runtime should rely on anyhow, but the library packages (e.g. core, wasm), should leverage only thiserror, with specific error information and names.

Checklist

• homestar-core
• homestar-wasm

Summary

We'd like to support first-class interop with serverless/edge-compute functions within a workflow, particularly these two "types of tasks":

• AWS Lambda
• Fastly Compute@Edge

Incorporation details are still TBD.

ETA: 2023-12-31

Summary

Tests require libsqlite3 to be installed.

Problem

Was an unexpected build failure on a new install.

Desktop (please complete the following information):

• OS: debian 11

ETA: 2023-12-31

aesni has been merged into the aes crate

Please use the aes crate going forward. The new repository location is at:

<https://github.com/RustCrypto/block-ciphers/tree/master/aes>

AES-NI is now autodetected at runtime on i686/x86-64 platforms.
If AES-NI is not present, the aes crate will fallback to a constant-time
portable software implementation.

To prevent this fallback (and have absence of AES-NI result in an illegal
instruction crash instead), continue to pass the same RUSTFLAGS which were
previously required for the aesni crate to compile:

RUSTFLAGS=-Ctarget-feature=+aes,+ssse3

See advisory page for additional details.

Summary

Dependencies

• This task has to be completed after #84 and before #89

ETA: 2023-12-31

Summary

The current MVP version will run workflows via configuration, i.e. JSON, YAML, etc. We need to investigate and build a suite of libraries and tools to generate workflows for composing tasks, task-types, etc.

ETA: 2024-03-31

Summary

Problem / Need / Opportunity

Success Scenario

Notes

Relates to:

• #100
• #101

ETA: 2024-03-31

ETA: 2023-08-15

Summary

IPLD <=> WIT interpreter for executing functions within Wasm components.

Flexible Types (not part of IPLD proper)

• record(s)
• flag(s)
• option(s)
• result(s)
• variant(s)
• enum(s)
• union(s) (unions have been 🪓'ed!)
• tuple(s)

ETA: 2023-10-20

Summary

Use gossipsub (and mdns) to share receipts (possibly other data) with connected peers.

Summary

For deterministic wasm, we should verify all links as part of the ahead-of-time "compilation" of workflows before any execution takes place. We should fail the workflow and return errors for all CIDs that do not exist at the time of execution.

If links do exist on the network but are not local, we should stream in the necessary (IPLD) blocks over the network to make the execution feasible, which is related to #78.

This does not involve the coordination piece of who should actually run the workflow, but only at the point when a node is deemed ready to execute it.