sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: Allow showing the expanded macros of only a given module / source file
Labels: C-feature-request

When working with many macros, looking at the expanded macro output of the whole crate doesn't scale.

There should be an option to only show the expanded macros from a given module / source file.

E.g. in one case I have 81733 lines in the expanded macro output from `cargo rustc -- -Z unstable-options --pretty=expanded`...
Repository: go
Issue: crypto/rsa: linux/arm64 Go 1.9 performance is +10X slower than OpenSSL
Labels: Performance,help wanted,NeedsFix

Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?
go version go1.9.2 linux/arm64

### Does this issue reproduce with the latest release?
yes

### What operating system and processor architecture are you using (`go env`)?
GOARCH="arm64"
GOBIN=""
GOEXE=""
GOHOSTARCH="arm64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH=""
GORACE=""
GOROOT="/usr/lib/go-1.6"
GOTOOLDIR="/usr/lib/go-1.6/pkg/tool/linux_arm64"
GO15VENDOREXPERIMENT="1"
CC="gcc"
GOGCCFLAGS="-fPIC -pthread -fmessage-length=0"
CXX="g++"
CGO_ENABLED="1"

### What did you do?
go test crypto/rsa -bench .

### What did you expect to see?
Performance can be on par with OpenSSL (https://blog.cloudflare.com/content/images/2017/11/pub_key_1_core-2.png)

### What did you see instead?
+10X slower than OpenSSL (https://blog.cloudflare.com/content/images/2017/11/go_pub_key_1_core.png)
Repository: node
Issue: domain migration to async_hooks
Labels: domain,async_hooks

The PR https://github.com/nodejs/node/pull/16222, contains the first step by @vdeturckheim to remove `domain` from the deep layers of nodecore and implement it on top of `async_hooks`. This PR just landed, thus I'm opening this issue to discuss the next steps.

- [Deprecate and remove `.domain` support from `MakeCallback`](https://github.com/nodejs/node/blob/97ba69f91543f89d389a4f3fef57c5c6c734df34/src/node.cc#L855L882). Implementers should use `async_context`. What will our depreciation and removal strategy for this be? _Note: we would like to ultimately remove this as it adds quite a bit of extra complexity._
  - [x] Deprecate `.domain` support from `MakeCallback` (PR: https://github.com/nodejs/node/pull/17417)
  - [ ] Remove `.domain` support from `MakeCallback`
- [x] [Remove special domain code in exception handling](https://github.com/nodejs/node/blob/97ba69f91543f89d389a4f3fef57c5c6c734df34/src/node.cc#L784L851). ~~It is unclear what the migration strategy for this is.~~ (PR: https://github.com/nodejs/node/pull/17159)
- [x] [Remove domain integration in events](https://github.com/nodejs/node/blob/283b949404745314801462f48e379397545bdde2/lib/events.js#L152L168). (PR: https://github.com/nodejs/node/pull/17403, PR: https://github.com/nodejs/node/pull/17588)
- Check for leftovers. Examples:
  - [x] [timers](https://github.com/nodejs/node/blob/4503da8a3a3b0b71d950a63de729ce495965f6ea/lib/timers.js#L266L275) (PR: https://github.com/nodejs/node/pull/17880)
  - [x] [env declarations](https://github.com/nodejs/node/blob/4503da8a3a3b0b71d950a63de729ce495965f6ea/src/env.h#L274) (PR: https://github.com/nodejs/node/pull/18291)
- [x] Track context with `async_hooks` (PR: https://github.com/nodejs/node/pull/16222)

/cc @addaleax @vdeturckheim
Repository: pytorch
Issue: Add SGDR, SGDW, AdamW and AdamWR
Labels: module: optimizer,triaged

Recently, there are two papers from [Ilya Loshchilov](http://ml.informatik.uni-freiburg.de/people/loshchilov/index.html) and [Frank Hutter](http://www2.informatik.uni-freiburg.de/~hutter/).
[SGDR: Stochastic Gradient Descent with Warm Restarts](https://arxiv.org/abs/1608.03983), introduces a learning rate decay method according to different training periods. Several hyperparameters improve the-state-of-the art result a lot. It has been added to tensorflow as [tf.train.cosine_decay](https://www.tensorflow.org/versions/master/api_docs/python/tf/train/cosine_decay)
Their recent work [Fixing Weight Decay Regularization in Adam](https://arxiv.org/abs/1711.05101) fixes a wide misunderstanding when using Adam and weight decay synchronously. It has been highly admitted by the author of [Adam](https://twitter.com/dpkingma/status/930849593767608320).
 
I think pytorch should add these features as well.

cc @vincentqb
Repository: opencv
Issue: How to load and save a tiff image with CMYK channel, and keep it unchanged
Labels: category: imgcodecs,incomplete

I read a tiff image, and then save it as png.
However, the color looks different.
I want to know how to load and save a tiff image with CMYK channel, and keep it unchanged

```
    p = "image.tif"
    origin = cv2.imread(p, cv2.IMREAD_UNCHANGED)
    cv2.imwrite("test.png", origin)
```
Repository: pytorch
Issue: Make pytest stop printing docstrings in its default diagnostic output
Labels: module: tests,triaged,enhancement

Sample:

```
_________________________________ TestNN.test_ConvTranspose3d_dilated_cuda ________________________[67/1868]

self = <test_nn.TestNN testMethod=test_ConvTranspose3d_dilated_cuda>
test = <test_nn.NewModuleTest object at 0x7f0b865920b8>

>   setattr(TestNN, cuda_test_name, lambda self, test=test: test.test_cuda(self))

test_nn.py:3636: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
common_nn.py:850: in test_cuda
    gpu_gradInput = test_case._backward(gpu_module, gpu_input, gpu_output, gpu_gradOutput)
test_nn.py:237: in _backward
    output.backward(grad_output, retain_graph=True)
../torch/autograd/variable.py:168: in backward
    torch.autograd.backward(self, gradient, retain_graph, create_graph, retain_variables)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

variables = (Variable containing:
(0 ,0 ,0 ,.,.) = 
 -5.6280e-02 -1.3005e-01  3.2031e-01 -4.1098e-03  2.5253e-01  1.3095e-01
  9.9...4e-01  1.4101e-01  3.8256e-01 -1.2257e-01  3.1663e-03 -4.4487e-01
[torch.cuda.FloatTensor of size 1x3x6x9x6 (GPU 0)]
,)
grad_variables = (Variable containing:
(0 ,0 ,0 ,.,.) = 
   0   1   0   0   1   1
   0   1   1   0   1   0
   1   0   1   0   1   0
   ...  1   0   1   1
   0   0   0   0   1   1
   0   1   1   1   1   0
[torch.cuda.FloatTensor of size 1x3x6x9x6 (GPU 0)]
,)
retain_graph = True, create_graph = False, retain_variables = None

    def backward(variables, grad_variables=None, retain_graph=None, create_graph=None, retain_variables=None
):
        """Computes the sum of gradients of given variables w.r.t. graph leaves.
    
        The graph is differentiated using the chain rule. If any of ``variables``
        are non-scalar (i.e. their data has more than one element) and require
        gradient, the function additionally requires specifying ``grad_variables``.
```

I guess it is trying to be helpfully chatty, but I don't need to see a big pile of docstring...

cc @mruberry
Repository: go
Issue: encoding/json: include field name in unmarshal error messages when extracting time.Time
Labels: NeedsInvestigation

allocated from #6716 .

### What version of Go are you using (`go version`)?
go1.9.2 linux/amd64

### Does this issue reproduce with the latest release?
yes

### What operating system and processor architecture are you using (`go env`)?
GOARCH="amd64"
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"

### What did you do?
run https://play.golang.org/p/YnlDi-3DMP

If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.


### What did you expect to see?
Field name with error message

### What did you see instead?
Error without field name
Repository: neovim
Issue: 'sessionoptions': restore quickfix window
Labels: enhancement


- `nvim --version`: v0.2.2
- Operating system/version: archlinux64
- Terminal name/version: termite
- `$TERM`: xterm-termite

### Steps to reproduce using `nvim -u NORC`

```
nvim -u NORC
:vsplit
C-w l
:copen
:mksession session.vim
:qa
nvim -u NORC -s session.vim
```

### Actual behaviour

The quickfix window (bottom right) is gone

### Expected behaviour

The quickfix window is restored. For my workflow there is some rationale where I place that window, so I would like to see it being restored just like other windows / buffers.
Repository: godot
Issue: Spatial/Node2D locks should not be saved through metadata
Labels: enhancement,topic:core,usability

**Operating system or device, Godot version, GPU Model and driver (if graphics related):**
450bdda97a933ed9081efa20bddc71ee0b8286c9

**Issue description:**
According to discussion in #12359 it seems locks should not be saved inside scene metadata anymore. Instead there should be new bool property inside node2d/spatial that should not be visible in inspector. As far as we discussed on IRC this still could be considered for 3.0
Repository: kubernetes
Issue: Make kubectl Scale function for RS, Deployments, Job, etc watch-based
Labels: kind/cleanup,area/kubectl,sig/autoscaling,sig/apps,lifecycle/frozen

Offshoot of https://github.com/kubernetes/kubernetes/issues/56064#issuecomment-345738834

As part of the kubectl Scale() function, we can optionally waitForReplicas to reach the desired count.
Currently, we're polling periodically to check that happens (for RS, jobs, etc). We should move them to use Watch instead - like we're doing for RCs currently:

https://github.com/kubernetes/kubernetes/blob/98fb71e8ce2caa3062f3f0b0ed4ab470683f5578/pkg/kubectl/scale.go#L233-L246

/area kubectl
/kind cleanup
Repository: godot
Issue: Cache calls to set custom clipping rectangles on a CanvasItem
Labels: enhancement,topic:core,topic:2d

For instance in this snipped of code:

	void MyCustomItem::_notification(int p_what) {

		case NOTIFICATION_DRAW: {
			// Enable clipping
			VisualServer::get_singleton()->canvas_item_set_clip(get_canvas_item(), true);
	
			draw_background();

			// Clip to margins
			VisualServer::get_singleton()->canvas_item_set_custom_rect(get_canvas_item(), true, Rect2(
				Point2(
				 margin_left,
				 margin_top
				),
				Size2(
				 width - margin_left - margin_right,
				 height - margin_top - margin_bottom
				)
			));

			draw_stuff();
			break;
		}
	}

I need `draw_background()` to paint something within the CanvasItem clipping area and `draw_stuff()` to draw everything else within some margin. Such thing would be possible if calls to `canvas_item_set_clip()` and `canvas_item_set_custom_rect()` were cached.
Repository: flutter
Issue: single finger scale gesture
Labels: framework,f: gestures,has reproducible steps,P2,found in release: 3.7,found in release: 3.9,team-framework,triaged-framework

`onScaleUpdate` is being triggered for a `GestureDetector` even when the user is touching the screen with only a single finger. In this case, `details.scale` is `1.0`. I don't know the behavior of iOS or Android, but it seems like scale update should not be triggered for a single finger.

This is a problem because when a user is placing or removing two fingers on the screen, often one finger will remain for a brief time, which will reset the scale factor and cause ugly jank.

The workaround would be for the developer to listen for `onScaleStart` and `onScaleEnd` and based on those listen for `onScaleUpdate` only during the time scale is active.

See also issue #13101
Repository: go
Issue: net/http: set response headers on TimeoutHandler timeout
Labels: NeedsDecision,FeatureRequest

I was recently suprised to discover that [`http.TimeoutHandler`] returns a blob of HTML (`"<html><head><title>Timeout</title></head><body><h1>Timeout</h1></body></html>"`) as the default message body. It does not attempt to set the appropriate Content-Type header and if you write a response yourself there is no option to set the content type.

The documentation says:

> (If msg is empty, a suitable default message will be sent.)

It would be nice if the format of the default message could be mentioned in the documentation, the default could be removed, or the Content-Type could be set (or some combination of the above).


[`http.TimeoutHandler`]: https://golang.org/pkg/net/http/#TimeoutHandler

/cc @bradfitz
Repository: neovim
Issue: UI: perf: avoid redraw for completed 'showcmd'
Labels: performance,ui

It was noticed that when 'showcmd' is enabled, even completed commands (or trivial commands such as `j` or ESC) cause a screen update, which is then cleared by an immediate redraw.

- RPC: `nvim_input('<esc>')` 
- One of the updates is: `#("cursor_goto" #(9 21)) #("put" #("^") #("[")) #("cursor_goto" #(0 0)))`

Sometimes you can even see this in a slow terminal, by holding down `j`, for example.

Perhaps we can avoid the screen update entirely.
Repository: puppeteer
Issue: expose timing information
Labels: feature,chromium

Exposing timing information would greatly benefit performance scenarios.
We shoud:
1. add `DOMContentLoaded` and `NavigationStart` metrics to the `Page.metrics()` struct
2. expose timing information for requests/response objects

There's currently a suspicion that [1] is not aligned with [2] in the protocol. We, however, should pick a single time scale and use it throughout the api.
Repository: rust
Issue: vtable addresses differ based on the number of codegen units
Labels: A-codegen,A-trait-system,T-lang,T-compiler,C-bug

I'm seeing the ptr::eq function from the standard library sometimes return false when it should return true.  This is happening in debug mode in nightly and beta, but not stable, and not in any version in release mode.

Here's the simplest I could get a reproduction of the issue:

    use std::ptr;
    use container::Container;

    trait Trait {}
    struct Struct {}
    impl Trait for Struct {}

    mod container {
        use Trait;

        pub(crate) struct Container<'a> {
            pub(crate) item: &'a Trait,
        }
    }

    impl<'a> Container<'a> {
        fn new(item: &'a Struct) -> Container<'a> {
            Container { item }
        }
    }

    fn main() {
        let item = Struct {};
        let container = Container::new(&item);

        assert!(ptr::eq(container.item, &item));
    }

Expected the assertion to pass, and it fails on beta and nightly, in debug mode only.

## Meta
`rustc +beta --version --verbose`:
rustc 1.22.0-beta.3 (cc6ed0640 2017-11-13)
binary: rustc
commit-hash: cc6ed0640fbcd2dff95b4532fd12aa0d6c545f28
commit-date: 2017-11-13
host: x86_64-pc-windows-msvc
release: 1.22.0-beta.3
LLVM version: 4.0

`rustc +nightly --version --verbose`:
rustc 1.23.0-nightly (5041b3bb3 2017-11-19)
binary: rustc
commit-hash: 5041b3bb3d953a14f32b15d1e41341c629acae12
commit-date: 2017-11-19
host: x86_64-pc-windows-msvc
release: 1.23.0-nightly
LLVM version: 4.0
Repository: go
Issue: cmd/compile: cannot compile valid (but esoteric) self-recursive interface
Labels: compiler/runtime

https://play.golang.org/p/YSkuYfVQHI

Esoteric case. Just for reference.
Repository: vscode
Issue: ANSI color support in edit buffer
Labels: feature-request,editor-rendering

<!-- Do you have a question? Please ask it on http://stackoverflow.com/questions/tagged/vscode. -->
Now ANSI colors are supported in the debug console, I'd like to see it in the editor, something like [SublimeANSI](https://github.com/aziz/SublimeANSI).

<!-- Use Help > Report Issues to prefill these. -->
- VSCode Version: 1.19
- OS Version: macOS

Steps to Reproduce:

1. open a file which contains ANSI color escape sequence, or simply `ls --color | code`
2. colorless raw ANSI code displayed, rather than colored text.

<!-- Launch with `code --disable-extensions` to check. -->
Reproduces without extensions: Yes
Repository: go
Issue: proposal: net: add support for "let localhost be localhost"
Labels: Proposal,Proposal-Hold

The I-D https://tools.ietf.org/html/draft-ietf-dnsop-let-localhost-be-localhost became an IETF dnsop-wg draft. It would be better to support the feature once the I-D has been published as an RFC for the sake of convenience instead of saying "sorry, there's no direct relationship between the IPv4 loopback address prefix ```127.0.0.0/8``` or the IPv6 loopback address ```::1``` and the name ```localhost```, that's just the convention", although the resolution for ```localhost``` still remains as a burden of applications from security perspective.
Repository: TypeScript
Issue: Sort jsdoc parameter suggestions by argument position 
Labels: Suggestion,Help Wanted,Good First Issue,Domain: Completion Lists,VS Code Tracked,PursuitFellowship

<!-- BUGS: Please use this template. -->
<!-- QUESTIONS: This is not a general support forum! Ask Qs at http://stackoverflow.com/questions/tagged/typescript -->
<!-- SUGGESTIONS: See https://github.com/Microsoft/TypeScript-wiki/blob/master/Writing-Good-Design-Proposals.md -->

From https://github.com/Microsoft/vscode/issues/35124

<!-- Please try to reproduce the issue with `typescript@next`. It may have already been fixed. -->
**TypeScript Version:**  2.7.0-dev.20171116

**Code**

For the code:

```ts
/**
 * @param |
 */
function foo(z, a) {}
```

Trigger completions at the `|` after `@param`


**Expected behavior:**
`z` is returned first, followed by `a`. The `sortText` can be used for this


**Actual behavior:**
`a` and `z` are returned with sort orders weights:

```
[Trace  - 11:33:07 PM] Sending request: completions (176). Response expected: yes. Current queue length: 0
Arguments: {
    "file": "/Users/matb/projects/san/y.ts",
    "line": 2,
    "offset": 11,
    "includeExternalModuleExports": true
}
[Trace  - 11:33:07 PM] Response received: completions (176). Request took 2 ms. Success: true 
Result: [
    {
        "name": "a",
        "kind": "parameter",
        "kindModifiers": "",
        "sortText": "0"
    },
    {
        "name": "z",
        "kind": "parameter",
        "kindModifiers": "",
        "sortText": "0"
    }
]
```
Repository: TypeScript
Issue: TypeScript: aggregate errors for file from all projects
Labels: Bug,Domain: TSServer

_From @OliverJAsh on September 30, 2017 16:20_

I have a project with three folders, two of which are TS projects and the third of which is shared between them:

- shared
- service-worker (with `tsconfig.json`)
- browser (with `tsconfig.json`)

Both "browser" and "service-worker" depend on "shared".

However, when I open a file in "shared", I only see errors related to one of the `tsconfig.json`s—usually this will be the `tsconfig.json ` used for the file I navigated from previously.

It would be great if VSCode could aggregate all errors for the current file for all matching TS projects.

_Copied from original issue: Microsoft/vscode#35432_
Repository: go
Issue: net: clarification on the use of 0.0.0.0/8, ::/128 and ::ffff:0.0.0.0/128 as destination
Labels: help wanted,NeedsInvestigation

The fixes for #6290 and #18806 revealed that the use of special IP addresses, 0.0.0.0/8 or ::/128, as the destination is confusing especially when working with datagram transport protocols as described in #22811. It would be better to clarify and to implement consistent API semantics (because some of the special addresses is prohibited from using the destination IP address, so the existing behavior is Go-specific extended interpretation) for avoiding unnecessary confusion.

Just FYI:
- 0.0.0.0/8 is defined in section 3.2.1.3 of RFC 1122 as "this host on this network." For historical reasons, some IP stack implementations allow to use 0.0.0.0/32 as the destination address of IP packets, but in general it's prohibited from using as the destination address,
- ::/128 is defined in section 2.5.2 of RFC 4291 as "the unspecified address." It's clearly stated that the unspecified address must not be used as the destination address and I've never seen IP stack implementation that allows to use the unspecified address as the destination address (I guess that  IPv6 protocol conformance tools did a great job.)
Repository: godot
Issue: Implement InputEventGesture (incl. Pan and Magnify) for all platforms
Labels: enhancement,platform:windows,platform:linuxbsd,platform:web,platform:ios,platform:android,topic:core,topic:porting,platform:uwp,topic:input

**Operating system or device, Godot version, GPU Model and driver (if graphics related):**
Current master (5a23136).

**Issue description:**
`InputEventGesture` was added to core in #12573, together with `InputEventPanGesture` and `InputEventMagnifyGesture`, but they're only implemented for macOS so far.

They should also be implemented for all platforms where they are relevant. I *guess* they would make sense on all platforms since gestures can be done on touchscreens as well as touchpads, so the list would be:

- [ ] Android (#25474 - reverted)
- [ ] iOS
- [ ] Javascript
- [ ] Wayland Linux and (if possible) *BSDs
- [ ] X11 Linux and (if possible) *BSDs
- [x] macOS (#12573)
- [ ] UWP
- [ ] Windows

See #12573 for the base API and its implementation on macOS.

If more types of gestures are wanted, they should likely be discussed in their own issue, let's keep this one focused on pan and magnify.
Repository: rust
Issue: Infer if type through indirection.
Labels: C-enhancement,A-inference

It surprised me that the first example works, while the second doesn't.

https://play.rust-lang.org/?gist=a1bee92067f87a67240b4ccd2bc9a6a4&version=stable

```rust
trait Foo {}

struct A;
impl Foo for A {}

struct B;
impl Foo for B {}

pub fn test() {
    let a = A;
    let b = B;

    // Works.
    let x: &Foo = if true { &a } else { &b };

    // Doesn't work.
    let y = if true { &a } else { &b };
    let z: &Foo = y;
}
```

```
error[E0308]: if and else have incompatible types
  --> src/main.rs:17:13
   |
17 |     let y = if true { &a } else { &b };
   |             ^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `A`, found struct `B`
   |
   = note: expected type `&A`
              found type `&B`
```

It seems like adding this `let` shouldn't change anything but it seems the required type of the if statement isn't propagated unless it is directly used. The same behaviour can be found when using `func(if ...)` vs `let x = if ...; func(x)`

(sorry if this is known, I couldn't find anything)