sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: #[rustc_allocator] documentation disagrees with implementation
Labels: A-allocators,T-compiler,A-docs,C-bug

The documentation of `#[rustc_allocator]` seems to disagree with its implementation.

The documentation says it applies a returns-nonnull hint. The implementation instead only applies a returns-noalias hint.

```rust
    // compiler/rustc_middle/src/middle/codegen_fn_attrs.rs:49
    /// `#[rustc_allocator]`: a hint to LLVM that the pointer returned from this
    /// function is never null.
    const ALLOCATOR                 = 1 << 1;
```

```rust
    // compiler/rustc_codegen_llvm/src/attributes.rs:304
    if codegen_fn_attrs.flags.contains(CodegenFnAttrFlags::ALLOCATOR) {
        Attribute::NoAlias.apply_llfn(llvm::AttributePlace::ReturnValue, llfn);
    }
```
Repository: storybook
Issue: Addon background light / dark doesn't work in Docs when using MDX
Labels: bug,help wanted,addon: backgrounds,mdx

**Describe the bug**
With 6.1.8 addon background doesn't work when using Docs + MDX. It does work with DocsPage but doesn't work when using MDX. With MDX the background color only switch when shifting to Canvas then back to Docs.

Example of a story definition in MDX that doesn't work:

```
<Canvas>
    <Story name="default">
        <Button>Cutoff</Button>
    </Story>
</Canvas>
```

Video that show the problem:

![background_addon](https://user-images.githubusercontent.com/794579/100493215-01375b00-3103-11eb-9f44-f93833318c88.gif)

**To Reproduce**
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

**Expected behavior**
A clear and concise description of what you expected to happen.

**Screenshots**
If applicable, add screenshots to help explain your problem.

**Code snippets**
If applicable, add code samples to help explain your problem.

**System**
Please paste the results of `npx sb@next info` here.

**Additional context**
Add any other context about the problem here.
Repository: pytorch
Issue: CARU: A Content-Adaptive Recurrent Unit for the Transition of Hidden State in NLP
Labels: feature,module: nn,module: rnn,triaged


[Chan2020_Chapter_CARUAContent-AdaptiveRecurrent.pdf](https://github.com/pytorch/pytorch/files/5611531/Chan2020_Chapter_CARUAContent-AdaptiveRecurrent.pdf)
## 🚀 Feature
An advanced RNN unit introduced by article:
https://link.springer.com/chapter/10.1007%2F978-3-030-63830-6_58

## Motivation
There is the experiment result and pytorch code for reference:
https://github.com/ChanKaHou/CARU

## Pitch
Please add this CARU unit as a component (like torch.nn.CARU) in this great engine.
CARU requires the same resources as GRU, but the performance is better than other recurrent unit.


cc @albanD @mruberry @zou3519
Repository: PowerToys
Issue: [KBM] Block "Win" shortcuts "system behavior" while not disabling the shortcuts
Labels: Idea-Enhancement,Product-Keyboard Shortcut Manager

## 📝 Provide a description of the new feature

Current Keyboard Shortcut Manager can only disable the shortcuts.
For example, I can not add "win+d" as "delete line" in VSCode, because that is the system shortcut for "display desktop". However, I can still not add it if I disable "win+d" in Keyboard Shortcut Manager, because the shortcut itself is disabled and VSCode can not use it either.

So can we only block the "system behavior" for "Win" shortcuts, while allowing the applications to still use them?  

---

If you'd like to see this feature implemented, add a 👍 reaction to this post.
Repository: rust
Issue: Stability annotation on defaulted generics fails
Labels: A-allocators,A-stability,T-compiler,C-bug

I'm adding `<A: AllocRef = Global>` to string types. Strings don't have a generic parameter, so the defaulted generic parameter is the first parameter:

```rust
pub struct String<#[unstable(feature = "allocator_api", issue = "32838")] A: AllocRef = Global> {}
```

However, the compiler complains, that this annotation is "useless":

```text
error: This stability annotation is useless
   --> library/alloc/src/string.rs:280:75
    |
280 | pub struct String<#[unstable(feature = "allocator_api", issue = "32838")] A: AllocRef = Global> {
    |                                                                           ^
```

Was this simply not added by #77118 or is this a false positive in general?

cc @varkor @Avi-D-coder
Repository: flutter
Issue: Unable to add pull to refresh functionality to the webview_flutter 
Labels: p: webview,package,team-ecosystem,has reproducible steps,P3,found in release: 2.2,found in release: 2.5,triaged-ecosystem

I have been trying to implement pull to refresh functionality to the web view by having it as a child for RefreshIndicator, but  couldn't accomplish this. Below is the code snippet. Please provide your suggestions.


```dart
Widget _buildWebViewWidget() {
    return WebView(
      initialUrl: 'https://flutter.dev',
      javascriptMode: JavascriptMode.unrestricted,
      debuggingEnabled: true,
      onWebViewCreated: (WebViewController webViewController) {
        _controller.complete(webViewController);
      },
      onPageStarted: (String result) {
        print('onPageStarted ' + result);
        setState(() {
          _isLoading = true;
        });
      },
      onWebResourceError: (WebResourceError webviewerrr) {
        print('-----' + webviewerrr.description);
        if (webviewerrr.description.contains('ERR_NAME_NOT_RESOLVED') ||
            webviewerrr.errorCode == -1009) {
          // net::ERR_NAME_NOT_RESOLVED
          setState(() {
            _hasWebViewErrorOccured = true;
          });
        }
      },
      onPageFinished: (String result) async {
        print('onPageFinished ' + result);

        setState(() {
          _isLoading = false;
        });
      },
    );
  }
```
This is how the _buildwebviewwidget is used inside RefreshInidicator.
```dart
  RefreshIndicator(
            child: _buildWebViewWidget(),
            onRefresh: () async {
              return await Future.delayed(Duration(seconds: 3));
            },
          );
```
Repository: youtube-dl
Issue:  trouble should have an option to log all failed downloads to a file
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.11.26. 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.11.26**
- [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.
-->
the trouble function of YoutubeDL.py should provide an option to log failed downloads to a file (using the same format that --download-archive uses), so that after review those files can be added to the --download-archive file in order to skip them in the future. Right now youtube-dl will retry failed downloads every time its re-run. (Ive seen a couple youtube channels with broken videos, which is what prompted this)
Repository: flutter
Issue: setState called when widget is not mounted on MultiFrameImage emitter
Labels: c: regression,c: crash,framework,a: images,customer: money (g3),a: null-safety,P2,team-framework,triaged-framework

Internal: b/174211205

customer:money is rarely seeing this crash (14 times within 4 weeks):

```
Thread 0 main thread_CastError: Null check operator used on a null value
at State.setState(framework.dart:1289)
at _ImageState._handleImageFrame(image.dart:1188)
at ImageStreamCompleter.setImage(image_stream.dart:616)
at MultiFrameImageStreamCompleter._emitFrame(image_stream.dart:946)
at MultiFrameImageStreamCompleter._decodeNextFrameAndSchedule(image_stream.dart:925)
at <asynchronous gap>(async)
```

Seems like there's a race between image frames being emitted and the widget being disposed.
Repository: rust
Issue: assert!(bool, bool) should probably trigger a lint
Labels: C-enhancement,T-libs-api

I just noticed this line in some code ported from JavaScript. The `rows.len() == 1` is ignored, without any warning from rustc or clippy. A bit surprising; perhaps this should be linted?

```rust
assert!(range.len() == 0, rows.len() == 1);
```
Repository: rust
Issue: Tracking Issue for `Iterator::intersperse`
Labels: T-libs-api,C-tracking-issue,A-iterators,disposition-merge,finished-final-comment-period,Libs-Tracked

This is a tracking issue for the `Iterator::intersperse` and `intersperse_with` methods. It is based on `itertools::intersperse` and is the iterator equivalent of `Vec::join`.

The feature gate for the issue is `#![feature(iter_intersperse)]`.

### Public API

```rust
// core::iter

pub trait Iterator {
    fn intersperse(self, separator: Self::Item) -> Intersperse<Self>
    where
        Self: Sized,
        Self::Item: Clone;

    fn intersperse_with<G>(self, separator: G) -> IntersperseWith<Self, G>
    where
        Self: Sized,
        G: FnMut() -> Self::Item;
}

#[derive(Debug, Clone)]
pub struct Intersperse<I: Iterator> where I::Item: Clone {}

impl<I> Iterator for Intersperse<I> where I: Iterator, I::Item: Clone {
    type Item = I::Item;
}

pub struct IntersperseWith<I, G> where I: Iterator {}

impl<I, G> Debug for IntersperseWith<I, G> where I: Iterator + Debug, I::Item: Debug, G: Debug {}

impl<I, G> Clone for IntersperseWith<I, G> where I: Iterator + Clone, I::Item: Clone, G: Clone {}

impl<I, G> Iterator for IntersperseWith<I, G> where I: Iterator, G: FnMut() -> I::Item {
    type Item = I::Item;
}
```

### Steps / History
<!--
Include each step required to complete the feature. Typically this is a PR
implementing a feature, followed by a PR that stabilises the feature. However
for larger features an implementation could be broken up into multiple PRs.
-->

- [x] Implement `intersperse`: #79479
- [x] Add `intersperse_with`: https://github.com/rust-lang/rust/pull/80567
- [x] FCP
- [x] Stabilization PR: https://github.com/rust-lang/rust/pull/88548
  (UPDATE: stabilization was reverted because there was a lot of breakage: #88967)
- [ ] Determine how to avoid breakage and un-revert
- [ ] Add `impl<I: FusedIterator> FusedIterator for Intersperse<I>`? (Can be added after stabilization, so not urgent.)

### Unresolved Questions
<!--
Include any open questions that need to be answered before the feature can be
stabilised.
-->

None.
Repository: TypeScript
Issue: Support forwarding generic type in extending class
Labels: Suggestion,Awaiting More Feedback

## Search Terms

generic forward extends default 

## Suggestion

Have a shortcut syntax to make the generic of an extending class the same type as its Parent generic.

**Current**
```typescript
class Parent <T extends any = any> {}
class Child <S extends any = any> extends Parent <S> {}
```

**Suggestion**
```typescript
class Parent <T extends any = any> {}
class Child <infer S> extends Parent <S> {}
```

## Use Cases

A default generic is useful to typescript users b

```typescript
interface Proto = {}
class SomeClass <T extends Proto = Proto> {}
```

It can be extended like this:

```typescript
class ExtendedClass extends SomeClass {}
```

but with this the author of `ExtendedClass` robs futher extenders of the possibility to extend the `T` generic of `SomeClass`. To allow further extension the author would need to add following construct.

```typescript
class ExtendedClass <T extends Proto = Proto> extends SomeClass<T> {}
```

This is quite bothersome to the author of `ExtendedClass`. It requires the import of `Proto` and is easy to forget.
To make it a little bit easier I thought it might be a good idea to have this special syntax.


## Examples

```typescript
type Events = {
   open: () => {}
   close: () => {}
}

class System <TEvents extends Events = Events> {
   on <TEvent extends keyof TEvents> (event: TEvent, listener: TEvents[TEvent]): this { return this }
   off <TEvent extends keyof TEvents> (event: TEvent, listener: TEvents[TEvent]): this { return this }
}

class CorpSystem <infer TEvents> extends System <TEvents> {}

type SectionEvents = {
   stall: () => {}
} & Events

class SectionSystem <TEvents extends SectionEvents = SectionEvents> extends CorpSystem<TEvents> {}

const s = new SectionSystem()
s.on('stall', () => {})
```

As probably clear in the example, this thought came up when dealing with Node's `EventEmitter` but I think it can be useful to pretty much any use of extending classes with generics. 

## 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: pytorch
Issue: at::size documentation conflict
Labels: module: docs,module: cpp,triaged

https://pytorch.org/cppdocs/api/function_namespaceat_1afb9ce3e765d84eda74dddc3b64ef3edf.html?highlight=size
The page of cpp function at::size is showing:

WARNING

doxygenfunction: Unable to resolve multiple matches for function “at::size” with arguments (const Tensor&, Dimname) in doxygen xml output for project “PyTorch” from directory: /var/lib/jenkins/workspace/docs/cpp/build/xml. Potential matches:

- int64_t size(const Tensor &self, Dimname dim)
- int64_t size(const Tensor &self, int64_t dim)


cc @yf225 @glaringlee @jlin27 @mruberry
Repository: pytorch
Issue: JIT script has wrong signature for .norm
Labels: oncall: jit,days,TSUsability,TSRootCause:PyTorchParityGap

## 🐛 Bug

```py
@torch.jit.script
def f(x: torch.Tensor):
    return x.norm(dim=1)
```
fails to script on `1.7.0` as JIT complains of missing `p` arg, which should have default value 2.

cc @ezyang @gchanan @zou3519 @bdhirsh @gmagogsfm
Repository: rust
Issue: Padding to ensure a value is well-aligned is not used for niche value optimization
Labels: A-mir-opt,A-layout

```rust
use core::mem::size_of;
use core::num::NonZeroU8;

struct Foo(u8, u16);
struct Bar(u8, u16, NonZeroU8);

fn main() {
    dbg!(size_of::<Foo>());
    dbg!(size_of::<Option<Foo>>());
    dbg!(size_of::<Bar>());
    dbg!(size_of::<Option<Bar>>());
}
```

([Playground](https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=c058daf309213fcbaa0636e46276a7ea))

Output:

```text
[src/main.rs:8] size_of::<Foo>() = 4
[src/main.rs:9] size_of::<Option<Foo>>() = 6
[src/main.rs:10] size_of::<Bar>() = 4
[src/main.rs:11] size_of::<Option<Bar>>() = 4
```

`size_of::<Foo>()` returns 4 as expected. `size_of::<Option<Foo>>()` returns 6, indicating that the unused padding byte is not being used to store the tag for the `Option`. ([playground](https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=5e5ae8c6380712e7888a09a02cb200cb))

However, by _adding a field_ that is `NonZero*`, the compiler is able to take advantage of the unused bit. This, of course, only works with one bit, not the potential eight.

In this example, the size of `Bar` is the same as `Foo`, but the situation that I ran across this with requires an _increase_ in size of the struct to _decrease_ the size of `Option<CompoundStruct>`; needless to say this is a tradeoff I don't want to make.

Presumably the compiler could do some magic here to take advantage of the niche values.
Repository: rust
Issue: Failed to garbage collect finalized incremental compilation session directory
Labels: T-compiler,A-incr-comp

Whenever and whatever I compile the warning is printed.
This is the output:
![IMG_20201129_164846](https://user-images.githubusercontent.com/31250625/100537418-7752d380-3263-11eb-9043-e5ef8c60debe.png)
I have tried deleting the `target` directory but it didn't work. Besides, I posted this problem to Rust Forum but until now no one could help. Although it seems not harmful, but it indeed exists, how can I resolve this?
Repository: flutter
Issue: [documentation] [tools] Decouple Flutter installation from Android Studio
Labels: c: new feature,platform-android,tool,d: api docs,a: first hour,P3,team-android,triaged-android

## Use case

- opinions:

   - for a number of reasons [vscode](https://code.visualstudio.com/) is a **_very_** popular, if not the most popular, IDE for flutter
   - `vscode` users rarely, if ever, use `android studio` outside the initial installation
   - while [no longer required](https://github.com/flutter/flutter/issues/9747#issuecomment-575839008) many developers might feel `android studio` installation is [mandatory](https://flutter.dev/docs/get-started/install/linux#android-setup)


- facts:
  - it is possible to use [flutter without android studio](https://ksrk.medium.com/install-flutter-without-android-studio-on-window-9d3781172912)
  - `flutter doctor` [complains](https://miro.medium.com/max/700/1*LIDGbFJne4y7j2qjNaFz1Q.png) about missing `android studio`, but ignores other IDEs

## Proposal

- [documenation] provide the steps to install  `Android platform dependencies` without android studio
- [tools] treat all major IDE / editor equally
- [tools] a way to [install Android environment via CLI flutter](https://github.com/flutter/flutter/issues/23520 ) would provide a **lighter** and [simpler](https://github.com/flutter/flutter/issues/9401) installation
- consider including this in the [installer requirements](http://flutter.dev/go/sdk-per-platform-installers)
Repository: pytorch
Issue: segment fault for Image model training by four GPUs
Labels: needs reproduction,module: crash,triaged

## 🐛 Bug

<!-- A clear and concise description of what the bug is. -->

after some epoches,  training task almost always crashed along with core file as segment fault in four-GPUs containerd environment, similar with https://github.com/facebookresearch/dlrm/issues/42

## To Reproduce

Steps to reproduce the behavior:

1. preparation that a four-GPUs containerd env is set, deployed with kubernetes or docker
2. in env above, exec a local training task
3. after some epoches, task exit with segment fault exception 

<!-- If you have a code sample, error messages, stack traces, please provide it here as well -->

## Expected behavior

<!-- A clear and concise description of what you expected to happen. -->
training task keeps running util a expected model is emited without same segment fault .

## Environment

Please copy and paste the output from our
[environment collection script](https://raw.githubusercontent.com/pytorch/pytorch/master/torch/utils/collect_env.py)
(or fill out the checklist below manually).

You can get the script and run it with:
```
wget https://raw.githubusercontent.com/pytorch/pytorch/master/torch/utils/collect_env.py
# For security purposes, please check the contents of collect_env.py before running it.
python collect_env.py

Collecting environment information...
PyTorch version: 1.4.0
Is debug build: No
CUDA used to build PyTorch: 10.1

OS: Ubuntu 18.04.2 LTS
GCC version: (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0
CMake version: version 3.14.5

Python version: 3.6
Is CUDA available: Yes
CUDA runtime version: Could not collect
GPU models and configuration:
GPU 0: GeForce RTX 2080 Ti
GPU 1: GeForce RTX 2080 Ti
GPU 2: GeForce RTX 2080 Ti
GPU 3: GeForce RTX 2080 Ti

Nvidia driver version: 418.43
cuDNN version: /usr/lib/x86_64-linux-gnu/libcudnn.so.7.6.0

Versions of relevant libraries:
[pip3] numpy==1.17.1
[pip3] torch==1.4.0
[pip3] torchvision==0.5.0
[conda] Could not collect
0
```



## Additional context

<!-- Add any other context about the problem here. -->


cc @ezyang @gchanan @zou3519 @bdhirsh
Repository: godot
Issue: Godot making duplicate material slots on OBJ import
Labels: bug,discussion,confirmed,topic:import,topic:3d

[Godot Material Dupes.zip](https://github.com/godotengine/godot/files/5613364/Godot.Material.Dupes.zip)
In Godot 3.2.3 (but not limited to it)

When you import an OBJ, Godot creates a material slot for every new material in the OBJ.
The problem is that a new slot is created every time the material being used in the .obj file changes, not every time a _new_ material is used.

So if the OBJ looks like this on the inside:
`using Material1`
`[draw some faces]`
`using Material2`
`[draw some faces]`
`using Material1`
`[draw some more faces]`

You end up with three material slots, instead of two (corresponding to all instances of Material 1 and Material 2). Even if that might be considered a messy OBJ file, some programs do export like this, and I believe Godot should still import it correctly and create a new material slot for every new _type_ of material, not every _change_ of material being used.

It's a big enough issue that if you're trying to work with a significant enough OBJ, you might end up with a few hundred materials in your MeshInstance node.
Repository: godot
Issue: "Ao Channel Affect" defaults to 0, giving unexpected results (fixed in `master` via different AO calculation)
Labels: discussion,topic:rendering,topic:3d

<!-- Please search existing issues for potential duplicates before filing yours:
https://github.com/godotengine/godot/issues?q=is%3Aissue
-->

**Godot version:**
3.2.3.Stable


**OS/device including version:**
NA


**Issue description:**
"Ao Channel Affect" defaults to 0, giving unexpected results. This means that as soon as you set an AO texture on a material, there will no longer be SSAO on that material. When this happened to me I assumed it was simply a limitation of the engine and on purpose. I think we should default that setting to 1. From talking to other Godot users I know others have thought that you couldn't use SSAO and AO textures at the same time because of this.

I'm also wondering if "Ao Channel Affect" is actually doing the correct thing. Currently it's controlling how much the SSAO can influence the AO maps, but it feels more logical that it would be how much the the AO maps are allowed to influence the SSAO.

![image](https://user-images.githubusercontent.com/4955051/100543411-e0c4e900-3247-11eb-863c-e9bab6f7bd8a.png)


**Steps to reproduce:**
Open the attached project to the see issue.

**Minimal reproduction project:**
[ssao_aompap_issue.zip](https://github.com/godotengine/godot/files/5612196/ssao_aompap_issue.zip)