People new to Deno might assume that the -L and --log-level flags affect all logging including console.* (see: #14143). Current help is certainly ambiguous:

    -L, --log-level <log-level>
            Set log level
            
            [possible values: debug, info]

We should make it clear that it only applies to internal bugging. Something like:

Set log lev

Maybe this should be used as a feat? idk

Describe the bug

https://github.com/tauri-apps/tauri/blob/45d427e44c0e06194079426c2690019643e03277/core/tauri/scripts/core.js#L136

here is my dom hierarchy:

import React from "react";
import classes from "./index.module.scss";
import clsx from "clsx";
import { Icon } from "@rsuite/icons";
import {
  VscChromeClose,
  VscChr

Describe the bug you encountered:

The options --map-syntax and --ignored-suffix cannot work together.

How to reproduce it:

1. Prepare a file foo.demo in YAML syntax:

   # file: foo.demo
   foo: "bar"

2. Use bat --map-syntax "*.demo:YAML" foo.demo can print it with YAML syntax highlighting:

   bat foo.demo \
       --map-syntax "

Since

• we have to test the dump behavior manually
• we often get bug reports during pre-release regarding the dumps

We might want to add a CI testing the dumps behavior

• Using each already created dump file on our public S3
  • try to import them into Meilisearch and check it was well imported (same documents, same key

It would be great if you could try to use the same/compatible dependency version across the swc crates, for example:

[[package]]
name = "swc_cached"
version = "0.1.1"
dependencies = [
 ...
 "dashmap 5.2.0",
]

[[package]]
name = "swc_ecma_loader"
version = "0.29.0"
dependencies = [
 ...
 "dashmap 4.0.2",
]

[[package]]
name = "swc_ecma_transforms_react"
version = "0.100

(As discussed in #885,) the current benchmark suite has a few shortcomings.

The most obvious one is that there is no standardized dataset. Past ideas involved using large Git repositories (Linux, Chromium, Rust compiler), but these repositories change over time. We can not simply check out a certain state because the .git folder will still grow. It'

This is about:

• Other (Important Tips)

Component communication might deserve a dedicated page.

Ancestor -> Descendant

straightforward: passing props. Using a context if the descendants can be too deep down the tree.

Descedant -> Ancestor

This is not very obvious. In fact, two people asked the same question on Discord in one day. And personally, I had no clue either despite h

Describe the bug

Currently, git push's is typed to only accept a single positional argument. This is incorrect, however, as multiple branches are definitely accepted by Git.

How to reproduce

1. Attempt to push multiple new branches at a time to a remote repository in Git. Observe that the command is rejected, and the following diagnostic is emitted:

   git push -u orig
   

When running rustdesk in portable mode on windows, if an attacker has write access to the application directory, we can hijack the dll which is used by rustdesk. It's a little like CVE-2020-35483 of anydesk (https://anydesk.com/cve/2020-35483/).
I have sent details to [email protected] by email.
Thanks.

I'm working on an application which mainly consists for sliders for parameter control. For better user experience, it would be nice to offer two features: reset to default and fine control.

On VST plugins this is normally done via double-clicks and/or modifier keys. E.g. double-clicking resets the slider to a default (mostly 0), alternatively Ctrl-/Cmd-Klick also does it. For fine control, ofte

Ref #94. It might be better for the output to say something like

added: foo (binary file)

than the current

Binary files /dev/null and b/foo differ

Describe the bug
Using a time dimension on a runningTotal measure on Snowflake mixes quoted and unquoted columns in the query. This fails the query, because Snowflake has specific rules about quoted columns. Specifically:

• All unquoted column names are treated as upper case
• Quoted column names are case sensitive.

So "date_from" <> date_from

To Reproduce
Steps to reproduce

It would be neat if you could change the color of the text that shows when the progress bar covers it without changing the background. My motivation is that I enjoy the black background but the default color can be hard to read on dark progress bar colors.

<img width="1423" alt="Screen Shot 2020-06-06 at 11 50 41 AM" src="https://user-images.githubusercontent.com/16331012/83952212-14b8d780-