sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Allow setting Telemetry Output Logs to Trace always and independently
Labels: feature-request


Type: <b>Feature Request</b>

I'd like to set `Telemetry` and `Extension Telemetry` to log level trace so they are always visible for me, but I don't want to have all of VS Code set to trace all the time. The quick pick for managing these log levels doesn't include them at present.

VS Code version: Code - Insiders 1.93.0-insider (d1388fd24fc0acf17ae1f759e85c1acf559ed759, 2024-08-28T05:14:36.262Z)
OS version: Windows_NT x64 10.0.22631
Modes:


<!-- generated by issue reporter -->
Repository: godot
Issue: `get_child` error when duplicating .GLB model nodes with animations
Labels: bug,regression,topic:animation

### Tested versions

reproducible in 4.3 stable 
not reproducible in 4.2 stable
not tested in other builds

### System information

Godot v4.3.stable - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1070 (NVIDIA; 31.0.15.5161) - Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz (8 Threads)

### Issue description

when attempting to duplicate() a  GLB node with animations under its animation player it is unable to understand the children and produces this error 

```
E 0:00:00:0862   node_3d.gd:5 @ _ready(): Index p_index = 1 is out of bounds ((int)data.children_cache.size() = 1).
  <C++ Source>   scene/main/node.cpp:1688 @ get_child()
  <Stack Trace>  node_3d.gd:5 @ _ready()
```

that also causes the next error in the debugger

```
E 0:00:00:0863   node_3d.gd:5 @ _ready(): Child node disappeared while duplicating.
  <C++ Error>    Parameter "copy_child" is null.
  <C++ Source>   scene/main/node.cpp:2926 @ _duplicate_properties()
  <Stack Trace>  node_3d.gd:5 @ _ready()
```


### Steps to reproduce

import a .GLB model with a animation into a scene and call the duplicate function on it

### Minimal reproduction project (MRP)

[glb-duplicate-test.zip](https://github.com/user-attachments/files/16789050/glb-duplicate-test.zip)
Repository: go
Issue: time: TestParseYday failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "time" && test == "TestParseYday"
```

Issue created automatically to collect these failures.

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

    === RUN   TestParseYday
    === PAUSE TestParseYday


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: godot
Issue: Playing multiple AudioStreams together causes alterations of pitch or volume
Labels: bug,needs testing,topic:audio

### Tested versions

- Reproducible in v4.3.stable.mono.official [77dcf97d8]
- Reproducible in v4.2.1.stable.mono.official [b09f793f5]

### System information

Godot v4.3.stable.mono - Windows 10.0.22631 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 2080 Super with Max-Q Design (NVIDIA; 32.0.15.6081) - Intel(R) Core(TM) i7-10875H CPU @ 2.30GHz (16 Threads)

### Issue description

This audio bug is hard to spot. When multiple AudioStreamPlayers play different AudioStreams, the pitch or volume of certain frequencies of the AudioStream get altered. 
I've provided a video below to show the issue better.

https://github.com/user-attachments/assets/11866800-dc11-4011-97f2-3ee54e52349f

In the video, a brownian noise is played constantly, with no major change in pitch or volume. When a pluck sound effect is played, however, you can hear the pitch of the brownian noise get very slightly altered. I suspect this happens to the audio frequencies shared by both sound effects, as it is easier to spot this bug if two AudioStreams have a very similar pitch range.

### Steps to reproduce

1. Start with a scene of your liking
2. Add two AudioStreamPlayers
3. Add two AudioStreams to the Players. (I recommend using a constant audio sample and a short sound effect, like a pluck)
4. Play the AudioStreamPlayers, and make sure both AudioStreams are audible at the same time
5. Try to spot the alteration in audio/volume

### Minimal reproduction project (MRP)

[audio-pitch-issue.zip](https://github.com/user-attachments/files/16789278/audio-pitch-issue.zip)

This is the same project I've used in the video. To replicate the issue, simply set the "playing" property of the first AudioStreamPlayer to True, and then do the same to the second one. The bug happens both in editor and in the running application.
Repository: vscode
Issue: Typing to reveal hidden notebook cell sometimes scrolls after reval
Labels: bug,notebook-layout


Type: <b>Bug</b>

From #163943

Potentially related to inertial scrolling on a trackpad. Tested on MacBook Pro trackpad

1. Create long notebook with multiple cells
1. Start editing in first cell
1. Scroll cell off screen
1. Type to make an edit

**Bug**
Sometimes when the cell is revealed, the entire notebook editor also scrolls down afterwards

https://github.com/user-attachments/assets/3a5fb7b3-44e8-466e-8352-5c68d54edf9e


VS Code version: Code - Insiders 1.93.0-insider (Universal) (d1388fd24fc0acf17ae1f759e85c1acf559ed759, 2024-08-28T05:14:36.262Z)
OS version: Darwin arm64 23.6.0
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Apple M2 Max (12 x 2400)|
|GPU Status|2d_canvas: unavailable_software<br>canvas_oop_rasterization: disabled_off<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: disabled_software<br>multiple_raster_threads: enabled_on<br>opengl: disabled_off<br>rasterization: disabled_software<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: disabled_software<br>video_encode: disabled_software<br>webgl: unavailable_software<br>webgl2: unavailable_software<br>webgpu: unavailable_software<br>webnn: disabled_off|
|Load (avg)|3, 3, 3|
|Memory (System)|64.00GB (0.19GB free)|
|Process Argv|--crash-reporter-id 0fffb5da-9cd7-46fd-9e7f-a1564e8c5fda|
|Screen Reader|no|
|VM|0%|
</details>
<!-- generated by issue reporter -->
Repository: rust
Issue: rustdoc search: allow type-based search for constants and statics
Labels: T-rustdoc,C-feature-request,A-rustdoc-search

Currently it is possible to search for function items based on their signature, but it is *not* possible to search for other kinds of items based on their type.

@rustbot label A-rustdoc-search
Repository: rust
Issue: Tracking Issue for fmt-debug option
Labels: T-compiler,C-tracking-issue,F-fmt_debug,-Zfmt-debug

This is a tracking issue for the `-Z fmt-debug` option

The feature gate for the option is `#![feature(fmt_debug)]`

### About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however *not* meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
Discussion comments will get marked as off-topic or deleted.
Repeated discussions on the tracking issue may lead to the tracking issue getting locked.

### Steps

- [x] Implement the proposal (https://github.com/rust-lang/rust/pull/123940)
- [ ] Adjust (stable user-facing) documentation ([see instructions on rustc-dev-guide][doc-guide])
- [ ] Stabilization PR ([see instructions on rustc-dev-guide][stabilization-guide])

[stabilization-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#stabilization-pr
[doc-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#documentation-prs
[Style Guide]: https://github.com/rust-lang/rust/tree/master/src/doc/style-guide

### Unresolved Questions
<!--
Include any open questions that need to be answered before the feature can be
stabilised.
-->

### Implementation history

* https://github.com/rust-lang/rust/pull/123940
Repository: go
Issue: x/tools/gopls: add a source action to see assembly for a range of lines
Labels: FeatureRequest,gopls,Tools

**Is your feature request related to a problem? Please describe.**
I wanted to understand why this allocates:
```go
func normalize(v any) (any, typeCode, bool) {
	switch v := v.(type) {
	case string:
		return v, typeCodeString, true
	// ...
	}
}
```

**Describe the solution you'd like**
I'd like to be able to select a line and view the assembly for that line (or for a range of lines).

**Describe alternatives you've considered**
I can (and did) use "Browse amd64 assembly for normalize" but that doesn't scale well to larger functions.

**Additional context**
https://github.com/golang/go/issues/67478
Repository: rust
Issue: Very long compilation time on Apple Silicon platform
Labels: A-LLVM,O-macos,I-compiletime,O-AArch64

I have a crate with about 2k files and 600kloc. Most of the code is autogenerated. It compiles in less than 2 minutes with release profile on Ryzen 7950X3D 96GB Linux and 40+ minutes on M1Max 64GB MacOS.

According to `-Ztime-passes` the majority of the time is spent in `finish_ongoing_codegen`. I can't share the original code, it uses a lot of private deps, but the link to the repro case is below.

Reproduces with rustc 1.78, 1.80, 1.81-nightly, 1.82-nightly.

The code in the repo takes 40+ minutes to compile on Apple Silicon (M1 and M3 tested)
On Linux (quite powerful box, 7950X3D, 96GB RAM) it takes 2 minutes.
This is a distilled down version of the original code, the original is autogenerated from a DSL and thus has such weird structure.

Originally it's a HTTP API service with A LOT of endpoints (621 specifically).


The python script recreates the `bug.rs` module and could be used to play with the number of "endpoints". It basically looks like that:
![image](https://github.com/user-attachments/assets/17b8b02f-a7dc-4afd-852f-83cf05260c2a)
X axis: number of "endpoints"
Y axis: seconds to compile.

If the fields in the struct could be made non-optional the problem goes away.

Chat discussion:  https://rust-lang.zulipchat.com/#narrow/stream/247081-t-compiler.2Fperformance/topic/Major.20slowdown.20on.20aarch64-apple-darwin

Repro case: https://github.com/kika/rust-apple-silicon-bug
Repository: vscode
Issue: Infinite loading when filesystem has no registered provider
Labels: bug,search,search-api

1. Debug the filesystem provider API
2. Try to do a search using the file picker
3. Notice that it infinitely loads because there is no file search provider :bug:
Repository: terminal
Issue: ConPTY inside WSL is broken (e.g. running cmd.exe inside WSL)
Labels: Product-Conpty,Area-Input,Issue-Bug,Priority-3

### Windows Terminal version

1.23.2391.0

### Windows build number

_No response_

### Other Software

_No response_

### Steps to reproduce

Run cmd.exe inside WSL.

### Expected Behavior

_No response_

### Actual Behavior

* W32IM never gets turned off.
  --> We must emit the corresponding mode resets before exiting VtIo.
* Launching the win32 process freezes for 3s as it waits for the DA1 response which gets mangled. Almost certainly the same issue as #17813.
Repository: next.js
Issue: next build hangs after next dev has compiled on Windows
Labels: bug

### Link to the code that reproduces this issue

https://github.com/jazelly/next-hang

### To Reproduce

1. `create-next-app`
2. `yarn dev` in one terminal
3. visit it to let it compile
4. `yarn build` in a different terminal
5. You might see an error, try again then you will see it hangs

### Current vs. Expected behavior

**Expect:**

I expect it to pass/fail consistently

**Actual:**

It hangs at

PS E:\github\my\next-bug\next-dead-lock> npx yarn build
npm info using npm@10.8.2
npm info using node@v22.5.1
npm http fetch GET 200 https://registry.npmjs.org/yarn 136ms (cache revalidated)
yarn run v1.22.22
$ next build
  ▲ Next.js 14.2.7

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Home
Binaries:
  Node: 22.5.1
  npm: 10.8.2
  Yarn: 1.22.22
  pnpm: N/A
Relevant Packages:
  next: 14.2.5
  eslint-config-next: 14.2.5
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.5.4
Next.js Config:
  output: N/A
```


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

Developer Experience

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

next build (local)

### Additional context

_No response_
Repository: rust
Issue: rustdoc search: path matches that skip segments should be deprioritized
Labels: T-rustdoc,C-enhancement,A-rustdoc-search

a search for `collections::b` matches `std::collections::LinkedList::back` far before it matches `std::collections::BTreeMap`.

ommitting segments at the start and end should not be penalized, but ommitting them in the *middle* should be.
Repository: go
Issue: proposal: slices: ChunkFunc to determine chunks of a slice using a function
Labels: Proposal

### Proposal Details

I propose adding a new function to the `slices` package that would return an iterator yielding variable-length subslices of a given slice based on a provided function. There are two possible implementations of this.

Version 1
-------------

The first is something I have personally used several times before, as well as being similar to [a function in the Elixir standard library](https://hexdocs.pm/elixir/Enum.html#chunk_by/2), looks like

```go
func ChunkFunc[T any, C comparable, S ~[]T](s S, chunker func(T) C) iter.Seq[[]T]
```

This function returns an iterator that yields subslices of `s` composed of consecutive runs of elements for which `chunker` returns the same value. In other words,

```go
ChunkFunc([]int{-1, -2, -3, 1, 2, -1, 3, 2, 1}, func(v int) bool { return v > 0 })
```

would yield `[]int{-1, -2, -3}`, `[]int{1, 2}`, `[]int{-1}`, and then `[]int{3, 2, 1}`. This is useful for a number of different things. For example, let's say that you have a slice of lines of output from something, some of which are to stdout and some to stderr. If you want to output those with a header to indicate which is which, being able to group the consecutive runs of lines that were to each is very useful, and a function like this can do it quite efficiently.

```go
groups := slices.ChunkFunc(outputs, func(output Output) string { return output.Destination })
for group := range groups {
  fmt.Printf("%v:\n", group[0].Destination) // Like Chunk(), never yields an empty slice.
  for _, output := range group {
    fmt.Println(output.Text)
  }
}
```

Version 2
--------------

The other possible implementation is to simply make the function always return a `bool`, and then define that each time it returns `true` is the start of a new chunk.

While this is not a function that I've personally had a use for, I'm not really stuck on either specifically simply because I'm pretty sure that both can be implemented using the other. I think it's probably easier to implement the `comparable` one using the `bool` version, though, as it would simply be something like the following untested function:

```go
func ChunkBy[T any, C comparable, S ~[]S](s S, chunker func(T) C) iter.Seq[[]T] {
  return func(yield func([]T) bool) {
    first := true
    var prev C
    chunks := ChunkFunc(s, func(v T) bool {
      check := chunker(v)
      if first {
        prev = check
        return true
      }
      start := check != prev
      prev = check
      return start
    })
    chunks(yield)
  }
}
```

Version 3
-------------

Another alternative is to simply provide both as, say, `ChunkFunc()` for the `bool` version and `ChunkBy()` for the `comparable` one.
Repository: vscode
Issue: Updater running then got an error
Labels: info-needed,install-update,windows

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
- VS Code Version: 1.92.1
- OS Version: 10.0.22631 Build 22631

Steps to Reproduce:

1. Check for Update
2. Restart for Update

<img width="860" alt="Screenshot 2024-08-29 at 09 27 46" src="https://github.com/user-attachments/assets/e8113de2-b8fc-4741-8aa0-c40866a31469">

Log snippet:
Aug 28 01:31:35.512 INFO Get file handle: "C:\\Users\\***\\AppData\\Local\\Programs\\Microsoft VS Code\\debug.log" (attempt 14)
Aug 28 01:31:45.313 INFO Get file handle: "C:\\Users\\***\\AppData\\Local\\Programs\\Microsoft VS Code\\debug.log" (attempt 15)
Aug 28 01:31:56.564 INFO Get file handle: "C:\\Users\\***\\AppData\\Local\\Programs\\Microsoft VS Code\\debug.log" (attempt 16)
Aug 29 01:16:42.908 ERRO Failed to create file handle: The process cannot access the file because it is being used by another process.
Repository: go
Issue: runtime: binaries should fail at startup when built with a GOARM64 version not supported on the runtime hardware
Labels: NeedsFix,arch-arm64,compiler/runtime,FixPending

### Go version

go version go1.23.0 linux/arm64

### Output of `go env` in your module/workspace:

```shell
Not relevant
```

### What did you do?

On an arm64 host, I ran

    GOARM64=v9.5 go test

on a simple hello world test.

### What did you see happen?

The test ran and passed.

### What did you expect to see?

This is on an AWS c7g instance. This is a graviton3 chip. I'm not 100% sure what the exact arm64 architecture version of that chip is (anyone know a good way to tell?), but I'm pretty sure it's v8.x. Someone on Hacker News claims that graviton3 is v8.4. In `/proc/cpuinfo` I see

```
processor       : 0
BogoMIPS        : 2100.00
Features        : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm jscvt fcma lrcpc dcpop sha3 sm3 sm4 asimddp sha512 sve asimdfhm dit uscat ilrcpc flagm ssbs paca pacg dcpodp svei8mm svebf16 i8mm bf16 dgh rng
CPU implementer : 0x41
CPU architecture: 8
CPU variant     : 0x1
CPU part        : 0xd40
CPU revision    : 1
```

Anyway, I'm pretty sure that it does not support arm64 v9.5. Yet, the binary I compiled with GOARM64=v9.5 does not check for CPU capabilities and exit on startup.

By contrast, on my local machine (AMD Ryzen 9 3900X) if I run

```
$ GOAMD64=v4 go test
This program can only be run on AMD64 processors with v4 microarchitecture support.
exit status 1
```

because my chip only supports GOAMD64=v3.

From the [CL 559555](https://go.dev/cl/559555) it sounds like GOARM64 support isn't being used in the compiler to do anything yet. However, it's still important that we fix this, because the `arm64.vX.Y` build tags are available to user code. I am able to write code today using (for example) the `arm64.v9.3` build tag to guard some v9.3-specific feature; when I run this binary on a v8.0 CPU it won't crash on startup but will hit some invalid instruction later.

P.S. It would be good if someone would update some of the wiki pages for GOARM64; in particular, [MinimumRequirements](https://go.dev/wiki/MinimumRequirements#amd64) and [GoArm](https://go.dev/wiki/GoArm). I found it a little hard to get info about GOARM64; as far as I can tell, besides the Go 1.23 release notes, the only places it's mentioned are `go help environment` and `go help buildconstraint`.

/cc @andreybokhanko @cherrymui
Repository: next.js
Issue: How to update current route data by using revalidateTag in the server action??
Labels: create-next-app,bug

### Link to the code that reproduces this issue

https://github.com/takakikasuga/revalidate-app

### To Reproduce

Now, I study app router and the next cahce like data cache and so on...
I try to do some option of fetch and revalidate tag and path.
today, I use [revalidateTag](https://nextjs.org/docs/app/api-reference/functions/revalidateTag) in the server action, and I wanna update data of the tag and I don't expect to update data other than tag.

In this below video, I updated `layout tag` in the ActionLayout, but after revalidate `layout tag`, other tag data like `page tag` in the ActionPage and `root tag` int the RootLayout  was updated.
I don't know this action happend...

additionally, after updated data related to all tags and reload the browser, `layout tag` was updated correctly but, other than tag like `page tag` and `root tag` wasn't updated and display old cached data...


https://github.com/user-attachments/assets/357a2961-82d1-4e79-913e-c1d6193a1043








How can I update current data by revalidateTag???👀



but,,, there is one thing, I succeeded in the specified tag's data.

I inject [redirect function](https://nextjs.org/docs/app/building-your-application/routing/redirecting#redirect-function) after revalidate tag and redirect to current route, I can found the my expectation that `layout tag` was updated and other than tag like `page tag` and `root tag` wasn't updated like below the video.
but I don't know this implementation is correct because this implementation example don't be writtern in the nextjs official document.
（I refered to the this [youtube](https://www.youtube.com/watch?v=-mPm2IRkacM)）


https://github.com/user-attachments/assets/142c9c49-284e-4c42-92cb-b57dae325743




I love the nextjs, thank you for your project and the best effort for software enginner!!

### Current vs. Expected behavior

 I wanna update data of the tag and I don't expect to update data other than tag by using only revalidateTag, it means I don't use redirect.

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: x64
  Version: Darwin Kernel Version 23.5.0: Wed May  1 20:12:58 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T6000
  Available memory (MB): 65536
  Available CPU cores: 10
Binaries:
  Node: 20.14.0
  npm: 10.7.0
  Yarn: 1.22.22
  pnpm: N/A
Relevant Packages:
  next: 14.2.7 // Latest available version is detected (14.2.7).
  eslint-config-next: 14.2.7
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.5.4
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

create-next-app

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

_No response_
Repository: rust
Issue: Large amounts of repeated data in debug info
Labels: A-LLVM,A-debuginfo,T-compiler,C-bug,C-tracking-issue,I-heavy

In https://github.com/rust-lang/rust/pull/128861#issuecomment-2292401581 I teased @nnethercote with the promise of more debug info inefficiency. One example is that the .debug_ranges section that specifies the ranges over which DWARF constructs such as functions, variables, etc are valid contains large amounts of repeated data. Rust's love of inlining and zero cost abstractions tends to produce repeated ranges.

When built with debuginfo-level = 2, tip Rust's librustc_driver.so has approximately 2.1 million entries in .debug_ranges. There are only  approximately 1.1 million unique entries though. Doing the dumbest possible thing in LLVM (checking in DwarfFile::add_range to see if the new range is exactly equal to the last range, and not adding a new entry if it is) eliminates virtually all duplicated ranges (less than 1k remain) and results in a 43% reduction in the size of the .debug_ranges section, or a roughly 1.75% reduction in the size of the .so

@rustbot label A-debuginfo A-llvm I-heavy
Repository: transformers
Issue: Is it possible to infer the model separately through encoder.onnx and decoder.onnx
Labels: Feature request

### Feature request

Is it possible to infer the model separately through encoder.onnx and decoder.onnx

### Motivation

Is it possible to infer the model separately through encoder.onnx and decoder.onnx

### Your contribution

Is it possible to infer the model separately through encoder.onnx and decoder.onnx