sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: crypto/x509: certificate with empty Authority Key Identifier extension considered invalid
Labels: NeedsInvestigation

### Go version

go version go1.18.1 linux/amd64

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

```shell
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/liu/.cache/go-build"
GOENV="/home/liu/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/liu/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/liu/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/lib/go-1.18"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go-1.18/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.18.1"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/dev/null"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build3649475886=/tmp/go-build -gno-record-gcc-switches"
```


### What did you do?

I used crypto/x509 of golang to convert the der certificate to a pem certificate. For my test case, there was an Authority Key Identifier extension with an empty value. 


### What did you see happen?

Golang considered it an invalid Authority Key Identifier extension, but openssl and gnutls did not.

### What did you expect to see?

According to rfc5280, the keyIdentifier, authorityCertIssuer, and authorityCertSerialNumber of the Authority Key Identifier extension are all OPTIONAL
Repository: next.js
Issue: Bug: Mangling of Constants Causing Runtime Errors in GraphQL-based Packages with Turbopack
Labels: bug,Turbopack,linear: turbopack

### Link to the code that reproduces this issue

https://github.com/0no-co/graphql.web/pull/43

### To Reproduce

1. Install and configure Next.js 15 with Turbopack and a GraphQL-based package (e.g., `gql.tada`).
2. Start the application using Turbopack in development mode.
3. Encounter runtime errors where exported constants (e.g., `Kind`) are incorrectly referenced (e.g., as `e` instead of `e1`).

### Current vs. Expected behavior

**Current behavior**: Some exported constants in `graphql.web`, such as `Kind` as `e`, are incorrectly referenced during the bundling process in Turbopack, leading to references like `e` instead of the intended `e1`. This causes runtime errors because the application expects the correct constant name (e.g., `e1` for `Kind`), but Turbopack provides an incorrect reference.

**Expected behavior**: The exported constants should be preserved with their correct names during bundling. For example, `Kind` should not be mangled to `e` or any other incorrect name, and it should maintain its correct reference throughout the build and runtime.


Example Code:
https://github.com/0no-co/graphql.web/pull/43

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.1.0: Thu Oct 10 21:02:45 PDT 2024; root:xnu-11215.41.3~2/RELEASE_ARM64_T8112
  Available memory (MB): 16384
  Available CPU cores: 8
Binaries:
  Node: 20.5.0
  npm: 9.8.0
  Yarn: N/A
  pnpm: 9.7.1
Relevant Packages:
  next: 15.0.3 // Latest available version is detected (15.0.3).
  react: 19.0.0-rc-66855b96-20241106
  react-dom: 19.0.0-rc-66855b96-20241106
  gql.tada: 1.8.10
  graphql: 16.9.0
  urql: 4.2.1
Next.js Config:
  output: N/A
```


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

Turbopack

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

next dev (local)

### Additional context

_No response_
Repository: ui
Issue: [bug]: "The component was not found. It may not exist at the registry. Please make sure it is a valid component."
Labels: bug

### Describe the bug

I was putting my v0 code in to cursor AI and it gave me this error after doing the whole procedure thing. I have searched for how to fix this, but all of them are not helping. Please if someone could give me a few minutes of their time, I would be really thankfull. 
![image](https://github.com/user-attachments/assets/6195cb76-8306-49b0-a6f4-4cf642865a6c)


### Affected component/components

styles

### How to reproduce

npx shadcn@latest and add the v0 codebase

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
windows 10? idk what to put here
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: next.js
Issue: Source map warning on Next 15.0.3 with turbopack, Windows, Firefox
Labels: please add a complete reproduction,Turbopack,linear: turbopack

### Link to the code that reproduces this issue

https://github.com/altbdoor/nextjs-sourcemap-warning-firefox-reproduction

### To Reproduce

1. Create a base reproduction template with `npx create-next-app -e reproduction-template`
2. Name the project as `test-ground`
3. `cd test-ground`
4. `npm run dev -- --turbo`
5. Open http://localhost:3000 in Windows Firefox 133.0 (64-bit)
6. Get warning on source map error


### Current vs. Expected behavior

```
Source map error: Error: Invalid URL: file://C%3A/Users/carbon/projects/test-ground/node_modules/next/src/client/app-bootstrap.ts
Stack in the worker:URLImpl@resource://devtools/client/shared/vendor/whatwg-url.js:22:13
setup@resource://devtools/client/shared/vendor/whatwg-url.js:537:14
URL@resource://devtools/client/shared/vendor/whatwg-url.js:246:18
createSafeHandler/<@resource://devtools/client/shared/vendor/source-map/lib/util.js:181:17
computeSourceURL@resource://devtools/client/shared/vendor/source-map/lib/util.js:437:22
BasicSourceMapConsumer/</that._absoluteSources<@resource://devtools/client/shared/vendor/source-map/lib/source-map-consumer.js:213:23
BasicSourceMapConsumer/<@resource://devtools/client/shared/vendor/source-map/lib/source-map-consumer.js:212:33

Resource URL: http://localhost:3000/_next/static/chunks/node_modules_next_dist_client_239c40._.js
Source Map URL: node_modules_next_dist_client_239c40._.js.map
```

<details><summary>Show warning image</summary>

![image](https://github.com/user-attachments/assets/cdec58ab-8a30-43c3-bff8-56aa7a179175)

</details> 

Should not have the warning, I suppose?

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro
  Available memory (MB): 16206
  Available CPU cores: 12
Binaries:
  Node: 22.11.0
  npm: 10.9.0
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 15.0.4-canary.32 // Latest available version is detected (15.0.4-canary.32).
  eslint-config-next: N/A
  react: 19.0.0-rc-b01722d5-20241114
  react-dom: 19.0.0-rc-b01722d5-20241114
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Turbopack

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

This warning **did not** appear for:

- Windows Edge 131.0.2903.70 (Official build) (64-bit), all `npm run` commands
- Windows Firefox 133.0 (64-bit), `npm run dev` without turbopack
- Windows Firefox 133.0 (64-bit), `npm run start` after build

Edit: tried it on Windows Firefox private mode with all extensions disabled, and I still see the warning.
Repository: rust
Issue: Scrutinee dropped after if-let body
Labels: A-lifetimes,T-lang,C-discussion

Objects inside block expressions in the scrutinee of an if-let statement are not dropped before the body.

This is inconsistent both with declaring a temporary variable, e.g. `x` in test #2, and let-else behavior in test #3. 

I tried this code:

```rust
fn main() {
	struct S(i32);
	impl Drop for S {
		fn drop(&mut self) {
			println!("Dropped S {}", self.0)
		}
	}

	println!("--- test 1");
	{
		println!("Before if-let");
		if let _ = { S(1).0 } {
			println!("Inside body");
		}
	}

	println!("--- test 2");
	{
		println!("Before if-let");
		let x = { S(2).0 };
		if let _ = x {
			println!("Inside body");
		}
	}

	println!("--- test 3");
	{
		println!("Before let-else");
		let _ = ({ S(3).0 }) else { unreachable!() };
		println!("After let-else");
	}
}
```

I expected to see this happen:
```
--- test 1
Before if-let
Dropped S 1
Inside body
--- test 2
Before if-let
Dropped S 2
Inside body
--- test 3
Before let-else
Dropped S 3
After let-else
```

Instead, this happened:
```
--- test 1
Before if-let
Inside body
Dropped S 1
--- test 2
Before if-let
Dropped S 2
Inside body
--- test 3
Before let-else
Dropped S 3
After let-else
```

### Meta

Same behavior on both stable and nightly.

`rustc --version --verbose`:
```
rustc 1.82.0 (f6e511eec 2024-10-15)
binary: rustc
commit-hash: f6e511eec7342f59a25f7c0534f1dbea00d01b14
commit-date: 2024-10-15
host: x86_64-unknown-linux-gnu
release: 1.82.0
LLVM version: 19.1.1
```
Repository: rust
Issue: Tracking issue for release notes of #132056: Stabilize `#[diagnostic::do_not_recommend]`
Labels: T-lang,relnotes,relnotes-tracking-issue


This issue tracks the release notes text for #132056.

### Steps

- [ ] Proposed text is drafted by PR author (or team) making the noteworthy change.
- [ ] Issue is nominated for release team review of clarity for wider audience.
- [ ] Release team includes text in release notes/blog posts.

### Release notes text

The responsible team for the underlying change should edit this section to replace the automatically generated link with a succinct description of what changed, drawing upon text proposed by the author (either in discussion or through direct editing).

````markdown
# Language
- [Stabilize `#[diagnostic::do_not_recommend]`](https://github.com/rust-lang/rust/pull/132056)
````

> [!TIP]
> Use the [previous releases](https://doc.rust-lang.org/nightly/releases.html) categories to help choose which one(s) to use.
> The category will be de-duplicated with all the other ones by the release team.
>
> *More than one section can be included if needed.*

### Release blog section

If the change is notable enough for inclusion in the blog post, the responsible team should add content to this section.
*Otherwise leave it empty.*

````markdown
````

cc @weiznich, @compiler-errors -- origin issue/PR authors and assignees for starting to draft text
Repository: rust
Issue: Tracking issue for release notes of #132397: Make missing_abi lint warn-by-default.
Labels: T-lang,relnotes,relnotes-tracking-issue


This issue tracks the release notes text for #132397.

### Steps

- [x] Proposed text is drafted by PR author (or team) making the noteworthy change.
- [ ] Issue is nominated for release team review of clarity for wider audience.
- [ ] Release team includes text in release notes/blog posts.

### Release notes text

The responsible team for the underlying change should edit this section to replace the automatically generated link with a succinct description of what changed, drawing upon text proposed by the author (either in discussion or through direct editing).

````markdown
# Category (e.g. Language, Compiler, Libraries, Compatibility notes, ...)
- [Make missing_abi lint warn-by-default.](https://github.com/rust-lang/rust/pull/132397)
````

> [!TIP]
> Use the [previous releases](https://doc.rust-lang.org/nightly/releases.html) categories to help choose which one(s) to use.
> The category will be de-duplicated with all the other ones by the release team.
>
> *More than one section can be included if needed.*

### Release blog section

If the change is notable enough for inclusion in the blog post, the responsible team should add content to this section.
*Otherwise leave it empty.*

````markdown
Omitting the ABI in extern blocks and functions (e.g. `extern {}` and `extern fn`)
will now result in a warning. Omitting the ABI after the `extern` keyword has always
implicitly resulted in the `"C"` ABI. It is now recommended to explicitly specify
the `"C"` ABI (e.g. `extern "C" {}` and `extern "C" fn`).
````

cc @m-ou-se, @traviscross -- origin issue/PR authors and assignees for starting to draft text
Repository: godot
Issue: Vulkan API Error: err != VK_SUCCESS in fence_wait and command_queue_execute_and_present
Labels: bug,platform:linuxbsd,topic:rendering,needs testing

### Tested versions

Godot_v4.3-stable

### System information

Debain12-Godot_v4.3-stable-Vulkan(1.2.175)forward-dedicated nvidia geforce gtx 710

### Issue description

When running a project in Godot using Vulkan, the following errors appear in the console:
ERROR: Condition "err != VK_SUCCESS" is true. Returning: FAILED
   at: fence_wait (drivers/vulkan/rendering_device_driver_vulkan.cpp:2066)
ERROR: Condition "err != VK_SUCCESS" is true. Returning: FAILED
   at: command_queue_execute_and_present (drivers/vulkan/rendering_device_driver_vulkan.cpp:2266)


### Steps to reproduce

1.Open the project in Godot.
2.Start the project and render a scene.
3.After a while, observe the console where the error messages appear during rendering.(point to be note that after some while it start showing this behaviour)


### Minimal reproduction project (MRP)

This issue occurs in all my projects, so it is not specific to a particular setup or scene. You can replicate the problem by creating a new project with default settings, using Vulkan as the rendering backend, and running it for a while until the error appears during scene rendering.
Repository: ollama
Issue: Audio to audio models
Labels: feature request

Hi, any plan to add audio to audio support? There are couple of open source model witch provide that
Repository: rust
Issue: Unnecessarily complex suggestion when using extraneous reference type
Labels: A-diagnostics,T-compiler,A-suggestion-diagnostics

### Code

```Rust
fn main() {
    let a: Vec<i32> = Vec::new();
    let ref_a = &a;
    let mut b: Vec<i32> = Vec::new();
    b.extend(&ref_a);
}
```

### Current output

```Shell
error[E0277]: `&&Vec<i32>` is not an iterator
   --> src/main.rs:5:14
    |
5   |     b.extend(&ref_a);
    |       ------ ^^^^^^ `&&Vec<i32>` is not an iterator
    |       |
    |       required by a bound introduced by this call
    |
    = help: the trait `Iterator` is not implemented for `&&Vec<i32>`, which is required by `&&Vec<i32>: IntoIterator`
    = note: required for `&&Vec<i32>` to implement `IntoIterator`
note: required by a bound in `extend`
   --> /playground/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/iter/traits/collect.rs:450:18
    |
450 |     fn extend<T: IntoIterator<Item = A>>(&mut self, iter: T);
    |                  ^^^^^^^^^^^^^^^^^^^^^^ required by this bound in `Extend::extend`
help: consider dereferencing here
    |
5   |     b.extend(&*ref_a);
    |               +

For more information about this error, try `rustc --explain E0277`.
```

### Desired output

```Shell
help: consider removing the borrow
```

### Rationale and extra context

The part that says:
```
help: consider dereferencing here
    |
5   |     b.extend(&*ref_a);
```
seems overly complicated, since a simpler solution is to just remove the borrow. It's possible there are cases when such a reborrow is needed, but when it is not, the simpler suggestion would be welcome.

Note that the message `help: consider removing the borrow` already exists in other situations (e.g. passing an `&i32` argument to a function that expects a `i32`).

### Other cases

```Rust

```

### Rust Version

```Shell
rustc 1.82.0 (f6e511eec 2024-10-15)
binary: rustc
commit-hash: f6e511eec7342f59a25f7c0534f1dbea00d01b14
commit-date: 2024-10-15
host: x86_64-unknown-linux-gnu
release: 1.82.0
LLVM version: 19.1.1
```

### Anything else?

_No response_
Repository: godot
Issue: "Make Local" will still reference original until editor restart.
Labels: bug,topic:editor

### Tested versions

- Reproducible in v4.3.stable.official [77dcf97d8], v4.4.dev5.official [9e6098432]

### System information

Windows 11 Vulkan forward + dedicated Nvidia GPU 3080

### Issue description

When a scene is "Make Local" resources attached to the scene are not made unique until after editor restart. 



https://github.com/user-attachments/assets/3f9fe79b-0f98-4606-bc6b-2a4d465a6aac


### Steps to reproduce

Add scene into scene tree, create a duplicate or drag an additional scene into the editor make one of the scenes "Make Local" , SAVE SCENE.  Go into the inspector panel and change a property, for example the albedo color, and observe that the scene that was not made local and references the original scene and resources also changes. Restart the editor to get the first scene to reference the original again.

### Minimal reproduction project (MRP)

[MRP](https://share.childlearning.club/s/RgpoM2dxcPkmpG7)

---
- NOTE: An editor restart can be avoided by going into the inspector and first making the mesh unique and then going to the surface material and selecting the "Make Unique" before making any changes to the albedo color. In this case everything works as I would understand the "Make Local" would work as intended, or at least the same result from what I can tell from "Make Local" and then doing an editor restart. To be clear, I don't know if "Make Local" is supposed to make sub-resources unique, it just appears to be what it is doing. And if that is what it is intended to do it is not doing it until after the editor restart.

- EDIT: Just found that the same behavior exists when selecting a scene from the scene tree and copying its surface material over to the surface material override. all scenes that reference the original scene show a change when this scenes surface material override's albedo color is changed, until editor restart, where they then revert back to the original.
Repository: tauri
Issue: [feat] Include local NSH files in windows NSIS hooks
Labels: type: feature request

### Describe the problem

Would be awesome to be able to use the !include feature in our `hooks.nsi` file so that we can abstract our nsi/nsh files.

### Describe the solution you'd like

Not sure if this is already possible but attempting to do `!include "Example.nsh"` doesn't work neither does prepending "./" or ".\".

Perhaps we need the `windows.nsis.installerHooks` to take in an array instead of a string so we can register other nsh/nsi files in there as well?

### Alternatives considered

Currently I just paste everything into my .nsi file which is just messy but does work.

### Additional context

The context is that I am working on an image viewer and using the `FileAssociation.nsh` script from the NSIS documentation:
https://nsis.sourceforge.io/File_Association
Repository: godot
Issue: Overriding virtual properties in C# leads to errors in the generated code.
Labels: needs testing,topic:dotnet

### Tested versions

4.2 and 4.3



### System information

Godot v4.3.stable.mono - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3080 Ti (NVIDIA; 32.0.15.6603) - AMD Ryzen 9 5950X 16-Core Processor (32 Threads)

### Issue description

Overriding virtual properties in C# leads to errors in the generated code.


### Steps to reproduce

Uncomment override code in SimpleOverride.cs

### Minimal reproduction project (MRP)

[Scripts.zip](https://github.com/user-attachments/files/17966933/Scripts.zip)

Included just a simple scripts folder for a fresh Godot project.
Repository: pytorch
Issue: F.cross_entropy unexpectedly slower than F.log_softmax + torch.gather
Labels: module: performance,module: nn,triaged

I’m working on some training code that computes the total log probabilities of prediction sequences (i.e. outputs from a language model).

I had previously implemented this using `F.log_softmax` followed by `torch.gather`, but realized this can also be done with `F.cross_entropy` with `reduction='none'` followed by a sum operation over the last dimension. I rewrote my code using `F.cross_entropy` thinking it would speed up my code since it’s a single builtin function instead of two but to my surprise, training is now significantly slower.

Here’s a hacky microbenchmark script capturing what I’m talking about:

```
import torch
import torch.nn.functional as F
import time

torch.manual_seed(42)

batch_size, seq_len, vocab_size = 2, 512, 50257
logits = torch.randn(batch_size, seq_len, vocab_size)
labels = torch.randint(0, vocab_size, (batch_size, seq_len))
labels[labels % 3 == 0] = -100

labels_safe = labels.detach()
labels_safe[labels_safe == -100] = 0

logits = logits.to("cuda")
labels = labels.to("cuda")
labels_safe = labels_safe.to("cuda")


def benchmark(func, num_iters=20):
    torch.cuda.synchronize()
    start = time.perf_counter()
    for _ in range(num_iters):
        value = func()
        torch.cuda.synchronize()
    end = time.perf_counter()
    return (end - start) / num_iters, value


def original_method():
    token_logprobs = F.log_softmax(logits, dim=-1)
    gathered_logprobs = torch.gather(
        token_logprobs, 2, labels_safe.unsqueeze(-1)
    ).squeeze(-1)
    mask = (labels_safe != -100).float()
    loss = (gathered_logprobs * mask).sum(dim=-1)
    return -loss


def new_method():
    token_loss = F.cross_entropy(
        logits.permute(0, 2, 1),
        labels,
        reduction="none",
    )
    loss = token_loss.sum(dim=-1)
    return loss


num_iters = 20
original_time, original_value = benchmark(original_method, num_iters)
new_time, new_value = benchmark(new_method, num_iters)

print(f"Original Average Time: {original_time * 1e3:.3f} ms")
print(f"Original Value: {original_value.tolist()}")
print(f"New Average Time: {new_time * 1e3:.3f} ms")
print(f"New Value: {new_value.tolist()}")
```

Outputs on 1x A100 GPU:

```
Original Average Time: 2.653 ms
Original Value: [5802.1328125, 5825.033203125]
New Average Time: 76.821 ms
New Value: [5802.1328125, 5825.0341796875]
```

I thought it might be due to the `reduction='none'`, but commenting it out doesn’t lead to any noticeable speedup. I'm on version 2.5.0.

Does anyone know what might be happening here?

cc @msaroufim @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki
Repository: go
Issue: cmd/internal/testdir: Test/fixedbugs/issue70189.go failures
Labels: NeedsInvestigation

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

Issue created automatically to collect these failures.

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

    === RUN   Test/fixedbugs/issue70189.go
    === PAUSE Test/fixedbugs/issue70189.go
    === CONT  Test/fixedbugs/issue70189.go
        testdir_test.go:147: exit status 1
            go: error obtaining buildID for go tool link: fork/exec /home/swarming/.swarming/w/ir/x/w/goroot/pkg/tool/netbsd_arm/link: bad file descriptor
            
    --- FAIL: Test/fixedbugs/issue70189.go (789.44s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: PowerToys
Issue: App picker
Labels: Idea-New PowerToy,Needs-Triage

### Description of the new feature / enhancement

Can you add a feature that force this panel similar to android ![Image](https://github.com/user-attachments/assets/ea5f6291-34c0-4d5f-a918-92bc588a58b4)
something similar to this app https://switchbar.com/



### Scenario when this would be used?

Let's say you clicked a link from an app and you have a chrome default browser.
if you have 3 chrome profile and one of them is open already the link will always goes to the last profile used. 
But if you go through the "Default app selector by windows"  you will open chrome home instead than select the profile you need. 
By the way, this always work when you install a new browser the first time. but after some use it disappear without notice![Image](https://github.com/user-attachments/assets/5a153ad7-8f79-4396-ba9c-844a2969b49d)
. 

### Supporting information

_No response_