tyger
tyger copied to clipboard
microsoft
Remote signal processing.
- replicate buffer tags to storage as metadata (limits?) - multiple storage accounts - attach as read-only account - rescan/reimport (async operation) OR (better) - database export of buffers from...
- reference existing identity - pass in the tyger cloud install - reference in run (opt-in)
Shipping run container logs to Log Analytics is redundant since we already store them in a storage account. This can be accomplished with an [annotation](https://learn.microsoft.com/en-us/azure/azure-monitor/containers/container-insights-data-collection-filter#annotation-based-filtering-for-workloads) on the pod.
When creating a new buffer or run, the user-supplied tags are validated by the server. When using `tyger {buffer,run} set --tag ...`, the tags are **not** validated. Example: ```bash $...
The npgsql connection pool size is currently hard-coded, but should be a function of the `max_connections` database server parameter and the number of Tyger replicas.
A run can be in a pending state for a while. It would be helpful to know when a run is waiting to be assigned to a node, is waiting...
Hi folks, When following the current Docker installation documentation, there's a bit of a hole that can be stepped into during the api install step. The documentation mentions that /opt/tyger...
Some users may have a need to delete runs and codespecs. When deleting a run, we should delete logs, etc. associated with the run.
It is possible to write a codespec that only partially reads from an input buffer, causing the run to fail, even if the job returns exit code 0. Example: Copy...