sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: TypeScript
Issue: In the generated description file, the module path needs to be modified to a relative path.
Labels: Needs Investigation

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Please read the FAQ first, especially the "Common Feature Requests" section.

-->

## Search Terms
description file, paths, baseURL, relative path 

## Suggestion
In the case where compilation parameters `--paths` and `--baseURL` are enabled

#9910 
>The compiler does not rewrite module names. module names are considered resource identifiers, and are mapped to the output as they appear in the source
>
>The module names you write are not going to change in the output. the "paths" and "baseURL" are there to tell the compiler where they are going to be at runtime.

This will cause the generated description file to be invalid.

In most cases, `--paths` and `--baseURL` are used to facilitate the import of source code modules without the use of very awkward relative paths.

I think the description file needs to convert the path map into a relative path as much as possible. Because the description file does not have a runtime environment, and there is no special packaging tool.

---

Related bugs: Inferring the type generated description file, fixed issue with import path.

in typescript 3.0.1:
https://github.com/ZSkycat/issue-typescript-20180821/blob/b29f377029aa8d0b1022bd2f703a7773389a760b/dist/types/deep/deep/factory.d.ts#L3

in typescript 3.1.0-dev.20180818:
https://github.com/ZSkycat/issue-typescript-20180821/blob/master/dist/types/deep/deep/factory.d.ts#L3

## Use Cases
https://github.com/ZSkycat/issue-typescript-20180821

This is a use case for packaging into a commonjs module using webpack.

path mapping config:
```
// webpack.config.js
resolve: {
    alias: {
        src: path.resolve('./src'),
    },
},
```
```
// tsconfig.json
"baseUrl": ".",
"paths": {
    "src/*": ["./src/*"],
},
```

This will cause the generated description file to be unusable.

https://github.com/ZSkycat/issue-typescript-20180821/blob/master/dist/types/deep/deep/factory.d.ts#L1
![image](https://user-images.githubusercontent.com/20368649/44361144-97758300-a4ef-11e8-9686-f5a85faf7c78.png)


## Examples

<!-- Show how this would be used and what the behavior would be -->

## 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. new expression-level syntax)
Repository: godot
Issue: Wasted Space  "Preview" in Theme->Edit->Label->Styles
Labels: enhancement,topic:editor,usability

https://github.com/godotengine/godot/commit/d88d0d457d2828db2016f4854efff8c5f8b90e91

The "Preview" in Theme->Edit->Label->Styles takes so much space and is a duplicate information.

Is there any useful use case for that in Themes?

![image](https://user-images.githubusercontent.com/4741886/44365840-27ed9c80-a4cb-11e8-97f6-e40a1a635ed8.png)

![image](https://user-images.githubusercontent.com/4741886/44365816-1c01da80-a4cb-11e8-8940-252bd56e2313.png)

![image](https://user-images.githubusercontent.com/4741886/44365869-39cf3f80-a4cb-11e8-83ee-7f2d66060928.png)

![image](https://user-images.githubusercontent.com/4741886/44365803-11474580-a4cb-11e8-8a0b-39c14c1d721f.png)
Repository: puppeteer
Issue: DNT Header does not populate navigator.doNotTrack
Labels: feature,upstream,chromium

Env:
MacBook, Node v10.8.0
├─ puppeteer-har@1.0.2
├─ puppeteer@1.7.0

Issue:
Adding DNT Header doesn't populate navigator.doNotTrack. Please let me know if you have any questions. I was also having trouble activating this using the chrome modHeader extension. I only had luck activating navigator.doNotTrack by changing privacy settings for my user in chrome (not chromium).
```javascript 
// in async function
const headerOptions = ['1', '0'];
for (header of headerOptions) {
    for (url of urls) {
      try {
        await page.setExtraHTTPHeaders({'DNT': header})
        await page.goto(`${hostName}${url}`, {timeout: 35000, waitUntil: ['networkidle0', 'load']});
        await page.waitFor(500);
        const doNotTrackValue = await page.evaluate(() => navigator.doNotTrack || window.doNotTrack || navigator.msDoNotTrack);
        const currentURL = await page.url();
        data.push([currentURL, doNotTrackValue]);
      } catch (e) {
        console.log(e)
      }
    }
    fs.writeFileSync(`./domState${header}.json`, JSON.stringify(data), {flags: 'w'});
  }
```

I expected `navigator.doNotTrack` to equal '1' or '0' depending on the iteration

instead `navigator.doNotTrack` equals null
Repository: vscode
Issue: [themes] Allow custom variables and references in workbench color customizations section
Labels: feature-request,themes

This is a feature request to allow defining custom color variables in the workbench color customizations section. It would allow creating a small palette of colors and reusing it across the workbench color definitions, saving many repetitions and making it much easier to maintain.

This is just simple text substitution based on some naming convention like the .less `@variable` convention. For example, see the `@PaletteXXX` variables in the sample below:

```
"workbench.colorCustomizations": {

      // custom colors
      "@Palette000": "#FFFFFF",
      "@Palette050": "#ECEFF1",
      "@Palette100": "#CFD8DC",
      "@Palette200": "#B0BEC5",
      "@Palette300": "#90A4AE",
      "@Palette700": "#455A64",

      // input control
      "input.background": "@Palette000",
      "input.foreground": "@Palette700",
      "input.placeholderForeground": "@Palette200",
      "inputOption.activeBorder": "@Palette300",
      "input.border": "@Palette100",

      // list views
      "list.activeSelectionBackground": "@Palette200",
      "list.activeSelectionForeground": "@Palette700",
      "list.inactiveSelectionBackground": "@Palette100",
      "list.hoverBackground": "@Palette100",
      "list.dropBackground": "@Palette100",
      "list.focusBackground": "@Palette100",

```
Repository: rust
Issue: rustdoc: Add crate=crate_name,file=filename.rs options to doctests for displaying in output
Labels: T-rustdoc,C-feature-request

Sometimes we write code samples where the crate the example is in and/or the file the example is in matters. Right now we just have to include that information outside of the code sample, but it can be easier to read (especially for people just looking at the example code) if it's included in the example itself. As such, I'm suggesting adding two more attributes to the doctests, `crate` and `file`. When actually running doctests, these are ignored, but when displaying in the output, are shown inside the example block.

For prior art, this is done a lot in hard print books. For example, page 5 of https://nostarch.com/download/samples/Realm_ch14.pdf shows the filename on the top right of the examples.

cc @QuietMisdreavus @alercah @GuillaumeGomez
Repository: go
Issue: cmd/compile: Fannkuch benchmark performance regression
Labels: Performance,NeedsInvestigation,compiler/runtime

Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?
go version go1.11rc1 darwin/amd64

### Does this issue reproduce with the latest release?
No.

### What operating system and processor architecture are you using (`go env`)?
macOS 10.13.6 (darwin/amd64)

### What did you do?
tested the benchmark at:

https://benchmarksgame-team.pages.debian.net/benchmarksgame/program/fannkuchredux-go-1.html

using 1.10.3 and 1.11rc1 with:

time go run fannkuchredux.go 12
time go1.11rc1 run fannkuchredux.go 12

results:
1.10.3: go run fannkuchredux.go 12  **44.65s** user 0.21s system 372% cpu **12.033** total
1.11rc1: go1.11rc1 run fannkuchredux.go 12  **57.70s** user 0.24s system 373% cpu **15.528** total

### What did you expect to see?
1.11rc1 timings closer to 1.10.3

### What did you see instead?
1.11rc1 timings slower than 1.10.3
Repository: pytorch
Issue: [feature request][caffe2] extend FC/FCTranspose op to handle 2d bias.
Labels: caffe2

Currently, FC/FCTranspose only accepts 1d bias. The FC's implementation will do the broadcast to create the 2d bias from 1d bias, but we could just provide the whole 2d bias. Then, we can do the better optimization for onnx Gemm op with caffe2 backend.

I will try to implement this idea and create a pull request later.

@houseroad @bddppq
Repository: pytorch
Issue: size mismatch when trying to reconstruct predifined network
Labels: triaged,module: vision

I tried resnet18 and vgg13, both cases return similar error. is there anything I missed?

```
import torch 
from torchvision.models import resnet18, vgg13
import torch.nn as nn
import numpy as np
from collections import OrderedDict

input_size = (10, 3, 224, 224)

def GetSelf(model):
    # l = list(model.named_children())[:-1]
    l = list(model.named_children())
    d = OrderedDict(l)
    return nn.Sequential(d)
 
# m1 = vgg13(pretrained=False)    
m1 = resnet18(pretrained=False)
m2 = GetSelf(m1)
inputs = np.random.random(input_size).astype(np.float32)
inputs = torch.from_numpy(inputs)

if torch.cuda.is_available():
    m1.cuda()
    m2.cuda()
    inputs = inputs.cuda()
with torch.no_grad():
    o1 = m1(inputs)
    o2 = m2(inputs)
    o1 = o1.cpu().numpy() if torch.cuda.is_available() else o1.numpy()
    o2 = o2.cpu().numpy() if torch.cuda.is_available() else o2.numpy()
```


```
  File "<ipython-input-12-044c200d14f5>", line 1, in <module>
    runfile('C:/Users/Administrator/Desktop/a.py', wdir='C:/Users/Administrator/Desktop')

  File "D:\Program Files\Anaconda3\lib\site-packages\spyder\utils\site\sitecustomize.py", line 866, in runfile
    execfile(filename, namespace)

  File "D:\Program Files\Anaconda3\lib\site-packages\spyder\utils\site\sitecustomize.py", line 102, in execfile
    exec(compile(f.read(), filename, 'exec'), namespace)

  File "C:/Users/Administrator/Desktop/a.py", line 27, in <module>
    o2 = m2(inputs)

  File "D:\Program Files\Anaconda3\lib\site-packages\torch\nn\modules\module.py", line 477, in __call__
    result = self.forward(*input, **kwargs)

  File "D:\Program Files\Anaconda3\lib\site-packages\torch\nn\modules\container.py", line 91, in forward
    input = module(input)

  File "D:\Program Files\Anaconda3\lib\site-packages\torch\nn\modules\module.py", line 477, in __call__
    result = self.forward(*input, **kwargs)

  File "D:\Program Files\Anaconda3\lib\site-packages\torch\nn\modules\linear.py", line 55, in forward
    return F.linear(input, self.weight, self.bias)

  File "D:\Program Files\Anaconda3\lib\site-packages\torch\nn\functional.py", line 1026, in linear
    output = input.matmul(weight.t())

RuntimeError: size mismatch, m1: [5120 x 1], m2: [512 x 1000] at c:\new-builder_3\win-wheel\pytorch\aten\src\thc\generic/THCTensorMathBlas.cu:249
```

cc @fmassa @vfdev-5
Repository: angular
Issue: Animation trigger with params won't work without a value
Labels: type: bug/fix,area: animations,freq2: medium,P3

<!--
## I'm submitting a...
<!-- Check one of the following options with "x" -->
<pre><code>
[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report  <!-- Please search GitHub for a similar issue or PR before submitting -->
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
[ ] Other... Please describe:
</code></pre>

So i have the following template:

```
    <div *ngFor="let image of chapterImages | async"
         [@image]="chapterAnimation">...</div>
```

And in the component:

```
  animations: [
    trigger('image', [
      transition(':enter', [
        style({ transform: 'translateX({{enter}})' }),
        animate('0.7s ease-in-out', style({ transform: 'translateX(0)' }))
      ], { params: { enter: '0%' } }),
      transition(':leave', [
        style({ transform: 'translateX(0)' }),
        animate('0.7s ease-in-out', style({ transform: 'translateX({{leave}})' }))
      ], { params: { leave: '-100%' } })
    ])
  ]
```

```
  chapterAnimation = {
    value: 'foo',
    params: {
      enter: '100%',
      leave: '-100%'
    }
  };
```

If i leave out the ```value: 'foo'``` line, the animation WILL NOT use the provided params and just use the default params. That is the bug (took me quite a while to figure out).

Angular 6.0.7
Repository: react
Issue: UMD builds are not enabled on UNPKG
Labels: Type: Discussion

Visiting https://unpkg.com/react displays the CJS build (https://unpkg.com/react@16.4.2/index.js) when the UMD build (https://unpkg.com/react@16.4.2/umd/react.development.js) should be displayed instead. I also noticed this issue with react-dom, so I assume all packages need to be fixed.

Please refer to the usage instructions at the bottom of https://unpkg.com/.
Repository: kubernetes
Issue: cephfs fuse is not mounted in its own systemd scope
Labels: kind/bug,sig/storage,lifecycle/frozen

<!-- This form is for bug reports and feature requests ONLY!

If you're looking for help check [Stack Overflow](https://stackoverflow.com/questions/tagged/kubernetes) and the [troubleshooting guide](https://kubernetes.io/docs/tasks/debug-application-cluster/troubleshooting/).

If the matter is security related, please disclose it privately via https://kubernetes.io/security/.
-->

**Is this a BUG REPORT or FEATURE REQUEST?**:

> Uncomment only one, leave it on its own line:
>
/kind bug
> /kind feature

cephfs fuse is [not mounted in its own systemd scope](https://github.com/kubernetes/kubernetes/blob/v1.13.0-alpha.0/pkg/volume/cephfs/cephfs.go#L412), fuse daemon processes will be killed when kubelet restarts.

It should be updated to use kubelet mounter, see https://github.com/kubernetes/kubernetes/pull/49640.

/assign
Repository: vscode
Issue: "editor.hover.enabled" not showing up when searching "hint" or "info" in settings
Labels: bug,settings-editor,confirmed,settings-search

Settings parameter "editor.hover.enabled" does not convey sense.
I was search that as "hint" or "info" and find nothing.

May be change name of this setting to "editor.hoverHint.enabled?

---
Русский перевод аналогично ничего не объясняет: "... отображается ли наведение".
Может быть "... отображается ли подсказка при наведении"?
Repository: rust
Issue: Experiment with a hybrid bitfield + range encoding for Span / DefId.
Labels: C-enhancement,T-compiler,A-incr-comp,I-compilemem

Roughly, if you have a "container" (file/crate/etc.), and sequential indices in it:
* you can use `(container_index, intra_container_index)` (but that takes 2x space)
* you can split an integer's *bitwidth* into two bitfields, one for each half of the pair above
  * the point where you choose to split is a tradeoff and you can run out of either half
* you can split an integer's *range*, with each container having its sequential range
  * `Span` does this currently, where the files are effectively "concatenated"
  * requires binary search to translate into the pair representation

An improvement on all of those is to choose an arbitrary chunk size (e.g. `2^17 = 128kB` for files), and then split each container into a number of chunks (ideally just 1 in the common case).
You can then use bitfields for `(chunk, intra_chunk_index)` (e.g. `15` and `17` bits of `u32`).

The difference is that to translate `chunk` to `container`, we *don't need* to use binary search, because `chunk` is several orders of magnitude smaller than the index space as a whole, and we can use arrays.

That is, `chunk -> container` can be an array, but also, if there is per-container data that would be accessed through `chunk`, we can optimize that by building a `chunk -> Rc<ContainerData>` array.

Translating `intra_chunk_index` to `intra_container_index` is similarly easy, if you can look up per-container data, you can subtract its overall start (if each container is a contiguous range of chunks).

<hr/>

Another reason this might be useful is translating (an unified) `DefId` or `Span` between crates or between incremental (re)compilation sessions - we can have a bitset of changed chunks: if a chunk is unchanged, the index is identical, otherwise we can have an intra-chunk/container binary search for changed ranges (or just a map of changes).

We can grow the number indices within the last chunk of a container, and if we run out of space, we can relocate the container's chunks without a significant cost. Alternatively, another tradeoff we can make is to fragment a container's chunks.

<hr/>

The first step in experimenting with this would have to be take `Span`, and round up the start/end of each file's range to a multiple of a power of `2` (e.g. `2^17` - but an optimal value would require gathering some real-world file-size statistics).
This way we can see if there's a negative performance impact from having unused gaps in the index space, everything else should be an improvement.
We can also try to replace the binary searches to find the `SourceFile` a `Span` is from.

cc @nikomatsakis @michaelwoerister
Repository: pytorch
Issue: Have all C++ modules expose a __file__ attribute
Labels: module: docs,triaged,enhancement

E.g. for `torch._C._VariableFunctions`. That would make it much easier for people to find the C++ code our Python code calls into.
Repository: pytorch
Issue: [caffe2] the caffe2 operators document is too old
Labels: caffe2

The document at https://caffe2.ai/docs/operators-catalogue.html is too old. A lot of attributes are not in this page.

How to request to update this web page?
Repository: rust
Issue: Bad "Ambiguous Numeric Type" Recommendation from Compiler in for loop
Labels: C-enhancement,A-diagnostics,T-compiler

The `pow` function cannot be called on an ambiguous numeric type. If `pow` is called on the variable of a `for` loop, the compiler's recommended solution to add a concrete numeric type does not compile.

Example code with ambiguous numeric type:
```rust
pub fn check() {
    for i in 0..1000 {
        println!("{}", i.pow(2));
    }
}
```

Gives the error:
```
error[E0689]: can't call method `pow` on ambiguous numeric type `{integer}`
  --> src/lib.rs:22:26
   |
22 |         println!("{}", i.pow(2));
   |                          ^^^
help: you must specify a type for this binding, like `i32`
   |
21 |     for i: i32 in 0..1000 {
   |         ^^^^^^

error: aborting due to previous error

For more information about this error, try `rustc --explain E0689`
```

Implementing this recommendation by adding type to variable `i` as shown in the compiler recommendation and trying to compile again gives the error:
```
error: missing `in` in `for` loop
  --> src/lib.rs:21:10
   |
21 |     for i: i32 in 0..1000 {
   |          ^ help: try adding `in` here

error: expected expression, found `:`
  --> src/lib.rs:21:10
   |
21 |     for i: i32 in 0..1000 {
   |          ^ expected expression

error: aborting due to 2 previous errors
```


Not sure if there is a better solution, but adding a cast to the range rather than specifying the type of the variable worked for me:
```rust
pub fn check() {
    for i in 0..1000 as i32 {
        println!("{}", i.pow(2));
    }
}
```
Repository: pytorch
Issue: [Caffe2] Failed to build dispatch_test. Error LNK2001: unresolved external symbol
Labels: caffe2

## Issue description

Getting LNK2001 on Windows for `dispatch_test`.
```
pytorch\build\caffe2\core\dispatch\dispatch_test.vcxproj" (default target) (56) ->
(Link target) -> 
  KernelRegistration.obj : error LNK2001: unresolved external symbol "__declspec(dllimport) private: __cdecl caffe2::TypeIdentifier::TypeIdentifier(unsigned short)" (__imp_??0TypeIdentifier@caffe2@@AEAA@G@Z) [pytorch\build\caffe2\core\dispatch\dispatch_test.vcxproj]
  OpSchema.obj : error LNK2001: unresolved external symbol "__declspec(dllimport) private: __cdecl caffe2::TypeIdentifier::TypeIdentifier(unsigned short)" (__imp_??0TypeIdentifier@caffe2@@AEAA@G@Z) [pytorch\build\caffe2\core\dispatch\dispatch_test.vcxproj]
  OpSchemaRegistration.obj : error LNK2001: unresolved external symbol "__declspec(dllimport) private: __cdecl caffe2::TypeIdentifier::TypeIdentifier(unsigned short)" (__imp_??0TypeIdentifier@caffe2@@AEAA@G@Z) [pytorch\build\caffe2\core\dispatch\dispatch_test.vcxproj]
  OpSchema_test.obj : error LNK2001: unresolved external symbol "__declspec(dllimport) private: __cdecl caffe2::TypeIdentifier::TypeIdentifier(unsigned short)" (__imp_??0TypeIdentifier@caffe2@@AEAA@G@Z) [pytorch\build\caffe2\core\dispatch\dispatch_test.vcxproj]
  Dispatcher.obj : error LNK2001: unresolved external symbol "__declspec(dllimport) private: __cdecl caffe2::TypeIdentifier::TypeIdentifier(unsigned short)" (__imp_??0TypeIdentifier@caffe2@@AEAA@G@Z) [pytorch\build\caffe2\core\dispatch\dispatch_test.vcxproj]
  DispatchKey.obj : error LNK2001: unresolved external symbol "__declspec(dllimport) private: __cdecl caffe2::TypeIdentifier::TypeIdentifier(unsigned short)" (__imp_??0TypeIdentifier@caffe2@@AEAA@G@Z) [pytorch\build\caffe2\core\dispatch\dispatch_test.vcxproj]
  DispatchTable.obj : error LNK2001: unresolved external symbol "__declspec(dllimport) private: __cdecl caffe2::TypeIdentifier::TypeIdentifier(unsigned short)" (__imp_??0TypeIdentifier@caffe2@@AEAA@G@Z) [pytorch\build\caffe2\core\dispatch\dispatch_test.vcxproj]
  pytorch\build\bin\RelWithDebInfo\dispatch_test.exe : fatal error LNK1120: 1 unresolved externals [pytorch\build\caffe2\core\dispatch\dispatch_test.vcxproj]

```

## System Info
- PyTorch or Caffe2: C2
- How you installed PyTorch (conda, pip, source): src
- Build command you used (if compiling from source): cmake
- OS: Win10
- PyTorch version: master
- VS version (if compiling from source): 2017
- CMake version: 3.12
Repository: rust
Issue: Custom attribute used on thing disallowing custom attributes should say that
Labels: C-enhancement,A-diagnostics,T-compiler

crate: `custom_attr`

```rust
extern crate proc_macro;
use proc_macro::TokenStream;

#[proc_macro_attribute]
pub fn custom(_attr: TokenStream, item: TokenStream) -> TokenStream {
    item
}
```

---

crate: not the previous one

```rust
extern crate custom_attr;
use custom_attr::custom;

fn main() {
   match () {
        #[custom]
        () => {}
    }
}
```

---

Current Error

```
error[E0658]: The attribute `custom` is currently unknown to the compiler and may have meaning added to it in the future (see issue #29642)
  --> src/main.rs:LL:L
   |
L |         #[custom]
   |         ^^^^^^^^
   |
   = help: add #![feature(custom_attribute)] to the crate attributes to enable
```

---

Wanted Error

```
error[E0NNN]: Custom attributes can only be applied to items
  --> src/main.rs:LL:L
   |
L |         #[custom]
   |         ^^^^^^^^
   |
```

(I'm assuming they can only be applied to items in nightly without using feature flags in Rust today. It'd be nice to get that assumption confirmed as well)