sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: neovim
Issue: Build fails on macOS
Labels: bug,platform:macos,build,needs:repro

### Problem

I tried to remove build and .deps directories, but still I get this error.

```
OK        Successfully built LuaJIT
gmake[2]: выход из каталога «/Users/m.doronin/code/neovim/.deps/build/src/luajit/src»
==== Successfully built LuaJIT 2.1 ====
==== Installing LuaJIT 2.1.1707061634 to /Users/m.doronin/code/neovim/.deps/usr ====
mkdir -p /Users/m.doronin/code/neovim/.deps/usr/bin /Users/m.doronin/code/neovim/.deps/usr/lib /Users/m.doronin/code/neovim/.deps/usr/include/luajit-2.1 /Users/m.doronin/code/neovim/.deps/usr/share/man/man1 /Users/m.doronin/code/neovim/.deps/usr/lib/pkgconfig /Users/m.doronin/code/neovim/.deps/usr/share/luajit-2.1/jit /Users/m.doronin/code/neovim/.deps/usr/share/lua/5.1 /Users/m.doronin/code/neovim/.deps/usr/lib/lua/5.1
cd src && install -m 0755 luajit /Users/m.doronin/code/neovim/.deps/usr/bin/luajit-2.1.1707061634
/bin/sh: line 0: cd: src: No such file or directory
gmake[1]: *** [Makefile:131: install] Ошибка 1
gmake[1]: выход из каталога «/Users/m.doronin/code/neovim/.deps/build/src/luajit»
[117/136] Performing build step for 'treesitter'
[1/2] Building C object CMakeFiles/tree-sitter.dir/lib/src/lib.c.o
[2/2] Linking C static library libtree-sitter.a
ninja: build stopped: subcommand failed.
make: *** [Makefile:88: deps] Error 1
```

### Steps to reproduce

`make CMAKE_BUILD_TYPE=RelWithDebInfo`

### Expected behavior

Build is successful.

### Neovim version (nvim -v)

commit 422b090

### Vim (not Nvim) behaves the same?

—

### Operating system/version

macOS 14.2

### Terminal name/version

—

### $TERM environment variable

—

### Installation

build from repo
Repository: vscode
Issue: Refresh all problems in the problems view with a button
Labels: feature-request,api,workbench-diagnostics

There are situation where problems in the problems view get stale. This happens to me even with TypeScript sometimes and there are cases in ESLint were this can happen as well. Adding some UI to the problems view were we can trigger are refresh would be cool. Since diagnostics are pull in VS Codes API we woulld need to do the following:

- having API to register a problem refresh provider
- when the UI is trigger the registered providers are notified
- some addition UI in the problems view to see which problems are refreshable (e.g. TS, ESLint, ...)


LSP has a pull model. For those server which register a pull provider we could automatically hook the refresh provider.
Repository: godot
Issue: proceduralsky is painfully slow on android compatibility mode
Labels: platform:android,topic:rendering,needs testing,performance

### Tested versions

4.3, 4.2, 4.1, 4.0

### System information

android [j2prime](https://www.gsmarena.com/samsung_galaxy_j2_prime-8424.php) android j7 (or any 2016~ phone) godot 4.3 dev3

### Issue description

+proceduralsky is really slow on android (20-30fps) on an empty scene
+when world environment sky is set to color or panorama the framerate is 60+

### Steps to reproduce

+create empty godot project (gl_compatibility)
+add environment
+add proceduralsky
+export to android with remote debug enabled
+fps ~30
+now remove sky
+fps 60+

### Minimal reproduction project (MRP)

N/A
Repository: next.js
Issue: Enabling scroll restoration causes iOS history snapshot to be blank
Labels: bug,Navigation

### Link to the code that reproduces this issue

https://github.com/khansherdil/test-nxt-load-ios

### To Reproduce

#### Spin up a Next.js 14.1 project (pages directory, iOS Safari/Chrome)
1. Enable `{experimental: scrollRestoration: true}}`
2. Use the router to navigate to a different page
3. Now navigate back by swiping left
4. Previous page snapshot is now blank


#### Live reproduction
1. Visit https://test-nx-load.vercel.app/ on your iPhone
2. Scroll all the way down to 'GO COLL'
3. Navigate back using iOS swipe left to go back
4. Previous page snapshot is now blank

#### Video of reproduction

https://github.com/vercel/next.js/assets/47143154/0e4b84b3-dcfb-4bc0-8693-5dbfb5dc2884



### Current vs. Expected behavior

#### Current
Previous page snapshot is blank

#### Expected
Previous page snapshot should be a snapshot of previously visited screen

### Provide environment information

```bash
OS: iOS Mobile 
------------------
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP Thu Oct 5 21:02:42 UTC 2023
Binaries:
  Node: 20.5.1
  npm: 9.8.0
  Yarn: 1.22.18
  pnpm: 7.5.1
Relevant Packages:
  next: 14.1.0
  eslint-config-next: 14.1.0
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.3
Next.js Config:
  const nextConfig = {
  reactStrictMode: true,
  experimental: {
    scrollRestoration: true,
  },
};
```


### Which area(s) are affected? (Select all that apply)

Routing (next/router, next/navigation, next/link)

### Which stage(s) are affected? (Select all that apply)

Vercel (Deployed)

### Additional context

Issue happens on a customer facing product that's deployed on Vercel. Occurs on both Safari and Chrome.
Repository: vscode
Issue: Git - Warn Unsaved Files Before Typing Commit Message
Labels: bug,git

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
When you commit a change, VSCode warns you if there are unsaved files. When this happens, you then have to **retype** the commit message.

It would be therefore be much more useful if it warned you that there were unsaved changes _before_ you actually type a commit message, so you could then save the changes beforehand.
Repository: pytorch
Issue: Please consider adding more optimization support for multi-layer recurrent neural networks to improve fitting speed.
Labels: module: nn,module: rnn,triaged,needs research

### 🚀 The feature, motivation and pitch

I attempted to construct a small-scale natural language processing model using torch.nn.GRU(num_layers=N, bidirectional=True). During training, the loss consistently decreased, but at a slow rate, especially after several dozen epochs, the decrease in loss was not very significant.

I changed my strategy and switched to using multiple single-layer GRUs, with LayerNorm and residual connections added in between. The improvement in fitting speed was evident.

I believe that adding more optimization support for multi-layer recurrent neural networks to improve fitting speed is necessary. Otherwise, support for multi-layer bidirectional becomes more of a hassle than a convenience.


cc @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki @zou3519
Repository: go
Issue: x/tools/go/analysis: identify test-only packages
Labels: Proposal,Proposal-Accepted,Tools,Analysis

### Proposal Details

Some analyzers need to customize their behavior based on the context in which the code is running, e.g. to restrict certain (inefficient) APIs to only be used in tests. 

At the moment analyzers have no way to determine if the file they are analyzing is only used in tests. One way of achieving this today is to check if the file ends in `_test.go`. This works for the most part. However it fails for libraries that are not tests themselves but can only be used in tests. Some build systems can enforce this. See bazels [`testonly` attribute](https://bazel.build/reference/be/common-definitions).

One way to support this would be similar to the version support based on `go/types.Info.FileVersions` which is a map from `*ast.File` to the version string. A map in the `analysis.Pass` from `*ast.File` to a bollean that says if the file is only used in tests or not would solve this problem.

Note: it is not a property of the package to be analyzed but the individual files because when analyzing a test package it consists of test files and the actual package source files.
Repository: storybook
Issue: Automigration: Vue3 replaced `app` export with `setup`
Labels: bug,vue3,automigrations,sev:S3

### Describe the bug

In 6.x @storybook/vue3 exported a Vue application instance called app. In 7.0, this has been replaced by a setup function that can be used to initialize the application in your .storybook/preview.js:

Before:

```js
import { app } from "@storybook/vue3";
import Button from "./Button.vue";

app.component("GlobalButton", Button);
```

After:

```js
import { setup } from "@storybook/vue3";
import Button from "./Button.vue";

setup((app) => {
  app.component("GlobalButton", Button);
});
```

Write an automigration for it.

### To Reproduce

_No response_

### System

_No response_

### Additional context

_No response_
Repository: next.js
Issue: Root loading.js doesn't work when navigating in nested routes (e.g. navigating from child to grandchild route)
Labels: bug,Navigation,linear: next

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/root-loading-nested-routes-wzthqy

### To Reproduce

1. Start the application
2. Navigate to child route (root loading.js will be used as loading UI)
3. Navigate from child route to grandchild route (root loading.js will not be used as loading UI)

### Current vs. Expected behavior

Based on (my understanding of) the docs, I would expect for loading.js to behave in a similar way as layout.js and error.js. 
In my example, the root layout.js is used for nested routes at any level (as expected), and I would expect for the root loading.js to work as a loading UI for all nested routes. 
Instead, loading.js works only for the route where it's placed and direct navigation from it, while it doesn't work when navigating from child to grandchild routes.

So, to sum up:
- navigating from root to child route -> root loading.js is used
- navigating **directly** from root to grandchild route -> root loading.js is used
- navigating from child route to grandchild route -> root loading.js is **not** used

If this is working as intended, please disregard my issue, but I would suggest to make this clearer in the docs [here](https://nextjs.org/docs/app/building-your-application/routing/loading-ui-and-streaming).
On top of that, I think that having the root loading.js to work as a fallback loading UI for the entire application (unless it's overrun by another loading.js down in the routes structure) would be very useful and expected by many, since it feels more consistent with layout.js and error.js behaviour. As of now, for a generic loading UI, we need to copy the same loading.js through all the app, which is not ideal (and leads to swapping from a loading.js to another loading.js when the latter is loaded, but this is [another issue](https://github.com/vercel/next.js/issues/56344)).
Many thanks!

### Provide environment information

```bash
latest, canary and I think everywhere in general

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro
Binaries:
  Node: 20.11.0
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.1.0
  eslint-config-next: 14.1.0
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.3
Next.js Config:
  output: standalone
```


### Which area(s) are affected? (Select all that apply)

App Router, Routing (next/router, next/navigation, next/link)

### Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local), next start (local), Other (Deployed)

### Additional context

_No response_

<sub>[NEXT-3292](https://linear.app/vercel/issue/NEXT-3292/root-loadingjs-doesnt-work-when-navigating-in-nested-routes-eg)</sub>
Repository: storybook
Issue: [Bug]: Hot reload on docs page causes scroll to top
Labels: bug,help wanted,sev:S4

### Describe the bug

When applying a hot-reload/fast-refresh while scrolled down and looking at the docs page, the page scrolls back to the top

This is quite annoying if you're using the docs page to see multiple stories at once while working on them

### To Reproduce

I've reproduced this using the sandboxes for `7.6.16` and `8.0.0-beta.2` with no modifications after running `npx sb sandbox`.

### System

```bash
Storybook Environment Info:

  System:
    OS: macOS 14.3
    CPU: (8) x64 Intel(R) Core(TM) i7-1068NG7 CPU @ 2.30GHz
    Shell: 5.1.8 - /usr/local/bin/bash
  Binaries:
    Node: 18.8.0 - ~/.asdf/installs/nodejs/18.8.0/bin/node
    Yarn: 1.22.21 - ~/.asdf/installs/nodejs/18.8.0/bin/yarn
    npm: 8.18.0 - ~/.asdf/installs/nodejs/18.8.0/bin/npm <----- active
    pnpm: 8.11.0 - ~/.asdf/installs/nodejs/18.8.0/bin/pnpm
  Browsers:
    Chrome: 121.0.6167.184
    Edge: 121.0.2277.128
    Safari: 17.3
  npmPackages:
    @storybook/addon-essentials: ^8.0.0-beta.2 => 8.0.0-beta.2
    @storybook/addon-interactions: ^8.0.0-beta.2 => 8.0.0-beta.2
    @storybook/addon-links: ^8.0.0-beta.2 => 8.0.0-beta.2
    @storybook/addon-onboarding: ^1.0.11 => 1.0.11
    @storybook/blocks: ^8.0.0-beta.2 => 8.0.0-beta.2
    @storybook/preset-create-react-app: ^8.0.0-beta.2 => 8.0.0-beta.2
    @storybook/react: ^8.0.0-beta.2 => 8.0.0-beta.2
    @storybook/react-webpack5: ^8.0.0-beta.2 => 8.0.0-beta.2
    @storybook/test: ^8.0.0-beta.2 => 8.0.0-beta.2
    storybook: ^8.0.0-beta.2 => 8.0.0-beta.2
```


### Additional context

_No response_
Repository: neovim
Issue: Is it possible for a line-based treesitter `(#offset!)` directive.
Labels: enhancement,treesitter

### Problem

Currently, `#offset!` allows clipping the start and end of a node away. It's useful, but it doesn't allow capturing only the block comments' contents.

Example can be

```c
// Some C comments

/**
 * Some C block comments
 * Foo
 * Bar
 */
```

Right now, if I do `#offset!` on the block comment with capture `@node` and `(#offset! @node 0 3 0 -3)`, I will have a range of
```c
 * Some C block comments
 * Foo
 * Bar
```



### Expected behavior

I'd like to ask for a line-based `#offset!`, so that I can remove all the leading `*` inside such block comments, for example, `(#line-offset! 0 3 0 -3)`, and have the resulting capture to be 

```c
// /** is removed, empty line
Some C block comments // <- captured with @node, the leading ` * ` is not captured 
Foo                   // <- captured with @node, the leading ` * ` is not captured
Bar                   // <- captured with @node, the leading ` * ` is not captured
// <space>*/ is removed, empty line
```
Repository: godot
Issue: Android Shoulder key release does not trigger when using Xbox controller
Labels: bug,platform:android,needs testing,topic:input

### Tested versions

4.2.1

### System information

WIn 11

### Issue description

Android Shoulder key release does not trigger when using Xbox controller
I tested it with two different controllers, but both XBOX controllers.

### Steps to reproduce

One-click deploy Using the XBOX handle on Android, press RT or LT and RB or LB to test

### Minimal reproduction project (MRP)

[test.zip](https://github.com/godotengine/godot/files/14310249/test.zip)
Repository: transformers
Issue: Request for Flash Attention 2.0 Support in GPNRoFormerForMaskedLM
Labels: Feature request,Flash Attention

Hello,

I trust this message finds you well. I am currently attempting to run the GPN-MSA model, which utilizes AutoModelForMaskedLM, and I am keen on parallelizing the computation across multiple GPUs. To optimize the model's performance, I would like to request the integration of Flash Attention 2.0 support into GPNRoFormerForMaskedLM.

As I explore this avenue for parallelization, I envision that many others within the community could benefit from this enhancement.

Thank you for your time and consideration.

Best regards.
Repository: material-ui
Issue: [material-ui] Review M3 token naming format
Labels: on hold,package: material-ui,customization: theme,enhancement,design: material you

From https://github.com/mui/material-ui/issues/29345#issuecomment-1944438976:

>  The CSS tokens used don't appear to follow M3 guidelines fully. Like the tokens generated by https://material-foundation.github.io/material-theme-builder/ and https://github.com/material-foundation/material-color-utilities are completely kebab-cased (like --md-sys-color-on-primary) but @mui/material-next appear to have the last part camel-cased (like --md-sys-color-onPrimary).
Is this something overlooked or am I missing something? Just saying coz, it would be great if all the libraries using M3 followed it completely (like https://github.com/material-components/material-web) so that they could be drop-in replaced easily and not worry about matching themes.

We should review our current CSS variable naming format so it makes copying themes as easy as possible.

**Search keywords**:  M3 tokens
Repository: flutter
Issue: Add overflow & maxLines option to CupertinoTabBar 
Labels: c: new feature,framework,f: cupertino,c: proposal,P2,team-design,triaged-design

### Use case

In some cases it makes sense to overflow the text of the `BottomNavigationBarItem` with `TextOverflow.ellipsis` to avoid breaking ui appearance. 

It the title of the  `BottomNavigationBarItem` breaks into 2 lines, the icon gets smaller and the alignment within the other `BottomNavigationBarItem` breaks. 

### Proposal

The `CupertinoTabBar` should have 2 more parameters. `maxLines` and `overflow`. Though this 2 parameters the developer can decide by themself how the titles should behave
Repository: opencv
Issue: Biased result when calling HoughLines with even number of disretization steps for rho
Labels: bug,category: imgproc

### System Information

OpenCV python version: 4.6.0
Operating System / Platform: Debian GNU/Linux 12 (bookworm)
Python version: 3.11.2


### Detailed description

Calling HoughLines with parameters st. the number of discretization steps for rho https://github.com/opencv/opencv/blob/68f6c81539457fc5098ca53f5cc97ba03261d98f/modules/imgproc/src/hough.cpp#L146 is even will lead to a bias in the rho values of all detected lines. The behavior is likely produced by https://github.com/opencv/opencv/blob/68f6c81539457fc5098ca53f5cc97ba03261d98f/modules/imgproc/src/hough.cpp#L194 truncating the offset due to integer by integer division and then ignoring this truncation when decoding rho at https://github.com/opencv/opencv/blob/68f6c81539457fc5098ca53f5cc97ba03261d98f/modules/imgproc/src/hough.cpp#L217

Replacing the multiplication by 0.5f with a division by int(2) should fix the issue.

### Steps to reproduce

```
import cv2
import numpy as np

binary_img= np.zeros((3, 3), dtype=np.uint8)
binary_img[:, 1] = 255

print("Input Image:")
print(binary_img)

lines = cv2.HoughLines(binary_img, rho=0.5, theta=np.pi/4., threshold=2, min_theta=0, max_theta=np.pi)

print("\nDetected Lines:")
print(lines)
print("\nOne would expect rho=1.0 not rho=0.75.")
```
output
```
Input Image:
[[  0 255   0]
 [  0 255   0]
 [  0 255   0]]

Detected Lines:
[[[0.75 0.  ]]]

One would expect rho=1.0 not rho=0.75.
```




### Issue submission checklist

- [X] I report the issue, it's not a question
- [X] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [X] I updated to the latest OpenCV version and the issue is still there
- [X] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: flutter
Issue: When building a Flutter app, the `flutter` tool still generates an AssetManifest.json file that is unused by the framework
Labels: P3,c: tech-debt,team-tool,triaged-tool

Before https://github.com/flutter/flutter/pull/122505 landed, the tool would generate a file named AssetManifest.json which was bundled into the flutter app being built. This file contained information about assets. After #122505, a new file gets generated, AssetManifest.bin, which succeeded AssetManifest.json. However, the tool still produces AssetManifest.json since some customers depend on it to determine what assets are available to an app at runtime. While this was never a publicly documented feature, it was recommended as a workaround to some users. In current times, the [`AssetManifest`](https://api.flutter.dev/flutter/services/AssetManifest-class.html) provides a supported way to do this, and we want users to use that instead.

We should announce a deprecation/removal of the AssetManifest.json concept, and remove all references to it in code.
Repository: node
Issue: Ambiguous wording at loading order description
Labels: doc

### Affected URL(s)

https://nodejs.org/api/modules.html#all-together

### Description of the problem

The following part at the linked page:
![1](https://github.com/nodejs/node/assets/66683424/598f919d-e71e-4cb3-994f-ae20790ad50e)

Can mean 2 things:
1. Sets `Y` as the file system root, so at step 3 `Y` means the same location as `./` .
2. Sets the file system root as a value of `Y` .

The 2.a. should be replaced with 1 of:
* `` set `Y` to the file system root ``
* `` set the file system root as a value of `Y` ``
* other
Repository: vscode
Issue: Git - Unable to see buttons when list of conflicting tag(s) is too long.
Labels: bug,git

<!-- ⚠️⚠️ 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: Version: 1.87.0-insider (Universal)
Commit: d84c946d27b649d614319c796911871320befd42
Date: 2024-02-16T06:05:20.657Z
Electron: 27.3.2
ElectronBuildId: 26836302
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: 11.8.172.18-electron.0

- OS Version: Darwin arm64 23.3.0

Steps to Reproduce:

1. Perform "Pull" when the local repository will have tags conflict for many tags.
2. "Unable to pull from remote repository due to conflicting tag(s)" window with all tags list will be shown
3. When there are a lot of conflicting tags window will be extremely long and bottom buttons will be hidden down the screen without the possibility of clicking them (Issue part 1)
4. Press Esc to close this window.
5. The main VS Code window will be positioned almost completely under the bottom of the screen with the only top part of the window visible (Issue part 2)

This window should have a scroll for that long tags list or trim list to some appropriate length. 
Issue present in both current "stable" and "insiders" versions.

Screenshots are attached from the "Mission Control" view.

![Curren stable build](https://github.com/microsoft/vscode/assets/291713/3a4ddea6-c97e-49e9-a6cc-30b4ba8d52f1)

![Current insiders build](https://github.com/microsoft/vscode/assets/291713/d8c0bb2b-2f30-474d-9f46-64b9ea84cab6)

<img width="1728" alt="Window position" src="https://github.com/microsoft/vscode/assets/291713/20940af3-9802-4c37-a7c0-9b313dec54ec">