sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: deno
Issue: Race condition in Deno.serve() and fetch()
Labels: ext/http

The following code sample is from one of my private repositories. The beforeAll starts an oak server and the afterAll closes it. So all test cases are making API calls to the same oak server.

These test cases all pass in deno 1.37.0+6f87962 canary build, then the second 2 fail in deno 1.37.0+c68650d. It still fails in v1.38.2.

```ts
const apiRouterTests = describe({
  name: "apiRouter",
  async beforeAll() {
    await listen();
  },
  async afterAll() {
    await close();
  },
});

const notFoundTests = describe.only(apiRouterTests, "route not found");

it(notFoundTests, "without extension", async () => {
  const response = await fetch("http://localhost:9001/api/invalid");
  const body = await response.json();
  assertEquals(response.status, 404);
  assertEquals(
    response.headers.get("Content-Type"),
    "application/json; charset=UTF-8",
  );
  assert(response.headers.has("X-Response-Time"));
  assert(!response.headers.has("etag"));
  assertEquals(body, {
    error: { name: "NotFoundError", message: "Not found", status: 404 },
  });
});

it(notFoundTests, "with json extension", async () => {
  const response = await fetch("http://localhost:9001/api/invalid.json");
  const body = await response.text();
  assertEquals(response.status, 404);
  assertEquals(response.headers.get("Content-Type"), null);
  assert(response.headers.has("X-Response-Time"));
  assert(!response.headers.has("etag"));
  assertEquals(body, "");
});

it(notFoundTests, "with non json extension", async () => {
  const response = await fetch("http://localhost:9001/api/invalid.html");
  const body = await response.text();
  assertEquals(response.status, 404);
  assertEquals(response.headers.get("Content-Type"), null);
  assert(response.headers.has("X-Response-Time"));
  assert(!response.headers.has("etag"));
  assertEquals(body, "");
});
```

All the test cases after the first now fail due to a leaking resource. It appears the connection from the first doesn't close before the next test starts.

```
error: Leaking resources:
  - An inbound HTTP connection (rid 7) was accepted before the test started, but was closed during the test. Do not close resources in a test that were not created during that test.
  - An inbound HTTP connection (rid 21) was accepted during the test, but not closed during the test. Close the inbound HTTP connection by calling `httpConn.close()`.
```

https://github.com/denoland/deno/pull/20680 is what caused this issue to start happening. It appears the change was made to fix a separate race condition in Deno.serve() and fetch(). In that case, a new server is being started for each test case instead of re-using the same server for each test case.

https://github.com/denoland/deno/issues/20443

Unlike that one, the issue cannot be resolved by simply adding `await delay(1)` to the end of each test case.

I don't know rust so I'm not sure why that PR causes this failure.
Repository: ollama
Issue: Add open assistant
Labels: model request

Could you add Open Assistant? Thank you!
Repository: tauri
Issue: [bug] Transparent window glitch on macos sonoma (14) after focus change
Labels: type: bug,platform: macOS,status: needs triage

### Describe the bug

I'm encountering a really strange bug which happens on any window which is transparent and a focus change occured. Images below for clarification. I couldn't confirm if the issue only happens with sonoma but seeing as sonoma is quite new and there arent any issues about this yet I thought it was clear it must be some breaking api change from apples side (as a lot of other apps have had breaking changes... I also tried testing the 2.0 alpha version which had the same effect, it works to reproduce with 1.x aswell but info was run on 2.0

Before focus change
<img width="1800" alt="Screenshot 2023-11-19 at 01 29 23" src="https://github.com/tauri-apps/tauri/assets/48829979/6c1875dd-268e-4a7d-8160-9b49ace94de8">

After focus change
<img width="1800" alt="Screenshot 2023-11-19 at 01 29 32" src="https://github.com/tauri-apps/tauri/assets/48829979/38c8e87a-06ba-4742-ab66-f9e9c4415d1b">


### Reproduction

Create a new tauri app. Set the window to transparent and enable macos private api. Go to your index.html and change the body background to something like #0000004c. Start dev or create a build and switch focus back and forth, the result from the images provided should be the same.

### Expected behavior

A normal transparent window :)

### Platform and versions

```text
[✔] Environment
    - OS: Mac OS 14.2.0 X64
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.75.0-nightly (c543b6f35 2023-10-14)
    ✔ cargo: 1.75.0-nightly (6fa6fdc76 2023-10-10)
    ✔ rustup: 1.26.0 (5af9b9484 2023-04-05)
    ✔ Rust toolchain: nightly-aarch64-apple-darwin (default)
    - node: 21.0.0
    - pnpm: 8.9.2
    - npm: 10.2.0
    - bun: 1.0.1
 
[-] Packages
    - tauri [RUST]: 2.0.0-alpha.17
    - tauri-build [RUST]: 2.0.0-alpha.11
    - wry [RUST]: 0.34.2
    - tao [RUST]: 0.23.0
    - @tauri-apps/api [NPM]: 2.0.0-alpha.11
    - @tauri-apps/cli [NPM]: 2.0.0-alpha.17

[-] App
    - build-type: bundle
    - CSP: unset
    - distDir: ../dist
    - devPath: http://localhost:1420/
    - framework: SolidJS
    - bundler: Vite
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: godot
Issue: Console isn't flushed during OS.crash()
Labels: bug,topic:core

### Godot version

4.1 stable, 4.2 RC-1

### System information

Godot v4.1.stable - Windows 10.0.22631 - Vulkan (Forward+) - integrated Intel(R) UHD Graphics 620 () - Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz (8 Threads)

### Issue description

Calling this code:
´´´
print("something")
OS.crash("something else")
´´´

produces no output in the editor terminal, this is undesirable.

### Steps to reproduce

Run above code.

### Minimal reproduction project

N/A
Repository: stable-diffusion-webui
Issue: [Feature Request]: List of favorite samplers for models
Labels: enhancement

### Is there an existing issue for this?

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

### What would your feature do ?

Not every model works correctly with all samplers, and for many they are all displayed in a list, which is not always convenient, but you can remove the ones you don’t need, but they are removed for all models.
Why not add the ability to display a list of favorite samplers for each model separately in the same model settings window where you select the preferred VAE for the model.

### Proposed workflow

The process is described, how to do this is already written above, but since I need to, I’ll describe it in more detail)
1. Open the models tab
2. Click on the Settings icon
3. In the samplers line, remove or add preferred samplers that will be displayed in the list for selection after loading the model.

### Additional information

_No response_
Repository: godot
Issue: FBX import takes forever (more than 2 minutes for single object)
Labels: bug,topic:import,topic:3d,performance

### Godot version

v4.1.3 stable official and v4.2.rc.custom_build [80de898d7]

### System information

Godot v4.2.rc (80de898d7) - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3070 (NVIDIA; 31.0.15.3742) - AMD Ryzen 5 3600 6-Core Processor (12 Threads)

### Issue description

When importing an FBX asset (56MB) it takes way too long (2 minutes and 17 seconds, yes I measured it).

On the other hand, blender takes 1-2 seconds.

### Steps to reproduce

1. Download any FBS asset (I used: https://free3d.com/3d-model/nathan-animated-003-walking-644277.html)
2. Unzip it
3. Drag & Drop `rp_nathan_animated_003_walking.fbx` to the scene / FileSystem to import it

### Minimal reproduction project

I can't upload it. For some reason, a single node3d and FBX import, the size of the ZIP is 250MB.
I'm not joking, the `.godot` folder size is 211MB (again this is brand new project that I only imported FBX)
![image](https://github.com/godotengine/godot/assets/17744127/a97e33df-b4e1-4f58-8cc2-1fcea1258f0f)

So I can't upload demo project

Possible solution is discussed here: https://github.com/godotengine/godot-proposals/discussions/8476
Repository: pytorch
Issue: Undocumented CUDA graphs requirement that kernels must use stream
Labels: triaged,module: custom-operators,module: cuda graphs

### 🐛 Describe the bug

I have a function that calls some custom cuda kernels interleaved with pytorch operations. When I try to capture the function with a cuda graph, the cuda kernels become no-ops. That is, the graph captures fine and performs all operations except for those in the cuda kernels. Does torch's cuda graph work with custom kernels? Is there something special I need to do to enable custom kernels with graphs?

### Versions

torch 2.1.0 on cuda 11.8

cc @mcarilli @ezyang
Repository: material-ui
Issue: [material-ui][Box] Box throws an error when there is a RSC (React Server Component) as a child
Labels: external dependency,package: material-ui,component: Box,nextjs

### Steps to reproduce 🕹

Link to live example: https://codesandbox.io/p/devbox/fragrant-forest-gn5rr6?file=%2Fsrc%2Fapp%2Fpage.tsx%3A1%2C1

```typescript
import { Box } from '@mui/material'

async function FooBar() {
  return <Box>foobar</Box>
}

export default function Page() {
  return (
    <Box>
      <FooBar />
    </Box>
  )
}
```

### Current behavior 😯

Throws the following error:
> app-index.js:32 Warning: Failed prop type: Invalid prop `children` supplied to `ForwardRef(Box)`, expected a ReactNode.

### Expected behavior 🤔

Not error =D

### Context 🔦

Absolutely love MUI, but this is preventing us from using it in server components

### Your environment 🌎

  System:
    OS: macOS 13.6
  Binaries:
    Node: 18.17.0 - ~/.nodenv/versions/18.17.0/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 9.6.7 - ~/.nodenv/versions/18.17.0/bin/npm
  Browsers:
    Chrome: 119.0.6045.159
    Edge: Not Found
    Safari: 16.6
Repository: vscode
Issue: Code cannot be read and edited using a screen reader in Android web version of VS code.
Labels: bug,accessibility,editor-core

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes/No

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: web
- OS Version: android 10

Steps to Reproduce:

1. Turn on TalkBack from settings >accessibility
2. open any file in web version of VS code.
3. Try to read the code inside the file with screen reader. Whenever the edit box is focused, the screen reader only announces name of the file with the edit box and does not announces any code written in the file. Hence the code cannot be edited as well. Also after typing some code if enter is pressed (in the mobile keyboard)the edit box becomes blank for the screen reader and it is not possible to read previous lines of that file.
Repository: godot
Issue: Hovering over a debugger error to view its details flickers the tooltip that's supposed to show it.
Labels: bug,topic:editor,topic:gui

### Godot version

v4.1.3.stable.mono.official [f06b6836a]

### System information

macOS 14.1.1 Macbook Air M2

### Issue description

A lot of the times, when I'm debugging in C#, I want to view the errors in detail. I normally do this by hovering over the error with my mouse cursor. This should trigger a tooltip to show up displaying the error's details. But a lot of the times, it just flickers the tooltip, and then it doesn't show up anymore. So I can't view the error.

https://github.com/godotengine/godot/assets/75036859/c90d159d-3673-4d9f-975a-3ab3b9a74c0b

Sometimes just restarting Godot fixes the issue, but it doesn't anymore for me since upgrading to Godot Mono 4.1.3 (from Godot Mono 4.1.1)

Also a workaround is just copying the error to clipboard and paste it in a text editor to view the error.

### Steps to reproduce

Add a C# script to a Node.
Write code that throws an error at runtime.
Hover over the error in the Godot's debugger.

Note: It doesn't always happen. For example when I tried to make a reproduction project, it didn't occur. But when it happens it's super annoying.

### Minimal reproduction project

[ErrorFlickerReprProject.zip](https://github.com/godotengine/godot/files/13402639/ErrorFlickerReprProject.zip)

I just made it throw an error in _Ready().

Note: The bug doesn't always happen. For example when I tried to make a reproduction project, it didn't occur. Maybe the Godot Editor needs to be open for some time?
Repository: go
Issue: proposal: net/http: optimize http.Dir when files are not modified and add GODEBUG to preserve old behavior
Labels: Proposal

# Proposal: net/http: optimize http.Dir when files are not modified and add GODEBUG to preserve old behavior

Author(s): @qiualidongfeng

Last updated: 2023-11-19

## Abstract

If there are no errors, http.Dir calls os.Open once every time Open is called. If the file has not changed, performance can be improved by reducing system calls by caching *os.File and []byte read from *os.File.

## Background

Background as described above.
Proposals to optimize http.Dir.

## Proposal

http.Dir.Open When the file modification time does not change, use the cached *os.FIle and []byte.
Add the GODEBUG environment variable httpdircache, go1.23 defaults to 1, enabling the behavior after the proposal implementation. Setting the value to 0 restores the previous behavior.

## Rationale

1, directly change the behavior, when the file modification time is unchanged but the content changes, backward incompatible.

2, Third-party libraries, such as https://github.com/qiulaidongfeng/cachefs , This is a prototype written in a third-party library before sending CL to the standard library. The advantage is that it can be used less than go1.23, and the disadvantage is that the code needs to be manually modified to use. 

## Compatibility

100% backward compatibility with godebug=httpdircache=0.

## Implementation

I  will send CL to implement the proposal, which is too close to go1.22 code freezing, so this proposal is for go1.23.
Repository: godot
Issue: Internal script error! Opcode: 25 - while assigning EditorInterface to the field
Labels: bug,topic:gdscript,topic:editor

### Godot version

4.2.rc1.mono

### System information

windows11-4.2.rc1.mono-vulkan(forward+)

### Issue description

The provided GDScript code contains instances where the editor_interface variable is being assigned without proper initialization in the constructor. This can lead to unexpected behavior and errors, specifically the issue flagged in the comment: "modules/gdscript/gdscript_vm.cpp:1319 - Condition ' !nc ' is true. Breaking..: Internal script error! Opcode: 25 (please report)."

**Expected Behavior**:
The editor_interface variable should be properly initialized in the constructor, preventing any potential runtime errors.

**Actual Behavior**:
The editor_interface variable is not initialized correctly in the constructor of the Test class, leading to a runtime error in the GDScript VM.

```gdscript
class Test:
	var editor_interface: EditorInterface
	
	func _init(ei):
		# modules/gdscript/gdscript_vm.cpp:1319 - Condition ' !nc ' is true. Breaking..:
		# Internal script error! Opcode: 25 (please report). 
		editor_interface = ei


class Test2:
	var editor_interface: EditorInterface
	
	func _init(ei):
		# OK
		self.editor_interface = ei


class Test3:
	var editor_interface: EditorInterface
	
	func _init(ei: EditorInterface):
		# OK
		editor_interface = ei


class Test4:
	var editor_interface
	
	func _init(ei):
		# OK
		editor_interface = ei

```

### Steps to reproduce

1. Activate Plugin 'test'
2. See the console output


### Minimal reproduction project

[editor-interface-issue.zip](https://github.com/godotengine/godot/files/13402855/editor-interface-issue.zip)
Repository: TypeScript
Issue: Inference from annotated parameters of context-sensitive functions is order dependent 
Labels: Bug

### 🔎 Search Terms

inference annotated parameters context sensitive order

### 🕗 Version & Regression Information

- This is the behavior in every version I tried

### ⏯ Playground Link

https://www.typescriptlang.org/play?ts=5.4.0-dev.20231118#code/CYUwxgNghgTiAEAzArgOzAFwJYHtXwxAGcMAeAFQBp4BBagIQD4AKHAIwCsAueAbwCh48TAA8e5ANyD4UHs1m1qo8QEp4AXkbwAbjizApQtnOPx6SjGPhUZPGms069B-gF8VPXfqn9CJZgJCyvAA5Ig4OCGU0gryPCQwWKgA5hYiDlq8rtFGJvEYiSlp1FAZfNluKj5+GAHSwWERUdKmzKYJSanCliVlWTm28HHwHUXd6RqZFe5SQA

### 💻 Code

```ts
declare function test<T, A, B>(obj: {
  ctx: T;
  a: (a: A, ctx: T) => void;
  b: (b: B, ctx: T, a: A) => void;
}): void;

test({
  ctx: 'foo',
  a: (a: string, ctx) => {},
  b: (b: string, ctx, a) => {},
});

test({
  ctx: 'foo',
  b: (b: string, ctx, a) => {},
  a: (a: string, ctx) => {},
});
```


### 🙁 Actual behavior

The second call doesn't infer properly

### 🙂 Expected behavior

I'd expect the second call to be inferred as good as the first one

### Additional information about the issue

related to https://github.com/microsoft/TypeScript/issues/47599
Repository: rust
Issue: Add rustdoc JS search benchmark in performance checks
Labels: T-rustdoc,T-infra

@notriddle wrote a tool to benchmark performance for the rustdoc search. I think it's an important enough topic to watch if there are any changes (both positive and negative). Only question is how to integrate it in the current tool.

Example of usage of the tool in https://github.com/rust-lang/rust/pull/118024.

cc @lqd @nnethercote (if you have any idea/suggestion?)
Repository: storybook
Issue: [Bug]: Can not correctly split summary of descriptions
Labels: bug,help wanted,block: description,sev:S3

### Describe the bug

Can not correctly split summary of descriptions in table, when summary has special syntax.

### To Reproduce

This case will working wrong.

```ts
const meta: Meta<typeof MyComp> = {
  title: 'MyComp',
  component: MyComp,
  args: {
  },
  argTypes: {
    offset: {
      description: 'description',
      type: { required: false, name: 'array', value: { name: 'number' } },
      table: {
        type: { summary: 'Array<number> | [number, number]' },
      },
      control: 'object',
    },
  },
};
```
Got: `Array<number> | [number, number]` 

This case will working well.

```ts
const meta: Meta<typeof MyComp> = {
  title: 'MyComp',
  component: MyComp,
  args: {
  },
  argTypes: {
    offset: {
      description: 'description',
      type: { required: false, name: 'array', value: { name: 'number' } },
      table: {
        type: { summary: 'NumberArrary | NumberArrayLike' },
      },
      control: 'object',
    },
  },
};
```
Got: `NumberArrary`  `NumberArrayLike` 

### System

```bash
System:
    OS: macOS 13.6.1
    CPU: (8) x64 Intel(R) Core(TM) i5-1038NG7 CPU @ 2.00GHz
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 16.20.2 - ~/.nvm/versions/node/v16.20.2/bin/node
    Yarn: 1.22.4 - /usr/local/bin/yarn
    npm: 8.19.4 - ~/.nvm/versions/node/v16.20.2/bin/npm <----- active
  Browsers:
    Chrome: 119.0.6045.159
    Safari: 16.6
  npmPackages:
    @storybook/addon-actions: ^7.5.3 => 7.5.3 
    @storybook/addon-essentials: ^7.5.3 => 7.5.3 
    @storybook/react: ^7.5.3 => 7.5.3 
    @storybook/react-vite: ^7.5.3 => 7.5.3 
    @storybook/storybook-deployer: ^2.8.16 => 2.8.16 
    eslint-plugin-storybook: ^0.6.15 => 0.6.15 
    storybook: ^7.5.3 => 7.5.3
```


### Additional context

None
Repository: ollama
Issue: Support for hyenadna-large-1m-seqlen-hf
Labels: model request

Hi, any plans to support hyenadna? it has 1 million tokens!

https://huggingface.co/LongSafari/hyenadna-large-1m-seqlen-hf
Repository: next.js
Issue: next/link with absolute URL paths + wildcard subdomains broken after using browser back button
Labels: bug,Navigation,Runtime

### Link to the code that reproduces this issue

https://github.com/aliceisjustplaying/broken-next-link-repro

### To Reproduce

1. Go to https://paperclip.monster
2. Click on one of the links ("Page 1" or "Page 2")
3. Click the browser back button
4. Try clicking the **same link as you clicked the first time**
5. Stare in disbelief that literally nothing happens.

This bug hinges on a few things:
1. It only happens in prod (deployed to vercel), cannot repro on localhost AND
2. With an apex domain (hence the need to test it at https://paperclip.monster or use another apex domain) AND
3. Because we're using wildcard subdomains with a middleware AND
4. I'm linking to the the two aforementioned through their absolute path, like this:
``` 
import Link from "next/link";
[...]
<Link href="https://page1.paperclip.monster">Page 1</Link>
<Link href="https://page2.paperclip.monster">Page 2</Link>
```

(Yes I know this may be considered bad practice. It should still work and it used to.)

### Current vs. Expected behavior

**Current**: When I click a link, use the back button and click the same link again, nothing happens
**Expected**: When I click a link, use the back button and click the same link again, it works

### Verify canary release

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

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.1.0: Mon Oct  9 21:27:24 PDT 2023; root:xnu-10002.41.9~6/RELEASE_ARM64_T6000
Binaries:
  Node: 21.2.0
  npm: 10.2.4
  Yarn: 1.22.19
  pnpm: 8.10.5
Relevant Packages:
  next: 14.0.4-canary.4
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.1.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

App Router, Middleware / Edge (API routes, runtime), Routing (next/router, next/navigation, next/link)

### Additional context

I've binary searched the canaries to find when this broke and [it happened somewhere between v14.0.3-canary.5 and v14.0.3-canary.6](https://github.com/vercel/next.js/compare/v14.0.3-canary.5...v14.0.3-canary.6) if I got it right. Looking at the commits, I think I did, though I don't know what *exactly* breaks this.