sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Have 1 log view with topic filters
Labels: feature-request,log

In my setup I am counting a total of 26 output channels, 12 of them are VS Code loggers and having them separate is a real headache

* it is nearly impossible to correlate events of different logs like renderer to main to EH
* I gave up on asking users to attach log files because there are too many


I understand that we often use dedicated log channels because from the owner's POV it's a nice grouping mechanism but it IMO it still defeats the purpose of having _a_ log file. Instead, I propose that all loggers write into the file but that they use a prefix on which the UI allows to filter. With that I can narrow down on one or more topics (like today but better) but also see the whole picture

<img width="1211" alt="Screenshot 2024-06-19 at 15 16 17" src="https://github.com/user-attachments/assets/9e730f64-4bbf-4d45-acf4-feaf21a11733">
Repository: go
Issue: proposal: x/tools/cmd/eg: support for generics
Labels: Proposal

### Proposal Details

It will be great is eg can support generics in a way it can handle e.g. slices of different types.

Example: Replacing a method that takes slices of elements that implements given interface.

```go
package template

import (
        "github.com/golang/protobuf/proto"
        "github.com/stackrox/rox/pkg/protoassert"
        "github.com/stretchr/testify/assert"
        "testing"
)

func before[T proto.Message](t *testing.T, a, b []T) bool {
        return assert.Equal(t, a, b)
}

func after[T proto.Message](t *testing.T, a, b []T) bool {
        return protoassert.SlicesEqual(t, a, b)
}
```
Repository: flutter
Issue: Add `primaryScroll` options on Navigator.
Labels: c: new feature,framework,f: routes,c: proposal,P3,team-framework,triaged-framework

### Use case

Currently, `Navigator` creates `PrimaryScrollController`, inherited widget. It makes sense because `Navigator` means new single page mostly. But how about we need nested navigation? For example, `TabBarView` or `IndexedStack`.

In this case, every `Navigator` inject `PrimaryScrollController` so it is so hard to access proper PrimaryScrollContoller with context. If you can’t to get root PrimaryScrollController in child (it means nested navigation), you need to bind GlobalKey or NavigatorKey on parents Navigator, get context from key then get PrimarySrcollController.

So it can be used when you need to implement nested Navigator or you don’t want to create PrimaryScrollController on Navigator.

### Proposal

As @moffatman mentioned, add `primaryScroll` (default to true) option on `Navigator`.

We need to fix https://github.com/flutter/flutter/blob/master/packages/flutter/lib/src/widgets/routes.dart#L1061

CC: @Piinks , @MitchellGoodwin
Repository: godot
Issue: Can not play animation in sub thread
Labels: needs testing,topic:animation

### Tested versions

v4.2.1.stable.mono.official [b09f793f5]

### System information

Godot v4.2.1.stable.mono - Windows 10.0.22631 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3080 Laptop GPU (NVIDIA; 31.0.15.5222) - AMD Ryzen 9 5900HX with Radeon Graphics (16 Threads)

### Issue description

E 0:00:01:0394   item_rect_changed: This function in this node (/root/Main/SubThread/Item/Sprite2D) can only be accessed from the main thread. Use call_deferred() instead.
  <C++ Error>    Condition "is_inside_tree() && !is_current_thread_safe_for_nodes()" is true.
  <C++ Source>   scene/main/canvas_item.cpp:531 @ item_rect_changed()


### Steps to reproduce

See MRP

### Minimal reproduction project (MRP)

[MultiThreadTest.zip](https://github.com/user-attachments/files/15901972/MultiThreadTest.zip)
Repository: next.js
Issue: Cannot find module 'tls'
Labels: examples

### 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 10 Pro
  Available memory (MB): 32712
  Available CPU cores: 8
Binaries:
  Node: 22.1.0
  npm: N/A
  Yarn: N/A
  pnpm: 9.1.1
Relevant Packages:
  next: 14.2.4 // Latest available version is detected (14.2.4).
  eslint-config-next: 14.1.0
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.4.5
Next.js Config:
  output: N/A
```


### Which example does this report relate to?

None

### What browser are you using? (if relevant)

Google Chrome Version 125.0.6422.176 (Official Build) (64-bit)

### How are you deploying your application? (if relevant)

Vercel

### Describe the Bug

I've installed PlayHT library with 'npm install --save playht' command and created an API route for testing purposes in "app/api/test/route.ts" file:
```
import {NextResponse} from "next/server";
import * as PlayHT from "playht";

async function handler(request: Request): Promise<NextResponse> {
    try {
        PlayHT.init({
            apiKey: "API_KEY",
            userId: "USER_ID",
        });
        return new NextResponse("SUCCESS", {status: 200}); // Return a success response.
    } catch (error) {
        return new NextResponse("INTERNAL SERVER ERROR", {status: 500}); // Return an error response.
    }
}

export const GET = handler;
```
Each time I send a request to the API endpoint, I get an error with the `Error: Cannot find module 'tls'` message. (I am aware that the code should not be executed on the client side as it requires Node.js modules.)

### Expected Behavior

I expect to receive a success response by getting the code executed on the server side without throwing any error.

### To Reproduce

To reproduce the error, you can simply execute 'npm install --save playht' in a (latest) NextJS project and create an API route with the following code (please note that you don't need to have API key and user ID in order to reproduce the error):
```
import {NextResponse} from "next/server";
import * as PlayHT from "playht";

async function handler(request: Request): Promise<NextResponse> {
    try {
        PlayHT.init({
            apiKey: "API_KEY",
            userId: "USER_ID",
        });
        return new NextResponse("SUCCESS", {status: 200}); // Return a success response.
    } catch (error) {
        return new NextResponse("INTERNAL SERVER ERROR", {status: 500}); // Return an error response.
    }
}

export const GET = handler;
```
Repository: PowerToys
Issue: Center-resize
Labels: Idea-New PowerToy,Needs-Triage

### Description of the new feature / enhancement

macos style resing window from both sides when holding a modifier key, ie holding shift and resizing keeps center of the window in the same spot

### Scenario when this would be used?

I often find myself resizing a windows and immediately moving it to where it was

### Supporting information

_No response_
Repository: godot
Issue: Can't edit CollisionShape3D with Half Resolution
Labels: bug,topic:editor,confirmed,topic:3d

### Tested versions

- Reproducible in 4.2.2 stable

### System information

Godot v4.2.2.stable - Linux Mint 21.3 (Virginia) - X11 - Vulkan (Forward+) - dedicated AMD Radeon RX 6600 (amdgpu; 6.3.6) - AMD Ryzen 5 3600 6-Core Processor (12 Threads)

### Issue description

When enabling Half Resolution in the perspective menu, I can't drag the boundaries of any collision shape. When disabling it, it works again. 

https://github.com/godotengine/godot/assets/121569485/83dc9cba-6885-4acd-8723-76d04e7b36f4



### Steps to reproduce

Add a collisionShape3D to the scene, activate Half Resolution in the perspective settings and try to grab those tiny round thingies.

### Minimal reproduction project (MRP)

[MRP(4.2.2).zip](https://github.com/user-attachments/files/15902794/MRP.4.2.2.zip)
Repository: next.js
Issue: Route interception doesn't work with two identical intercepted paths in different layouts/groups
Labels: bug,Navigation,Parallel & Intercepting Routes

### Link to the code that reproduces this issue

https://github.com/DominikMeca/nextjs-shared-route-interception-reproduction

### To Reproduce

1. Start the application and navigate to ``/test1` (root should redirect here)
2. Click the link/text on the page
3. Observe the navigation
4. (Optionally) Try `/test2`

### Current vs. Expected behavior

**Current behaviour:** 

The app navigates to the underlying modal page at `app/modal/page.jsx`.

**Expected behaviour:**

The app should intercept the navigation and append the modal content (just text in the repro) to the page. The intercepted route from the current layout should be selected.

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP Fri Mar 29 23:14:13 UTC 2024
  Available memory (MB): 26054
  Available CPU cores: 12
Binaries:
  Node: 18.19.0
  npm: 10.2.3
  Yarn: 1.22.21
  pnpm: 9.0.1
Relevant Packages:
  next: 14.2.4 // Latest available version is detected (14.2.4).
  eslint-config-next: 14.2.4
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.4.5
Next.js Config:
  output: N/A
```


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

Navigation, Parallel & Intercepting Routes

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

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

### Additional context

_No response_
Repository: next.js
Issue: ERR_SSL_WRONG_VERSION_NUMBER when doing fetch request in middleware to api route
Labels: bug

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/stupefied-visvesvaraya-64xkvr

### To Reproduce

use "next": "^14.2.4"
create pages/api handler
make request in middleware using await fetch(${req.nextUrl.origin}/api/${handlerName}

### Current vs. Expected behavior

Current behaviour:
fetch throws error when deployed:
{ library: 'SSL routines', reason: 'wrong version number', code: 'ERR_SSL_WRONG_VERSION_NUMBER' }

Expected behaviour:
fetch makes requests successfully (as it was in next@13.4.12)

NOTE: works locally, also works if we use await fetch('http:${req.nextUrl.host}/api/${handlerName}', but not sure if it is secure to switch to http protocol.



### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.3.0: Wed Dec 20 21:30:59 PST 2023; root:xnu-10002.81.5~7/RELEASE_ARM64_T6030
  Available memory (MB): 18432
  Available CPU cores: 11
Binaries:
  Node: 20.14.0
  npm: 10.7.0
  Yarn: 1.22.19
  pnpm: N/A
Relevant Packages:
  next: 14.2.4 // Latest available version is detected (14.2.4).
  eslint-config-next: 14.2.4
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.4.5
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Not sure

### Which stage(s) are affected? (Select all that apply)

Vercel (Deployed), Other (Deployed)

### Additional context

_No response_
Repository: godot
Issue: buggy editor preview on android 
Labels: bug,platform:android,topic:rendering,topic:editor,regression

### Tested versions

-Reproducible in: 4.3.0.beta1 , 4.3.beta3,4.3.dev4
-Not Reproducible in: 4.2

### System information

Android 11 - Godot V.4.3.0.beta1

### Issue description

when I add a shader to a spatial or 3D mesh the preview window sometimes become
buggy and unresponsive . I think it sometimes also mess up the script's preview tho it's uncommon and harder to replicate 

https://youtu.be/H3LpudcVXQY?si=HssNDh3pIDYJMkQO

### Steps to reproduce

just try to add a gdshader to a mesh and open and close the shader editor. I don't think this is the only way tho.
also I'm using compatibility renderer 

### Minimal reproduction project (MRP)

N\A
Repository: next.js
Issue: next build --no-mangling keeps mangling
Labels: bug,SWC

### Link to the code that reproduces this issue

https://github.com/inside/no-mangling-option

### To Reproduce

1. `npm install`
2. `npm run build -- --profile --no-mangling`
3. `npm start`
4. Open your browser to `http://localhost:3000`
5. Open the devtools
6. If installed, go to the React Developer Tools profiler tab
7. Click on "Reload and start profiling"
8. After a few seconds, click stop on the red circle

### Expected behavior versus Current

Following the previous section, a flamegraph with no mangled names should appear like shown in the screenshot below:

![image](https://github.com/inside/no-mangling-option/assets/107884/ed372007-9a13-4327-8377-12b05f1efc2f)

Instead a flamegraph with mangled names appears like shown in the screenshot below:

![image](https://github.com/inside/no-mangling-option/assets/107884/0233417f-875e-43f9-b7aa-546adb847ae5)

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #35~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue May  7 09:00:52 UTC 2
  Available memory (MB): 15747
  Available CPU cores: 8
Binaries:
  Node: 20.12.1
  npm: 10.5.1
  Yarn: 1.22.21
  pnpm: 7.11.0
Relevant Packages:
  next: 15.0.0-canary.37 // Latest available version is detected (15.0.0-canary.37).
  eslint-config-next: N/A
  react: 19.0.0-rc.0
  react-dom: 19.0.0-rc.0
  typescript: N/A
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

SWC

### Which stage(s) are affected? (Select all that apply)

next build (local)

### Additional context

_No response_
Repository: transformers
Issue: will this be a model or just a tokenizer/embeddings ? technically a sentence trancformer ?
Labels: Feature request

### Feature request

for the text component : will this config be abe to take a languge model as a pretrained config ? 

ie when creating a vision/text decoder model you can specify the tet model component ( ie the mistral model ) ? 
as the mistral is a decoder only model .... maybe it would need corss attention to connect ?
will the text componant be able to be used with the standard AutoModelForCausalLM ? <<< If so it would be prudent to be able to intialize a model with the pretrained components ... ie a lnaguge model and a whisper and a clip model and a xclip ? or to the effect of ... enableing for the genration of modelif these (bodys) ... ie collection of tensors whcih can be read by the imagebind library  transfromer... instead of a simple tokenizer .... it would then be able to utilize the tokenizer from the llm or combine the tokenizers into a single model by adding the speicla tokens to the languge model base ? 

in truth this would enable the generation of even larger models and give the pretrained model a chance to find thier homes in the new body of a (imagebind) as it is the wrapper which makes the model ...(hence perhaps also including a feature to execute code on the fly and return the executing back to the model directly if enabled or ok byu the user...as this is the method as the model could generate its on code to execute in opython and return the result to the transformer to be utilized in the response it is generating .... so if the model is given functions as an input (it would also be able to run them in the back ground pre retuning the response) ... also given code by the user in chat it should be able to run the code in ipython behind the scenes and return the response (not on the system directoy(hence havign hiddon ipython repl) ..(it would still have to make the calls)

### Motivation

rags internally ! 
usablity ! of the model wrapper to understand that each component could be trained seperate or even within the model itself !

as well as fitting with anything in and wnything out principle (media wise) (code as an input (function)) 

### Your contribution

i really would like to see this project get forwards as its the same thing i was working towards but i have fiath you will succeed ... if not i will stillc arry on my path !
Repository: rust
Issue: Tracking Issue for `array::repeat`
Labels: T-libs-api,C-tracking-issue,F-array_repeat

<!--
Thank you for creating a tracking issue!

Tracking issues are for tracking a feature from implementation to stabilization.

Make sure to include the relevant RFC for the feature if it has one.

If the new feature is small, it may be fine to skip the RFC process. In that
case, you can use `issue = "none"` in your initial implementation PR. The
reviewer will ask you to open a tracking issue if they agree your feature can be
added without an RFC.
-->

Feature gate: `#![feature(array_repeat)]`

This is a tracking issue for `array::repeat`, a function for creating array filled with a single `Clone`able value.

### Public API

```rust
// core::array

pub fn repeat<T: Clone, const N: usize>(v: T) -> [T; N];
```

### Steps / History

<!--
For larger features, more steps might be involved.
If the feature is changed later, please add those PRs here as well.
-->

- [x] ACP: https://github.com/rust-lang/libs-team/issues/310
- [x] Implementation: #119127 
- [ ] Final comment period (FCP)[^1]
- [ ] Stabilization PR

<!--
Once the feature has gone through a few release cycles and there are no
unresolved questions left, the feature might be ready for stabilization.

If this feature didn't go through the RFC process, a final comment period
(FCP) is always needed before stabilization. This works as follows:

A library API team member can kick off the stabilization process, at which point
the rfcbot will ask all the team members to verify they agree with
stabilization. Once enough members agree and there are no concerns, the final
comment period begins: this issue will be marked as such and will be listed
in the next This Week in Rust newsletter. If no blocking concerns are raised in
that period of 10 days, a stabilization PR can be opened by anyone.
-->

### Unresolved Questions

<!--
Include any open questions that need to be answered before the feature can be
stabilised. If multiple (unrelated) big questions come up, it can be a good idea
to open a separate issue for each, to make it easier to keep track of the
discussions.

It's useful to link any relevant discussions and conclusions (whether on GitHub,
Zulip, or the internals forum) here.
-->

- None yet.

[^1]: https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html
Repository: TypeScript
Issue: Convert params to destructed object: Cannot apply refactoring 
Labels: Bug,Fix Available

Repro:

1. Go to buffer.ts
2. Put cursor in `static wrap`
3. ctrl+.
4. Select convert params code action

![Recording 2024-06-19 at 06 48 54](https://github.com/user-attachments/assets/aa0d4b74-966d-42cc-8629-ef968ce6e5c1)
Repository: godot
Issue: In the GDScript, adding an Animation with LoopMode set to LOOP_PINGPONG does not produce the expected effect.
Labels: bug,topic:animation

### Tested versions

v4.3.beta1.official [a4f2ea91a]

### System information

Godot v4.3.beta1 - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3060 Ti (NVIDIA; 32.0.15.5585) - AMD Ryzen 5 3600 6-Core Processor (12 Threads)

### Issue description

I tried to add an Animation to the AnimationPlayer in the code, hoping it would achieve the exact same effect as the “stand” animation added to AnimationPlayer2 in the editor. However, when I set the LoopMode to PINGPONG, an issue arose where the offset of the third frame of the animation was abnormal and did not match that of AnimationPlayer2.

### Steps to reproduce

the code in my mimimal reproduction project.

### Minimal reproduction project (MRP)

[bugreport.zip](https://github.com/user-attachments/files/15903754/bugreport.zip)
This is my minimal reproduction project,thanks.
Repository: node
Issue: `net` socket does not behave according to stream documentation after close
Labels: stream

### Version

v18.20.2

### Platform

Linux desktop-home 6.6.33 #1-NixOS SMP PREEMPT_DYNAMIC Wed Jun 12 09:13:03 UTC 2024 x86_64 GNU/Linux

### Subsystem

net

### What steps will reproduce the bug?

```js
"use strict";

const net = require("net");

let server = net.createServer((socket) => {
	socket.on("close", () => {
		console.log("socket fully closed");
	});

	let success = socket.write("test");
	console.log({ success }); // { success: true }

	setTimeout(() => {
		// This *should* throw an error, according to streams documentation
		let success = socket.write("test");
		console.log({ success }); // instead, it logs { success: false }
	}, 2000);
});

server.listen(4891);

let client = net.connect(4891, () => {
	client.end();
});

client.on("data", (data) => {
	console.log("recv:", data);
});

/* Full output:
{ success: true }
recv: <Buffer 74 65 73 74>
socket fully closed
{ success: false }
*/
```

### How often does it reproduce? Is there a required condition?

Consistently happens.

### What is the expected behavior? Why is that the expected behavior?

After a socket has been closed by the other side, attempting to write to it *should* result in a write error; a `net.Socket` is a `stream.Writable`, which says the following in [the documentation](https://nodejs.org/docs/latest/api/stream.html#writableendchunk-encoding-callback):

> Calling the [stream.write()](https://nodejs.org/docs/latest/api/stream.html#writablewritechunk-encoding-callback) method after calling [stream.end()](https://nodejs.org/docs/latest/api/stream.html#writableendchunk-encoding-callback) will raise an error.

Although in the most literal interpretation this only specifies that an error would occur if `end` was called on the *same* side that you are attempting to write from, it is surprising behaviour that this is different when the socket is closed from the *other* side, because the writable stream has still ended all the same (and the above reduced testcase demonstrates this by logging the 'socket fully closed' event).

### What do you see instead?

Instead, the write-while-closed merely returns `false` as if the internal buffer has temporarily filled up, but then never actually emits a `drain` event (presumably because there is no socket to drain *to* anymore).

### Additional information

I worked this out after several hours of debugging, and I was unable to find any reference to this behaviour in the documentation; in my case, it created a difficult-to-debug silent failure, as my code was waiting for the `drain` signal to continue writing data, but never received it.
Repository: deno
Issue: an attempted import of Node's built-in "zlib" module is being interpreted as being for a "zlib" NPM module
Labels: bug,node compat

Attempting to import `npm:contentful-management` produces the following error (the same as denoland/deno_ast#227, but per https://github.com/denoland/deno_ast/issues/227#issuecomment-2179031517 it's a different underlying issue):

```
> deno
Deno 1.44.2
exit using ctrl+d, ctrl+c, or close()
REPL is running with all permissions allowed.
To specify permissions, run `deno repl` with allow flags.
> import "npm:contentful-management"
Uncaught TypeError: Could not find npm package 'zlib' referenced by 'contentful-management@11.27.3'.
    at async <anonymous>:1:22
>
```

It seems like it might be interpreting a locally-ambiguous import of `zlib` that should be resolved as the built-in node module (`node:zlib`) instead as if it's an import for an NPM module of the same name (`npm:zlib`), but from a quick look I wasn't able to identify where the problematic import is actually happening.
Repository: PowerToys
Issue: Peek crashes on Windows 24H2 with Surface Laptop 7th Edition
Labels: Issue-Bug,Needs-Triage,Needs-Team-Response

### Microsoft PowerToys version

0.81.1

### Installation method

Microsoft Store

### Running as admin

No

### Area(s) with issue?

Peek

### Steps to reproduce

Peek crashes when attempting to preview at least pdf and mp4 files on the release version of Windows 24H2 (Build 26100.863) on a brand new Surface Laptop 7th Edition. So far I have not gotten Peek to work at all. Peek does work to preview the same files on an ARM64 Lenovo X13s (also v0.81.1, Windows build 22631.3737), so this may be a 24H2 regression. 

### ✔️ Expected Behavior

Peek to open a preview of the file. 

### ❌ Actual Behavior

The PowerToys app silently crashes. 

### Other Software

_No response_