sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: runtime/coverage: out-of-bounds panic in `VisitFuncs` via `processCoverTestDir`
Labels: NeedsInvestigation,compiler/runtime

```
#!watchflakes
post <- log ~ `panic: runtime error: slice bounds out of range` && log ~ `^\s*runtime/coverage\.\(\*emitState\)\.VisitFuncs`
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/b594cce651df988c94d911ef703445d99cd302f7)):

    vcs-test.golang.org rerouted to http://127.0.0.1:43053
    https://vcs-test.golang.org rerouted to https://127.0.0.1:44521
    go test proxy running at GOPROXY=http://127.0.0.1:40533/mod
    2023/11/14 16:00:23 http: TLS handshake error from 127.0.0.1:50386: read tcp 127.0.0.1:44521->127.0.0.1:50386: read: connection reset by peer
    2023/11/14 16:00:39 http: TLS handshake error from 127.0.0.1:50772: read tcp 127.0.0.1:44521->127.0.0.1:50772: read: connection reset by peer
    2023/11/14 16:00:39 http: TLS handshake error from 127.0.0.1:50792: read tcp 127.0.0.1:44521->127.0.0.1:50792: read: connection reset by peer
    2023/11/14 16:00:39 http: TLS handshake error from 127.0.0.1:50780: EOF
    2023/11/14 16:00:44 http: TLS handshake error from 127.0.0.1:50906: EOF
    2023/11/14 16:00:44 http: TLS handshake error from 127.0.0.1:50916: EOF
    2023/11/14 16:00:44 http: TLS handshake error from 127.0.0.1:50922: EOF
    ...
    --- FAIL: TestScript (0.06s)
        --- FAIL: TestScript/cover_pkgall_runtime (6.05s)
            script_test.go:132: 2023-11-14T16:01:03Z
            script_test.go:134: $WORK=/workdir/tmp/cmd-go-test-1942127129/tmpdir4285299461/cover_pkgall_runtime1388929147
            script_test.go:156: 
                > env GO111MODULE=off
                # Issue 23882 (6.045s)
                > [short] skip
                [condition not met]
                > go test -coverpkg=all x
    ...
                testing.(*M).Run.deferwrap1()
                	/workdir/go/src/testing/testing.go:2004 +0x27 fp=0xa104df8 sp=0xa104df0 pc=0x820cd67
                testing.(*M).Run(0xa05e0a0)
                	/workdir/go/src/testing/testing.go:2055 +0x12fb fp=0xa104f68 sp=0xa104df8 pc=0x820c99b
                main.main()
                	_testmain.go:81 +0x195 fp=0xa104fac sp=0xa104f68 pc=0x822e025
                runtime.main()
                	/workdir/go/src/runtime/proc.go:271 +0x4e7 fp=0xa104ff0 sp=0xa104fac pc=0x80b9c07
                runtime.goexit({})
                	/workdir/go/src/runtime/asm_386.s:1363 +0x1 fp=0xa104ff4 sp=0xa104ff0 pc=0x81141d1


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: neovim
Issue: workspace/didCreateFiles notification not sent to language server after a code action creates a file
Labels: enhancement,lsp

### Problem

The nvim lsp client does not send `workspace/didCreateFiles` notifications back to the language server after performing a code action that create files (for example, the `marksman` language server supports such an action). Therefore, the language server does not receive that information and is unable to update its internal state to reflect the existence of the created files.


### Steps to reproduce using "nvim -u minimal_init.lua"

Minimal config: 
```lua
local pattern = "markdown"
local cmd = { "marksman" }
-- Add files/folders here that indicate the root of a project
local root_markers = { ".git", ".editorconfig", ".marksman.toml" }
-- Change to table with settings if required
local settings = vim.empty_dict()

vim.api.nvim_create_autocmd("FileType", {
    pattern = pattern,
    callback = function(args)
	local match = vim.fs.find(root_markers, { path = args.file, upward = true })[1]
	local root_dir = match and vim.fn.fnamemodify(match, ":p:h") or nil
	vim.lsp.start({
	    name = "bugged-ls",
	    cmd = cmd,
	    root_dir = root_dir,
	    settings = settings,
	})
    end,
})
```
Steps to reproduce:
1. Setup: 
    - Create a notebook directory `mkdir notebook-test`.
    - Initialize the notebook root `touch notebook-test/.marksman.toml`.
2. Open a markdown file: `nvim -u minimal_init.lua notebook-test/index.md`.
3. Create a link to a new file by inserting something like test `[[test]]`.
4. There should be a diagnostic warning you that the `test.md` file does not exist.
5. Hover your cursor on `test`.
6. Perform the code action:
    - `:lua vim.lsp.buf.code_action()`
    - Choose the `Create test.md` option.
    - The diagnostic will still be there.
7. Test that the language server does not know about the file 
    - `:lua vim.lsp.buf.definition()`
    - You will not be taken to the `test.md` file.
8. Exit the file and check that the `test.md` file was indeed created with `ls notebook-test`

### Expected behavior

A notification is sent to the language server to reflect that files have been created. It seems that `VsCode` sends a `workspace/didCreateFiles` notification in the same scenario, so that seems like a good candidate. Some more details regarding `emacs` are described [here](https://github.com/artempyanykh/marksman/pull/239#pullrequestreview-1542292940).

### Neovim version (nvim -v)

Tested on 0.9.4 release and 0.10.0 Nightly

### Language server name/version

marksman latest

### Operating system/version

Tested on Arch Linux and MacOs

### Log file

_No response_
Repository: godot
Issue: Instanced meshes incorrectly scale normals in Compatibility backend
Labels: bug,topic:rendering,topic:3d

### Godot version

4.2-beta6

### System information

Godot v4.2.beta6 - Windows 10.0.19045 - GLES3 (Compatibility) - NVIDIA GeForce RTX 4060 Ti (NVIDIA; 31.0.15.4584) - AMD Ryzen 9 5900X 12-Core Processor (24 Threads)

### Issue description

Related to #82763

The Compatibility renderer doesn't use flags for instanced meshes, nor does it pass them to the scene shader. This means that even if they have non-uniform scaling, their normals will appear broken:

<img width="851" alt="aaaaa" src="https://github.com/godotengine/godot/assets/53150244/7142eb7b-d352-4e06-918e-be28a3fbb857">
(The left ones are particles, the right one is a multi-mesh instance)


### Steps to reproduce

- Open the provided MRP 
- open `node_3d.tscn`

### Minimal reproduction project

[compat_instanced_normal_scaling.zip](https://github.com/godotengine/godot/files/13352685/compat_instanced_normal_scaling.zip)
Repository: pytorch
Issue: FP8 types should not participate in type promotion and should have no math ops defined on them
Labels: high priority,triaged,module: float8

Right now, the following works
```
In [1]: import torch

In [2]: a=torch.randn(4, device="cuda")

In [3]: b=torch.zeros(4, device="cuda", dtype=torch.float8_e5m2)

In [4]: a+b
Out[4]: tensor([-0.6676, -0.6190, -0.8736,  0.1410], device='cuda:0')
```
But fp8 types are meant to work with per-tensor scales, and the above is a footgun that most people should avoid (it assumes the scales of the float8 tensor are 1), erroring out in this case and relying on operations implementation via subclassing fp8 tensor or some other means is the way to go. 
If someone indeed wants unscaled operations, they can explicitly cast fp8 tensor to a wider type, and rely on `torch.compile` to fuse this explicit cast away.  

cc @ezyang @gchanan @zou3519 @kadeng @yanbing-j @vkuzo @albanD
Repository: transformers
Issue: Plain-DETR
Labels: New model,Vision

### Model description

Plain-DETR is an object detector that maintains a "plain" nature: using a single-scale feature map and global cross-attention calculations without specific locality constraints. 
In contrast to previous leading DETR-based detectors that reintroduce architectural inductive biases of multi-scale and locality into the decoder.  
By leveraging the Object365 dataset for pre-training, it achieved 63.9 mAP accuracy using a Swin-L backbone, which is highly competitive with state-of-the-art detectors which all heavily rely on multi-scale feature maps and region-based feature extraction
Published in the proceedings of ICCV 2023.

### Open source status

- [X] The model implementation is available
- [X] The model weights are available

### Provide useful links for the implementation

Official implementation: [code](https://github.com/impiga/Plain-DETR)
Paper: [DETR Does Not Need Multi-Scale or Locality Design](https://openaccess.thecvf.com/content/ICCV2023/html/Lin_DETR_Does_Not_Need_Multi-Scale_or_Locality_Design_ICCV_2023_paper.html)
Repository: material-ui
Issue: [joy-ui][Menu] allow better trigger mechanism (click | hover)
Labels: new feature,component: menu,package: joy-ui

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Summary 💡

```gherkin
Feature: Menu trigger mechanism
  As a developer,
  I want an intuitive API to trigger visiblity of the menu
  So that I can decide how a menu should be opened

  # This is satisfied
  Scenario: Tigger is click
    When I click on the MenuButton
    Then the Menu should open
    When I click outside the Menu
    Then the Menu should close

  # This is NOT satisfied
  Scenario: Tigger is hover and user clicks outside
    When I hover on the MenuButton
    Then the Menu should open
    When I click outside the Menu
    Then the Menu should close

  # This is NOT satisfied
  Scenario: Tigger is hover and user leaves menu
    When I hover on the MenuButton
    Then the Menu should open
    When I move outside the Menu
    Then the Menu should close

```

### Examples 🌈

This is sort of what I expect but it is a VERY complex example: https://mui.com/joy-ui/react-menu/#side-navigation-icons

Also it is extremely buggy (see video) because it will not close unless you leave the menu itself. It remains open on outside clicks

https://github.com/mui/material-ui/assets/1148334/01fae4ed-4e6d-4ee9-ba3e-056563241600


 

### Motivation 🔦

I am trying to implement a common dropdown menu with multiple levels that can work on hover while maintaining the default click activation (as option)

I understand that this can be implemented but the amount of work needed to achieve such a behavior is extremely complex and tedious, additionally prone to bugs.
Repository: pytorch
Issue: document functional_collectives
Labels: oncall: distributed,module: docs,triaged,oncall: pt2

### 📚 The doc issue

currently distributed collective docs don't mention functional collectives.

PT2 support needs functional collectives to be used.  (also, PT2 supports transparently rewriting _Some_ c10d collectives into functional equivalents but not all of them (not the async variants).

Functional collectives aren't "released" yet.  Should we release them?  Can we add them to the docs if we do not?

cc @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @H-Huang @kwen2501 @awgu @penguinwu @fegin @XilunWu @svekars @carljparker @ezyang @msaroufim @bdhirsh @anijain2305 @zou3519 @xmfan @wanchaol @Chillee @geeta

### Suggest a potential alternative/fix

_No response_
Repository: deno
Issue: deno compile OOM crash when mixing two zod versions together in an project
Labels: bug,compile,node compat

Hey im using zod with shared code for frontend and backend. One time we only updated one site's version and kept the old version. Which works fine, running and handling the zod objects worked but until we tried to compile the backend with these mixed versions it got stuck at 100% CPU and using up to 6 GB or RAM until if failed after almost 5 minutes.

![image](https://github.com/denoland/deno/assets/11093382/5a653498-0edb-4a25-8c57-aaf50c4c7411)

First i tried to just patch that outdated version to be the same, but that didn't help. only after updating the outdated versions everything worked again.
Repository: pytorch
Issue: Failure to resume from a normal (non-FSDP) checkpoint due to the optimizer state dict rekey
Labels: module: optimizer,triaged,module: fsdp

https://github.com/pytorch/pytorch/blob/edd967fe78bca74dd35ef00830e03bd24153f796/torch/distributed/fsdp/fully_sharded_data_parallel.py#L1634-L1643

When storing optimizer state dict from a non-FSDP model, the parameters are stored with the reference of ID and their order in the dict is not the same as the order of `model.parameters()`. 

So, rekeying the optim state dict by param.Name fails due to the mismatch in the param shape upon loading optim state dict.

cc @vincentqb @jbschlosser @albanD @janeyx99 @crcrpar @zhaojuanmao @mrshenli @rohan-varma @awgu @fegin @penguinwu
Repository: PowerToys
Issue: [Docs] Group policies: Auto-generate the table of utility policies
Labels: Idea-Enhancement,Issue-Docs,Needs-Triage

### Provide a description of requested docs changes

I have reworked the Policy documentation on learn.microsoft.com. No the md file/page contains a list of all utility enabled policies.

Because @crutkas worries that the table gets out of sync he suggested to auto-generate it based on the ADMX/ADML file.

See also: https://github.com/MicrosoftDocs/windows-dev-docs/pull/4719#discussion_r1384017199
Repository: godot
Issue: Path3D tilt handle size in settings does not work and value is not kept between launches
Labels: bug,topic:editor,topic:3d

### Godot version

4.2b4

### System information

macos 12.7

### Issue description

the tilt handles were very small as i had very large path3ds in that project, i found the setting to change their size but it did not seem to do anything, and after restarting the editor, the value was reset.

### Steps to reproduce

change tilt handle size value
restart
check tilt handle size

### Minimal reproduction project

N/A
Repository: angular
Issue: Add more info to Angular Hydration warning message when app not stable within 10 seconds
Labels: area: core,core: hydration

### Which @angular/* package(s) are relevant/related to the feature request?

_No response_

### Description

Currently whenever you try to use Angular hydration and your client side app is not stable within 10 seconds, you get a warning that looks like this:

```
NG0506: Angular hydration expected the ApplicationRef.isStable() to emit `true`, but it didn't happen within 10000ms. Angular hydration logic depends on the application becoming stable as a signal to complete hydration process. Find more at https://angular.io/errors/NG0506
```

The problem is that it can be extremely hard to figure out at times what exactly is keeping your application unstable.

### Proposed solution

The NgZone keeps track of microtasks and macrotasks so perhaps we can get something from what is being tracked in the NgZone to report to the user what exactly is keeping the application unstable.

### Alternatives considered

Currently to debug this I either just keep commenting out stuff until the warning goes away to narrow in on what may be causing the issue or use a global patch like this one from @yharaskrik:

```
const o = window.setTimeout;

(window as any)['setTimeout'] = function (handler: TimerHandler, timeout?: number, ...args: any[]) {
    console.trace();
    return o(handler, timeout, ...args);
};

const i = window.setInterval;

(window as any)['setInterval'] = function (handler: TimerHandler, timeout?: number, ...args: any[]) {
    console.trace();
    return i(handler, timeout, ...args);
};
```
Repository: pytorch
Issue: [export] Support capturing of non-tensor inputs
Labels: triaged,export-triaged,oncall: export

### 🚀 The feature, motivation and pitch

Currently, `torch.export.export` would burn-in non-tensor inputs:

Example:
```python
import torch

def logsoftmax(x, dim):
    return torch.nn.LogSoftmax(dim)(x)

exp = torch.export.export(logsoftmax, ( torch.randn(10, 10), 1))
print(exp.graph_module.code)
```
yields 

```
def forward(self, arg0_1, arg1_1):
    _log_softmax = torch.ops.aten._log_softmax.default(arg0_1, 1, False);  arg0_1 = None
    return (_log_softmax,)
```

Here, arg1_1 become dangling and the value `1` is hardcoded. So when this function is called with a different value, it would produce wrong result.

Desired output would be
```
def forward(self, arg0_1, arg1_1):
    _log_softmax = torch.ops.aten._log_softmax.default(arg0_1, arg1_1, False);  arg0_1 = None
    return (_log_softmax,)
```

### Alternatives

_No response_

### Additional context

_No response_

cc @avikchaudhuri @gmagogsfm @zhxchen17 @tugsbayasgalan @angelayi @suo @ydwu4
Repository: deno
Issue: Stack traces are not printed when modified by the user
Labels: bug,design limitation

```js
const e = new Error("oh no");
e.stack = "oh no\nSome very useful information about the origin of the error";

throw e;
```

When you run this from the browser console, all browsers except Firefox display the stack trace:
<img width="426" alt="image" src="https://github.com/denoland/deno/assets/2737650/fadd3290-df47-4dfb-be8c-e9c70f6a4f0a">

But Deno actually removes the existing stack trace completely and only logs the error message:
<img width="312" alt="image" src="https://github.com/denoland/deno/assets/2737650/4fdb2c07-cf15-4594-a8fa-16d8a743262e">
Repository: godot
Issue: CanvasLayer does not hide if parent node is hidden
Labels: enhancement,topic:rendering,documentation,topic:2d

### Godot version

v4.2.beta5.mono.official [4c96e9676]

### System information

Windows 11

### Issue description

No matter what you do, without directly hiding a CanvasLayer, it will always render:
![image](https://github.com/godotengine/godot/assets/22286697/9da73753-0204-41fd-86ce-005d8db816b5)


### Steps to reproduce

1. Create a scene
2. Add a CanvasLayer child to the scene
3. Add some visible node as a child of the CanvasLayer
4. Hide the root node of the scene and observe the CanvasLayer does not hide

### Minimal reproduction project

N/A
Repository: pytorch
Issue: Removing index_put fallback results in bad C++ code
Labels: triaged,oncall: pt2,oncall: cpu inductor

### 🐛 Describe the bug

In inductor, index_put has a fallback for bool because triton atomic_add does not support bools. Since this was not gated on triton only, it was hiding the fact that for CPU code, we generate `fetch_add` on `std::atomic<bool>` which I believe the C++ standard does not require to be defined, and hence is not defined.

https://github.com/pytorch/pytorch/pull/113655 removes the fallback for scatter but leaves it for index_put. It should also be removed from index_put.

### Versions

origin/main

cc @ezyang @msaroufim @wconstab @bdhirsh @anijain2305 @zou3519
Repository: pytorch
Issue: C++ backtrace logging for dynamic shapes specialization
Labels: triaged,ezyang's list,module: dynamic shapes

### 🐛 Describe the bug

something like this

```
diff --git a/torch/fx/experimental/symbolic_shapes.py b/torch/fx/experimental/symbolic_shapes.py
index d76ed611800..23d8febb70d 100644
--- a/torch/fx/experimental/symbolic_shapes.py
+++ b/torch/fx/experimental/symbolic_shapes.py
@@ -3325,6 +3325,10 @@ class ShapeEnv:
                 maybe_extra_debug,
                 stack_info=is_debug,
             )
+            self.log.debug(
+                "guard\n%s",
+                ''.join(CapturedTraceback.extract(cpp=True).format())
+            )
 
     @lru_cache(256)
     @record_shapeenv_event(save_tracked_fakes=True)
```

but less wordy, not on by default. Maybe also want to make the symbolization faster by batching.

### Versions

main
Repository: pytorch
Issue: torch.compile doesnt respect use_determistic_algorithms during the backward()
Labels: triaged,module: determinism,oncall: pt2,module: aotdispatch,module: pt2-dispatcher

Minimal repro:
```
import torch

m = torch.nn.ReflectionPad2d((1, 2, 3, 4))
m_compiled = torch.compile(m)

inp = torch.randn(2, 3, 8, 8, device='cuda', requires_grad=True)
out = m_compiled(inp)

# set use_deterministic_algorithms to True
torch.use_deterministic_algorithms(True)

# the backward of ReflectionPad2d should error, because it doesn't have a deterministic implementation!
out.sum().backward()
```

The core problem comes from the fact that:

(1) torch.compile will eagerly trace out a backward graph when we compile the forward (`torch.nn.ReflectionPad2d`)

(2) This requires us to run our meta implementations for the backward graph, including for `aten.replication_pad2d_backward`, **ahead-of-time**, during the forward

(3) We don't know during trace-time of the forward whether or not `torch.use_deterministic_algorithms` will be set at runtime during the backward

cc @mruberry @kurtamohler @ezyang @msaroufim @wconstab @anijain2305 @zou3519
Repository: next.js
Issue: Smooth scrolling to root path '/' does not work in app directory
Labels: bug,Navigation

### Link to the code that reproduces this issue

https://github.com/robiot/nextjs-smoothscroll-appdir

### To Reproduce

1. **Create a Next.js app: (select app dir)**
   ```bash
   pnpm create next-app my-nextjs-app
   cd my-nextjs-app
   ```

2. **Install required dependencies:**
   ```bash
   pnpm install
   ```

3. **Open the `styles/globals.css` file:**
   Replace the existing content with the following CSS:

   ```css
   /* styles/globals.css */
   html, body {
     scroll-behavior: smooth;
   }
   ```

4. **Open the `app/page.tsx` file:**
   Replace the existing content with the following code:

      ```tsx
      import Image from "next/image";
      import Link from "next/link";
      
      export default function Home() {
        return (
          <>
            <div className="top-0 sticky left-0 w-full h-16 bg-black flex gap-5">
              <Link href="/">
                Home
              </Link>
              <Link href="/#2">Nr2</Link>
            </div>
            <section className="h-[90vh] bg-red-500">This is App router canary</section>
            <section id="2" className="h-[90vh] bg-green-500">
              nr.2
            </section>
          </>
        );
      }
      ```

5. **Run the Next.js app:**
   ```bash
   npm run dev
   ```

6. **Open your browser and navigate to [http://localhost:3000](http://localhost:3000).**
   Ensure that the application is running and that you see the "Home" and "Section 1" links in the navbar.

7. **Test the scroll behavior:**
   - Click on the "Section 1" link and ensure that it smoothly scrolls to the "Section 1" part of the page.
   - Click on the "Home" link and you will see it **wont scroll up smoothly**.


### Current vs. Expected behavior

Expected behavior would be that the page still uses smooth scrolling when scrolling to '/'.
Here is a website showing how it is when using pages directory. You can see the page smoothy scrolls to '/' and to the section.
https://nextjs-smoothscroll-pages.vercel.app/

But when using app router, https://nextjs-smoothscroll-appdir.vercel.app the smooth scrolling doesn't apply when scrolling to top.

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro
Binaries:
  Node: 20.8.1
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.0.3-canary.7
  eslint-config-next: 14.0.2
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.2.2
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

App Router, Routing (next/router, next/navigation, next/link)

### Additional context

Issue is not only present in canary, it also affects `^14.0.2`.