sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: x/tools/gopls: don't link command-line-arguments packages in hover
Labels: gopls,Tools

This is a follow-up issue to fix some remaining bugs in hovering over command-line-arguments packages.
1. We should url-escape package paths.
2. We should not offer links to command-line-arguments packages, as they are not real.

              So, to summarize, there are two bugs here:

              1. gopls is not properly url-escaping package paths.
              3. ~gopls is not providing accurate hover information for builtins, when viewing the builtin file.~

              (1) should be fixed by a relatively straighforward application of url escaping. Assigning to our new team member @h9jiang as this is a good starter exercise for bug fixing and writing a test.

              On the other hand, (2) might require a more sweeping refactoring of how we handle the builtin file and unsafe packages, and is just about the polar opposite of a good starter bug: requires familiarity with nitty-gritty details of the codebase. I will do this part.

_Originally posted by @findleyr in https://github.com/golang/go/issues/68026#issuecomment-2182899550_
Repository: pytorch
Issue: [ONNX] Run report_exportability when report=True
Labels: module: onnx,triaged,onnx-triaged

Leverage https://github.com/pytorch/pytorch/blob/99deedff57feca48af8a364e49325c99acc0a541/torch/_export/tools.py#L61C5-L61C25 when there is an export issue when generating the ONNX export report.
Repository: flutter
Issue: [Cocoon] FR: Use class-level logging and structured logging
Labels: team-infra,P2,triaged-infra

While debugging issues, all lines are logged unstructured. You can search for specific logs using regex, but you cannot search for "all error logs for class Fu".

Cocoon is using the regular dart logger, so this would be:

1. Every class that logs creates a static `log = Logger('$ClassName');`
2. Add a listener to root level logging that logs the name and the level (if > info).

For 2; we currently call `useLoggingPackageAdaptor()` for appengine - which adds the log name, but the level is passed through to the service. so if we wanted `[level]` in the name, we might have to make detached loggers who modify their message before passing along to the root (appengine watching) logger.

```dart
            message = '${record.loggerName}: $message';
```
Repository: rust
Issue: `thread_local!` initialization code panics on some `aarch64-apple-darwin` envs, works on others
Labels: O-macos,A-thread-locals,C-bug,T-libs,O-AArch64,E-needs-investigation

I tried this code:

https://github.com/near/near-sdk-rs/blob/master/near-sdk/src/environment/mock/mod.rs#L11-L16

```rust
thread_local! {
    static BLOCKCHAIN_INTERFACE: RefCell<MockedBlockchain>
         = RefCell::new(MockedBlockchain::default());
}
```

I expected to see this happen: 

`thread_local!` initialization code for `RefCell::new(MockedBlockchain::new)`
works

Instead, this happened: 

on **unclarified** `aarch64-apple-darwin` environment(s) `thread_local!`
panics on https://doc.rust-lang.org/src/core/ptr/mod.rs.html#1277 .

The issue doesn't reproduce on other `aarch64-apple-darwin` real macs, 
and on `macos-14-arm64` github actions vm.

Original issue: https://github.com/near/near-sdk-rs/issues/1252 


### Meta

`rustc --version --verbose`:

```
stable: 1.80, 1.81, 1.82 panics
beta 1.83 panics
nightly 1.84 panics
```

backtrace from original issue: 
https://github.com/near/near-sdk-rs/issues/1252#issuecomment-2454692564
Repository: pytorch
Issue: Setting a `str` value to `weight` and `pos_weight` argument of `BCEWithLogitsLoss()` gets an indirect error message
Labels: module: nn,triaged

### 🐛 Describe the bug

Setting the `complex` value `3.+2.j` to `weight` and `pos_weight` argument of [BCEWithLogitsLoss()](https://pytorch.org/docs/main/generated/torch.nn.BCEWithLogitsLoss.html) gets the direct error message as shown below:

```python
import torch
from torch import nn

tensor1 = torch.tensor([8., -3., 0., 1., 5., -2.])
tensor2 = torch.tensor([-3., 7., 4., -2., -9., 6.])
                                                   # ↓↓↓↓↓↓
bcelogits = nn.BCEWithLogitsLoss(weight=torch.tensor(3.+2.j))
bcelogits(input=tensor1, target=tensor2) # Error
                                                       # ↓↓↓↓↓↓
bcelogits = nn.BCEWithLogitsLoss(pos_weight=torch.tensor(3.+2.j))
bcelogits(input=tensor1, target=tensor2) # Error
```

> RuntimeError: result type ComplexFloat can't be cast to the desired output type Float

But setting the `str` value `"Hello"` to `weight` and `pos_weight` argument of `BCEWithLogitsLoss()` gets the indirect error message as shown below:

```python
import torch
from torch import nn

tensor1 = torch.tensor([8., -3., 0., 1., 5., -2.])
tensor2 = torch.tensor([-3., 7., 4., -2., -9., 6.])
                                                   # ↓↓↓↓↓↓↓
bcelogits = nn.BCEWithLogitsLoss(weight=torch.tensor("Hello"))
bcelogits(input=tensor1, target=tensor2) # Error
                                                       # ↓↓↓↓↓↓↓
bcelogits = nn.BCEWithLogitsLoss(pos_weight=torch.tensor("Hello"))
bcelogits(input=tensor1, target=tensor2) # Error
```

> TypeError: new(): invalid data type 'str'

And, setting the `bool` value `True` to `pos_weight` argument of `BCEWithLogitsLoss()` gets the indirect error message as shown below:

```python
import torch
from torch import nn

tensor1 = torch.tensor([8., -3., 0., 1., 5., -2.])
tensor2 = torch.tensor([-3., 7., 4., -2., -9., 6.])
                                                       # ↓↓↓↓
bcelogits = nn.BCEWithLogitsLoss(pos_weight=torch.tensor(True))
bcelogits(input=tensor1, target=tensor2) # Error
```

> RuntimeError: Subtraction, the `-` operator, with a bool tensor is not supported. If you are trying to invert a mask, use the `~` or `logical_not()` operator instead.

So, their error messages should be direct as shown below:

> RuntimeError: result type str can't be cast to the desired output type Float

> RuntimeError: result type bool can't be cast to the desired output type Float

Or, their error messages should be direct as shown below:

> RuntimeError: weight should be Float

> RuntimeError: pos_weight should be Float


### Versions

```python
import torch

torch.__version__ # '2.5.1'
```

cc @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki
Repository: deno
Issue: Add JS binding for wgpu's start_capture and stop_capture
Labels: suggestion,webgpu

I would like to use Deno to profile WebGPU compute workloads within Xcode without any need for graphics. Currently, to capture a Metal trace within Xcode for a Deno workload, I'm having to create a window and canvas, invoke my compute workload, and then present the canvas, and then I can (manually) capture the Metal layer and see my compute-workload profile. This is not ideal; I don't want or need graphics at all. I'd like to do this at the command line and/or completely headless.

I believe I can do this if I have JS bindings to the [wgpu calls `start_capture` and `stop_capture`](https://docs.rs/wgpu/latest/wgpu/struct.Device.html#method.start_capture). With JS bindings to those calls, I can then start and stop capture around my compute workload, then run within Xcode and see profile information.

What would make this even better is if I could write that trace to a file (and this was exposed in JS). Metal has a [`MTLCaptureManager`](https://developer.apple.com/documentation/metal/mtlcapturemanager) and https://github.com/gfx-rs/wgpu/pull/3504 appears relevant here.

Also please note https://github.com/gfx-rs/wgpu/issues/6255, which notes Metal backend device capture issues in wgpu.

cc: @raphlinus
Repository: animate.css
Issue: [FEATURE] Combining multiple classes
Labels: feature request

### Is your feature request related to a problem? Please describe.

It will be great if you can combine multiple classes.

### Describe the solution you'd like.

```
<h1 class="animate__animated animate__backInLeft 
pause-0.5 
animate__bounce 
pause-1 .0
animate__backOutRight
">
  An animated element
</h1>
```

### Describe alternatives you've considered.

n/a

### Additional Context

_No response_
Repository: TypeScript
Issue: "Private identifers are only available when"... should not occur in .d.ts files
Labels: Bug,Help Wanted

See https://github.com/microsoft/TypeScript/issues/60427#issuecomment-2460357068
Repository: flutter
Issue: [ios][platform_view]Fix weird implementation of gesture recognizer delegate in FlutterDelayingGestureRecognizer 
Labels: platform-ios,a: platform-views,P2,c: tech-debt,team-ios,triaged-ios

### Use case

Just circle back on [this PR](https://github.com/flutter/engine/pull/55724) which got reverted, but some weird implementation we found is still valid: 

1. `shouldBeRequiredToFailByGestureRecognizer` checks `otherGestureRecognizer != self`, which is always YES, since we set `self` (the delaying recognizer) as the delegate. 

2. `shouldRequireFailureOfGestureRecognizer` checks `otherGestureRecognizer == self`, which is always NO for the same reason. The PR changed it to `otherGestureRecognizer == _forwardingRecognizer`, however, it makes one of our customer's app not responding to touch completely. 


### Proposal

We might as well just fix this logic error as a clean up. 

In long term, if we are able to get https://github.com/flutter/flutter/issues/157080 done, we can remove the 2 recognizers all together. Though I am still curious how the reverted PR broke one of our customer's app, which can be helpful for us to identify any missing corner cases for testing purpose.
Repository: TypeScript
Issue: "Bigint literals are not available when targeting..." error should not occur in .d.ts files
Labels: Bug,Help Wanted

See https://github.com/microsoft/TypeScript/issues/60427#issuecomment-2460357068
Repository: go
Issue: x/tools/go/{packages/packagestest,expect}: deprecate, tag, and delete
Labels: Proposal-Accepted,Tools

- [golang.org/x/tools/go/packages/packagestest](https://golang.org/x/tools/go/packages/packagestest)
- [golang.org/x/tools/go/expect](https://golang.org/x/tools/go/expect)

**Background:** These packages, designed for use in tests in x/tools, were published without proper deliberation, so any changes to their public APIs must go through the proposal process. There are dozens of improvements we (in x/tools) would like to have made that are simply too costly as a result. However, these packages are almost never used outside x/tools. Of the couple dozen [imports reported by pkg.go.dev](https://pkg.go.dev/golang.org/x/tools/go/packages/packagestest?tab=importedby), nearly all are in repos that are forks of x/tools. The only real one is is k8s.io.

**Proposal:** We propose to fork these packages to an internal subtree, and then to tag and delete the public packages using the same process as https://github.com/golang/go/issues/59676.
Repository: pytorch
Issue: Both `input` and `target` argument or at least `target` argument of `BCELoss()` shoud accept the values out of `0 <= x <= 1` so that `BCELoss()` with `torch.sigmoid()` and `nn.Sigmoid()` gets the same results as `BCEWithLogitsLoss()`.
Labels: module: nn,module: loss,triaged

### 🚀 The feature, motivation and pitch

I can use `0 <= x <= 1` values both for `input` and `target` argument of [BCEWithLogitsLoss()](https://pytorch.org/docs/main/generated/torch.nn.BCEWithLogitsLoss.html) and [BCELoss()](https://pytorch.org/docs/main/generated/torch.nn.BCELoss.html) with [torch.sigmoid()](https://pytorch.org/docs/stable/generated/torch.sigmoid.html) and [nn.Sigmoid()](https://pytorch.org/docs/stable/generated/torch.nn.Sigmoid.html) to get the same results as shown below:

```python
import torch
from torch import nn

tensor1 = torch.tensor([0.4, 0.8, 0.6, 0.3, 0.0, 0.5])
tensor2 = torch.tensor([0.2, 0.9, 0.4, 0.1, 0.8, 0.5])

bcelogits = nn.BCEWithLogitsLoss()
bcelogits(input=tensor1, target=tensor2)
# tensor(0.7205)

bceloss = nn.BCELoss()
bceloss(input=torch.sigmoid(input=tensor1), target=tensor2)
# tensor(0.7205)

sigmoid = nn.Sigmoid()

bceloss = nn.BCELoss()
bceloss(input=sigmoid(input=tensor1), target=tensor2)
# tensor(0.7205)
```

Then, I can also use the values out of `0 <= x <= 1` both for `input` and `target` argument of `BCEWithLogitsLoss()` but I cannot use the values out of `0 <= x <= 1` both for `input` and `target` argument of `BCELoss()` with `torch.sigmoid()` and `nn.Sigmoid()` to get the same results as shown below. *The results of `BCELoss()` are different from `BCEWithLogitsLoss()` if I use `torch.sigmoid()` and `nn.Sigmoid()` both for `input` and `target` argument of `BCELoss()` as shown below:

```python
import torch
from torch import nn

tensor1 = torch.tensor([8., -3., 0., 1., 5., -2.])
tensor2 = torch.tensor([-3., 7., 4., -2., -9., 6.])

bcelogits = nn.BCEWithLogitsLoss()
bcelogits(input=tensor1, target=tensor2)
# tensor(19.8648)

bceloss = nn.BCELoss()
bceloss(input=torch.sigmoid(input=tensor1), target=tensor2) # Error

bceloss = nn.BCELoss()
bceloss(input=torch.sigmoid(input=tensor1), target=torch.sigmoid(input=tensor2))
# tensor(3.2804)

sigmoid = nn.Sigmoid()

bceloss = nn.BCELoss()
bceloss(input=sigmoid(input=tensor1), target=tensor2) # Error

bceloss = nn.BCELoss()
bceloss(input=sigmoid(input=tensor1), target=sigmoid(input=tensor2))
# tensor(3.2804)
```

> RuntimeError: all elements of target should be between 0 and 1

### Alternatives

So, both `input` and `target` argument or at least `target` argument of `BCELoss()` shoud accept the values out of `0 <= x <= 1` so that `BCELoss()` with `torch.sigmoid()` and `nn.Sigmoid()` gets the same results as `BCEWithLogitsLoss()`.

### Additional context

_No response_

cc @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki
Repository: terminal
Issue: [Terminal Chat Setup] App link like ms-terminal-can://... doesn't launch Terminal
Labels: Issue-Bug,Product-Terminal,Needs-Tag-Fix,Area-Chat

### Windows Terminal version

1.23.3091.0, 1.23.3101.0

### Windows build number

10.0.22631.0

### Other Software

_No response_

### Steps to reproduce

1. Launch Settings
2. Navigate to Terminal Chat (Experimental)
3. Expand GitHub Copilot under Service Providers
4. Click Authenticate via GitHub
5. Authenticate and approve access to GitHub account in browser
6. Click "Open Terminal Canary" in resulting browser modal dialog

### Expected Behavior

Windows Terminal Canary should launch and receive the auth token from GitHub to complete GitHub Copilot setup for Terminal Chat.

### Actual Behavior

Windows Terminal Canary does not launch. This does not work from the default browser (Chrome) nor from Edge.
Repository: TypeScript
Issue: "Go to Symbol in Workspace…" but with symbols in dependencies, or equivalent functionality
Labels: Needs More Info

### 🔍 Search Terms

typescript, symbol, go to symbol in workspace, dependencies

### ✅ Viability Checklist

- [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
- [x] This wouldn't change the runtime behavior of existing JavaScript code
- [x] This could be implemented without emitting different JS based on the types of the expressions
- [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
- [x] This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
- [x] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

### ⭐ Suggestion

When using the "Go to Symbol in Workspace…" feature in VS Code, only symbols within my project are shown. I think it should show symbols in my project _and_ my dependencies, or at the very least there should be a setting to toggle showing dependency symbols.

I previously thought this was a bug but was told this was intentional (#59551) so I'm opening a formal feature request.

### 📃 Motivating Example

I often want to use "Go to Symbol in Workspace…" to look up symbols in Node, TS, VS Code, or other dependencies, as I work. I actually rarely use it to look up my own symbols, I instead use ⌘P and jump to the relevant file.

### 💻 Use Cases

## What do you want to use this for?
I want to use it for browsing the APIs of my dependencies, such as whether a given API even exists.

## What shortcomings exist with current approaches?
It is more tedious to type out the desired type and ⌘-click it.
Sometimes I want to want to look up a symbol to see if it even exists before I type it.

## What workarounds are you using in the meantime?
I type out the symbol and ⌘-click it.
Repository: TypeScript
Issue: Show deprecation warnings on implementations of a deprecated property
Labels: Suggestion,Experience Enhancement

### 🔎 Search Terms

- Deprecated implementation
- Deprecated interface 

Related https://github.com/microsoft/typescript/issues/57584

### 🕗 Version & Regression Information

Not a regression 


### ⏯ Playground Link

_No response_

### 💻 Code

```ts
type I = {
    /**
     * @deprecated
     */
    text: string;
};

function f(i: I) { return i; }
f({ text: 'a' });

const a: I = { text: 'a' }
a.text;
```





### 🙁 Actual behavior

Currently only the last use of `a.text` shows as deprecated![Image](https://github.com/user-attachments/assets/28e5eaf5-ab15-4cec-9a4d-bd4b92a80c0a)


### 🙂 Expected behavior

It would be helpful to also render deprecations for any implementations of `I.text` too as these are also using the deprecated property


### Additional information about the issue

_No response_
Repository: kubernetes
Issue: Job: Consider to limit the number of goroutine workers in parallel executions
Labels: kind/feature,sig/apps,needs-triage

### What would you like to be added?

We would like to consider the possibility of limiting the goroutine workers in the following logics:

https://github.com/kubernetes/kubernetes/blob/2caf4eddd8fc1ab7236ed608c1b548404dbc6bcf/pkg/controller/job/job_controller.go#L1076-L1079

https://github.com/kubernetes/kubernetes/blob/2caf4eddd8fc1ab7236ed608c1b548404dbc6bcf/pkg/controller/job/job_controller.go#L1127-L1130

https://github.com/kubernetes/kubernetes/blob/2caf4eddd8fc1ab7236ed608c1b548404dbc6bcf/pkg/controller/job/job_controller.go#L1426-L1429

https://github.com/kubernetes/kubernetes/blob/2caf4eddd8fc1ab7236ed608c1b548404dbc6bcf/pkg/controller/job/job_controller.go#L1727-L1736

### Why is this needed?

As we discussed in https://github.com/kubernetes/kubernetes/pull/128513#discussion_r1829829553, the current JobController launches the number of Pods goroutine workers to deletion or creation operation against owned Pods.
This allows us to increase JobController operation throughput as long as the APIServer performance.

OTOH, the APIServer seats have limited resources, and it is not unlimited. 
So, when the Job has 1k and 10k parallelisms (`.spec.parallelism`) and completions (`.spec.completions`), the JobController potentially faces the API Priority and Fairness issues, then the kube-controller-manager might be locked out, finally WRITE operation request by the kube-controller-manager never succeeded.

To mitigate these issues, the cluster administrator might be able to prepare the kube-controller-manager specific seat by APF setting by themselves.

But, by default, we might want to prepare minimum safeguards like limiting the number of workers to 100 at the JobController level.

/sig apps
Repository: neovim
Issue: feat(defaults): add ]p and [p linewise mappings from unimpaired-vim
Labels: enhancement,defaults

### Problem

Since https://github.com/neovim/neovim/pull/28525 was merged, I've removed https://github.com/tpope/vim-unimpaired from my configuration. 

I miss nothing except for `]p` and `[p`. Using these, I can force something I've yanked to paste "on its own line", even when the yanked text is not a full line.

Precedent for other additions: 

- #30984 
- #30943

cc @gpanders

### Expected behavior

I'd like those to be present.

Counterpoint: it seems like https://github.com/tummetott/unimpaired.nvim does not have `]p`/`[p`. Maybe that means that few people use it.

These mappings being missing from unimpaired.nvim also means I haven't figured out an effective/short way to define these myself to tide me over. Help from a (n)vim master is welcome.
Repository: flutter
Issue: [pigeon] Consider removing Java generator
Labels: platform-android,package,team-ecosystem,p: pigeon,P2,triaged-ecosystem

(Filing to track and centralize discussion, since this has come up in several discussions.)

The number of generators in Pigeon is an issue for ongoing development (e.g., event channel support), and we are currently maintaining two generators—Java and Kotlin—for the use case of Android plugin development. Ideally we would only maintain one, and Kotlin has a number of advantages (true nullability support, more similarity to the modern generation of languages that also use, most notably Dart and Swift).

In favor of turning it down:
- Java/Kotlin interop is pretty seamless; in my experiment with some Flutter-team-owned plugins, I could replace the Java generated code with Kotlin generated code with almost no changes to non-generated code.
- It gives us stronger type safety all the way to the client-authored code boundary, so there's some incremental value in switching.

Impediments to turning it down:
- We are not using Kotlin in our own plugins currently, and don't have plans to switch in the near term, so we would be introducing an extra language (although not one we would need to interact with regularly as it's generated).
- Adding a Kotlin dependency to a plugin that didn't previously have one can affect plugin clients, and increase the incidence of ecosystem issues like Kotlin version mismatches.
Repository: flutter
Issue: [pigeon] Consider removing Obj-C generator
Labels: platform-ios,platform-mac,package,team-ecosystem,p: pigeon,P2,triaged-ecosystem

(Filing to track and centralize discussion, since this has come up in several discussions.)

The number of generators in Pigeon is an issue for ongoing development (e.g., event channel support), and we are currently maintaining two generators—Objective-C and Swift—for the use case of iOS/macOS plugin development. Ideally we would only maintain one, which given the direction of iOS and macOS development would be Swift.

In favor of turning it down:
- We're actively working on [deprecating explicit support for Obj-C in Flutter tooling](https://github.com/flutter/flutter/issues/148586).
- We [want to be using Swift for our own Plugins](https://github.com/flutter/flutter/issues/119015), at which point we would not have any actual first-party usage.

Impediments to turning it down:
- Swift/Obj-C interop is non-trivial; in particular, it doesn't seem to be possible to implement a Swift interface in Obj-C, so at least the top level code (the plugin class, or code factored out of it in cases where that's the whole implementation) would need to be converted to Swift as part of switching to the Swift Pigeon generator. That's work we want to do eventually, but isn't currently a priority.
  - This would apply to third parties as well; very crude GitHub search (e.g., no fork de-duping) suggests a majority of iOS Pigeon clients are using Obj-C rather than Swift, but not an overwhelming majority. Of course, they could always keep using older versions of Pigeon until they had time to transition.
  - Clients would be forced to write/maintain non-generated Swift code, which is not ideal for plugin maintainers who want to use Obj-C based on their own experience.