sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: use scons compiler  R_AARCH64_LD64_GOTPAGE_LO15  errors 
Labels: bug,platform:linuxbsd,topic:buildsystem,confirmed

### Godot version

3.3.stable

### System information

GLES3

### Issue description

```
[ 94%] modules/libmodules.x11.opt.tools.64.a(godotscript_editor.x11.opt.tools.64.o): In function `Thread::get_main_id()':
/data/godot33/./core/os/thread.h:67:(.text+0x1188): relocation truncated to fit: R_AARCH64_LD64_GOTPAGE_LO15 against symbol `Thread::main_thread_id' defined in .bss section in core/libcore.x11.opt.tools.64.a(thread.x11.opt.tools.64.o)
/data/godot33/./core/os/thread.h:67: warning: Too many GOT entries for -fpic, please recompile with -fPIC
/usr/bin/ld: final link failed: Nonrepresentable section on output
collect2: error: ld returned 1 exit status
[ 94%] scons: *** [bin/godot.x11.opt.tools.64] Error 1
scons: building terminated because of errors.
```

### Steps to reproduce

```
scons p=x11 tools=yes target=release_debug bits=64 -j8
```

### Minimal reproduction project

```
[ 94%] modules/libmodules.x11.opt.tools.64.a(gdscript_editor.x11.opt.tools.64.o): In function `Thread::get_main_id()':
/data/godot33/./core/os/thread.h:67:(.text+0x1188): relocation truncated to fit: R_AARCH64_LD64_GOTPAGE_LO15 against symbol `Thread::main_thread_id' defined in .bss section in core/libcore.x11.opt.tools.64.a(thread.x11.opt.tools.64.o)
/data/godot33/./core/os/thread.h:67: warning: Too many GOT entries for -fpic, please recompile with -fPIC
/usr/bin/ld: final link failed: Nonrepresentable section on output
collect2: error: ld returned 1 exit status
[ 94%] scons: *** [bin/godot.x11.opt.tools.64] Error 1
scons: building terminated because of errors.
```
Repository: tensorflow
Issue: Support torch.nn.fold in tensorflow?
Labels: stat:contribution welcome,type:feature

This function is popular in Vision Models. 

I don't find any api function in tf that is equivalent with [torch.nn.fold](https://pytorch.org/docs/stable/generated/torch.nn.Fold.html?highlight=fold#).

So does Tensowflow already have such a function or is there a plan to do so?
Repository: pytorch
Issue: Support differentiability through clone and update
Labels: feature,module: autograd,module: nn,triaged,needs design

## 🚀 Feature
<!-- A clear and concise description of the feature proposal -->

Dear people from PyTorch,

I was reading through the Learn2Learn codebase for Meta-Learning and came across an interesting hack they had to implement.

https://github.com/learnables/learn2learn/blob/master/learn2learn/utils/__init__.py#L53

```py
    net = nn.Sequential(Linear(20, 10), nn.ReLU(), nn.Linear(10, 2))
    clone = clone_module(net)
    error = loss(clone(X), y)
    error.backward()  # Gradients are back-propagate all the way to net.
```

The second trick is implemented here: https://github.com/learnables/learn2learn/blob/master/learn2learn/utils/__init__.py#L230 to perform the update and preserve differentiability

I believe it would be interesting for PyTorch to support this natively.

Here could be the API for cloning: 

```py
model.clone(keep_differentiability=False/True)
```

Here could be the API for the function optimization API: 

```py
F.sgd(params, grads, keep_differentiability=False/True)
```


## Motivation

<!-- Please outline the motivation for the proposal. Is your feature request related to a problem? e.g., I'm always frustrated when [...]. If this is related to another GitHub issue, please link here too -->

## Pitch

<!-- A clear and concise description of what you want to happen. -->

## Alternatives

<!-- A clear and concise description of any alternative solutions or features you've considered, if any. -->

## Additional context

<!-- Add any other context or screenshots about the feature request here. -->


cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @soulitzer @Lezcano @Varal7 @mruberry @jbschlosser @walterddr
Repository: TypeScript
Issue: Should `target: es2020` set `module: es2020` by default?
Labels: Suggestion,Needs Investigation

From #44656 

>Should this function return ModuleKind.ES2020 and ES2022 following the `target` version? It seems #33893 missed this, and I wonder this needs to be fixed.
>
>https://github.com/microsoft/TypeScript/blob/5afe42e14e61d7e4df5d75cc0022283711cb593a/src/compiler/utilities.ts#L6035-L6039
Repository: axios
Issue: Maybe a bug in isURLSameOrigin function?
Labels: state::triage

#### Describe the bug

There is probably a bug in https://github.com/axios/axios/blob/7d6bddba2d8de29c263feaef4c40daa50cb4b176/lib/helpers/isURLSameOrigin.js#L56

If you pass `undefined`, the `parsed` variable becomes `undefined` and then you try to access `parsed.protocol`. Of course I wouldn't pass `undefined` intentionally, but if I have some config object and property is missing, then you get this unexpected behavior in browser.

#### To Reproduce

```js
const someConfigObject = {};
const opts = { url: someConfigObject.accidentallyNotExistingProperty };
axios(opts).then(response => console.log(response)).catch(e => console.log(e));
```

#### Expected behavior

At least error message saying that the url should be string, not undefined.

#### Environment

 - Axios Version: 0.21.4 (via https://cdn.jsdelivr.net/npm/axios/dist/axios.min.js)
 - Browser: Firefox
 - Browser Version 92.0.1

#### Additional context/Screenshots
...
Repository: pytorch
Issue: I am getting undefined symbol: _ZN5torch3jit17parseSchemaOrNameERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE error. This I am getting when I am trying to "import torch from nemo.collections import nlp". I am trying to use pytorch ngc container 21.05. I tried to import torch before the nemo extension. Please suggest how I can resolve this.
Labels: oncall: jit

## ❓ Questions and Help

### Please note that this issue tracker is not a help form and this issue will be closed.

We have a set of [listed resources available on the website](https://pytorch.org/resources). Our primary means of support is our discussion forum:

- [Discussion Forum](https://discuss.pytorch.org/)
Repository: pytorch
Issue: C++ extensions don't correctly set USE_C10D_FOO preprocessor macros
Labels: oncall: distributed

## 🐛 Bug

Some header files (such as [ProcessGroupNCCL.hpp](https://github.com/pytorch/pytorch/blob/master/torch/csrc/distributed/c10d/ProcessGroupNCCL.hpp)) are "gated" by a preprocessor macro (like `USE_C10D_NCCL`). When that macro is unset, the header "looks empty". PyTorch's own CMake files set these macros based on the config and some automatic feature tests, and propagate them to all dependent CMake targets. However, when building a C++ extensions these macros aren't set. Thus a C++ extension cannot use these macros to check for the availability of some features, nor can it reliably include headers that make use of these macros.

## To Reproduce

Steps to reproduce the behavior:

1. Create a C++ extension
1. Add `#include <c10d/ProcessGroupNCCL.hpp>`
1. Try using the `c10d::ProcessGroupNCCL` class

## Expected behavior

The C++ extension build system should set these preprocessor macros according to the value they have in the PyTorch installation.

## Additional context

To be honest, though, it's probably a bad idea to require these macros be set "from the outside" (i.e., to be specified in the compiler invocation via `-DFOO=1`). A more robust approach could be to auto-generate a `c10d/Config.hpp` header file during the build, based on a template, where we materialize the value that these macros had in CMake, and then this header can be included by all files that need those macros.

cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @SciPioneer @H-Huang
Repository: kubernetes
Issue: Incorrect Priority Level for kube-proxy/node-problem-detector/konnectivity-server/glbc
Labels: kind/bug,sig/api-machinery,sig/auth,triage/accepted

#### What happened:
Currently, requests from multiple components go to global-default Priority Level:
- kube-proxy
- node-problem-detector
- konnectivity-server
- glbc

#### What you expected to happen:
I expected requests assigned to workload-low or workload-high Priority Level
#### How to reproduce it (as minimally and precisely as possible):
Logs confirming issue taken from https://k8s-testgrid.appspot.com/sig-scalability-gce#gce-master-scale-performance job:
kube-proxy:
```
"HTTP" verb="GET" URI="/api/v1/nodes?fieldSelector=metadata.name%3Dgce-scale-cluster-minion-group-1-gxj1&limit=500&resourceVersion=0" latency="1.36583ms" userAgent="kube-proxy/v1.23.0 (linux/amd64) kubernetes/6f47878" audit-ID="dcde2865-8562-4d2d-9384-c1679543ebec" srcIP="10.40.8.85:54464" apf_pl="global-default" apf_fs="global-default" apf_fd="system:kube-proxy" resp=200
```
node-problem-detector:
```
"HTTP" verb="GET" URI="/api/v1/nodes/gce-scale-cluster-minion-group-3-3bcw" latency="5.586004ms" userAgent="node-problem-detector/v0.8.9" audit-ID="e3950e20-5af1-4db2-a4db-4208e7a2910a" srcIP="10.40.8.153:35150" apf_pl="global-default" apf_fs="global-default" apf_fd="system:node-problem-detector" resp=200
```
konnectivity-server:
```
"HTTP" verb="POST" URI="/apis/authentication.k8s.io/v1/tokenreviews" latency="1.21476ms" userAgent="proxy-server/v0.0.0 (linux/amd64) kubernetes/$Format" audit-ID="d7329045-32fc-4354-85c7-c75cb1b19ca7" srcIP="[::1]:41986" apf_pl="global-default" apf_fs="global-default" apf_fd="system:konnectivity-server" resp=201
```
glbc:
```
"HTTP" verb="GET" URI="/api/v1/namespaces/test-5jtsix-3/services/medium-service-9" latency="5.498ms" userAgent="glbc/v0.0.0 (linux/amd64) kubernetes/$Format" audit-ID="00bed3ac-2efc-4506-ba4a-b29bb077a9c2" srcIP="[::1]:41830" apf_pl="global-default" apf_fs="global-default" apf_fd="system:controller:glbc" resp=200
```
#### Anything else we need to know?:

#### Environment:
- Kubernetes version (use `kubectl version`):
- Cloud provider or hardware configuration:
- OS (e.g: `cat /etc/os-release`):
- Kernel (e.g. `uname -a`):
- Install tools:
- Network plugin and version (if this is a network-related bug):
- Others:
Repository: opencv
Issue: Extension of denoising algorithm to 32bits
Labels: feature,priority: low,category: photo

I'm using opencv for astronomy software. It works well and I'm happy of that.
I would like to add denoising algorithms however it is not possible for now.

Indeed, methods that are implemented only work on 8 or 16 images. In astrophotography one need to work on 32bits floatting point images.

I've seen there is some ticket, opened in 2015 requesting to extend some algorithm to 16bits (#4914) or another one (#13924) more recent asking to work in a better precision than 8bits.

Indeed, 32bits floatting point seems to be a precision that need to be handled by a library like opencv. However, as the opened ticket are quite old, maybe it is not your priority?

May I ask you if it could be possible to add such a feature?

Cheers
Repository: godot
Issue: Add a way to manually pop down the virtual keyboard after it was displayed
Labels: enhancement,platform:android,topic:porting,usability

### Godot version

3.3.3 stable

### System information

Windows 10, 2 x RTX 2070 Super

### Issue description

When using lineEdit and textEdit nodes, the Android keyboard pops up but there isn't any way to pop it back down. Like for example, if you open up Chrome in Android and type in the URL, you get an arrow sign in the bottom right part of the keyboard that does the job of 'pressing enter' and pops down the keyboard automatically. When using godot made game/app, we get a 'line break' option that shifts the curson to a new line. Getting the 'press enter and pop down the keyboard' key is not available when using keyboard with Godot made game/app for Android (and probably iOS too).

We can hide the keyboard by pressing the back button, but on many newer Android devices, the home screen buttons get hidden by default when running an app or a game. So to press back, we have to first slide upwards on the screen to reveal the home screen buttons and then press the back button. While sliding upwards to reveal the home screen buttons, a sliding gesture may get inputted into the game or a touch screen button may take the input, which is not a desirable user experience.

### Steps to reproduce

-Add line edit or text edit node to a Node2D.
-Export it to Android.
-Type in anything into the field and try hiding the keyboard.

### Minimal reproduction project

_No response_
Repository: rust
Issue: Can't fail a test with my custom error message without the panic boilerplate
Labels: A-diagnostics,A-libtest,C-bug,A-error-handling,T-testing-devex

<!-- Thanks for filing a 🐛 bug report 😄! -->

**Problem**
Hi there. In certain cases when failing a test run with cargo, I need to display a custom error message.
There doesn't seem to be a way to do this without displaying the whole panic boilerplate. For various reasons I'm running with `RUST_BACKTRACE=1`, so this also displays the full backtrace and makes the custom error very hard to find (especially in CI).

**Steps**

1. Write this test:
```rust
#[test]
fn foo () -> Result<(), String> {
    Err("aaa!!!".to_owned())
}
```
2. Get this output:
```
running 1 test
test foo ... FAILED

failures:

---- foo stdout ----
Error: "aaa!!!"
thread 'foo' panicked at 'assertion failed: `(left == right)`
  left: `1`,
 right: `0`: the test returned a termination value with a non-zero status code (1) which indicates a failure', /rustc/a178d0322ce20e33eac124758e837cbd80a6f633/library/test/src/lib.rs:193:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace


failures:
    foo
```
3. I would really like to get this output instead:
```
running 1 test
test foo ... FAILED

failures:

---- foo stdout ----
aaa!!!

failures:
    foo
```

Output of `cargo version`:
cargo 1.54.0 (5ae8d74b3 2021-06-22)
Repository: storybook
Issue: custom 404 page
Labels: feature request

**Is your feature request related to a problem? Please describe**
We recently moved [our documentation](https://d3plus.org/) to Storybook from a Github Pages site, and the 404 page that is displayed for the older now non-existent routes leaves a little bit to be desired design-wise...

**Describe the solution you'd like**
Either an add-on or core functionality that lets us supply a custom HTML or Image to be displayed for 404 routes.

**Are you able to assist to bring the feature to reality?**
Yes, but I am unfamiliar with the internal codebase of Storybook.

**Additional context**
Current 404 page:
<img width="1306" alt="Screen Shot 2021-09-30 at 11 16 41 AM" src="https://user-images.githubusercontent.com/1847581/135483289-2e6da394-7b87-4601-b907-a8e010892837.png">
Repository: terminal
Issue: VS devshell generator should prefer using powershell core if available
Labels: Help Wanted,Area-Settings,Product-Terminal,Issue-Task

moved from https://github.com/microsoft/terminal/pull/11326#issuecomment-930690887
# Description of the new feature/enhancement
use pwsh for the devshell command on the visual studio generators
Repository: terminal
Issue: Bug: Quake mode (globalSummon) animation with dropdownDuration=0
Labels: Help Wanted,Needs-Repro,Issue-Bug,Product-Terminal,Priority-3,Area-Windowing

### Windows Terminal version (or Windows build number)

1.10.2383.0

### Other Software

Windows 1909 (build 18363), might be relevant for repro since it's about the actual window.

### Steps to reproduce

Add the following action to `settings.json` under `"actions"`:
```json
{ "keys": "win+`", "command": { "action": "globalSummon", "name": "_quake", "dropdownDuration": 0 } },
```
First press <kbd>Win</kbd>+<kbd>`</kbd> to launch the quake window.

Then press it again to hide, and another time to show the quake window, and notice the show/hide animations.

### Expected Behavior

Both the hide and show animations should be instant, no animation should play and the window should appear and disappear instantly.

### Actual Behavior

The hide animation works as expected, but the show animation is no longer a reveal from above but rather a zoom out and pan (to top left) for some reason.

Changing `"dropdownDuration"` to 1 instead of 0 works as expected, a workaround.

If it doesn't repro for you, perhaps the Windows version is important.
Repository: pytorch
Issue: [POLL][RFC] DataParallel Deprecation
Labels: triaged,module: deprecation

Hey everyone,

We wanted to let you know that we are considering the deprecation of DataParallel (`torch.nn.DataParallel`, a.k.a. DP) module with the upcoming v1.11 release of PyTorch. Our plan is to keep DataParallel in maintenance mode for the 12 months following the v1.11 release and afterwards completely remove it from our code base. No matter whether we follow this plan or not, we still highly encourage everyone relying on DataParallel to onboard with the Distributed Data Parallel (`torch.distributed`, a.k.a. DDP) module as we consider it the future of PyTorch Distributed. Your feedback is very important to us, so please let us know your thoughts.

--

**Why should I use DDP over DP?**
DDP is a faster and scalable alternative to DP. It is in active development, has a clear roadmap, and represents the future of PyTorch Distributed. DP was our first attempt to data parallel training, but over time due to its inefficiency and lack of some key features such as multi-node training fell into disuse. Today a big majority of our users have already migrated to DDP. We ask our remaining users to migrate in the near future so that we can dedicate all our resources to DDP.

**I use DP on a single multi-GPU machine. Why do I to have to use a “distributed” API?**
DDP can be used on a single machine as well. In fact it is faster than DP on a single machine with multiple GPUs since it avoids Python’s GIL.

**How is DDP faster than DP?**
DP uses multi-threaded parallelism, while DDP uses multi-process parallelism. Due to Python’s infamous GIL contention across threads, the collective operations of DP introduce a lot of overhead and are universally slower than their DDP counterparts. Moreover DP repeatedly copies model parameters between the threads which introduces yet another overhead.

**But DP is a lot easier to use, DDP requires me to write additional code to set it up. Is there a way to avoid it?**
We are actively working on filling any usability gaps between the two APIs and aim to have parity in the following months before the removal of DP. Also note that DDP comes with a launcher script (see [here](https://pytorch.org/docs/stable/elastic/quickstart.html)) that handles most of the boilerplate code. In the meantime if you have any suggestions, feel free to reach out to us.

--

If you have any specific questions, please let us know below. Going forward we will actively monitor this post and try to address any concerns, suggestions, or feedback you have.

Thank you,
PyTorch Distributed Team

cc @mrshenli @pritamdamania @rohan-varma @vitaly-fedyunin @ngimel @bowangbj
Repository: go
Issue: x/pkgsite: possible change in how example links work
Labels: NeedsInvestigation,pkgsite

https://golang.org/cl/353391 points out that a link in Effective Go () does not work.  The link is https://golang.org/pkg/strings/#example_Map.  That link currently just goes to the docs for the strings package.  If we change the underscore to a hyphen (https://golang.org/pkg/strings/#example-Map) then it links to the example.

The link has been there since 2013 (added in https://golang.org/cl/7454044) and it seems to me unlkely that nobody ever checked that the link worked.  While I can't prove it, it seems much more likely that this broke when golang.org was moved over to pkg.go.dev.

It seems to me that we should make the underscore links work for examples, unless there is some good reason not to.  Thanks.
Repository: rust
Issue: Function with impossible-to-satisfy higher-ranked bound triggers error when a closure is present
Labels: A-lifetimes,A-borrow-checker,C-bug,T-types,A-higher-ranked

The following program compiles successfully:

```rust
fn impossible() where for<'a> &'a (): 'static {

}

fn main() {}
```

The `where` clause on `impossible` is impossible to satisfy, since it is not the case that every choice of `'a` outlives `'static`. However, we never call `impossible`, so this program compiles (similar to an unsatisfiable trait bound like `where String: Copy`).

If we add a closure to the function:

```rust
fn impossible() where for<'a> &'a (): 'static {
    let _ = || {};
}

fn main() {}
```

then it stops compiling (note that this occurs both with and without `#![feature(nll)]`):

```
error: higher-ranked lifetime error
 --> src/main.rs:2:13
  |
2 |     let _ = || {};
  |             ^^^^^
  |
  = note: could not prove for<'a> &'a (): 'static

error: could not compile `playground` due to previous error
```

The issue occurs here:

https://github.com/rust-lang/rust/blob/6dc08b909b469d58dd8fa54c57ab193b8cf95257/compiler/rustc_borrowck/src/type_check/mod.rs#L2688

When we instantiate the predicates of the closure during type-checking of `impossible`, we also instantiate the predicates for the parent of the closure - that is, the predicates of `impossible`. This results in us trying to *prove* that `for<'a> &'a (): 'static` holds, leading to an error. Normally, we will *not* try to prove this predicate during type-checking of `impossible` itself.
Repository: flutter
Issue: [Proposal] Show changelog on Flutter upgrade
Labels: c: new feature,tool,d: api docs,c: proposal,P3,team-tool,triaged-tool

## Use case
I currently work on the beta channel of Flutter.    
When running, ```flutter upgrade``` I quite often wonder what exactly changed between the version I had installed and the new, current version.

## Proposal

I would be nice to see the changelog (generated from the Flutter releases section), when running ```flutter upgrade``` on channel beta and dev.
Repository: create-react-app
Issue: src, scripts, public folder not created
Labels: needs triage

npx version: 7.24.1
node version: 14.18.0
npm : 7.24.1

Created a react-app using: npx create-react-app my-app
Folder with node_modules, package.json and packageloack.json is created but src, public and scripts folder is not created.

Tried reinstalling nodejs, 
clearing cache,
npm rm -g create-react-app
npm install -g create-react-app
npx create-react-app my-app

But nothing solved my problem...
Kindly help
Repository: godot
Issue: GDScript naming inconsistencies
Labels: discussion,topic:codestyle

### Godot version

3.3.stable

### System information

All systems

### Issue description

I've noticed some inconsistencies in naming convention for built-in methods and properties, for example:

- `Line2D.default_color` and `Polygon2D.color`

- `@GDScript.lerp()` and `Vector2.linear_interpolate()` and `Vector2.slerp()`

- `Rigidbody2D.add_force()` and `Rigidbody2D.apply_impulse()`

Is there a reason for these differences? If so, are they documented anywhere? If not, can there be a more consistent approach to naming? e.g.

- `Line2D.color` and `Polygon2D.color`

- `@GDScript.lerp()` and `Vector2.lerp()` and `Vector2.slerp()`




### Steps to reproduce

None required.

### Minimal reproduction project

_No response_
Repository: TypeScript
Issue: Provide a specialized error on top-level await and --module node12
Labels: Suggestion,Help Wanted,Good First Issue

Under `node12`, a top-level await results in

```
Top-level 'await' expressions are only allowed when the 'module' option is set to 'es2022', 'esnext', 'system', or 'nodenext', and the 'target' option is set to 'es2017' or higher.
```

This error message has too much text. We should consider specializing these cases for

* ES modules < es2022
* Node modules < nodenext

```
The module setting '{0}' does not support top-level 'await' expressions. Consider switching to '{1}'.
```