sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: node
Issue: http.server.close() closes idle connections in v20 and v21
Labels: http

### Version

21.7.3

### Platform

_No response_

### Subsystem

_No response_

### What steps will reproduce the bug?

_No response_

### How often does it reproduce? Is there a required condition?

_No response_

### What is the expected behavior? Why is that the expected behavior?

_No response_

### What do you see instead?

In [18.20.3](https://github.com/nodejs/node/releases/tag/v18.20.3) release notes, it shows: 
"This release fixes a regression introduced in Node.js 18.19.0 where http.server.close() was incorrectly closing idle connections."

This fix was made on this [pull request](https://github.com/nodejs/node/pull/52336) in this [commit](https://github.com/nodejs/node/pull/52336/commits/1a435a9b5618c2ca966a71716baacd56625f4e3a) where `server.closeIdleConnections();` is removed from `httpServerPreClose` function.

This was fixed for next 18.x releases, as can be seen [here](https://github.com/nodejs/node/blob/v18.20.4/lib/_http_server.js#L508), but on node 20.x and node 21.x, the regression was also included and has not been removed, as can be seen [here](https://github.com/nodejs/node/blob/v21.7.3/lib/_http_server.js#L515).




### Additional information

_No response_
Repository: angular
Issue: [Bug]: Cannot read properties of undefined (reading 'each') of zone-testing
Labels: area: zones

### Which @angular/* package(s) are the source of the bug?

zone.js

### Is this a regression?

No

### Description

Transfer from https://github.com/thymikee/jest-preset-angular/issues/2211

### Please provide a link to a minimal reproduction of the bug

The repo is in the linked issue provided
Repository: godot
Issue: Local to scene resource unlinks in inherited scenes when changed outside them
Labels: bug,topic:editor

### Tested versions

- Reproducible in: 3.0.stable, 3.5.stable, 3.6.rc1, 4.0.stable, 4.2.2.stable.mono, 4.3.beta3.mono

### System information

Godot v4.3.beta3.mono - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 2060 (NVIDIA; 31.0.15.4584) - AMD Ryzen 5 2600 Six-Core Processor (12 Threads)

### Issue description

When non-imported resource set to Local to Scene is changed, all inherited scenes' nodes that used this resource "unlink" it, creating an identical copy saved inside the scene, unless the resource was changed in an inherited scene. Works when setting the local to scene option to true too.

### Steps to reproduce

1. Create a scene
2. Add a node that uses a non-imported resource
3. Set the resource to be local to scene
4. Create a scene that inherits this scene
5. Change a resource's parameter outside the inherited scene; definitely works in the inherited scene's base scene
6. Save the base scene
7. Open the inherited scene, the resource should be unlinked

Using the MRP: change any parameter in the example_material or example_stylebox thorugh the base_scene inspector, save the scene, then look to the corresponding resources in inherited_scene

### Minimal reproduction project (MRP)

[inherited resource bug repro.zip](https://github.com/user-attachments/files/16310764/inherited.resource.bug.repro.zip)
Repository: vscode
Issue: Deprecated settings do not show in settings UI even when configured by the user
Labels: bug,settings-editor,confirmation-pending

<!-- ⚠️⚠️ 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.91.1
Commit: f1e16e1e6214d7c44d078b1f0607b2388f29d729
Date: 2024-07-09T22:08:12.169Z
Electron: 29.4.0
ElectronBuildId: 9728852
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Linux x64 6.5.0-41-generic

Steps to Reproduce:

1. Deprecate an existing setting using either `deprecateMessage` or `markdownDeprecationMessage`.
2. Modify the setting either in the workspace or user settings JSON files.
3. Open the settings UI.
4. Expect to see the setting, but it's not there.

The [docs](https://github.com/microsoft/vscode-docs/blob/d7fa4a3ee512344e347d6ebd2ba881ce770617d8/api/references/contribution-points.md?plain=1#L331) say that the setting to be visible in the settings UI when modified by the user (emphasis mine):

> If you set `deprecationMessage`, or `markdownDeprecationMessage`, the setting will get a warning underline with your specified message. Also, the setting will be hidden from the settings UI **_unless it is configured by the user_**.
Repository: rust
Issue: Request for `tune-cpu` code generation option to be promoted to stable
Labels: T-compiler,A-CLI,A-targets

I'm raising this issue as I couldn't find an existing tracking issue for the [`tune-cpu` code generation option](https://doc.rust-lang.org/rustc/codegen-options/index.html#tune-cpu) being stabilized - and I would like it to be.

A common use of `target-cpu` is to specify the oldest type of CPU an application supports.  This will unfortunately result in a binary _tuned for that specific CPU_ - since by default `tune-cpu` picks up the value from `target-cpu`.  I would like to be able to use `tune-cpu=generic` to resolve this without needing to use the nightly compiler.
Repository: ollama
Issue: Expose model capabilities via /api/tags and /v1/models[/model]
Labels: feature request,api

It would be convenient if the capabilities of a model (completion, tools, insert, \<future caps\>) were made available so that clients can adjust API calls.
Repository: ui
Issue: [bug]: shadcn charts (stacked charts) 
Labels: bug

### Describe the bug

![Screenshot 2024-07-19 at 8 23 10 PM](https://github.com/user-attachments/assets/f0693943-a56c-48b3-9499-994a4ec61197)
not rendering correctly

### Affected component/components

chart, recharts

### How to reproduce

-

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
-
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: flutter
Issue: AnimatedCrossfade's ClipRect should be configurable.
Labels: c: new feature,framework,c: proposal,P3,team-framework,triaged-framework

### Use case

Using overflowing widgets or shadow inside AnimatedCrossfade is not possible currently. I can't see any reason for clipping being default behavior, we can clip the children we pass if that's desired. If this widget will keep having ClipRect wrapped around it should at least be configurable.

### Proposal

If we add a property for configuring [ClipRect in AnimatedCrossfade](https://github.com/flutter/flutter/blob/89c88ae8e8ee1cdfc439bd4ac95b27b4da11e30c/packages/flutter/lib/src/widgets/animated_cross_fade.dart#L371) this behavior can be easily enabled. Current widget clips everything with hardEdge with no way of changing the behavior without replacing/rewriting whole widget.
Repository: godot
Issue: Web export with gdextension not working on 4.3 if threads/nothreads variants are mismatched
Labels: enhancement,platform:web,documentation,topic:gdextension

### Tested versions

- Reproducible on 4.3.dev6 ~ 4.3.beta3
- Not Reproducible on 4.2.2 stable

### System information

Confirmed on MacOS and Windows

### Issue description

Web export with gdextension not working on 4.3 dev6 ~ 4.3.beta3.
Empty project with gdextension support flag on works well, but add a gdextention (I use [debug draw 3d](https://github.com/DmitriySalnikov/godot_debug_draw_3d), but my own gdextention not working too) addon to the project cause problem, and console says:
```
LinkError: WebAssembly.instantiate(): Import #62 "env" "memory": mismatch in shared state of memory, declared = 1, imported = 0
``` 
<img width="1685" alt="image" src="https://github.com/user-attachments/assets/e94eb5ea-313c-45d2-a956-f76e0a0280b3">


### Steps to reproduce

Download MRP, run in broswer.

### Minimal reproduction project (MRP)

[gdextention test.zip](https://github.com/user-attachments/files/16312163/gdextention.test.zip)
Repository: godot
Issue: AudioStreamInteractive: Pop and mistiming in seamless transitions
Labels: bug,topic:audio

### Tested versions

Reproduced in 4.3-beta3 and latest master [293c0f76463a4e1c2c2e86d8fbfc3e04f491b347]

### System information

Godot v4.3.beta3 - macOS 15.0.0 - Vulkan (Mobile) - integrated Apple M1 Max - Apple M1 Max (10 Threads)

### Issue description

Using AudioStreamInteractive, a transition from Clip End to Clip Start with fade disabled between audio files that match up seamlessly creates an audible pop, as well as a time discrepancy.

Here is a timeline with Godot’s audio output (top) alongside the expected concatenation of the original files (bottom):

![4 3-beta3](https://github.com/user-attachments/assets/21d6cbb5-295d-4730-bc8c-24807bd0be9f)

Note the odd waveform shape that occurs in Godot’s audio roughly between markers labeled 1 and 2, which creates a noticeable click sound.
Additionally, although the tracks are in sync prior to the transition (notice the corresponding peaks at marker 0), Godot’s audio drifts out of alignment after the transition (notice the bottom track’s peak at marker 3 corresponding to the top track’s peak at marker 4).

I was able to hack a correction for the time discrepancy by adding an (experimentally-determined) magic number to [line 721 in `modules/interactive_music/audio_stream_interactive.cpp`](https://github.com/godotengine/godot/blob/293c0f76463a4e1c2c2e86d8fbfc3e04f491b347/modules/interactive_music/audio_stream_interactive.cpp#L721):
```c++
src_fade_wait = end - current_pos + 0.01355;
```

This change yields the following:

![Time-adjusted](https://github.com/user-attachments/assets/c38ad3e5-db50-4d04-9132-b8085c7786d1)

The timing is now basically perfectly in sync with the reference track, but the click still occurs roughly between markers 1 and 2.

### Steps to reproduce

Run the MRP’s scene, which will autoplay the AudioStreamInteractive and automatically advance clips after ~20sec. Note the click that occurs during this transition.

### Minimal reproduction project (MRP)

### MRP
[Audio Testing.zip](https://github.com/user-attachments/files/16312134/Audio.Testing.zip)

### CYA
The attached audio is a copyrighted work included for demonstration purposes only. No license is provided for its usage beyond the scope of this issue.
Repository: next.js
Issue: with-next-translate example broken (html, body missing in layout; 404 pages)
Labels: examples

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
stackblitz
(but also local install via create-next-app)
```


### Which example does this report relate to?

with-next-translate

### What browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_

### Describe the Bug

When opened, says:
```
Missing required html tags
The following tags are missing in the Root Layout: <html>, <body>.
Read more at https://nextjs.org/docs/messages/missing-root-layout-tags
```

Even if the tags are added, the index page returns 404.
If manually navigated to `/en` as project seems to suggest, it's still 404
If manually navigated to `/en-US` it finally renders the page but without any translations, and all links inside lead to 404.

### Expected Behavior

works.

### To Reproduce

1. go to  https://github.com/vercel/next.js/tree/main/examples/with-next-translate
2. click Stackblitz
Repository: material-ui
Issue: [joy-ui][Select] Bug: Options visually selected after clicking the clear selections button in the Select component
Labels: on hold,component: select,package: joy-ui,support: docs-feedback

### Related page

https://mui.com/joy-ui/react-select/

### Kind of issue

Broken demo

### Issue description

There is a bug in JoyUI's Select component at [Clear Action](https://mui.com/joy-ui/react-select/#clear-action) example. When I use the clear selections button, the selected values ​​are removed as expected. However, when I open the options menu again, the previously chosen options still visually appear as selected.

**Steps to reproduce:**

1- Go to the Select component example page with the clear selections button.
2- Select some options in Select.
3- Click the button to clear selections.
4- Open the Select Options menu again.

**Expected behavior:**

Options that were previously selected should not visually appear as selected after clicking the clear selections button.

**Current behavior:**

Options that were previously selected still appear visually as selected after clicking the clear selections button, even though they are no longer selected.

### Context

While implementing a `Select all` option, I realized the effect was not being applied correctly after selecting all the options.

**Search keywords**: UI, visual bug, clear selection
Repository: next.js
Issue: Stale search parameters when using an anchor/fragment in the `as` property of `Link`
Labels: bug,Navigation,Pages Router

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/quirky-links-34d7yr

### To Reproduce

1. Visit the CodeSandox (the dev server starts automatically);
2. Follow the instructions.

### Current vs. Expected behavior

The reproduction shows the correct behaviour when the url does not contain an anchor part.
We would expect the same behaviour even when the anchor part is present.

### 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): 8198
  Available CPU cores: 4
Binaries:
  Node: 20.11.1
  npm: 10.2.4
  Yarn: 1.22.19
  pnpm: 8.15.4
Relevant Packages:
  next: 14.2.5 // Latest available version is detected (14.2.5).
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.4.5
Next.js Config:
  output: N/A
```


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

Navigation, Pages Router

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

next dev (local), next start (local), Other (Deployed)

### Additional context

We tested the issue on our version of Next.js (14.2.0) and in the very latest version (14.2.5).
Repository: godot
Issue: Version 3.6.rc1 freezing when try to export AAB. APK export works fine.
Labels: bug,platform:android,regression,topic:export

### Tested versions

- Reproducible: 3.6.rc1

### System information

Mac OS Sonoma 14.5

### Issue description

I am upgrading my project from 3.5.3 to 3.6.rc1, in order to export with Google API level 34 (required by Google until August 31st). Export from version 3.5.3 works fine, but after upgrading to version 3.6, download and install new models (even deleted Android folder at project root) and export new AAB file just freeze the application. 

Export to APK with or without debug works just fine.

Some screenshots are in Portuguese, because I am brazilian. Sorry about that.

<img width="581" alt="Captura de Tela 2024-07-19 às 15 21 19" src="https://github.com/user-attachments/assets/79e15ac3-e27c-4a6d-86cc-aa5650e6ae53">
<img width="722" alt="Captura de Tela 2024-07-19 às 15 21 55" src="https://github.com/user-attachments/assets/ca9c5851-69ac-4a4a-b6d1-5f7dff1f716f">
<img width="505" alt="Captura de Tela 2024-07-19 às 15 22 20" src="https://github.com/user-attachments/assets/77d1a435-4a1f-4ff1-a05b-da7883d90fe0">


### Steps to reproduce

- Downloaded version 3.6-rc
- replace old Godot app (v3.5.3)
- Update new models from internet
- Update custom templates from the model downloads
- Export to APK works fine
- Export to AAB don't work. No error, just freeze the application and I have to close it.

### Minimal reproduction project (MRP)

N/A
Repository: bitcoin
Issue: Logging controls
Labels: Brainstorming,Utils/log/libs

Categories in the logging system currently work as follows:

 * You can set a global log level (defaulting to `debug`), to `trace` to enable trace logs in all (enabled) categories (`-loglevel=trace`), or to `info` to disable debug logs even enabled categories (`-debug=all -loglevel=info` will still leave debugging disabled)
 * You can override the global log level on a per-category basis, either making it more verbose (override info to debug or trace, or override debug to trace), or to make it less verbose (override a global default of debug or trace to a category specific level of info or debug), eg `-loglevel=walletdb:trace -loglevel=net:info`
 * The log levels are only relevant for "enabled" categories (eg, you have to specify `-debug=walletdb -loglevel=walletdb:trace` to enable wallet db tracing)
 * Enabling/disabling categories can be done at startup via the `-debug` option, or at runtime via the `logging` RPC
 * Setting the log level is currently only possible at startup via the (currently hidden) `-loglevel` option

Is this behaviour worth preserving, or can we simplify it? I think it would be simpler and almost as powerful if we set things up as:

 * Every category has a log level, that can be either `info` (default), `debug`, or `trace` (trace gives you everything, debug gives you everything but `LogTrace()`, and info skips both `LogDebug()` and `LogTrace()`)
 * We add a new `-trace` config option that sets a category's log level to trace, analogously to `-debug` (so you would just specify `-trace=walletdb` for wallet db tracing.
 * We add an optional third argument to the `logging` rpc that accepts a list of categories to enable trace logging
 * We support `-debug=all` or `-trace=all` to do all categories at once, and `-debug=all -debugexclude=leveldb` as usual to set all categories to debug but one left at info, or `-trace=all -debug=walletdb` to trace all categories but one left at debug (which offer similar behaviour to `-debug=all -loglevel=debug -loglevel=leveldb:info` or `-debug=all -loglevel=trace -loglevel=walletdb:debug`)

(Looking for concept acks/feedback)
Repository: node
Issue: DNS Lookups Failing After Updating to Latest Node 20 and 18 for IBM i
Labels: dns,ibm i

### Version

v20.15.1

### Platform

```text
IBM i 7.3:

OS400 idev 3 7 00780002A1F1 powerpc Os
```


### Subsystem

DNS

### What steps will reproduce the bug?

Any DNS lookup fails with connection timeout. Can run this code to reproduce:

```js
require("dns").resolve("smtp.office365.com", function() { console.log(arguments); })
```

Fails with `ETIMEOUT`, even though the system DNS configuration is good and other software can perform DNS lookups.

### How often does it reproduce? Is there a required condition?

Every time. This started happening when updating to Node 20.15.1 and Node 18.20.4 for IBM i. Everything was working fine before the update. Before, I was using Node 20.11.1 and Node 18.18.2.

### What is the expected behavior? Why is that the expected behavior?

I expect a good DNS lookup, as the system DNS configuration is good and most other software can perform lookups.

### What do you see instead?

ETIMEOUT on any DNS lookup.

### Additional information

An interesting thing we noticed that may relate....

On the affected systems, the NSLOOKUP CL command can perform lookups with no problem, but the `nslookup` command in PASE fails with ETIMEOUT for any lookup.
Repository: PowerToys
Issue: Auto-Move Window to Next Available Zone in FancyZones
Labels: Idea-Enhancement,Product-FancyZones,Needs-Triage

### Description of the new feature / enhancement

There could be a toggle in the settings for this auto-move out of the way/force no-overlapping.

When moving a window (white one in the video) into a zone that is already occupied, the original window (black one) should be moved to the empty zone closest to the original zone.



### Scenario when this would be used?

Sometimes I want to move a window into a more ergonomic/central position, but without overlapping whatever was there, having to move that manually or alt+tab into it.

### Supporting information

Edited video simulating the feature: https://github.com/user-attachments/assets/11c35379-b443-4d85-b207-b9479bca9a71
Repository: pytorch
Issue: Missing float8 storage
Labels: triaged,module: float8

### 🚀 The feature, motivation and pitch

I'm trying to use float8 to try mistral nemo which was trained in a quantization aware way, to do inference in FP8.
Ref:
- https://mistral.ai/news/mistral-nemo/
- https://huggingface.co/mistralai/Mistral-Nemo-Base-2407#transformers

### Alternatives

_No response_

### Additional context

Environment:
- macOS 14.5
- Python 3.12.4
- pytorch 2.3.1
- transformers at 43ffb785c0b2f24948d2011883d40dccb609d341

Repo:

```
import torch                                                                    
import transformers
print(torch.__version__)                                                        
transformers.pipeline(                                                 
      "text-generation",                                                        
      model="mistralai/Mistral-Nemo-Instruct-2407",                             
      torch_dtype=torch.float8_e4m3fn)  
```

Failure:

```
2.3.1
Traceback (most recent call last):
  File ".../repro.py", line 3, in <module>
    transformers.pipeline(                                                 
    ^^^^^^^^^^^^^^^^^^^^^^
  File ".../venv/lib/python3.12/site-packages/transformers/pipelines/__init__.py", line 895, in pipeline
    framework, model = infer_framework_load_model(
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File ".../venv/lib/python3.12/site-packages/transformers/pipelines/base.py", line 283, in infer_framework_load_model
    model = model_class.from_pretrained(model, **kwargs)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File ".../venv/lib/python3.12/site-packages/transformers/models/auto/auto_factory.py", line 564, in from_pretrained
    return model_class.from_pretrained(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File ".../venv/lib/python3.12/site-packages/transformers/modeling_utils.py", line 3724, in from_pretrained
    dtype_orig = cls._set_default_torch_dtype(torch_dtype)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File ".../venv/lib/python3.12/site-packages/transformers/modeling_utils.py", line 1572, in _set_default_torch_dtype
    torch.set_default_dtype(dtype)
  File ".../venv/lib/python3.12/site-packages/torch/__init__.py", line 796, in set_default_dtype
    _C._set_default_dtype(d)
TypeError: couldn't find storage object Float8_e4m3fnStorage
```

When I try with float8_e5m2, the exception is Float8_e5m2Storage

cc @yanbing-j @vkuzo @albanD @kadeng @penguinwu