-
## Issue Report Template
### Tectonic Version
tectonic-1.5.5-tectonic.3
### Environment
baremetal/virtualbox VMs
What hardware/cloud provider/hypervisor is being used with Tectonic?
Te…
-
## Describe the bug
I noticed that when I was doing IO on the HDD BTRFS storage pool where Longhorn has volumes located, all the volumes will crash sooner or later (usually really fast).
## To R…
-
I envision 3 operation modes
In italic are 'nice to have' features that may or may not be difficult to achieve.
## Mode1: shared usage for debugging (default mode for human users)
1. resourc…
-
Hey folks.
I am using meson + ninja since ... well, 3 years or so, largely because other devs
switched to it increasingly. Meson and ninja is an awesome combination. Hopefully
we can abandon the …
-
### Describe the bug
Sequential offloading doesn't work when using `pytest`, but does seem to work outside of tests.
This is an issue, because we can't properly test sequential offloading on Stabl…
-
## Describe the bug (🐛 if you encounter this issue)
I have a freshly deployed Longhorn 1.4.0 which appears to be working properly. However when deploying pods that require persisted volumes it take…
-
By the time we get to our first `convert_namespace_to_omegaconf` call, we already have:
```
# from hydra.core.config_store import ConfigStore
(Pdb) cs = ConfigStore.instance()
(Pdb) cs.repo.keys()…
-
https://github.com/django-q2/django-q2/blob/7add68f7709856f875bf145d59374adc80112009/django_q/cluster.py#L317
Is there a reason why the cluster command's schedule processing is locked at running on…
xaqbr updated
4 months ago
-
### Description of the new feature / enhancement
There needs to be a schedule for the keep awake feature allowing users to set a specific **time range**, similar to the **Night Light** feature. So …
-
### Bug description
Problem is the title. No matter what timezone I select, the report job gets scheduled 12 hours ahead.
In the Superset UI, the timezone display on the created report job is alw…