When map.fitBounds(...) is called with a bearing option passed in, it seems like the bearing is not taken into the account on calculating the appropriate zoom, resulting in part of the bounded area to not be in view.

mapbox-gl-js version: 1.12.0

browser: Chrome

Steps to Trigger Behavior

1. Create a bounded area with a list of coordinates
2. Call map.fitBounds(...) wi

I think we should patch test/CMakeLists.txt to always use -Wall -Werror on *nix and the corresponding MSVC flags. It is way too easy to overlook a warning in the CI output as #1797 has shown.

@nlohmann Thoughts?

Describe the bug
See screenshot. Should be don't not don't

To Reproduce
Steps to reproduce the behavior:

1. Install latest 4.0 windows client
2. Add cluster
3. Go to cluster settings
4. Read text for "accessible Napespaces"

Expected behavior
Escaped cor

Thanos, Prometheus and Golang version used:

thanos, version  (branch: , revision: )
  build user:
  build date:
  go version:       go1.15.5
  platform:         darwin/amd64

built at revision d6162144. We saw the same effect in production with v0.15.0, haven't tried again in 0.17.2.

Prometheus version N/A.

Object Storage Provider: N/A

What happened:

A rule

according to runtime doc, I code Deno.dir("home").

but output as follow:

Uncaught TypeError: Deno.dir is not a function
    at <anonymous>:2:6

env:

deno 1.5.4 (bc79d55, release, x86_64-apple-darwi