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.

Describe the bug
When a user signs in using Auth.signIn() the "signIn" event is registered multiple times in the Hub listener

To Reproduce

1. Add a log inside the "signIn" event in the Hub.listener callback
2. Open devtools
3. Sign in using Auth.signIn()
4. Notice there is at least 4 or more logs and the same amount of network calls

Expected behavior
The sign in event shou

The word is used in lots of places, e.g.:
https://thanos.io/tip/thanos/design.md/ "Chunk files hold a few hundred MB worth of chunks each."
https://thanos.io/tip/thanos/storage.md/ "This can be used to find chunk with samples in the chunk files."

It would be good to define it, like "a chunk is part of the data structure of Prometheus TSDB, holding up to 120 samples for a single timeseries".

Description

Adding Indonesian translation of Readme.md and contributing.md

Con

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.

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

Where is the list of abbreviations used in the standard? The term "UA" is used extensively throughout the text but not explained anywhere...

https://html.spec.whatwg.org/commit-snapshots/009a7316ad7f1b69de978101b043b9b29878d975/#table-of-contents

Just playing around with my miner tonight, I set burn_fee_cap = -2 and the miner stopped with a thread panic.

Process abort due to thread panic
   0: backtrace::backtrace::libunwind::trace
             at .cargo/registry/src/github.com-1285ae84e5963aae/backtrace-0.3.50/src/backtrace/libunwind.rs:95
      backtrace::backtrace::trace_unsynchronized
             at .cargo/registry/src/git

We want to have consistent and structured logs to improve the ability to filter and analyse longhorn-manager logs.
Currently the controller uses the global logrus package logger, the task here would be to switch the log calls to the instance logger that was implemented in longhorn/longhorn-manager#661

While doing this also improve the log messages, where possible.
For an example of a successf