sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: youtube-dl
Issue: Download segments of Youtube Dash or HLS format in parallel
Labels: question

<!--

######################################################################
  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:
- Look through the README (http://yt-dl.org/readme) and FAQ (http://yt-dl.org/faq) for similar questions
- Search the bugtracker for similar questions: http://yt-dl.org/search-issues
- Finally, put x into all relevant boxes (like this [x])
-->

- [x ] I'm asking a question
- [ x] I've looked through the README and FAQ for similar questions
- [ ] I've searched the bugtracker for similar questions including closed ones


## Question

<!--
Ask your question in an arbitrary form. Please make sure it's worded well enough to be understood, see https://github.com/ytdl-org/youtube-dl#is-the-description-of-the-issue-itself-sufficient.
-->

youtube-dl downloads DASH or m3u8 format very slow. Download speed is about 500 kbps, and download speed of other MP4 formats are about 20 Mbps on my computer. Can youtube-dl download segments in parallel. If youtube-dl doesn't support this feature, which method should I use to implement this feature:

- Write a new downloader
- Only use youtube-dl to get list of format info. Use nodejs + ffmpeg to download segments and merge into mp4 video.
Repository: svelte
Issue: Preprocessing tries to process style string within script section
Labels: feature request,awaiting submitter,stale-bot

**Describe the bug**
I have a component which generates a small bit of HTML which is injected into an `iframe`. The HTML contains a `style` section which the preprocessing tries to transform, yielding a parser error because there are interpolated values in it.

(Accidentally opened this issue in `svelte-preprocess` first: https://github.com/sveltejs/svelte-preprocess/issues/225
The problem is in the [wrapper code][code-ref] though.)

**To Reproduce**

A component like this will cause the error:

```svelte
<script>
	function getItemHtml(html)
	{
		const style = window.getComputedStyle(document.documentElement);

		const background = style.getPropertyValue('--background');
		const foreground = style.getPropertyValue('--foreground');

		return html + /*html*/`<style>
			html
			{
				background: ${background};
				color: ${foreground};
			}
		</style>`;
	}
</script>

<style>
	:global(:root)
	{
		--background: #333;
		--foreground: #ddd;
	}
</style>

<div>
	HTML:
	<pre>
		{getItemHtml('Hello World')}
	</pre>
</div>
```

[[Repository with Webpack config]](https://github.com/brunnerh/svelte-style-in-script-issue)

**Expected behavior**
No attempted transform and thus no errors.

**Stacktraces**
<details>
  <summary>Stack trace</summary>

```
ERROR in ./src/app.svelte
Module build failed (from ./node_modules/svelte-loader/index.js):
CssSyntaxError: .\src\app.svelte:4:19: Unknown word
    at Input.error (.\node_modules\postcss\lib\input.js:130:16)        
    at Parser.unknownWord (.\node_modules\postcss\lib\parser.js:563:22)
    at Parser.other (.\node_modules\postcss\lib\parser.js:168:12)      
    at Parser.parse (.\node_modules\postcss\lib\parser.js:77:16)       
    at parse (.\node_modules\postcss\lib\parse.js:17:12)
    at new LazyResult (.\node_modules\postcss\lib\lazy-result.js:60:16)
    at Processor.<anonymous> (.\node_modules\postcss\lib\processor.js:138:12)
    at Processor.process (.\node_modules\postcss\lib\processor.js:117:23)
    at transformer (.\node_modules\svelte-preprocess\dist\transformers\globalStyle.js:55:67)
    at Object.exports.runTransformer (.\node_modules\svelte-preprocess\dist\autoProcess.js:51:12)
    at async style (.\node_modules\svelte-preprocess\dist\autoProcess.js:171:33)
    at async .\node_modules\svelte\compiler.js:27016:32
    at async Promise.all (index 0)
    at async replace_async (.\node_modules\svelte\compiler.js:26971:52)
    at async preprocess (.\node_modules\svelte\compiler.js:27012:19)
 @ ./src/main.js 1:0-31 3:4-7
 @ multi ./src/main.js
```

</details>

**Information about your project:**

- Your browser and the version: -
- Your operating system: Windows 10 64bit
- `svelte` version: 3.24.1
- Webpack

**Severity**

Low; workarounds exist.

**Workaround**

Trick the Regex looking for `<style>`, e.g.:
```js
return html + /*html*/`<${''}style>...</${''}style>`
```

[code-ref]: https://github.com/sveltejs/svelte/blob/master/src/compiler/preprocess/index.ts#L117
Repository: go
Issue: x/pkgsite: establish guidelines for feature development for pkgsite
Labels: Documentation,NeedsInvestigation,pkgsite

Following up on https://github.com/golang/go/issues/40612#issuecomment-676587998, the pkgsite team is working on processes to give users time to give feedback on large feature changes, before these features are live in production. These processes include:

- [x] Creating [milestones](https://github.com/golang/go/milestones) for pkgsite
   - [x] Correlate these milestones with the [x/pkgsite Roadmap](https://github.com/golang/pkgsite#roadmap)
- [x] Allowing users to opt-in to experiments before they are fully rollout: https://github.com/golang/go/issues/40905
- [x] Publishing documentation on expectations for feature development with x/pkgsite, in addition to the [CONTRIBUTING.md](https://github.com/golang/pkgsite/blob/master/CONTRIBUTING.md)
Repository: material-ui
Issue: [core] Use hard tabs in the source for accessibility
Labels: accessibility,core

<!-- Provide a general summary of the feature in the Title above -->

<!--
  Thank you very much for contributing to Material-UI by creating an issue! ❤️
  To avoid duplicate issues we ask you to check off the following list.
-->

<!-- Checked checkbox should look like this: [x] -->

- [x] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.

## Summary 💡

Hard tabs allow contributors to choose how many spaces a tab represents, which aids accessibility.

Discussion:
https://github.com/romefrontend/rome/issues/425

<!-- Describe how it should work. -->

## Examples 🌈
https://github.com/romefrontend/rome

<!--
  Provide a link to the Material design specification, other implementations,
  or screenshots of the expected behavior.
-->

## Motivation 🔦

Material-UI as a user interface component library has a strong accessibility ethic. This should extend to contributor DX.
Repository: pytorch
Issue: Cannot find CUDA devices when the machine stays idle for a while
Labels: module: cuda,triaged

From this discussion: https://discuss.pytorch.org/t/pytorch-suddenyl-stops-recognising-gpu/93384

> I am using PyTorch through Anaconda Environment and something weird happens. While working or if I leave the machine for some time and come back, PyTorch stops recognizing the GPU. And the only way it starts recognizing the GPU is after rebooting the machine.

```
THCudaCheck FAIL file=/opt/conda/conda-bld/pytorch_1591914886554/work/aten/src/THC/THCGeneral.cpp line=47 error=999 : unknown error
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/user/anaconda3/envs/work/lib/python3.8/site-packages/torch/cuda/__init__.py", line 330, in current_device
    _lazy_init()
  File "/home/user/anaconda3/envs/work/lib/python3.8/site-packages/torch/cuda/__init__.py", line 153, in _lazy_init
    torch._C._cuda_init()
RuntimeError: cuda runtime error (999) : unknown error at /opt/conda/conda-bld/pytorch_1591914886554/work/aten/src/THC/THCGeneral.cpp:47
```

The user confirmed that `nvidia-smi` works fine though and the following command can fix the problem. 

```
$ sudo rmmod nvidia_uvm
$ sudo modprobe nvidia_uvm
```

cc @ngimel
Repository: godot
Issue: GLTF Importer fails to import if compression is off
Labels: bug,topic:rendering

<!-- Please search existing issues for potential duplicates before filing yours:
https://github.com/godotengine/godot/issues?q=is%3Aissue
-->

**Godot version:**
844251596fb6ceaaeef521611ea32e138b1adc3b


**OS/device including version:**
pop OS, 1080ti


**Issue description:**
When trying to reimport the model with 'Compress' unchecked the model disappears and this error shows up in console:
ERROR: Size of data provided (192816) does not match expected (203528)


**Steps to reproduce:**
1. Open an empty project
2. Import attached model:
https://mega.nz/file/qc11CJII#zL8LjZSjnwY_4uf8o170JjBS5Q6pilNTLMXQZU9bjzQ
3. Uncheck 'Compress' in import settings and reimport the model.
Repository: storybook
Issue: Component-level css not loading into stories
Labels: question / support,react,cra

I created a react app using create-react-app, and added a button component, a css for the button. When I load the story for the button, the styles are not loaded for the button. Pasting below, the related files. Is there any configuration that I am to do, to get this up and running with styles?

[github repo for the project](https://github.com/akhiltheguitarist/StoryBook/tree/master/storybookapp) 

Component: index.js

```
 import React, { Component } from 'react';
import styles from './style.css';
class CustomButton extends Component{
    render(){
        return (
            <button className={styles.customButton}>Hello</button>     
        );
    }
}
export default CustomButton;
```

style.css:
```
.customButton {
    border: 1px solid red;
    padding: 10px;
    background-color: rgb(223, 19, 19);
}
```

Story file:
```
import React from 'react';
import CustomButton from '../../src/index';
import { storiesOf } from '@storybook/react';


const story = storiesOf("Custom button",module);

story.addWithJSX("simple",() => <CustomButton/>);
```

System info:
```
Environment Info:

  System:
    OS: Windows 7 6.1.7601
    CPU: (2) x64 Intel(R) Core(TM) i3-2370M CPU @ 2.40GHz
  Binaries:
    Node: 10.16.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.4 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
    npm: 6.9.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 84.0.4147.125
  npmPackages:
    @storybook/addon-info: ^5.3.19 => 5.3.19
    @storybook/components: ^5.3.19 => 5.3.19
    @storybook/preset-create-react-app: ^3.1.4 => 3.1.4
    @storybook/react: ^5.3.19 => 5.3.19
```
Repository: storybook
Issue: Canvas crashes with ForwardRef's error when selecting component from controls select dropdown
Labels: feature request,has workaround,addon: controls

**Describe the bug**

Storybook's Canvas is crashing with ForwardRef errors when switching between dropdown controls, where the value is a React component.  A valid use case being Material-UI Button's endIcon /startIcon props.

The initial render using the provided prop `endIcon={<div>initial</div>}` is rendering correctly.  The error only occurs when a new selection is made in the dropdown.

Interestingly the issue only presents itself on the Storybook's Canvas component, the same story works when when toggled in the Docs addon; so it seem to be related to the storybook Canvas.



**To Reproduce**

1. Using Storybook 6 for React with Controls addon 
2. Create a story and configure a ReactNode based prop to handle a select dropdown control, where the value is a Component
2. Select an option of the dropdown and you'll see the following error.

**Expected behavior**

The component updates to represent the change in prop and doesn't crash.

**Screenshots**

<img width="814" alt="Screenshot 2020-08-19 at 21 01 19" src="https://user-images.githubusercontent.com/67582072/90684016-5e4b8700-e25f-11ea-9184-e21c2e8c790e.png">


**Code snippets**

```
import React from "react";
import { Story, Meta } from "@storybook/react/types-6-0";
import { Button, ButtonProps } from "@material-ui/core/Button";

export default {
  title: "Inputs/Button",
  component: Button,
  argTypes: {
    endIcon: {
      control: {
        options: { Alpha: <div>alphra</div>, Beta: <div>beta</div> },
      },
    },
  },
} as Meta;

const Template: Story<ButtonProps> = (args) => {
  return (
    <Button {...args} />
  );
};

const baseArgs: Partial<ButtonProps> = {
  children: "Button",
  variant: "contained",
};

export const Index = Template.bind({});
Index.args = {
  ...baseArgs,
  color: "default",
  endIcon: <div>initial</div>,
};

```

**System:**
`npx sb@next info` not working for me, but I'm using the following:

```
    "@react-theming/storybook-addon": "^1.0.3",
    "@storybook/addon-actions": "^6.0.13",
    "@storybook/addon-essentials": "^6.0.13",
    "@storybook/addon-links": "^6.0.13",
    "@storybook/addon-storysource": "^6.0.13",
    "@storybook/addon-viewport": "^6.0.13",
    "@storybook/node-logger": "^6.0.13",
    "@storybook/react": "^6.0.13",
```

**Additional context**
Add any other context about the problem here.
Repository: vscode
Issue: Add ability to apply custom icon to Custom Editors
Labels: help wanted,feature-request,api,custom-editors

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
With webviews, we can add icons we like to the webview with webviewPanel.iconPath but when this is applied to the Custom Text Editor's webview panel, nothing is displayed.

Create a method to apply a custom icon to Custom Text Editors without having to provide an entire Icon Theme. Ideally this would override ONLY the Custom Editor associated to that viewType, which would allow us to differentiate open text editors vs Custom Editors viewing the same file by icon.
Repository: TypeScript
Issue: TypedPropertyDescriptorMap<T>
Labels: Suggestion,Awaiting More Feedback

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker.

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ, especially the "Common Feature Requests" section: https://github.com/Microsoft/TypeScript/wiki/FAQ

-->

## Search Terms

<!-- List of keywords you searched for before creating this issue. Write them down here so that others can find this suggestion more easily -->

TypedPropertyDescriptor
TypedPropertyDescriptorMap
Typed Property Descriptor Map

## Suggestion

<!-- A summary of what you'd like to see added or changed -->
Include `TypedPropertyDescriptorMap<T>`, the typed version of `PropertyDescriptorMap`. The following type should do the trick:

```ts
type TypedPropertyDescriptorMap<T> = {
  [P in keyof T]: TypedPropertyDescriptor<T[P]>
}
```

This would require a change to the Object.defineProperties type definition since it only accepts a PropertyDescriptorMap type, an indexed type. Passing in an object with a type of `TypedPropertyDescriptorMap<T>` results in the error: `Index signature is missing in type 'TypedPropertyDescriptorMap<T>'`. There's a related issue on this topic (https://github.com/Microsoft/TypeScript/issues/15300).

## Use Cases

<!--
What do you want to use this for?
What shortcomings exist with current approaches?
-->

It's a headache to have to define a type like the following when I already have defined the final object type:
```ts
// Final object looks like
interface MyProps {
  prop1: string
  prop2: (params: Record<string, string>) => Promise<void>
}

// My custom TypedPropertyDescriptor map
interface MyPropDescriptors {
  prop1: TypedPropertyDescriptor<MyProps['prop1']>
  prop2: TypedPropertyDescriptor<MyProps['prop2']>
  ...
}
```

## Examples

<!-- Show how this would be used and what the behavior would be -->

```ts
// Final object looks like
interface MyProps {
  prop1: string
  prop2: (params: Record<string, string>) => Promise<void>
}

// My custom TypedPropertyDescriptor map
type MyPropDescriptors = TypedPropertyDescriptorMap<MyProps>
```

## Checklist

My suggestion meets these guidelines:

* [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: TypeScript
Issue: Intellisense doesn't find variable in tsconfig's "paths" directory in parent folder
Labels: Needs Investigation

*TS Template added by @mjbvz*

**TypeScript Version**: 4.1.0-dev.20200818

**Search Terms**
- tsconfig
- auto import

---

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->
<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: https://code.visualstudio.com/insiders/ -->

<!-- Use Help > Report Issue to prefill these. -->
- VSCode Version: Insiders
- OS Version: macOS 10.15.6

Steps to Reproduce:

1. Clone this repo: https://github.com/Floriferous/paths-resolution
2. Try to use intellisense to import `someVar` in the `test.js` file
3. Notice that it does not work, even though `paths` is properly declared in `tsconfig.json`
 

<!-- Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes
Repository: go
Issue: proposal: sync: add WaitContext to WaitGroup
Labels: Proposal

#### background
Some times when using a `sync.WaitGroup`, I want to bound the whole action with a timeout.

I thought this had been called out in #39863 or some [other issue](https://github.com/golang/go/issues?q=is%3Aissue+sync.waitgroup+context.Context+), but I could not find anything.

#### description
We should be able to add a context aware wait method:
```go
package sync

func (wg *WaitGroup) WaitContext(ctx context.Context) {
	ctx, cancel := context.WithCancel(ctx)
	go func() { wg.Wait(); cancel() }()
	<-ctx.Done()
}
```

#### costs
It may be weird to have the callers of `sync.WaitGroup.Done` untethered, since `sync.WaitGroup.WaitContext` can return early, but if you want to add a watchdog thread it can still use `sync.WaitGroup.Wait` since there are no changes to that implementation. That being said, it does add complexity.

#### alternatives
Since this method somewhat consumes the `context.Context` callers may prefer that `context.Context.Err` be returned. Unfortunately, this mixes the intentions, since the same error is available to the caller, but is not a painful implementation:
```go
func (wg *WaitGroup) WaitContext(ctx context.Context) error {
	ctx1, cancel := context.WithCancel(ctx)
	go func() { wg.Wait(); cancel() }()
	<-ctx1.Done()
	return ctx.Err()
}
```

If we instead wanted to embed the `context.Context` into the `struct` directly, so that `sync.WaitGroup.Wait` used it implicitly, we could either add a public field, or a private field with a setter. I assume we would want the latter since that is what was done for `http.Request`. Continuing on, we may want to expose the `error` that the embedded `context.Context has, requiring a `func (wg *WaitGroup) Err() error` method. Unfortunately, all of this is pretty complex, and would require reworking several extant method implementations, and did not seem worth the cost.
Repository: flutter
Issue: clang-format incorrectly orders primary header in unit tests
Labels: team,engine,P2,team-engine,triaged-engine

Recently, when clang-formatting `*_unittests.cc` files in the engine, it's moving the primary header (i.e., the header for the class/file under test) down with all the other headers instead of leaving it first. I believe this is a regression, but I'm not 100% certain.

See https://github.com/flutter/engine/pull/20651 for an example.

We should figure out why and fix it, because the style guide is explicit that tests should have the primary header first.
Repository: godot
Issue: SoftBody shoots from point zero [GLES2]
Labels: bug,confirmed,topic:physics

<!-- Please search existing issues for potential duplicates before filing yours:
https://github.com/godotengine/godot/issues?q=is%3Aissue
-->

**Godot version:**
<!-- Specify commit hash if using non-official build. -->
Godot 3.2.3.rc (a6ef6b10b2)


**OS/device including version:**
<!-- Specify GPU model, drivers, and the backend (GLES2, GLES3, Vulkan) if graphics-related. -->
MacOSX 10.15.5 (19F101)

**Issue description:**
<!-- What happened, and what was expected. -->
I have several instances of scene with SoftBody inside. When scene starts SoftBodies jumps from 0,0,0 point so they have huge inertia in this direction and dangle around several frames.

![Снимок экрана 2020-08-20 в 10 40 59](https://user-images.githubusercontent.com/1177068/90731303-35180e80-e2d2-11ea-9240-873e02f5b693.png)

The screenshot shows flags from blue boat and from another one boat which is in left side out the screen.

The video of first few seconds of this scene:

[Запись экрана 2020-08-20 в 10.39.10.zip](https://github.com/godotengine/godot/files/5101451/2020-08-20.10.39.10.zip)


**Steps to reproduce:**

Make the scene with SoftBodies which are placed not in zero point. Run project on GLES2.

**Minimal reproduction project:**
<!-- A small Godot project which reproduces the issue. Drag and drop a zip archive to upload it. -->
Repository: pytorch
Issue: Set SummaryWriter step globally
Labels: oncall: visualization

## 🚀 Feature

Ability to set the step in `SummaryWriter` globally.

## Motivation

If you write a bunch of logs, passing in the steps to each is verbose:

```py
writer = SummaryWriter(f"/runs/{datetime.now():%m.%d-%H:%M:%S}")

for batch, (samples, labels) in enumerate(loader):
    # ...
    writer.add_scalar("KL_div", kl_div, batch)
    writer.add_scalar("ELBO", elbo, batch)

    writer.add_scalar("train_acc", train_acc, batch)
    writer.add_scalar("val_acc", train_acc, batch)
```

vs

```py
writer = SummaryWriter(f"/runs/{datetime.now():%m.%d-%H:%M:%S}")

for batch, (samples, labels) in enumerate(loader):
    # ...
    writer.set_step(batch)
    writer.add_scalar("KL_div", kl_div)
    writer.add_scalar("ELBO", elbo)

    writer.add_scalar("train_acc", train_acc)
    writer.add_scalar("val_acc", train_acc)
```

## Alternatives

[`writer. add_scalars`](https://pytorch.org/docs/stable/tensorboard.html#torch.utils.tensorboard.writer.SummaryWriter.add_scalars) helps in cases when the scalars are related and can be collected at a single call site but more often than not I find one of those not to apply.

## Pitch

There's already an experimental implementation in TensorFlow: [`tf.summary.experimental.set_step
`](https://www.tensorflow.org/api_docs/python/tf/summary/experimental/set_step).