sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: x/text: support for go/types.Aliases
Labels: NeedsInvestigation

The main package  cmd/gotext needs to be updated to set gotypesalias=1 GODEBUG value by default when built by a toolchains >= 1.24. Otherwise it will not be able to type check inputs with type parameterized aliases (1.24). This can be done by conditionally setting the variable (see https://go.dev/cl/627715 for an example). Or updated the go.mod to go language setting to >= 1.23.

`golang.org/x/text/message/pipeline` may need to by updated to support go/types.Alias being produced by the type checker. Given that this calls `go/types.Underlying()`, it likely needs to be updated. Alternatively this could be audited by an expert on the package to determine if this is not necessary.

See #69772 for additional context.

CC @mpvl
Repository: vscode
Issue: Interactive window shows standard editor rulers
Labels: bug,interactive-window

Settings:

```js
  "editor.rulers": [
    80,
    { "column": 100 },
    { "column": 120, "color": "#662222" },
  ],
```

I don't expect these to show up in the interactive window:

![Image](https://github.com/user-attachments/assets/bbb253d3-7845-4254-8331-8e841e44b238)
Repository: vscode
Issue: Can barely make out interactive window export icon on standard density monitor
Labels: bug,icons-product,interactive-window

Windows @ 100% scale monitor, 1 devicePixelRatio (ie. pretty standard setup):

![Image](https://github.com/user-attachments/assets/ffb683cf-5f98-4547-a786-696c5cf3feef)

![Image](https://github.com/user-attachments/assets/04463f10-adf0-474d-85c7-054f812686cc)

Compare that to the collapse icon which looks great (designed for this size so no blurring, has sub-pixel anti-aliasing as it's a codicon):

![Image](https://github.com/user-attachments/assets/8ae50328-a4d6-4d20-98cc-4708d8d24c47)
Repository: go
Issue: x/mobile: support for go/types.Aliases
Labels: NeedsInvestigation,mobile

The main packages cmd/{gobind,gomobile} need to be updated to set gotypesalias=1 GODEBUG value by default when built by a toolchains >= 1.24. Otherwise they will not be able to type check inputs with type parameterized aliases (1.24). This can be done by conditionally setting the variable (see https://go.dev/cl/627715 for an example). Or updated the go.mod to go language setting to >= 1.23.

`golang.org/x/mobile/bind` may need to by updated to support go/types.Alias being produced by the type checker. Given that this calls `go/types.Underlying()`, it likely needs to be updated. Alternatively this could be audited by an expert on the package to determine if this is not necessary.

See #69772 for additional context.

CC @hyangah
Repository: vscode
Issue: Actives disappear when focusing between a notebook, interactive window and native REPL
Labels: bug,notebook-layout,notebook-variables

![Image](https://github.com/user-attachments/assets/3f815c6a-c9b9-4e98-94c4-34f11eb42e76)
Repository: flutter
Issue: 3.28 branch info
Labels: team-release

### 3.28 beta branch info ###

| Repo | Branch | Commit | Internal CL |
| --- | --- | --- | --- |
| flutter/flutter | [flutter-3.28-candidate.0](https://github.com/flutter/flutter/tree/flutter-3.28-candidate.0) | https://github.com/flutter/flutter/commit/74669e4bf1352a5134ad68398a6bf7fac0a6473b | cl/702911218 |
| flutter/engine | [flutter-3.28-candidate.0](https://github.com/flutter/engine/tree/flutter-3.28-candidate.0) | https://github.com/flutter/engine/commit/9e8fcad4eaf6c266f032ea9ec304739fb316a7dc | N/A |
| dart-lang/sdk | [3.7.0-209.0.dev](https://github.com/dart-lang/sdk/tree/3.7.0-209.0.dev) | https://github.com/dart-lang/sdk/commit/61bfa9bbb91d50754f6b6a2bef5629c9fd074e6f | cl/702410045 |
| google/skia | as needed | https://github.com/google/skia/commit/c9647f13cdedac9871fd93a70e3fa27d8f8972b9 | N/A |

CC @christopherfujino @zanderso
Repository: kubernetes
Issue: Namespace deletion does not trigger container lifecycle hooks
Labels: kind/bug,kind/support,sig/node,triage/needs-information,needs-triage

### What happened?

I want to ensure that certain commands are run on graceful deletion of a pod, so I have set up a container lifecycle prestop hook to do so. Deleting the pod does trigger the prestop hook as expected; however, when deleting the namespace that the pod is in, I would expect this to also be a graceful shutdown event, which should trigger the prestop hook, but this does not happen. In addition, helm uninstalling our helm chart with the relevant statefulset has the same issue. See the test example below where we have setup RBAC for kubectl access within the container:

```
apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: <>
  namespace: <>
  labels:
    component: <>
    app: <>
spec:
  ...
  template:
    metadata:
      labels:
    spec:
      containers:
        - name: testContainer
          image: <>
          lifecycle:
           preStop:
             exec:
               command:
                  - /bin/bash
                  - -c
                  - "kubectl label cm test-configmap -n test-prestop-hook testlabel=8 --overwrite"
             
```

### What did you expect to happen?

Prestop hook should be triggered by namespace deletion. 

### How can we reproduce it (as minimally and precisely as possible)?

1. Bring up a pod with a container that has a prestop hook configured
2. Exec into the pod and label the ConfigMap to see that it works (no RBAC or image issues)
3. Delete the namespace that the pod is in (expected to trigger the prestop hook)
4. Wait 30 seconds and see that the prestop hook did not run, configmap label did not change to `testlabel: "8"`

### Anything else we need to know?

_No response_

### Kubernetes version

<details>

```console
$ kubectl version
Client Version: v1.28.1
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.29.10-eks-7f9249a
```

</details>


### Cloud provider

<details>
AWS
</details>


### OS version

<details>

NA

</details>


### Install tools

<details>
Using helm to install the helm chart with statefulset:

$ helm version
version.BuildInfo{Version:"v3.12.3", GitCommit:"3a31588ad33fe3b89af5a2a54ee1d25bfe6eaa5e", GitTreeState:"clean", GoVersion:"go1.20.7"}

</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>
Repository: ant-design
Issue: Dropdown "judders" if it can't figure out where to determine placement
Labels: Inactive,unconfirmed

### Reproduction link

https://codesandbox.io/p/sandbox/8334zm

### Steps to reproduce

1. Open reproduction in new window (https://8334zm.csb.app/).
2. Open dropdown in Actions column.

### What is expected?

The action menu to correctly determine where to open based on available space.

### What is actually happening?

It endlessly "judders", causing a horrible user experience.


### Additional information
This reproduction users a specific column width to easily replicate the issue, but I have seen this issue numerous other locations outside of a table.

| Environment | Info |
| --- | --- |
| antd | 5.22.3 |
| React | Latest |
| System | Windows |
| Browser | All |

---
This seems to be caused by an rc-trigger change.

https://github.com/react-component/trigger/issues/496
https://github.com/react-component/trigger/pull/419

ref: UIEN-6867
<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: TypeScript
Issue: No paste edits returned when copying between commonjs files
Labels: Needs Proposal

### 🔎 Search Terms

5.8.0-dev.20241204

### 🕗 Version & Regression Information

- This changed between versions ______ and _______
- This changed in commit or PR _______
- This is the behavior in every version I tried, and I reviewed the FAQ for entries about _________
- I was unable to test this on prior versions because _______


### ⏯ Playground Link

_No response_

### 💻 Code

From https://github.com/microsoft/vscode/issues/235105#issuecomment-2517293705

1. Create a file `main.js`:
```ts
// main.js
const fs = require('fs');
const dirs = [
	'',
	'build',
];
if (fs.existsSync(`${__dirname}/../../.build/distro/npm`)) {
	dirs.push('.build/distro/npm/remote/web');
}
```


2. Copy the line `	dirs.push('.build/distro/npm/remote/web');`
1. Paste into another file called `other.js` 


Full logs: [tsserver.log](https://github.com/user-attachments/files/18029033/tsserver.log)


### 🙁 Actual behavior

No paste edits returned

Specifically `preparePasteEdits` returns `no content available`:

```
Info 209  [12:07:33.903] request:
    {
      "seq": 10,
      "type": "request",
      "command": "preparePasteEdits",
      "arguments": {
        "file": "/Users/matb/projects/sandbox/main.js",
        "copiedTextSpan": [
          {
            "start": {
              "line": 8,
              "offset": 1
            },
            "end": {
              "line": 9,
              "offset": 1
            }
          }
        ]
      }
    }
Perf 210  [12:07:33.904] 10::preparePasteEdits: elapsed time (in milliseconds) 0.4798
Info 211  [12:07:33.904] response:
    {"seq":0,"type":"response","command":"preparePasteEdits","request_seq":10,"success":false,"message":"No content available."}
```

### 🙂 Expected behavior

We should generate an edit in this case that exports `dir`. This is the behavior I see in other cases

### Additional information about the issue

_No response_
Repository: pytorch
Issue: Refactor generate_fallback_kernel_with_runtime_lookup_jit
Labels: triaged,oncall: pt2

generate_fallback_kernel_with_runtime_lookup_jit and some related functions do no use IndentedBuffer to handle output code indentation nicely. It will be great to fix that and make it consistent with other parts of WrapperCodegen.

cc @chauhang @penguinwu
Repository: pytorch
Issue: Fix segfaulting profiler tests in 3.13
Labels: module: tests,oncall: profiler,module: python frontend

https://github.com/pytorch/pytorch/pull/141674 and https://github.com/pytorch/pytorch/pull/141951 disabled some profiler tests in 3.13/dynamo-wrapped due to segfaults.

cc @seemethere @malfet @pytorch/pytorch-dev-infra @mruberry @ZainRizvi @robieta @chaekit @guotuofeng @guyang3532 @dzhulgakov @davidberard98 @briancoutinho @sraikund16 @sanrise @albanD
Repository: vscode
Issue: Debugging VS Code prints `console.log` statements late
Labels: bug,debug,papercut :drop_of_blood:

Steps to Reproduce:

1.  have a early `console.log` statement in the window on startup
2. debug vscode with F5

🐛 the log message appears quite late
Repository: vscode
Issue: GPU rendering: workbench.colorCustomizations for brackets only applies after window reload
Labels: bug,editor-gpu

Testing #234577, I only see the bracket color change from `workbench.colorCustomizations` applied after I reload the window. Non gpu lines show up correctly without the reload
Repository: ollama
Issue: Low GPU usage on second GPU
Labels: bug

### What is the issue?

I am on the 0.5.0 release (which links to 0.4.8-rc0) and using Qwen 2.5 32b Q5 with 32k context and flash attention with q8_0 KV cache.

I have a 3090 and 2080ti.

Ollama is putting 22GB on the 3090 and 5.3GB on the 2080ti.

When running a prompt the 3090 is at 80%-90% GPU usage while the 2080ti is only at 10%.

When using llama.cpp directly with split row, the VRAM on the 2080ti is mostly maxed and the GPU usage on both GPU is in the 50%-65% range.

----

My question: Why is the 3090 doing most of the work on Ollama?


### OS

Linux

### GPU

Nvidia

### CPU

AMD

### Ollama version

0.4.8-rc0
Repository: godot
Issue: Can't return typed arrays from C# functions to GDScript
Labels: bug,topic:dotnet

### Tested versions

Reproducible in 4.4dev5

### System information

Windows 10, Godot v4.4dev5

### Issue description

If I declare a function in C# like this:
```csharp
public Godot.Collections.Array<Vector2> GetCoolPlaces() {
    return new Godot.Collections.Array<Vector2>(... some values);
}
```

I would expect to be able to put the result into a typed array variable in GDScript:
```gdscript
var cool_places: Array[Vector2] = CSharpObject.GetCoolPlaces()
```

But the above code will result in this runtime error:
`Trying to assign an array of type "Array" to a variable of type "Array[Vector2i]".`

It is possible to do by creating a new typed array from the result of the function like this:
```gdscript
var cool_places: Array[Vector2] = Array(CSharpObject.GetCoolPlaces(), TYPE_VECTOR2, "", null)
```
But this is really clunky and annoying to do, especially when it's a function you use often.

Note: Packed arrays would not be a solution here, as this is also a problem for custom classes (e.g. Resources).

### Steps to reproduce

Create a function in C# that returns an array and try to put the result of that function into a typed array in GDScript. See MRP for example

### Minimal reproduction project (MRP)

Reproduce by running this project:

[CSharp Typed Arrays.zip](https://github.com/user-attachments/files/18029521/CSharp.Typed.Arrays.zip)
Repository: vscode
Issue: 1px gap to side of minimap lets code show through
Labels: bug,editor-minimap


Type: <b>Bug</b>

With word wrap off, there's about a 1px gap to the right side of the minimap that shows overflowing text  (see the couple of white bars on the right side of the minimap below)

![Image](https://github.com/user-attachments/assets/82b8834c-e010-4bd2-a729-1a15cfab5827)



VS Code version: Code - Insiders 1.96.0-insider (Universal) (6567c244f90af8e31d9250e8f9a757b58565649a, 2024-12-05T05:04:06.424Z)
OS version: Darwin arm64 24.1.0
Modes:

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

|Item|Value|
|---|---|
|CPUs|Apple M2 Max (12 x 2400)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|2, 3, 4|
|Memory (System)|64.00GB (1.43GB free)|
|Process Argv|--crash-reporter-id 0fffb5da-9cd7-46fd-9e7f-a1564e8c5fda|
|Screen Reader|no|
|VM|0%|
</details>
<!-- generated by issue reporter -->
Repository: vscode
Issue: Rules show over line numbers with gpu rendering 
Labels: bug,editor-gpu


Type: <b>Bug</b>

1. Enable gpu editor rendering
2. Disable word wrap
3. In a file with long lines, scroll horizontally until the ruler is on top of the line numbers

![Image](https://github.com/user-attachments/assets/dd6b27a0-6079-4d6d-8d89-7f934cbaf542)


VS Code version: Code - Insiders 1.96.0-insider (Universal) (6567c244f90af8e31d9250e8f9a757b58565649a, 2024-12-05T05:04:06.424Z)
OS version: Darwin arm64 24.1.0
Modes:

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

|Item|Value|
|---|---|
|CPUs|Apple M2 Max (12 x 2400)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|3, 3, 3|
|Memory (System)|64.00GB (0.97GB free)|
|Process Argv|--crash-reporter-id 0fffb5da-9cd7-46fd-9e7f-a1564e8c5fda|
|Screen Reader|no|
|VM|0%|
</details>
<!-- generated by issue reporter -->
Repository: pytorch
Issue: [3.13] Fix failing torch.package dynamo-wrapped test
Labels: oncall: package/deploy,module: python frontend

See https://github.com/pytorch/pytorch/pull/141886.

To repro: remove the skip and `PYTORCH_TEST_WITH_DYNAMO=1 pytest test/package/test_package_script.py -k test_save_shared_tensors`

cc @albanD
Repository: pytorch
Issue: [3.13] Fix failing module tracker dynamo-wrapped test due to recursion error
Labels: triaged,oncall: pt2,module: dynamo

See https://github.com/pytorch/pytorch/pull/141887.

Repro: remove skip and `PYTORCH_TEST_WITH_DYNAMO=1 pytest test/test_module_tracker.py -k test_confused_hierarchy`

Sample CI failure: https://hud.pytorch.org/pytorch/pytorch/pull/141264?sha=a486ca1f8486e1f092913e551e2e04ec0cb09956

cc @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @amjames
Repository: go
Issue: runtime: some possible SwissTable map benchmark improvements
Labels: NeedsInvestigation,compiler/runtime

The current runtime map benchmarks (imported from the CockroachDB SwissTable repo and used for recent runtime map work) have clearly been useful, especially for comparing the optimizations that have happened so far, but it might be worth tweaking those benchmarks.

For example, for the current benchmarks:

 1. Most might be overly friendly to the branch predictor with repetitive key patterns, especially at lower elem counts.
 2. Most of the elem sizes are power-of-two, which translates to a relatively low load factor and might not make the tables "sweat" as much as they would in practice.
 3. Most of the benchmarks use a mod operation in the benchmark code, which might be around 1/3 of the CPU time for the benchmarks that fit in cache. 
     * This is fine if someone has this in mind when comparing results, but might be cleaner without.
 4. Could probably benefit from some cold map cases (e.g., so many small or medium maps that they become cold) to better assess cache miss impact.
     * The original SwissTable folks and Folly F14 folks had collaborated on C++ benchmarks to help them compare approaches, with a sample of one of their cold map C++ benchmarks [here](https://github.com/google/hashtable-benchmarks/blob/e19019081ab6776de17f6ddff78c3cf628dc5c72/hashtable_benchmarks.cc#L379-L409).  (A couple of years ago, I had a WIP set of cold map Go benchmarks [here](https://github.com/thepudds/swisstable/blob/9c77dc657777eb8554d0a3d75bbb731f3364fa97/map_test.go#L1031), partially based on that).

Part of my immediate interest is the current benchmarks might not capture some of the benefits / costs of some adjustments to the current implementation, like:
  * Trying 16-element group sizes (instead of the current 8), or 
  * Alternative memory layouts (like putting all the control bytes for a single table together, rather than current interspersing of control bytes with the slots)

In particular, I have a draft change to the runtime SwissTable for 16-element group sizes (currently SWAR-only, not SIMD), but I suspect some of the benefit would be masked by the current benchmarks (maybe -- I don't know without tweaking the benchmarks 😅).
  
Separately, the benchmarks as they are might not be showing the advantages of the new implementation as clearly as they could compared to the old runtime map (including because "easier" benchmarks are probably making the prior map implementation look artificially better, vs. "easy" benchmarks not helping the SwissTable implementation as much).

----------

All that said, maybe some of those concerns don't matter in practice or maybe I'm mistaken.
  
Filing this issue to help with any discussion (including perhaps any feedback of "not worth it"). 

I plan on sending some benchmark CLs to attempt to improve or mitigate above issues.

CC @prattmic
Repository: flutter
Issue: Fix for custom shaders inside an Opacity widget might be too aggressive in some situations
Labels: engine,P3,team-engine,triaged-engine

https://github.com/flutter/engine/pull/56936 fixed a bug where use of custom shaders might ignore the opacity modulation of an Opacity widget.

Theoretically it might also disable an optimization for group opacity in some rare circumstances in parts of scenes in close proximity to code that uses a custom shader. No functional bug will result but we will lose an opportunity to maintain the performance advantage of group opacity optimizations in these uncommon situations.

The problem is that we mark a DisplayList layer as incompatible with group opacity when it has any rendering operations that were drawn while a RuntimeEffect color source or image filter was in play even if the indicated rendering operation does not use those rendering attributes. The test for RuntimeEffects in the DisplayListBuilder needs to check the attribute usage of each rendering operation as it makes the determination of whether or not it will break the group opacity peephole optimization rules.
Repository: TypeScript
Issue: Definitions have `.any()` instance and static methods on `AbortSignal` even though there is only a static method
Labels: Bug,Help Wanted,Domain: lib.d.ts

### 🔎 Search Terms

AbortSignal

### 🕗 Version & Regression Information

- This changed in commit or PR #58211


### ⏯ Playground Link

https://www.typescriptlang.org/play/?noImplicitReturns=false&noUncheckedIndexedAccess=true&allowUnreachableCode=true&allowUnusedLabels=true&noUnusedLocals=true&noUnusedParameters=true&declaration=false&target=99&jsx=0&module=0&strictBuiltinIteratorReturn=true&useUnknownInCatchVariables=true&exactOptionalPropertyTypes=true&noFallthroughCasesInSwitch=true&noImplicitOverride=true&noPropertyAccessFromIndexSignature=true&ts=5.7.2&filetype=ts#code/PTAEBcAsEsGdQLYFMoHsAmp2qfAdquKEgB5zgBQeSA7qAIIBGqATuAMrQDmeAhgDYAKAJQA6XngCeggNoBdYUA

### 💻 Code

```ts
// this method does not exist
new AbortSignal().any([])
```


### 🙁 Actual behavior

TypeScript doesn't give `Property 'any' does not exist on type 'AbortSignal'.(2339)`.

### 🙂 Expected behavior

TypeScript gives `Property 'any' does not exist on type 'AbortSignal'.(2339)`.

### Additional information about the issue

_No response_
Repository: pytorch
Issue: [3.13] Fix skipped numpy 2.0 dynamo-wrapped tests
Labels: module: tests,triaged,module: numpy,module: python frontend

Added skips in https://github.com/pytorch/pytorch/pull/141862 and https://github.com/pytorch/pytorch/pull/141950.

Logs for former failure: https://ossci-raw-job-status.s3.amazonaws.com/log/33781064111
Sample:
```
2024-12-02T11:02:07.7846581Z PRINTING LOG FILE of torch_np/numpy_tests/lib/test_function_base 1/1 (test/test-reports/torch_np.numpy_tests.lib.test_function_base_1.1_7c04d20bed56d027_.log)
2024-12-02T11:02:07.7847867Z Traceback (most recent call last):
2024-12-02T11:02:07.7848824Z   File "/var/lib/jenkins/workspace/test/torch_np/numpy_tests/lib/test_function_base.py", line 41, in <module>
2024-12-02T11:02:07.7850113Z     from numpy.lib import delete, extract, insert, msort, place, setxor1d, unwrap, vectorize
2024-12-02T11:02:07.7851588Z ImportError: cannot import name 'delete' from 'numpy.lib' (/opt/conda/envs/py_3.13/lib/python3.13/site-packages/numpy/lib/__init__.py)
2024-12-02T11:02:07.7852778Z Got exit code 1
2024-12-02T11:02:07.7853877Z No stepcurrent file found. Either pytest didn't get to run (e.g. import error) or file got deleted (contact dev infra)
2024-12-02T11:02:07.7854775Z 
2024-12-02T11:02:07.7855958Z FINISHED PRINTING LOG FILE of torch_np/numpy_tests/lib/test_function_base 1/1 (test/test-reports/torch_np.numpy_tests.lib.test_function_base_1.1_7c04d20bed56d027_.log)
2024-12-02T11:02:07.7857361Z 
2024-12-02T11:02:07.7857674Z torch_np/numpy_tests/lib/test_function_base 1/1 failed!
```

Logs for latter failure: https://hud.pytorch.org/pytorch/pytorch/pull/141264?sha=0b5977838f532164868d660cf11dbd762909d062

cc @mruberry @ZainRizvi @rgommers @albanD