sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: neovim
Issue: Spell checking could be just another diagnostic source
Labels: enhancement,needs:discussion,spell,diagnostic

### Feature already in Vim?

No

### Feature description

At the moment, NeoVim has a spell checking capability inherited from Vim - as far as I know, mostly unchanged/common to how Vim behaves.

Of course, NeoVim also has a generalized diagnostic handling capability too. I tend to use `[d`, `]d` to navigate around my diagnostics, and `[s`, `]s` (from `vim-unimpaired`) to navigate around my misspellings. It occurred to me, then, that really misspellings are just a special case of diagnostics. It would be really interesting if NeoVim were to treat misspellings as diagnostic entries, presumably in a 'spelling' namespace - enabling us to treat them in a common way. There might be some breaking changes around the fringes, but if the existing spell keybindings continued to work with that "in-built diagnostic provider" too much backwards-breaking-change could be avoided.

I'm sure this is not a trivial refactoring, but I would be interested to know if other folks would see the value.
Repository: go
Issue: cmd/go: add -e flag to 'go get -u'
Labels: Proposal,Proposal-Accepted,GoCommand

A missing dependency currently blocks `go get -u` from working at all. For a concrete example, see https://github.com/golang/go/issues/28424#issuecomment-1175438836.

`go mod tidy` and `go mod vendor` have a `-e` flag that means: "attempt to proceed despite errors
encountered while loading packages". I propose that we add an analogous `-e` flag to `go get -u`.

cc @bcmills
Repository: material-ui
Issue: How do I use CSSProperties from legacy mui/styles module?
Labels: support: question,v5.x migration

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Current behavior 😯

Hi Mui team.

I really like to use mui 5 and it excited me.
Today, I have one trouble to use it with mui/styles.
In my project, I am using many things like CSSProperties, CreateCSSProperties, PropsFunc, createStyles, WithStyles, withStyles from @mui/styles.
Btw, mui 5 says @mui/styles is just legacy libray.

If yes, where can I import above interfaces and functions and how to use it?
This is really important and urgent for me.

I hope you update me with good solution.
Thanks a lot.

### Expected behavior 🤔

_No response_

### Steps to reproduce 🕹

Steps:

1.
2.
3.
4.


### Context 🔦

_No response_

### Your environment 🌎

Currently my env is
- windows 10
- Visual Studio code
- Dependencies
 "@mui/icons-material": "5.8.4",
 "@mui/lab": "5.0.0-alpha.87",
 "@mui/material": "5.8.6",
 "@mui/styles": "5.8.6",
 "@mui/utils": "5.8.6",
  "typescript": "4.7.4"
  "react": "^18.2.0",
  "react-dom": "^18.2.0",
  
  "eslint": "^8.18.0",
  "eslint-config-tetra": "workspace:^",
Repository: transformers
Issue: Add TF implementation of LongT5 model
Labels: TensorFlow,New model

### Feature request

Add TF implementation of LongT5 model

### Motivation

Add support for TF backend to allow using LongT5 with TF.

### Your contribution

I will add this :]

cc: @gante @patrickvonplaten
Repository: neovim
Issue: "E302: Could not rename swap file" when using neovim as my MANPAGER with a non-default swap directory
Labels: bug,runtime

### Neovim version (nvim -v)

v0.7.2

### Vim (not Nvim) behaves the same?

Not applicable: vim cannot be configured as a manpager this easily

### Operating system/version

Ubuntu 22.04 LTS

### Terminal name/version

Terminal 2.12.7 (445)

### $TERM environment variable

xterm-256color

### Installation

apt install -y neovim

### How to reproduce the issue

I'd like to use neovim to view man pages. To accomplish this, I have the following set in my `.bashrc` file:

```
export MANPAGER='nvim +Man!'
```

Opening a man page eventually comes up in neovim, but on startup for each man page brings up the following annoying message for about a second or two:

```
Error detected while processing function man#init_pager:
line   20:                                                                                                                                                                                                                                                                                    
E302: Could not rename swap file
```

I've found that this is related to putting my swap files in `~/.vim/swap` because I prefer them there rather than polluting my working tree:

```
" Where to store swap files.  By default, they will go into ~/.vim/swap, but                                    
" if that doesn't work, they will go in cwd.                                    
set directory=~/.vim/swap,.                                     
```

Is there a way to get these two settings (using neovim as my MANPAGER and setting an alternate swap location) to work together?

This can be reproduced easily using docker:

```
docker pull ubuntu
docker run -it --name test_nvim_manpager ubuntu /bin/bash

apt update
apt install -y neovim man
unminimize

mkdir -p ~/.config/nvim
echo 'source ~/.vimrc' > ~/.config/nvim/init.vim

echo "export MANPAGER='nvim +Man\!'" >> ~/.bashrc
echo "set directory=~/.vim/swap,." >> ~/.vimrc
source ~/.bashrc

man ls

```

### Expected behavior

I expect not to be prompted with the `E302: Could not rename swap file` message.

### Actual behavior

```
Error detected while processing function man#init_pager:
line   20:                                                                                                                                                                                                                                                                                    
E302: Could not rename swap file
```
Repository: material-ui
Issue: ListItemButton passes style to ListItemText but not ListItemIcon
Labels: support: question,component: list

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Current behavior 😯

I can apply color styles to `<ListItemButton>` and they pass to the child `<ListItemText>` but they don't pass to `<ListItemIcon>`.  I want my hover to apply the text color to everything under the button and I don't see a way to do that.  The background color works as expected, but not the 'color' property


```
<ListItemButton
        sx={{
          "&.Mui-selected": {
            backgroundColor: "red",
            color: "white",
            ":hover": {
              backgroundColor: "yellow",
              color: "gray"
            }
          },
          ":hover": {
            backgroundColor: "blue",
            color: "yellow"
          }
        }}
        selected={selected}
        onClick={() => setSelected((prev) => !prev)}
      >
    <ListItemIcon>
          <AcUnitIcon />
    </ListItemIcon>
    <ListItemText primary="Some Text" />
 </ListItemButton>

Here is a CodeSandbox: [](https://codesandbox.io/s/mui-listitemicon-not-taking-style-from-parent-listitembutton-y9qj9k?file=/src/App.js:560-1144)

### Expected behavior 🤔

I would expect both the text and the icon to get the button's style.  I can hover the text or the icon, but not both.

### Steps to reproduce 🕹

Steps:


[](https://codesandbox.io/s/mui-listitemicon-not-taking-style-from-parent-listitembutton-y9qj9k?file=/src/App.js:560-1144)
https://codesandbox.io/s/mui-listitemicon-not-taking-style-from-parent-listitembutton-y9qj9k?file=/src/App.js:560-1144

### Context 🔦

I want to hover and select the List item parent and have the style apply to both the text and icon

### Your environment 🌎

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
Browser: Chrome Version 103.0.5060.114 (Official Build) (32-bit)

  System:
    OS: Windows 10 10.0.19044
  Binaries:
    Node: 16.14.2 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.15 - C:\Program Files\nodejs\yarn.CMD
    npm: 8.2.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 103.0.5060.114
    Edge: Spartan (44.19041.1266.0), Chromium (103.0.1264.44)
  npmPackages:
    @emotion/react: ^11.9.3 => 11.9.3
    @emotion/styled: ^11.9.3 => 11.9.3
    @mui/base:  5.0.0-alpha.87
    @mui/icons-material: ^5.8.4 => 5.8.4
    @mui/material: ^5.8.6 => 5.8.6
    @mui/private-theming:  5.8.6
    @mui/styled-engine:  5.8.0
    @mui/system:  5.8.6
    @mui/types:  7.1.4
    @mui/utils:  5.8.6
    @types/react: ^18.0.14 => 18.0.14
    react: ^18.2.0 => 18.2.0
    react-dom: ^18.2.0 => 18.2.0
    typescript: ^4.7.4 => 4.7.4
```
</details>
Repository: transformers
Issue: An example for finetuning FLAVA or any VLP multimodel using trainer (for example for classification)
Labels: Examples,Feature request

### Feature request

There is no example of finetuning any VLP model using trainer. I would appreciate an example

### Motivation

The way to use trainers with any Vision and Language pretrained model is not clear. 

### Your contribution

None.
Repository: PowerToys
Issue: Mouse Pointer Speed tray-popup/hotkeys/per-device options
Labels: Idea-New PowerToy

### Description of the new feature / enhancement

![image](https://user-images.githubusercontent.com/77922942/177879762-d1a40966-4421-4964-bfd0-e8d285d59ca8.png)


### Flyout
Add a systray icon with a popout for quickly accessing Pointer Speed options.

Essentially a "volume control" icon but for Pointer Speeds.

Instead of vague ticks/numbers, the explicit multiplier applied should be labelled.

### Hotkey
In the popup there should be a checkbox that enables/disables hotkeys for incrementing/decrementing the slider, as well as setting back to neutral position (proposed default: `[modifier] [+] / [-] / [0]` for incre/decrement/recenter)

### Per-device
While Precision Touchpads have their own instance of Pointer Speed and Acceleration options but still using the exact same calculation/input conversion algorithm as other devices. 

This seems to indicate that the implementation already allows for per-device options, just that it's not exposed for some reason, perhaps due to OEM considerations of not wanting to confuse end-users.

In demographic of users who go out of their way to install PowerToys, the risk of confusion is very unlikely, so if the per-device management of input conversion factor is ever to be exposed, a PowerToys utility would be the ideal place to expose it.

### Scenario when this would be used?

Flyout style quick-adjust is useful for a user to quickly verify or tweak this accessibility/comfort option.

"Mouse volume" hotkey would be an absolute godsend for drawing applications where the user might quickly switch between precise drawing (needing low pointer speed) and selecting UI elements (needing high pointer speed)

Per-device management is useful if user connects or swaps between multiple devices of different input resolutions.

### Supporting information

According to this [this link here](https://liquipedia.net/starcraft2/Mouse_settings#Optimal_Windows_Setting) the 0~10 slider steps in `main.cpl` is only an _interleaved half_ of what's available in the UWP mouse settings page:

![image](https://liquipedia.net/commons/images/8/8b/Mousecpl.PNG) ![image](https://user-images.githubusercontent.com/77922942/177874158-73999d4c-c35a-4fe1-855d-91663c3c9dc4.png)

![image](https://liquipedia.net/commons/images/5/5a/Sensitivity.PNG)

# Source: https://liquipedia.net/starcraft2/Mouse_settings
Repository: flutter
Issue: Fuchsia FEMU yields inconsistent paths in unit tests
Labels: a: tests,engine,dependency: fuchsia,P2,team-engine,triaged-engine

Some unit tests are failing the Linux Fuchsia FEMU pre-submit test because of some path inconsistencies. The failing tests all deal with snapshot paths, which can be found normally in other tests but not in the Linux Fuchsia FEMU test. For example, the JIT snapshot unit tests in https://github.com/flutter/engine/pull/34244 fail the Linux Fuchsia FEMU test but pass all the other ones (including the Linux Fuchsia test). The origin of the failure seems to be that the path where the mock snapshots generated by the test are do not match the paths specified in the unit tests. It seems like the only difference between tests like Linux Fuchsia FEMU and Linux Fuchsia is that the recipe used in Linux Fuchsia is "engine/engine" whereas Linux Fuchsia FEMU uses "engine/femu_test". Is there any way to standardize the paths for the Linux Fuchsia FEMU test to match those of the other tests? Or would you have any suggestions on how to adjust unit tests' paths to account for this? For now, the tests are just ignored in Fuchsia.
Repository: pytorch
Issue: [Releng] Improve the tutorials release process
Labels: module: build,module: ci,triaged

### 📚 The doc issue

Copying from [tutorials](https://github.com/pytorch/tutorials/issues/1964) by @b0noI' request.

We need a better way to test tutorials against the RC than we have now. Today we wait until the release to merge the tutorials which is a confusing way of doing it. We don't have a clear way to know against which dependencies the tutorial was tested against.

### Suggest a potential alternative/fix

We should be able to merge to a branch that runs against RCs and publish under pytorch.org/some-link so that we can preview and make sure the tutorials build correctly before the release.
It would also help to have some kind of printenv output that would tell exactly against which binaries for all pytorch components and related dependancies we have build the tutorials.

cc @malfet @seemethere @pytorch/pytorch-dev-infra
Repository: youtube-dl
Issue: deezer download
Labels: site-support-request

Hello, I notice that deezer download works well, but it only downloads 30 seconds of audio. Is there an alternative to this?
Repository: vscode
Issue: update the language pack and then click reload then the shown language is changed to English
Labels: bug,l10n-platform

1. config display language to chinese
2. install new version vscode
3. then we could find ther extensions update, update the language package
4. click reload
5. display language will be changed to english
Repository: go
Issue: x/vuln/vulncheck: warn on unavailable Go version in binaries
Labels: NeedsFix,vulncheck or vulndb

vulncheck requires Go versions to detected vulnerabilities in standard libraries. If the Go version is `devel` or in general does not parse into semver, we should at least warn the user that stdlib vulnerabilities might not be detected.

cc @jba @julieqiu
Repository: storybook
Issue: framework-preset-react-dom-hack for React versions < 18 isn’t loading without addons declared
Labels: bug,react,has workaround,sev:S3

**Describe the bug**

Follow-up to #18402, specifically for React versions before 18. Switching from v6.4 to v6.5 with Webpack 5, I now get the following error upon building Storybook:

```
ERR! => Failed to build the preview
ERR! Module not found: Error: Can't resolve 'react-dom/client' in '[…]/node_modules/@storybook/react/dist/esm/client/preview'
```

This is because of the `react-dom/client` dynamic import added for React 18 compatibility: https://github.com/storybookjs/storybook/blob/e2673f765722cbb542ef1b5cf8d533c8e746a127/app/react/src/client/preview/render.tsx#L76

The React framework has [framework-preset-react-dom-hack](https://github.com/storybookjs/storybook/blob/next/app/react/src/server/framework-preset-react-dom-hack.ts) set up with an `IgnorePlugin` to work around this, however this isn’t being loaded for some reason.

When logging Webpack plugins via `webpackFinal`, I can see the IgnorePlugin isn’t loaded (it should be last):

```js
[
  VirtualModulesPlugin […]
  HtmlWebpackPlugin […]
  DefinePlugin […]
  ProvidePlugin […]
  CaseSensitivePathsPlugin […]
  ProgressPlugin […]
]
```

This seems to be due to the config’s lack of a `addons: []` (see below).

**To Reproduce**

- Repro repository: https://github.com/thibaudcolas/storybook-react-16
- [package.json](https://github.com/thibaudcolas/storybook-react-16/blob/main/package.json) (not much to see there)
- [.storybook/main.js](https://github.com/thibaudcolas/storybook-react-16/blob/main/.storybook-fails/main.js)
- [Failing CI build](https://github.com/thibaudcolas/storybook-react-16/runs/7243516075?check_suite_focus=true)

**System**

```
  System:
    OS: macOS 12.4
  Binaries:
    Node: 16.15.1
    npm: 8.11.0
  Browsers: […]
```

**Additional context**

This is fixed by adding `addons: []` to the config, as shown in [this separate config](https://github.com/thibaudcolas/storybook-react-16/blob/main/.storybook-works/main.js). This is very puzzling. I don’t know how Storybook combines the different framework presets so didn’t investigate further. I can at least see the `IgnorePlugin` at the end of the list of Webpack plugins as expected, and everything else also seems to be working:

```js
IgnorePlugin {
  options: {
    resourceRegExp: /react-dom\/client$/,
    contextRegExp: /(app\/react|app\\react|@storybook\/react|@storybook\\react)/
  },
  checkIgnore: [Function: bound checkIgnore]
}
```
Repository: electron
Issue: [Bug]: AudioWorklet received data is all zeros when packaged
Labels: platform/macOS,bug :beetle:,has-repro-gist,19-x-y,20-x-y

### 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 bug report that matches the one I want to file, without success.

### Electron Version

19.0.7

### What operating system are you using?

macOS

### Operating System Version

12.4 (21F79)

### What arch are you using?

x64

### Last Known Working Electron version

unknown

### Expected Behavior

Our usage of AudioWorklet functions properly both in development mode and production mode.

### Actual Behavior

Our AudioWorklet, intended to turn incoming data into a final MP3, only receives all zeroes from its upstream audio nodes.

The attached gist works when in development mode, but in production mode produces no errors, just a silent final MP3. You can see the 'process' log lines from the worklet - all of its incoming data is zeroes, so the problem is upstream.

You can also see that when packaged the app doesn't appear to be accessing the microphone, because there is no orange dot macOS provides to show you that's happening. You do see the orange dot when in development mode.

### Testcase Gist URL

https://gist.github.com/aed002f3e08b606b36928f449d998ee5

### Additional Information

Also, via Electron Fiddle I've tried it with 19.0.8, and 20.0.0-beta.6. Same: development build works, packaged does not.
Repository: storybook
Issue: addon-interactions: canvasElement returns empty #root div element
Labels: bug,vue,addon: interactions

**Describe the bug**
While trying to test my Vue 2 component with addon-interactions, the `canvasElement` returns an empty #root div element.
I can see the story rendered in the DOM, but `canvasElement` does not include the nested story element.

It's kind of weird. when I switch between stories, it works. only on the first load does it fail to find the story element.

```
import AppButton, { allowedStates, allowedSizes, allowedTypes } from '@/components/AppButton.vue';
import { within, userEvent } from '@storybook/testing-library';
import { expect } from '@storybook/jest';
export default {
  title: 'Components/AppButton',
  component: AppButton,
  argTypes: {
    default: { control: { type: 'text' } },
    icon: { control: { type: 'text' } },
    size: { options: allowedSizes, control: { type: 'select' } },
    state: { options: allowedStates, control: { type: 'select' } },
    type: { options: allowedTypes, control: { type: 'select' } },
    click: { action: 'click' }
  }
};

const Template = (args, { argTypes }) => ({
  props: Object.keys(args),
  components: { AppButton },
  template:
  `<app-button v-bind="$props" @click="click">
    <template v-if="$props.default"><div v-html="$props.default" /></template>
    <template v-if="$props.icon" #icon><div v-html="$props.icon" /></template>
  </app-button>`
});

export const Default = Template.bind({});
Default.args = {
  state: 'primary',
  size: 'medium',
  type: 'button',
  default: '<div>Hello</div>'
};

Default.play = async({ args, canvasElement }) => {
  // Starts querying the component from its root element
  const canvas = within(canvasElement);
  console.log(canvasElement); // <div id="root"></div> <================================= EMPTY ELEMENT
  const button = await canvas.queryByTestId('app-button');
  await expect(button).toBeTruthy();
  await userEvent.click(button);
  await expect(within(button).getByText('Hello')).toBeTruthy();
};
```

**System**
Environment Info:
  System:
    OS: macOS 12.2
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
  Binaries:
    Node: 14.15.1 - /usr/local/bin/node
    npm: 6.14.8 - /usr/local/bin/npm
  Browsers:
    Chrome: 103.0.5060.114
    Firefox: 99.0
    Safari: 15.3
  npmPackages:
    @storybook/addon-actions: ^6.5.9 => 6.5.9 
    @storybook/addon-essentials: ^6.5.9 => 6.5.9 
    @storybook/addon-interactions: ^6.5.9 => 6.5.9 
    @storybook/addon-links: ^6.5.9 => 6.5.9 
    @storybook/addon-postcss: ^2.0.0 => 2.0.0 
    @storybook/jest: 0.0.10 => 0.0.10 
    @storybook/testing-library: 0.0.13 => 0.0.13 
    @storybook/vue: ^6.5.9 => 6.5.9 

**Additional context**
hope this video helps.
https://user-images.githubusercontent.com/37899422/177896735-ea92547a-a22f-49a4-b3a4-ed00d405055e.mov
Repository: deno
Issue: Deno Compile do not use config file
Labels: bug,compile

When we compile our deno app to an executable, it compiles it without deno.json options. I needed `emitDecoratorMetadata` in my project and it works fine with config file but when I compile it, it does not work.
Repository: pytorch
Issue: [ONNX] Exporting the operator `::svd` to ONNX opset version 13 is not supported.
Labels: module: onnx,triaged,OSS contribution wanted,onnx-triaged

### 🐛 Describe the bug

Exporting the operator ::svd to ONNX opset version 13 is not supported.

```
File "C:\Users\kimju\anaconda3\envs\HybrIK\lib\site-packages\torch\onnx\__init__.py", line 350, in export
  return utils.export(
File "C:\Users\kimju\anaconda3\envs\HybrIK\lib\site-packages\torch\onnx\utils.py", line 163, in export
  _export(
File "C:\Users\kimju\anaconda3\envs\HybrIK\lib\site-packages\torch\onnx\utils.py", line 1074, in _export
  graph, params_dict, torch_out = _model_to_graph(
File "C:\Users\kimju\anaconda3\envs\HybrIK\lib\site-packages\torch\onnx\utils.py", line 731, in _model_to_graph
  graph = _optimize_graph(
File "C:\Users\kimju\anaconda3\envs\HybrIK\lib\site-packages\torch\onnx\utils.py", line 308, in _optimize_graph
  graph = _C._jit_pass_onnx(graph, operator_export_type)
File "C:\Users\kimju\anaconda3\envs\HybrIK\lib\site-packages\torch\onnx\__init__.py", line 416, in _run_symbolic_function
  return utils._run_symbolic_function(*args, **kwargs)
File "C:\Users\kimju\anaconda3\envs\HybrIK\lib\site-packages\torch\onnx\utils.py", line 1421, in _run_symbolic_function
  raise symbolic_registry.UnsupportedOperatorError(
torch.onnx.symbolic_registry.UnsupportedOperatorError: Exporting the operator ::svd to ONNX opset version 13 is not supported. Please feel free to request support or submit a pull request on PyTorch GitHub.
```

### Versions

pytorch 1.12.0