There are a lot of options in persistConfig that aren't mentioned in the README. We should add a section to the README that documents each option you can declare in a persistConfig.

Is your proposal related to a problem?

Moving from Prometheus to Thanos and I am now noticing that Ruler does not show alert rule duration in the UI like Prometheus would show. I think it is important to show this

Before opening, please confirm:

• I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
• I have searched for duplicate or closed issues.
• I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-cli/blob/master/CONTR

Local PV (device) provisioner leaves a stale BDC in the following case:

• On PVC request, creates a BDC
• If the system doesn't have a matching BD, then PVC request keeps retrying, and so does the NDM operator that keeps retrying
• Now if the user deletes the PVC, then Local PV (device) provisioner doesn't get the trigger to process delete, as there was no PVC.

This causes the stale BDC

I read the docs of dexie-export-import thoroughly, however I didn't find a way how to add onto the current database when importing the data. It either completely replaces the whole table or merges and overwrites any row with the same id.

What I'd like to do is to import the data with new id's, while keeping the old data in the table intact.

https://html.spec.whatwg.org/multipage/interaction.html#focus-processing-model

Let candidate be target's top-level browsing context's active document.

This should be

Let candidate be target's browsing context's top-level browsing context's active document.

where the inserted "browsing context" links to #concept-document-bc.

Here is an issues with detailed description: NekR/offline-plugin#77

Question

Environment:
v1.1.1
v1.20.6+k3s1

• Node config
  • Alpine (2x worker)
  • Ubuntu 20.04 (Worker/master)

Does Longhorn Require Bash?

Reason I ask is because I'd installed the following and remounted / as shared and whilst longhorn was running I couldn't get anything to mount if the pod was scheduled to the alpine node, longhorn would be showing attaching/detac

The benchmarking scripts in benches/ haven't been updated since the VM decoupling refactor began.