sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: material-ui
Issue: Cannot use conditional CSS blocks inside styled() definitions written as functions
Labels: bug 🐛,package: system,customization: theme

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

Link to live example: https://codesandbox.io/s/exciting-agnesi-xnoes2?file=/demo.js

1. There are 2 elements creating an override for a background color
2. First override uses the `styled()/* styles here */` syntax and this works correctly
3. Second uses uses the `styled()(({ theme }) => /* styles here */` syntax and the overrides are not applied

The syntax follows: https://github.com/styled-components/styled-components/issues/3189

### Current behavior 😯

Conditional styles should get applied to a provided element.

### Expected behavior 🤔

Styles don't get applied, and no errors are thrown.

### Context 🔦

I'm trying to render a css block conditionally within a block using theme variables. Excerpt from the demo:
```js
const MyComponent = () => {
  const Component = styled("div")(
    ({ theme }) => `
      background: black;
      ${true && css`
        background: red;
      `}
  `);
  return <Component />;
};
```

The result is element with black background rather than red;

### Your environment 🌎

_No response_
Repository: rust
Issue: Fix: Consider U+01C3(ǃ) as a misleading punctuation, not as alphabetic
Labels: C-enhancement,A-diagnostics,A-Unicode

here's my reasoning: 
```rust
1ǃ=2 // U+1C3 inserted here
```
errors with the wrong message: 
```rust
error: invalid suffix `ǃ` for number literal
 --> src/main.rs:2:1
  |
2 | 1ǃ=2
  | ^^ invalid suffix `ǃ`
  |
  = help: the suffix must be one of the numeric types (`u32`, `isize`, `f32`, etc.)

error[E0070]: invalid left-hand side of assignment
 --> src/main.rs:2:3
  |
2 | 1ǃ=2
  | --^
  | |
  | cannot assign to this expression

For more information about this error, try `rustc --explain E0070`.
```
Repository: deno
Issue: commandChildUnref is flaky
Labels: flaky

It fails a lot in PRs:

```
commandChildUnref => ./cli/tests/unit/command_test.ts:726:6
error: AssertionError: Expected function to throw.
    throw new AssertionError(msg);
          ^
    at assertThrows (file:///home/runner/work/deno/deno/test_util/std/testing/asserts.ts:684:11)
    at commandChildUnref (file:///home/runner/work/deno/deno/cli/tests/unit/command_test.ts:798:5)
```

Failure on main: https://github.com/denoland/deno/actions/runs/3497648099/jobs/5857006952
Repository: create-react-app
Issue: TypeScript error 6385 import { ReportHandler } from "web-vitals";
Labels: needs triage

If you have a general question about Create React App or about building an app with Create React App we encourage you to post in GitHub Discussions instead of this issue tracker. The maintainers and other community members can provide help and answer your questions there: https://github.com/facebook/create-react-app/discussions

If you're looking for general information on using React, the React docs have a list of resources: https://reactjs.org/community/support.html

If you've discovered a bug or would like to propose a change please use one of the other issue templates.

Thanks!
Repository: rust
Issue: Parsing issue in complex nested match statement with &&.
Labels: A-diagnostics,T-compiler,C-bug,A-suggestion-diagnostics,D-terse

I think I found a case where I am hitting an issue with Rust's parser which seems to get confused on the following bit of code:

```rust
fn main() {
    let x = 2;
    let y = 1;
    
    let test = match x {
        2 => match y {
            1 => true,
            _ => false,
        } && true,
        _ => false,
    };
}
```

I expected that it would compile similar to the snippet below:

```rust
fn main() {
    let x = 2;
    let y = 1;
    
    let test = match x {
        2 => {
            let foo = match y {
                1 => true,
                _ => false,
            };
            foo && true
        }
        _ => false,
    };
}
```

Instead, it seems to hit a parsing issue following the `&&` after the inner `match` yielding a `bool`, where it shows the following error instead:

```
error: unexpected , in pattern
  --> src/main.rs:11:18
   |
11 |         } && true,
   |                  ^
   |
help: try adding parentheses to match on a tuple...
   |
11 ~         } (&& true,
12 ~         _) => false,
   |
help: ...or a vertical bar to match on multiple alternatives
   |
11 ~         } && true |
12 ~         _ => false,
```

This happens on:

```
$ rustc --version
rustc 1.65.0 (897e37553 2022-11-02)
```

As well as on:

```
$ rustc +nightly --version
rustc 1.67.0-nightly (73c9eaf21 2022-11-07)
```
Repository: kubernetes
Issue: Option to prevent CRD from being deleted if CR instances still exist
Labels: sig/api-machinery,kind/feature,triage/accepted

### What would you like to be added?

Currently if you delete a CustomResourceDefinition, all CustomResource instances of that CRD will be deleted. There should be a field users can specify in the CRD spec that protects the CRD from deletion if CR instances still exist. 

### Why is this needed?

This will prevent consequences if someone accidentally deletes a CRD.
Repository: PowerToys
Issue: "Gather Windows"
Labels: Idea-New PowerToy,Needs-Triage

### Description of the new feature / enhancement

On Multi Monitor systems, the MacOS has a feature that is very powerful, "Gather" windows. If you have current access to only one monitor, say in a remote login like VNC for example. When you launch an application on an app is running on another monitor, we have to jump through a lot of hoops to get to it in Windows. If Power Toys had a tool to selct and App - or ALL apps and bring it to the current monitor, say through a Right Click on the desktop, this would be a HUGE feature.
Also, some mechanism when launching a new app to force it to the "current" screen.

### Scenario when this would be used?

Any situation where you have muti-monitors, but want to work on only one for various reasons.

### Supporting information

_No response_
Repository: rust
Issue: Borrowing an overflowing expression supresses `arithmetic_overflow`
Labels: A-lints,A-diagnostics,T-compiler,C-bug,L-arithmetic_overflow

This is possibly related to #98444

I tried this code:

```rust
fn main() {
    let x = &-(-127i8 - 1);
}
```

I expected to see this happen:

```
error: this arithmetic operation will overflow
 --> src/main.rs:3:13
  |
3 |     let x = &-(-127i8 - 1);
  |              ^^^^^^^^^^^^^ attempt to negate `i8::MIN`, which would overflow
  |
  = note: `#[deny(arithmetic_overflow)]` on by default
```

Instead, this happened: No diagnostic

### Meta
Tested on the playground 1.65 and nightly 2022-11-17
Repository: vscode
Issue: Continue Working On should surface working changes with slight differences in edit session state
Labels: feature-request,continue-working-on

1. Be on `microsoft/vscode` `main` a few commits behind upstream 
2. Have uncommitted changes
3. Continue Working On somewhere else
4. :bug: changes don't come with you

This is related to https://github.com/microsoft/vscode/issues/162120.  If there is drift in the branch state, we can't confidently resume because there's a chance we have stale file state, instead we need a way to soft nudge the user to take action and retrieve their changes.
Repository: flutter
Issue: [flutter_tools] remove package:archive as upstream it pulls in new deps
Labels: tool,P1,team-tool,triaged-tool

See https://github.com/flutter/flutter/pull/115600/files.

I will temporarily pin archive at 3.3.2, but we should discuss long-term whether it's worth keeping package:archive as a dependency.
Repository: godot
Issue: All of Project Manager's subwindows are broken (OpenGL issue)
Labels: bug,platform:windows,topic:rendering,topic:editor

### Godot version

v4.0.beta5.official [89a33d28f]

### System information

Windows 10 Home 21H2, AMD A10-9620P RADEON R5, 64 bit system

### Issue description

After the new version of Godot, Beta 5, the project manager's subwindows are very messed up. When any Window shows up (tooltips included), its contents appears on the main window for a frame and then the subwindow shows another window's contents (can also be the main window, seen especially with tooltips), nothing, or the right content but scaled inappriopiatly. The subwindows also seem to do the same thing again if it is redrawn.

I should note that this bug does _not_ happen on v4.0.beta4.official [e6751549c].

The subwindows strangely _work fine in the editor and when running a project_, both if subwindows are embed or not.

My screen recorder can only record one window, so excuse me if this video does just that. Tell me if you want to see all the windows.

https://user-images.githubusercontent.com/107559799/202775137-50009e2e-70f8-41f7-a936-e482bf817403.mp4

### Steps to reproduce

Just open Godot and show a tooltip or a window in the project manager.
Alternativly, you can also open and/or run a project and see that it works fine there.

### Minimal reproduction project

N/A
Repository: next.js
Issue: Fast Refresh waits for the Suspense Boundary to finish.
Labels: bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

    Operating System:
      Platform: linux
      Arch: x64
      Version: #1 SMP Wed Mar 2 00:30:59 UTC 2022
    Binaries:
      Node: 16.14.2
      npm: 8.5.0
      Yarn: 1.9.4
      pnpm: N/A
    Relevant packages:
      next: 13.0.4-canary.5
      eslint-config-next: 13.0.4
      react: 18.2.0
      react-dom: 18.2.0

### What browser are you using? (if relevant)

Chrome 107.0.5304.107

### How are you deploying your application? (if relevant)

_No response_

### Describe the Bug

If there is any `<Suspense>` boundary with an `async` component inside, then any changes to the page outside of `<Suspense>` will be updated after the time it takes to render the async component.

### Expected Behavior

The changes outside of the `<Suspense>` boundary should be immediately shown.

### Link to reproduction - Issues with a link to complete (but minimal) reproduction code will be addressed faster

https://github.com/jakubsobel/nextjs13-fast-refresh-issue

### To Reproduce

1. Run `npm run dev`,
2. Go to http://localhost:3000/
3. Wait 10 seconds for the `Test` component to load and then edit any text outside of the `<Suspense>` (e.g. content of the `<p>` just above the `<Suspense>`).
4. Save the file.
5. "Fast Refresh" will update the page after another 10 seconds, because of the `Suspense` below, instead of doing it immediately.
Repository: pytorch
Issue: Meta implementation for copy_ is wrong
Labels: triaged,module: meta tensors

### 🐛 Describe the bug

Currently, the meta impl for copy_ just returns self without performing any checks. This is wrong and we should fix this. 
CPU tensor: (correctly fails)
```
>>> x=torch.randn([5, 1]).expand(5, 5)
>>> x.stride()
(1, 0)
>>> sqrt=x.sqrt()
>>> sqrt.stride()
(5, 1)
>>> x.copy_(sqrt)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
RuntimeError: unsupported operation: more than one element of the written-to tensor refers to a single memory location. Please clone() the tensor before performing the operation.
```

Meta (incorrectly passes):
```
>>> x=torch.randn([5, 1], device='meta').expand(5, 5)
>>> sqrt=x.sqrt()
>>> x.copy_(sqrt)
tensor(..., device='meta', size=(5, 5))
```

### Versions

master

cc @ezyang @eellison @bdhirsh @soumith
Repository: stable-diffusion-webui
Issue: [Bug]: Bigger Images = 'Leaked semaphore objects' Crash on MacOS
Labels: bug-report,platform:mac

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What happened?

On MacOS (M1), Automatic crashes when trying to make a larger image, such as 1024 width.

This continues to happen on a different Mac, new Automatic installation and all... Everything works fine but You change to 1024 width, for instance, and it just can't handle it. This is the message I get almost every time:

```
  0%|                                                    | 0/20 [00:00<?, ?it/s]/AppleInternal/Library/BuildRoots/f0468ab4-4115-11ed-8edc-7ef33c48bc85/Library/Caches/com.apple.xbs/Sources/MetalPerformanceShaders/MPSCore/Types/MPSNDArray.mm:705: failed assertion `[MPSTemporaryNDArray initWithDevice:descriptor:] Error: product of dimension sizes > 2**31'
./run_webui_mac.sh: line 18:  2893 Abort trap: 6           python webui.py --precision full --no-half --use-cpu Interrogate GFPGAN CodeFormer $@
/opt/homebrew/Caskroom/miniconda/base/envs/web-ui/lib/python3.10/multiprocessing/resource_tracker.py:224: UserWarning: resource_tracker: There appear to be 1 leaked semaphore objects to clean up at shutdown
  warnings.warn('resource_tracker: There appear to be %d '

```



### Steps to reproduce the problem

1. Launch Automatic1111 via CLI 
2. Go to .... Automatic1111, generate 512x512 and 512x768 images fine
3. Press ....Change width to 1024 (keep x 512), generate image, 'Automatic crashes in Terminal and shows error



### What should have happened?

Images should produce normally.

### Commit where the problem happens

 98947d1

### What platforms do you use to access UI ?

MacOS

### What browsers do you use to access the UI ?

Apple Safari

### Command Line Arguments

```Shell
cd stable-diffusion-webui && ./run_webui_mac.sh  --disable-safe-unpickle --autolaunch
```


### Additional information, context and logs

_No response_
Repository: pytorch
Issue: code sharing for fundamental ops in quantization
Labels: oncall: quantization,triaged

### 🐛 Describe the bug

As @vkuzo mentioned in https://github.com/pytorch/pytorch/pull/89269#discussion_r1026672280 we should share the code for ops that's critical for numerics in quantization, such as quantize_per_tensor, quantize_per_channel, fake quantize, and dequantize ops, this will help us to have identical numerics across different flows (QAT, PTQ) and different APIs (convert_to_reference_fx, _convert_to_reference_decomposed_fx)

### Versions

master

cc @jianyuh @raghuramank100 @jamesr66a @vkuzo @jgong5 @Xia-Weiwen @leslie-fang-intel
Repository: PowerToys
Issue: Maximum shaking distance option - Mous tool -> Find my mous
Labels: Idea-Enhancement,Needs-Triage,Product-Mouse Utilities

### Description of the new feature / enhancement

To the "Find my mous" in the mous tool, add a maximum shaking distance like the minimum shaking distance option for the activation method. 

### Scenario when this would be used?

Because like that we can set a precise speed of movement to find our mous and it allows to do major movement with our mous (to show something in screen-sharing in example) without activate the "find my mous" feature needlessly.


### Supporting information

_No response_
Repository: vscode
Issue: Sticky scroll messes up accurate markdown scroll sync
Labels: bug,markdown,editor-sticky-scroll

1. With stick scroll enabled
2. Open the md file:
```md
# h1
# h2
# h3
# h4
# h5
# h6
# h7
```
3. Open markdown preview to side
4. Scroll the preview slowly down to the bottom of the content 

**Bug**
Notice how the editor only scroll when you reach `h7`

I believe this is happening because of this logic for sticky scrolling : https://github.com/microsoft/vscode/blob/39911aac41bc0fc65118ec91ecc918cc053be3de/src/vs/editor/browser/viewParts/lines/viewLines.ts#L683
Repository: next.js
Issue: Dynamic Imports Cause Hydration Error With Babel
Labels: bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

    Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.1.0: Sun Oct  9 20:15:09 PDT 2022; root:xnu-8792.41.9~2/RELEASE_ARM64_T6000
    Binaries:
      Node: 18.12.1
      npm: 8.19.2
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 13.0.4
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0


### What browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_

### Describe the Bug

I first encountered this in a more complicated application where it manifested as a react hydration error. I created a minimal reproducible example (https://github.com/davidgolden/next-dynamic-minimal-bug) where it manifests as the dynamically imported component rendering on the screen twice. We haven't upgraded to SWC quite yet, but just upgraded from next@10.2.3 where everything was working fine to next@13.0.4. We've been using @babel/plugin-syntax-dynamic-import successfully with dynamic imports in Next for years.

I'm not sure if this is a bug or not because obviously we are not using the latest recommended Next config (not on SWC yet), but it seems strange to me that we'd need to add that plugin to get dynamic imports to work. I'm having trouble understanding what exactly that plugin is doing, so maybe that is the key.

### Expected Behavior

Dynamic imports should not cause imported component to render multiple times or cause hydration errors.

### Link to reproduction - Issues with a link to complete (but minimal) reproduction code will be addressed faster

https://github.com/davidgolden/next-dynamic-minimal-bug

### To Reproduce

Steps to reproduce:

```
git clone https://github.com/davidgolden/next-dynamic-minimal-bug.git
cd next-dynamic-minimal-bug
npm ci
npm run start
```

You will see "Hello World" rendered to the screen twice at localhost:3000. If you uncomment the `react-loadable-plugin` babel plugin in `babel.config.js` then "Hello World" will correctly only be rendered once.
Repository: go
Issue: x/exp/cmd/gorelease: hangs
Labels: NeedsInvestigation

<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.19.3 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/ben/.cache/go-build"
GOENV="/home/ben/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/ben/.gvm/pkgsets/go1.19.3/global/pkg/mod"
GONOPROXY="source.vivint.com,gitlab.com/vivint"
GONOSUMDB="source.vivint.com,gitlab.com/vivint"
GOOS="linux"
GOPATH="/home/ben/.gvm/pkgsets/go1.19.3/global"
GOPRIVATE="source.vivint.com,gitlab.com/vivint"
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/home/ben/.gvm/gos/go1.19.3"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/ben/.gvm/gos/go1.19.3/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.19.3"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/ben/vivint/PL/platformusers/go.mod"
GOWORK=""
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 -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build1894158366=/tmp/go-build -gno-record-gcc-switches"

</pre></details>

### What did you do?

Running gorelease on most of our internal software takes 3-5 minutes and works as expected. On one particular repo it will hang for an hour with no response. I recognize that this gives no information to solve the issue. Is there a way to get debug output that would be helpful?
Repository: terminal
Issue: [Feature Request] Option to auto trim leading/ending new lines/spaces from pasted content
Labels: Issue-Feature,Help Wanted,Area-Settings,Product-Terminal

<!-- 
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨

I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement.
2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement.
3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number).
4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement.
5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement.

All good? Then proceed!
-->

# Description of the new feature/enhancement

Simple feature quest, to add an option to automatically trim spaces and/or new lines from pasted text.

I'm constantly copying stuff, pasting in the terminal and having to go with my arrow keys to erase unnecessary chars so that my commands work.

# Proposed technical implementation details (optional)

We can have these options:

1) Trim new lines
2) Trim spaces

a) Trim leading
b) Trim ending

Maybe it should display as two ComboBoxes:

New line trimming: Disabled/Leading/Ending/Both
Space trimming: Disabled/Leading/Ending/Both
Repository: godot
Issue: Popups (Color-Picker / Menu) stay open when Alt-Tabbing to other Window
Labels: bug,topic:gui

### Godot version

v4.0.beta.custom_build [d93bec61c]

### System information

Linux X11 Xfce

### Issue description

When Alt-Tabbing to a different Window, Popups like the Color-Picker or Menus stay open when Single-Window-Mode is off.

I was not able to reproduce this on Windows, but using the method described in #68197, it might be possible to reproduce it even there.

A solution should likely investigate #68447.

### Steps to reproduce

In the following video I
1) open in the editor the color-picker,
2) use Alt-Tab to switch to a different Window.

After _2._ the color-picker is visible above the Window, that I switched to, even though it should not be.

https://user-images.githubusercontent.com/6299227/200845883-b00c778a-273e-4e97-b6dc-7b0143eb7faf.mp4

### Minimal reproduction project

Reproducible in Editor
Repository: vscode
Issue: Typing when simple filtering is enabled in the explorer should center the item
Labels: feature-request,file-explorer

This would make it a lot more usable, currently I often need to press down several times to get the context.

![Recording 2022-11-18 at 12 56 19](https://user-images.githubusercontent.com/2193314/202800916-1764081a-a5a5-4780-bd80-02ba4a61b498.gif)