Describe the bug
POST to /api/database will overwrite an existing database instead of erroring

To Reproduce
Create a database with a POST to /api/database.
Run the same call again.

Expected behavior
Expect Metabase to error and say, "Database with name 'foo' already exists"

Actual behavior
Metabase gives another 200 and will overwrite any previous database config with

Issue Description

I'm unable to run DL4J with nvidia CUDA back end despiite following the instructions here:
https://deeplearning4j.org/docs/latest/deeplearning4j-config-gpu-cpu
Project works fine with native back end. When I debug, I can see the service loader finding the JCublasBackend.java class and then failing on isAvailable().

As far as I can tell I've done everything recommende

1. Select theme with thick strip in line number block.
2. Save and restart. Open some file. Нou see that the first characters of the lines are hidden under stripe.
3. Open another file. All display properly.
4. If you see carefully that the whole block with line numbers in the first case is shifted to the left.
   First file
   

I've wanted to craft a "1 minute", "5 minute", "15 minute" moving average (like a unix load average), but don't know the right r to pass to ewma-timeless to get it.

Either documenting a rule of thumb or providing a mechanism to recreate that would be helpful.

https://github.com/ring-clojure/ring/blob/master/ring-devel/src/ring/middleware/reload.clj

It appears wrap-reload needs to be passed a handler as normal, but with the caveat that its referenced through a var (see mmcgrana/ring#72).

Something along the lines of:

(def app
  (-> (compojure.core/routes my-routes)
      (compojure.handler/api)))

(def app-with-reloa

Evaling the form (throw (ex-info "foo" {})) with M-x cider-pprint-eval-last-sexp-to-comment yields the empty comment string:

;; =>

Arguably it should either:

1. Not yield a ;; => at all (just the empty string) (and appropriate cider error buffer)

or it should:

2. Print the error in the comment.

The later might be useful when describing code interactions and REPL s

Problem

Currently when a user receives a PN, we show a very generic message (no indication of sender, body, etc). This will change in the future (e.g. with status-im/status-react#7043), so it would be good to be more explicit about the fact that we are showing a generic PN message due to the db being locked. Also, since we may receive PNs from users we've since removed

we need more than lsmagic.

Currently, changes to plugin information models need to be mirrored, manually in the respective README.md.

This proposal outlines a possible approach to:

1. Generate the relevant portion of the README directly from the info model.
2. Integrate into the existing plugin release process.

A: Create a doc-gen lein plugin to render an information-model map into markdown

• Content should correspond

If I wanted to specify ClojureScript dependencies, the following snippet would suffice.

#!/bin/sh
"exec" "lumo" "-c" "tools.cli-0.3.7.jar" "$0" "$@"

I think we should document this somewhere in this project.

How can I specify npm dependencies in a clojurescript script? Can it be documented, too?

Classpath conflict: org.clojure/clojure version 1.8.0 already loaded, NOT loading version 1.3.0

If you specify a Clojure version in boot.properties and don't specify the same Clojure version in your :dependencies you will get a warning like the one above.

Not sure if this is worth it but we could provide some more context for the specific case of Clojure:

Classpath confli

Unity has changed the UI to configure the Mono Runtime in 2019.2 and we need to update our documentation to reflect that.

The documentation is not inaccurate for older versions of Unity, so maybe an amendment (as opposed to a replacement) with a note about checking your Unity version is the way to go.

Tracking down a problem with the latest upgrade. Because of a resolve failure, the arguments to a field are included in an error map; one value is a java.time.LocalDateTime. Cheshire throws an exception when streaming this as JSON, and the final result is a response with a body that is the empty string.

The right solution is to use cheshire.generator/add-encoder:

(add-encoder LocalDa

When defining a resource, I leave a lot of decision points at their default value (by not implementing them). The default paths could be indicated on the decision graph with a different colour.

This would save a lot of time going back and forth between the graph an this table.

![image](https://user-images.githubusercontent.