sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: deno
Issue: Horrible performances with some npm packages (but fine on other runtimes) ?
Labels: perf,windows

I'm trying to use unified/remark/rehype to render markdown and the performances on deno specifically are horrible.
As demonstrated below, it's 17.5s for startup time on deno, while bun only take 1.2s and node (not using ts) 2.3s.

The 8x-17x time factor between deno and other runtimes seems really abnormal.

```diff
  vscode ➜ /workspaces/libs/markdown $ time bun test.ts 
  ok

+ real    0m1.210s
  user    0m0.119s
  sys     0m0.172s
  vscode ➜ /workspaces/libs/markdown $ time deno test.ts 
  ok

- real    0m17.546s
  user    0m0.126s
  sys     0m0.646s
  vscode ➜ /workspaces/libs/markdown $ time node --experimental-modules test.mjs
  ok

! real    0m2.342s
  user    0m0.257s
  sys     0m0.124s
```

Note that running the same through https://esm.sh imports yields extremely good result (even when deps are not cached):
```diff
  vscode ➜ /workspaces/libs/markdown $ time deno run esm_test.ts 
  ok

+ real    0m1.326s
  user    0m0.138s
  sys     0m0.016s
  vscode ➜ /workspaces/libs/markdown $ time deno run esm_test.ts 
  ok

+ real    0m0.057s
  user    0m0.038s
  sys     0m0.029s
```

Version:
```
vscode ➜ /workspaces/libs/markdown $ deno --version
deno 1.46.1 (stable, release, x86_64-unknown-linux-gnu)
v8 12.9.202.2-rusty
typescript 5.5.2
```

Reproduction:

<details>
<summary><code>test.ts</code></summary>

```ts
import { unified, type Processor as _Processor } from "unified"
import remarkRehype from "remark-rehype"
import remarkParse from "remark-parse"
import rehypeRaw from "rehype-raw"
import rehypeStringify from "rehype-stringify"

// Prevent tree-shaking
if ((unified && remarkRehype && remarkParse && rehypeRaw && rehypeStringify)) {
  console.log("ok")
}
```

</details>

<details>
<summary><code>deno.jsonc</code></summary>

```json
{
  "imports": {
    "unified":"npm:unified@11",
    "rehype-raw":"npm:rehype-raw@7",
    "rehype-stringify":"npm:rehype-stringify@10",
    "remark-parse":"npm:remark-parse@11",
    "remark-rehype":"npm:remark-rehype@11",
  },
}
```

</details>
Repository: vscode
Issue: Should we add a docs link to the `.github/dependabot.yml`?
Labels: feature-request,containers

Testing #226686

I wonder if it'd be helpful / logical to add an (i) docs link here:
![Image](https://github.com/user-attachments/assets/057f51d0-47ae-4b74-9cf9-48c696513ef4)

Like what we do for Templates and Features:

![Image](https://github.com/user-attachments/assets/f885b0fe-1098-4895-950d-8d06d48b3e95)
Repository: go
Issue: all, x/build/cmd/relui: automate go directive maintenance in golang.org/x repositories
Labels: Builders,Proposal,Proposal-Accepted

## Abstract

The value of the `go` directive in golang.org/x repositories is automatically maintained to be at least 1.(N-1).0, where Go 1.N is the most recent major Go release, and Go 1.(N-1) is the previous major Go release.

## Background

In the beginning, there was the GOPATH mode and versions of dependencies of golang.org/x repositories weren't explicitly tracked. Go 1.11 introduced the module mode, and over time it became the default mode. All golang.org/x repositories had an initial go.mod file checked in, and that file was maintained manually. This meant that a bug fix or a new feature in one golang.org/x repository didn't benefit another golang.org/x repository until someone chose to manually update that dependency. It also meant that eventual updates sometimes jumped many versions at once to catch up. This was resolved in 2022, when an automated monthly relui workflow began to create tags and update golang.org/x dependencies across all golang.org/x repositories (issue #48523).

At this point there are upwards of 35 [golang.org/x](https://golang.org/x) repositories. Owners of each repository update the "go" directive manually, ad-hoc, so golang.org/x repositories may receive different levels of "go" directive maintenance. For example, owners of the golang.org/x/mod module wished to use the new-to-Go-1.22 `go/version` package as soon as Go 1.23 came out, and so its "go" directive was recently updated to "1.22.0". On the other hand, golang.org/x/image hasn't been updated in a while, and its "go" directive is currently still at "1.18", which itself was an upgrade from "1.12" in [CL 526895](https://go.dev/cl/526895) as part of bringing all golang.org/x repos to use at minimum Go 1.18 language version (issue #60268).

Leaving go directive maintenance to be done entirely manually creates the possibility of some repositories staying on an older Go language version longer. When there's enough of a need to finally upgrade it to a recent Go language version, this requires a change across multiple major Go releases at once, which can be harder to review. Having continuous, smaller incremental upgrades requires creating many CLs for all of golang.org/x repositories every 6 months, which is toilsome if always done manually.

## Design

Design document at [go.dev/design/69095-x-repo-continuous-go](https://go.googlesource.com/proposal/+/HEAD/design/69095-x-repo-continuous-go.md).

CC @golang/release.
Repository: flutter
Issue: [Pigeon] Add Equatable conformance for Swift classes
Labels: c: new feature,package,c: proposal,team-ecosystem,p: pigeon,P2,triaged-ecosystem

In Swift, a class has to conform to [Equatable](https://developer.apple.com/documentation/swift/equatable) to allow comparisons with the `==` operator.  This is particularly useful for me when writing tests. When using Obj-C, it's handy to use the generated `toList` method to compare stuff, but that no longer works with swift as you can't compare `[Any?]` types. 

Adding equatable conformance just requires overriding the `==` method like so 

```
static func == (lhs: FooType, rhs: FooType) -> Bool {
  return lhs.var1 == rhs.var1
    && lhs.var2 == rhs.var2
/// and so on
}
```

I've been using extensions, but it would be nice if this was something part of the generated class already, since it's kind of tedious having to manually write that for every single class.
Repository: flutter
Issue: kTouchSlop too low and not configurable (RE: kTouchSlop const needs to change from 18 to 64 for touches to feel responsive #137962)
Labels: framework,f: gestures,c: proposal,P3,team-framework,triaged-framework

### Steps to reproduce

This is a follow up on the unresolved-but-closed issue: https://github.com/flutter/flutter/issues/137962

I'm experiencing the same issue  implementing a touch-screen keyboard: the 18 (logical) px `kTouchSlop` constant causes typing at a reasonable (not fast) speed to be impractical.    This is on a relatively "full size" touch keyboard with keys about 100 (L)px square.

`TapGestureRecognizer`  (and also `LongPressGestureRecognizer`) do not allow configuration of a touch slop value.  Other gestures (e.g. pan) do support enclosing a `GestureDetector` in a `MediaQuery` with a custom `DeviceGestureSettings` value specifying touch slop.   

`TapGestureRecognizer` and `LongPressGestureRecognizer` both extend `PrimaryPointerGestureRecognizer`.  `PrimaryPointerGestureRecognizer` does allow configuration of touch slop, but the extending Tap/LongPress recognizers don't expose it for configuration.  I've had success creating my own gesture recognizer based on `PrimaryPointerGestureRecognizer`, differing only from `TapGestureRecognizer` in its ability to set touch slop.  

In my case, when the slop is upgraded to 64px, the keyboard can be typed on at reasonable/fast speeds.  When typing quickly, a user's touch will be less precise and drag more across keys.

Even outside the keyboard, it appears the entire application could benefit from a significantly larger touch slop.  With 18px it requires fairly precise taps.


### Expected results

Touch slop should be configurable on a per-application, per gesture-detector, or per-gesture-recognizer basis.   `TapGestureRecognizer` and `LongPressGestureRecognizer` should support `MediaQuery`-based `DeviceGestureSettings`.

### Actual results

Touch slop is hardcoded as `kTouchSlop` constant and cannot be modified.  `DeviceGestureSettings` do not work on tap/longpress gestures.

### Code sample

        child: MediaQuery(
          data: MediaQuery.of(context).copyWith(
            gestureSettings: const DeviceGestureSettings(
              touchSlop: 64,
            ),
          ),
          child: GestureDetector(
            onTap: widget.onTap,


### Screenshots or Video

N/A

### Logs

N/A

### Flutter Doctor output

N/A
Repository: vscode
Issue: Change rendered text in readonly markdown code to not include `or p;ress enter to edit`
Labels: bug,papercut :drop_of_blood:,notebook-markdown,notebook-output,notebook-diff

Open a diff virewer for notebooks with an empty md output.
The following is displayed
![Screenshot 2024-08-28 at 09 49 20](https://github.com/user-attachments/assets/e8e98109-42f0-49da-a149-3f7bf55441af)


Given that the content is readonly, we should not include the text `double-click or press enter to edit`
Repository: vscode
Issue: Second layer of filtering after returning from `FileSearchProviderNew`'s `provideFileSearchResults(...)`
Labels: search,polish,search-api

Testing #226668

I suspect here that I am just not too well-versed in how these APIs work and this is as-expected, but thought i'd ask here anyway :) 

For this example I have hardcoded a single file to always return from `provideFileSearchResults(...)`

```ts
class mySearchProvider implements vscode.FileSearchProviderNew {
	provideFileSearchResults(pattern: string, options: vscode.FileSearchProviderOptions, token: vscode.CancellationToken): vscode.ProviderResult<vscode.Uri[]> {
		return [
			vscode.Uri.parse('memfs:/josh.txt'),
		]
	}
}
```

As expected, when I search for any substring of `josh` I see it pop up in the quick open search window


![Image](https://github.com/user-attachments/assets/c96026f4-785e-402c-a58e-3d82c0c2536c)

As expected, i've made this utterly useless since it won't actually show me the files in my project.  But in this case, I still expected to see `josh.txt` since it was hardcoded (as shown above).

![Image](https://github.com/user-attachments/assets/9bb7379c-4f1f-4c6f-90c9-fdfff5c85a1d)

Again, likely a misunderstanding on my part of how the API works. I thought this API was the "source of truth" for providing search results, yet my hardcoding of the value is doing some filtering outside of my (apparent) control.
Repository: pytorch
Issue: LSTM inference c++ threads block on DropoutState
Labels: module: cpp,module: rnn,triaged,module: multithreading

### 🐛 Describe the bug

I'd doing RL with c++ mutiple threads on a single GPU.
I find find threads are all block was block in lstm foward in get_dropout_state on a static varable:

RNN.cpp
_cudnn_impl(){
  ...
  auto& dropout_state = get_dropout_state(dropout_p, train, input.options());
  std::unique_lock<DropoutState> lock{dropout_state};
  ...
}

get_dropout_state(){
  ...
  static std::vector dropout_state_cache{
  static_cast<size_t>(cuda::getNumGPUs())};
  ...
}

And the DropoutState comments says:

// Every time we use a dropout state, we need to synchronize with its event,
// to make sure all previous uses finish running before this one starts. Once
// we’re done, we record the event to allow others to synchronize with this
// kernel. Those events are really needed only for inter-stream sync on a
// single GPU. I doubt anyone will want to run cuDNN RNNs in parallel on a
// single GPU, so they should end up being complete no-ops.

In fact lstm forwad doesn’t need a DropoutState, but it still mutex lock on it.
Is it possible to bypass the mutex lock in this situation?

### Versions

v2.4.0

cc @jbschlosser @mikaylagawarecki
Repository: godot
Issue: AudioStreamPlayer, useless checkbox
Labels: discussion,topic:editor,topic:audio

### Tested versions

4.3.stable

### System information

windows 10

### Issue description

The first checkbox is useless, the second one is the one that works.
![image](https://github.com/user-attachments/assets/eec5440d-e836-4cd6-b7ab-fb5fd66316eb)

At first i clicked the first checkbox but later down the line realized that the song didn't loop when i thought i clicked a loop feature

### Steps to reproduce

clicking looping checkbox turns on looping checkbox, clicking on turns on checkbox
if both on and one clicks looping it turns both off 

### Minimal reproduction project (MRP)

[audio.zip](https://github.com/user-attachments/files/16775544/audio.zip)
Repository: godot
Issue: Can't assign a node not in the tree to `SceneTree.current_scene`
Labels: discussion,topic:core

### Tested versions

Reproducible in Godot v4.3.stable.mono.official [77dcf97d8] - Not tested in other builds

### System information

Windows 10 - Godot v4.3.stable.mono.official [77dcf97d8]

### Issue description

Method `SceneTree::set_current_scene()` won't allow setting `current_tree` to a node that is not in the tree.

The assertion occurs here:
https://github.com/godotengine/godot/blob/8e80c1070420cf7f9fd9ffcefe9a12f05cfcbb64/scene/main/scene_tree.cpp#L1457

This behavior makes it impossible to implement a custom scene manager that changes the scene manually and properly preserves the behavior of `SceneTree.change_scene_to_file()` and `SceneTree.change_scene_to_packed()` regarding `SceneTree.current_scene`. That is because, when manually changing the scene, the node intended to be the next `current_scene` can't be assigned to `SceneTree.current_scene` until after it is added to the scene; but that's what `SceneTree.change_scene_to_file()` and `SceneTree.change_scene_to_packed()` do. (as seen below)

https://github.com/godotengine/godot/blob/8e80c1070420cf7f9fd9ffcefe9a12f05cfcbb64/scene/main/scene_tree.cpp#L1470

A scene manager made in GDScript or C# can only change `SceneTree.current_scene` after the node is added to the scene. That means `SceneTree.current_scene` will be `null` during `_ready()` and `_enter_tree()`, but you *can* access `SceneTree.current_scene` when changing the current scene from these functions when changing the scene using the native methods.

### Steps to reproduce

Example:
```csharp
using Godot;

public partial class ManualSceneManager : Node
{
    public void ChangeToSceneB()
    {
        // Remove & free current scene
        Node currentScene = GetTree().CurrentScene;
        currentScene.GetParent().RemoveChild(currentScene);
        currentScene.Free();

        // Load SceneB
        Node sceneB = ResourceLoader.Load<PackedScene>("res://scene_b.tscn").Instantiate();

        // Change to SceneB
        GetTree().CurrentScene = sceneB; // Error: Condition "p_scene && p_scene->get_parent() != root" is true.
                                         //   <C++ Source>   scene/main/scene_tree.cpp:1399 @ set_current_scene()
        GetTree().Root.AddChild(sceneB);
        GetTree().CurrentScene = sceneB; // Here, the assignment is allowed without errors, but SceneB._EnterTree()
                                         // and SceneB._Ready() have already been called while
                                         // GetTree().CurrentScene was null.
    }
}
```

### Minimal reproduction project (MRP)

I uploaded a project for this issue, but it's basically just the example code above, nothing special about it.

Link: https://github.com/leonardoraele/mrp_current_scene
Repository: PowerToys
Issue: An option to revert to the previous UI for Advanced Paste
Labels: Needs-Triage

### Description of the new feature / enhancement

Reverting to the previous UI will be much more efficient and keyboard-friendly.

### Scenario when this would be used?

All the time. Having to grab the mouse to access history is a terrible click-tax.

### Supporting information

Please 🙏
Repository: stable-diffusion-webui
Issue: [Bug]: Including reverse proxy like this is a huge security liability + bugs
Labels: bug-report

### Checklist

- [X] The issue exists after disabling all extensions
- [X] The issue exists on a clean installation of webui
- [ ] The issue is caused by an extension, but I believe it is caused by a bug in the webui
- [X] The issue exists in the current version of the webui
- [ ] The issue has not been reported before recently
- [ ] The issue has been reported before but has not been fixed yet

### What happened?

Began debugging why I was able to access service from an internal ip (docker net) but not via my own traefik proxy, and then realized I could also access it from a *.gradio.live url given that the docker template I was using had a share flag included in the entrypoint.

### Steps to reproduce the problem

Start webui.sh without understanding the security risks of opening a connection to an arbitrary url.

### What should have happened?

Do not package a reverse proxy server with this application and then expect people to install it on their home pc's. It's a liability, regardless of your intention. Even inside of a container ecosystem, this is a security risk given that the user didn't configure it themselves. This is potentially a vector for many now insecure devices, and this is not some novel concept.

There are plenty of exploits posted around the web for gradio.live specifically, but allowing users to unknowingly add a `--share` without likely understanding that implication is extremely careless at best. Consider removing the ability to proxy gradio all together. Consider including a readme with instructions on how to properly set up a secure reverse proxy themselves using nginx + best practices.

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

_No response_

### Sysinfo

Ubuntu Server x86_64 (or any other operating system)


### Console logs

```Shell
None.
```


### Additional information

_No response_
Repository: go
Issue: net/http: using io.Copy to copy a file to http.ResponseWriter does not use sendfile
Labels: NeedsInvestigation

### Go version

go version go1.22.6 linux/amd64

### Output of `go env` in your module/workspace:

```shell
GO111MODULE=''
GOARCH='amd64'
GOBIN=''
GOCACHE='/root/.cache/go-build'
GOENV='/root/.config/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/root/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='linux'
GOPATH='/root/go'
GOPRIVATE=''
GOPROXY='https://*********'
GOROOT='/root/server/go'
GOSUMDB='******************'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/root/server/go/pkg/tool/linux_amd64'
GOVCS=''
GOVERSION='go1.22.6'
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='gcc'
CXX='g++'
CGO_ENABLED='0'
GOMOD='/dev/null'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -m64 -fno-caret-diagnostics -Qunused-arguments -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/data/tmp/go-build1438424244=/tmp/go-build -gno-record-gcc-switches'
```


### What did you do?

Implement a Handler for http.Server and try to streaming a file:
``` Go
func (handler Handler) ServeHTTP(w http.ResponseWriter, r *http.Request) {
  file, _ := os.Open("file")
  io.Copy(w, file)
}
```

### What did you see happen?

`io.Copy` not using `sendfile()` when copy from `*os.File` to `http.ResponseWriter`:

1. `io.Copy` first try to use `WriterTo` from `*os.File`, but `*http.response` does not implement syscall.Conn interface;
2. fallback to `genericWriteTo` in `WriteTo` of `*os.File`;
3. file got wrapped in `os.fileWithoutWriteTo` (file.go:269)
4. another call to `io.Copy` try to use `*http.response.ReadFrom()` which calls `sendfile()`
5. which trys to use `TCPConn.ReadFrom()`
6. src is not a `*os.File` but a `os.fileWithoutWriteTo` wrapper. (sendfile_linux_go:20)
7. fallback to `genericReadFrom()` which will do all the copying stuff (tcpsock_posix.go:54)

### What did you expect to see?

calling `sendfile()` in either `*os.File.WriteTo` Or `*http.response.ReadFrom`;
Repository: vscode
Issue: Features required from Multi-diff editor for Notebook diffing
Labels: feature-request,notebook-diff

Feature requests for multi file editor widget:

* [ ] Ability to configure an editor as editable (the right hard editor)
    * Currently cell text models are virtual documents (and they are readonly `TextResourceEditorModel`)
    * Unless we make make some changes to have another instance of `BaTextEditorModel` thats read-write (based on whether the notebook document is read-write)
* [ ] Custom context for toolbar actions (currently hardcoded to pass uri) https://github.com/microsoft/vscode/issues/204074
* [ ] Custom collapsible sections (with a hierarchy)
    * Custom borders to clearly distinguish between different cells
* [ ] Toggle white space differences per item (or resource type)
* [ ] Change progress lable from `No Changed Files` to something else (e.g. `Computing Notebook Diffs`)
* [ ] Ability to hide/collapse unchanged cells (like unchanged lines)
* [ ] Ability to navigate to an item (even if its currently not visible, required to navigate to next/previous changed cell)
* [ ] Custom editors (webview support in outputs) https://github.com/microsoft/vscode/issues/206062
* [ ] Diff view ruler
Repository: react-native
Issue: Direct JSC debugging cannot be used in Mac simulator from 0.74.1
Labels: Needs: Author Feedback,Needs: Repro,Newer Patch Available

### Description

When I updated react native to 0.74.1, I found safari devtools(direct JSC debugging) cannot inspect JSContext of the iphone simulator in my mac, which works right in 0.74.0.

I checked the change records and found this commit, it looks like JSC debugging has been banned in MacOS, but I really need it.
![image](https://github.com/user-attachments/assets/915f4ef8-b836-4c6c-94c3-525173ede934)
https://github.com/facebook/react-native/commit/0a4d97362f5a40cff62edce5200c3e7e8622d912




### Steps to reproduce

1. Init react native project without framework(react native >= 0.74.1), like https://reactnative.dev/docs/getting-started-without-a-framework
2. disable hermes
3. npm run ios(with iPhone simulator)
4. open safari devtools, no JSContext avaliable in iPhone simulator

### React Native Version

0.74.1

### Affected Platforms

Runtime - iOS, Build - MacOS

### Output of `npx react-native info`

```text
System:
  OS: macOS 14.2.1
  CPU: (8) x64 Apple M3
  Memory: 28.77 MB / 16.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 20.11.1
    path: ~/.nvm/versions/node/v20.11.1/bin/node
  Yarn:
    version: 1.22.22
    path: ~/.nvm/versions/node/v20.11.1/bin/yarn
  npm:
    version: 10.2.4
    path: ~/.nvm/versions/node/v20.11.1/bin/npm
  Watchman:
    version: 2024.04.08.00
    path: /usr/local/bin/watchman
Managers:
  CocoaPods:
    version: 1.15.2
    path: /usr/local/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.4
      - iOS 17.4
      - macOS 14.4
      - tvOS 17.4
      - visionOS 1.1
      - watchOS 10.4
  Android SDK: Not Found
IDEs:
  Android Studio: 2023.3 AI-233.14808.21.2331.11709847
  Xcode:
    version: 15.3/15E204a
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.11
    path: /usr/bin/javac
  Ruby:
    version: 2.6.10
    path: /usr/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.3.1
    wanted: 18.3.1
  react-native:
    installed: 0.74.1
    wanted: 0.74.1
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: false
  newArchEnabled: false
```


### Stacktrace or Logs

```text
no Stacktrace or logs
```


### Reproducer

https://github.com/yandadaFreedom/test-jsc-macOS

### Screenshots and Videos

_No response_