Kris Nóva

Results 100 issues of Kris Nóva

Please read [the offficial rustdoc docs](https://doc.rust-lang.org/beta/rust-by-example/meta/doc.html) and begin auditing our rust code for documentation best practices. In some cases the `missing_docs` clippy tag which will WARN during a compile has...

Good First Issue

All fields in the `/proto` directory such as [runtime.proto](https://github.com/aurae-runtime/aurae/blob/main/api/v0/runtime.proto) needs to have full rustdoc compatible documentation, including each field in the messages. For example. Look at the following INCOMPLETE message....

Good First Issue

We want to have beautiful logs in the Aurae project. This is a perpetually open issue that will be ever-relevant to newcomers to the project. At any time new contributors...

Good First Issue

All Aurae cells should setup the namespaces by scheduling a process immediately. We believe this will be the nested `auraed`. Once the new namespaces have been "cloned" we can track...

Auraed
Subsystem: Runtime

The PSL releases the project to the public domain, and also includes the concept of a "steward" of the project. Can we please change the license from Apache 2.0 to...

We should not be able to change a cell after it has been created, you must destroy the cell and allocate a new one if you want to change anything...

Right now running `auraed -v` creates entirely too much `TRACE` output and is unsuable. We need a way to use `-v` without flooding the screen from gRPC.

Right now we have several build jobs that are executed during a pull request and a merge to main - [build-docs.yml](https://github.com/aurae-runtime/aurae/blob/main/.github/workflows/build-docs.yml) - [build-compile-test.yml](https://github.com/aurae-runtime/aurae/blob/main/.github/workflows/build-compile-test.yml) - [deploy-website.yml](https://github.com/aurae-runtime/aurae/blob/main/.github/workflows/deploy-website.yml) Can we please leverage #78...

Good First Issue
Ops

Right now `auraescript` errors and can produce many types of outputs. Would it be possible to guarantee (or strongly encourage) auraescript users to always have their output in the form...

What if we established a pattern such that a single configuration file/source was all that was needed to guarantee that an Aurae instance with defined workloads were able to start....