sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: build: build failure on x_tools-go1.23-openbsd-riscv64
Labels: NeedsInvestigation

```
#!watchflakes
default <- builder == "x_tools-go1.23-openbsd-riscv64" && repo == "tools" && mode == "build"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8744223965864345841)):

    [I2024-06-25T07:03:33.039778+10:00 20708 0 sink.go:276] SinkServer: warm-up started
    [I2024-06-25T07:03:33.040735+10:00 20708 0 sink.go:346] SinkServer: starting HTTP server...
    [I2024-06-25T07:03:33.051422+10:00 20708 0 sink.go:281] SinkServer: warm-up ended
    [I2024-06-25T07:03:33.053360+10:00 20708 0 cmd_stream.go:487] rdb-stream: starting the test command - ["/home/swarming/.swarming/w/ir/cache/tools/bin/result_adapter" "go" "-v=false" "-dump-json" "/home/swarming/.swarming/w/ir/x/w/go.testjson" "--" "/home/swarming/.swarming/w/ir/x/w/goroot/bin/go" "test" "-json" "-short" "-timeout=40m0s" "./..."]
    [I2024-06-25T07:54:21.998856+10:00 20708 0 cmd_stream.go:483] rdb-stream: the test process terminated
    [I2024-06-25T07:54:22.000778+10:00 20708 0 sink.go:371] SinkServer: shutdown started
    [I2024-06-25T07:54:22.001410+10:00 20708 0 sink.go:349] SinkServer: HTTP server stopped with "http: Server closed"
    [I2024-06-25T07:54:22.001840+10:00 20708 0 sink_server.go:96] SinkServer: draining TestResult channel started
    [I2024-06-25T07:54:22.002219+10:00 20708 0 sink_server.go:98] SinkServer: draining TestResult channel ended
    [I2024-06-25T07:54:22.002367+10:00 20708 0 sink_server.go:100] SinkServer: draining Artifact channel started
    [I2024-06-25T07:54:22.003202+10:00 20708 0 sink_server.go:102] SinkServer: draining Artifact channel ended
    [I2024-06-25T07:54:22.003672+10:00 20708 0 sink.go:374] SinkServer: shutdown completed successfully
    [I2024-06-25T07:54:22.003974+10:00 20708 0 cmd_stream.go:415] rdb-stream: exiting with -1


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: create-react-app
Issue: Frontend Host doesn't match the current host in the browser, so it's probably incorrect. Links in emails and file downloads from the API will not work. Click here to update.
Labels: needs triage,issue: bug report

Frontend Host doesn't match the current host in the browser, so it's probably incorrect. Links in emails and file downloads from the API will not work. Click here to update.         why?
Repository: ollama
Issue: Groq's "name" option within "messages" parameter of the chat endpoint payload
Labels: feature request,api

Groq has a really helpful option within the "messages" parameter that one would provide in the payload to their chat completion API that helps the model distinguish between multiple users of the same role.  This is helpful for situations in which a multi-agent conversation is taking place and there is more than one agent in a given role--for example, a roleplay in which we want to differentiate between an assistant representing one personality with its own system prompt talking to another assistant representing another agent with its own system prompt, all chatting with the user role.

For more on this, please see the following link to the Groq docs https://console.groq.com/docs/text-chat under the "messages" parameter.
Repository: neovim
Issue: Unexpected active treesitter parser (vim.treesitter.stop() doesn't detach parser)
Labels: bug,treesitter

### Problem

I've created a issue in nvin-treesitter about this bug. According to this response, reproduced the error.

I think this is an issue with neovim core, stemming from the fact that a buffer is given the treesitter foldexpr, then the filetype changes (to one without a parser, i.e. no fold queries), then buffer content changes (now there is no way to properly calculate folds, because no parser/fold queries); hence an error

_Originally posted by @ribru17 in https://github.com/nvim-treesitter/nvim-treesitter/issues/6822#issuecomment-2196072409_

### Steps to reproduce

1. Visit a file, say some test.cpp with treesitter actived
2. On command line, exec `set ft=xxd`
3. On command line, exec `%!xxd`, there would be an error msg like "no parser for 'xxd' language"

### Expected behavior

No treesitter parser actived by this situation

### Neovim version (nvim -v)

0.10.0

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

no

### Operating system/version

ubuntu 22.04

### Terminal name/version

xterm

### $TERM environment variable

xterm-256

### Installation

appimage
Repository: tauri
Issue: [feat] automatically create tasks.json 
Labels: type: feature request

### Describe the problem

there are issues due to wrong commands like `tauri dev --release` instead of `tauri build`
or `cargo tauri run` instead of `npm tauri run` or whatever else could be

### Describe the solution you'd like

create `tasks.json`
you already create `.vscode/extensions.json` automatically
and you already print the commands when creating a project
*and* you also have docs that asks to create [tasks](https://tauri.app/v1/guides/debugging/vs-code/)

why not instead... just... do it... automatically.... all at once, in 1 file, no docs needed

### Alternatives considered

_No response_

### Additional context

this would fix many ***many*** issues I've had in the past and would have saved me countless time I never could get back
Repository: godot
Issue: Callable argument conversion error: Cannot convert argument 1 from int to int.
Labels: discussion,topic:core,documentation,needs testing

### Tested versions

- Reproducible in Godot 4.2.2 stable

### System information

Arch Linux - AMD 5800X3D - Forward+

### Issue description

Callable with bound arguments cannot be called with call() or with provided parameters after unbind. I expected this to work but I get argument conversion errors, in the first case about a callable to int and in the second about int to int.

In my project I would get the error about a PackedInt32Array, I tried to reproduce it in the bug report project but this fails on the int argument so it seems unrelated to argument type.

### Steps to reproduce

1. Start the project to test the unbind and call with arguments method.
2. Uncheck useUnbind to test call method with bound arguments. Neither works in this project

### Minimal reproduction project (MRP)

[test-callable.zip](https://github.com/user-attachments/files/16026340/test-callable.zip)
Repository: terminal
Issue: [Terminal Canary] The language setting doesn't match with the OS
Labels: Issue-Bug,Needs-Attention,Product-Terminal,Needs-Tag-Fix,Priority-2,Area-i18n

### Windows Terminal version

1.22.1781.0

### Windows build number

10.0.26241.5000

### Other Software

_No response_

### Steps to reproduce

1. I changed the language setting from English to French.
2. The entire OS changed to French after I signed out.
3. I opened Terminal Canary and it's still in English.

![image](https://github.com/microsoft/terminal/assets/89489853/b248d5be-4b3d-4e16-a009-4fa85a0055ad)


### Expected Behavior

I'm expecting the language in Terminal to match with the OS since it should follow the system default

### Actual Behavior

Even tho Terminal's setting language uses the "system default", it remains the same previous language.
Repository: storybook
Issue: [Bug]: Infinite Loading State When Using Dynamic Import Between Storybook Files
Labels: bug,needs triage

### Describe the bug

In my project, I are using two different configurations of Storybook. One configuration uses the `[name].stories.tsx` file, while the other uses `[name].test.stories.tsx`. I encountered an issue when trying to dynamically import stories from `[name].stories.tsx` into `[name].test.stories.tsx`. While everything works fine during development, the build process results in an infinite loading state for the pages where this dynamic import is used.

![When I open my Storybook, it shows a loading state](https://github.com/storybookjs/storybook/assets/11547305/81f86a44-4552-4e63-ae6c-7ca443ed62d6)


### Reproduction link

https://github.com/yuheiy/storybook-issue-infinite-loading-state-when-using-dynamic-import-between-storybook-files

### Reproduction steps

1. Set up a project with two Storybook configurations:
   - One using `[name].stories.tsx` file.
   - Another using `[name].test.stories.tsx` file.
2. Use dynamic import in the `[name].test.stories.tsx` to load stories from `[name].stories.tsx`.

`Button.stories.ts`:

```tsx
import type { Meta, StoryObj } from '@storybook/react';
import { Button } from './Button';

const meta = {
  title: 'Button',
  component: Button,
} satisfies Meta<typeof Button>;

export default meta;
type Story = StoryObj<typeof meta>;

export const Primary: Story = {
  args: {
    primary: true,
    label: 'Button',
  },
};
```

`Button.test.stories.ts`:

```tsx
import type { Meta, StoryObj } from '@storybook/react';
import { Button } from './Button';

const meta = {
  title: 'Button',
  component: Button,
} satisfies Meta<typeof Button>;

export default meta;
type Story = StoryObj<typeof meta>;

export const Primary: Story = {
  ...(await import('./Button.stories')).Primary,
};
```


### System

```bash
Storybook Environment Info:

  System:
    OS: macOS 14.5
    CPU: (10) arm64 Apple M1 Max
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.13.1 - ~/.nvm/versions/node/v20.13.1/bin/node
    npm: 10.5.2 - ~/.nvm/versions/node/v20.13.1/bin/npm <----- active
  Browsers:
    Chrome: 126.0.6478.127
    Safari: 17.5
  npmPackages:
    @storybook/react: ^8.1.11 => 8.1.11 
    @storybook/react-vite: ^8.1.11 => 8.1.11 
    storybook: ^8.1.11 => 8.1.11
```


### Additional context

- The issue occurs only when using dynamic import. Static imports do not cause this issue.
- The problem arises specifically when importing story files associated with a different Storybook configuration. For example, importing from `[name].stories.tsx` to `[name].stories.tsx` or from `[name].test.stories.tsx` to `[name].test.stories.tsx` does not cause any issues.
- The issue is not present during development but only appears after the build process.
Repository: transformers
Issue: Any config for DeBERTa series as decoders for TSDAE? 
Labels: Feature request

### Feature request

Seems that there is no config for DeBERTa v1-2-3 as decoder (while there are configs for BERT/RoBERTa et similia models)... This is needed in order to perform TSDAE unsupervised fine tuning.

*(TSDAE: Using Transformer-based Sequential Denoising Auto-Encoder for Unsupervised Sentence Embedding Learning)*

### Motivation

Here a reference for the related sentence transformer issue: https://github.com/UKPLab/sentence-transformers/issues/2771

TSDAE demonstrated to be a powerful unsupervised approach, and DeBERTa is proven to be a really strong base model for further fine tuning (also, v2 has a an xxlarge 1.5B version and v3 demonstrated strong performance and efficiency with its ELECTRA-style pretraining)

For context, here the TSDAE paper: https://arxiv.org/abs/2104.06979

### Your contribution

I'm not sure if I can contribute to the repository... 

Anyway, i can certainly open source multiple domain adapted models, including models in a size range (1.5B) where there is not much choices while working with encoder-only models

Edited
Repository: ollama
Issue: allow for num_ctx parameter in the openai API compatibility
Labels: feature request

The OpenAI compatibility module does not allow for setting the number of tokens window (num_ctx) via API call dynamically instead of having to adjust the Modelfile each time we want to use another context window.

Therefore it would be great to have in the OpenAI compatibility. I can also try a PR for this.

Thanks a lot for this wonderful project! :-)
Repository: go
Issue: x/tools/internal/refactor/inline: support inlining functions with type parameters
Labels: NeedsFix,FeatureRequest,gopls,Tools,Refactoring

Functions with type parameters [cannot be inlined](https://cs.opensource.google/go/x/tools/+/master:internal/refactor/inline/callee.go;l=122;drc=bcec0994e0bf81991b2e35f788768c9074a20152) at the moment. 

This is a feature request to make it possible to inline functions with type parameters.
Repository: PowerToys
Issue: Margins for Fancy Zones set to 0. After hibernate margins appear on windows.
Labels: Issue-Bug,FancyZones-Settings,Product-FancyZones,Area-Quality,Priority-1

### Microsoft PowerToys version

0.81.1

### Installation method

PowerToys auto-update

### Running as admin

None

### Area(s) with issue?

FancyZones

### Steps to reproduce

This issue goes back years. Multi monitor setup. Set fancy zones with zero margin. Hibernate computer, when it wakes all your windows now have a margin around them and need resnapping.

### ✔️ Expected Behavior

That no margin would remain as intended. There's no reason to suddenly add a margin after hibernate.

### ❌ Actual Behavior

Margins were added.

### Other Software

_No response_
Repository: material-ui
Issue: Autocomplete with groups throws accessibility scanner issues
Labels: accessibility,component: autocomplete

### Steps to reproduce

[Link to live example](https://mui.com/material-ui/react-autocomplete/#grouped)

Steps:
1. Create an autocomplete component with grouping enabled, same as the [official example](https://mui.com/material-ui/react-autocomplete/#grouped).
```tsx
    <Autocomplete
      id="grouped-demo"
      options={options.sort((a, b) => -b.firstLetter.localeCompare(a.firstLetter))}
      groupBy={(option) => option.firstLetter}
      getOptionLabel={(option) => option.title}
      sx={{ width: 300 }}
      renderInput={(params) => <TextField {...params} label="With categories" />}
    />
```
3. Open the dropdown and scan with an accessibility tool like [axe DevTools](https://www.deque.com/)
Note: you may need to force the autocomplete to stay open while you scan with `open={true}`


### Current behavior

I get a bunch of errors around incorrect aria roles:

![image](https://github.com/mui/material-ui/assets/93141585/2c3c9fc9-5e4b-4603-a03c-43e89d4dd7ef)

This is because `<li />` are not allowed as children of `listbox`.

The current role structure is:

```
listbox
  generic <--- the group label
  list
    option
    option
    ...
  generic
  list
    option
    ...
```

### Expected behavior

No accessibility errors.

To achieve this, you should follow the [ARIA APG Listbox pattern](https://www.w3.org/WAI/ARIA/apg/patterns/listbox/examples/listbox-grouped/) which forms this role structure:

```
listbox
  group
    presentation <--- the group label
    option
    option
    ...
  group
    presentation
    option
    ...
```

This can be achieved in html like this

```html
<div role="listbox">
   <ul role="group">
     <li role="presentation">
       Group 1
     </li>
     <li role="option">
        Option 1
     </li>
     ...
   </ul>
   <ul role="group">
     <li role="presentation">
       Group 2
     </li>
     <li role="option">
       Option 1
     </li>
     ...
   </ul>
</div>
```

In my case, I achieved this in the Autocomplete component with fully custom rendering (`renderOption`, `renderGroup`), but I wouldn't expect most users to do this.

### Context

I was trying to create a grouped autocomplete list.

My company is a paying customer, our support key / order number is `65425`


### Your environment

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  System:
    OS: Windows 11 10.0.22631
  Binaries:
    Node: 21.5.0 - C:\Program Files\nodejs\node.EXE
    npm: 10.2.4 - C:\Program Files\nodejs\npm.CMD
    pnpm: Not Found
  Browsers:
    Chrome: Not Found
    Edge: Chromium (126.0.2592.68)

```
</details>


**Search keywords**: autocomplete accessibility roles
Repository: vscode
Issue: Have to click "stop" action multiple times
Labels: bug,debug

I feel like I mostly see this when debugging an extension. This doesn't happen every time.

1. Start debugging an extension (I'm usually using https://github.com/microsoft/vscode-pull-request-github)
2. Make a change to the extension code (this step may not be needed)
3. From the ext dev host window, run the Developer: Reload Window command
4. Repeat steps 2 and 3 at least once more
5. In your debugger window, click the "stop" action in the debug toolbar
6. It sometimes takes multiple clicks to actually stop the debugger

// cc @hediet since you've also seen this.
Repository: go
Issue: net: Dial does not respond to quickly-broken IPv6 connections by falling back to IPv4
Labels: NeedsInvestigation

### Go version

go version go1.22.4 darwin/arm64

### Output of `go env` in your module/workspace:

```shell
GO111MODULE=''
GOARCH='arm64'
GOBIN=''
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='arm64'
GOHOSTOS='darwin'
GOINSECURE=''
GOOS='darwin'
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/opt/homebrew/Cellar/go/1.22.4/libexec'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/opt/homebrew/Cellar/go/1.22.4/libexec/pkg/tool/darwin_arm64'
GOVCS=''
GOVERSION='go1.22.4'
GCCGO='gccgo'
AR='ar'
CC='cc'
CXX='c++'
CGO_ENABLED='1'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -arch arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -ffile-prefix-map=/var/folders/q9/qcgtwgsj0y72gr01_djqgmyw0000gq/T/go-build1826860007=/tmp/go-build -gno-record-gcc-switches -fno-common'
```


### What did you do?

Trying to fetch a random module (all break the same):

> % go get nhooyr.io/websocket
go package net: confVal.netCgo = false  netGo = false
go package net: using cgo DNS resolver
go package net: hostLookupOrder(proxy.golang.org) = cgo
go: module nhooyr.io/websocket: Get "https://proxy.golang.org/nhooyr.io/websocket/@v/list": write tcp [fe80::bed0:74ff:fe64:598e%utun4]:56330->[2a00:1450:4003:80c::2011]:443: write: socket is not connected

Machine has IPv6 disabled:
> % dig proxy.golang.org
; <<>> DiG 9.10.6 <<>> proxy.golang.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53713
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

> ;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4000
;; QUESTION SECTION:
;proxy.golang.org.		IN	A

> ;; ANSWER SECTION:
proxy.golang.org.	46	IN	A	142.250.184.177

> ;; Query time: 366 msec
;; SERVER: 10.20.141.5#53(10.20.141.5)
;; WHEN: Fri Jun 28 21:47:33 AEST 2024
;; MSG SIZE  rcvd: 61


### What did you see happen?

Go get is unable to fetch a module because it's using a wrong proxy address.

### What did you expect to see?

Go get should be able to fetch a module.
Repository: react-native
Issue: Memory Leak with latest React Native Integrated App on v0.74.2
Labels: Issue: Author Provided Repro

### Description

Facing Memory Leak with React Native app integrated with existing native app. 

I am currently on React Native 0.71.1 and tried to update to React Native 0.74.2.After upgrade facing memory leak. Memory usage keeps on increasing. With version 0.72 also there is no leak faced. But from version 0.73 facing memory leak.

Following [this react native callstack brownfield architecture](https://github.com/callstack/react-native-brownfield) to load react native inside existing app as we have multiple entry points from native app to load react native in Fragment and also in Activity.

### Steps to reproduce

1. Clone the repo - `https://github.com/callstack/react-native-brownfield`
2. Do `yarn install`
3. Try to open the example kotlin app
4. Open profiler from android studio
5. Perform Action like Click on Open React Native Button
6. Capture the Heapdump

### React Native Version

0.74.2

### Affected Platforms

Runtime - Android

### Output of `npx react-native info`

```text
System:
  OS: macOS 14.5
  CPU: (10) arm64 Apple M1 Pro
  Memory: 125.97 MB / 16.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 18.20.1
    path: ~/.nvm/versions/node/v18.20.1/bin/node
  Yarn:
    version: 1.22.22
    path: ~/.nvm/versions/node/v18.20.1/bin/yarn
  npm:
    version: 10.5.0
    path: ~/.nvm/versions/node/v18.20.1/bin/npm
  Watchman:
    version: 2024.05.06.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: Not Found
IDEs:
  Android Studio: 2024.1 AI-241.15989.150.2411.11948838
  Xcode:
    version: 15.4/15F31d
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.10
    path: /Users/satheshrangasamy/.jenv/shims/javac
  Ruby:
    version: 2.7.4
    path: /Users/satheshrangasamy/.rbenv/shims/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.74.2
    wanted: 0.74.2
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: true
  newArchEnabled: false
```


### Stacktrace or Logs

```text
Attached Memory Leak Profiler ScreenShot
```


### Reproducer

https://github.com/satheshrgs-rksv/memoryleakreproducer

### Screenshots and Videos

![Screenshot 2024-06-28 at 17 18 32](https://github.com/facebook/react-native/assets/171787196/782f0cc1-657d-49aa-a587-5ec6409545f8)

![image](https://github.com/facebook/react-native/assets/171787196/7b7088a5-2648-4d6d-a6ac-e5b497ead270)
Repository: vscode
Issue: Extension Profiling Path PII-Masking Hides Relevant Information
Labels: papercut :drop_of_blood:

I'm using this feature to create an extension host profile:

![Image](https://github.com/user-attachments/assets/d7e194ce-2c1d-4214-8ebc-d03c530a05b9)


Then I load the profile in chrome and get this:

![Image](https://github.com/user-attachments/assets/4e5349ed-9f43-4816-9c0f-52e75ce29502)

In that view, it seems that the full path is removed (for data privacy reasons I guess). However, in that form, it makes the feature very useless, as it does not tell me from which extension `extension.js` comes from.

Seems this happens here:

https://github.com/microsoft/vscode/blob/1b27e602ed26c3aa7d232788c5ca32edc41b9bba/src/vs/workbench/contrib/extensions/electron-sandbox/runtimeExtensionsEditor.ts#L216-L224

and here:

https://github.com/microsoft/vscode/blob/1b27e602ed26c3aa7d232788c5ca32edc41b9bba/src/vs/platform/profiling/common/profiling.ts#L52-L61

Can we add a hidden setting to disable this?