-
Updated
Nov 30, 2020 - Go
storage
Here are 2,168 public repositories matching this topic...
-
Updated
Nov 5, 2020 - JavaScript
-
Updated
Sep 2, 2020 - JavaScript
-
Updated
Nov 26, 2020 - JavaScript
-
Updated
Nov 2, 2020 - Python
-
Updated
Nov 30, 2020 - Go
Describe the bug
When a user signs in using Auth.signIn() the "signIn" event is registered multiple times in the Hub listener
To Reproduce
- Add a log inside the "signIn" event in the Hub.listener callback
- Open devtools
- Sign in using Auth.signIn()
- Notice there is at least 4 or more logs and the same amount of network calls
Expected behavior
The sign in event shou
It'd be great to have a frequently asked questions section as part of our official website. Such like https://prometheus.io/docs/introduction/faq/
We are getting similar questions from the community over public slack channels and office hours. We can gather them together and help the community.
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.
-
Updated
Nov 30, 2020 - JavaScript
Here is an issues with detailed description: NekR/offline-plugin#77
cc @mikewest @annevk @ericlaw1979
From https://html.spec.whatwg.org/multipage/system-state.html#normalize-protocol-handler-parameters:
'If the resulting URL record's scheme is not "https" or the resulting URL record's origin is not same origin with environment's origin, then throw a "SecurityError" DOMException.'
It seems this forbids localhost URLs like http://127.0.0.1 that are in a se
-
Updated
Nov 30, 2020 - Python
-
Updated
Oct 11, 2019 - Java
-
Updated
Sep 10, 2020 - JavaScript
-
Updated
Nov 30, 2020 - C
-
Updated
Nov 30, 2020 - Ruby
-
Updated
Nov 1, 2018 - Go
-
Updated
Nov 8, 2020
-
Updated
Nov 20, 2020 - JavaScript
-
Updated
Nov 19, 2020 - JavaScript
-
Updated
May 11, 2019 - JavaScript
-
Updated
Nov 18, 2020 - Go
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
Improve this page
Add a description, image, and links to the storage topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the storage topic, visit your repo's landing page and select "manage topics."
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.