sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: generic_const_exprs breaks object safety
Labels: T-compiler,C-bug,A-const-generics,F-generic_const_exprs,T-types

I know that `generic_const_exprs` is still incomplete, so feel free to close the issue if this bug is already known and/or covered by already planned parts of the implementation.

But just in case it helps, I found a case where enabling `generic_const_exprs` breaks object safety detection if the trait references a constant.

Here's the code:

```rust
#![allow(dead_code, incomplete_features)]
#![feature(generic_const_exprs)] // no error without this

const COUNT: usize = 2;

pub trait WithoutConstant {
    fn foo(&self, x: &[u8; 2]);
}

pub trait WithConstant {
    fn foo(&self, x: &[u8; COUNT]);
}

// no error
fn without_constant(y: &dyn WithoutConstant) {
    y.foo(&[0; COUNT]);
}

// error[E0038]: the trait `WithConstant` cannot be made into an object
fn with_constant(y: &dyn WithConstant) {
    y.foo(&[0; COUNT]);
}

fn main() {
    println!("Hello, world!");
}
```

This should compile, and without `generic_const_exprs`, it does, but when I enable the feature, I get this error:

```
error[E0038]: the trait `WithConstant` cannot be made into an object
  --> src/main.rs:20:22
   |
20 | fn with_constant(y: &dyn WithConstant) {
   |                      ^^^^^^^^^^^^^^^^ `WithConstant` cannot be made into an object
   |
note: for a trait to be "object safe" it needs to allow building a vtable to allow the call to be resolvable dynamically; for more information visit <https://doc.rust-lang.org/reference/items/traits.html#object-safety>
  --> src/main.rs:11:22
   |
10 | pub trait WithConstant {
   |           ------------ this trait cannot be made into an object...
11 |     fn foo(&self, x: &[u8; COUNT]);
   |                      ^^^^^^^^^^^^ ...because method `foo` references the `Self` type in this parameter
   = help: consider moving `foo` to another trait

For more information about this error, try `rustc --explain E0038`.
error: could not compile `generic_const_expr_repro` (bin "generic_const_expr_repro") due to previous error
```

### Meta

`rustc --version --verbose`:
```
rustc 1.71.0-nightly (8bdcc62cb 2023-04-20)
binary: rustc
commit-hash: 8bdcc62cb0362869f0e7b43a6ae4f96b953d3cbc
commit-date: 2023-04-20
host: aarch64-apple-darwin
release: 1.71.0-nightly
LLVM version: 16.0.2
```
Repository: transformers
Issue: Need support for Sentence Similarity Pipeline
Labels: Feature request

### Feature request

HuggingFace now has a lot of Sentence Similarity models, but the pipeline does not yet support this: https://huggingface.co/docs/transformers/main_classes/pipelines

### Motivation

HuggingFace now has a lot of Sentence Similarity models, but the pipeline does not yet support this: https://huggingface.co/docs/transformers/main_classes/pipelines

### Your contribution

I can write a PR, but might need some one else's help.
Repository: godot
Issue: Shapecasting beneath a one-way tilemap collision stops the shapecast
Labels: bug,topic:physics,topic:2d

### Godot version

4.0 beta 14

### System information

Windows 10

### Issue description

Shapecasting from under a one-way tile cause the shapecast to be interrupted, which shouldn't happen unless the shapecast is aiming downwards through the one-way tile.

### Steps to reproduce

- Add a shapecast2d node
- Add a tilemap with tiles using one-way collisions.
- Fire the shapecast upwards through the one-way tile
- The shapecast will register the tile.

### Minimal reproduction project

[shapecastus_interruptus.zip](https://github.com/godotengine/godot/files/11298772/shapecastus_interruptus.zip)

[shapecastus_interruptus_with_ray.zip](https://github.com/godotengine/godot/files/11298771/shapecastus_interruptus_with_ray.zip)
Repository: storybook
Issue: [Bug]: `preview` `decorators` ignored if `preview` uses top-level await
Labels: feature request,help wanted,core

### Describe the bug

If the `preview` file (or more likely a file it depends on directly or transitively) uses top-level await, then the `decorators` it exports (whether directly or as part of a `export default preview`) are not run.
This need not necessarily be considered a bug, because setting `experiments.topLevelAwait` is likely not technically a supported use case by Storybook, but wanted to make y'all aware of it already because probably at some point it will be supported (and aside from this bug already seems to work quite well).

### To Reproduce

* Check out https://github.com/jeysal/sbrepro
* `yarn install && yarn storybook`
* Open the button story
* Observe that there is no red background (which the decorator should create)

To further confirm:
* Comment out the first line (top-level `await`) in `preview.js`
* Observe that the red background appears

### System

```shell
Environment Info:

  System:
    OS: Linux 6.2 Arch Linux
    CPU: (16) x64 AMD Ryzen 9 5900HS with Radeon Graphics
  Binaries:
    Node: 18.15.0 - ~/.nvm/versions/node/v18.15.0/bin/node
    Yarn: 1.22.19 - /usr/bin/yarn
    npm: 9.5.0 - ~/.nvm/versions/node/v18.15.0/bin/npm
  Browsers:
    Firefox: 112.0
  npmPackages:
    @storybook/addon-essentials: ^7.0.6 => 7.0.6 
    @storybook/addon-interactions: ^7.0.6 => 7.0.6 
    @storybook/addon-links: ^7.0.6 => 7.0.6 
    @storybook/blocks: ^7.0.6 => 7.0.6 
    @storybook/react: ^7.0.6 => 7.0.6 
    @storybook/react-webpack5: ^7.0.6 => 7.0.6 
    @storybook/testing-library: ^0.0.14-next.2 => 0.0.14-next.2 
```
```


### Additional context

_No response_
Repository: flutter
Issue: device doctor healthcheck error: b"error: protocol fault"
Labels: team-infra,P3,triaged-infra

We are seeing this error pop up temporarily on bots in our devicelab pools (e.g. https://chromium-swarm.appspot.com/botlist?c=id&c=task&c=os&c=status&d=asc&f=pool%3Aluci.flutter.staging&s=id). It goes away in a few seconds.

```Quarantined: device doctor healthcheck error: b"error: protocol fault (couldn't read status): Connection reset by peer\nUnhandled exception:\nExecutable adb failed with exit code 1.\n#0 fail (package:device_doctor/src/utils.dart:33)\n#1 eval (package:device_doctor/src/utils.dart:105)\n<asynchronous suspension>\n#2 Future.timeout.<anonymous closure> (dart:async/future_impl.dart:870)\n<asynchronous suspension>\n#3 AndroidDeviceDiscovery._deviceListOutputWithRetries.<anonymous closure> (package:device_doctor/src/android_device.dart:54)\n<asynchronous suspension>\n#4 RetryOptions.retry (package:retry/retry.dart:131)\n<asynchronous suspension>\n#5 AndroidDeviceDiscovery._deviceListOutputWithRetries (package:device_doctor/src/android_device.dart:52)\n<asynchronous suspension>\n#6 AndroidDeviceDiscovery.discoverDevices (package:device_doctor/src/android_device.dart:74)\n<asynchronous suspension>\n#7 AndroidDeviceDiscovery.checkDevices (package:device_doctor/src/android_device.dart:104)\n<asynchronous suspension>\n#8 main (file:///b/s/w/ir/x/w/cocoon/device_doctor/bin/main.dart:67)\n<asynchronous suspension>\n"```
Repository: pytorch
Issue: cuda 12.0 support request for building pytorch from source code
Labels: module: build,module: cuda,triaged,enhancement

### 🚀 The feature, motivation and pitch

Motivation:
      It does support cuda 12.1, but it does not support cuda 12.0
     According to the doc: https://github.com/pytorch/pytorch#from-source , the magma-cuda* that does not match the CUDA version 12.0 from https://anaconda.org/pytorch/repo. Only magma-cuda121 can be found, no magma-cuda120

feature: please support cuda 12.0 for building pytorch from source code

Thank you!

### Alternatives

_No response_

### Additional context

_No response_

cc @malfet @seemethere @ngimel
Repository: vscode
Issue: TreeError [SearchView] Unknown compressed tree node
Labels: bug,error-telemetry,search

```javascript
Error: TreeError [SearchView] Unknown compressed tree node
at h.setChildren in src/vs/base/browser/ui/tree/compressedObjectTreeModel.ts:162:10
at d.setChildren in src/vs/base/browser/ui/tree/compressedObjectTreeModel.ts:456:14
at te.setChildren in src/vs/base/browser/ui/tree/objectTree.ts:208:14
at <anonymous> in src/vs/workbench/contrib/search/browser/searchView.ts:589:16
at Array.forEach (<anonymous>)
at Yc.refreshTree in src/vs/workbench/contrib/search/browser/searchView.ts:588:20
at Yc.ld in src/vs/workbench/contrib/search/browser/searchView.ts:567:15
at Yc.kd in src/vs/workbench/contrib/search/browser/searchView.ts:558:16
at <anonymous> in src/vs/workbench/contrib/search/browser/searchView.ts:413:71
at g.invoke in src/vs/base/common/event.ts:723:17
at o.deliver in src/vs/base/common/event.ts:936:22
at u.fire in src/vs/base/common/event.ts:892:24
at u.fire in src/vs/base/common/event.ts:1070:11
at <anonymous> in src/vs/workbench/contrib/search/browser/searchModel.ts:1480:69
at g.invoke in src/vs/base/common/event.ts:723:17
at o.deliver in src/vs/base/common/event.ts:936:22
at a.fire in src/vs/base/common/event.ts:892:24
at K.onFolderChange in src/vs/workbench/contrib/search/browser/searchModel.ts:991:18
at <anonymous> in src/vs/workbench/contrib/search/browser/searchModel.ts:791:59
at g.invoke in src/vs/base/common/event.ts:723:17
at o.deliver in src/vs/base/common/event.ts:936:22
at a.fire in src/vs/base/common/event.ts:892:24
at U.onFolderChange in src/vs/workbench/contrib/search/browser/searchModel.ts:991:18
at <anonymous> in src/vs/workbench/contrib/search/browser/searchModel.ts:791:59
at g.invoke in src/vs/base/common/event.ts:723:17
at o.deliver in src/vs/base/common/event.ts:936:22
at a.fire in src/vs/base/common/event.ts:892:24
at U.onFolderChange in src/vs/workbench/contrib/search/browser/searchModel.ts:991:18
at <anonymous> in src/vs/workbench/contrib/search/browser/searchModel.ts:791:59
at g.invoke in src/vs/base/common/event.ts:723:17
at o.deliver in src/vs/base/common/event.ts:936:22
at a.fire in src/vs/base/common/event.ts:892:24
at U.onFileChange in src/vs/workbench/contrib/search/browser/searchModel.ts:978:19
at <anonymous> in src/vs/workbench/contrib/search/browser/searchModel.ts:1083:67
at g.invoke in src/vs/base/common/event.ts:723:17
at o.deliver in src/vs/base/common/event.ts:936:22
at a.fire in src/vs/base/common/event.ts:892:24
at Us.db in src/vs/workbench/contrib/search/browser/searchModel.ts:497:18
at Us.Z in src/vs/workbench/contrib/search/browser/searchModel.ts:414:8
at P.h in out/vs/workbench/workbench.desktop.main.js:90:17598
at P.g in src/vs/base/common/async.ts:886:9
```
[Go to Errors Site](https://vscode-errors.azurewebsites.net/card?ch=704ed70d4fd1c6bd6342c436f1ede30d1cff4710&bH=7d910557-f32c-cab8-6733-c8a342c16cf0)
Repository: vscode
Issue: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.
Labels: error-telemetry

```javascript
Error: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.
at D.g in src/vs/editor/browser/view/viewLayer.ts:504:18
at D.render in src/vs/editor/browser/view/viewLayer.ts:450:10
at R.renderLines in src/vs/editor/browser/view/viewLayer.ts:359:27
at a.renderText in src/vs/editor/browser/viewParts/lines/viewLines.ts:605:22
at j.I in src/vs/editor/browser/view.ts:406:20
at <anonymous> in src/vs/editor/browser/view.ts:364:30
at func in src/vs/editor/browser/view.ts:557:10
at safeInvokeNoArg in src/vs/editor/browser/view.ts:364:3
at j.v in src/vs/editor/browser/view.ts:230:8
at Object.getLineWidth in src/vs/editor/browser/view.ts:272:10
at d.getLineWidth in src/vs/editor/browser/controller/mouseTarget.ts:345:27
at n.u in src/vs/editor/browser/controller/mouseTarget.ts:787:25
at n.o in src/vs/editor/browser/controller/mouseTarget.ts:727:30
at n.g in src/vs/editor/browser/controller/mouseTarget.ts:549:41
at n.createMouseTarget in src/vs/editor/browser/controller/mouseTarget.ts:497:33
at S.p in src/vs/editor/browser/controller/mouseHandler.ts:250:34
at S.u in src/vs/editor/browser/controller/mouseHandler.ts:282:17
at <anonymous> in src/vs/editor/browser/controller/mouseHandler.ts:91:9
at callback in src/vs/editor/browser/editorDom.ts:182:64
```
[Go to Errors Site](https://vscode-errors.azurewebsites.net/card?ch=704ed70d4fd1c6bd6342c436f1ede30d1cff4710&bH=5fc1c533-6208-c725-1a14-7f06e59fe3dc)
Repository: next.js
Issue: Error when starting the project in dev mode
Labels: bug

### Verify canary release

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

### Provide environment information

```bash
OS: MacOS Ventura 13.3.1 (22E261)
Node: v18.16.0
NextJS: 13.1.5
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

_No response_

### Link to the code that reproduces this issue

/none

### To Reproduce

yarn create next-app . 
✔ Would you like to use TypeScript with this project? … Yes
✔ Would you like to use ESLint with this project? … Yes
✔ Would you like to use Tailwind CSS with this project? … No
✔ Would you like to use `src/` directory with this project? … No
✔ Would you like to use experimental `app/` directory with this project? … No
✔ What import alias would you like configured? … @/*

### Describe the Bug

Error when starting the project in dev mode

ready - started server on 0.0.0.0:3000, url: http://localhost:3000
info  - Loaded env from /Users/aleksandrnistratov/Jobs/WD/next_front_wd/.env.local
    [webpack.cache.PackFileCacheStrategy] No pack exists at /Users/aleksandrnistratov/Jobs/WD/next_front_wd/.next/cache/webpack/edge-server-development.pack: Error: ENOENT: no such file or directory, stat '/Users/aleksandrnistratov/Jobs/WD/next_front_wd/.next/cache/webpack/edge-server-development/index.pack'
<t> [webpack.cache.PackFileCacheStrategy] restore cache container: 26.27136 ms
<t> [webpack.cache.PackFileCacheStrategy] restore cache container: 33.788389 ms
<t> [webpack.cache.PackFileCacheStrategy] restore cache container: 39.765747 ms
<t> [webpack.cache.PackFileCacheStrategy] check build dependencies: 16.330353 ms
<t> [webpack.cache.PackFileCacheStrategy] restore cache content metadata: 0.845364 ms
<t> [webpack.cache.PackFileCacheStrategy] check build dependencies: 14.224899 ms
<t> [webpack.cache.PackFileCacheStrategy] restore cache content metadata: 1.941427 ms
    [webpack.cache.PackFileCacheStrategy] starting to restore cache content 0 (41.8 MiB) because of request to: ResolverCachePlugin|normal|default|dependencyType=|esm|path=|/Users/aleksandrnistratov/Jobs/WD/next_front_wd|request=|/Users/aleksandrnistratov/Jobs/WD/next_front_wd/node_modules/next/dist/compiled/@next/react-refresh-utils/dist/runtime.js
<t> [webpack.cache.PackFileCacheStrategy] restore cache content 0 (41.8 MiB): 96.737304 ms
    [webpack.cache.PackFileCacheStrategy] starting to restore cache content 0 (1.3 MiB) because of request to: ResolverCachePlugin|normal|default|dependencyType=|esm|path=|/Users/aleksandrnistratov/Jobs/WD/next_front_wd|request=|private-next-pages/_app
<t> [webpack.cache.PackFileCacheStrategy] restore cache content 0 (1.3 MiB): 30.980119 ms
event - compiled client and server successfully in 392 ms (166 modules)


### Expected Behavior

The project runs without errors

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

_No response_

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

_No response_
Repository: next.js
Issue: Prefetching failed to fetch RSC payload
Labels: bug

### Verify canary release

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

### Provide environment information

```bash
Operating System:
      Platform: linux
      Arch: x64
      Version: #1 SMP Fri Jan 27 02:56:13 UTC 2023
    Binaries:
      Node: 19.8.1
      npm: 9.6.4
      Yarn: 1.22.19
      pnpm: N/A
    Relevant packages:
      next: 13.3.1-canary.17
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

_No response_

### Link to the code that reproduces this issue

https://github.com/somersby10ml/next-url-test/tree/reproduction-template-app-dir

### To Reproduce

1. Please run the yarn dev command to start the local development server.
2. Press the F12 key to open the Developer Tools and navigate to the http://localhost:3000 URL.
3. Click on the `search` button.
	- After moving, don't hover your mouse over the `Home` or `Search` buttons.
5. Click on either the `move1` or `move2` button.
6. Hover over either the `Home` or `Search` element.



or

1. Navigate to http://localhost:3000/search?name=%E3%84%B1%E3%84%B4%E3%84%B7%E3%84%B9 in your web browser.
2. Hover over either the `Home `or `Search` element.
3. 

### Describe the Bug

- An error occurs if you use a non-English string in the URL.

### console.error
```
Failed to fetch RSC payload. Falling back to browser navigation. TypeError: Failed to execute 'fetch' on 'Window': Failed to read the 'headers' property from 'RequestInit': String contains non ISO-8859-1 code point.
```

### 🔽 console.error 
 ![a](https://user-images.githubusercontent.com/85594221/233690160-1ef8506c-b672-4314-913a-0a5164a8ecf8.png)

### 🔽 when an error occurs.
![b](https://user-images.githubusercontent.com/85594221/233690146-482f9a91-a3e9-4e67-886a-d22c68c7d7a7.png)

### 🔽 header not giving error
![c](https://user-images.githubusercontent.com/85594221/233690155-f581347b-8afa-4452-a6ab-847d3bb10a51.png)

### 🔽 header giving error
![d](https://user-images.githubusercontent.com/85594221/233690158-32214fa7-1881-45dd-a093-fb195ac6b7cc.png)



### Expected Behavior

console.error not showing

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

Chrome(112.0.5615.138) FireFox(112.0.1 64Bit)

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

_No response_
Repository: flutter
Issue: Timeout in general.shard/android/android_gradle_builder_test.dart "gradle build build aar uses selected local engine with arm32 ABI"
Labels: tool,P2,team-tool,triaged-tool

For example https://cirrus-ci.com/task/4506910049697792?logs=main#L2306

```
02:15 +2911 ~3 -1: test/general.shard/android/android_gradle_builder_test.dart: gradle build build aar uses selected local engine with arm32 ABI [E]                                                   
  TimeoutException after 0:00:02.000000: Test timed out after 2 seconds.
  dart:isolate  _RawReceivePort._handleMessage
To run this test again: /tmp/flutter sdk/bin/cache/dart-sdk/bin/dart test test/general.shard/android/android_gradle_builder_test.dart -p vm --plain-name 'gradle build build aar uses selected local engine with arm32 ABI'
```
Repository: TypeScript
Issue: Spurious "referenced directly or indirectly in its own initializer" when combined with narrowing, asserts function, and loop
Labels: Suggestion,Experience Enhancement

# Bug Report

<!--
  Please fill in each section completely. Thank you!
-->

### 🔎 Search Terms

<!--
  What search terms did you use when trying to find an existing bug report?
  List them here so people in the future can find this one more easily.
-->

referenced directly or indirectly asserts

### 🕗 Version & Regression Information

<!-- When did you start seeing this bug occur?

"Bugs" that have existed in TS for a long time are very likely to be FAQs; refer to
  https://github.com/Microsoft/TypeScript/wiki/FAQ#common-bugs-that-arent-bugs

If possible, please try testing the nightly version of TS to see if it's already been fixed.
For npm: `typescript@next`
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly

Note: The TypeScript Playground can be used to try older versions of TypeScript.

Please keep and fill in the line that best applies:
-->
- This is the behavior in every version I tried

### ⏯ Playground Link

<!--
  A link to a TypeScript Playground "Share" link which shows this behavior

  The TypeScript Workbench can be used for more complex setups, try
  https://www.typescriptlang.org/dev/bug-workbench/

  As a last resort, you can link to a repo, but these will be slower for us to investigate.
-->
[Playground Link](https://www.typescriptlang.org/play?ts=5.0.4#code/CYUwxgNghgTiAEYD2A7AzgF3gWwJ4CUQBHAVwEs4AueAChoAdrMYyUBzASngF4A+eAN4BfeAB94JFKABmrEMC7jJMucADcAKA2hIsBNMlgMZVPCho0IGBgCSaACIhZKeQB4AKrxoA3KBBIg1O4c1OaW1mjwvv4IZJEAcqjxJBDQAEYQIB68WgYoRiYo8NIoAIw0XAIa8DXwZNK0AIR4hKQUIJXVtd1wGCQwKJrdQlrd0kgwtMjoWPTwSA0A2gBEUMsANPDLacsAup3d3QD0R-AAojAwEwD8XYeIqJjwcGgpWNw4BMTkcDTLaEhsCAMAALVhsZYcIb3MwWKy2BxOVQ0F5vKF3eAjEYaPIFUwlABMFUEGPqTRa33aBxhvX6gwx2LGEymj1m8yWqw2Wx2+xJMPgJ3gAHkANZQXC3fnTJ6oiDvT6tH4gP4AoGg8GQ6H3MkokCvOU8bgfZRIlwKeCgq4Ad3gLhtFyuMD+SCQ9DQmoZGmxuOM+JQAGZiVUmZMaNK2Qt4Cs1pttntqfdBaLxZKYeHnnq3jwFZS4I0VYDgWD2B7+WF4XZHM55Lr9Rh0cMvUA)

### 💻 Code

<!-- Please post the relevant code sample here as well-->
```ts
declare const myRequire: ((p: string) => {} | undefined) | undefined;

declare function assertIsDefined<T>(value: T): asserts value is NonNullable<T>

function fn1() {
    if (!myRequire) {
        return;
    }

    for (const p of ["a", "b"]) {
        // Error?
        const result = myRequire("something");
        assertIsDefined(result);
    }
}
```

### 🙁 Actual behavior

<!-- What happened, and why it was wrong -->

`result` is claimed to be referenced directly or indirectly in its initializer.

Modifying the code in various ways makes the error go away.

### 🙂 Expected behavior

<!-- What you expected to happen instead, and why -->

No error; there's no relationship between the initializer and the result.
Repository: go
Issue: x/vuln/internal/vulncheck: TestCommand failures
Labels: NeedsInvestigation,vulncheck or vulndb

```
#!watchflakes
post <- repo == "vuln" && test ~ `^TestCommand`
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/a1b1a41ef00a4f299a54d0313b63136d825df45e)):

    main.go:13:2: no required module provides package golang.org/x/vuln/internal/scan; to add it:
    	go get golang.org/x/vuln/internal/scan
    --- FAIL: TestCommand (0.13s)
        buildtest.go:78: exit status 1
    main.go:13:2: no required module provides package golang.org/x/vuln/internal/scan; to add it:
    	go get golang.org/x/vuln/internal/scan


— [watchflakes](https://go.dev/wiki/Watchflakes)