sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: create-react-app
Issue: Cannot find module 'ajv/dist/compile/codegen'
Labels: needs triage,issue: bug report

### Describe the bug

I am quite new to the world of npm. When I say "npx create-react-app my-app; cd my-app; npm start" as instructed on the Getting Started page, I get an error message "Cannot find module 'ajv/dist/compile/codegen'"

### Did you try recovering your dependencies?

I had to manually say `npm install --save-dev ajv` to get it to work.

I report this as an issue because it's obviously not intended behaviour, and it's not a nice welcome to beginners. If this happens only on my machine, then I'd like to understand what's wrong with my environment.

### Environment

I am using npm version 10.8.2
I did "npm install -g npm@latest" as recommended, removed the my-app directory and tried again, but the issue remains.

```
(dev) luc@yoga:~/work/my-app$ npm ls -g
/usr/local/lib
├── corepack@0.28.1
├── html-webpack-plugin@5.6.0
├── n@9.2.3
├── npm@10.8.2
├── react-dom@18.3.1
└── typedoc@0.25.3

```

Environment Info:

  current version of create-react-app: 5.0.1
  running from /home/luc/.npm/_npx/c67e74de0542c87c/node_modules/create-react-app

  System:
    OS: Linux 6.5 Ubuntu 22.04.4 LTS 22.04.4 LTS (Jammy Jellyfish)
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz
  Binaries:
    Node: 20.15.1 - /usr/local/bin/node
    Yarn: 1.22.22 - /usr/local/bin/yarn
    npm: 10.8.2 - /usr/local/bin/npm
  Browsers:
    Chrome: Not Found
  npmPackages:
    react: ^18.3.1 => 18.3.1 
    react-dom: ^18.3.1 => 18.3.1 
    react-scripts: 5.0.1 => 5.0.1 
  npmGlobalPackages:
    create-react-app: Not Found

### Steps to reproduce

As instructed on https://create-react-app.dev/docs/getting-started :

```
npx create-react-app my-app
cd my-app
npm start

```
### Expected behavior

No error message and the browser starting at http://localhost:3000

### Actual behavior

```
(dev) luc@yoga:~/work/my-app$ npm start

> my-app@0.1.0 start
> react-scripts start

Cannot find module 'ajv/dist/compile/codegen'
Require stack:
- /home/luc/work/my-app/node_modules/ajv-keywords/dist/definitions/typeof.js
- /home/luc/work/my-app/node_modules/ajv-keywords/dist/keywords/typeof.js
- /home/luc/work/my-app/node_modules/ajv-keywords/dist/keywords/index.js
- /home/luc/work/my-app/node_modules/ajv-keywords/dist/index.js
- /home/luc/work/my-app/node_modules/schema-utils/dist/validate.js
- /home/luc/work/my-app/node_modules/schema-utils/dist/index.js
- /home/luc/work/my-app/node_modules/webpack-dev-server/lib/Server.js
- /home/luc/work/my-app/node_modules/react-scripts/scripts/start.js
(dev) luc@yoga:~/work/my-app$ 

```
Repository: pytorch
Issue: AOTAutograd.process_inputs doesn't work on nested subclasses
Labels: triaged,tensor subclass,oncall: pt2,module: aotdispatch,module: pt2-dispatcher

### 🐛 Describe the bug

When AOTAutograd starts, it converts all the input into fake tensors via process_input function https://github.com/pytorch/pytorch/blob/32a284c27549449c19e3b1455f531692439d6316/torch/_functorch/aot_autograd.py#L508, this today doesn't take into account that some inputs are nested subclasses. This is bad because AOTAutograd will always create fresh fake tensors for nested subclasses, ignoring the metadata added from Dynamo. 

### Versions

main 

cc @ezyang @albanD @zou3519 @bdhirsh @penguinwu @chauhang
Repository: vscode
Issue: [GNOME Linux] No window decoration (shadow) if a window title bar style is custom
Labels: info-needed,upstream,electron,titlebar,confirmation-pending,wayland

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.92.0
- OS Version: Fedora 40 (GNOME 46)

Steps to Reproduce:

1. Set `window.titleBarStyle` options to `custom` in the settings
2. Run VSCode in the Wayland mode, for example, type it in the terminal:
```
$ ELECTRON_OZONE_PLATFORM_HINT=auto code
```

**Expected behaviour**

There should be a window decoration (shadow) as it is in XWayland compatibility mode:
![image](https://github.com/user-attachments/assets/05cc418e-473a-447a-9176-b6ce88ac2ad8)

**Actual behaviour**

There is no window decoration/shadow:
![image](https://github.com/user-attachments/assets/ab49b4c1-9cf5-4d51-8f94-0500ec73bd32)

But If I set `window.titleBarStyle` to `native`, the window decoration/shadow appears:
![image](https://github.com/user-attachments/assets/d56b4c6d-b2e9-4cde-9e0c-ca6f079555e6)
Repository: go
Issue: os/exec: TestCancelErrors/killed_after_spurious_ErrProcessDone failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "os/exec" && test == "TestCancelErrors/killed_after_spurious_ErrProcessDone"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8740304216196094849)):

    === RUN   TestCancelErrors/killed_after_spurious_ErrProcessDone
    === PAUSE TestCancelErrors/killed_after_spurious_ErrProcessDone
    === CONT  TestCancelErrors/killed_after_spurious_ErrProcessDone
        exec_test.go:1685: Cancel returning an error wrapping ErrProcessDone


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: runtime:cpu2: TestUserArena failures
Labels: NeedsInvestigation,compiler/runtime

```
#!watchflakes
default <- pkg == "runtime:cpu2" && test == "TestUserArena"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8740248133464382897)):

    === RUN   TestUserArena
        arena_test.go:146: expected zero waiting arena chunks, found 1
    --- FAIL: TestUserArena (0.62s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: proposal: expose the `internal/runtime/sys.Prefetch` intrinsic
Labels: Proposal

### Proposal Details

I'm working on a concurrent hash map and with me having experience in using them in highly concurrent contexts with high throughput requirements I knew to add batch Put and Get methods to it. Such API design exposes the very obvious opportunity for prefetching the data.

To experiment with the impact of `internal/runtime/sys.Prefetch` on the batch Get call I modified `runtime/panic.go` to expose the intrinsic. `go tool objdump` then confirmed that a PREFETCHT0 instruction is emitted into the binary as expected.
```go
// in runtime/panic.go
func Prefetch(addr uintptr) {
	sys.Prefetch(addr)
}

// and using it like this
for _, bucket := range initial_buckets_for_keys {
	runtime.Prefetch(uintptr(unsafe.Pointer(bucket)))
}
```

Looking up 100k distinct entries from a hash map with 5000k entries became significantly faster.
```
old: BenchmarkLookupBatches/size=100000-8                      63.14 million_lookups/s
new: BenchmarkLookupBatches/size=100000-8                      96.64 million_lookups/s
```

Which looks like a worthwhile optimization for me.

I personally like how for me this `runtime.Prefetch` Just Works™ so I propose adding just it. I also propose to not tell of it's addition in the change log so people don't use it willy-nilly. Just imagine the damage that all the blog spam will cause in the overall ecosystem, possibly leaking into other language communities too.
Repository: flutter
Issue: [Impeller] Improve mesh gradient performance by removing render to texture for drawVertices w/ texture coordinates.
Labels: P3,e: impeller,team-engine,triaged-engine

To implement drawVertices w/ texture coordinates, Impeller will first render to texture and then re-sample the contents. For an application that makes use of a mesh gradient, this accounts for a substantial amount of performance overhead. See: https://github.com/renancaraujo/omesh/tree/main/flutter/mesh . In short, this package uses fragment shaders + texture coordinates to draw patches of the gradient and stich them together.

We can simplify the process and remove the render to texture by allowing the runtime effect vertex stage to override the position for the fragment stage. This should be equivalent to the current behavior but with no render to texture.

https://github.com/flutter/engine/blob/main/impeller/entity/shaders/runtime_effect.vert

That is, we'd add the following configurable behavior:

```
// Copyright 2013 The Flutter Authors. All rights reserved.
// Use of this source code is governed by a BSD-style license that can be
// found in the LICENSE file.

#include <impeller/types.glsl>

uniform FrameInfo {
  mat4 mvp;
  bool use_coord_position;
}
frame_info;

in vec2 position;
in vec2 coordinatePosition;
// Note: The GLES backend uses name matching for attribute locations. This name
// must match the name of the attribute input in:
// impeller/compiler/shader_lib/flutter/runtime_effect.glsl
out vec2 _fragCoord;

void main() {
  gl_Position = frame_info.mvp * vec4(position, 0.0, 1.0);
  if (frame_info.use_coord_position) {
    _fragCoord = coordinatePosition;
  } else {
    _fragCoord = position;
  }
}
```
Repository: vscode
Issue: Notebook Sticky Scroll does not show up on document reopen
Labels: bug,notebook-sticky-scroll

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes/No

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->

https://github.com/user-attachments/assets/daf6440c-72e9-447e-838b-e2dea423f708
Repository: transformers
Issue: Implement `generate` (inference) for torch exported text-generation models
Labels: Feature request,Generation,ExecuTorch

### Feature request

Unlike `torch.compile`, `torch.export` only export the inner transformer to predict a single token for text-generation models. The autoregressive logics are not included in the exported artifact. For ExecuTorch Runtime, the autoregressive logics is implemented there, either directly in c++ ([code pointer](https://github.com/pytorch/executorch/blob/main/examples/models/llama2/runner/runner.cpp#L310-L415)) or python ([code pointer](https://github.com/pytorch/executorch/blob/main/examples/models/llama2/runner/generation.py#L70-L124)). Here is a minimal `generate` impl in a test for Phi3-mini in 🤗  ([code pointer](https://github.com/huggingface/transformers/blob/543df489147412efb20575c3c2a3fb69a18ac107/tests/models/phi3/test_modeling_phi3.py#L73)). 

Instead of duplicate the generate logics for each exported model, it's better to have a common implementation of `generate` that can be used by any exported text-generation mdoel.

### Motivation

To support the new "Export to ExecuTorch" workflow. This would enable users to have a unified `generate` experience as they run inference using eager or compiled model. 

### Your contribution

TBD
Repository: go
Issue: proposal: x/crypto/ssh: hostbased authentication method
Labels: Proposal,Proposal-Crypto

### Proposal Details

[RFC 4252 Section 9](https://datatracker.ietf.org/doc/html/rfc4252#section-9) provides for "hostbased" authentication based on the private host key of the client. Currently the ssh implementation does not support this method.

I propose either the addition of this method, or allowing the implementation of the `AuthMethod` interface by clients. The former would strengthen compliance of the RFC as the authentication method is indeed deemed `OPTIONAL`. The latter option would allow for customize-ability by consumers of the package (at their own peril, of course).

To my naive eyes, the message format for "hostbased" per the RFC is not too dissimilar to standard private key based authentication. Given the security concerns expressed towards the end of section 9, it may be desirable to mark this method insecure.

My particular use case involves connecting to machines within a well guarded internal network where host-based auth is the expected standard.

I am open to contribute time/code to the implementation of this.
Repository: godot
Issue: Wayland completely unreceptive to touch input
Labels: bug,platform:linuxbsd,topic:porting,topic:input

### Tested versions

4.3rc2

### System information

Godot v4.3.rc2 - Nobara Linux 40 (GNOME Edition) - Wayland - Vulkan (Mobile) - dedicated NVIDIA GeForce RTX 3050 Ti Laptop GPU - 11th Gen Intel(R) Core(TM) i7-11370H @ 3.30GHz (8 Threads)

### Issue description

I have a Microsoft Surface Studio laptop with a touchscreen.

Touchscreen works fine in regular Godot.

However, switching the "prefer Wayland" setting on renders the editor completely unresponsive to touch (mouse till works fine).

### Steps to reproduce

1. Enable "prefer wayland" setting & restart.
2. Touch the screen and try to get the Godot editor to react

### Minimal reproduction project (MRP)

N/A
Repository: transformers
Issue: CLIP is ExecuTorch compatible
Labels: Feature request,ExecuTorch

### Feature request

Enable CLIP to ["Export to ExecuTorch"](https://github.com/huggingface/transformers/issues/32253) workflow

### Motivation

See details in #32253

### Your contribution

Support on common export issues
Repository: transformers
Issue: Bart/Wav2Vec2 is ExecuTorch compatible
Labels: Feature request,ExecuTorch

### Feature request

Enable Bart/Wav2Vec2 to ["Export to ExecuTorch"](https://github.com/huggingface/transformers/issues/32253) workflow

### Motivation

See details in #32253

### Your contribution

TBD
Repository: transformers
Issue: TrOCR is ExecuTorch compatible
Labels: Feature request,ExecuTorch

### Feature request

Enable TrOCR to ["Export to ExecuTorch"](https://github.com/huggingface/transformers/issues/32253) workflow

### Motivation

See details in #32253

### Your contribution

TBD
Repository: pytorch
Issue: Add a warning for `drop_last` argument in `DataLoader`
Labels: module: dataloader,triaged

### 🚀 The feature, motivation and pitch

I was working with PyTorch data loaders and realised that some argument combinations may lead to sudden training pipeline crashing. 

Particularly, if the `drop_last` argument of the `DataLoader` object is set to `False` and `len(dataset) % batch_size == 1` then the last batch will be of size `1`. That can lead to crashing of the training pipeline in the end of the epoch in case the neural network contains a `BatchNorm` module (it requires batches of size `> 1`). 

The problem is that this issue is hard to detect, because only the last batch causes a conflict with the network structure.

The suggestion is to raise a warning when encountered the combination `drop_last == False` and `len(dataset) % batch_size == 1`

### Alternatives

_No response_

### Additional context

_No response_

cc @andrewkho @gokulavasan @SsnL @VitalyFedyunin @dzhulgakov
Repository: go
Issue: cmd/internal/testdir: Test/64bit.go failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "cmd/internal/testdir" && test == "Test/64bit.go"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8740248133701416641)):

    === RUN   Test/64bit.go
    === PAUSE Test/64bit.go
    === CONT  Test/64bit.go
        testdir_test.go:145: exit status 1
            go: error obtaining buildID for go tool compile: signal: segmentation fault (core dumped)
            
    --- FAIL: Test/64bit.go (16.09s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: kubernetes
Issue: option to suppress DNSConfigForming warning log messages and events
Labels: sig/node,kind/feature,needs-triage

### What would you like to be added?

A kubelet flag that will disable or otherwise prevent these warning messages from being printed.



### Why is this needed?

The condition that causes the DNSConfigForming "Nameserver limits were exceeded, some nameservers have been omitted, the applied nameserver line is" warning log messages and k8s events is well known:
- https://github.com/kubernetes/kubernetes/issues/82756
- https://github.com/kubermatic/kubeone/issues/1744
- http://jpetazzo.github.io/2024/05/12/understanding-kubernetes-dns-hostnetwork-dnspolicy-dnsconfigforming/
- https://kubernetes.io/docs/tasks/administer-cluster/dns-debugging-resolution/#known-issues

However, in some network/cloud environments, having > 3 DNS servers is effectively considered correct or unavoidable and it is not always possible to limit. For example, AFAIK NetworkManager does not have an option to limit the number of DNS servers received via DHCP.  So this is generally considered to be a problem with no solution that you just have to live with.

However the issue with that is the constant noise and log pollution generated by these messages, from kubelet and any pods that use hostNetwork. It fills up syslog/journald on the nodes and contributes to unnecessary load (IOPS and storage) when the events are written in etcd, especially for large clusters, all of which is really unnecessary because the issue is considered harmless and can be safely ignored - so let's actually ignore it! _The noise produced by these warnings is worse than the actual condition that they are warning about._ So can we fully suppress these events and messages? There could be a kubelet option like `--ignore-dns-nameserver-limit-warning=True` to hide the warnings or `--force-truncate-nameservers=3`  to explicitly drop any nameservers after the first 3 so that we don't need to complain about them.
Repository: electron
Issue: Best Practices/Security - Mark "Enable process sandboxing" as enabled by default
Labels: documentation :notebook:

Most sections in the Best Practices/Security guide feature a handy information box when the recommendation is the default behavior. 

This seems to be missing from _4. Enable process sandboxing_

According to the documentation, process sandboxing is enabled per default, by now: _"Starting from Electron 20, the sandbox is enabled for renderer processes without any further configuration."_

Could the info box be added to this section?
Repository: vscode
Issue: Add copy button in exception peek view
Labels: feature-request,debug

Type: <b>Feature Request</b>

Add copy button for error when red layer next to "x" button
Ticket is related with https://github.com/microsoft/vscode/issues/221643


VS Code version: Code 1.92.0 (b1c0a14de1414fcdaa400695b4db1c0799bc3124, 2024-07-31T23:26:45.634Z)
OS version: Windows_NT x64 10.0.22631
Modes:


<!-- generated by issue reporter -->
Repository: pytorch
Issue: If you compile a function/module, we should definitely attempt to compile it (don't try to skip it)
Labels: triaged,oncall: pt2,module: dynamo

### 🐛 Describe the bug

Related: https://github.com/pytorch/pytorch/issues/128954

Precipitating issue: https://github.com/pytorch/pytorch/issues/132921

Let's say I have an nn.Module and I compile() it. I should definitely attempt to compile it. I should not silently (except on debug dynamo logging) skip it just because it thinks it is skipfiled. Even if I skip it, something should show up in TORCH_TRACE/tlparse saying that it was skipped.

I am a little unsure how to implement this. The eval frame handler doesn't distinguish if it was the first frame after you set it, or some deeply nested frame handler invocation.

If we switch to @jansel's idea of manually implementing a bytecode interpreter instead of using the eval frame API (to solve future Python version incompatibility problem), we would be able to tell because we need to recursively apply bytecode interpreter to resumptions and those can be marked differently. But actually, in this universe, we would probably be much less aggressive about recursively trying to compile things; if we get to a frame where we are unable to instrument internal calls to reenable the bytecode interpreter, we would just not recurse. In some cases like https://github.com/pytorch/pytorch/issues/128954 this would be desirable.

We don't have to wait for a manual bytecode interpreter to implement this. We can setup resumption functions that disable the eval frame to avoid recursing. In that case, we could dramatically reduce the incidence we hit skipfiles, at which point we can just log them all. We have to decide this is the right policy in general, not just in #128954 like situations.

There are probably less "blow it all up" ways to immediately fix this as well.

cc @chauhang @penguinwu @rec @yanboliang @anijain2305 @williamwen42 @jansel 

### Versions

main
Repository: transformers
Issue: chore: move `conftest.py` to `tests/`
Labels: Feature request,WIP

### Feature request

It's a common practice to place the `conftest.py` file within the `tests/` directory.


### Your contribution

Initial Attempt: https://github.com/huggingface/transformers/pull/32011

### References

* https://github.com/pytest-dev/pytest/discussions/10708
Repository: pytorch
Issue: [inductor] If the pattern matcher causes a new mutable op to be added to the graph, it doesn't update the mutation regions
Labels: triaged,oncall: pt2,module: inductor

I'm not sure if this is possible though

cc @ezyang @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire
Repository: kubernetes
Issue: CVE PLACEHOLDER ISSUE
Labels: kind/bug,area/security,lifecycle/frozen,committee/security-response,triage/accepted

/triage accepted
/lifecycle frozen
/area security
/kind bug
/committee security-response
Repository: go
Issue: net/http: TestClientCallsCloseOnlyOnce/h1 failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "net/http" && test == "TestClientCallsCloseOnlyOnce/h1"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8740234169836945329)):

    === RUN   TestClientCallsCloseOnlyOnce/h1
    === PAUSE TestClientCallsCloseOnlyOnce/h1
    === CONT  TestClientCallsCloseOnlyOnce/h1
        client_test.go:2065: dial tcp 127.0.0.1:51531: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
    --- FAIL: TestClientCallsCloseOnlyOnce/h1 (1.14s)


— [watchflakes](https://go.dev/wiki/Watchflakes)