sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: InputDecorator appears not to expand for entire widget
Labels: a: text input,framework,f: material design,has reproducible steps,found in release: 3.7,found in release: 3.8,team-design,triaged-design

I noticed that when you set `TextField`'s input decoration border to `OutlineInputBorder` it does encompass it's full size.

`TextField ` example: https://dartpad.dev/?id=9fdc5bbe62239c8912ced4d1677abe89

`InputDecorator` example: https://dartpad.dev/?id=4c1d9d0962bfaf77f57a519cafb3a1e8

**Expected results:** <!-- what did you want to see? -->

I would expect the `OutlineInputBorder` to wrap the entire `TextField`.

**Actual results:** <!-- what did you see? -->

The `OutlineInputBorder` just wraps the first line.

<details>
<summary>flutter doctor -v</summary>
<!-- Finally, paste the output of running `flutter doctor -v` here. -->

```
[✓] Flutter (Channel stable, 3.7.3, on macOS 12.6.2 21G320 darwin-arm64, locale
    en-GB)
    • Flutter version 3.7.3 on channel stable at /usr/local/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 9944297138 (5 days ago), 2023-02-08 15:46:04 -0800
    • Engine revision 248290d6d5
    • Dart version 2.19.2
    • DevTools version 2.20.1

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/robbiebykowski/Library/Android/sdk
    • Platform android-33, build-tools 31.0.0
    • ANDROID_SDK_ROOT = /Users/robbiebykowski/Library/Android
    • Java binary at: /Users/robbiebykowski/Library/Application
      Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/203.7621141/Android
      Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7281165)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14C18
    • CocoaPods version 1.11.3

[✓] Android Studio (version 2020.3)
    • Android Studio at /Users/robbiebykowski/Library/Application
      Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/203.7621141/Android
      Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7281165)

[✓] VS Code (version 1.75.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.58.0

[✓] Connected device (1 available)
    • macOS (desktop) • macos • darwin-arm64 • macOS 12.6.2 21G320 darwin-arm64

```

</details>
Repository: go
Issue: x/vuln/vulncheck: missing empty inlined vulnerable functions
Labels: NeedsDecision,vulncheck or vulndb

Consider the following illustrative program where `bvuln.Vuln` is a vulnerable symbol used at a vulnerable version:

```
package main
                        
import (
   "golang.org/bmod/bvuln"
)
        
func main() {
   bvuln.Vuln()
}
  
// ---------------------------------------------------------------
package bvuln
        
const debug = true
        
func Vuln() {
   if debug {
      return
    }
    ... // some important code, such as ACL check
}
```

### What did you expect to see?

vulncheck and govulncheck binary analysis to detect `Vuln`.

### What did you see instead?

Nothing detected.

The suspected and likely reason for this is that `Vuln` gets inlined and its whole body is deleted due to the constant propagation pass.  Since `debug` is provably `true`, this optimization step will conclude that 1) the code after `if-then` is unreachable and 2) the actual `if-then` can be reduced to a `return`. The actual call to `Vuln` then can be optimized to a no-op. There are no instructions in the binary whose source is `Vuln` and hence there is no way currently to detect the existence of `Vuln`.

### Why is this an issue?

The vulnerability can be caused precisely because `debug` is mistakenly set to true, so the code after `if-then` is never triggered. That could be code that, say, does some ACL checking.

### Is there a potential fix?
 
The compiler could leave a no-op instruction in the binary whose parent is `Vuln`. This is done for some other constructs.

Thanks to @prattmic for bringing this up.

cc @jba
Repository: rust
Issue: Suggest easily-typo'd alternate methods that match provided arguments
Labels: A-diagnostics,A-resolve,T-compiler,D-papercut

### Code

```Rust
fn main() {
    0.add_number(vec![1,2,3]);
    0.add_numbers(1);
}

trait Adder {
    fn add_number(&self, number: i32) -> i32;
    fn add_numbers(&self, numbers: impl IntoIterator<Item=i32>) -> i32;
}

impl Adder for i32 {
    fn add_number(&self, number: i32) -> i32 {
        self + number
    }

    fn add_numbers(&self, numbers: impl IntoIterator<Item=i32>) -> i32 {
        self + numbers.into_iter().sum::<i32>()
    }
}


[Playground](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=817296cf5e5207ed8df1542ed311297d)
```


### Current output

```Shell
error[E0308]: mismatched types
 --> src/main.rs:2:18
  |
2 |     0.add_number(vec![1,2,3]);
  |       ---------- ^^^^^^^^^^^ expected `i32`, found struct `Vec`
  |       |
  |       arguments to this function are incorrect
  |
  = note: expected type `i32`
           found struct `Vec<{integer}>`
note: associated function defined here
 --> src/main.rs:7:8
  |
7 |     fn add_number(&self, number: i32) -> i32;
  |        ^^^^^^^^^^

error[E0277]: `{integer}` is not an iterator
 --> src/main.rs:3:19
  |
3 |     0.add_numbers(1);
  |       ----------- ^ `{integer}` is not an iterator
  |       |
  |       required by a bound introduced by this call
  |
  = help: the trait `Iterator` is not implemented for `{integer}`
  = note: if you want to iterate between `start` until a value `end`, use the exclusive range syntax `start..end` or the inclusive range syntax `start..=end`
  = note: required for `{integer}` to implement `IntoIterator`
note: required by a bound in `Adder::add_numbers`
 --> src/main.rs:8:41
  |
8 |     fn add_numbers(&self, numbers: impl IntoIterator<Item=i32>) -> i32;
  |                                         ^^^^^^^^^^^^^^^^^^^^^^ required by this bound in `Adder::add_numbers`

Some errors have detailed explanations: E0277, E0308.
For more information about an error, try `rustc --explain E0277`.
error: could not compile `playground` due to 2 previous errors
```
```


### Desired output

```Shell
The first line should suggest using `.add_numbers` instead, and the second should recommend using `.add_number` instead.
```


### Rationale and extra context

This was motivated by https://github.com/bevyengine/bevy/issues/7631. This is a commonly encountered error and new Rust users are thrown off course by the suggestion about trait implementations.

### Other cases

_No response_

### Anything else?

_No response_
Repository: svelte
Issue: `a11y-click-events-have-key-events` incorrectly repoted on `<dialog>` elements.
Labels: a11y

### Describe the bug

By default, a dialog element shown via `dialog.showModal()` can be closed by pressing escape.

If I add an `on:click` handler to the dialog to enable clicking the background to dismiss it, I get an `a11y-click-events-have-key-events` warning on the dialog, despite being able to interact with the dialog via keyboard.

I wouldn't mind needing to explicitly disable the warning, but I can't just use
```svelte
<!-- svelte-ignore a11y-click-events-have-key-events -->
```
as that also disables the warnings for all *children* of the dialog as well.

### Reproduction

```svelte
<script>
  let modal;
  const clickBackdrop = (event) => {
    if (event.target === modal) {
      close();
    }
  }
</script>

<button on:click={() modal.showModal()}>
	Open
</button>
<dialog bind:this={modal} style:overflow="none" on:click={clickBackdrop}>
  <div>
    <button on:click={() => modal.close()} >Close</button>
  </div>
</dialog>

<style>
  div {
    background-color: white;
    height: 3em;
    width: 6ch;
    padding: 1em;
  }
  dialog {
    border: 0;
    padding: 0;
  }
  dialog::backdrop {
    background-color: rgba(10, 10, 10, 0.86);
  }
</style>
```

### Logs

_No response_

### System Info

```shell
npmPackages:
    svelte: ^3.55.1 => 3.55.1 
```
```


### Severity

annoyance
Repository: neovim
Issue: `vim.lsp.buf.format()` will cause an empty modification in Lua
Labels: bug,lsp,marks

### Neovim version (nvim -v)

v0.9.0-dev-944+g89722ddfa

### Language server name/version

lua-language-server 3.6.11

### Operating system/version

Ubuntu 22.04

### Steps to reproduce using "nvim -u minimal_init.lua"

```lua
local pattern = 'lua'
local cmd = { 'lua-language-server' }
-- Add files/folders here that indicate the root of a project
local root_markers = { '.git', '.editorconfig' }
-- Change to table with settings if required
local settings = vim.empty_dict()

vim.api.nvim_create_autocmd('FileType', {
	pattern = pattern,
	callback = function(args)
		local match = vim.fs.find(root_markers, { path = args.file, upward = true })[1]
		local root_dir = match and vim.fn.fnamemodify(match, ':p:h') or vim.NIL
		vim.lsp.start({
			name = 'bugged-ls',
			cmd = cmd,
			root_dir = root_dir,
			settings = settings
		})
	end
})
```


### Expected behavior

If the buffer is formatted, `vim.lsp.buf.format()` should not cause a modification.

Maybe this happened because `lua-language-server` not checking if the formatting file is already formatted or if this is something that neovim's ls-client should check.

### Actual behavior

If your buffer is already formatted, then when you execute `vim.lsp.buf.format()` again, the file will become a modified file even it's changed nothing.

Moreover, if you press `u` to undo this buffer, you will find that it does nothing.

So if you do `vim.lsp.buf.format()` multiple times, you will need to undo it multiple times to undo your desired modification.

### Log file

No output
Repository: flutter
Issue: [google_sign_in_web] Link to more user authentication systems that support Google Sign In.
Labels: d: api docs,platform-web,p: google_sign_in,P3,team-web,triaged-web

The README.md of the package suggest users that long-lived sessions to use some 3P user authentication system.

It currently lists: 

* [Firebase Auth](https://firebase.google.com/docs/auth/flutter/federated-auth#google)

But it seems that more alternatives may come down the line, for example:

* it seems that Amplify has this feature in "development preview": https://docs.amplify.aws/lib/auth/social/q/platform/flutter/#how-it-works
* auth0 does not support web (?): https://community.auth0.com/t/flutter-sdk-support-for-web-applications/91328
* (Maybe others?)

Link to those alternatives once their solution is generally available (especially if they have integration instructions)
Repository: PowerToys
Issue: Mouse Utilities - Mouse Pointer Crosshairs doesn't update its position as much when using a trackpad pointing device
Labels: Issue-Bug,Needs-Repro,Needs-Team-Response,Product-Mouse Utilities

### Microsoft PowerToys version

0.67.1

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Mouse Utilities

### Steps to reproduce

The issue only affects trackpad usage, other forms of cursor input like mouse movement gets tracked just fine. Possibly related to #16634, not #16650. Shaking the cursor using a mouse gets tracked normally, exclusively only trackpad in my case.

1. Enable `Mouse Pointer Crosshairs` in Mouse Utilities, doesn't matter how one activates it.
2. Move the mouse using a trackpad with increased sensitivity, the "enhance pointer precision" option doesn't affect the issue.

### ✔️ Expected Behavior

The bullseye of the crosshair to stay aligned with the cursor position. I can't get a proper screenshot which includes the mouse and the crosshairs

### ❌ Actual Behavior

The pointer gets ahead of the crosshair, and the crosshair not updating its position

### Other Software

_No response_
Repository: flutter
Issue: [google_sign_in_web] Improve mocking of the GIS API.
Labels: platform-web,p: google_sign_in,package,P3,c: tech-debt,team-web,triaged-web

The current `gis_client.dart` file was introduced to not use the `google_identity_services_web` API and yet be mockable in tests.

However, the file itself contains some code that could use testing; particularly the handling of JS SDK client responses within Streams of events.

Move the mocking "one level up" so we mock two service facades:

* google_identity_services_web/id.dart (exports the "id" namespace)
* google_identity_services_web/oauth2.dart (exports the "oauth2" namespace)

That way the bits of the GIS client that are part of the plugin can be tested.
Repository: vscode
Issue: terminal smooth scroll is slow to response
Labels: bug,help wanted,upstream,upstream-issue-linked,terminal-input


https://user-images.githubusercontent.com/41773861/218630899-02576742-70f8-44df-b43b-5469bcfb571b.mov

```
Version: 1.75.1 (Universal)
Commit: 441438abd1ac652551dbe4d408dfcec8a499b8bf
Date: 2023-02-08T21:34:59.000Z
Electron: 19.1.9
Chromium: 102.0.5005.194
Node.js: 16.14.2
V8: 10.2.154.23-electron.0
OS: Darwin x64 22.3.0
Sandboxed: No
```
Repository: next.js
Issue: Nextjs Image component  doesn't work with dynamic url
Labels: bug,Image (next/image)

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

Operating System:
      Platform: linux
      Arch: x64
      Version: #62-Ubuntu SMP Tue Nov 22 19:54:14 UTC 2022
    Binaries:
      Node: 16.16.0
      npm: 8.15.1
      Yarn: 1.22.19
      pnpm: N/A
    Relevant packages:
      next: 13.1.1
      eslint-config-next: 13.1.1
      react: 18.2.0
      react-dom: 18.2.0

### Which area(s) of Next.js are affected? (leave empty if unsure)

Image optimization (next/image, next/legacy/image)

### Link to the code that reproduces this issue

https://github.com/zwelhtetyan/tiktok-clone

### To Reproduce

---

### Describe the Bug

```javascript
// It doesn't work with next Image component
export default function UserProfile({ src, className }: Props) {
  return (
    <Image
      src={src}
      width={100}
      height={100}
      alt='profile_img'
      className={`${className} w-12 h-12 rounded-full p-[4px] duration-200 hover:bg-gray-200 dark:hover:bg-darkSecondary cursor-pointer`}
    />
  );
}
```
I reuse UserProfile component in showing userAccount by maping the response data from server.

Nextjs Image component doesn't work with dynamic url. So It doesn't affect when user change profile picture.

When i change default img tag , It does work expectly.But still showing warning to use Next Image component.

```javascript
// It does work with default img tag
export default function UserProfile({ src, className }: Props) {
  return (
    <img
        src={src}
        alt='profile_img'
        className={`${className} w-12 h-12 rounded-full p-[4px] duration-200 hover:bg-gray-200 dark:hover:bg-darkSecondary cursor-pointer`}
      />
  );
}
```


### Expected Behavior

_Image component should work with dynamic url_

### Which browser are you using? (if relevant)

chrome

### How are you deploying your application? (if relevant)

--not yet
Repository: vscode
Issue: Quick input missing required ARIA state
Labels: bug,accessibility,quick-pick

<!-- ⚠️⚠️ 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.75.1
- OS Version: Windows 10

Steps to Reproduce:

1. Open Command Palette
2. Inspect the quick input DOM

```
<input class="input" autocorrect="off" autocapitalize="off" spellcheck="false" type="text" wrap="off" aria-describedby="quickInput_message" placeholder="Type the name of a command to run." style="background-color: inherit; color: var(--vscode-input-foreground); width: calc(100% - 0px);" aria-label="Type the name of a command to run." role="combobox" aria-haspopup="true" aria-autocomplete="list" aria-activedescendant="list_id_11_0">
```

It has role `combobox` but without `aria-expanded`. `aria-expanded` is required for `combobox` role. Refers to
https://w3c.github.io/aria/#combobox

It's reported as a level A violation to WCAG [Criteria 4.1.2](https://www.w3.org/TR/WCAG21/#name-role-value) by accessibility scan.

Fix would probably look something like below
For file https://github.com/microsoft/vscode/blob/main/src/vs/platform/quickinput/browser/quickInput.ts
```
private setComboboxAccessibility(enabled: boolean) {
	if (enabled !== this.comboboxAccessibility) {
		const ui = this.getUI();
		this.comboboxAccessibility = enabled;
		if (this.comboboxAccessibility) {
			ui.inputBox.setAttribute('role', 'combobox');
			ui.inputBox.setAttribute('aria-haspopup', 'true');
			ui.inputBox.setAttribute('aria-expanded', ui.list.isDisplayed()); // <- add
			ui.inputBox.setAttribute('aria-autocomplete', 'list');
			ui.inputBox.setAttribute('aria-activedescendant', ui.list.getActiveDescendant() || '');
		} else {
			ui.inputBox.removeAttribute('role');
			ui.inputBox.removeAttribute('aria-haspopup');
			ui.inputBox.removeAttribute('aria-expanded'); // <- add
			ui.inputBox.removeAttribute('aria-autocomplete');
			ui.inputBox.removeAttribute('aria-activedescendant');
		}
	}
}
```
Repository: electron
Issue: [Feature Request]: Add a way to programmatically close file dialog opened with showOpenDialog
Labels: enhancement :sparkles:

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a feature request that matches the one I want to file, without success.

### Problem Description

When opening a file dialog with showOpenDialog, there is no way to close it programmatically.
I was thinking that it would close when its associated browser window would be closed, but it remains opened.

### Proposed Solution

We could add a 'signal' option the same way it is done for showMessageBox.

### Alternatives Considered

I also tried to use showOpenDialog inside a spawned process, and close that process when I want to close the file dialog. But this solution seems very suboptimal.

### Additional Information

_No response_
Repository: storybook
Issue: [Bug]: play function does not work as expected when running tests in forEach loop
Labels: bug,addon: interactions

### Describe the bug

I'm using StoryBook 6.5 and  i have a simple tabs component written using React 18 and MUI.

I'm trying to write a simple test that checks that all tabs are in view.

I have this simple play function:


> export const Default = Template.bind({});
> Default.play = async ({ canvasElement, args }) => {
>     const canvas = await within(canvasElement);
>     args.children.forEach(async (tab, idx) => {
>     const tabBtn = document.getElementById(tab.props.id)!;
>     await expect(tabBtn).toBeInTheDocument();
>     await userEvent.click(tabBtn);
>     const tabContent = await canvas.findByText(`Tab ${idx + 1}`);
>     await expect(tabContent).toBeInTheDocument();
>   });
> };

But i'm seeing a very weird behavior:

![image](https://user-images.githubusercontent.com/36603084/218692508-a69d650c-6fda-475a-b522-9469e18d6e34.png)

as you can see, it seems to first run this line several times: `await expect(tabBtn).toBeInTheDocument();`
then this line: `await userEvent.click(tabBtn);`
and at the end it tries to run: `const tabContent = await canvas.findByText(`Tab ${idx + 1}`);`

and obviously the test fails since it can't find the correct content.

Since i'm using await, I would expect it to run in the order it was written.

Furthermore, when running it in jest all the tests pass:

![image](https://user-images.githubusercontent.com/36603084/218694379-1be48a99-3bb6-4463-8991-ba02a5c9c4ad.png)

Am I missing something?



### To Reproduce

_No response_

### System

```shell
System:
    OS: macOS 12.6
    CPU: (8) arm64 Apple M1
  Binaries:
    Node: 18.13.0 - ~/.nvm/versions/node/v18.13.0/bin/node
    Yarn: 1.22.19 - ~/Library/pnpm/yarn
    npm: 8.19.3 - ~/.nvm/versions/node/v18.13.0/bin/npm
  Browsers:
    Chrome: 109.0.5414.119
    Firefox: 103.0.2
    Safari: 16.0
```


### Additional context

_No response_
Repository: storybook
Issue: [Feature Request]: storySort but for composition
Labels: feature request,needs triage

### Is your feature request related to a problem? Please describe

We have 2 storybooks: one for design system and another one is a sandbox. DS Storybook is embedded in Sandbox via composition. But it renders after all Sandbox stories which is not ideal.

### Describe the solution you'd like

We would like to be able to configure the order of embedded storybooks. 

### Describe alternatives you've considered

We could have 3 storybooks:
Host 
|--- Design System
|--- Sandbox

But it makes working with Chromatic overly complex, as we rely on it to publish our storybooks. Other teams members, management and designers often use published storybook and they would like to see all stories in one place

### Are you able to assist to bring the feature to reality?

yes, I can

### Additional context

_No response_