sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: youtube-dl
Issue: Hook that called when complete postprocessing
Labels: request

<!--

######################################################################
  WARNING!
  IGNORING THE FOLLOWING TEMPLATE WILL RESULT IN ISSUE CLOSED AS INCOMPLETE
######################################################################

-->


## 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 2020.09.06. 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 **2020.09.06**
- [x] I've searched the bugtracker for similar feature requests including closed ones


## Description

<!--
Provide an explanation of your issue in an arbitrary form. Please make sure the description is worded well enough to be understood, see https://github.com/ytdl-org/youtube-dl#is-the-description-of-the-issue-itself-sufficient. Provide any additional information, suggested solution and as much context and examples as possible.
-->

 I'm embedding youtube-dl in my program. I know youtube-dl has download hook, but it didn't called when finished postprocessing. My hook just called when finished download. Is there any hook that called when completed postprocessing? (Ex: finish convert downloaded video to mp3)
Repository: opencv
Issue: DNN_TARGET_OPENCL_FP16 support for RK3399's Mali-T860
Labels: feature,priority: low,category: ocl,category: dnn,platform: arm

DNN_TARGET_OPENCL_FP16 inference is currently available only with InferenceEngine (Intel hardware). However T8xx Mali GPUs (and many other GPUs), present in the quite popular ARM64 RK3399, are able to perform fp16 operations. This would result in a x4 inference speed up compared to fp32 inference.

I hope this could trigger a discussion on the changes involved. (Unfortunately I cannot help if OpenCL kernels need changes)

##### Issue submission checklist

 - [x] I report the issue, it's not a question
   <!--
   OpenCV team works with answers.opencv.org, Stack Overflow and other communities
   to discuss problems. Tickets with question without real issue statement will be
   closed.
   -->
 - [x] I checked the problem with documentation, FAQ, open issues,
       answers.opencv.org, Stack Overflow, etc and have not found solution
   <!--
   Places to check:
   * OpenCV documentation: https://docs.opencv.org
   * FAQ page: https://github.com/opencv/opencv/wiki/FAQ
   * OpenCV forum: https://answers.opencv.org
   * OpenCV issue tracker: https://github.com/opencv/opencv/issues?q=is%3Aissue
   * Stack Overflow branch: https://stackoverflow.com/questions/tagged/opencv
   -->
 - [x] I updated to latest OpenCV version and the issue is still there
   <!--
   master branch for OpenCV 4.x and 3.4 branch for OpenCV 3.x releases.
   OpenCV team supports only latest release for each branch.
   The ticket is closed, if the problem is not reproduced with modern version.
   -->
 - [x] There is reproducer code and related data files: videos, images, onnx, etc
   <!--
   The best reproducer -- test case for OpenCV that we can add to the library.
   Recommendations for media files and binary files:
   * Try to reproduce the issue with images and videos in opencv_extra repository
     to reduce attachment size
   * Use PNG for images, if you report some CV related bug, but not image reader
     issue
   * Attach the image as archite to the ticket, if you report some reader issue.
     Image hosting services compress images and it breaks the repro code.
   * Provide ONNX file for some public model or ONNX file with with random weights,
     if you report ONNX parsing or handling issue. Architecture details diagram
     from netron tool can be very useful too. See https://lutzroeder.github.io/netron/
   -->
Repository: pytorch
Issue: PyTorch wheel's own OpenMP library clashing with system-wide OpenMP library at runtime
Labels: triaged,module: openmp

## 🐛 Bug

On MacOS Catalina with PyTorch installed with pip, when the same Python script imports both PyTorch and another package using also OpenMP, the Python interpreter crashes with the following message:

`OMP: Error #15: Initializing libiomp5.dylib, but found libiomp5.dylib already initialized.
OMP: Hint This means that multiple copies of the OpenMP runtime have been linked into the program. That is dangerous, since it can degrade performance or cause incorrect results. The best thing to do is to ensure that only a single OpenMP runtime is linked into the process, e.g. by avoiding static linking of the OpenMP runtime in any library. As an unsafe, unsupported, undocumented workaround you can set the environment variable KMP_DUPLICATE_LIB_OK=TRUE to allow the program to continue to execute, but that may cause crashes or silently produce incorrect results. For more information, please see http://www.intel.com/software/products/support/.`

The issue is that PyTorch provides its own version of OpenMP on MacOS in `<path-to-python-libs>/site-packages/torch/.dylibs/libiomp5.dylib` whereas all python packages imported in a same python script should ideally use the **same** OpenMP library (typically the system-wide one, e.g. `/usr/local/lib/libomp.dylib`). I think it is not portable nor maintainable that all OpenMP-based python packages import their own OpenMP libraries.

## To Reproduce

Steps to reproduce the behavior:

1. `pip install torch`
2. Install another OpenMP-based python module, e.g. xgboost
3. Import both modules in the same python script and run parallel functions from both modules, you'll get the above abort message from the python interpreter

## Expected behavior

PyTorch uses the system-wide OpenMP library used by other OpenMP-based python modules. So the user can choose whatever **unique** OpenMP library she wants to link against the python interpreter.

## Environment

```
Collecting environment information...
PyTorch version: 1.6.0
Is debug build: False
CUDA used to build PyTorch: None

OS: Mac OSX 10.15.1 (x86_64)
GCC version: Could not collect
Clang version: 11.0.3 (clang-1103.0.32.62)
CMake version: version 3.18.2

Python version: 3.7 (64-bit runtime)
Is CUDA available: False
CUDA runtime version: No CUDA
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA

Versions of relevant libraries:
[pip3] numpy==1.19.1
[pip3] torch==1.6.0
[conda] Could not collect
```
Repository: rust
Issue: Confusing diagnostics for lifetime on associated type
Labels: A-diagnostics,A-lifetimes,A-associated-items,T-compiler,D-papercut,D-newcomer-roadblock,A-GATs

When you declare this:
```rust
trait HasAssoc {
    type Assoc;
    fn tap(some: Self::Assoc) -> Self::Assoc;
}
impl HasAssoc for i32 {
    type Assoc = &'a i32;

    fn tap(some: Self::Assoc) -> Self::Assoc {
        some
    }
}
```
you get this error:
```
error[E0261]: use of undeclared lifetime name `'a`
  --> src\main.rs:12:19
   |
12 |     type Assoc = &'a i32;
   |                   ^^ undeclared lifetime
   |
help: consider introducing lifetime `'a` here
   |
11 | impl<'a> HasAssoc for i32 {

```
but if you follow the suggestion and place the lifetime parameter on the impl block, you get this:

```rust
error[E0207]: the lifetime parameter `'a` is not constrained by the impl trait, self type, or predicates
  --> src\main.rs:11:6
   |
11 | impl<'a> HasAssoc for i32 {
   |      ^^ unconstrained lifetime parameter
```

Until today, I thought this requires GATs and I wanted to suggest to put this information in the error message (which some other errors already tells you). But after playing around, I am actually not sure if it requires GATs or if it's even possible - either way, I don't know how to fix the error, so I think the diagnostics could be improved 😉
Repository: godot
Issue: StyleBoxTexture margin cant take floats in inspector
Labels: topic:editor,topic:gui

<!-- Please search existing issues for potential duplicates before filing yours:
https://github.com/godotengine/godot/issues?q=is%3Aissue
-->

**Godot version:**
v3.2.2 mono


**OS/device including version:**
Windows 10 1909


**Issue description:**
When editing a StyleBoxTexture Ressource, the margin inputs in the inspector can't take an float as value, but the region editor and the file can both use floats as values.

**Steps to reproduce:**
1. Make a new StyleBoxTexture
2. add a texture
3. play around with the region editor margins widgets
4. inspect the produced file
5. try to set a float as the margin in the inspector
6. inspect the file again

**Minimal reproduction project:**
[StyleBoxTextureBug.zip](https://github.com/godotengine/godot/files/5184252/StyleBoxTextureBug.zip)
Repository: create-react-app
Issue: Cra can't support postcss-nested syntax because webpack.config.js file haven't postcss-nested module
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..."
-->

Cra can't support postcss-nested syntax because webpack.config.js file haven't **postcss-nested** module.

Sample nested css in my header.module.css file

```css
.Header {
  background: white;
  h1 {
    color: red;
  }
}
```

Expected behavior when compiled

```css
.Header {
  background: white;
}
.Header h1 {
    color: red;
}
```

### Describe the solution you'd like

<!--
  Provide a clear and concise description of what you want to happen.
-->

The problem solved when ejected cra and adding the 'postcss-nested' module to webpack.module.js.

**Can you support postcss-nested by default?**

```js
// config/webpack.config.js
// row 89
ident: 'postcss',
          plugins: () => [
            require('postcss-flexbugs-fixes'),
            require('postcss-nested'), // <----  added this line 
            require('postcss-preset-env')({
              autoprefixer: {
                flexbox: 'no-2009'
              },
              stage: 3
            }),

```
### Describe alternatives you've considered

<!--
  Let us know about other solutions you've tried or researched.
-->

[postcss-nesting](https://www.npmjs.com/package/postcss-nesting) may be an alternative.

### 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.
-->

(Write your answer here.)
Repository: flutter
Issue: RefreshIndicator should work without scrollable child
Labels: c: new feature,framework,f: material design,f: gestures,P3,team-design,triaged-design

To reload data for the current screen it should be possible to use the RefreshIndicator without a scrollbale child.

There are workarounds but they don't feel sensefull...

f.e.:
https://stackoverflow.com/questions/57627368/how-to-use-refreshindicator-without-scroll-widget
https://stackoverflow.com/questions/50195259/refresh-indicator-without-scrollview
Repository: neovim
Issue: Repeat signs across wrapped lines
Labels: enhancement,core,column

Im writing a plugin to work with Github issues. Since Im writing all issue comments in the same buffer, I wanted to highlight each individual comment by adding some signs to the sign column:

<img width="1344" alt="image" src="https://user-images.githubusercontent.com/125701/92417446-775e9e00-f162-11ea-9fc1-ff57d01879cb.png">

As you can see in the screenshot, the last two comments are shown correctly, but the first one is not. The `│` character is not repeated for all the "virtual" lines shown when wrapped lines are used.

It would be desirable to add an option to `sign_place` to specify that a sign should be repeated or not across wrapped lines. This should be applicable on a sign by sign basis. For example, in the case of the `└` sign, we don't want to repeat it.

Thanks!
Repository: electron
Issue: Window snapping on Windows does not persist the window position/size after hide/show
Labels: platform/windows,bug :beetle:,9-x-y

### Preflight Checklist

* [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:** `9.3.x`
* **Operating System:** Windows 10 & Windows 7
* **Last Known Working Electron version:** Never to my knowledge

### Expected Behavior
Hiding/showing a window that's snapped to a screen edge should not affect the window's position/size.

### Actual Behavior
Showing a window after hiding restores the window position/size to the settings from prior to the window snapping.

### To Reproduce
[Repro fiddle](https://gist.github.com/acfe60ab445096e2f869b3d3617da897)
Repository: TypeScript
Issue: Extract to constant refactor does not preserve type of context-sensitive function calls
Labels: Bug,Domain: Refactorings

<!-- 🚨 STOP 🚨 STOP 🚨 STOP 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Even if you think you've found a *bug*, please read the FAQ first, especially the Common "Bugs" That Aren't Bugs section!

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ

Please fill in the *entire* template below.
-->

<!--
Please try to reproduce the issue with the latest published version. It may have already been fixed.
For npm: `typescript@next`
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly
-->
**TypeScript Version:** 4.1.0-dev.20200907

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:** isContextSensitive

**Code**

```ts
declare function foo<T = number>(): T;
const result: string = foo();
```

Apply "Extract to constant in enclosing scope" refactor on `foo()` expression

**Expected behavior:**

```ts
const newLocal: string = foo();
const result: string = newLocal;
```

**Actual behavior:**

```ts
const newLocal = foo();
const result: string = newLocal;
```

It doesn't seem to be intentional [based on this code](https://github.com/microsoft/TypeScript/blob/master/src/services/refactors/extractSymbol.ts#L1098-L1100), and it works in this example:

```ts
const result: { x: (x: string) => string } = { x: (x) => x };
```

```ts
const newLocal: { x: (x: string) => string; } = { x: (x) => x };
const result: { x: (x: string) => string } = newLocal;
```

**Playground Link:** https://www.typescriptlang.org/play?ts=4.1.0-dev.20200907#code/CYUwxgNghgTiAEAzArgOzAFwJYHtVJxwB4AVeAXnlWQFsAjEGAPgAoBKALnhIG4AoMHgDOGeHCHIIGLiJhZUAcwoEc7HkA

**Related Issues:** <!-- Did you find other bugs that looked similar? -->
Repository: pytorch
Issue: Request: Add PyTorch version to state dicts
Labels: module: serialization,triaged,enhancement

## 🚀 Feature
Embed a minimal metadata such as the current version of Pytorch by which the model is saved into the saved model.

## Motivation
Now that we see lots of breaking changes going from one version to the next, its best to at the very least have some metadata saved into the models themselves, so they can be used to determine the next proper set of actions. for example, if I'm trying to load a model saved in 1.5, in pytorch 1.6, and something goes wrong! these meta datacan be used and displayed in the generated error message. or I myself can use that metadata to know how to deal with what! 
Without these kinds of meta-data, it can become really tedious and at times mind bugling to find out the underlying cause of the issue! and this can save a huge amount of time not going to waste to ultimately find out something that could be easily known in seconds!

## Pitch

When saving a model, add the current version of Pytorch (and possibly torchvision) as a metadata to the model itself. 

## Alternatives

Nothing that I know of atm!

## Additional context

<!-- Add any other context or screenshots about the feature request here. -->


cc @mruberry
Repository: go
Issue: testing: document rules for using TB
Labels: Documentation,help wanted,NeedsInvestigation

There's rules about what a `TestFoo` may do with the `*testing.T` it is given. Some are documented (e.g. https://golang.org/pkg/testing/#T puts restrictions on invoking `Fatalf` and friends), but some are not (e.g. `Logf` and probably most other methods should not be called after `TestFoo` returns). Same applies to `*testing.B` and any future such values/types.

I came across this while trying to diagnose a problem that seems to be due to #40908, but realised I couldn't find the rules written down anywhere.
Repository: godot
Issue: EditorInspector signal object_id_selected(id: int) is never called
Labels: bug,topic:editor,topic:plugin

<!-- Please search existing issues for potential duplicates before filing yours:
https://github.com/godotengine/godot/issues?q=is%3Aissue
-->

**Godot version:** 3.2.2 stable
<!-- Specify commit hash if using non-official build. -->


**OS/device including version:** linux mint 20
<!-- Specify GPU model, drivers, and the backend (GLES2, GLES3, Vulkan) if graphics-related. -->


**Issue description:** after connecting the signal, it never calling object_id_selected(id). The documentation in says it will calling the function if user is selecting any object in remote inspector tree but no luck.
<!-- What happened, and what was expected. -->


**Steps to reproduce:**

1. run the project
2. select Node2D from remote inspector
3. expect some number to print in debugger but nothing printed

**Minimal reproduction project:**
[bug.zip](https://github.com/godotengine/godot/files/5187880/bug.zip)

<!-- A small Godot project which reproduces the issue. Drag and drop a zip archive to upload it. -->
Repository: TypeScript
Issue: Disable type checking for node_modules entirely
Labels: Suggestion,Awaiting More Feedback

## Search Terms

skipLibCheck
node_modules
ignore library
exclude

## Suggestion

Either a new option or the existing option `skipLibCheck` should be able to disable type checking for node_modules.

## Use Cases

A library author might have a faulty import or might only provide typescript files for his library and not transpiled code. As a user of this library I want to be able to disable type checking for a library (or all) because I trust this library has been tested enough in other ways. 

Another issue where I found a library shipping ts files and causing errors for the user: https://github.com/microsoft/TypeScript/issues/15363

The response at the end is very relevant


> I understand that libraries **shouldn't** publish `*.ts` files, but sometimes, they just **do**, and we can't control every other library easily.
> I think typescript should not try to apply this kind of setting (here `noImplicitAny`) to the `node_modules` simply because it is meant to be applied to the user code being compiled, not the external dependencies.

_Originally posted by @victornoel in https://github.com/microsoft/TypeScript/issues/15363#issuecomment-309459043_

## Examples

I had the case that a library came with a `dist/` folder and almost all types were perfectly arranged in .d.ts files. But one file was making an import from `../index.d.ts`(which seems to be for development purposes, the lib main file is `dist/index.d.ts`) which in turn then imported `src/ClassA.ts`

The library author used a different tsconfig and didn't use strict type checking, but I do and that's why the type check fails for me, because now the typescript source files of the library author are type checked.

## Checklist

My suggestion meets these guidelines (in case of a new option):

* [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
* [x] This wouldn't change the runtime behavior of existing JavaScript code
* [x] This could be implemented without emitting different JS based on the types of the expressions
* [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).
Repository: storybook
Issue: Cannot consistently decorate story source
Labels: feature request,addon: storysource

**Describe the bug**

I'm trying to write a simple set of HTML stories in with Storybook Vue. Since I need to add backticks to the templates of each story, the "Story" source panel will parse the code snippet with those backticks, which is undesired (and invalidates highlighting). I figured I could easily remove those backticks from the source, but I've found no consistent way of doing this outside of the docs addon.

I've tried using a custom decorator, but however I modify the story, the source panel is still using the original, undecorated source.

This is the story in the MDX file:

```jsx
<Canvas>
    <Story name="Group">{`
<div class="btnGroup">
    <button type="button" class="btn btn--primary">
    Confirm
    </button>
    <button type="button" class="btn btn--secondaryAlt">
        Cancel
    </button>
</div>
    `}</Story>
</Canvas>
```
This is the resulting source panel:

<img width="467" alt="Screenshot 2020-09-08 at 06 45 47" src="https://user-images.githubusercontent.com/330375/92437704-6a13d480-f19f-11ea-918c-ec9c2199e7fb.png">

**Expected behavior**

I want source snippets trimmed of backticks. I would've expected the content of the "Story" source panel to allow decorators to modify its content. Alternatively, a `tranformSource` filter would be preferable (and perhaps more consistent with other parts of Storybook).

**Code snippets**

This works like a charm, but it's only applicable to Docs pages:

```js
// .storybook/preview.js

export const parameters = {
    docs: {
        transformSource (source, storyId) {
            return source.replace(/^\s*`\s*((.|\s)*)\s*`\s*$/gm, '$1')
        }
    }
}
```

I've tried using a global decorator, to no avail. It runs every time the story is rendered, sure, but the source panel doesn't respect any transformations:

```js
// .storybook/preview.js

export const decorators = [
    makeDecorator({
        // ...
        wrapper: (storyFn, context, { parameters }) => {
            context.parameters.storySource.source = context.parameters.storySource.source
                .replace(/^\s*`\s*((.|\s)*)\s*`\s*$/gm, '$1')

            return storyFn(context);
        }
    })
]
```

Strangely, the decorator will take effect on reload for the first-rendered story. Subsequent stories' sources are not decorated when focused.

<details>
    <summary>Video of behavior</summary>

![Kapture 2020-09-08 at 07 09 18](https://user-images.githubusercontent.com/330375/92439319-7ea59c00-f1a2-11ea-94a2-e42fe071ad30.gif)

</details>