sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: [Poll] Support DistributedDataParallel (DDP) in PyTorch C++ API (libtorch)
Labels: oncall: distributed,feature,triaged,module: ddp

We have seen several requests to support distributing training natively as part of the PyTorch C++ API (libtorch), namely [1](https://github.com/pytorch/pytorch/issues/40581), [2](https://github.com/pytorch/vision/issues/3052) (in torchvision repo), [3](https://discuss.pytorch.org/t/libtorch-c-mpi-example/39671/4), and an [example](https://github.com/pytorch/examples/pull/809/files) that uses `MPI_allreduce` because `DistributedDataParallel` in C++ is not supported. 

This issue aims to gauge the interest in this feature. Please add a reaction or comment if your project would benefit from Distributed Data Parallel support in PyTorch's C++ API! 

cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @agolynski @SciPioneer @H-Huang @mrzzd
Repository: rust
Issue: Tracking Issue for denying trailing semicolons in expression macro bodies
Labels: A-macros,T-lang,C-tracking-issue,S-tracking-needs-to-bake

This is a tracking issue for MCP https://github.com/rust-lang/lang-team/issues/70

### What is this issue?

If you're a crate author who's been linked here, this issue tracks emitting a hard error when a trailing semicolon occurs in a macro used in expression position. See https://github.com/rust-lang/lang-team/issues/70 for some background about the issue.

In the future, code like this may stop compiling:

```rust
macro_rules! foo {
    () => {
        true;
    }
}

fn main() {
    let val = match true {
        true => false,
        _ => foo!()
    };
}
```

In the above code snippet, `foo!()` is invoked in expression position (in this case, a macro arm). However, `foo!()` expands to the token stream `true;`, which is not a valid expression due to the presence of a trailing semicolon.

To make the behavior of macro expansion more consistent, we plan to turn this into a hard error at some point in the future.

Fixing issues in your crate is usually as simple as removing the trailing semicolon from the macro definition.

Currently, the associated lint (`semicolon_in_expressions_from_macros`) is set to allow-by-default. As time goes on, we may increase this to warn-by-default.


### About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however *not* meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

### Steps

- [x] Implement the lint: https://github.com/rust-lang/rust/pull/79819
- [X] Do a Crater run to determine the full extent of the impact (https://github.com/rust-lang/rust/pull/81477)
- [X] Fix `lint_node_id` so that we can apply `#[allow]` close to a macro call site (https://github.com/rust-lang/rust/pull/87146)
- [x] When https://github.com/rust-lang/rustfmt/pull/4507 makes it way into a stable release, make the lint warn-by-default
- [x] Mark the lint for inclusion in the cargo future-incompat-report (see https://github.com/rust-lang/rust/issues/71249) (https://github.com/rust-lang/rust/pull/103418)
- [ ] Switch the lint to deny-by-default
- [ ] Consider making the lint a hard error over an edition boundary

### Unresolved Questions
<!--
Include any open questions that need to be answered before the feature can be
stabilised.
-->

### Implementation history

1. Lint implemented in https://github.com/rust-lang/rust/pull/79819
2. Made warn-by-default in https://github.com/rust-lang/rust/pull/87385
3. Added to future-incompat report in https://github.com/rust-lang/rust/pull/103418
Repository: puppeteer
Issue: preferCSSPageSize option for PDF generation doesn't do anything
Labels: bug,confirmed,P3

We have upgraded the Chromium 80.0.3987.0 - Puppeteer v2.1.0 to the newest Chromium 88.0.4298.0 - Puppeteer 5.5.0 to pursue the taggable PDF output. After the upgrade the following HTML ...

    <html xmlns="http://www.w3.org/TR/REC-html40">
    <head>
    <style>
    @page section
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
    div.section
	{page:section;}
    </style>
    </head>
    <body>
	<b>Test string before content</b>
	
	<div class="section"><p>Content</p></div>
	
	<b>Test string after content</b>
    </body>
    </html>

when converted to PDF produces 3 pages, one with before content, the second with content, and the third with after content. With the previous Puppeteer 2.1 we had, the same HTML was producing the single PDF page, which we would expect if `preferCSSPageSize: false`, which is the default by the way. I assume the option tells the converter to ignore `@Page` media.
Are there any changes to this PDF option? Is my assumption wrong (but in this case what does this option do for the given HTML)?
We have tried to set explicitly `preferCSSPageSize`, but it doesn't make any difference, we are getting 3 pages PDF all the time.

Please note: I am not asking how to modify HTML to get one page, I am completely aware of the [page CSS property](https://www.quackit.com/css/properties/css_page.cfm); I am asking what was changed over the versions, as well as clearly understand why `@Page` media suddenly start working when should be suppressed.
Repository: pytorch
Issue: non-negative least squares solver feature request
Labels: feature,triaged

## 🚀 Feature
non-negative least squares solver.

## Motivation
Scipy has [nnls](https://docs.scipy.org/doc/scipy/reference/generated/scipy.optimize.nnls.html#scipy.optimize.nnls) which is useful when solving linear least squares with non-negativity constraint.

## Pitch
The solution to the least squares should be non-negative. 

## Additional context
In the new version, PyTorch has lstsq implemented. But it does not include the non-negative constraints. 

Thank you.
Repository: pytorch
Issue: Scripting silently ignores methods of class derived from `NamedTuple`
Labels: oncall: jit

## 🐛 Bug

When a Python class derives from `NamedTuple`, its methods and staticmethods are silently ignored at compile time until their callsite.

## To Reproduce

```
import torch
from typing import NamedTuple, Tuple


class Pair(NamedTuple):
    x: int
    y: int

    @staticmethod
    def from_tuple(t: Tuple[int, int]):
        return Point(t[0], t[1])

    def sum(self):
        return self.x + self.y


def fn():
    v = (2, 3)
    p = Pair.from_tuple(v)
    return (p.x, p.y)

def fn2():
    p = Pair(3, 4)
    return p.sum()

scripted_fn = torch.jit.script(fn)  # fails with: attribute lookup is not defined on __torch__.Pair:
scripted_fn2 = torch.jit.script(fn2) # fails with: Tried to access nonexistent attribute or method 'sum' of type '__torch__.Pair'
```

## Expected behavior

Either gives clear error message stating that deriving from NamedTuple isn't allowed or fully support deriving from NamedTuple with custom methods.



cc @gmagogsfm
Repository: angular
Issue: Patch `requestIdleCallback` for ZoneJS
Labels: area: zones,P3

`requestIdleCallback` doesn't appear to be patched by ZoneJS.
Repository: godot
Issue: Visual glitch with WorldEnvironment dof_blur_near & HTML
Labels: bug,platform:web,topic:rendering,confirmed

**Godot version:**
3.2.3 stable

**OS/device including version:**
i7-7700 CPU, Gforce 1080, gles 3

**Issue description:**
Visual glitch with **WorldEnvironment** in **canvas mode**, with **dof_blur_near enabled**, exported to HTML

**Steps to reproduce:**
create node2d main scene, add sprite, add WorldEnvironment node, set it to canvas mode and enable dof_blur_near, export it to html.

dof_blur_near enabled
![Desktop Screenshot 2020 12 08 - 03 46 19 02](https://user-images.githubusercontent.com/55656526/101429064-b12e7480-390a-11eb-845e-b654f9d8cc62.png)

dof_blur_near disabled
![Desktop Screenshot 2020 12 08 - 03 46 40 81](https://user-images.githubusercontent.com/55656526/101429067-b390ce80-390a-11eb-8acb-bb33c695d6fb.png)


**Minimal reproduction project:**
[Minimal reproduction WorldEnviroment html Glitch.zip](https://github.com/godotengine/godot/files/5656389/Minimal.reproduction.WorldEnviroment.html.Glitch.zip)
Repository: pytorch
Issue: Torch1.2 can't be downloaded!
Labels: triaged

The day before yesterday,I have successfully downloaded torch1.2 by the command provided by office,however I can't download it today using the same command 'pip install torch==1.2.0 torchvision==0.4.0'. Is there someone like me?
Repository: neovim
Issue: :messages shows "search hit BOTTOM, continuing at TOP"
Labels: enhancement,complexity:low,messages

Searches and jumps w/ `n`, `N` are written to the message log. I'm guessing (though am not sure) that `echomsg` is used to display the search information. Is there a setting I can toggle to use `echo` instead, so the search info still appears on the bottom but does not appear when I run `:messages`?

Example (in case this description isn't clear):
If in a new buffer I type `this is a test this is a test`, then `*`, then `n` a bunch of times, and then open up messages I see:
```
search hit BOTTOM, continuing at TOP
/\<test\>                                                        [1/2] W
/\<test\>                                                          [2/2]
search hit BOTTOM, continuing at TOP
/\<test\>                                                        [1/2] W
/\<test\>                                                          [2/2]
search hit BOTTOM, continuing at TOP
/\<test\>                                                        [1/2] W
/\<test\>                                                          [2/2]
search hit BOTTOM, continuing at TOP
/\<test\>                                                        [1/2] W
/\<test\>                                                          [2/2]
```
I want these messages displayed at the time of searching/jumping, but not in the log.
Repository: material-ui
Issue: [Accordion] Cannot create custom <AccordionSummary> variants
Labels: new feature,component: accordion,ready to take

- [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 💡

Right now it's not possible to customize `<AccordionSummary>` if your customization cannot be done via props adding styles and stuff into the `content` div.

## Current Behavior 😯

AccordionSummary has a hardcoded `content` `<div>` wrapping the `children` and an icon button outside it in a hardcoded location, so there are some things you cannot customize simply by changing styles.

The AccordionSummary's accordion behaviours depend on `AccordionContext`. However `AccordionContext` is not an official part of MUI, it's not in the docs or types. So you cannot create your own `AccordionContext`.

## Expected Behavior 🤔

It should be possible to create your own `AccordionSummary` without needing to use the internal `AccordionContext`.

## Motivation 🔦

I was trying to implement a customized MUI Accordion from the designer I'm working with. Their accordion moved the expandIcon before the content area. However the built-in accordion summary has the expand icon hardcoded as a position=end icon button after the content area.

So naturally I tried to customize AccordionSummary and then fork it because I couldn't simply customize it and since it's a custom design it's reasonable to not expect the built-in AccordionSummary to handle it. Then of course I discovered that it just wasn't possible officially.
Repository: vscode
Issue: Pressing `shift-left/right` will exit multi-caret mode
Labels: bug,editor-columnselect

When multiple carets are inserted, no matter with or without selections, pressing `shift-left` or `shift-right` exits the multi-caret mode (in some cases), and selecting texts only under the first caret, instead of initiate(or adjust) text selections for every caret. 

Scenario:
* If entered multi-caret mode with `shift+up/down`, then text selection works fine. 
  * If carets are moved in any direction after (this would deselect texts under all carets, but keep all the carets in place, if any text previously selected), then selection failed to initiate/being adjusted correctly. 
* If multiple carets are inserted by mouse clicking (holding `alt`) or `column selection mode`, selection failed to initiate correctly.
* `shift-end/home` works fine in both situation, but after that, pressing `shift-left/right` exits the multi-caret mode, and deselects texts under all other carets.
* will exit multiple selection mode initiated by `ctrl-d`(named "Add selection to next find match"), too.

<del>As i remembered, there was a time when i could adjust multiple text selections simultaneously/synchronized.</del> (confirmed: that is PyCharm instead of vscode)

It seems adjusting multiple selection will only work when all carets are "aligned" and "not modified yet", at present. Would this be a bug?

Also: `move lines up and down` does not work under multi-caret mode either, but this seems unrelated to this issue (i'm too lazy to submit this in a new issue).

======================

Tested: behaves exactly the same when all extensions are disabled.

======================

Version: 1.51.1
Commit: e5a624b788d92b8d34d1392e4c4d9789406efe8f
Date: 2020-11-10T23:31:29.624Z (3 wks ago)
Electron: 9.3.3
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Linux x64 4.15.0-23-generic (note: Ubuntu 16.04)
Repository: deno
Issue: Line number only coverage reporter
Labels: cli,suggestion

From discord (copy link is not working in safari, eh)

> Would it be a good idea to add a flag for deno test --coverage to tell it to output the line numbers of uncovered code instead of the actual lines of code? Maybe --line-numbers. Early in testing when there are many uncovered lines, it feels like seeing the uncovered code isn't as useful as just seeing the line numbers that need attention.
Repository: storybook
Issue: Storybook get access to hidden tabs
Labels: bug,ui

**Describe the bug**

Hi everyone! Our design system contains documentation and stories apart from each other. (common documentation, like color palette, icons, etc.). The documentation section doesn't have a canvas tab at least we use out-of-box modules, like ColorPalette and it cannot be rendered in canvas. See more why it can't be used in stories https://github.com/storybookjs/storybook/issues/8753#issuecomment-581666601

So, the problem is when I want to see stories in my design system, I use canvas, then I want to read some docs (where the canvas tab is hidden) but Storybook has navigated me on the same tab even though he is hidden!
It caught some errors that our customers can see and feel themselves little confused. It seems like something went wrong and they have got an error. Just in case they see the error in the colors palette canvas section.


**To Reproduce**
You can create simple stories with different parameters for previewTabs or see the code snippets and video below.

**Expected behavior**
Routes in the Storybook navigation panel contain URLs for visible tabs only
 
For example:

The first story contains tabs: canvas, docs, notes
The next one contains docs, canvas.

Then I look at the first canvas story and decide to go next. The next page opens on docs route (even though the previews one was on canvas)

**Video**

[![Click for for demo video](https://drive.google.com/file/d/1GF2tCtOAXCdhSjYFNTDMxD36IzaVpIPj/view?usp=sharing)](https://drive.google.com/file/d/1oCnLjsvaSD9fqDOO2qvHNxGD4FPEGf-t/view?usp=sharing)

**Code snippets**

```typescript
// available tabs: docs, notes
import * as React from 'react';

type IProps = {
    children: string;
};

const Component = ({children}: IProps) => <button>{children}</button>;

const Template: ITemplate<IProps> = ({args}) => <Component {...args}/>;

export default {
    title: 'Storybook/Example/Doc',
    component: Component,
    parameters: {
		previewTabs: {
			canvas: {
				hidden: true,
			},
		},
    },
    argTypes: {
        children: {
            control: {
                type: 'text'
            }
        }
    }
};

export const common = Template.bind({});

common.args = {
    children: 'Click me'
};

common.storyName = 'Without canvas tab';
```

And the second:

```typescript
//available tabs: canvas, docs, notes
import * as React from 'react';

type IProps = {
    children: string;
};

const Component = ({children}: IProps) => <div>{children}</div>;


const Template: ITemplate<IProps> = ({args}) => <Component {...args}/>;


export default {
    title: 'Storybook/Example/Story',
    component: Component,
    argTypes: {
        children: {
            control: {
                type: 'text'
            }
        }
    }
};

export const common = Template.bind({});

common.args = {
    children: 'Hello world'
};

common.storyName = 'With canvas tab';
```
**System**

MacOS: 10.15.7
@storybook/react@6.1.10
node version: 10.17.0
npm version: 6.11.3
Repository: PowerToys
Issue: [Feature Request] Add background acrylic to Color Picker
Labels: Status-In progress,Area-User Interface,Product-Color Picker

Seeing as Image Resizer and Color Picker PowerToys have both had a recent makeover to fit in with the Fluent UI guidelines it'll be nice to go a bit further and to introduce Acrylic into the mix with background acrylic.

I have tested this in a small sample app with [ModernWPF](https://github.com/Kinnara/ModernWpf) (which is what the Image Resizer and Colour Picker are using) with [FluentWpfChromes](https://github.com/vbobroff-app/FluentWpfChromes), and it seems to work really well together. 

![image](https://user-images.githubusercontent.com/14894973/101481135-941a9580-394c-11eb-87b4-936f00e1be02.png)
Repository: go
Issue: html/template: Tree is only updated after Execute is called
Labels: Documentation,NeedsFix

<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.15.5 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/vktec/.cache/go-build"
GOENV="/home/vktec/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/vktec/.go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/vktec/.go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/lib/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build234409553=/tmp/go-build -gno-record-gcc-switches"
</pre></details>

### What did you do?

```go
tmpl := template.Must(template.New("").Parse(`{{.}}`))
fmt.Println(tmpl.Tree.Root)
tmpl.Execute(ioutil.Discard, "")
fmt.Println(tmpl.Tree.Root)
```
https://play.golang.org/p/Tt61uh_jIRf

### What did you expect to see?

Before `Execute` is called, the `Tree` should already have been "updated to be HTML-safe", as implied by [the documentation] for that field:

> The underlying template's parse tree, updated to be HTML-safe.

[the documentation]: https://golang.org/pkg/html/template/#Template

### What did you see instead?

The `Tree` is only updated after `Execute` is called.
Repository: godot
Issue: Reverting a resource with editor doesn't properly update the editor (e.g. CollisionShape2D)
Labels: bug,topic:editor

<!-- 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. -->
3.2.4 beta3

**Issue description:**
When a resource has a dedicated editor (e.g. CollisionShape2D or NavigationPolygon) and you revert the resource, the viewport isn't properly refreshed and its handles will linger. Doesn't happen when you explicitly clear the resource.
![Y8kp8JlgyK](https://user-images.githubusercontent.com/2223172/101486048-5b82b800-395c-11eb-8232-4bcc94217f29.gif)
Repository: pytorch
Issue: Discrete Cosine Transform
Labels: feature,triaged

## 🚀 Feature
Dear developers, i hope that the new version supports Discrete Cosine Transform (DCT). 

## Motivation
The third-party library torch-dct (https://github.com/zh217/torch-dct) who depends on the function torch.fft(), is the only method for implementing DCT with pytorch. However, Pytorch 1.7.0 has a new module, torch.fft, to replace the function torch.fft() in a future PyTorch release. So, torch-dct will be incompatible with Pytorch, and there will be no elegant way to implement DCT.


## Pitch
Hope the future PyTorch release to officially support DCT.
Repository: three.js
Issue: Inherit group render order
Labels: Suggestion

**Is your feature request related to a problem? Please describe.**

We frequently work with deep scene graphs featuring lots of 2D objects in the same Z-plane. Render order is our go-to feature to ensure things are drawn on top of each other in the correct order.

I began to notice that our code was getting littered with haphazardly organized render order assignments, and after some digging I found out that render lists sort objects by `groupOrder` first and `renderOrder` second. So far, so good. However, an object's `groupOrder` is apparently determined by its closest ancestor Group, and not by any Groups higher up in the scene graph. That's very surprising behavior!

For example, consider the following tree:

- Scene
  - Group A (renderOrder: 4)
    - Group (renderOrder: 0)
      - Mesh A
  - Group B (renderOrder: 3)
    - Group (renderOrder: 1)
      - Mesh B

I would expect mesh A to be drawn on top of Mesh B. However, the opposite happens, and Mesh B is drawn on top of mesh A.

This is because currently, only the renderOrder attribute of the closest ancestor Group is actually taken into account when sorting.

**Describe the solution you'd like**

For renderOrder of _all_ parent nodes (and not just Group objects either, since any Object3D can have children and a renderOrder) to be considered when sorting the render list.

I wouldn't know off the top of my head what would be the shortest route to an implementation though.

**Describe alternatives you've considered**

Well, currently we are sprinkling our code with (many) additional renderOrder assignments to inherit renderOrder from parent groups manually.
Repository: flutter
Issue: [gen_l10n] Documentation regarding plugins & modules
Labels: a: internationalization,d: api docs,P2,a: plugins,team-tool

As stated in #70840 I kindly ask to update the documentation of the l10n integration regarding plugins and modules. For instance how synthetic package needs to be disabled etc. Thank you!