sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Godot v4.0-beta1 dotnet doesn't support some nuget dependencies
Labels: bug,topic:dotnet

### Godot version

Godot_v4.0-beta1_mono_linux.x86_64 official build

### System information

Linux Fedora 35, Vulkan, NVIDIA GeForce 940MX (Driver Version: 515.65.01)

### Issue description

Hello. I have a working standalone dotnet project that depends on the nuget package `Microsoft.DotNet.Interactive.CSharp`, and uses the code `new Microsoft.DotNet.Interactive.CSharp.CSharpKernel();`.  When I try to use the same dependency and code in `Godot_v4.0-beta1_mono_linux.x86_64` it builds fine but at runtime it gives some error and doesn't work. While searching for a fix online I tried adding any possible nuget dependency I could find without success. Sometimes after one of these dependencies was added the first error was replaced by another error.

Actually I'm not sure if this is a bug, or something that requires a workaround, or some expected limitation of the dotnet that Godot 4 Beta1 supports. In the latter cases, maybe it should be documented?

### Steps to reproduce

1. Launch `Godot_v4.0-beta1_mono_linux.x86_64` and create a new project.
2. Attach a C# script to a node.
3. In `.csproj` file add the following dependency:
   ```xml
   <PackageReference Include="Microsoft.DotNet.Interactive.CSharp" Version="1.0.0-beta.22452.2" />
   ```
4. In `.cs` file, inside `public override void _Ready() {...}`, add the following line:
   ```csharp
   var kernel = new Microsoft.DotNet.Interactive.CSharp.CSharpKernel();
   ```
5. Build and run project: the following error should happen:

```
ERROR: System.NotSupportedException: Can't create a metadata reference to an assembly without location.
   at Microsoft.CodeAnalysis.MetadataReference.CreateFromAssemblyInternal(Assembly assembly, MetadataReferenceProperties properties, DocumentationProvider documentation)
   at Microsoft.CodeAnalysis.Scripting.ParameterValidationHelpers.<>c__DisplayClass4_0`2.<SelectChecked>b__0(T item)
   at System.Linq.Enumerable.SelectArrayIterator`2.MoveNext()
   at Microsoft.CodeAnalysis.Scripting.ParameterValidationHelpers.AddRangeChecked[T](ArrayBuilder`1 builder, IEnumerable`1 items, String parameterName)
   at Microsoft.CodeAnalysis.Scripting.ScriptOptions.AddReferences(IEnumerable`1 references)
   at Microsoft.DotNet.Interactive.CSharp.CSharpKernel..ctor(String name)
   ...
```
In a plugin instead of a scene the error would be the same (but with the stacktrace printed to the terminal).

### Minimal reproduction project

[new_godot_project.zip](https://github.com/godotengine/godot/files/9602769/new_godot_project.zip)
Repository: stable-diffusion-webui
Issue: CLIP guided Stable Diffusion
Labels: enhancement

**Is your feature request related to a problem? Please describe.**
It would be great to add support for using [CLIP](https://huggingface.co/models?search=clip+laion) in WebUI. It seems to have [better results](https://twitter.com/psuraj28/status/1571886160137306112) at the cost of more processing time.

**Describe the solution you'd like**
an option that allows using CLIP in the image generation tabs.

**Additional context**
[Here](https://colab.research.google.com/github/huggingface/notebooks/blob/main/diffusers/CLIP_Guided_Stable_diffusion_with_diffusers.ipynb) is an implementation.
Repository: PowerToys
Issue: Type-Box Popup Menu Too Much in the Way
Labels: Issue-Bug,Product-PowerRename,Priority-3

### Microsoft PowerToys version

0.62.1

### Running as admin

- [X] Yes

### Area(s) with issue?

PowerRename

### Steps to reproduce


![Screenshot](https://user-images.githubusercontent.com/113954560/191147319-5b8b06e3-e445-45d7-bdd4-df89d9a60811.jpg)


### ✔️ Expected Behavior

A standard type-in box experience.

### ❌ Actual Behavior

- The dropdown menu gets in the way.
- The history isn't delete-able
- There can be a suggested autofill feature added.

### Other Software

_No response_
Repository: material-ui
Issue: No type information for styles inside `[theme.breakpoints.down()]` object
Labels: typescript,status: expected behavior

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

Steps:

1. Write the following styled button:
```
export const StyledButton = styled('button')(({ theme }) => ({
    width: '100%',

    [theme.breakpoints.down('md')]: {
    }
}));
```
2. Start writing `width: 50%` inside the `[theme.breakpoints.down('md')]` styles. Notice how there are no CSS completions such as the ones provided outside that object.


### Current behavior 😯

No CSS completions inside `[theme.breakpoints.down('XX')]` objects.

### Expected behavior 🤔

CSS completions are always displayed when using `styled`.

### Context 🔦

_No response_

### Your environment 🌎

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  Browser used: Chrome

  System:
    OS: macOS 12.6
  Binaries:
    Node: 16.17.0 - /private/var/folders/kq/jlq8006j7tg9d32d8frd8w800000gn/T/xfs-69364989/node
    Yarn: 3.2.3 - /private/var/folders/kq/jlq8006j7tg9d32d8frd8w800000gn/T/xfs-69364989/yarn
    npm: 8.15.0 - ~/.nvm/versions/node/v16.17.0/bin/npm
  Browsers:
    Chrome: 105.0.5195.125
    Edge: Not Found
    Firefox: Not Found
    Safari: 16.0
```
</details>

<details>
   <summary><code>tsconfig.json</code> file</summary>

```
    {
    "include": [
        "next-env.d.ts",
        "next.config.mjs",
        "**/*.ts",
        "**/*.tsx"
    ],
    "exclude": [
        "node_modules"
    ],
    "compilerOptions": {
        // Type checking
        "allowUnreachableCode": false,
        "allowUnusedLabels": false,
        "noFallthroughCasesInSwitch": true,
        "noImplicitAny": true,
        "noImplicitOverride": true,
        "noImplicitReturns": true,
        "noImplicitThis": true,
        "noPropertyAccessFromIndexSignature": true,
        "noUncheckedIndexedAccess": true,
        "noUnusedLocals": true,
        "noUnusedParameters": true,
        "strict": true,

        // Modules
        "module": "esnext",
        "moduleResolution": "nodenext",
        "resolveJsonModule": true,

        // Emit
        "importHelpers": true,
        "importsNotUsedAsValues": "error",
        "removeComments": true,
        "sourceMap": true,
        "noEmit": true,

        // JS support
        "allowJs": true,
        "checkJs": true,

        // Interop constraints
        "esModuleInterop": true,
        "isolatedModules": true,
        "forceConsistentCasingInFileNames": true,

        // Language and environment
        "target": "ESNext",
        "jsx": "preserve",
        "lib": [
            "dom",
            "dom.iterable",
            "esnext"
        ],

        // Projects
        "incremental": true,

        // Completeness
        "skipLibCheck": true
    }
}
```
</details>
Repository: go
Issue: all: test failures using proxy.golang.org
Labels: NeedsInvestigation,proxy.golang.org

```
#!watchflakes
default <- (`(Get|read) \\?"https://?proxy.golang.org/` ||
	(section == "go test -short ./..." && test == "" && log ~ `(Get|read) "https://?proxy.golang.org/`)) &&
	(builder != "plan9-arm" && builder != "plan9-386-0intro" && builder != "plan9-amd64-0intro")
```
Various tests flake because they use proxy.golang.org 
(sometimes the URLs get path.Cleaned and only use one slash in https://).
Repository: go
Issue: all: test failures using non-golang.org proxies
Labels: NeedsInvestigation

```
#!watchflakes
default <- `(Get|read(ing)?) "?https://?(goproxy.io|proxy.golang.com.cn|goproxy.cn)`
```

Various tests flake because they use proxies other than proxy.golang.org
(sometimes the URLs get path.Cleaned and only use one slash in https://).
See also #55162.
Repository: go
Issue: cmd/go: test failures due to network
Labels: NeedsInvestigation

```
#!watchflakes
post <- (pkg ~ `^cmd/go` || pkg ~ `^golang.org/x/mod`) && (
	`Failed to connect to github.com port 443: Connection refused` ||
	`remote: Internal Server Error.` ||
	`error: RPC failed; HTTP 500` ||
	`GnuTLS recv error` ||
	`The TLS connection was non-properly terminated` ||
	`connect: network is unreachable` ||
	`502 Bad Gateway` ||
	`remote: Repository not found.` ||
	`The requested URL returned error: 50\d` ||
	`system library:.*:Connection reset by peer` ||
	`dial tcp .*: i/o timeout` ||
	`Failed to connect to .* port .*: Connection timed out` ||
	`Failed to connect to .* port .*: Operation timed out` ||
	`Empty reply from server` ||
	`Could not resolve host:` ||
	`Failed to connect to .* port 443 .*: Couldn't connect to server` ||
	`read: connection reset by peer`)
```

cmd/go's tests flake when the network is having trouble (or the servers on the other end are).
This should only happen on the longtest builders.
This issue gathers reports so we can watch the frequency.
Repository: go
Issue: all: test failures due to windows dns errors
Labels: NeedsInvestigation

```
#!watchflakes
post <- goos == "windows" && 
        (`dnsquery: DNS server failure` || `getaddrinfow: This is usually a temporary error`)
```
Windows builders occasionally have problems with DNS resolution.
Repository: go
Issue: all: ignored builders for test flakes reporting
Labels: NeedsDecision

```
#!watchflakes
skip <-
	builder ~ `android-.*-emu` && date != "" && date < "2022-12-05" ||
	builder ~ `^darwin-.*-aws` && date != "" && date < "2022-12-05" ||
	builder == "dragonfly-amd64-622" && date != "" && date < "2022-09-01" ||
	builder == "freebsd-arm-paulzhol" && date != "" && date < "2022-12-01"||
	builder == "linux-amd64-alpine" && date != "" && date < "2022-09-01" ||
	builder == "linux-amd64-unified" && date != "" && date < "2022-12-01" ||
	builder == "linux-loong64-3a5000" && date != "" && date < "2022-12-01" ||
	builder ~ `^netbsd.*-9_0` ||
	builder ~ `^netbsd.*` && date != "" && date < "2022-10-12" ||
	builder ~ `^plan9-(386|amd64)` ||
	builder == "plan9-arm" && date != "" && date < "2022-12-01" ||
	builder == "solaris-amd64-oraclerel" && date != "" && date < "2022-11-29" ||
	builder ~ `.*-newcc.*` && date != "" && date < "2022-12-01" ||
	builder == "windows-arm64-11" && date != "" && date < "2022-12-01" ||
	builder == "linux-amd64-wsl" && date != "" && date < "2023-05-01" ||
	builder == "wasip1-wasm-wasmedge" ||
	builder == "wasip1-wasm-wasmer" ||
	builder == "wasip1-wasm-wasmtime" ||
	builder == "openbsd-ppc64-n2vi"
```

This issue defines policy (above) for which builders are entirely ignored for flake finding.
Repository: go
Issue: runtime: corruption in tests
Labels: NeedsInvestigation,compiler/runtime

```
#!watchflakes
default <- (log ~ `runtime.throw\(` || log ~ `^\s*fatal error:`) &&
	builder != "plan9-386-0intro" &&
	builder != "plan9-amd64-0intro" &&
	builder != "plan9-arm" &&
	builder != "linux-loong64-3a5000" &&
	!(builder ~ `(gotip|go1\.\d\d)-` && date < "2024-01-18")
```

This issue gathers flakes caused by runtime.throw, which should "never happen" and usually indicates some kind of corruption.
Repository: go
Issue: x/exp/jsonrpc2: TestServe failures
Labels: NeedsInvestigation

```
#!watchflakes
post <- pkg == "golang.org/x/exp/jsonrpc2" && test == "TestServe"
```

Bug automatically created to track these flakes.

— watchflakes
Repository: go
Issue: x/tools/internal/jsonrpc2: TestIdleTimeout failures
Labels: NeedsFix,Tools

```
#!watchflakes
post <- pkg == "golang.org/x/tools/internal/jsonrpc2" && test == "TestIdleTimeout"
```

Bug automatically created to track these flakes.

— watchflakes
Repository: go
Issue: x/build/cmd/coordinator: TestFindWork failures
Labels: Builders,NeedsInvestigation

```
#!watchflakes
post <- pkg == "golang.org/x/build/cmd/coordinator" && test == "TestFindWork"
```

Bug automatically created to track these flakes.

— watchflakes
Repository: go
Issue: net/http: TestServerSetKeepAlivesEnabledClosesConns failures
Labels: NeedsInvestigation

```
#!watchflakes
post <- pkg == "net/http" && test == "TestServerSetKeepAlivesEnabledClosesConns"
```

Bug automatically created to track these flakes.

— watchflakes
Repository: go
Issue: x/build/internal/workflow: TestWatchdog failures
Labels: Builders,NeedsInvestigation

```
#!watchflakes
post <- pkg == "golang.org/x/build/internal/workflow" && test == "TestWatchdog"
```

Bug automatically created to track these flakes.

— watchflakes
Repository: go
Issue: runtime: TestSpuriousWakeupsNeverHangSemasleep failures
Labels: NeedsInvestigation,compiler/runtime

```
#!watchflakes
post <- pkg == "runtime" && test == "TestSpuriousWakeupsNeverHangSemasleep"
```

Bug automatically created to track these flakes.

— watchflakes
Repository: go
Issue: net: TestUDPServer failures
Labels: NeedsInvestigation

```
#!watchflakes
post <- pkg == "net" && test == "TestUDPServer"
```

Bug automatically created to track these flakes.

— watchflakes
Repository: go
Issue: x/vulndb: TestChecksBash failures
Labels: NeedsInvestigation,FrozenDueToAge,vulncheck or vulndb

```
#!watchflakes
post <- pkg == "golang.org/x/vulndb" && test == "TestChecksBash"
```

Bug automatically created to track these flakes.

— watchflakes
Repository: go
Issue: net: TestDialParallelSpuriousConnection failures on darwin/arm64 and ios/arm64
Labels: OS-Darwin,NeedsInvestigation,arch-arm64

```
#!watchflakes
post <- builder ~ `^(darwin|ios)-.*arm` && pkg == "net" && test == "TestDialParallelSpuriousConnection"
```

Bug automatically created to track these flakes.

— watchflakes
Repository: go
Issue: net/http: TestTransportReading100Continue failures
Labels: NeedsInvestigation

```
#!watchflakes
post <- pkg == "net/http" && test == "TestTransportReading100Continue"
```

Bug automatically created to track these flakes.

— watchflakes
Repository: go
Issue: x/net/bpf: failures about BPF packet outputs not matching
Labels: NeedsInvestigation

```
#!watchflakes
post <- pkg == "golang.org/x/net/bpf" && `Go BPF and OS BPF packet outputs do not match`
```

Bug automatically created to track these flakes.

— watchflakes
Repository: opencv
Issue: opencv videoio error
Labels: question (invalid tracker),incomplete

I run other application which uses opencv and got below error. Not sure what does the error mean, any hints? Thanks!

[ WARN:0@0.519] global /usr/src/debug/opencv/4.5.5-r0/git/modules/videoio/src/cap_gstreamer.cpp (1813) close_ OpenCV | GStreamer warning: No source in GStreamer pipeline. Ignore
[ERROR:0@0.519] global /usr/src/debug/opencv/4.5.5-r0/git/modules/videoio/src/cap.cpp (595) open VIDEOIO(GSTREAMER): raised OpenCV exception:

OpenCV(4.5.5) /usr/src/debug/opencv/4.5.5-r0/git/modules/videoio/src/cap_gstreamer.cpp:147: error: (-215:Assertion failed) ptr in function 'get'
Repository: pytorch
Issue: Crash in `torch.package.PackageExporter`
Labels: module: crash,triaged,oncall: package/deploy,imported,module: edge cases

### 🐛 Describe the bug

Passing invalid input to `f` or `importer` in `torch.package.PackageExporter`, can causes a crash with Aborted (core dumped).
## code

```python
import torch

torch.package.PackageExporter(f=1, importer=1)
```

## output
```bash
terminate called after throwing an instance of 'pybind11::error_already_set'
  what():  AttributeError: 'int' object has no attribute 'write'
Aborted (core dumped)
```

### Versions

PyTorch version: 1.12.1+cu102
Is debug build: False
CUDA used to build PyTorch: 10.2
ROCM used to build PyTorch: N/A

OS: Ubuntu 20.04.4 LTS (x86_64)
GCC version: (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
Clang version: Could not collect
CMake version: Could not collect
Libc version: glibc-2.31

Python version: 3.8.10 (default, Jun 22 2022, 20:18:18) [GCC 9.4.0] (64-bit runtime)
Python platform: Linux-5.4.0-117-generic-x86_64-with-glibc2.29
Is CUDA available: False
CUDA runtime version: No CUDA
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

Versions of relevant libraries:
[pip3] numpy==1.18.5
[pip3] torch==1.12.1
[conda] Could not collect
Repository: flutter
Issue: WGSL Compute Shaders support
Labels: c: new feature,engine,c: proposal,P3,team-engine,triaged-engine

## Use case
Push expensive math operations on GPU, enrich the newly added shader feature in Flutter 3.3.0

## Proposal
Implement WGSL specs [https://www.w3.org/TR/WGSL/](url)
Repository: PowerToys
Issue: [Screen Ruler] Add horizontal scroll
Labels: Issue-Feature,Product-Screen Ruler

### Description of the new feature / enhancement

When using the screen ruler, using the vertical scroll on the mouse adjusts the vertical ruler. Using the horizontal scroll should adjust the horizontal ruler

### Scenario when this would be used?

An increasing number of mice have a horizontal scroll wheel, this would be useful for them.

### Supporting information

_No response_
Repository: neovim
Issue: incommand with `c` flag (confirm) to `:substitute`
Labels: enhancement,inccommand

### Feature already in Vim?

I don't think so

### Feature description

When writing a substitution we can use `inccommand` to preview the changes in the buffer and/or in a split, which is really great! The if you add the `c` flag to the substitution command to confirm each substitution you no longer have a preview for what the substitution will be when the confirm dialog is active.

I think it would be really useful if one could preview the changes before confirming a substitution, maybe either as virtual text or in the split used by `inccommand`.

Would this make sense? If so, would it fit in core or better in a plugin? I'd be happy to try to work on this if it sounds like a good idea. Although I don't know in detail how to do it yet.
Repository: go
Issue: x/build/cmd/watchflakes, cmd/go: flaky test timeout
Labels: Builders,NeedsInvestigation

```
#!watchflakes
post <- pkg == "cmd/go" && test == "" && `panic: test timed out`
```

Bug automatically created to track these flakes.

— watchflakes
Repository: go
Issue: x/build/cmd/watchflakes, x/net/http2: flaky test timeout
Labels: Builders,NeedsInvestigation

```
#!watchflakes
post <- pkg == "golang.org/x/net/http2" && test == "" && `panic: test timed out`
```

Bug automatically created to track these flakes.

— watchflakes
Repository: ant-design
Issue: onFinishFailed called with outOfDate: true with a custom form control
Labels: Inactive,improvement

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/antd-reproduction-template-forked-1nj4pi)

### Steps to reproduce

In the codesandbox example, click on the "fill" button to put a valid URL in the form
There is still an error caused by the hidden 'fake' field, but the corresponding rule is marked as warningOnly so this should not cause submit error
Click on the submit button : error!


### What is expected?

Since the rule on the 'fake' field is marked as warningOnly, and the 'url' field is valid, the submit should be a success

### What is actually happening?

submit fails with no error and the property "outOfDate" to true

| Environment | Info |
| --- | --- |
| antd | 4.23.0 |
| React | 18.2.0 |
| System | Windows 10 |
| Browser | Chrome 105.0.5195.127 |

---
I think the issue comes from the special component FakeFormControl in the codesandbox example
For us this component is a way to intergrate multiple data from different sources and consider them as one and only form
Not really the usual usecase but this was working in version 4.22.8 :-D

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: PowerToys
Issue: Find my mouse: set spotlight duration
Labels: Help Wanted,Cost-Small,Product-Mouse Utilities

### Description of the new feature / enhancement

I should be able to set the duration the spotlight appears.

### Scenario when this would be used?

There exists a delicate balance in the universe: Shake minimum distance. Too much distance, and you look like a crazed maniac shaking your mouse to find it. Too little distance, and your screen flashes like the WOPR learning that nobody wins at Global Thermonuclear War[^1]. If the spotlight duration could be specified, the interruption would be brief, and the cost for a lower Shake minimum distance would be reduced[^2].
[^1]https://www.theaceblackblog.com/2016/10/movie-review-wargames-1983.html
[^2]Yes, I realize the screen would flash more like the War Games movie scene, however, the visualization was too good to resist using the analogy.



### Supporting information

_No response_
Repository: go
Issue: cmd/go: test tmpdir failure
Labels: NeedsFix,GoCommand

```
#!watchflakes
post <- pkg == "cmd/go" && test == "" && `unexpected files left in tmpdir` && `vcstest\d+`
```

Bug automatically created to track these flakes.

— watchflakes
Repository: go
Issue: runtime/trace: flaky test crash
Labels: NeedsInvestigation,FrozenDueToAge,compiler/runtime

```
#!watchflakes
post <- pkg == "runtime/trace" && test == "" && !`panic: test timed out`
```

Bug automatically created to track these flakes.

— watchflakes
Repository: godot
Issue: Error when using AnimationNodeStateMachinePlayback.start(state_string)
Labels: bug,topic:animation

### Godot version

3.5.stable.official

### System information

Windows 10, GLES3

### Issue description

When attempting to use the start(state_string) function on an AnimationNodeStateMachinePlayback, the bnimation does not play and the following error occurs:
```
 scene/animation/animation_tree.cpp:68 - Condition "!state->tree->property_parent_map.has(base_path)" is true. Returned: Variant()
 scene/animation/animation_tree.cpp:59 - Condition "!state->tree->property_parent_map.has(base_path)" is true.
```
This problem occurs when, in my plugin, I have a project defaulted to 8-directions, then another character that needs on 4-directions.  When I switch to 4-directions and set up the state, as soon as the animations are generated and .start(state_string) is called, this error pops every frame until the animation is no longer being played.

(Submitted by request of iFire on Godot Discord)

### Steps to reproduce

1) Add the plugin to Godot Engine and activate it.
2) Do the First Time Setup (documentation is linked on the First Time Setup popup), choosing 8-direction as the project type
3) Create a character
4) Set up a state for the character (Edit State button) with a texture, generate the animations, save & close
5) Switch the defaults to 4-direction (right side of the interface, 'Edit Defaults' button)
6) Make another character
7) Set up the same state & generate animations
8) Error pops

I apologize in advance for the complexity of the attached project, but I could not find a way to reproduce it minimally.  However, I believe the issue is tied to the way the AnimationTree is being handled.  The Engine does not seem to be clearing a cache or perhaps  is not allowing AnimationTree > AnimationNodeBlendTree > StateMachine nodes to be unique despite having 'Local to Scene' checked.  This is exemplified in the attached plugin project when creating a new character, then editing the base character's AnimationTree > AnimationNodeBlendTree >StateMachine.  Changes made will be reflected in all State Machines in all characters created in the plugin.

### Minimal reproduction project

[AutoAnimGenerator.zip](https://github.com/godotengine/godot/files/9608234/AutoAnimGenerator.zip)
Repository: godot
Issue: Crash when CSGMesh gets a CylinderMesh assigned
Labels: bug,platform:android,topic:core,crash,topic:3d

### Godot version

4.0beta1

### System information

Poco F2 pro

### Issue description

If you create a CSGMesh and assign it a CylinderMesh the engine will crash instantly

### Steps to reproduce

Create a 3D scene
Add a CSGMesh
Assign it a CylinderMesh -> Crash

### Minimal reproduction project

https://user-images.githubusercontent.com/96994272/191315800-71d23ae9-df88-4da1-8e43-af4db63f1100.mp4