sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: RID constructor mismatched types
Labels: bug,topic:gdscript

**Godot version:**
3.2 beta 6

**Issue description:**
The RID constructor takes an Object, but generates an error saying "No constructor of RID(Object).
Documentation says RID creates an ID for a Resource. However, passing a typed resource also creates the same error.
Maybe the docs should be updated if this is intended behaviour, because it is not clear how and what the RID object is for.

**Steps to reproduce:**
![Godot_v3 2-beta6_win64_YFWiwukEfd](https://user-images.githubusercontent.com/15088582/72286050-a3ae3300-3644-11ea-9b36-8c6613e4eff4.png)
![Godot_v3 2-beta6_win64_PvgHueZedI](https://user-images.githubusercontent.com/15088582/72286055-a6108d00-3644-11ea-805c-eab3faecd29c.png)

**Minimal reproduction project:**
[RID bug.zip](https://github.com/godotengine/godot/files/4055435/RID.bug.zip)
Repository: terminal
Issue: Feature request: Dynamic settings attribute(s) toggle
Labels: Issue-Feature,Area-Extensibility,Product-Terminal

<!-- 
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨

I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement.
2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement.
3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number).
4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement.
5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement.

All good? Then proceed!
-->

# Description of the new feature/enhancement
Recently, a few issues have popped up expressing an interest in a feature which could support the dynamic switching of the colors and styling settings attributes of an open `Profile`. The following settings attributes could be made to support dynamic switching: 
- `colorScheme` (if nothing else this is a must support)
- `foreground`
- `background`
- `backgroundImage`
- `fontSize`
- `fontFace`
- `requestedTheme`

Issues which are related to this generic feature request:
- #4176, supporting switching to a presentation mode
- #4066, supporting switching between light/dark `colorScheme`/theme
- #3687, supporting switching between `colorScheme`s (this one wants different `colorScheme` per tab, rather than all tabs of a certain profile)

<!-- 
A clear and concise description of what the problem is that the new feature would solve.
Describe why and how a user would use this new functionality (if applicable).
-->

# Proposed technical implementation details (optional)
It would make sense to implement the switching trigger as a shortcut key binding which changes the present tab's `colorScheme` to a preset scheme. When the `colorScheme` has been switched and the shortcut key is pressed again it could return to the default scheme for the tab's profile. 

Potentially this shortcut key could be bound to switch not only the `colorScheme` but also other settings attributes as well (like `fontSize`). The return to default behavior could be applied to all the switched attributes.
<!-- 
A clear and concise description of what you want to happen.
-->
Repository: storybook
Issue: CSS breaks syntax highlighting in Storybook docs
Labels: bug,compatibility with other tools,theming,addon: docs

**Describe the bug**
The CSS from the Gentellela (a bootstrap admin template) overides the .tags and pre/code css selectors which breaks the syntax highlighting in storybook docs.

gentellela include in `preview-head.html`

```html
<link href="https://cdnjs.cloudflare.com/ajax/libs/gentelella/1.4.0/css/custom.min.css" rel="stylesheet">
```

**Screenshots**
If applicable, add screenshots to help explain your problem.
![image](https://user-images.githubusercontent.com/10500823/72287490-261efe80-3615-11ea-9690-e9ccfcd13155.png)
![image](https://user-images.githubusercontent.com/10500823/72289388-025db780-3619-11ea-92e0-860a74017994.png)


**Potential Solution**
use hash classes instead of 'tag' 'text' etc...
![image](https://user-images.githubusercontent.com/10500823/72287866-d260e500-3615-11ea-88c9-dcf62b70f30a.png)


**System:**
Please paste the results of `npx -p @storybook/cli@next sb info` here.
```
Environment Info:

  System:
    OS: Linux 5.0 Debian GNU/Linux 9 (stretch) 9 (stretch)
    CPU: (4) x64 Intel(R) Core(TM) i5-7400 CPU @ 3.00GHz
  Binaries:
    Node: 11.15.0 - /usr/bin/node
    npm: 6.7.0 - /usr/bin/npm
  npmPackages:
    @storybook/addon-a11y: ^5.2.8 => 5.2.8
    @storybook/addon-docs: ^5.3.0-rc.1 => 5.3.0-rc.1
    @storybook/addon-storyshots: ^5.2.8 => 5.2.0
```

Thank you for storybook :heart: , :smile: :cat:
Repository: terminal
Issue: Pull conhost measurements with low/no future relevancy
Labels: Product-Conhost,Issue-Task,Area-Quality,Gathering-Data

After a meeting with the data team, we decided to pull a bunch of the interactivity measurements from `conhost.exe` that we're not planning on using ever again (primarily because Terminal is becoming/has become the face of user interactivity so we don't need to really measure how people are interacting with conhost.exe anymore to make a decision.)

This represents walking through the events and pulling them. We're still planning on leaving events that may influence feature decisions in the new Terminal (or help us identify people who cannot complete their workflow in Terminal and are stuck on `conhost.exe`.)
Repository: flutter
Issue: Please copy the description in the generated web/manifest.json from pubspec.yaml
Labels: c: new feature,tool,platform-web,P2,team-web,triaged-web

In the `web/manifest.json` that is generated by `flutter create`, please copy the description from `pubspec.yaml`.

/cc @RedBrogdon
Repository: go
Issue: proposal: net/http: add accessor for number of listeners and connections
Labels: Proposal,FeatureRequest

Hi,
running a http/server it would be helpfully to know the count of listeners and connections, for monitoring reasons. The server already has the fields **listeners** and **activeConn**.  What about adding methods like _GetCurrentListenersCount_ and _GetActiveConnectionsCount_?
Repository: pytorch
Issue: Idempotency Keys for RPC Retry
Labels: triaged,module: rpc

Implement Idempotency Keys to ensure we can safely retry RPC's with functions that aren't idempotent (such as RPC's from user code like UDF's).

These keys must also be flushed at some regular time intervals (otherwise this may use far too much memory).

Parent Issue: #32119

cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @gqchen @aazzolini @rohan-varma @xush6528 @jjlilley @osalpekar
Repository: PowerToys
Issue: Make windows Acrylic / Transparent 
Labels: Idea-New PowerToy

# Summary of the new feature/enhancement

It would be so awesome (if not necessarily easy to code) to be able to select areas of ANY application that you wanted to make acrylic.

Example: "Acrylicize" Outlook so that everything but the list of messages and the message frame was transparent with a blurred background to help focus the user on what matters (just the next evolution from using the dark theme with it).

# Proposed technical implementation details

Such a PowerToy would allow:

1. Selecting an app
1. Selecting one or more areas to modify
1. Seting transparency, blur, tint, and/or other visual effects to be applied to the objects seen through those elements, possibly with some presets like "Windows Acrylic", of course
1. Selecting what the transparent areas reveal:
   1. The applications beneath it (the way Windows does such things currently)
   1. The desktop background (act as if applications beneath it do not exist)
   1. The applications beneath it when not maximized and the desktop background when maximized (I suggest this be the default because it's awesome)
1. Enabling/disabling per app (and remember settings while disabled)
1. Resetting settings per app (to go back to defaults in case things get weird)
1. Changes to be saved across application close/open and system restarts, of course.
1. Starting automatically with Windows as a service, etc.

A user should never have to draw areas that should be affected but rather select existing window elements both on classic/legacy applications and UWP apps, just as developers are currently used to doing when using "developer mode" on all modern browsers.

This will obviously cause some serious redraw and possibly some performance issues, so there should probably be warnings to that effect.
Repository: flutter
Issue: Ensure Android embedding v2 works with Dart callback registration
Labels: platform-android,engine,P2,team-android,triaged-android

An issue was found with the `android_alarm_manager` that exposed the following detail about the v2 Android embedding:

> The plugin was attempting to perform the callback lookup before an instance of FlutterEngine was created. However, the callback cache isn't populated until FlutterMain::Init is called, so we querying an empty map resulting in a failed lookup. We should probably check that the cache has actually been initialized when a lookup request has been issued and then throw or assert after outputting a message stating that a FlutterEngine instance must be created before performing a callback lookup.

As reported here: https://github.com/flutter/flutter/issues/47406

This ticket is to work with @bkonyi to determine what, if anything, should be altered in the v2 embedding to help Dart callback registration play nice with the v2 embedding.
Repository: pytorch
Issue: Slighty out of tolerance for `test_mv` and `test_cholesky_solve_batched_cuda_float64`
Labels: module: tests,triaged

## 🐛 Bug

<!-- A clear and concise description of what the bug is. -->
Seeing these two failures when running `test/test_torch.py`

```
======================================================================
FAIL: test_mv (__main__.TestTorch)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "test_torch.py", line 848, in test_mv
    _test_mv(torch.randn(100, 100, dtype=torch.float32), torch.randn(100, dtype=torch.float32))
  File "test_torch.py", line 846, in _test_mv
    self.assertEqual(res1, res2)
  File "/home/jenkins/pytorch/test/common_utils.py", line 859, in assertEqual
    assertTensorsEqual(x, y)
  File "/home/jenkins/pytorch/test/common_utils.py", line 829, in assertTensorsEqual
    self.assertLessEqual(max_err, prec, message)
AssertionError: tensor(1.0014e-05) not less than or equal to 1e-05 :

======================================================================
FAIL: test_cholesky_solve_batched_cuda_float64 (__main__.TestTorchDeviceTypeCUDA)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/jenkins/pytorch/test/common_utils.py", line 678, in wrapper
    method(*args, **kwargs)
  File "/home/jenkins/pytorch/test/common_device_type.py", line 197, in instantiated_test
    result = test(self, device_arg, dtype)
  File "/home/jenkins/pytorch/test/common_device_type.py", line 337, in dep_fn
    return fn(slf, device, *args, **kwargs)
  File "/home/jenkins/pytorch/test/common_device_type.py", line 337, in dep_fn
    return fn(slf, device, *args, **kwargs)
  File "test_torch.py", line 7518, in test_cholesky_solve_batched
    cholesky_solve_batch_helper((5, batchsize), (batchsize, 5, 10), upper)
  File "test_torch.py", line 7515, in cholesky_solve_batch_helper
    self.assertLessEqual(b.dist(torch.matmul(A, x_act)), 2e-12)  # Correctness check
AssertionError: tensor(2.0572e-12, device='cuda:0', dtype=torch.float64) not less than or equal to 2e-12
```

## To Reproduce

Steps to reproduce the behavior:

1. Build from source on ppc64le
2. Run `test/test_torch.py`

<!-- If you have a code sample, error messages, stack traces, please provide it here as well -->

## Expected behavior

The tests should pass

## Environment

Please copy and paste the output from our

PyTorch version: N/A
Is debug build: N/A
CUDA used to build PyTorch: N/A

OS: Ubuntu 18.04.2 LTS
GCC version: (Ubuntu 7.3.0-27ubuntu1~18.04) 7.3.0
CMake version: Could not collect

Python version: 2.7
Is CUDA available: N/A
CUDA runtime version: Could not collect
GPU models and configuration: 
GPU 0: Tesla V100-SXM2-16GB
GPU 1: Tesla V100-SXM2-16GB
GPU 2: Tesla V100-SXM2-16GB
GPU 3: Tesla V100-SXM2-16GB

Nvidia driver version: 440.33.01
cuDNN version: Could not collect


## Additional context

I'm with IBM and we have a bunch of Power systems we can test things out on if you guys have suggestions
Repository: create-react-app
Issue: Build a CLI interface for `react-scripts`
Labels: issue: proposal,needs triage

### Is your proposal related to a problem?

Currently, `react-scripts` is just a simple "script", with almost zero arguments/flags.

```
$ yarn run react-scripts 
Unknown script "undefined".

$ yarn run react-scripts --help
Unknown script "--help".
```

This can cause

1. Make users confusing without `--help`
2. Difficult to add more features. For example, I want to build my project with a NODE_ENV value different than "production". With a CLI interface, I can use something like `vue-cli-service build --env test` to present this feature.

A complete CLI interface can solve these issues. 

### Describe the solution you'd like

<!--
  Provide a clear and concise description of what you want to happen.
-->


Maybe we can choose a famous npm package to implement it. 

[commander](https://github.com/tj/commander.js) for example, who has already been installed by `react-scripts`: `react-scripts` > `html-webpack-plugin` > `html-minifier` > `commander`

And of course, there are many other options in the JS world.

### Describe alternatives you've considered

<!--
  Let us know about other solutions you've tried or researched.
-->

N/A

### Additional context

<!--
  Is there anything else you can add about the proposal?
  You might want to link to related issues here, if you haven't already.
-->

N/A
Repository: pytorch
Issue: torch.nn.functional.normalize epsilon too small for half precision
Labels: module: numerical-stability,module: nn,triaged,module: half,module: norms and normalization

`torch.nn.functional.normalize` uses an epsilon of 1e-12. This value is too small for half precision and gets evaluated as zero (`torch.HalfTensor([1e-12]) == 0`). This causes nans in half precision when the norm is evaluated as zero. This should be fixable by increasing the epsilon to 1e-6.

cc @albanD @mruberry
Repository: flutter
Issue: "flutter build ios-framework" version check for generating podspec should happen during command validation
Labels: platform-ios,tool,a: existing-apps,P3,team-ios,triaged-ios

## Steps to Reproduce

1. Check master channel of Flutter.  Make sure it's not tagged by a version (dev, beta, etc).
1. In an add-to-app Flutter module, run:
```
flutter build ios-framework --xcframework --cocoapods --no-universal --output=/Users/m/Projects/MyApp/Flutter 
```

**Expected results:** <!-- what did you want to see? -->
Fail immediately:
```
$flutter build ios-framework --xcframework --cocoapods --no-universal --output=/Users/m/Projects/MyApp/Flutter 
--cocoapods is only supported on the dev, beta, or stable channels. Detected version is 1.13.9-pre.69
```

**Actual results:** <!-- what did you see? -->
Started building, deleted the output directory, then failed.
```
flutter build ios-framework --xcframework --cocoapods --no-universal --output=/Users/m/Projects/MyApp/Flutter 
Building framework for com.example.flutterapp in debug mode...
 ├─Creating Flutter.podspec...                                       0ms
--cocoapods is only supported on the dev, beta, or stable channels. Detected version is 1.13.9-pre.69
Repository: flutter
Issue: Avoid unnecessary syscall to get current time in MessageLoopFuchsia::WakeUp.
Labels: customer: fuchsia,engine,platform-fuchsia,P2,team-engine,triaged-engine

[`MessageLoopFuchsia::Wakeup`](https://github.com/flutter/engine/blob/fb526223045198114ee328c25b748b075b07abac/fml/platform/fuchsia/message_loop_fuchsia.cc#L26) is implemented via `async::PostDelayedTask`. This requires the calculation of the delay by requesting the current time (via a syscall) and subtracting that from the target timepoint. That syscall can be avoided by using the target timepoint directly in `async::PostTaskForTime` instead.
Repository: pytorch
Issue: We should change DeprecationWarnings to UserWarnings in 27361
Labels: module: docs,triaged

See https://github.com/pytorch/pytorch/pull/27361

This uses DeprecationWarnings, but we usually use UserWarnings because many python versions filter DeprecationWarnings by default, making them pretty much useless.
Repository: flutter
Issue: `flutter create` doesn't create `fuchsia` directory
Labels: c: new feature,tool,platform-fuchsia,P3,team-tool,triaged-tool

We probably would want to guard this behind some flag, but there should be some way to create the necessary meta.cmx etc. via the tool.
Repository: pytorch
Issue: pin_memory may change the type of instance returned by collate_fn.
Labels: module: dataloader,triaged

## 🐛 Bug

<!-- A clear and concise description of what the bug is. -->

Setting `pin_memory=True` to dataloader sometimes converts custom classes to native python types.

## To Reproduce

I have a class representing batched data, which I inherit from `dict` as follows:

```python
class TrainingBatch(dict):
    def __init__(self, instances: List[TrainingInstance]):
        # Implement logic equivalent to `collate_fn` here.
        ...

    def to(self, *args, **kwargs):
        # Implement casting and device transfer logic here.
        ...
```

Hence `collate_fn` simply looks like this:
```python
def collate_fn(instances: List[TrainingInstance]) -> TrainingBatch:
    return TrainingBatch(instances)
```

### Main issue:

I set `pin_memory=True` to the dataloader, and here is what I get:
```python
>>> batch = next(iter(dataloader))
>>> type(batch)
<class 'dict'>
```

## Expected behaviour

```python
>>> type(batch)
<class 'TrainingBatch'>
```

## Bug:

The bug is here: https://github.com/pytorch/pytorch/blob/master/torch/utils/data/_utils/pin_memory.py#L56
This `hasttr(data, "pin_memory")` should be the first condition to be checked, so custom classes can implement their own `pin_memory` method.

## Environment

 - PyTorch Version (e.g., 1.0): v1.3.1
 - OS (e.g., Linux): Linux
 - How you installed PyTorch (`conda`, `pip`, source): `conda`
 - Build command you used (if compiling from source): None
 - Python version: 3.6.8


cc @SsnL
Repository: godot
Issue: Vulkan: GIProbe Reflection does not take sky into account
Labels: bug,topic:rendering,confirmed,topic:3d

**Godot version:**
Godot 3.2 Beta 5, Godot 4 Vulkan
**OS/device including version:**
Windows 10 64 bit
**Issue description:**
When using GIProbe the sky is not taken into account in reflections. This is most visible in metallic chrome surfaces. 

Godot 3.2 Beta 5
![Godot32_GIProbe_NoSkyInreflections](https://user-images.githubusercontent.com/11403345/72311432-a57ef300-3652-11ea-9d83-291a3788ae60.PNG)


Godot 4
![Godot4_GIProbe_NoSkyInreflections](https://user-images.githubusercontent.com/11403345/72311441-b0398800-3652-11ea-9975-31c4d0d9cdd8.PNG)



**Steps to reproduce:**
Add a plane to the scene, add a sphere with a chrome material, and add a GIProbe and bake.
**Minimal reproduction project:**
[GIProbeSkyReflections.zip](https://github.com/godotengine/godot/files/4057179/GIProbeSkyReflections.zip)
Repository: react
Issue: Bug: I shouldn't own the DOM fixtures website
Labels: Component: Build Infrastructure,Type: Needs Investigation

Some folks at Google are helping us to think through some ideas to help our input code be more sane, and we discovered that our DOM Text Fixtures site (http://react-dom-fixtures.surge.sh) was both:

- _Very_ out of date
- Owned by me

Both seem fixable. However I think a good first start is to figure out a way to publicly host the fixtures where I am not a bottleneck.

What do you think? Could we setup a deploy process - maybe with netlify - to deploy the fixtures automatically?
Repository: TypeScript
Issue: Don't escape valid Unicode characters in strings
Labels: Bug,Help Wanted,Effort: Difficult

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Even if you think you've found a *bug*, please read the FAQ first, especially the Common "Bugs" That Aren't Bugs section!

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ

Please fill in the *entire* template below.
-->

<!--
Please try to reproduce the issue with the latest published version. It may have already been fixed.
For npm: `typescript@next`
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly
-->
**TypeScript Version:**  3.7.4

**Code**

```ts
const sf = createSourceFile(
  'aaa',
  'const a: string = "哈哈"',
  ScriptTarget.Latest
)
// try to do sth in transfrom.
const result = transform(sf, [])
const printer = createPrinter()
const printed = printer.printNode(
  EmitHint.SourceFile,
  result.transformed[0],
  sf
)
console.log(printed)
```

**Expected behavior:**
const a: string = "哈哈"

**Actual behavior:**
const a: string = "\u54C8\u54C8";

I am trying to use compiler api to do some transform.  but the Printer seems could not generate the decoded unicode characters. wonder how to do this right?
Repository: TypeScript
Issue: JSDoc support for @memberof and @namespace
Labels: Suggestion,Awaiting More Feedback,Domain: JSDoc

I work on a NodeJS Javascript codebase which uses plain JSDoc (i.e. no Typescript/Closure specific syntax). It uses `require()` rather than ES6/Typescript-style imports.

Our codebase has JDoc'ed code which lives under arbitrary `@namespace` declarations, meaning they do not correspond to actual code 'namespaces'. For example our code is JSDoc'ed as `@namespace utilities` but the module may be imported as `utils`.

My colleagues using Webstorm get the full JSDoc annotations/code completion/tooling but VSCode Intellisense does not recognised references like `models.Account` for e.g. parameters as shown below ...

```
// models.js

/** @namespace models */

/** @memberof models */
class Account {
  // ...
}

module.exports = { Account }
```
```
// main.js
const { Account } = require('./models')

/**
 * @return {models.Account}
 */
myMethod (account) => {
  return new Account()
}
```

Since basically the entire codebase is namespaced, I get reduced Intellisense support for my custom code and no support for writing correct JSDocs.
Repository: rust
Issue: std::fs: change ownership or Improvements for UNIX Domain Socket creation.
Labels: T-libs-api,C-feature-request,A-io,A-filesystem

https://gitlab.com/cheako/files-rs/blob/c993fc0ce90fcacc1b8821035027baf623366ab8/src/main.rs#L72-127

If there was an interface to assist with changing ownership that would make this code nicer.  I can only speak about UNIX systems, not including Mac and even then only about using libc.