sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: DISABLED test_byte_mask_accumulate (__main__.TestAdvancedIndexing)
Labels: triaged,module: flaky-tests,module: macos,skipped

Platforms: mac, macos

This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/flakytest?name=test_byte_mask_accumulate&suite=TestAdvancedIndexing&limit=100) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/24818124271).

Over the past 3 hours, it has been determined flaky in 2 workflow(s) with 2 failures and 2 successes.

**Debugging instructions (after clicking on the recent samples link):**
DO NOT ASSUME THINGS ARE OKAY IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
3. Grep for `test_byte_mask_accumulate`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.



<details><summary>Sample error message</summary>

```
Traceback (most recent call last):
  File "/Users/ec2-user/runner/_work/pytorch/pytorch/test/test_mps.py", line 10856, in test_byte_mask_accumulate
    self.assertEqual(len(w), 2)
  File "/Users/ec2-user/runner/_work/_temp/conda_environment_9029383781/lib/python3.9/site-packages/torch/testing/_internal/common_utils.py", line 3646, in assertEqual
    raise error_metas.pop()[0].to_error(
AssertionError: Scalars are not equal!

Expected 2 but got 3.
Absolute difference: 1
Relative difference: 0.5

To execute this test, run the following from the base repo dir:
     python test/test_mps.py -k TestAdvancedIndexing.test_byte_mask_accumulate

This message can be suppressed by setting PYTORCH_PRINT_REPRO_ON_FAILURE=0
```

</details>


Test file path: `test_mps.py`

ResponseTimeoutError: Response timeout for 5000ms, GET https://raw.githubusercontent.com/pytorch/pytorch/main/test/test_mps.py 200 (connected: true, keepalive socket: false, socketHandledRequests: 1, socketHandledResponses: 1)
headers: {"connection":"keep-alive","content-length":"518659","cache-control":"max-age=300","content-security-policy":"default-src 'none'; style-src 'unsafe-inline'; sandbox","content-type":"text/plain; charset=utf-8","etag":"\"3b3da62a27aeb5094cbc77af203069a957757aa1be9e108c1cf3253b2102adfb\"","strict-transport-security":"max-age=31536000","x-content-type-options":"nosniff","x-frame-options":"deny","x-xss-protection":"1; mode=block","x-github-request-id":"33E6:10BA36:2ECDDBB:31615F5:663E3FB3","accept-ranges":"bytes","date":"Fri, 10 May 2024 15:39:33 GMT","via":"1.1 varnish","x-served-by":"cache-sjc1000107-SJC","x-cache":"MISS","x-cache-hits":"0","x-timer":"S1715355574.538166,VS0,VE182","vary":"Authorization,Accept-Encoding,Origin","access-control-allow-origin":"*","cross-origin-resource-policy":"cross-origin","x-fastly-request-id":"c8e9dc7441418d14bb99e367fdf092022dd9303e","expires":"Fri, 10 May 2024 15:44:33 GMT","source-age":"0"}

cc @clee2000 @malfet @albanD
Repository: storybook
Issue: [Bug]: Stories are not overwriting {control: false} from meta (argTypes)
Labels: bug,good first issue,help wanted,addon: controls,sev:S3

### Describe the bug

I want to have an argument disabled in most of the stories for a component, but I cannot overwrite the value on meta definition in specific stories.


### To Reproduce

Set in meta definition: argTypes{ whatever: {control: false} }; and then try to set argTypes{ whatever: {control: "string"} } inside a story. The control for that arg will remain disabled ("-"). 

Nonetheless, if you go from control:"string" in meta definition to control: "object" in story, it will overwrite it correctly.



### System

```bash
System:
    OS: Windows 10 10.0.19045
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz
  Binaries:
    Node: 20.11.1 - C:\Program Files\nodejs\node.EXE
    npm: 10.5.2 - ~\Documents\GitHub\design-system\node_modules\.bin\npm.CMD <----- active
  Browsers:
  npmPackages:
    @storybook/addon-a11y: ^8.0.10 => 8.0.10
    @storybook/addon-essentials: ^8.0.10 => 8.0.10
    @storybook/addon-interactions: ^8.0.10 => 8.0.10
    @storybook/addon-themes: ^8.0.10 => 8.0.10
    @storybook/blocks: ^8.0.0-rc.1 => 8.0.10
    @storybook/preview-api: 8.0.10 => 8.0.10
    @storybook/react: ^8.0.10 => 8.0.10
    @storybook/react-vite: ^8.0.10 => 8.0.10
    @storybook/theming: ^8.0.10 => 8.0.10
    chromatic: 11.3.0 => 11.3.0
    eslint-plugin-storybook: 0.8.0 => 0.8.0
    storybook: ^8.0.10 => 8.0.10
```


### Additional context

_No response_
Repository: neovim
Issue: `E490: no fold found` with tree-sitter
Labels: bug,treesitter,folds

### Problem

Tree-sitter computed folds don't work on files opened through commands. This breaks session restore functionality.

Related:

* #25948
* [nvim-treesitter #1337](https://github.com/nvim-treesitter/nvim-treesitter/issues/1337)
* [nvim-telescope #699](https://github.com/nvim-telescope/telescope.nvim/issues/699)
* [auto-session #109](rmagatti/auto-session/issues/109)
* [possession.nvim #19](https://github.com/jedrzejboczar/possession.nvim/issues/19)

### Steps to reproduce

**minimal.lua**:
```lua
for name, url in pairs {
  ts = "https://github.com/nvim-treesitter/nvim-treesitter/",
} do
  local install_path = vim.fn.fnamemodify('nvim_issue/' .. name, ':p')
  if vim.fn.isdirectory(install_path) == 0 then
    vim.fn.system { 'git', 'clone', '--depth=1', url, install_path }
  end
  vim.opt.runtimepath:append(install_path)
end

require("nvim-treesitter.configs").setup({
  ensure_installed = { "c" }
})

vim.opt.foldmethod = "expr"
vim.wo.foldexpr = "v:lua.vim.treesitter.foldexpr()"
vim.opt.foldlevelstart = 99

vim.cmd("e hello-world.c")
vim.cmd("setf c")
```
**helloworld.c**:
```c
#include <stdio.h>

int main() {
    printf("Hello, world!");
    return 0;
}
```

**Steps**:

* `nvim --clean -u minimal.lua`
* Press `za` on foldable section
* message: `E490: no fold found`

Entering insert mode or pressing `zx` seems to restore fold functionality. Not working without these actions breaks a complete session restore.

### Expected behavior

Folds should always work, including those restored via sessions.

### Neovim version (nvim -v)

NVIM v0.10.0-dev-3103+gca735c755

### Vim (not Nvim) behaves the same?

not applicable

### Operating system/version

Arch Linux x86_64

### Terminal name/version

Alacritty 0.13.2-2

### $TERM environment variable

alacritty

### Installation

GitHub nightly tarball
Repository: node
Issue: node-api: include experimental feature flags in add-on version reported at runtime
Labels: feature request,node-api

This only applies to features that change the behaviour of existing APIs.

We currently have two flags for each experimental behaviour-changing API:
1. A feature flag indicating that it is available within the `NAPI_EXPERIMENTAL` portion of the API.
2. An opt-out flag indicating that, although the add-on chose to use `NAPI_EXPERIMENTAL` it does not wish to use this particular feature of the experimental bundle.

In order to avoid going down the experimental code path when running an add-on that chose to opt out of an experimental feature, we need to encode that choice in the version reported to the add-on loader.

If `NAPI_EXPERIMENTAL` is defined, all experimental features are turned on, unless, for any given feature, its opt-out flag is given.

We can include experimental flags in the version number reported at runtime as follows:

<table>
<tr>
<td colspan="4">highest 16 bits</td>
<td>lowest 16 bits</td>
</tr>
<tr>
<td>feature 1</td>
<td>feature 2</td>
<td>...</td>
<td>feature 16</td>
<td>NAPI_VERSION (latest released, i.e. 8, 9, 10, etc.)</td>
</tr>
<tr>
<th colspan="5">or</th>
</tr>
<tr>
<td colspan="5">NAPI_VERSION_EXPERIMENTAL (2147483647) All experimental features are requested</td>
</tr>
</table>

This value ends up on `napi_env`. At runtime we can check against the bits of this value to decide on the code path. We should probably create a family of macros for making decisions based on the feature flags.

At our Node-API meeting we concluded that we should introduce behaviour-changing features extremely sparingly, because, in order to ensure we do not break our users, even those that have opted into `NAPI_EXPERIMENTAL`, the testing complexity doubles with each feature we introduce.
Repository: material-ui
Issue: Screen reader doesn't announce Dialog description but it announces Modal description
Labels: accessibility,component: dialog,package: material-ui

### Steps to reproduce

Link to live example: 
- [Modal example at StackBlitz](https://stackblitz.com/edit/react-f1nsx7?file=Demo.tsx)
- [Dialog example at StackBlitz](https://stackblitz.com/edit/react-yegnub?file=Demo.tsx)

Steps:
1. Create a button and a Dialog / Modal
2. Add `aria-labelledby` and `aria-describedby` props
3. Open VoiceOver (another screen reader might work as well)
4. Click the button


### Current behavior

Screen reader announces both title and description of Modal.
Screen reader announces only title of Dialog.

### Expected behavior

Screen reader should announce both title and description of Dialog.

### Context

I am trying to make VoiceOver announce both the title referenced by `aria-labelledby` and the description referenced by `aria-describedby`. Because dialogs are good for alerting results, changes, or alerts. I am expecting a screen reader to announce dialog content.

### Your environment

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
 System:
    OS: macOS 14.4.1
  Binaries:
    Node: 18.16.1 - ~/.nvm/versions/node/v18.16.1/bin/node
    npm: 9.5.1 - ~/.nvm/versions/node/v18.16.1/bin/npm
    pnpm: Not Found
  Browsers:
    Chrome: 124.0.6367.156
    Edge: 124.0.2478.80
    Safari: 17.4.1
  npmPackages:
    @emotion/react: 11.11.4 => 11.11.4
    @emotion/styled: 11.11.5 => 11.11.5
    @mui/base:  5.0.0-beta.40
    @mui/core-downloads-tracker:  5.15.17
    @mui/material: 5.15.17 => 5.15.17
    @mui/private-theming:  5.15.14
    @mui/styled-engine:  5.15.14
    @mui/system:  5.15.15
    @mui/types:  7.2.14
    @mui/utils:  5.15.14
    @types/react: 18.3.1 => 18.3.1
    react: 18.3.1 => 18.3.1
    react-dom: 18.3.1 => 18.3.1
    typescript: 5.4.5 => 5.4.5
```
</details>


**Search keywords**: VoiceOver, Screen Reader, aria-describedby, Dialog, Modal
Repository: flutter
Issue: Improve Flutter's Android device orientation performance
Labels: platform-android,a: layout,P2,design doc,team-android,triaged-android,:scroll:

### Document Link

https://flutter.dev/go/performance-android-orientation-changes

### What problem are you solving?

Proposal to improve Flutter’s Android device rotation performance.
Repository: vscode
Issue: Can't see blinking cursor when it's moved before a closing character like ) or }
Labels: bug,editor-rendering

<!-- ⚠️⚠️ 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?: No (but)

* but: I see the blinking cursor because the box around the matching ( and ) have a dimmer color, but I can see the cursor overlaps the left side of the box, that overlapping in some themes lead to an invisible cursor if the box is not dim enough.

![Screenshot_2024-05-10_14-15-22](https://github.com/microsoft/vscode/assets/1278556/8ae6794e-2252-4da5-a1fe-019b21f96abd)

See the left side of the box is brighter? that's the cursor, that overlaps exactly with the left side of the box around the closing )

<!-- 🪓 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.89.0 (it happened with previous versions too)
- OS Version: Linux Mint 21

Steps to Reproduce:

The blinking cursor is at the end and I can see it blinks, one pixel to the right of the box that appears for the matching ( and ).

![Screenshot_2024-05-10_14-02-31](https://github.com/microsoft/vscode/assets/1278556/699c1856-f7ef-49ba-aebc-af347b94ecba)

Then I move the cursor one character to the left, and I don't see it blinking, basically I lost where the cursor is, then need to grab the mouse to point, which is a waste of time.

![Screenshot_2024-05-10_14-02-48](https://github.com/microsoft/vscode/assets/1278556/fb93f0fd-9cd4-4f61-9128-14fa58ef95d5)

It would be better to show the blinking cursor on top of everything else, even those boxes for the matching opening and closing characters, and use a different color too.
Repository: flutter
Issue: [camera_android_camerax] Ensure `startVideoCapturing` and `stopVideoRecording` return video with expected duration
Labels: platform-android,p: camera,package,P2,team-android,triaged-android

https://github.com/flutter/packages/pull/6697 makes an attempt to listen to CameraX [`VideoRecordEvent`](https://developer.android.com/reference/androidx/camera/video/VideoRecordEvent)s to ensure that `startVideoCapturing` and `stopVideoRecording` only return when the video recording process has actually started/stopped the video recording process, respectively. However, when testing this by recording a video for 2s, we found consistently that the duration of the video is shorter by a couple hundred of ms (1500/1400ms vs 2000ms), indicating that the process of starting/stopping video recording eats into the expected recording time.

We should identify whether the cause is within the CameraX library, the delay between Java/Dart communication, etc. and find a fix for this issue.

**Note:** Via testing, we found that `camera_android` has a similar delay, but it is slightly less (1800ms-ish vs 2000ms).
Repository: pytorch
Issue: [NestedTensor] multiply batch and ragged dimension to get shape of values tensor
Labels: triaged,module: nestedtensor

### 🚀 The feature, motivation and pitch

From @albanD:
> I would argue that it would be so cool to be able to do something like:

```
# Assume I want a new Tensor with the first two dimensions collapsed
nested_size = my_nested_tensor.size()
nested_size[1] = nested_size[0] * nested_size[1]
nested_size.pop(0)
my_new_nested_tensor = torch.zeros(nested_size)
```

https://github.com/pytorch/pytorch/pull/124687#discussion_r1596098648



### Alternatives

I think this is just the same as `nt.values()`.

### Additional context

_No response_

cc @cpuhrsch @jbschlosser @bhosmer @drisspg @soulitzer
Repository: go
Issue: github.com/googleapis/gax-go/v2/apierror: unrecognized failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "github.com/googleapis/gax-go/v2/apierror" && test == ""
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/a832e48c6259c701e1879edeaf6edd38b3ce2d2a)):

    SIGSEGV: segmentation violation
    PC=0x80cd278 m=1 sigcode=1 addr=0x81f22bb0
    
    goroutine 0 gp=0x29806488 m=1 mp=0x29848008 [idle]:
    runtime.fallback_nanotime()
    	runtime/sys_freebsd_386.s:251 +0x18 fp=0x2982df58 sp=0x2982df34 pc=0x80cd278
    runtime.nanotime1()
    	runtime/vdso_freebsd.go:103 +0x40 fp=0x2982df6c sp=0x2982df58 pc=0x80c33a0
    runtime.nanotime(...)
    	runtime/time_nofake.go:19
    ...
    edx    0x1
    edi    0x8057f80
    esi    0x1
    ebp    0xffffffff
    esp    0x2982df34
    eip    0x80cd278
    eflags 0x10202
    cs     0x33
    fs     0x13
    gs     0x8f


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: go/types: NewSignatureType mutates its TypeParams, and panics unless they are new
Labels: NeedsInvestigation

If a client of go/types uses NewSignatureType to create a variation on an existing type, it is an error to pass the TypeParams of the existing function, as bindTParams will update their index field, and panic if the field has already been set. 

I think there are two separate issues here:
1. NewSignatureType mutates its operands. It's not at all obvious that it does this; if this is unavoidable, it should be documented.
2. If the same type parameters are re-used, their indices will be the same. In that case, bindTParams should probably just skip the update since it is unnecessary, rather than panic unnecessarily.

Offending client code:
```go
		// Emit signature.
		//
		// Elide parameters after the third one.
		// WriteSignature is too complex to fork, so we replace
		// parameters 4+ with "invalid type", format,
		// then post-process the string.
		if sig.Params().Len() > 3 {
			sig = types.NewSignatureType(
				sig.Recv(),
				typesSeqToSlice[*types.TypeParam](sig.RecvTypeParams()),
				typesSeqToSlice[*types.TypeParam](sig.TypeParams()),
				types.NewTuple(append(
					typesSeqToSlice[*types.Var](sig.Params())[:3],
					types.NewVar(0, nil, "", types.Typ[types.Invalid]))...),
				sig.Results(),
				false) // any final ...T parameter is truncated
		}
		types.WriteSignature(&buf, sig, pkgRelative)
```

(Gopls uses NewSignatureType to truncate long parameter lists so that they can be formatted using TypeString or WriteSignature. If the machinery of TypeString provided more control over the traversal this would not be necessary.)

@gri @findleyr
Repository: opencv
Issue: Om object track
Labels: question (invalid tracker)

import cv2
import numpy as np

# Replace 'path_to_video' with the path to your video file
cap = cv2.VideoCapture('https://github.com/opencv/opencv/assets/169485743/5cf5d70b-cf55-449d-9c4c-02252d81cf98

')

# Set up the parameters for ShiTomasi corner detection
feature_params = dict(maxCorners=100, qualityLevel=0.3, minDistance=7, blockSize=7)

# Parameters for lucas kanade optical flow
lk_params = dict(winSize=(15, 15), maxLevel=2, criteria=(cv2.TERM_CRITERIA_EPS | cv2.TERM_CRITERIA_COUNT, 10, 0.03))

# Take the first frame and find corners in it
ret, old_frame = cap.read()
old_gray = cv2.cvtColor(old_frame, cv2.COLOR_BGR2GRAY)
p0 = cv2.goodFeaturesToTrack(old_gray, mask=None, **feature_params)

# Create a random color to draw tracks
color = np.random.randint(0, 255, (100, 3))

while True:
    # Read the new frame
    ret, frame = cap.read()
    if not ret:
        break

    frame_gray = cv2.cvtColor(frame, cv2.COLOR_BGR2GRAY)

    # Calculate optical flow
    p1, st, err = cv2.calcOpticalFlowPyrLK(old_gray, frame_gray, p0, None, **lk_params)

    # Select good points
    good_new = p1[st == 1]
    good_old = p0[st == 1]

    # Draw the tracks
    for i, (new, old) in enumerate(zip(good_new, good_old)):
        a, b = new.ravel()
        c, d = old.ravel()
        frame = cv2.line(frame, (a, b), (c, d), color[i].tolist(), 2)
        frame = cv2.circle(frame, (a, b), 5, color[i].tolist(), -1)

    # Display the result
    cv2.imshow('Frame', frame)

    # Update the previous frame and previous points
    old_gray = frame_gray.copy()
    p0 = good_new.reshape(-1, 1, 2)

    if cv2.waitKey(1) & 0xFF == ord('q'):
        break

# Release the capture and close any open windows
cap.release()
cv2.destroyAllWindows()
Repository: flutter
Issue: [two_dimensional_scrollables] childPositionGetter in Tableview.builder
Labels: c: new feature,framework,f: scrolling,package,c: proposal,P3,team-framework,triaged-framework,p: two_dimensional_scrollables

### Use case



https://github.com/flutter/flutter/assets/61263149/007739ee-6f64-4d5e-842b-f50b55b5a577


In the video, I demonstrated the need to make the spot price stick to both the top and bottom. Achieving this requires knowing the element's position in the viewport or having a built-in feature that allows elements to stick to the top or bottom.

I forked the package and included additional code to determine the element's position. However, integrating such functionality directly into the package would greatly facilitate the creation of complex UIs, making the development process more efficient and user-friendly.

### Proposal


```
void _getChildPosition({
    required double rowOffset,
    required double standardRowHeight,
  }) {
    if (childPositionGetter == null) {
      return;
    }

    
    final double offset = rowOffset;

    final double percent;
    if ((viewportDimension.height / 2) > offset) {
      percent = offset / viewportDimension.height;
    } else {
      final bool isAtBottom = offset + standardRowHeight >= viewportDimension.height;
      percent = isAtBottom ? 1.0 : (rowOffset + standardRowHeight) / viewportDimension.height;
    }

    childPositionGetter?.call(TableVicinity(column: 0, row: childIndex!), percent);
  }

```

if we can have something similar in `RenderTableViewport` class in `_layoutCells` we can easily get the child position
Repository: ollama
Issue: NikolayKozloff/Meta-Llama-3-8B-Instruct-bf16-correct-pre-tokenizer-and-EOS-token-Q8_0-GGUF
Labels: model request

please add [Meta-Llama-3-8B-Instruct-bf16-correct-pre-tokenizer-and-EOS-token-Q8_0-GGUF](https://huggingface.co/NikolayKozloff/Meta-Llama-3-8B-Instruct-bf16-correct-pre-tokenizer-and-EOS-token-Q8_0-GGUF)


converted to GGUF without changing tensor data type. Moreover, the new correct pre-tokenizer llama-bpe is used ([ref](https://github.com/ggerganov/llama.cpp/pull/6745#issuecomment-2094991999)) and the EOS token is correctly set