sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: storybook
Issue: [Bug]: Storybook fails to launch with `NODE_OPTIONS=--experimental-strip-types`
Labels: bug,needs triage

### Describe the bug

Storybook fails to launch when [`NODE_OPTIONS=--experimental-strip-types`](https://nodejs.org/api/typescript.html#type-stripping) is present in the environment. Removing the variable makes it work, but I would prefer not having to do that as I want my Node to be able to run Typescript.

```
SB_CORE-SERVER_0007 (MainFileEvaluationError): Storybook couldn't evaluate your .storybook/main.ts file.

Original error:
Error [ERR_REQUIRE_ESM]: require() of ES Module /.storybook/main.ts from /node_modules/@storybook/core/dist/common/index.cjs not supported.
Instead change the require of main.ts in /node_modules/@storybook/core/dist/common/index.cjs to a dynamic import() which is available in all CommonJS modules.
    at TracingChannel.traceSync (node:diagnostics_channel:315:14)
    at interopRequireDefault (/node_modules/@storybook/core/dist/common/index.cjs:145609:11)
    at serverRequire (/node_modules/@storybook/core/dist/common/index.cjs:145623:14)
    at loadMainConfig (/node_modules/@storybook/core/dist/common/index.cjs:151297:18)
    at loadMainConfig (./node_modules/@storybook/core/dist/common/index.cjs:151315:11)
    at async buildDevStandalone (./node_modules/@storybook/core/dist/core-server/index.cjs:256949:11)
    at async withTelemetry (./node_modules/@storybook/core/dist/core-server/index.cjs:255711:12)
    at async dev (./node_modules/storybook/dist/generate.cjs:738:506)
    at async Command.<anonymous> (./node_modules/storybook/dist/generate.cjs:740:245)
```

### Reproduction link

https://github.com/silverwind/storybook-node-strip

### Reproduction steps

1. Have Node.js 22.6.0 or higher installed
2. Clone repo
3. Run `npm run storybook`

### System

```bash
Storybook Environment Info:

  System:
    OS: macOS 14.5
    CPU: (16) arm64 Apple M3 Max
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.6.0 - /opt/homebrew/bin/node
    Yarn: 1.22.22 - /opt/homebrew/bin/yarn
    npm: 10.8.2 - /opt/homebrew/bin/npm <----- active
    pnpm: 9.7.0 - ~/.npm-global/bin/pnpm
  Browsers:
    Chrome: 127.0.6533.89
    Safari: 17.5
  npmPackages:
    @storybook/addon-essentials: 8.2.9 => 8.2.9
    @storybook/addon-interactions: 8.2.9 => 8.2.9
    @storybook/addon-links: 8.2.9 => 8.2.9
    @storybook/addon-onboarding: 8.2.9 => 8.2.9
    @storybook/blocks: 8.2.9 => 8.2.9
    @storybook/react: 8.2.9 => 8.2.9
    @storybook/react-vite: 8.2.9 => 8.2.9
    @storybook/test: 8.2.9 => 8.2.9
    eslint-plugin-storybook: 0.8.0 => 0.8.0
    storybook: 8.2.9 => 8.2.9
```


### Additional context

_No response_
Repository: godot
Issue: Misleading return value on Object::call_deferred
Labels: discussion,topic:core,breaks compat

### Tested versions

master

### System information

N/A

### Issue description

Call deferred is marked as returning Variant while it actually always returns null. 
This is misleading as it may confuse developers into thinking it can return something else.
Easily patchable by changing the method info in object.cpp
![Screenshot_20240813_185246_GitHub](https://github.com/user-attachments/assets/9fa0a8f3-a7c4-4bce-b3ec-4ce243ca63e7)


### Steps to reproduce

N/A

### Minimal reproduction project (MRP)

N/A
Repository: ollama
Issue: ollama - default tool support 
Labels: feature request

In the standard cli there should be some default tools like IPython (just like code interpreter, disabled by default), or so so that you can simply add it those tools to any model that supports such a tool, and a way to integrate custom tools, maybe someone wants to integrate their SD3 workflow, but it should be provided from the CLI itself, no?

as CLI flag wthout needing to use the ollama api, just CLI!
Repository: PowerToys
Issue: [PTRun] Better Fuzzy Match
Labels: Idea-Enhancement,Product-PowerToys Run,Needs-Triage

### Description of the new feature / enhancement

I want to work for #20672. I have come up with an algorithm for this:

Firstly, for each letter "query[i]", its score depends on its distance from the position of "query[i-1]"  in stringToCompare.

In order to achieve high scores for the first letter, the distance is set to the position of the word + the position of the letter in the word

Finally, through dynamic programming, the matching score can be obtained.

But I am not sure if it is truly feasible. moreover, this algorithm has another issue. Unlike the existing algorithm, a smaller score means a better result. To ensure minimal disruption, the score needs to be negated. Does the current code support negative scores?

Hope to receive some suggestions.



### Scenario when this would be used?

PTRun FuzzyMatch

### Supporting information

_No response_
Repository: vscode
Issue: Cmd-Click doesn't work on JSDoc {@link URL|LinkText} format
Labels: bug,typescript,javascript

<!-- ⚠️⚠️ 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: 
- OS Version: 

Steps to Reproduce:

1. Create a `.ts` file containing
   ```ts
   /**
    * {@link https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise/withResolvers|Promise.withResolvers}
    */
   ```
   This is one of the valid ways of providing link text according to https://jsdoc.app/tags-inline-link.
3. Cmd-Click (or Windows equivalent) on the URL
4. VSCode opens https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise/withResolvers%7CPromise.withResolvers, instead of https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise/withResolvers

When I tried `{@link http://www.google.com|Google}`, Cmd-Clicking on the link doesn't open anything, and logs
```
2024-08-13 12:04:55.265 [error] TypeError: Invalid URL
	at new URL (node:internal/url:797:36)
	at Object.canOpenExternalUri (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/simple-browser/dist/extension.js:1:6134)
```

Fortunately I can use `[Link Text]{@link URL}` format, but I expected VSCode to support any valid `@link` format.
Repository: vscode
Issue: History graph diff always shows horizontal scroll bar
Labels: bug,multi-diff-editor

<!-- ⚠️⚠️ 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

<!-- 🪓 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: 1.93.0-insider (922413f6d97e16c05b565398f33d95c306b1ceb7)
- OS Version: macOS Sonoma 14.5

Steps to Reproduce:

1. Open a Git repository.
2. Go to the source control view.
3. Click on a commit in the Incoming/Outgoing section.
4. A horizontal scroll bar is shown at the bottom, but scrolling has no effect.

https://github.com/user-attachments/assets/d65726ef-a9cd-45bf-9fdc-7f5bc43b12fa
Repository: ollama
Issue: Llama 3.1 70B high-quality HQQ quantized model - 99%+ quality of fp16 
Labels: model request

I'm not really sure if that's possible but adding that to ollama could really impact the performance on 4-bit quant option:

99%+ in all benchmarks in lm-eval relative performance to FP16 and similar inference speed to fp16 

url:
https://huggingface.co/mobiuslabsgmbh/Llama-3.1-70b-instruct_4bitgs64_hqq

<img width="604" alt="Screenshot 2024-08-13 at 19 03 57" src="https://github.com/user-attachments/assets/64cd0427-b7c7-4fb8-b846-15f172669248">

also this:

https://huggingface.co/ModelCloud/Meta-Llama-3.1-70B-Instruct-gptq-4bit

<img width="597" alt="Screenshot 2024-08-13 at 19 07 18" src="https://github.com/user-attachments/assets/c3518ffe-323d-42f0-9162-d188179797fb">
Repository: TypeScript
Issue: `importModuleSpecifierPreference: "non-relative"` should use self-name package imports
Labels: Suggestion,Awaiting More Feedback

### 🔎 Search Terms

- relative imports
- workspaces
- monorepo
- subpath export

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about auto imports and subpath exports.

### ⏯ Playground Link

_No response_

### 💻 Code

Full reduced test case: https://github.com/OliverJAsh/typescript-auto-imports-exports

Contents inlined below. TLDR:

- Two workspaces, `packages/a` and `packages/b`.
- `packages/b` depends on `packages/a`.

**Root files**:

`tsconfig.json`:
```json
{
  "compilerOptions": {
    "strict": true,
    "noEmit": true,
    "target": "ESNext",
    "module": "Node16",
    "moduleResolution": "Node16"
  }
}

```

`package.json`:
```json
{
  "private": true,
  "dependencies": {
    "typescript": "^5.5.4"
  },
  "workspaces": [
    "packages/a",
    "packages/b"
  ],
  "packageManager": "yarn@4.4.0"
}

```


**Package `a`**:

`packages/a/package.json`:
```json
{
  "name": "a",
  "private": true,
  "exports": {
    "./test": "./module.ts"
  }
}

```

`packages/a/module.ts`:
```ts
export const a = 1;

```

`packages/a/other-module.ts`:
```ts
// Try to import this
// Auto import uses a relative path here: `./module` ❌
a;

```

**Package `b`**:

`packages/b/package.json`:
```json
{
  "name": "b",
  "private": true,
  "dependencies": {
    "a": "workspace:^"
  }
}

```

`packages/b/module.ts`:
```ts
// Try to import this
// Auto import works correctly here: `a/test` ✅
a;

```



### 🙁 Actual behavior

- The auto import suggestion in `packages/b/other-module.ts` uses the subpath export defined in `packages/a/package.json`. The suggested import path is `a/test`. ✅
- The auto import suggestion in `packages/a/other-module.ts` does not use the subpath export defined in `packages/a/package.json`. Instead it uses a relative import. The suggested import path is `./module`.

It seems that TypeScript is not using the subpath export information for self-referencing imports.

### 🙂 Expected behavior

In both cases I would expect the subpath export to be used (rather than relative imports), otherwise you can end up with some verbose relative paths in the case of projects with deeply nested folders.

I would expect TypeScript to only use a relative import if a subpath export is not available.

### Additional information about the issue

_No response_
Repository: godot
Issue: Overlapping collision reports are non-deterministic when clicked despite sorting.
Labels: discussion,documentation,topic:physics,needs testing,topic:2d

### Tested versions

- Reproducible in: 4.3.rc3, 4.2.2.stable.

### System information

Windows 10 - Godot v4.3.rc3 - Vulkan (Forward+)

### Issue description

Despite setting both `set_physics_object_picking_sort` and `set_physics_object_picking_first_only` as `true`, input events triggered when clicking an area with overlapped collision shapes produces a seemingly random picked shape.

Changing the node tree order or the z-index setting has no apparent effect on the outcome.

### Steps to reproduce

As illustrated by the provided MRP, create two CollisionArea2D regions as children of an Area2D node.  Assign any shape to both CollisionAreas, and place them so that they partially overlap.  For the sake of telling them apart, the second is colored pink.  Attach the following script to the Area2D, and then connect the input_event signal to the _on_input_event function.

```gdscript
extends Area2D

func _ready():
    get_viewport().set_physics_object_picking_sort(true)
    get_viewport().set_physics_object_picking_first_only(true)

func _on_input_event(viewport, event, shape_idx):
    if event is InputEventMouseButton and event.pressed and event.button_index == MOUSE_BUTTON_LEFT:
        var shape_owner = shape_owner_get_owner(shape_find_owner(shape_idx))
        print("Picking '%s'" % [shape_owner.name])
```

**Important: Turn on "Visible Collision Shapes" in the Debug menu to see the shapes when running the MRP.**

Clicking inside either the blue or pink CollisionShape2D regions alone works as expected.  However, when clicking in the space where they overlap, the debug output in the provided GDScript shows that the `shape_idx` passed to the `_on_input_event` function can be either shape, and which shape it is changes with each click.  

As both 'sort' and 'pick first' are enabled, it's expected that the "top" pink shape would be the only one sent to the `_on_input_event` function when the overlapped area is clicked.

### Minimal reproduction project (MRP)

[CollisionPickOrdering.zip](https://github.com/user-attachments/files/16603097/CollisionPickOrdering.zip)
Repository: react-native
Issue: ScrollView doesn't scroll when overflows the parent view
Labels: Issue: Author Provided Repro,Component: ScrollView,Newer Patch Available

### Description

If we have a parent view, and render Touch like elements, (for eg. - Button, Pressable, TouchableOpacity) outside the Parent View with overflow:'visible' the Touch works fine.
But if I render a ScrollView outside the parent view, it doesn't scroll.

### Steps to reproduce

https://snack.expo.dev/@rtk_jain/scrollview-does-not-work-when-overflowing

### React Native Version

0.74.3

### Affected Platforms

Runtime - Android, Runtime - iOS, Runtime - Web

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

```text
System:
  OS: macOS 14.4
  CPU: (12) arm64 Apple M3 Pro
  Memory: 82.45 MB / 18.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 20.15.1
    path: ~/.nvm/versions/node/v20.15.1/bin/node
  Yarn:
    version: 3.6.4
    path: ~/.nvm/versions/node/v20.15.1/bin/yarn
  npm:
    version: 10.7.0
    path: ~/.nvm/versions/node/v20.15.1/bin/npm
  Watchman:
    version: 2024.07.15.00
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.15.2
    path: /opt/homebrew/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.5
      - iOS 17.5
      - macOS 14.5
      - tvOS 17.5
      - visionOS 1.2
      - watchOS 10.5
  Android SDK:
    API Levels:
      - "29"
      - "30"
      - "33"
      - "34"
    Build Tools:
      - 29.0.2
      - 30.0.3
      - 33.0.0
      - 34.0.0
      - 35.0.0
    System Images:
      - android-29 | ARM 64 v8a
      - android-29 | Intel x86 Atom
      - android-29 | Intel x86_64 Atom
      - android-29 | Google APIs ARM 64 v8a
      - android-29 | Google APIs Intel x86 Atom
      - android-29 | Google APIs Intel x86_64 Atom
      - android-29 | Google Play ARM 64 v8a
      - android-29 | Google Play Intel x86 Atom
      - android-29 | Google Play Intel x86_64 Atom
    Android NDK: Not Found
IDEs:
  Android Studio: 2024.1 AI-241.18034.62.2411.12071903
  Xcode:
    version: 15.4/15F31d
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.10
    path: /usr/bin/javac
  Ruby:
    version: 2.6.10
    path: /usr/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.74.3
    wanted: 0.74.3
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: true
  newArchEnabled: false
```


### Stacktrace or Logs

```text
No Stack Trace
```


### Reproducer

https://snack.expo.dev/@rtk_jain/scrollview-does-not-work-when-overflowing

### Screenshots and Videos

_No response_
Repository: godot
Issue: undefined symbol: AudioDriverScriptProcessor::finish_driver()
Labels: bug,platform:web,topic:buildsystem,topic:porting

### Tested versions

Reproducible in master

### System information

Any

### Issue description

When compiling web with address sanitizer it does not find the function body because it is missing from the source code
`wasm-ld: error: platform/web/audio_driver_web.web.template_debug.dev.wasm32.nothreads.o: undefined symbol: AudioDriverScriptProcessor::finish_driver()`

### Steps to reproduce

`scons platform=web target=template_debug threads=no dev_build=yes use_asan=yes`

### Minimal reproduction project (MRP)

N/A
Repository: godot
Issue: MOUSE_MODE_CAPTURED - Remote Desktop (Raw Input Issue)
Labels: bug,platform:windows,topic:input

### Tested versions

- Reproducable in Godot 4.2.2 Stable

### System information

Windows 10 - Godot 4.2.2 Stable

### Issue description

When editing a game using remote desktop you are unable to use "mouse_mode = MOUSE_MODE_CAPTURED"
All other mouse modes work. I assume this is because that is the only mouse mode that uses raw input for mouse motion and because I am editing remote the mouse input is external.

### Steps to reproduce

use RDP to edit a godot project and set mouse mode to MOUSE_MODE_CAPTURED
[Primordial-main.zip](https://github.com/user-attachments/files/16605207/Primordial-main.zip)


### Minimal reproduction project (MRP)

use RDP to edit a godot project and set mouse mode to MOUSE_MODE_CAPTURED
Repository: deno
Issue: `Deno has panicked` via `task` command and `package.json` starting version `1.45.3`
Labels: needs info

Facing a crash with `Deno has panicked` when trying to run a script via `deno task dev` targeting even an empty script.

Error details:
```
Platform: macos aarch64
Version: 1.45.5
Args: ["deno", "task", "dev"]

thread 'main' panicked at /Users/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/deno_semver-0.5.7/src/lib.rs:275:32:
programming error: cannot use matches with a tag: latest
```

No `deno.lock` file in project root.

`package.json`:

``` json
{
  "scripts": {
    "dev": "deno run server/router.ts",
  }
}
```

`router.ts` file exists and absolutely empty.

Running `deno run server/router.ts` cause no error.

Downgrade Deno to version `1.44.4` helped to avoid an error. Tried other versions: 

- [`1.45.4`](https://github.com/denoland/deno/releases/tag/v1.45.4), [`1.45.3`](https://github.com/denoland/deno/releases/tag/v1.45.3) crashes too. 

- [`1.45.2`](https://github.com/denoland/deno/releases/tag/v1.45.2) works well
Repository: pytorch
Issue: Number of kernels generated increased after changes to statically_known_multiple_of
Labels: triaged,oncall: pt2,module: dynamic shapes,module: inductor

### 🐛 Describe the bug

In https://github.com/pytorch/pytorch/pull/131649, we change the behavior of `statically_known_multiple_of`, which led an increased number of kernels generated in the unbacked symint cases (e.g. https://github.com/pytorch/pytorch/pull/133276). 

In other words, it decreases the fusion opportunities. Is there anything we can do to get the fusion opportunities back?

cc @ezyang @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire @jansel 

### Error logs

_No response_

### Minified repro

_No response_

### Versions

main
Repository: go
Issue: runtime: SIGSEGV in preemptone (riscv64)
Labels: help wanted,NeedsInvestigation,arch-riscv,Tools,compiler/runtime

```
#!watchflakes
default <- goarch == "riscv64" && builder == "linux-riscv64-mengzhuo" && `sigcode=1 addr=0xc0`  
```

Original flakes

```
#!watchflakes
default <- pkg == "golang.org/x/tools/internal/imports" && test == "TestModReplace2"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8739701229570308529)):

    === RUN   TestModReplace2
    SIGSEGV: segmentation violation
    PC=0x54520 m=12 sigcode=1 addr=0xc0
    
    goroutine 0 gp=0x3f504421c0 m=12 mp=0x3f50526708 [idle]:
    runtime.preemptone(0x3f504421c0?)
    	/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/proc.go:6297 +0x38 fp=0x3f5043ff28 sp=0x3f5043ff10 pc=0x54520
    runtime.preemptall()
    	/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/proc.go:6275 +0x60 fp=0x3f5043ff50 sp=0x3f5043ff28 pc=0x544c0
    runtime.forEachPInternal(0x2fa878)
    ...
    a3  0x223abf02	a4  0x3f98bb8000
    a5  0x31a7d99	a6  0x29ab75fd
    a7  0x1187f0	s2  0x3f5043fed0
    s3  0x3f50526708	s4  0x3f50474000
    s5  0x3f50241500	s6  0xffffffff
    s7  0x4	s8  0x3f50038688
    s9  0x3f5043fdc8	s10 0x2fa878
    s11 0x3f504421c0	t3  0x2eb2a46908caf
    t4  0xffffffffffffffff	t5  0x1913e15049b3
    t6  0x3f50038408	pc  0x54520


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: flutter
Issue: Tracking for new tokens
Labels: framework,f: material design,a: fidelity,c: proposal,P2,team-design,triaged-design

              As i understand these tokens aren't currently used by any widgets that support these tokens. We can keep a issue tracker to make sure to use new tokens.

_Originally posted by @TahaTesser in https://github.com/flutter/flutter/pull/153385#discussion_r1715905739_

This issue is to keep tracking any newly added tokens for widgets. 

* Some widgets use hard-coded defaults because there was no tokens available, and later even if the token is available, the hard-corded defaults cannot be automatically updated by token generator. Therefore, once tokens are updated, we should check whether new tokens should be applied to the according widgets.

* New tokens may also mean features that we haven't supported. 
   - [ ] [Selected status for menu item](https://m3.material.io/components/menus/specs#dc2e3722-43be-4a95-a09b-b9fba9180401), tokens are available in 5.0.0(https://github.com/flutter/flutter/pull/153385)
   - [ ] [Update Material 3 `DatePicker` default size to use updated tokens ](https://github.com/flutter/flutter/issues/153505), tokens are updated in https://github.com/flutter/flutter/pull/120149

CC: @TahaTesser