sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: [Nested Tensor] view + inplace for autograd. 
Labels: module: autograd,triaged,module: nestedtensor

## Summary
This is currently erroring:
```
import torch
a = torch.randn(1, 2, 4, requires_grad=True)
b = torch.randn(2, 2, 4, requires_grad=True)
c = torch.randn(3, 2, 4, requires_grad=True)
nt = torch.nested_tensor([a,b,c])
buffer = nt.values()
buffer.mul_(2)
```
This is
1. Creating a view nt -> buffer 
2. Applying an inplace op on buffer. 


This triggers rebase_history() which in turn creates copy_slices. Copy slices utilize a struct called TensorGeometry to track geometry information about the base and the view.  The view_fn will be used instead of as_strided. However we apply this function on result which is an empty of clone of base. We don't currently have a factory function that can do this. This will be unblocked when we add this.


cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @soulitzer @Lezcano @Varal7 @cpuhrsch @jbschlosser @bhosmer
Repository: pytorch
Issue: [Nested Tensor] Move nested tensor specific ops to nested namespace
Labels: triaged,module: nestedtensor

# Summary
Currently all nested tensor specific ops are dumped into the default namespace `torch`. This issue is used to track work on creating a nested tensor namespace and moving all the nested tensor specific functions that namespace.

cc @cpuhrsch @jbschlosser @bhosmer
Repository: rust
Issue: global_allocator does not work with -C prefer-dynamic
Labels: A-linkage,A-diagnostics,A-allocators,T-compiler,C-bug,-Cprefer-dynamic

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

Could not find anything related to this online. Using `RUSTFLAGS="-C prefer-dynamic" cargo run` on this does not panic.

```rust
use std::alloc::{GlobalAlloc, Layout};

#[global_allocator]
static ALLOC: Alloc = Alloc;

pub struct Alloc;

unsafe impl GlobalAlloc for Alloc {
    unsafe fn alloc(&self, layout: Layout) -> *mut u8 {
        panic!()
    }
    
    unsafe fn alloc_zeroed(&self, layout: Layout) -> *mut u8 {
        panic!()
    }
    
    unsafe fn realloc(&self, ptr: *mut u8, layout: Layout, new_size: usize) -> *mut u8 {
        panic!()
    }
    
    unsafe fn dealloc(&self, ptr: *mut u8, layout: Layout) {
        panic!()
    }
}

fn main() {
    let _ = Box::new(1);
}
```

### Meta

`rustc --version --verbose`:
```
rustc 1.65.0-nightly (29e4a9ee0 2022-08-10)
binary: rustc
commit-hash: 29e4a9ee0253cd39e552a77f51f11f9a5f1c41e6
commit-date: 2022-08-10
host: x86_64-unknown-linux-gnu
release: 1.65.0-nightly
LLVM version: 14.0.6
```
Repository: terminal
Issue: Author a KB article documenting DxD and how to disable it
Labels: Product-Conhost,Issue-Docs,Product-Terminal,Needs-Tag-Fix,Priority-1

When DxD hits broadly, it will be good for us to have some official Microsoft documentation on (1) what happened, (2) the anticipated risk to applications and (3) how to revert to a known-good state. Enterprises can fall back on this documentation, and we can point users to it.

## Why a KB article, instead of Terminal Docs?

We should do both, but a KB article is more "official." They're not user-editable, and they document "best practice" and compatibility risks and things like that.
Repository: rust
Issue: LLVM ERROR: Broken module with  -Cdebuginfo=2  -Zsanitizer=cfi -Clto
Labels: A-LLVM,A-debuginfo,I-ICE,E-needs-test,T-compiler,A-sanitizers,C-bug,glacier,PG-exploit-mitigations

<!--
Thank you for finding an Internal Compiler Error! 🧊  If possible, try to provide
a minimal verifiable example. You can read "Rust Bug Minimization Patterns" for
how to create smaller examples.

http://blog.pnkfx.org/blog/2019/11/18/rust-bug-minimization-patterns/

-->

### Code
`./src/test/ui/issues/issue-27901.rs`
```Rust
// run-pass
trait Stream { type Item; }
impl<'a> Stream for &'a str { type Item = u8; }
fn f<'s>(s: &'s str) -> (&'s str, <&'s str as Stream>::Item) {
    (s, 42)
}

fn main() {
    let fx = f as for<'t> fn(&'t str) -> (&'t str, <&'t str as Stream>::Item);
    assert_eq!(fx("hi"), ("hi", 42));
}
```


### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.65.0-nightly (0b79f758c 2022-08-18)
binary: rustc
commit-hash: 0b79f758c9aa6646606662a6d623a0752286cd17
commit-date: 2022-08-18
host: x86_64-unknown-linux-gnu
release: 1.65.0-nightly
LLVM version: 15.0.0
```

### Error output
`rustc ./issue-27901.rs -Cdebuginfo=2  -Zsanitizer=cfi -Clto`
```
inlinable function call in a function with debug info must have a !dbg location
  call void @_ZN11issue_279011f17h923e371f4763f6b8E.cfi(ptr sret({ { ptr, i64 }, i8, [7 x i8] }) %6, ptr align 1 @3, i64 2)
inlinable function call in a function with debug info must have a !dbg location
  call void @_ZN11issue_279011f17h923e371f4763f6b8E.cfi(ptr sret({ { ptr, i64 }, i8, [7 x i8] }) %6, ptr align 1 @3, i64 2)
LLVM ERROR: Broken module found, compilation aborted!
```

<!--
Include a backtrace in the code block by setting `RUST_BACKTRACE=1` in your
environment. E.g. `RUST_BACKTRACE=1 cargo build`.
-->
<details><summary><strong>Backtrace</strong></summary>
<p>

```
same
```

</p>
</details>



<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"rcvalle"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: PowerToys
Issue: Remove PDF file explorer items (preview pane / thumbnail) from PowerToys since MS Edge does this better
Labels: Idea-Enhancement,Needs-Community Feedback,Product-File Explorer

### Description of the new feature / enhancement

Microsoft Edge has these abilities now in both preview pane and thumbnails.  It does a better job as well.

### Scenario when this would be used?

Simplifying PowerToys code base, users have a better, built in option

### Supporting information

_No response_
Repository: storybook
Issue: Addon-docs: 'show code' not displaying correct component name when using forwardRef with args
Labels: bug,react,block: source

**Describe the bug**
When using args with a component that uses `forwardRef`, you will not be shown the correct component name when clicking 'Show code' in the docs section of storybook

**To Reproduce**
Repo: https://github.com/Jamess-Lucass/storybook-issue-reproduction

1. Create a component using `forwardRef`
2. Use that component with the args feature within storybook

**System**
```bash
Environment Info:

  System:
    OS: Linux 5.10 Ubuntu 20.04.4 LTS (Focal Fossa)
    CPU: (32) x64 AMD Ryzen 9 5950X 16-Core Processor
  Binaries:
    Node: 16.16.0 - ~/.nvm/versions/node/v16.16.0/bin/node
    npm: 8.11.0 - ~/.nvm/versions/node/v16.16.0/bin/npm
  npmPackages:
    @storybook/addon-actions: 6.5.10 => 6.5.10
    @storybook/addon-essentials: 6.5.10 => 6.5.10
    @storybook/addon-interactions: 6.5.10 => 6.5.10
    @storybook/addon-links: 6.5.10 => 6.5.10
    @storybook/builder-vite: 0.2.2 => 0.2.2
    @storybook/react: 6.5.10 => 6.5.10
    @storybook/testing-library: 0.0.13 => 0.0.13
```

**Additional context**
I am experiencing this issue when the component uses `forwardRef` and your story is using args. The below code will replicate this error.

currently on version `6.5.10`

`button.tsx` - normal component
```typescript
import { forwardRef } from "react";

export type ButtonProps = {
  text: string;
};

const Button = forwardRef<HTMLButtonElement, ButtonProps>(
  ({ text }: ButtonProps, ref) => <button ref={ref}>{text}</button>
);

// const Button = ({ text }: ButtonProps) => <button>{text}</button>;

export default Button;
```

`button.stories.tsx` - story file
```typescript
import { ComponentMeta, ComponentStory } from "@storybook/react";
import Button from "./button";

export default {
  title: "Button",
  component: Button,
} as ComponentMeta<typeof Button>;

const Template: ComponentStory<typeof Button> = ({ text }) => (
  <Button text={text} />
);

// const Template: ComponentStory<typeof Button> = () => (
//   <Button text="button text" />
// );

export const Default = Template.bind({});
Default.args = {
  text: "Best button!",
};
```

When viewing the docs in storybook you will see the component loaded as `_c`:

![storybook-forwardref-template-args-issue](https://user-images.githubusercontent.com/23193271/185718860-d067ba16-551d-4b87-ac3c-0d74cf9b0800.png)

If you remove `args` in the `button.stories.tsx` file it will work:
```typescript
const Template: ComponentStory<typeof Button> = () => <Button text="test" />;
```
This is not feasible for me as I want to use the args feature.

Likewise, if you were to not use `forwardRef` in the `button.tsx` component it will work with args:
```typescript
const Button = ({ text }: ButtonProps) => <button>{text}</button>;
```
This is also not feasible for me as I want to use `forwardRef` in the component and others may not have direct access to the component if they're using a library like MUI or Chakra
Repository: flutter
Issue: Deprecate and remove FocusScope and FocusScopeNode
Labels: framework,f: focus,P2,team-framework,triaged-framework

The `FocusScopeNode` serves two main purposes:

1) It "scopes" the focus so that you can't escape the scope by tab traversal.
2) It keeps a stack of previously focused widgets so that if you return focus to the scope, it will re-focus the widget that previously had focus inside of the scope.

The two jobs are pretty orthogonal to each other, and rather than give it even more "modes", it makes sense to split it into two things.

The `FocusTraversalGroup` is the proper place for a flag that would limit the tab traversal to within the group (the actual flag would be on FocusNode), and it would make sense to deprecate the remaining `FocusScopeNode` (and associated `FocusScope` widget) and replace it with something that just did the focus history piece (probably called `FocusHistory` for obvious reasons).

This would give us a chance to separate these concerns, and would let us simplify a lot of the weird knots that the focus API is wound into as a result of wanting to keep from breaking previous APIs.

cc @goderbauer
Repository: rust
Issue: Renaming eq_by to related_by
Labels: T-libs-api

Take a look at the following code [[Rust Playground](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=42d35540d79d41353a5ca600cdcf0398)]
```
#![feature(iter_order_by)]

fn main() {
    let xs = [1, 2, 3, 4];
    let ys = [1, 5, 10, 16];

    assert!(xs.iter().eq_by(&ys, |&x, &y| x * x <= y));
}
```

eq_by name suggests that the function can only be used for checking if the two iterators are equal however, as you can see, the function can check for any relation, not just equality thus it should be renamed to related_by.

Instead another function named eq_by/eq_by_key should be created similar to this but, instead of taking a closure that takes two inputs of same type, it should take in one input, and return a generic data type which implements PartialOrd, then this data can be checked for equality.

Essentially, this eq_by/eq_by_key should be equivalent to `a.iter().count() == b.iter().count() && a.iter().zip(b.iter()).all(|(ele_a, ele_b)| fn(ele_a) == fn(ele_b))`  where a and b are two generic types that implement Iterator, and, fn is the function for generating argument, which is checked for equality instead.

Edit : Changed just eq_by to eq_by/eq_by_key and added a more specific description of eq_by/eq_by_key method as suggested by @timvermeulen.
Repository: godot
Issue: Using `bool()` on a `float` emits a warning if done on a typed variable
Labels: bug,topic:gdscript

### Godot version

v3.5.stable.official [991bb6a]

### System information

Windows 10

### Issue description

When I use bool(), I pass in a float, and although it works fine, I get an unexpected warning: 
```
W 0:00:00.637   Narrowing conversion (float is converted to int and loses precision).
  <C++ Error>   NARROWING_CONVERSION
  <Source>      PlayerState.gd:15
```
![image](https://user-images.githubusercontent.com/39019460/185733858-2a76b051-e371-40df-ab65-3580bc892e82.png)


### Steps to reproduce

You must pass a static typing float variable to run this method. Check minimal reproduction project. 

### Minimal reproduction project

```gdscript
var f: float = 0.1
print(bool(f)) # warning
```
```gdscript
var f := 0.1
print(bool(f)) # warning
```
```gdscript
var f = 0.1
print(bool(f)) # no warning
```
Repository: neovim
Issue: inccommand: make command preview independent of command-line mode
Labels: enhancement,editor-state

### Feature already in Vim?

No

### Feature description

Currently, previewing a command requires creating a command and specifying a preview callback function. This has several limitations:

- the input passed to the callback can only be supplied from the command line, not programmatically (an example of this is typing in a [`dressing.nvim`](https://github.com/stevearc/dressing.nvim) input box and wanting to feed the input to the command preview callback)
- it is not possible to assign a keybinding to show the preview (e.g. toggle it on and off) because one must be in command-line mode and actively type the command and its arguments 
- typing in command-line mode can have unwanted side effects, e.g. calling `getchar` inside the callback moves the cursor (https://github.com/neovim/neovim/pull/19035) 

I think the idea of saving buffer state and restoring it later is more universally useful than just for command-line mode. 

### Proposal
Preferably, two new functions would be introduced: let's call them `save` and `restore`

Plugin authors can then call `save`,  modify the buffer state and later call `restore` to restore any highlights / changed text.
Repository: deno
Issue: Deno.serve() - unable to determine what request is associated with an error...
Labels: suggestion,ext/http

The `onError()` method that can be passed requires a `Response` or `Promise<Response>` return, but lacks the context of what request it is associated with (nor is it clear under what conditions `onError` would be called).  This means it is impossible to return a meaningful response or even log anything meaningful, because you can't associate it with any particular context.

I know we were following the `std/http/serve()` but it actually makes it really difficult to provide a resilient server implementation, where with `Deno.serveHttp()` you can handle each request and response independently, and handle any rejections/exceptions with `.respondWith()`.

With oak, I am having to basically make the solution less robust in handling exceptions to cater to flash.
Repository: create-react-app
Issue: Auto cropping once Vercel deploy my app
Labels: needs triage

Hi Team, 

I have a storefront where all images look fine on the local side of the project and images fit and all that good stuff. However, 
once I take it and deploy it to vercel, for some reason I found the images have been cropped and changed around. The client I am working for needs to have the whole image in the product cards and not cropped. They are a photographer that needs to have images shown to the fullest. I really hope someone knows how to stop the auto-cropping or can show me the light on this issue


( DEV Server )
<img width="914" alt="Screen Shot 2022-08-19 at 5 06 11 pm" src="https://user-images.githubusercontent.com/17910103/185741870-1e902bd8-6f22-41d0-b440-57e129ec10f5.png">


( Vercel Deploy Server )
<img width="874" alt="Screen Shot 2022-08-19 at 2 12 17 am" src="https://user-images.githubusercontent.com/17910103/185741836-99ffad89-6be1-458d-bfb7-d67110a59b98.png">

I have done alot of changes in the app and tried to work it ou myself,  but nothing I do help when it comes to images as something built into the deploy change the image scale and crops it
Repository: rust
Issue: Iterator::sum requires type annotations in seemingly simple cases
Labels: C-enhancement,A-diagnostics,T-compiler

Even with type annotations, Iterator::sum is not handled very nicely:
```
    let foo: usize = (1usize..10).sum() + 1usize;
```
fails to build with:
```
error[[E0283]](https://doc.rust-lang.org/stable/error-index.html#E0283): type annotations needed
 --> src/main.rs:2:35
  |
2 |     let foo: usize = (1usize..10).sum() + 1usize;
  |                                   ^^^ cannot infer type of the type parameter `S` declared on the associated function `sum`
  |
  = note: cannot satisfy `_: Sum<usize>`
note: required by a bound in `std::iter::Iterator::sum`
help: consider specifying the generic argument
  |
2 |     let foo: usize = (1usize..10).sum::<S>() + 1usize;
  |                                      +++++
help: consider specifying the type argument in the function call
  |
2 |     let foo: usize = (1usize..10).sum::<S>() + 1usize;
  |                                      +++++
```

The converse:
```
    let bar: usize = 1usize + (1usize..10).sum();
```
fails to build with:
```
error[[E0284]](https://doc.rust-lang.org/stable/error-index.html#E0284): type annotations needed: cannot satisfy `<usize as Add<_>>::Output == usize`
 --> src/main.rs:2:29
  |
2 |     let bar: usize = 1usize + (1usize..10).sum();
  |                             ^ cannot satisfy `<usize as Add<_>>::Output == usize`
```
Repository: go
Issue: gollvm: os_linux.go:360:14: error: reference to undefined name '_itimerspec'
Labels: OS-Linux,NeedsInvestigation

Caught a bug, [out here](https://github.com/advancedwebdeveloper/gollvm_build_process/runs/7918314975?check_suite_focus=true#step:12:62445):

>/home/runner/work/gollvm_build_process/gollvm_build_process/gollvm_build_process/llvm-project/llvm/tools/gollvm/gofrontend/libgo/go/runtime/os_linux.go:360:14: error: reference to undefined name '_itimerspec'
>/home/runner/work/gollvm_build_process/gollvm_build_process/gollvm_build_process/llvm-project/llvm/tools/gollvm/gofrontend/libgo/go/runtime/os_linux.go:360:14: error: expected type
>/home/runner/work/gollvm_build_process/gollvm_build_process/gollvm_build_process/llvm-project/llvm/tools/gollvm/gofrontend/libgo/go/runtime/os_linux.go:246:40: error: use of undefined type '_sigevent'
>/home/runner/work/gollvm_build_process/gollvm_build_process/gollvm_build_process/llvm-project/llvm/tools/gollvm/gofrontend/libgo/go/runtime/os_linux.go:366:6: error: reference to field 'sigev_notify' in object which has no fields or methods
>/home/runner/work/gollvm_build_process/gollvm_build_process/gollvm_build_process/llvm-project/llvm/tools/gollvm/gofrontend/libgo/go/runtime/os_linux.go:366:22: error: reference to undefined name '_SIGEV_THREAD_ID'
>/home/runner/work/gollvm_build_process/gollvm_build_process/gollvm_build_process/llvm-project/llvm/tools/gollvm/gofrontend/libgo/go/runtime/os_linux.go:367:6: error: reference to field 'sigev_signo' in object which has no fields or methods
>/home/runner/work/gollvm_build_process/gollvm_build_process/gollvm_build_process/llvm-project/llvm/tools/gollvm/gofrontend/libgo/go/runtime/os_linux.go:368:33: error: reference to field '_sigev_un' in object which has no fields or methods
>/home/runner/work/gollvm_build_process/gollvm_build_process/gollvm_build_process/llvm-project/llvm/tools/gollvm/gofrontend/libgo/go/runtime/os_linux.go:246:40: error: use of undefined type '_sigevent'
>/home/runner/work/gollvm_build_process/gollvm_build_process/gollvm_build_process/llvm-project/llvm/tools/gollvm/gofrontend/libgo/go/runtime/os_linux.go:250:58: error: use of undefined type '_itimerspec'
>[1795/3011] Creating /home/runner/work/gollvm_build_process/gollvm_build_process/gollvm_build_process/build_release/tools/gollvm/libgo/tmp-sysinfo.go
Repository: terminal
Issue: Send different key codes for `Tab` and `Ctrl+I` (READ: support `modifyOtherKeys`)
Labels: Issue-Feature,Product-Conhost,Help Wanted,Area-Input,Area-VT,Issue-Task

<!-- 
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨

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
When using ms-terminal, `Tab` and `Ctrl+I` send the same key codes. This makes it impossible to map them differently, for example in vim or nvim (which support this functionality: https://github.com/neovim/neovim/pull/17932#issue-1188088238).

If ms-terminal sent different key codes (like for example kitty or alacritty terminal), then it would be possible to map these keys to different functionalities in software running inside the terminal. This would enhance user experience and make it easier to migrate from the aforementioned terminals.
<!-- 
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)

<!-- 
A clear and concise description of what you want to happen.
-->
Repository: axios
Issue: Time out and Memory Leak Issue
Labels: state::triage

When I try to get this url: https://antoniomoreau.com/

Then I can't get a result for a long time, at the same time, the operating system memory is gradually increasing until the memory is full, finally cause memory leak, and make the program terminated accidentally.

Please note this 'problem url':
   
          https://antoniomoreau.com/
Repository: godot
Issue: Tree Control Focus Mode Causing Items To be Hidden Past 3.3
Labels: needs testing,topic:gui

### Godot version

3.5

### System information

Kubuntu, gles3

### Issue description

Tree control hiding items because of focus mode.

### Steps to reproduce

Make a Tree control, give it items and a focus mode that is anything but 'none', then click it.  It will hide the items, when another control is focused, the items show back up.  
Edit: Apparently it was important to include the custom style overrides for bg and bg focus.  Also the project was created in 3.3, as my main project was that had this issue earlier, the issue only came up after updating, in-case that is relevant.

### Minimal reproduction project

https://www.udrop.com/77Iz/MRP.zip

Can't get the drag and drop for files to work.