sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: Camera Plugin request for an optional parameter to the recordVideo() method
Labels: c: regression,p: camera,package,team-ecosystem,P2,triaged-ecosystem

See https://github.com/flutter/flutter/issues/31225#issuecomment-789224339 for additional information

I would like to be able to pass the desired file path to the recordVideo() method so I will control where it is to be stored (internal vs external storage for example).  This input parameter was recently removed (see reference above).

This should be an optional parameter.
Repository: godot
Issue: Inspector fails to show any exported fields of a custom resource right after creation
Labels: bug,topic:editor

**Godot version:**
3.2.3 stable

**OS/device including version:**
Windows 10 20H2

**Issue description:**
Inspector doesn't allow setting values of a new custom resource making custom resource. You need to save an "empty" resource and only then you can modify it.

**Steps to reproduce:**
1. Add a custom resource via `.gd` file having some exported field
2. Click (inside inspector) to create new object based on `Resource`
3. In the `Script` field use your new script file
4. Expect to see fields of exported variables, but instead you need to save the resource and reopen it.

**Minimal reproduction project:**
[ResourceInspectorBug.zip](https://github.com/godotengine/godot/files/6072210/ResourceInspectorBug.zip)
Repository: flutter
Issue: Enable custom "flutter create" templates
Labels: c: new feature,tool,P3,team-tool,triaged-tool

It would be interesting to enable the creation of custom templates usable with `flutter create`, which don't require that the templates be actually in our repo. For example, if Rive wanted to create a template that showed off how to use Rive animations in Flutter, they could do so without having to land code in the flutter/flutter repo. (VGV have done something similar: https://verygood.ventures/blog/flutter-starter-app-very-good-core-cli)

Should we enable anyone to create a template, or should we have an allowlist? There's a risk of people tricking people into running hostile code if we allow anyone to host templates. We could have two tiers, one for template sets whose creators we trust, and one which gets a big warning.

How do we identify templates? We could do it by URL, or by some well-established pattern e.g. domain:path, like `example.com:demoapp` which expands to `example.com/.flutter-templates/demoapp.zip` or some such.

How do we host templates? zip files?

How do we avoid having to include redundant files? e.g. it'd be nice if most templates could be just lib/main.dart and pubspec.yaml.
Repository: godot
Issue: TextEdit: setting scroll_vertical does not always work properly
Labels: bug,needs testing,topic:gui

**Godot version:**
v3.2.3.stable.official

**OS/device including version:**
Windows 10 20H2

**Issue description:**
I have a TextEdit that is set to readonly, used to display help texts in a panel that can be hidden (visible = false).  The help texts are just strings that get applied to the TextEdit's .text property.  These strings have wrapped lines, but I am not sure if that is relevant.
If the control is invisible, setting scroll_vertical does not work.  It will only update the scroll position if the control is visible.  As far as I can tell, this is not documented (i.e. that you cannot set scroll_vertical on a hidden control), but probably should be.
However, even if I set scroll_vertical after the TextEdit is set to be visible, it sometimes does not work (in my case, when I re-open the same help text - i.e. do not change the text).  I managed to work around it by adding yield(get_tree(),"idle_frame") before I set the scroll position, but it's not clear from any documentation that this is what is required, and ideally it should not be needed.

So the issue is in two parts: (1) a TextEdit must be visible or setting scroll_vertical has no effect (sometimes meaning that you need to wait a frame before setting it), and (2) none of this is documented.

**Steps to reproduce:**
As above.

**Minimal reproduction project:**
Let me know if this is needed.
Repository: rust
Issue: No way to run `no_run` doctests
Labels: T-rustdoc,A-doctests

The Rustdoc book [suggests](https://doc.rust-lang.org/rustdoc/documentation-tests.html) that `no_run`

> [..] is important for examples such as "Here's how to retrieve a web page," which you would want to ensure compiles, but might be run in a test environment that has no network access.

However, it follows from this that in some cases you _do_ want to run doctests marked as `no_run`, such as if the test environment _does_ have network access. This is possible with regular tests marked `#[ignore]` by passing `-- --ignored` to `cargo test`, but the same does not work with documentation tests. Either an argument to run `no_run` doctests should be added, or the rustdoc book should be updated with a more appropriate use-case for `no_run`. The latter is probably a better solution for now, given that adding such a flag would likely be difficult.
Repository: pytorch
Issue: doxygen and pytorch documentation
Labels: module: docs,module: cpp,triaged

## 📚 Documentation

PyTorch needs to have better documentation.  The web site hosts document pages which are essentially blank and offers zero information:  https://pytorch.org/cppdocs/api/classat_1_1_tensor.html

I attempted to generate my own Doxygen docs, but quickly realized that output of my own doxygen pages looked essentially the same as what is available on the web site.

This makes it extremely difficult for developers new to pytorch to use the API, as it appears there is no documentation available.

cc @yf225 @glaringlee @brianjo @mruberry
Repository: create-react-app
Issue: Use Babel "assumptions"
Labels: issue: proposal,needs triage

### Is your proposal related to a problem?

I've had to add global `loose: true` in my project because one of the proposals react needs and CRA sets had (and has) `loose: true` and babel was unhappy about mismatch `loose` settings around 2020-05-27.

Since then, babel has evolved, and lately `loose: true` became more loose w.r.t. arrays: https://github.com/babel/babel/issues/12935

### Describe the solution you'd like

At the same time, `assumptions` were recently added to babel, which allow for more granular control than the boolean `loose`.
Spec: https://github.com/babel/rfcs/blob/master/rfcs/0003-top-level-assumptions.md

Perhaps, it is possible to configure react or user code that uses react via assumptions as opposed to setting `loose` on one specific transform?

Previous discussion: https://github.com/facebook/create-react-app/issues/4263

### Describe alternatives you've considered

Status quo  leaves me in a bind and is not pretty:
* global `loose: true` breaks some array use
* global `loose: false` works but generates a ton of babel warnings

[There probably are other alternatives, I'm certainly not an expert here; I wish react and babel folks talked to each other 🙏🏿 ]
Repository: neovim
Issue: /dev/stdin not available in system()
Labels: bug,job-control

<!-- Before reporting: search existing issues and check the FAQ. -->

- `nvim --version`: NVIM v0.3.8
- `vim -u DEFAULTS` (version: ) behaves differently? yes
- Operating system/version: Linux, CentOS 7
- Terminal name/version: Terminal.app
- `$TERM`: xterm-256color

### Steps to reproduce using `nvim -u NORC`

```
$ nvim -u NORC

:echo system('cat /dev/stdin', '1')
```

### Actual behaviour

    cat: /dev/stdin: No such device or address

### Expected behaviour

    1

---

Doesn't repro in Vim (Linux or macOS) and in Neovim on macOS. Probably on macOS /dev/stdin symlink actually exists – not some shell trickery
Repository: neovim
Issue: virt_text overlay does not scroll horizontally
Labels: bug,marks

- `nvim --version`: NVIM v0.5.0-dev+1116-gbda12927b

### Steps to reproduce using `nvim -u NORC`

```
nvim -u NORC
:set nowrap
5000ik<ESC>
:lua ns_id = vim.api.nvim_create_namespace("foo")
:lua vim.api.nvim_buf_set_extmark(0, ns_id, 0, 1, { virt_text={{'gg', 'String'}}, virt_text_pos='overlay'})
$
```

### Actual behaviour

When scrolling right, the overlay virtual text stays in the same place relative to the window.

### Expected behaviour

It should scroll with the rest of the text
Repository: node
Issue: Worker threads can trigger MaxListenersExceededWarning when stdout/stderr are overloaded or corked
Labels: worker

* **Version**: 15.10.0
* **Platform**: macOS
* **Subsystem**: worker

### What steps will reproduce the bug?

Run `node example.js` with these files:

#### example.js
```
const { Worker } = require("worker_threads");

process.stdout.cork();
for (let i = 0; i < 15; i++) {
  new Worker("./example_worker.js");
}
process.stdout.write(Buffer.alloc(process.stdout.writableHighWaterMark, "!"));
```
#### example_worker.js
```
console.log("OUT");
```

### How often does it reproduce? Is there a required condition?

Reproduces consistently.

### What is the expected behavior?

Should run and then exit silently.

### What do you see instead?

Runs and logs a warning:
```
(node:23883) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 drain listeners added to [WriteStream]. Use emitter.setMaxListeners() to increase limit
(Use `node --trace-warnings ...` to show where the warning was created)
```

### Additional information

The worker logic uses `.pipe()` and tries to avoid issues like this with its `pipeWithoutWarning` helper, but that doesn't apply to events that are added internally within `pipe` at a later time, so that approach just doesn't seem right.

`.pipe()` adds `dest.on("drain", ...` when the destination is corked or overloaded, and so if the number of workers is > `defaultMaxListeners` and the destination write returns `false`, Node logs a warning.
Repository: go
Issue: x/tools/go: create modanalysis package
Labels: NeedsInvestigation,FeatureRequest,Tools,Analysis

### background
An analysis framework was built out for the go language, to make writing linters (and metalinters easier). `go.mod` files are another custom dsl, where you may want to enforce standards. Thus it seems reasonable to make an analysis package for modules.

One of the big potential benefits is an official "get me the main `go.mod`" function, since currently guessing or slurping `go env -json` are the best bad options. Furthermore, third party `go.mod` linters have already started popping up: [gomodguard](https://github.com/ryancurrah/gomodguard).

### alternatives
The exact location is not terribly important, it could also be `golang.org/x/tools/go/analysis/modanalysis` or `golang.org/x/mod/analysis`, but `golang.org/x/tools/go/analysis/modanalysis` seems reasonable.

Instead of adding a whole new package and interface, it may be easier to add a `ModPass` struct based on the `go.mod` syntax, a new `ModRun func(*ModRun) (interface{}, error)` struct field, and the plumbing to read in the main `go.mod`. This seems like a choice for someone more familiar with the current package.
Repository: godot
Issue: CSGMesh is not updated when it's properties are changed
Labels: bug,topic:core,confirmed,regression,topic:3d

<!-- Please search existing issues for potential duplicates before filing yours:
https://github.com/godotengine/godot/issues?q=is%3Aissue
-->

**v3.2.4.rc3.official**

**Windows 10 PRO; Radeon RX 570 8GB; Driver 20.12.1; GLES3**

**Issue description:**
CSGMesh is not updated when it's properties are changed


**Steps to reproduce:**

1. Add a CSGMesh to the scene.
2. Change the mesh property. Some of them show up immediatly, some do not.
3. If the mesh is not visible, changing to a different tab and coming back will fix it.
- *If you undo changing the mesh change, the meshes wireframe stays visible.*

**Minimal reproduction project:**


https://user-images.githubusercontent.com/12641229/109754737-3643c580-7baa-11eb-84af-58d115801c8d.mp4
Repository: youtube-dl
Issue: Support downloading YouTube videos with multiple audio tracks
Labels: request

## Checklist

<!--
Carefully read and work through this check list in order to prevent the most common mistakes and misuse of youtube-dl:
- First of, make sure you are using the latest version of youtube-dl. Run `youtube-dl --version` and ensure your version is 2021.03.03. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Search the bugtracker for similar feature requests: http://yt-dl.org/search-issues. DO NOT post duplicates.
- Finally, put x into all relevant boxes (like this [x])
-->

- [x] I'm reporting a feature request
- [x] I've verified that I'm running youtube-dl version **2021.03.03**
- [x] I've searched the bugtracker for similar feature requests including closed ones

## Description

Some YouTube videos have multiple audio tracks. Here’s an example: https://www.youtube.com/watch?v=WaOKSUlf4TM

![](https://user-images.githubusercontent.com/81942/109778316-f65dfc00-7c04-11eb-9ee4-b06ef774b140.png)

It would be nice if `youtube-dl` would download all available audio tracks by default. Separately (but IMHO less importantly), perhaps there should be an option to specify the audio track(s) to download.
Repository: create-react-app
Issue: magic header not detected when build .wasm file 
Labels: needs triage

Hi, 
I  use .wasm file in create-react-app, but when I run 'npm run build', I got the error:

 **Module parse failed: magic header not detected
File was processed with these loaders:
 * ./node_modules/wasm-loader/index.js
You may need an additional loader to handle the result of these loaders.
Error: magic header not detected**

I already add 'wasm-loader' in the project according to this article: https://www.telerik.com/blogs/using-webassembly-with-react 
However when I import the same .wasm file in vue-cli, it can work correctly.

Could the create-react-app support .wasm or change the default webpack config to support this? Thanks!
Repository: excalidraw
Issue: More arrow ending shapes 
Labels: enhancement

I would like to see a few more arrow-ending options be added. 
I would like to see some more, such as hollow circle, and half-circle. 

Is this something that could be added?

Is there an existing plan to add more, or should I try to provide som commonly used in my work as an enterprise architect?
Repository: storybook
Issue: [vue] Code preview ignores<template> inside story template
Labels: bug,vue,block: source

**Describe the bug**
<template> cut out from code preview
<template v-slot>  fully cutted with slot data, descendents

**Expected behavior**
I expect to see the full code template in the preview


**Code snippets**
```
// ~/BaseTable.stories.js
export const CustomRender = (args, { argTypes }) => ({
    props: Object.keys(argTypes),
    components: { BaseButton, BaseTable },
    methods: {
        formatPrice,
    },
    template: `
  <BaseTable v-bind="$props">
    <template>
      <div>Template??</div>
    </template>
    <template v-slot:price="{ value }">
        {{ formatPrice(value) }}
    </template>
    <template v-slot:actions="{ row }">
        <BaseButton secondary small error icon="trash" />
    </template>
  </BaseTable>
`,
});

CustomRender.args = {
    ...Base.args,
    columns: [
        { dataPath: 'name', title: 'Название' },
        { dataPath: 'sku', title: 'Артикул', scopedSlots: { customRender: 'sku' } },
        { dataPath: 'price', title: 'Цена', scopedSlots: { customRender: 'price' } },
        { dataPath: '', scopedSlots: { customRender: 'actions' } },
    ],
};
```

code preview output

```
<template>
  <BaseTable
    :columns='...'
    :dataSource='...'
    defaultValue="—"
    rowKey="model_id"
  >
    <div>Template??</div>
  </BaseTable>
</template>
```
**System**
Environment Info:

  System:
    OS: Windows 10 10.0.19042
    CPU: (8) x64 AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx  
  Binaries:
    Node: 13.14.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.10 - C:\Program Files\nodejs\yarn.CMD
    npm: 6.14.4 - C:\Program Files\nodejs\npm.CMD
  Browsers:
   hromium (88.0.705.81)
  npmPackages:
    @storybook/addon-actions: ^6.1.17 => 6.1.17
    @storybook/addon-essentials: ^6.1.20 => 6.1.20
    @storybook/addon-links: ^6.1.17 => 6.1.17
    @storybook/vue: ^6.1.20 => 6.1.20
Repository: electron
Issue: Eyedropper of color picker can't pick color outside of window
Labels: platform/windows,bug :beetle:,12-x-y,13-x-y,14-x-y,17-x-y,32-x-y,33-x-y

<!--  As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->

### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->

* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.

### Issue Details

* **Electron Version:**
  * 12.0.0
* **Operating System:**
  * Windows 10 (1909)
* **Last Known Working Electron version:**
  * no such

### Expected Behavior
Be able to eyedrop color from outside of electron window

### Actual Behavior
Eyedrop magnifier disappears outside of electron window

### To Reproduce
electron fiddle
https://gist.github.com/kutu/cca8df7c89d317d298213c8a0ce32da5

### Screenshots
![image](https://user-images.githubusercontent.com/228802/109808716-e5cb7700-7c40-11eb-99d0-59eff6943dbd.png)

### Additional Information
In screenshot, you can see that eyedropper see pixels outside of the electron window, but you can't eyedrop them, and eyedrop magnifier crops at the edge of electron window.
Repository: create-react-app
Issue: Support AudioWorklet
Labels: issue: proposal,needs triage

### Is your proposal related to a problem?

<!--
  Provide a clear and concise description of what the problem is.
  For example, "I'm always frustrated when..."
-->

The `AudioContext#createScriptProcessor` method is deprecated, the new way to process audio is through AudioWorklet.

Reference: https://developer.mozilla.org/en-US/docs/Web/API/BaseAudioContext/createScriptProcessor

Right now, there's no way to use the new API with Create React App because it doesn't support web worklets.

This issue is related to #3660 but aims to have a narrower scope in order to only support AudioWorklet.

### Describe the solution you'd like

<!--
  Provide a clear and concise description of what you want to happen.
-->

CRA should allow the creation of AudioWorklet instances.

### Describe alternatives you've considered

<!--
  Let us know about other solutions you've tried or researched.
-->

The only alternative right now is to use the deprecated API.

### Additional context

<!--
  Is there anything else you can add about the proposal?
  You might want to link to related issues here, if you haven't already.
-->
No.
Repository: electron
Issue: [Feature]: Support cookies on pages loaded over custom protocols
Labels: enhancement :sparkles:,11-x-y,12-x-y,13-x-y

* **Electron Version:** 12.0.0 (actually any version, I tested many except from the beta/nightly)
* **Operating System:** Linux
* **Last Known Working Electron version:** none

### Expected Behavior
The `document.cookie:  is-paid-user=1` gets printed to console.

### Actual Behavior
The `document.cookie: ` gets printed to console (no `is-paid-user=1` cookie record).

### To Reproduce
After changing the `web://news.ycombinator.com` to https://news.ycombinator.com the issue will be gone.

```javascript
const {app, BrowserWindow, protocol} = require("electron");

const scheme = "web";

protocol.registerSchemesAsPrivileged([{scheme, privileges: {secure: true, standard: true, corsEnabled: true}}]);

app.whenReady().then(() => {
  const window = new BrowserWindow();

  window.webContents.session.protocol.registerBufferProtocol(scheme, (...[, callback]) => {
    callback({mimeType: "text/html", data: Buffer.from("<h5>blank page</h5>")})
  })

  window.loadURL("web://news.ycombinator.com").then(() => {
    window.webContents.openDevTools();
    window.webContents.executeJavaScript(`
      document.cookie = "is-paid-user=1;expires=Fri, 31 Dec 2021 20:59:59 GMT;domain=.ycombinator.com;path=/";
      console.log("document.cookie: ", document.cookie);
    `);
  });
});
```


### Screenshots

- https scheme:
  ![expected](https://user-images.githubusercontent.com/1560781/109812794-90419b00-7c3d-11eb-9b76-5f3d97e1446d.png)
- web/custom scheme:
  ![actual](https://user-images.githubusercontent.com/1560781/109812809-946db880-7c3d-11eb-98da-f579daa01c60.png)

### Additional Information

My understanding was that setting `standard: true` in `registerSchemesAsPrivileged` call is enough to make `document.cookie` work on the custom schemes.
Repository: deno
Issue: Runtime permissons request text could be hidden using iTerm custom escape codes
Labels: bug,cli,permissions,high priority

Script to reproduce:
```typescript
console.log("\x1b[38;2;255;0;0mPlease, enter 'g' now");
console.log("\x1b]1337;SetColors=fg=fff\x1b\\\x1b]1337;SetColors=bg=fff\x1b\\");
await Deno.permissions.request({ name: "env" });
```
When running this on iTerm, the only thing visible on the screen is `Please, enter 'g' now` (and also emoji), and it's not clear that script is actually asking for permissions.
Repository: deno
Issue: Add a default and configured threshold for  `deno coverage`
Labels: suggestion,testing

## Overview

`deno coverage` should be able to set a threshold, and fail if coverage doesn't meet it.

## What

It would be great if `deno coverage` could use a default threshold that must be met, otherwise the command will fail with an exit code other than `0`. On top of this, it would be great for this to be configured so a user can set their own threshold.

For example, `deno coverage --check --lcov` will return a status of 1 if my coverage (which is 79%) doesn't meet the default threshold (which is 80%).

Then `deno coverage --check --lines=90 --lcov` would return a status of 1 when my coverage for lines (which is 89%) doesn't meet the expected 90%.

Note that the thresholds, return status' and configuration implementation are demonstrated just for explanation. I'm not suggesting how to configure nor what the default threshold should be.

## Why

If people were to start adding coverage to their modules, then ideally the command(s) need to fail if coverage is too low (ie a new feature was added but not unit tests or coverage for it were implemented).

It would also help in the CI, where we usually have a `master` or `ci` job that runs our tests, if test coverage doesn't meet an expectation, then the user (be it a fork on the repo or not), would have to **ensure they add coverage** because the CI will fail due to the returned status code





*100% coverage all the way*
Repository: go
Issue: cmd/go: document how licenses are added to modules that are nested in a repository
Labels: Documentation,NeedsInvestigation

https://pkg.go.dev/github.com/mit-plv/fiat-crypto/fiat-go

The fiat-crypto project is triple licensed under MIT OR Apache-2.0 OR BSD-1-Clause (https://github.com/mit-plv/fiat-crypto/blob/master/COPYRIGHT), but pkg.go.dev isn't recognizing this. It's instead saying the license isn't known.

Incidentally, it seems like maybe https://pkg.go.dev/license-policy should be updated to support BSD-1-Clause?

Related: #40171