sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: node
Issue: armhf segmentation fault --inspect-brk and simple import statement
Labels: confirmed-bug,v8 engine,inspector

### Version

18.13.0, 18.17.0

### Platform

6.1.0-10-armmp #1 SMP Debian 6.1.38-1 (2023-07-14) armv7l GNU/Linux

### Subsystem

inspector

### What steps will reproduce the bug?

Execute
node --inspect-brk main.js

with these files:

```main.js
import './odd.js';
```

and
```odd.js
class A extends URL {
	constructor(str) {
		super(str);
	}
	toString() {
		return super.toString();
	}
}

console.log("fail")
```


### How often does it reproduce? Is there a required condition?

_No response_

### What is the expected behavior? Why is that the expected behavior?

Not fail

### What do you see instead?

Segmentation fault

### Additional information

Reproduced with the debian package AND the latest nodesource package node 18.x on debian bookworm.
Small changes to odd.js will stop crashing.
Repository: godot
Issue: Can't Open Vulkan
Labels: bug,platform:linuxbsd,topic:rendering,needs testing

### Godot version

Godot Engine v4.0.2.stable.mono.official.7a0977ce2 

### System information

PopOS (ubuntu22.04)

### Issue description

```
(base) yingshaoxo@pop-os:~/CS/Godot/godot-4-3d-third-person-controller$ Godot_v4.0.2-stable_mono_linux.x86_64  --video-driver opengl
```
```
Godot Engine v4.0.2.stable.mono.official.7a0977ce2 - https://godotengine.org
xkbcommon: ERROR: failed to add default include path /home/yingshaoxo/anaconda3/share/X11/xkb
Vulkan API 1.3.224 - Forward+ - Using Vulkan Device #2: NVIDIA - NVIDIA GeForce RTX 3070 Laptop GPU
ERROR: Condition "err" is true. Returning: ERR_CANT_CREATE
   at: _initialize_queues (drivers/vulkan/vulkan_context.cpp:1561)
ERROR: Condition "err != OK" is true. Returning: ERR_CANT_CREATE
   at: _window_create (drivers/vulkan/vulkan_context.cpp:1689)
ERROR: Can't create a Vulkan window
   at: _create_window (platform/linuxbsd/x11/display_server_x11.cpp:5145)
/usr/bin/zenity: symbol lookup error: /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37: undefined symbol: gst_codec_utils_caps_get_mime_codec
ERROR: Unable to create DisplayServer, all display drivers failed.
   at: setup2 (main/main.cpp:2018)
ERROR: Pages in use exist at exit in PagedAllocator: N7Variant5Pools11BucketLargeE
   at: ~PagedAllocator (./core/templates/paged_allocator.h:140)
ERROR: Pages in use exist at exit in PagedAllocator: N7Variant5Pools12BucketMediumE
   at: ~PagedAllocator (./core/templates/paged_allocator.h:140)
ERROR: Pages in use exist at exit in PagedAllocator: N7Variant5Pools11BucketSmallE
   at: ~PagedAllocator (./core/templates/paged_allocator.h:140)
ERROR: BUG: Unreferenced static string to 0: interface_added
   at: unref (core/string/string_name.cpp:131)
```

### Steps to reproduce

```
Godot_v4.0.2-stable_mono_linux.x86_64 --video-driver GLES2
```

### Minimal reproduction project

https://github.com/gdquest-demos/godot-4-3d-third-person-controller
Repository: ant-design
Issue: Telugu Language Support
Labels: help wanted,Inactive

### What problem does this feature solve?

It will add one more  Language Support in antd

### What does the proposed API look like?

It will add one more  Language Support in antd

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: go
Issue: x/tools/gopls: type constraint discrepancy between go compiler and gopls
Labels: NeedsFix,gopls,Tools

Working on Go project In VSCode, I noticed gopls reports a problem which is ok for the compiler. 

I extracted a minimal example as follows:

Suppose we have a project with packages `foo` (file `foo.go`) and `bar` (file `bar.go`). 

The package `foo` exports type constraint `A`:
```go
// foo.go
package foo

type A comparable
```
The package `bar` consumes the constraint `A` as
```go
// bar.go
package bar

// import "foo"

func F[T foo.A](a T, b T) bool {
	return a == b
}
```

Since the constraint `A` "inherits" from `comparable`, the expression `a == b` is well defined: `T` is constrained by `A` which _is_ comparable, hence `==` is available for values of type `T`. The compiler is happy with the code.

But VSCode reports `a == b` as the problem:

> invalid operation: a == b (incomparable types in type set)

In editor,
![image](https://github.com/golang/go/assets/38156408/028fbb99-c7da-4645-9e4d-3b14214321bd)

Two observations:

* if the constraint `type A comparable` is defined in the package `bar`, it's ok for gopls – it's an cross-package problem
* if the constraint is defined as `type A = comparable` ie. as typedef (not "newtype") in package `foo`, it's also ok
Repository: tauri
Issue: [bug]  Borders on <body> do not work because width is a decimal 
Labels: type: bug,status: needs triage

### Describe the bug

This has been driving me nuts.  I have a window with decorations set to false. I tried to set a 1px border to body, but the right border is not showing up. I thought this could be because any child elements are overflowing, but this is not the case. I also removed the template css. After a lot of debgging I found out that this is because the width of the element is a decimal.

 

https://github.com/tauri-apps/tauri/assets/69343917/9f09aeb9-6833-431c-9dfe-c8f184222319



### Reproduction

Platform: Windows 10.

1. Create a new tauri app with cargo create-tauri-app
2. Select default settings. (I selected js, vanilla, npm)
3. Remove the default styles
4. Go to styles.css and give the body ``margin: 0`` and ``border: 1px solid black``
5. Run npm run tauri dev.

thats it

### Expected behavior

A black border to appear on both sides

### Platform and versions

```text
[✔] Environment
    - OS: Windows 10.0.22621 X64
    ✔ WebView2: 115.0.1901.183
    ✔ MSVC: Visual Studio Build Tools 2022
    ✔ rustc: 1.69.0 (84c898d65 2023-04-16)
    ✔ Cargo: 1.69.0 (6e9a83356 2023-04-12)
    ✔ rustup: 1.26.0 (5af9b9484 2023-04-05)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (default)
    - node: 18.17.0
    - npm: 9.6.7

[-] Packages
    - tauri [RUST]: 1.4.1
    - tauri-build [RUST]: 1.4.0
    - wry [RUST]: 0.24.3
    - tao [RUST]: 0.16.2
    - @tauri-apps/api [NPM]: 1.4.0
    - @tauri-apps/cli [NPM]: 1.4.0

[-] App
    - build-type: bundle
    - CSP: default-src 'self'; img-src 'self' asset: https://asset.localhost
    - distDir: ../dist
    - devPath: http://localhost:1420/
    - framework: Svelte
    - bundler: Vite
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: vscode
Issue: Allow extension link detection to run on exception popups
Labels: feature-request,debug

![image](https://github.com/microsoft/vscode/assets/1078012/8fd14c40-3e7f-4214-94cd-749b621a139d)

This exception text includes a non-file URI (`package:`) that the Dart extension knows how to translate to a file path. There's a terminal link provider that would make this URI clickable in the terminal - it'd be nice if there was an option to run it here.

(yes, enabling All Exceptions would cause the debugger to break there, but that's not what developers tend to run with so it's inconvenient to enable it and re-trigger your exception when the code you want to jump to is already written there in front of you)

This is slightly similar to https://github.com/microsoft/vscode/issues/157500, which is for the test peek window.
Repository: next.js
Issue: Inaccurate sourcemaps for sources under node_modules
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: #85~20.04.1-Ubuntu SMP Mon Jul 17 09:42:39 UTC 2023
Binaries:
  Node: 18.16.0
  npm: 9.5.1
  Yarn: 1.22.18
  pnpm: 8.6.7
Relevant Packages:
  next: 13.4.12
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: N/A
Next.js Config:
  output: N/A
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

_No response_

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/replayio/nextjs-inaccurate-sourcemaps

### To Reproduce

- `npm run build`
- upload `.next/static/chunks/main-26f0defd1fe4aedb.js[.map]` to https://evanw.github.io/source-map-visualization/
- select `webpack://_N_E/node_modules/@swc/helpers/esm/_interop_require_wildcard.js` as the original source
- for comparison, upload `.next/static/chunks/pages/_app-27374a655d3a2ebe.js[.map]` to https://evanw.github.io/source-map-visualization/ and select `webpack://_N_E/src/_interop_require_wildcard.js`

Alternatively, you can look at these sourcemaps here:
- `webpack://_N_E/node_modules/@swc/helpers/esm/_interop_require_wildcard.js`: https://app.replay.io/recording/5072126e-507f-43d9-8c9e-889ad2bfd0dd/sourcemap/o4-80-c194bb-ec5646
- `webpack://_N_E/src/_interop_require_wildcard.js`: https://app.replay.io/recording/5072126e-507f-43d9-8c9e-889ad2bfd0dd/sourcemap/o6-6-c194bb-5d30d7


### Describe the Bug

I've noticed that the sourcemaps produced by Next.js are inaccurate for some sources, making it impossible for debuggers to show scopes with original (rather than generated) variable names.
This seems to be the case for all sources under `node_modules`.
To reproduce the problem I've used create-next-app to create an app and copied `node_modules/@swc/helpers/esm/_interop_require_wildcard.js` to `src/_interop_require_wildcard.js`. This is what [a sourcemap visualizer](https://evanw.github.io/source-map-visualization/) shows for these two copies of the same source:

`node_modules/@swc/helpers/esm/_interop_require_wildcard.js`:

![Screenshot_2023-07-27_13-49-26](https://github.com/vercel/next.js/assets/16060807/ad4a9cdb-e2cf-40ef-a9de-bbd5891ea6d0)

`src/_interop_require_wildcard.js`:

![Screenshot_2023-07-27_13-50-09](https://github.com/vercel/next.js/assets/16060807/a8c36cb7-4711-4846-a0dc-fc9d2de54b40)


### Expected Behavior

Sourcemaps for sources under `node_modules` should be accurate. 

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: pytorch
Issue: Allow settingsetGraphExecutorOptimize default for all threads
Labels: oncall: jit

### 🚀 The feature, motivation and pitch

Our teams have had numerous issues with torchscipt optimization and have had to disabled it to avoid breaking the code.

I recently debugged one such issue here: https://github.com/pytorch/pytorch/issues/106128

`torch::jit::setGraphExecutorOptimize` sets a thread-local variable, but the model may be run on a different thread.  This was difficult to debug when a change to our test execution framework started running unit tests on new threads, but the model was only loaded once and reused across the tests.

Disabling optimization as a workaround would be much easier if it could be set globally for all threads.  

### Alternatives

Surfacing and resolving optimizer bugs instead of working around them and sacrificing performance would be ideal, but when it blocks research work we need a stable workaround.

### Additional context

Refer to https://github.com/pytorch/pytorch/issues/106128 for an example.

cc @EikanWang @jgong5 @wenzhe-nrv @sanchitintel
Repository: storybook
Issue: [Bug]: static directory is duplicated inside storybook --output-dir
Labels: bug,needs triage

### Describe the bug

If I build storybook in custom directory `storybook build --output-dir dist/storybook`, it creates one more `static` directory with all content. After this I have 2 directories, `dist/static` and `dist/storybook/static` with same content.

### To Reproduce

_No response_

### System

```shell
Environment Info:

  System:
    OS: Windows 10 10.0.22621
    CPU: (24) x64 AMD Ryzen 9 3900XT 12-Core Processor
  Binaries:
    Node: 20.3.1 - C:\Program Files\nodejs\node.EXE
    npm: 9.7.2 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.22621.1992.0), Chromium (115.0.1901.183)
  npmPackages:
    @storybook/addon-actions: ^7.1.1 => 7.1.1
    @storybook/addon-backgrounds: ^7.1.1 => 7.1.1
    @storybook/addon-controls: ^7.1.1 => 7.1.1
    @storybook/addon-docs: ^7.1.1 => 7.1.1
    @storybook/addon-essentials: ^7.1.0 => 7.1.0
    @storybook/addon-links: ^7.1.1 => 7.1.1
    @storybook/addon-measure: ^7.1.1 => 7.1.1
    @storybook/addon-outline: ^7.1.1 => 7.1.1
    @storybook/addon-toolbars: ^7.1.1 => 7.1.1
    @storybook/addon-viewport: ^7.1.1 => 7.1.1
    @storybook/blocks: ^7.1.0 => 7.1.0
    @storybook/react: ^7.1.0 => 7.1.0
    @storybook/react-vite: ^7.1.0 => 7.1.0
    @storybook/testing-library: ^0.2.0 => 0.2.0
```


### Additional context

_No response_
Repository: node
Issue: Memory leak - Base class instance
Labels: memory

### Version

16.6.0

### Platform

window

### Subsystem

_No response_

### What steps will reproduce the bug?

I have created Node.js TypeScript app having get method which will create an object of a class which inherit base class.
I have run `node --inspect` and see that the base class instance existing in memory after API request completed.

![image](https://github.com/expressjs/express/assets/32077544/2afe372d-cd4b-421a-a51e-82b419fda5dd)

`App.ts`:
```ts
import express from 'express';
import { welcome } from './welcome';
const app = express();
const port = 3000;

app.get('/', (req, res) => {
	const screen: any = {}
	screen.test = new welcome();	
        delete screen.test;
	res.send('Hello World!');
});

app.listen(port, () => {
	return console.log(`Express is listening at http://localhost:${port}`);
});
```

`basecontroll.ts`:
```ts
export class BaseController {
	constructor() {
		console.log('BaseController');
	}
}
```


`welcome.ts`:
```ts
import { BaseController } from "./basecontroller";

export class welcome extends BaseController {
	constructor() {
		super()
		console.log("welecome");

	}
}
```

I have tried to delete `welcome` object forcefully like `delete screen.test` but still base class instance existing in memory.

I have tried below command but we can't do this for each class 

`delete screen.test.__proto__.__proto__.constructor`

This is working but it just temporary.

`package.json`:
```json
{
  "name": "nodejsmemoryleak",
  "version": "1.0.0",
  "description": "",
  "main": "dist/index.js",
  "types": "dist/index.d.ts",
  "scripts": {
    "start": "tsc && node --inspect dist/app.js",
    "build": "tsc"
  },
  "keywords": [],
  "author": "",
  "license": "ISC",
  "devDependencies": {
    "@types/express": "^4.17.1",
    "nodemon": "^3.0.1",
    "ts-node": "^10.9.1",
    "typescript": "^5.1.6"
  },
  "dependencies": {
    "express": "^4.17.1"
  }
}
```
In my case, All class inherit base class so I can see multiple base instance exist in memory for my application.

I have created `welcome1` class which is also inheriting same `BaseController`. below is the memory snapshot after executing below code
![image](https://github.com/expressjs/express/assets/32077544/ee2a2979-6612-4bb1-85b4-c14b2c19a220)

![image](https://github.com/expressjs/express/assets/32077544/b52284ca-d52c-458c-8ffd-d305c7180da1)


### How often does it reproduce? Is there a required condition?

_No response_

### What is the expected behavior? Why is that the expected behavior?

it should clean base class object

### What do you see instead?

![image](https://github.com/nodejs/node/assets/32077544/d29acee3-0036-4b65-9448-5a5271fda8cc)


### Additional information

_No response_
Repository: pytorch
Issue: torch._subclasses.fake_tensor.DynamicOutputShapeException: aten.nonzero.default
Labels: triaged,module: fakeTensor

Hi team, I'm trying to grab a computational graph using FakeTensor, but encountered DynamicOutputShapeException exception.

PyTorch Version: 2.0.1+cu118


```
import torch
from torch._subclasses.fake_tensor import FakeTensorMode
import traceback
from torch.fx.experimental.symbolic_shapes import ShapeEnv
from torch._dynamo.output_graph import config

a = torch.ones([1, 0])
mode = FakeTensorMode()

a = mode.from_tensor(a)
try:
    with mode:
        b = torch.nonzero(a)
except Exception as e:
    traceback.print_exc() 
```

The stacktrace is:

```
Traceback (most recent call last):
  File "<ipython-input-15-5efd30f1231c>", line 13, in <cell line: 11>
    b = torch.nonzero(a)
  File "/usr/local/lib/python3.10/dist-packages/torch/utils/_stats.py", line 20, in wrapper
    return fn(*args, **kwargs)
  File "/usr/local/lib/python3.10/dist-packages/torch/_subclasses/fake_tensor.py", line 987, in __torch_dispatch__
    return self.dispatch(func, types, args, kwargs)
  File "/usr/local/lib/python3.10/dist-packages/torch/_subclasses/fake_tensor.py", line 1162, in dispatch
    op_impl_out = op_impl(self, func, *args, **kwargs)
  File "/usr/local/lib/python3.10/dist-packages/torch/_subclasses/fake_tensor.py", line 403, in dyn_shape
    raise DynamicOutputShapeException(func)
torch._subclasses.fake_tensor.DynamicOutputShapeException: aten.nonzero.default
```


So, anyone can help me to bypass this exception with nonzero operator?

Any response will be appreciated, thanks.
Repository: stable-diffusion-webui
Issue: [Bug]: Image generation hangs on the last step of generation. SDXL
Labels: bug-report,sdxl

### Is there an existing issue for this?

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

### What happened?

When generating images using the SD XL base model, the images start rendering fine, but the last step of the generation takes longer than the rest of the image combined.
Tested with regular, medvram and lowvram, multiple samplers and steps.

Testing done with 3060ti, 8 gigs of vram.
32 gigs of ram


### Steps to reproduce the problem

1. Go to .... 
2. Press ....
3. ...


### What should have happened?

-

### Version or Commit where the problem happens

1.5, latest build

### What Python version are you running on ?

Python 3.10.x

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

Windows

### What device are you running WebUI on?

_No response_

### Cross attention optimization

xformers

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

Google Chrome

### Command Line Arguments

```Shell
--autolaunch --xformers --opt-sdp-attention --no-half-vae --opt-channelslast
```


### List of extensions

Extensions disabled

### Console logs

```Shell
Console shows nothing of substance.
```


### Additional information

_No response_
Repository: vscode
Issue: Remove Legacy Diffing Algorithm
Labels: debt,diff-editor

Now that the new diffing algortihm is the default, we can remove the legacy diffing algortihm.
Repository: PowerToys
Issue: Adds margins to regular windows snapping when installed
Labels: Issue-Bug,FancyZones-Layouts,Priority-1

### Microsoft PowerToys version

0.71.0

### Installation method

Microsoft Store

### Running as admin

None

### Area(s) with issue?

FancyZones

### Steps to reproduce

When Fancy Zones enabled just regular Windows snapping adds a margin around windows. Unclear exactly when and how this happens but my snapped windows always seem to endup with a margin.

Super annoying, why would you EVER want to waste screen space like this? It should also not be the default for fancy zones to add margins around windows, disabling fancy zone margins also seems to have bugs and needs doing on every layout.

### ✔️ Expected Behavior

No margins ever around windows snapped with Windows built in snapping.

If you re-snap the window it does appear to fix it.

### ❌ Actual Behavior

Margins are added

### Other Software

_No response_
Repository: stable-diffusion-webui
Issue: [Feature Request]: RTX IO?
Labels: enhancement,extension-request

### 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 ?

Just a thought I just had... would it be possible to use RTX IO for faster loading times?

### Proposed workflow

see above

### Additional information

_No response_
Repository: material-ui
Issue: [Skeleton][material][joy] inferring dimensions only works for "text" variant
Labels: docs,package: material-ui,component: skeleton,ready to take,package: joy-ui

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

Link to live example: https://codesandbox.io/s/clever-resonance-wl4snj?file=/Demo.js:454-517

Steps:

1. fork [Skeleton "Inferring Dimensions"](https://mui.com/material-ui/react-skeleton/#inferring-dimensions) demo Codesandbox https://codesandbox.io/s/xtdlsy?file=/Demo.js
2. add the prop `variant="rounded"` or `variant="rectangular"` to `<Skeleton />`
3. see result


### Current behavior 😯

Skeleton inferring dimensions missing padding when variant prop is set:
<img width="577" alt="image" src="https://github.com/mui/material-ui/assets/143295/23bdbeae-1d7d-41a5-9b73-12b1b7d0a724">


### Expected behavior 🤔

Skeleton inferring dimensions not missing padding when variant prop is set:

### Context 🔦

just trying to use the Skeleton inferring dimensions feature w/ variants

### Your environment 🌎

skipped `@mui/envinfo` output - using Codesandbox w/ Chrome: 114.0.5735.248
Repository: vscode
Issue: Ghost text hover sometimes has empty rendering
Labels: bug,inline-completions

Trigger suggest widget
Wait for ghost text to appear
Hover over ghost text

Notice that the rendering is broken. It does not say how many items are there.

![Screenshot 2023-07-27 at 16 36 33](https://github.com/microsoft/vscode/assets/1926584/e6e35d83-f290-4e75-812c-f223fbe5097a)
Repository: vscode
Issue: Left click on Ghost text should show hover and pass focus
Labels: feature-request,inline-completions

Have some ghost text
Click on it
Nothing happens

I think we could show the hover and pass focus to it. What do you think?
My hypothesis is that new users might explore ghost text by cliking on it, and hover might provide some value.

Bonus bug: right click on ghost text -> hides it and does not do anything.
IMHO it should just open the regular editor context menu.
Repository: storybook
Issue: [Bug]: @types/jest is updated to 29.6.1 even if version in package.json is lower
Labels: bug,needs triage

### Describe the bug

The package @types/jest is updated inside node_module file to 29.6.1 even if version in package.json is lower like 27.*. 

This problem breaks the compatibility of storybook with Stencil which is not compatible with version 29.X and more globally breaks probably the compatibility with Jest if you don't have version 29.x installed. 

### To Reproduce

Just run : npm install  @types/jest@27.5.1 jest@27.5.1 jest-cli@27.5.1  @storybook/addon-essentials
Check version of @types/jest in node_module. You will have 29.6.1 and NOT 27.5.1. 

### System

```shell
Environment Info:

  System:
    OS: macOS 13.2
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
  Binaries:
    Node: 18.16.1 - /usr/local/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 9.5.1 - /usr/local/bin/npm
  Browsers:
    Chrome: 115.0.5790.114
    Edge: 113.0.1774.57
    Safari: 16.3
  npmPackages:
    @storybook/addon-docs: ^7.1.1 => 7.1.1
    @storybook/addon-links: ^7.1.1 => 7.1.1
    @storybook/addon-viewport: ^7.1.1 => 7.1.1
    @storybook/html: ^7.1.1 => 7.1.1
    @storybook/html-webpack5: ^7.1.1 => 7.1.1
```


### Additional context

This problem happen just with some addons like @storybook/addon-essentials.