sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: TypeScript
Issue: "No inputs were found in config file", when looking at some files within node_modules
Labels: Help Wanted,Possible Improvement

<!-- ⚠️⚠️ 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.96.4
- OS Version: Darwin arm64 23.5.0

When a node_module bundles in a tsconfig file I'll end up getting this error. Most packages do not do this, it makes sense, the tsconfig is really just for builds. BUT occasionally they do bundle it, and when that happens obviously sources can not be found. I'll contact the offending package, but a built in solution would be nice as well since this is a frequent problem - this happens multiple times per year for me.

**Example repo:** https://github.com/deca-inc/vscode-repro-issue-238768

**Steps to Reproduce:**
1. Make any basic typescript project, with any package manager
2. Install a package that has a tsconfig.json within it, where the inputs won't be found
3. Import that node_module then try to "meta/command+click" into the definition of that import

**Outcome:** A "Problem" appears under the Problem tab. There's no way to make this problem go away unless you close the files and close vscode completely. 

**Possible solutions:**
1. Don't look for tsconfig files under node_modules ever
2. Document how to ignore specific offending packages - it's pretty hard to find the answer for this out there on search engines.
Repository: go
Issue: proposal: allow eliding "_" fields in unkeyed struct literals
Labels: LanguageChange,Proposal,LanguageChangeReview,LanguageProposal

### Proposal Details

Change treatment of  `_` fields so that they may be omitted from unkeyed struct literals and (if omitted) do not count as unexported fields.  In the case of a struct with multiple `_` fields, either all must be present or all must be omitted, to avoid ambiguity.

The reason for this is to make it easier to use `_` fields for things like establishing field alignment, modifying layout, and [other type attributes](https://go.dev/issue/67265). Without this change, `_` fields require providing pointless initial "values" in unkeyed literals, and make it impossible to use unkeyed literals across package boundaries (it may be bad style, but it is legal Go and probably exists -- a particular use case is Windows).  One specific motivation was looking at the work required and effects on code/tools/usability to add `structs.HostLayout` annotations to the code generated by cgo; it was messy and unpleasant.

This breaks no Go code, so it is compatible.

It also "potentially affects" very little code anyway; unkeyed literals for structs with `_` fields are rare.  I ran an ecosystem analysis of 44,000 Go projects that were imported 5 or more times.  Of those, there were only 137 instances of an unkeyed literal "initializing" a `_` field.  Of that 137, 127 were in tests, of of that 127, 75 were literals for the same struct type.  Of the 10 "non-test" examples, it turned out to really be only 5 because of duplication in the report, appearing in only 3 p[rojects, and 2 of that 3 involved VNC (i.e., derivative code).

In any case where the export-forbidding properties of `_` were desirable, renaming that field to any other export-forbidding name (e.g., `__` or `underscore`) obtains the same effect.

This will require a change to the Go compiler, and to tools that analyze Go code, so that both forms of struct literals are recognized.
Repository: puppeteer
Issue: [Bug]: Dblclick events can get dropped when using WebDriver BiDi with Chrome
Labels: bug,P1,confirmed,bidi

### Minimal, reproducible example

```TypeScript
import puppeteer from 'puppeteer';

const puppeteerOptions = {
  //browser: 'firefox',
  headless: false,
  protocol: 'webDriverBiDi',
}


function timeout(time) {
  return page.evaluate(time => {
          return new Promise(r => {
                  setTimeout(r, time)
          })
  }, time)
}

async function enterValue(selector, value) {
  const el = (await page.$(selector))
  await el.evaluate(node => ((node).value = ''))
  await el.type(value)
  await el.press('Enter')
}

const browser = await puppeteer.launch(puppeteerOptions);

const page = await browser.newPage();

await page.goto(String.raw`data:text/html,
  <style>

.todo-list li.editing .edit {
	display: block;
}

.todo-list li.editing .view {
	display: none;
}

.todo-list li label {
	display: block;
}

.todo-list li .edit {
	display: none;
}

</style>
<script>
function editTodo() {
    item.className = 'editing';
}
function keydup(event) {

    if (event.key === 'Enter') {
        item.className = '';
        document.querySelector('label').innerHTML = item.querySelector('.edit').value;
    }
}
</script>

<ul class="todo-list">
    <li id=item>
      <div class="view">
        <input class="toggle" type="checkbox" />
        <label ondblclick="editTodo(event)">Foo</label>
        <button class="destroy"></button>
      </div>
      <input class="edit"  onkeyup="keydup(event)" type="text"  />
    </li>
  </ul>
<div id="output"></div>
`)

await page.click('label',  { count: 2 });
await enterValue('.edit', 'edited!')

await page.click('label',  { count: 2 });
await enterValue('.edit', 'edited again!')

console.log(await page.evaluate(() => document.querySelector("label").innerText));

await browser.close();
```

### Background

This is a reduced test case from the vue e2e test suite.

### Expectation

The script should print `edited again!`

### Reality

It prints `edited!`. In Chrome without WebDriver BiDi and in Firefox with WebDriver BiDi it prints `edited again!`

### Puppeteer configuration file (if used)

```TypeScript

```

### Puppeteer version

24.1.1

### Node version

23.5.0

### Package manager

yarn

### Package manager version

1.22.22

### Operating system

macOS
Repository: ollama
Issue: Problems with deepseek-r1:671b, ollama keeps crashing on long answers
Labels: bug

### What is the issue?

Hi all,
  I'm using an r960 with 2TB of ram, so ram is not a problem here. I'm experiencing constant crashes of ollama 0.5.7 and deepseek-r1:671b, even increasing the context window with the command /set parameter num_ctx 4096.
  I also tried a second system, an r670 csp with 1TB of ram, but the problem occurs in the same way.
  I'm not able to use gpu due to the massive size of the model, anyway plenty of cores do the job for my current pourposes.

  os are ubuntu 22.04.5 and 24.04.1



### OS

Linux

### GPU

_No response_

### CPU

Intel

### Ollama version

0.5.7
Repository: tailwindcss
Issue: [v4] Ignore certain paths from scanning no longer supported
Labels: v4

**What version of Tailwind CSS are you using?**

v4.0.0

**What build tool (or framework if it abstracts the build tool) are you using?**

Vite 6

**What version of Node.js are you using?**

22.13

**Describe your issue**

In v3 one could add a line with an exclamation mark `!` prefix in the `tailwind.config.js` to exclude certain files or paths from being scanned:

```js
    content: [
        './resources/views/**/*.blade.php',
        '!./resources/views/somefoldername/*',
    ],
```

but that option seems to have vanished in v4. I know I can do `@import 'tailwindcss' source(none);` and then  `@source '../../../resources/views';` which works but there is no way to exclude a subfolder from that path.

One work around is to add all the subfolders by hand, but that's a bit of a PITA when the project grows and you forget you need to add every view subfolder to the config css now.
Repository: next.js
Issue: Webpack hot reloading stops working if projects is located in a folder starting with ".git"
Labels: Webpack

### Link to the code that reproduces this issue

https://github.com/lorissikora/empty-nexts-template

### To Reproduce

1. Create or navigate to a folder starting with `.git` (example `.git-projects`)
2. Create a new project inside of it (example `npx create-next-app@canary` and select defaults)
3. `next dev` (without `--turbo`)
4. Open example page in browser
5. Change `src/app/page.tsx`
6. Observe no change


### Current vs. Expected behavior

**Current**
If the parent folders of a nextjs application start with ".git", the webpack dev server (without `--turbo`) will not hot reload any changes made to the app.

Example paths of this might be:
- `/path/to/my/.git-projects/nextjs-app` (this is my setup, which is how I found this in the first place)
- `/path/to/my/.git-projects/a/b/c/nextjs-app`
- `/path/to/my/.git/nextjs-app`

This is not an issue when using Turbopack.

**Expected**
Hot reloading should work.

---

I honestly don't expect this to be fixed, but I would love for others, who are facing a similar issue, to find this and spare them of multiple hours of wondering why this isn't working as expected.


### Provide environment information

```bash
/bin/sh: pnpm: command not found

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.1.0: Thu Oct 10 21:03:11 PDT 2024; root:xnu-11215.41.3~2/RELEASE_ARM64_T6020
  Available memory (MB): 32768
  Available CPU cores: 12
Binaries:
  Node: 22.9.0
  npm: 10.8.3
  Yarn: 1.22.19
  pnpm: N/A
Relevant Packages:
  next: 15.2.0-canary.27 // Latest available version is detected (15.2.0-canary.27).
  eslint-config-next: 15.2.0-canary.27
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.7.3
Next.js Config:
  output: N/A
```

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

Webpack

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

next dev (local)

### Additional context

Was tested on `@latest` and `@canary`. Ignore the github repo, it is simply the default template of the current canary version.
Repository: ollama
Issue: Ollama: torch.OutOfMemoryError: CUDA out of memory
Labels: bug

### What is the issue?

Running some tests using pytest with the following 6 models.  What I find is that if I run all tests with each model before go on to the next model, the tests mostly worked fine. 123/126 passed.  But if I run each test against all 6 models sequentially and then go to the next test then I see hangs or out of memory error.  Is this a known issue? I expect the order of running tests using Ollama should not matter.

ollama version is 0.5.7
pytest 8.3.4
| NVIDIA-SMI 550.144.03             Driver Version: 550.144.03     CUDA Version: 12.4     |
|   0  NVIDIA GeForce RTX 4070 Ti     Off |   00000000:01:00.0  On |                  N/A |
Linux kennethpc 6.8.0-51-generic #52-Ubuntu SMP PREEMPT_DYNAMIC Thu Dec  5 13:09:44 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

qwen2:latest
qwen2.5:latest
mistral:latest
llama3-groq-tool-use:latest
llama3.2:latest
llama3.2:latest

Here is some examples of the errors. Sometimes I simply see hangs:
FAILED tests/_1_misc_test.py::test_t6_func[mistral:latest] - assert None is not None
FAILED tests/_1_misc_test.py::test_t6_func[llama3-groq-tool-use:latest] - assert None is not None
FAILED tests/_2_rag_test.py::test_t7_func[qwen2:latest-chroma] - assert 768 == 384
FAILED tests/_2_rag_test.py::test_t7_func[qwen2.5:latest-chroma] - torch.OutOfMemoryError: CUDA out of memory. Tried to allocate 20.00 MiB. GPU 0 has a total capacity of 11.72 GiB of which 41.50 MiB is free. Process 263255 has 3.40 GiB memory in use. Process 263532 has 6.09 GiB memory in use. In...
FAILED tests/_2_rag_test.py::test_t7_func[qwen2.5:latest-huggingface] - torch.OutOfMemoryError: CUDA out of memory. Tried to allocate 20.00 MiB. GPU 0 has a total capacity of 11.72 GiB of which 41.50 MiB is free. Process 263255 has 3.40 GiB memory in use. Process 263532 has 6.09 GiB memory in use. In...

### OS

Linux

### GPU

Nvidia

### CPU

Intel

### Ollama version

0.5.7
Repository: puppeteer
Issue: [Feature]: make DOM events available
Labels: feature

### Feature description

#12682 proposes to add a `waitForEvent` to `Page`. This idea is a combination of two ideas:
1. Listening to events that are emitted by an element on the page and getting them out to the Puppeteer context
2. Finding the element itself and creating a Promise that resolves once an event (or a number of events) have been emitted/received.

I would like to focus on idea number 1 and take it a step further: get to a situation where we can say 'Puppeteer, please listen to events of type so-and-so that are emitted by in-page object such-and-such, and expose them in the Puppeteer context'. In other words:
```ts
// getting a handle
const button = await page.evaluateHandle(() => document.getElementById('button'))

const buttonThatEmitsClickEvents = await doSomethingInvolving(
  button, // probably, right? unless this could become an 'instance method' on `ElementHandle` or `JSHandle`...
  'click', // definitely, because we need to know what to listen to, we can't listen to all types of events
  /* and maybe something else */
);

// the idea being that we can now
buttonThatEmitsClickEvents.addEventListener('click', e => {
  // now the question is of course: which properties of the original click event made their way to this `e`? Probably not
  // `preventDefault()`, but I think we should be able to get `offsetX` for example. 
})
```

As you can see, I'm not sure what the API would look like exactly. Also I don't know if this even makes sense as a feature for Puppeteer. I suppose it could be argued that there is no need to get events from the page, because any event that happens in the page was probably caused by Puppeteer itself, so this adds no new information. On the other hand, it could also be argued that someone might want to test some functionality that produces custom DOM-like events.

What do you think?

(By the way: I really needed this for one of my projects, so I created [an npm package](https://www.npmjs.com/package/puppeteer-event-target-handle) that provides a form of the functionality that I am proposing.)
Repository: pytorch
Issue: Dynamo performance test benchmarks reuse model state between eager and compiled
Labels: oncall: pt2

### 🐛 Describe the bug

See `model`:
https://github.com/pytorch/pytorch/blob/64cd81712ddf867d1c4dc46ba4554d40d6d7d610/benchmarks/dynamo/common.py#L3431-L3470

Later, it is also used by the `speedup_experiment`. This can cause issues with stateful models like convit_base: https://github.com/huggingface/pytorch-image-models/blob/d81da93c1640a504977b0ee494791e5c634ec63c/timm/models/convit.py#L67-L70, or DDP/FSDP wrappers.

If we deepcopy the model, a few cudagraphs perf benchmarks start to fail e.g. convit_base, llama, cm3leon_generate
`RuntimeError: Error: accessing tensor output of CUDAGraphs that has been overwritten by a subsequent run.`

### Versions

main

cc @chauhang @penguinwu
Repository: PowerToys
Issue: SLNX solution files
Labels: Area-Build,Needs-Triage

### Description of the new feature / enhancement

So, today I learned about the existence of a new format: SLNX. I opened this issue to track the what, when and why. I presume it'll be a big task.

### Scenario when this would be used?

Using new solutions?

### Supporting information

I find it strange to see how few info is online.
https://blog.ndepend.com/slnx-the-new-net-solution-xml-file-format/
Repository: ollama
Issue: Support Request for jonatasgrosman/wav2vec2-large-xlsr-53-italian
Labels: model request

    (.venv) raphy@raohy:~/llama.cpp$ git clone https://huggingface.co/jonatasgrosman/wav2vec2-large-xlsr-53-italian
    Cloning into 'wav2vec2-large-xlsr-53-italian'...
    remote: Enumerating objects: 99, done.
    remote: Total 99 (delta 0), reused 0 (delta 0), pack-reused 99 (from 1)
    Unpacking objects: 100% (99/99), 545.41 KiB | 1.55 MiB/s, done.
    Filtering content: 100% (2/2), 2.35 GiB | 92.80 MiB/s, done.
    
    
    (.venv) raphy@raohy:~/llama.cpp$ ollama create Modelfile 
    transferring model data 
    unpacking model metadata 
    Error: Models based on 'Wav2Vec2ForCTC' are not yet supported
Repository: ollama
Issue: Support Janus-Pro-7b for vision models
Labels: feature request

Just announced and performing great with OCR
https://huggingface.co/deepseek-ai/Janus-Pro-7B
Repository: pytorch
Issue: Error instead of silent specializing when an unbacked dimension has a value range cardinality of one
Labels: oncall: pt2,module: dynamic shapes

```
import torch

torch._dynamo.config.automatic_dynamic_local_pgo = False

@torch.compile()
def fn(x):
    return torch.cat([x, torch.ones(5, 5)])

x = torch.ones(5, 5)
torch._dynamo.decorators.mark_unbacked(x, 0)
torch._dynamo.decorators.mark_unbacked(x, 1)
fn(x)
```

Results in

```
L_x_: "f32[u0, 5][5, 1]cpu"
```

even though we explicitly marked x.size()[1] as unbacked.

We should error similar to the constraint tests in mark_dynamic

cc @chauhang @penguinwu @ezyang
Repository: next.js
Issue: Calling a server action during render tries to update `Router` component, causing an error
Labels: Runtime

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/crazy-field-gnyj7q

### To Reproduce

1. Visit the reproduction app.
2. In the app preview, see the Next.js error pop-up:

    > __Console Error__
    >
    > Cannot update a component (`Router`) while rendering a different component (`Demo`). To locate the bad setState() call inside `Demo`, follow the stack trace as described in https://react.dev/link/setstate-in-render

    Note that there is no explicit `setState()` call inside the component.


### Current vs. Expected behavior

Currently, calling a server action during a render causes a React error (see above).

The expected behavior is that the server action returns a `Promise` (without causing a React error), and that the `Promise`, if properly cached, can be consumed with `use` (without causing a React error).


### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Sun Aug  6 20:05:33 UTC 2023
  Available memory (MB): 4102
  Available CPU cores: 2
Binaries:
  Node: 20.9.0
  npm: 9.8.1
  Yarn: 1.22.19
  pnpm: 8.10.2
Relevant Packages:
  next: 15.2.0-canary.27 // Latest available version is detected (15.2.0-canary.27).
  eslint-config-next: N/A
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.3.3
Next.js Config:
  output: N/A
```

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

Runtime

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

next dev (local), next start (local)

### Additional context

_No response_
Repository: ollama
Issue: s390x support for the install.sh
Labels: feature request

It would be good if the install.sh script be capable of ollama install in s390x machines, it would make life easier for multiple developers currently working on it. 

curl -fsSL https://ollama.com/install.sh | sh

You may say that you current don't have a s390x to develop it , you can get a trial one for 120 days [here ](https://community.ibm.com/zsystems/form/l1cc-oss-vm-request/) .

The process to build it from source works fine (make -j 5) command as it works fine for any linux other arch/x86/arm machines.

Thanks
Repository: flutter
Issue: Attestation failed while packaging Flutter 3.29.0-0.2.pre beta release
Labels: team-release

Google internal only logs: https://ci.chromium.org/ui/p/dart-internal/builders/flutter/Windows%20Production%20Engine%20Drone/8248/infra

```
flutter_windows_3.29.0-0.2.pre-beta.zip provenance rejected: NoAttestationsProvided: Caller didn't provide any attestation with subject matching the digest of the requested artifact: '_:{sha256:a475487459ea10bd47a58763387b1d4b3545670e8b818637145e57f7c0ee485e}'.
```
Repository: yt-dlp
Issue: YouTube Clipped audio? (over 0dBFS)
Labels: question

### DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

- [x] I understand that I will be **blocked** if I *intentionally* remove or skip any mandatory\* field

### Checklist

- [x] I'm asking a question and **not** reporting a bug or requesting a feature
- [x] I've looked through the [README](https://github.com/yt-dlp/yt-dlp#readme)
- [x] I've verified that I have **updated yt-dlp to nightly or master** ([update instructions](https://github.com/yt-dlp/yt-dlp#update-channels))
- [x] I've searched [known issues](https://github.com/yt-dlp/yt-dlp/issues/3766) and the [bugtracker](https://github.com/yt-dlp/yt-dlp/issues?q=) for similar questions **including closed ones**. DO NOT post duplicates
- [x] I've read the [guidelines for opening an issue](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#opening-an-issue)

### Please make sure the question is worded well enough to be understood

Hi all! 

I have been recently investigating something interesting I noticed with the music I downloaded from YouTube using some various tools such as this one.

The issue is that some of the songs I download go over 0dBFS! (here is the one from the example [Euphoria](https://music.youtube.com/watch?v=KZ-daHDx6HA&si=0MnqbM0U8FqXOygB) 
That data, that could seem to be lost because of it being clipped, actually can be recovered if I bring the volume down using an audio editor such as adobe audition.

Here is the raw audio as it comes from youtubedl in webm format, encoded with OPUS: [image](https://imgur.com/a/VD7MHdu)

And here it is when I lower its overall volume: [image](https://imgur.com/a/GTso9pK)

As you can see the clipped data can actually be recovered, that is I think, because of the 32bit properties the file has as you can see here: [image](https://imgur.com/a/pxswje2)

I am still to try capturing youtube's audio with a 32 bit capable sound card, but still, it would NOT make any sense for the audio played by youtube to be anywhere what the downloaded is, clipped. 

I have been behind this for a while but don't seem to be getting any close. 
What are your thoughts on this? 
There is obviously no way youtube songs are uploaded in a 32 bit floating point format... The standard is 24 bit and 16 for distribution 

Are we maybe in front of what it is called "loudness war"?

### Provide verbose output that clearly demonstrates the problem

(It's not actually a problen with yt-dlp itself)

- [ ] Run **your** yt-dlp command with **-vU** flag added (`yt-dlp -vU <your command line>`)
- [ ] If using API, add `'verbose': True` to `YoutubeDL` params instead
- [ ] Copy the WHOLE output (starting with `[debug] Command-line config`) and insert it below

### Complete Verbose Output

```shell

```
Repository: flutter
Issue: When releasing 3.29 beta provenance rejected
Labels: c: regression,a: release,team-release

https://ci.chromium.org/ui/p/dart-internal/builders/flutter/Windows%20Production%20Engine%20Drone/8248/infra

```
flutter_windows_3.29.0-0.2.pre-beta.zip provenance rejected: NoAttestationsProvided: Caller didn't provide any attestation with subject matching the digest of the requested artifact: '_:{sha256:a475487459ea10bd47a58763387b1d4b3545670e8b818637145e57f7c0ee485e}'
```

Google owned bug that covers some of how provenance works in builds https://b.corp.google.com/issues/309500637 
Google owned document about provenance. [go/bcid-for-flutter-in-google3](http://goto.google.com/bcid-for-flutter-in-google3)