sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: TypeScript
Issue: Provide a way to clone a ast tree includes it's all children
Labels: Suggestion,API,Awaiting More Feedback

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker.

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ, especially the "Common Feature Requests" section: https://github.com/Microsoft/TypeScript/wiki/FAQ

-->

## Search Terms
api, plugin, transformer
<!-- List of keywords you searched for before creating this issue. Write them down here so that others can find this suggestion more easily -->

## Suggestion
Provide a way to clone an ast tree not only top level node but includes it's all children.

<!-- A summary of what you'd like to see added or changed -->

## Use Cases

Currently, [replace node with the original node](https://github.com/HearTao/ts-react-hooks-tools/blob/main/src/service.ts#L399-L419) is not work with textChanges(It will fail an assert).

So I have to do it like this: https://github.com/HearTao/ts-react-hooks-tools/blob/main/src/utils.ts#L458-L476.

I think It's not a good idea even it works.

<!--
What do you want to use this for?
What shortcomings exist with current approaches?
-->

## Examples

<!-- Show how this would be used and what the behavior would be -->

## Checklist

My suggestion meets these guidelines:

* [ ] This wouldn't be a breaking change in existing TypeScript/JavaScript code
* [ ] This wouldn't change the runtime behavior of existing JavaScript code
* [ ] This could be implemented without emitting different JS based on the types of the expressions
* [ ] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
* [ ] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).
Repository: go
Issue: x/tools/go/analysis/passes/copylock: allows assignment of composite literal with a "lock"
Labels: NeedsInvestigation,Tools,Analysis

The copylocks checker does not complain about 
```
var a nonCopyableType
...
a = nonCopyableType{}
```

but does complain about 
```
var a nonCopyableType
var b nonCopyableType
...
a = b
```
(as expected).

`nonCopyableType` looks something like:
```
type nonCopyableType struct {
    _ sync.NoCopy

    ...
}
```


where `sync.NoCopy` is 
https://github.com/google/gvisor/blob/a97ceec01bc464c9efa5d8140906c46f637e9002/pkg/sync/nocopy.go#L22

I think this is because of 
https://github.com/golang/go/blob/e10c94af26b95f4af71c4a040b3d3f01499d01de/src/cmd/vendor/golang.org/x/tools/go/analysis/passes/copylock/copylock.go#L74 which allows assignment with a rhs composite literal, while ignoring the lhs.
Repository: youtube-dl
Issue: Option '--only-progress'
Labels: request

## Checklist

- [x] I'm reporting a feature request
- [x] I've verified that I'm running youtube-dl version **2020.11.29**
- [x] I've searched the bugtracker for similar feature requests including closed ones


## Description

Would it be possible to add an option --only-progress (like --quiet but with showing progress line), without those lines:
[youtube] dIEHRYlcgRY: Downloading webpage
[youtube] dIEHRYlcgRY: Downloading video info webpage
[download] Destination: ***
Repository: TypeScript
Issue: filter noUncheckedIndexedAccess with own property check
Labels: Suggestion,Awaiting More Feedback

## Search Terms

ownProperty

hasOwnProperty

noUncheckedIndexedAccess

type check

## Suggestion

<!-- A summary of what you'd like to see added or changed -->
`noUncheckedIndexedAccess` is a great feature. However, ts reports that object can be `undefined` even with `hasOwnProperty` check.

I suggest that a `hasOwnProperty` check makes unchecked indexed accesses checked, and return the checked value.

## Use Cases

```ts
const obj: {[key: string]: string} = {};
// do something with obj
const key = "someKey";
if (Object.prototype.hasOwnProperty.call(obj, key)) {
  console.log(obj[key].length); // TS2532: Object is possibly 'undefined'.
}
```
Since only `string` values are allowed in `obj`, the only case such value is `undefined` is when the key does not exist on `obj`. The value of `obj[key]` can only be `string`. However, typescript still reports type of `obj[key]` being `string | undefined`.

## Examples
```ts
const obj: {[key: string]: string} = {};
// do something with obj
const key = "someKey";
if (Object.prototype.hasOwnProperty.call(obj, key)) {
  console.log(obj[key].length); // no problem, since obj[key] has correct type string
}
```

## Checklist

My suggestion meets these guidelines:

* [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
* [x] This wouldn't change the runtime behavior of existing JavaScript code
* [x] This could be implemented without emitting different JS based on the types of the expressions
* [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).
Repository: flutter
Issue: [proposal][animations] OpenContainer widget to slide back
Labels: c: new feature,package,c: proposal,p: animations,team-ecosystem,P3,triaged-ecosystem

Currently ,OpenContainer widget cannot slide back
Repository: go
Issue: x/sys/cpu: add support for darwin/arm64
Labels: NeedsFix

`darwin/arm64` support for `internal/cpu` was implemented in c15593197453b8bf90fc3a9080ba2afeaf7934ea using a mix of dynamic detection with sysctlbyname and hardcoded minimal feature support assumed on `darwin/arm64`.

For `x/sys/cpu` it can be assumed it only needs to work with Go 1.16 and newer. Interestingly darwing/arm64 was previosly used for the now ios/arm64 port. We should keep compatibility such that old code still compiles pre Go 1.16 even if there may be no runtime detection supported.

Implementing support for `x/sys/cpu` will be a bit more complex. While `x/sys/cpu` does not need to be as low dependency as `internal/cpu` it should still avoid uncommon or large dependencies. Note that `x/sys/cpu` is vendored into the standard library for some crypto support that is also vendored in. 

`x/sys/cpu` should avoid a dependency on `x/sys/unix`: https://github.com/golang/go/issues/32102
Repository: pytorch
Issue: When multiple GPUs run multiple processes, it is found that any process not running in GPU 0 will have some more memory (such as 200m) in GPU 0. What is the cause of this?（多个GPU跑多进程时候，发现只要不在0号GPU跑的进程都会在0号GPU多出一些内存(如200M)，请问这是什么情况导致的？）
Labels: oncall: distributed

Hello everyone, when multiple GPUs run multiple processes, we find that a process running in GPU 0 only occupies 1000m of memory; however, running a process with GPU 1 will occupy 1000m of memory in GPU 1, and it will also occupy 200m of memory in GPU 0; GPU 2 or GPU 3 are the same; we found that as long as the processes not running in GPU 0 will have 200m more memory in GPU 0, what is the cause of this? Thank you!

大家好，在多个GPU跑多个进程的时候发现，0号GPU跑的一个进程只占显存1000M；但是用1号GPU跑一个进程会在1号GPU占显存1000M，而且会在0号GPU也占用200M显存；2号或3号GPU都一样；发现只要不在0号GPU跑的进程都会在0号GPU多出200M显存，请问这是什么情况导致的，谢谢！

cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @agolynski @SciPioneer @H-Huang @mrzzd
Repository: deno
Issue: Implement Deno.permissions.requestAll
Labels: permissions,public API,suggestion

The basic idea for this is to allow for requesting multiple permissions as a block by using a array. This would allow a script (when well written) to request the permissions it knows it needs all at once instead of individually.

It's the difference between the new android model of asking for permission when the app needs it, and the old model of asking when installing. Sometimes you want it at the start.

This could also allow for default lists to be added into std (or elsewhere) for people who want to write (reasonably) secure scripts without having to individually tailor all the permissions. (I.E: ReadWriteNet for Read/Write current directory + allow net, which is what most of us want anyway.)

`requestAll` Should probably request everything as a all-or-nothing batch since if you need only a single one, you can use `request`, or if there are optional sets, you can use multiple `requestAll`.
Repository: next.js
Issue: [i18n] Can't link to/access pages in locale directories
Labels: Internationalization (i18n)

# Bug report

## Describe the bug

It's not possible to link to or access a page located in a folder with the same name as a configured locale, e.g.

```
pages/
  de/
    impressum.tsx
```

## To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

1. Go to https://codesandbox.io/s/thirsty-chatelet-11if4
2. Click on any of the links to one of the imprint pages (behavior is described)

## Expected behavior

It should be possible to use a page structure that mimics locales.

Considering abovementioned page structure, at least one of these should work. Not sure which would be best, since they all deviate a bit from the existing behavior
- `<Link href="/de/imprint" locale={false}>` (technically locale is "de")
- `<Link href="/de/imprint" locale="de">` (weird because "de" appears in href and locale)
- `<Link href="/imprint" locale="de">` (weird because usually href is same as page path in file system)

Also, a page in a locale subfolder should have its router `locale` properly set.

## Screenshots

If applicable, add screenshots to help explain your problem.

## System information

- Version of Next.js: 10.0.3
- Version of Node.js: 14
- Deployment: next dev
Repository: TypeScript
Issue: Richer Diagnostic Display Meta-Issue
Labels: Discussion,Domain: Error Messages,Meta-Issue

This issue tracks a couple of different useful ideas for making diagnostics "richer" for display purposes. We've wanted some of these for a while, and they're partially inspired by testing tools like Jest and Mocha. We've also seen tools like Rust, Rome, and Flow prove them out to some extent.

Long-term, you could imagine them being interactive with the a richer compiler client.

# Printing Messages Across Lines

Types can get unwieldy, and displaying them inline makes it harder to see where things begin/end.

```
Type

    { x: string, y: number }

is not assignable to

    { x: string, y: string }
```

Notice no punctuation at the end. Not sure if we can generalize messages that way.

Also not sure how this plays well with

* tools that parse our output.
* diagnostic *elaborations*

# Highlighted Spans in Messages

Imagine being able to highlight individual sections inside of types to indicate where the issue occurs.

```
                              vvvvvvvvvvv
Type '{ a: string; b: number; c: boolean; }' is not assignable to type '{ a: string; b: number; }'.
                              ^^^^^^^^^^^
  Object literal may only specify known properties, and 'c' does not exist in type '{ a: string; b: number; }'.
```

# Diff Highlighting in Messages

Basically imagine red being the provided color, with green being an expected color.

```diff
Type '[string, number, boolean]' is not assignable to type '[string, string, boolean]'.
               ^^^^^^                                                ^^^^^^
               rrrrrr                                                gggggg
```
Repository: pytorch
Issue: CUDA error: illegal memory access Conv3d
Labels: module: cudnn,module: convolution,triaged

## 🐛 Bug
I get this error:
RuntimeError: CUDA error: an illegal memory access was encountered

with the following code:

## To Reproduce

Steps to reproduce the behavior:

import torch
torch.backends.cuda.matmul.allow_tf32 = True
torch.backends.cudnn.benchmark = True
torch.backends.cudnn.deterministic = False
torch.backends.cudnn.allow_tf32 = True
data = torch.randn([2, 1, 33, 352, 608], dtype=torch.float, device='cuda', requires_grad=True)
net = torch.nn.Conv3d(1, 1, kernel_size=[3, 3, 3], padding=[1, 1, 1], stride=[1, 1, 1], dilation=[1, 1, 1], groups=1)
net = net.cuda().float()
out = net(data)
out.backward(torch.randn_like(out))
torch.cuda.synchronize()

## Expected behavior

I expect no error.

## Environment

Collecting environment information...
PyTorch version: 1.7.0+cu110
Is debug build: True
CUDA used to build PyTorch: 11.0
ROCM used to build PyTorch: N/A

OS: Ubuntu 20.04.1 LTS (x86_64)
GCC version: (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
Clang version: Could not collect
CMake version: version 3.16.3

Python version: 3.8 (64-bit runtime)
Is CUDA available: True
CUDA runtime version: Could not collect
GPU models and configuration: 
GPU 0: GeForce RTX 2080 Ti
GPU 1: GeForce RTX 2080 Ti

Nvidia driver version: 450.51.06
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A

Versions of relevant libraries:
[pip3] numpy==1.18.3
[pip3] torch==1.7.0+cu110
[pip3] torchaudio==0.7.0
[pip3] torchgeometry==0.1.2
[pip3] torchvision==0.8.1+cu110
[conda] Could not collect



cc @csarofeen @ptrblck
Repository: go
Issue: flag: fails to parse flags with particularly-placed (but valid) double-quotes inside executable path on windows
Labels: OS-Windows,NeedsInvestigation

<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

go version go1.15.2 darwin/amd64, cross-compiling for and running on win

I noticed this issue after cross-compiling for win, then running on win. I have only been able to reproduce on Win. I have not tried compiling natively on win to see if the issue also exists under those circumstances

### Does this issue reproduce with the latest release?


### What operating system and processor architecture are you using (`go env`)?
Host (build):
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/mattewong/Library/Caches/go-build"
GOENV="/Users/mattewong/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/mattewong/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/mattewong/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/3d/4_23s9qj7dj3z966y7_q__hm0000gp/T/go-build380736401=/tmp/go-build -gno-record-gcc-switches -fno-common"

Target (run): Windows Server 2016

### What did you do?

flag_bug.go:
```
/*
  demo of flag bug
*/
package main

import (
        "flag"
        "log"
)


func main() {
        stringVar := "default string value"
        flag.StringVar(&stringVar, "str", stringVar, "set a string var")
        flag.Parse()
        log.Printf("String var: %s\n", stringVar)
}
```

compile:
`GOOS=windows go build flag_bug.go`

copy flag_bug.exe to target system c:\temp\

run:

1. flag_bug.exe -h
2. "c:\temp"\flag_bug.exe -h
3. "c:\temp\\"flag_bug.exe -h

### What did you expect to see?

Same result each time: usage


### What did you see instead?

First 2 behave as expected:
```
Usage of flag_bug.exe:
  -str string
        set a string var (default "default string value")
```

However, the third one (`"c:\temp\"flag_bug.exe -h`) does not:
```
2020/12/07 20:10:22 String var: default string value
```

It appears that the double-quotes somehow cause the flag parsing to entirely fail, and no flags are parsed (whether expected flags or not)
Repository: flutter
Issue: Handling non-square pixels
Labels: c: new feature,e: device-specific,framework,engine,a: quality,e: embedder,P3,team-engine,triaged-engine

Some displays, especially in the embedded world (e.g. the [official Raspberry Pi touchscreen](https://www.raspberrypi.org/products/raspberry-pi-touch-display/)), have non-square pixels. Right now, we report the devicePixelRatio as a single number. I think we should add a field that reports the Size, and have devicePixelRatio report the mean of the actual x and y device pixel ratios. The framework can then be adjusted to scale in both directions according to the two values appropriately, instead of applying a uniform scale.
Repository: rust
Issue: `overflow evaluating the requirement` when trait bound is added
Labels: A-trait-system,T-compiler,C-bug,T-types

### Source
```rust
pub trait Baz<S> {
    type Quaks;
}

impl Baz<[(); 8]> for bool {
    type Quaks = u8;
}

impl<T, S> Baz<[S; 3]> for T
where
    T: Baz<S>,
    <T as Baz<S>>::Quaks: Copy,
{
    type Quaks = [<T as Baz<S>>::Quaks; 3];
}

pub trait Bar
where
    Self: Sized,
    bool: Baz<Self>,
{
    fn foo(bits: <bool as Baz<Self>>::Quaks);
}

impl Bar for [(); 8] {
    fn foo(_: u8) {}
}

impl<S: Bar> Bar for [S; 3]
where
    bool: Baz<S>,
{
    fn foo(_: <bool as Baz<Self>>::Quaks) {}
}

fn main() {}
```


`rustc overflow_demo.rs` returns:

```
error[E0275]: overflow evaluating the requirement `bool: PackedElement<[_; 8]>`
  |
  = help: consider adding a `#![recursion_limit="256"]` attribute to your crate (`overflow_demo`)
  = note: required because of the requirements on the impl of `PackedElement<[[_; 8]; 8]>` for `bool`
  = note: 127 redundant requirements hidden
  = note: required because of the requirements on the impl of `PackedElement<[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[_; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]; 8]>` for `bool`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0275`.
```

Now remove the line
```
    <T as Baz<S>>::Quaks: Copy,
```
and it compiles without error. `Copy` can be replaced with most any other trait bound.

Separately, where as normally such `overflow evaluating the requirement` errors give a line number, here, no line number is given.

### Meta
`rustc --version --verbose`:
```
rustc 1.48.0 (7eac88abb 2020-11-16)
binary: rustc
commit-hash: 7eac88abb2e57e752f3302f02be5f3ce3d7adfb4
commit-date: 2020-11-16
host: x86_64-unknown-linux-gnu
release: 1.48.0
LLVM version: 11.0
```
Approximately the same behavior in nightly
```
rustc 1.50.0-nightly (5be3f9f10 2020-12-03)
binary: rustc
commit-hash: 5be3f9f10e9fd59ea03816840a6051413fbdefae
commit-date: 2020-12-03
host: x86_64-unknown-linux-gnu
release: 1.50.0-nightly
```
Repository: flutter
Issue: [ios] [integration_test] avoid using preprocessor macros to make it easier to use from Swift
Labels: a: tests,platform-ios,f: integration_test,P3,c: tech-debt,team-ios,triaged-ios

The iOS implementation of integration_test uses a C preprocessor macro to make it easier to avoid some boilerplate. This makes it impossible to reuse that code from Swift, or to set breakpoints.

Rather than defining and encouraging users to use `INTEGRATION_TEST_IOS_RUNNER`, we should just have users call the right method(s). This will also make it easier for users to write Swift based test files for this, should they so chose (right now the instructions are ObjC only).
Repository: opencv
Issue: accessviolationexception
Labels: incomplete



opencv version --- 4.1
windows 10
vs 2019
x64 release


code :
System::String^ __clrcall AlgoCpp::Class1::template_match(System::Drawing::Bitmap^ sourceImage_bitmap, int pos_no)
{
	try
	{

		std::cout << std::endl;
		std::cout << std::endl;
		std::cout << "*****************  template_match output from c++ ************* " << std::endl;
	

		source_image_mat.release();
		 source_image_mat = _CommonAlgo.BitmapToMat(sourceImage_bitmap);

		 //*******************
		// template match function 
		    template_match_with_rotation_return_image = _CommonAlgo.Template_match_with_rotation_match(
			 source_image_mat,
			_vector_template_rect.at(pos_no-1).first,
			_vector_template_rect.at(pos_no - 1).second,
			10);
		resize(template_match_with_rotation_return_image, source_image_mat, source_image_mat.size(),1,1);
		//source_image_mat = template_match_with_rotation_return_image.clone();
		std::cout << "*****************  template_match output from c++  END  ************* " << std::endl;
		//***************************

		return "ok";

	}//try 
	catch (const std::exception & e)
	{
		const char* err_msg = e.what();
		std::string s = err_msg;
		return gcnew System::String("Exception In template_match .");

	}
Repository: flutter
Issue: Update the create template to better support integration_test with a proper testing target in the Xcode workspace
Labels: a: tests,c: new feature,platform-ios,tool,f: integration_test,P3,team-ios,triaged-ios

Depends on https://github.com/flutter/flutter/issues/71873, since we'd want to do this in both the Swift and ObjC templates.

Today, for a user to use integration_test without `flutter drive`, they would have to manually change their Xcode project. This could be added to the template so they don't have to do that, which would reduce some friction for testing on e.g. FTL.
Repository: material-ui
Issue: Add useBreakpointValue hook
Labels: new feature,priority: important

- [x] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.

## Summary 💡

Provide a JavaScript API as a counterpart to the CSS [sx breakpoint's API](https://next.material-ui.com/system/basics/#responsive-values).

## Examples 🌈

```jsx
function MyApp() {
  const elevation = useBreakpointValue({ xs: 1, md: 2 });
  return <AppBar elevation={elevation} sx={{ mb: { xs: 1, md: 2 } }}>...</AppBar>;
}
```

Internally, `useBreakpointValue` would use `useMediaQuery` or `useBreakpoint` (probably better).

## Motivation 🔦

We have started to surface the need for it in https://github.com/mui-org/material-ui/issues/15561#issuecomment-674454140. The hook can be used anytime a value needs to be determined based on the breakpoints. This comment https://github.com/mui-org/material-ui/issues/17000#issuecomment-740159615 triggered the idea around opening this issue. I think that this hook is best for props that are already dependent on JavaScript logic. 

One could argue that many of the CSS properties could be made responsive, e.g. the `color` prop. However, it might be overkill, we could use this hook as an escape hatch.

We have been discussing the idea to remove the `<HiddenCss>` helper as the Box covers most of the usage thanks to the sx's display feature. I think that this JS counterpart can solve the `<HiddenJs>` part of the migration issue: https://github.com/mui-org/material-ui/issues/19704#issuecomment-612034247.

### Benchmarks

- https://seek-oss.github.io/braid-design-system/components/useResponsiveValue
- https://react-restart.github.io/hooks/api/useBreakpoint
- https://chakra-ui.com/docs/hooks/use-breakpoint-value
- https://xstyled.dev/docs/hooks/#usebreakpoint