sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Web export renders 1px wide textures completely black.
Labels: bug,topic:rendering,needs testing,topic:3d

### Tested versions

- Reproducible in v4.3.stable.steam [77dcf97d8]
(Unable to immediately test older versions)

### System information

Windows 10 - v4.3.stable.steam [77dcf97d8] - Replicates on OpenGL

### Issue description

If you set a StandardMaterial3D's texture to a 1 pixel thin texture and apply it to a mesh, it will render the mesh's material as completely black when playing via web.

**In Editor as a single pixel thin texture:**
![image](https://github.com/user-attachments/assets/803e00bb-d268-4ef9-8c2d-d7aea1fb7bbc)

**In Desktop debug (Windows):**
![image](https://github.com/user-attachments/assets/8df6b094-8754-4830-be1c-2e06319022b5)

**In web debug (Waterfox, but has been tested on Chrome, Edge, Firefox, etc, same result):**
![image](https://github.com/user-attachments/assets/5284b866-708d-4576-a9e0-f7ae85ee2ab7)


### Steps to reproduce

- Create a StandardMaterial3D
- I set it to shading mode unshaded, but even if lit, it shows up as a slight dark grey/black.
- Apply 1px wide texture

### Minimal reproduction project (MRP)

[minimal-reproduction-project.zip](https://github.com/user-attachments/files/17992757/minimal-reproduction-project.zip)
Repository: godot
Issue: Using built-in feature tags as custom feature tags can cause bugs
Labels: bug,topic:export

### Tested versions

v4.3.stable.official [77dcf97d8]

### System information

Godot v4.3.stable - Windows 10.0.22631 - GLES3 (Compatibility) - NVIDIA GeForce GTX 980 Ti (NVIDIA; 32.0.15.6603) - 13th Gen Intel(R) Core(TM) i7-13700K (24 Threads)

### Issue description

It seems that using some built-in feature tags as custom feature tags can cause bugs. As an example, using the `web` custom feature tag on Windows exports causes audio playback to stop working.

This problem also occurs when using the "Customize Run Instances..." feature. By setting the `web` custom feature tag in this window, audio playback will stop working in these instances.

I believe that an error should be presented any time the user attempts to use a built-in feature tag as a custom feature in either an export preset or a run instance.

### Steps to reproduce

1. Create a project that plays audio.
2. Create a new Windows Export preset.
3. Add "web" as a custom feature.
4. Export the game for Windows and note that audio no longer plays.

### Minimal reproduction project (MRP)

[web feature tag bug.zip](https://github.com/user-attachments/files/17803933/web.feature.tag.bug.zip)
Repository: flutter
Issue: FlutterTexture should provide timestamp and duration or targetTimestamp
Labels: c: new feature,engine,c: proposal,P3,team-engine,triaged-engine

### Use case

Time obtained for example from `CACurrentMediaTime` in `copyPixelBuffer` is irregular because this function is not called at exact time intervals. This irregularity then may be transferred into animation or video sampling leading to choppy animation or dropping frames (as now happens with `video_player` plugin). Currently there is used [this workaround](https://github.com/misos1/packages/blob/24002603a885533831cd343624aab5df2639e933/packages/video_player/video_player_avfoundation/darwin/video_player_avfoundation/Sources/video_player_avfoundation/FVPVideoPlayerPlugin.m#L571-L575) in https://github.com/flutter/packages/pull/7466.

### Proposal

`FlutterTexture` should provide `timestamp` and `duration` or `timestamp` and `targetTimestamp` of the display link (or all 3).
Repository: TypeScript
Issue: .module.scss.d.ts F12 does not direct to .scss.
Labels: Bug,Help Wanted

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
Version: 1.95.1 (system setup)
Commit: 65edc4939843c90c34d61f4ce11704f09d3e5cb6
Date: 2024-10-31T05:14:54.222Z
Electron: 32.2.1
ElectronBuildId: 10427718
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.20348

Steps to Reproduce:

1. Enable both javascript.preferGoToSourceDefinition and typescript.preferGoToSourceDefinition
2. Have a vite project with sassDts enabled.
3. Have a My.module.scss with a class .myClass
4. Have a file My.js
5. Have the line ```import styles from "./My.module.scss";```
6. sassDts generates a .d.ts file for the My.module.scss, called My.module.scss.d.ts
7. In My.js, add ```styles.myClass```
8. Hit F12
9. The definitions popup now opens the .d.ts by default, which is useless. It should've opened the .scss file (which it also suggests, but there's no way to make this the default).
Repository: pytorch
Issue: Better Error Message for SymIntArrayRef expected to contain only concrete integers
Labels: triaged,oncall: pt2,module: dynamic shapes

### 🐛 Describe the bug

Recently it took multiple people and many suggestions to debug why we were getting `SymIntArrayRef expected to contain only concrete integers` error. 

The common reasons are:

- FakeTensorMode not enabled
- Op doesn't support symints
- Pydispatcher not enabled - related to above ^.

We should augment the error message to be more informative and potentially diagnose which of the above it is.

cc @ezyang @chauhang @penguinwu @bobrenjc93 @youkaichao 

### Versions

master
Repository: kubernetes
Issue: Native histogram support for Kubernetes metrics
Labels: kind/feature,sig/instrumentation,triage/accepted

### What would you like to be added?

Following up on the [slack thread](https://kubernetes.slack.com/archives/C0EG7JC6T/p1731346401543199), creating this placeholder issue to add support for instrumenting native histograms in Kubernetes metrics.

### Why is this needed?

[Native histograms](https://prometheus.io/docs/prometheus/latest/feature_flags/#native-histograms) were added to Prometheus that have some nice features around having dynamic bucketing for histograms, reduced cardinality to name a few.

Following are some considerations we should keep in mind when working on native histogram support for K8s metrics (ensure we continue to support both classic histograms meanwhile). As of today, native histograms 
- is still an experimental feature in Prom 
- only supports Prom protobuf exposition format
Repository: PowerToys
Issue: Audio Relay type Feature
Labels: Needs-Triage

### Description of the new feature / enhancement

The new feature should be like the Audio Relay application which transfers audio from one device to the other. It would be nice to have it in Power Toys like an all in one bundle type thing. 

### Scenario when this would be used?

You would use this when you have multiple desktops and want to use one pair of headphones to listen to the audio on either desktop. It would be nice if it could support more than just two desktops like Audio Relay does though.

### Supporting information

This is the site of the application I use currently for the audio feature: https://audiorelay.net/
Repository: pytorch
Issue: xpu: implement aten::_linalg_eigvals for XPU backend (affecting HF Transformers v4.46.0 and later)
Labels: triaged,enhancement,module: xpu

Recent changes in Huggingface Transformers (https://github.com/huggingface/transformers/commit/cdee5285cade176631f4f2ed3193a0ff57132d8b and https://github.com/huggingface/transformers/commit/4a3f1a686fcda27efc19b8b3a87b62a338c2ad86) introduced usage of `torch.linalg.eigvals()` which is not implemented for XPU backend (missing `aten::_linalg_eigvals`) and it's not registered for automated CPU fallback as well. To use this operator with XPU you need to use `PYTORCH_ENABLE_XPU_FALLBACK=1`. Transformers version v4.46.0 and later are affected. Can this operator, please, be added?

- [ ] `aten::_linalg_eigvals`

With:
* https://github.com/huggingface/transformers/commit/e80a65ba4fbbf085fda2cf0fdb0e8d48785979c8
* https://github.com/huggingface/accelerate/commit/8ade23cc6aec7c3bd3d80fef6378cafaade75bbe
* https://github.com/pytorch/pytorch/commit/e429a3b72e787ddcc26ee2ba177643c9177bab24

Can be reproduced running Huggingface Transformers tests for a number of models (such as albert, mpt, gemma2). Here is example for one of the model:
```
$ cat spec.py
import torch
DEVICE_NAME = 'xpu'
MANUAL_SEED_FN = torch.xpu.manual_seed
EMPTY_CACHE_FN = torch.xpu.empty_cache
DEVICE_COUNT_FN = torch.xpu.device_count

$ TRANSFORMERS_TEST_DEVICE_SPEC=spec.py python3 -m pytest --pspec \
  tests/models/albert/test_modeling_albert.py::AlbertModelTest::test_resize_embeddings_untied \
  tests/models/albert/test_modeling_albert.py::AlbertModelTest::test_resize_tokens_embeddings
```

CC: @gujinghui @EikanWang @fengyuan14 @guangyey @jgong5


cc @gujinghui @EikanWang @fengyuan14 @guangyey
Repository: go
Issue: x/tools/gopls/internal/cache/methodsets: "can't find path for func" panic in indexBuilder.build (no object path for method)
Labels: gopls,Tools,gopls/telemetry-wins

```
#!stacks
"runtime.gopanic" && "methodsets.(*indexBuilder).build.func2:+12" ||
 "bug.Reportf" && "(*indexBuilder).build.func2:+32"
```


Issue created by [stacks](https://pkg.go.dev/golang.org/x/tools/gopls/internal/telemetry/cmd/stacks).
```go
		// Instantiations of generic methods don't have an
		// object path, so we use the generic.
		if p, err := objectpathFor(method.Origin()); err != nil {
			panic(err) // can't happen for a method of a package-level type
		} else {
			m.ObjectPath = b.string(string(p))
		}
```

First stack is [here](https://github.com/golang/go/issues/70418#issuecomment-2486096416).


gopls version: v0.17.0-pre.2/go1.23.2
gopls flags: 
update flags: proxy
extension version: 0.42.1
environment: Cursor darwin
initialization error: undefined
issue timestamp: Sat, 16 Nov 2024 15:11:16 GMT
restart history:
Sat, 16 Nov 2024 15:10:59 GMT: activation (enabled: true)

<details><summary>gopls stats -anon</summary>
{
  "DirStats": {
    "Files": 5774,
    "TestdataFiles": 216,
    "GoFiles": 960,
    "ModFiles": 1,
    "Dirs": 516
  },
  "GOARCH": "arm64",
  "GOOS": "darwin",
  "GOPACKAGESDRIVER": "",
  "GOPLSCACHE": "",
  "GoVersion": "go1.23.2",
  "GoplsVersion": "v0.17.0-pre.2",
  "InitialWorkspaceLoadDuration": "1.603257166s",
  "MemStats": {
    "HeapAlloc": 318890328,
    "HeapInUse": 434987008,
    "TotalAlloc": 1358687472
  },
  "WorkspaceStats": {
    "Files": {
      "Total": 9784,
      "Largest": 4950165,
      "Errs": 0
    },
    "Views": [
      {
        "GoCommandVersion": "go1.23.2",
        "AllPackages": {
          "Packages": 2191,
          "LargestPackage": 159,
          "CompiledGoFiles": 10309,
          "Modules": 322
        },
        "WorkspacePackages": {
          "Packages": 199,
          "LargestPackage": 54,
          "CompiledGoFiles": 1185,
          "Modules": 1
        },
        "Diagnostics": 0
      }
    ]
  }
}

</details>
Dups: yJIbcA 9nLJcw
Repository: svelte
Issue: Legacy #await problem
Labels: bug

### Describe the bug

Await block unexpectedly evaluates expression upon state changes in legacy mode.
Expected behavior is to only have the expression evaluated when its variables change.

### Reproduction

https://svelte.dev/playground/53cc8a72175c41c6bebb2bbb75d069a7?version=5.2.3

### Logs

_No response_

### System Info

```shell
System:
    OS: Windows 10 10.0.19045
    CPU: (16) x64 Intel(R) Xeon(R) CPU E5-2680 v4 @ 2.40GHz
    Memory: 9.01 GB / 25.53 GB
  Binaries:
    Node: 18.12.1 - C:\Program Files\nodejs\node.EXE
    npm: 9.1.3 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Chromium (130.0.2849.80)
    Internet Explorer: 11.0.19041.4355
  npmPackages:
    rollup: ^4.22.4 => 4.27.3
    svelte: ^5.1.6 => 5.2.3
```


### Severity

blocking an upgrade
Repository: transformers
Issue: Export to ExecuTorch with Quantization
Labels: Feature request,ExecuTorch

### Feature request

This task is to experiment running quantized HuggingFace models with ExecuTorch out-of-the-box.

The heavy-lifting quantization work will be done through [`quantize_`](https://github.com/pytorch/ao/blob/main/torchao/quantization/quant_api.py#L94) API by [`torchao`](https://github.com/pytorch/ao), for example `quantize_(model, int4_weight_only())`.

The quantization API can be integrated with the integration points to executorch `transformers.integrations.executorch`, expanding the export workflow with a new option of "exporting with quantization". In eager, users can verify the numerics accuracy of the quantized exported artifact, e.g. the script for eval llama ([here](https://github.com/pytorch/ao/blob/main/torchao/_models/llama/eval.py)). In ExecuTorch, users can just load the quantized `.pte` files to ExecuTorch runner for inference.



### Motivation

Experiment quantization workflow w/ `transforms` + `torchao` + `executorch`

### Your contribution

Direct contribution, or provide guidance to anyone who is interested in this work
Repository: pytorch
Issue: `torch._inductor.cpu_vec_isa.pick_vec_isa` takes ~9 seconds to run
Labels: module: cpu,triaged,oncall: pt2,module: inductor,oncall: cpu inductor

I noticed that when compiling a small microbenchmark (with inductor warm caching), E2E compile times were ~4s with cuda tensors and ~15s with cpu tensors. It looks like the majority of the extra time for cpu is spent when inductor runs `pick_vec_isa`:
```
import torch
from torch._inductor.cpu_vec_isa import pick_vec_isa
import time

start = time.time()
out = pick_vec_isa()
end = time.time()
# 9.106s on my machine
print(end - start)
```

cc @jgong5 @mingfeima @XiaobingSuper @sanchitintel @ashokei @jingxu10 @chauhang @penguinwu @voznesenskym @EikanWang @Guobing-Chen @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire @aakhundov @ezyang @gchanan @zou3519 @msaroufim
Repository: transformers
Issue: Add `Tensor Parallel` support for ALL models
Labels: Feature request,Tensor Parallel,Good Difficult Issue

Just opening this to add support for all models following #34184

Lets bring support to all model! 🤗 

- [x] Llama

It would be great to add the support for more architectures such as
- [ ] Qwen2
- [ ] QwenVl
- [ ] Mistral
- [ ] Llava


... and many more

For anyone who wants to contribute just open a PR and link it to this issue, and ping me for a review!! 🤗
Repository: PowerToys
Issue: Specific Configrurations on Startup
Labels: Needs-Triage

### Description of the new feature / enhancement

How cool would it be to have specific utilities automatically run at startup! With all bells and whistles enabled I feel, this op might be a little resource intensive, so this configuration makes more sense.

### Scenario when this would be used?

At Startup!

### Supporting information

Fun rant: I asked ChatGPT if it was possible to enable only a specific set of util at startup with Powertoys. it said no — but also suggested forwarding the idea to the team, as they actively accept feature requests.
Repository: vscode
Issue: Calling openNotebookDocument with hidden notebook URI creates another untitled*.ipynb with same URI
Labels: bug,notebook

Investigated from: https://github.com/microsoft/vscode-python/pull/24148#pullrequestreview-2443313565 
In the reloading of notebook document such as native REPL, calling 
```
 await workspace.openNotebookDocument(mementoValue as Uri);
```
works fine if the notebook document is visible.

Problem happens when user hide their notebook document (such as native REPL) hiding behind some untitled text file, and then calling 
```
 await workspace.openNotebookDocument(mementoValue as Uri);
```
will create another instance of untitled.ipynb with the same exact URI as the notebook that was hidden.

https://github.com/user-attachments/assets/75e93dcc-ccc5-46ef-b4c8-d824bfc3fdbe
Repository: go
Issue: runtime: deprecate SetFinalizer
Labels: NeedsFix,compiler/runtime

The original intent of proposal #67535 included the deprecation of SetFinalizer. While the proposal is approved and the implementation has landed in the tree, we feel less [comfortable](https://go-review.googlesource.com/c/go/+/629215/comment/915b4be1_5b9fd51d/) with deprecating SetFinalizer in the same release as the addition of AddCleanup. Notibly, the lack of a trivial migration from SetFinalizer to AddCleanup was an issue that was mentioned. This issue intends to track the deprecation of SetFinalizer in a future release of Go and the discussion surrounding it.

@mknyszek @cagedmantis @ianlancetaylor
Repository: go
Issue: cmd/go: TestScript/cover_sync_atomic_import failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "cmd/go" && test == "TestScript/cover_sync_atomic_import"
```

Issue created automatically to collect these failures.

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

    === RUN   TestScript/cover_sync_atomic_import
    === PAUSE TestScript/cover_sync_atomic_import
    === CONT  TestScript/cover_sync_atomic_import
        script_test.go:139: 2024-11-18T20:54:46Z
        script_test.go:141: $WORK=/home/swarming/.swarming/w/ir/x/t/cmd-go-test-727923194/tmpdir1021279256/cover_sync_atomic_import3372092879
        script_test.go:163: 
            PATH=/home/swarming/.swarming/w/ir/x/t/cmd-go-test-727923194/tmpdir1021279256/testbin:/home/swarming/.swarming/w/ir/x/w/goroot/bin:/home/swarming/.swarming/w/ir/x/w/goroot/bin:/home/swarming/.swarming/w/ir/x/w/goroot/bin:/home/swarming/.swarming/w/ir/cache/tools/bin:/home/swarming/.swarming/w/ir/bbagent_utility_packages:/home/swarming/.swarming/w/ir/bbagent_utility_packages/bin:/home/swarming/.swarming/w/ir/cipd_bin_packages:/home/swarming/.swarming/w/ir/cipd_bin_packages/bin:/home/swarming/.swarming/w/ir/cipd_bin_packages/cpython3:/home/swarming/.swarming/w/ir/cipd_bin_packages/cpython3/bin:/home/swarming/.swarming/w/ir/cache/cipd_client:/home/swarming/.swarming/w/ir/cache/cipd_client/bin:/home/swarming/.swarming/cipd_cache/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
            HOME=/no-home
            CCACHE_DISABLE=1
            GOARCH=amd64
    ...
            [stdout]
            ok  	sync/atomic	1.032s	coverage: 23.3% of statements
            > go test -short -cover -race -run=TestAnd8 internal/runtime/atomic
            [stdout]
            PASS
            error generating coverage report: processing counter data file /home/swarming/.swarming/w/ir/x/t/cmd-go-test-727923194/tmpdir1021279256/cover_sync_atomic_import3372092879/tmp/go-build3209127363/b001/gocoverdir/covcounters.f3aa8210249b3824780256cba1210f3b.419336.1731963357691381105: merging counters: len(dst)=4 len(src)=1
            FAIL	internal/runtime/atomic	0.044s
            FAIL
        script_test.go:163: FAIL: testdata/script/cover_sync_atomic_import.txt:20: go test -short -cover -race -run=TestAnd8 internal/runtime/atomic: exit status 1
    --- FAIL: TestScript/cover_sync_atomic_import (71.48s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: cmd/go: TestScript/test_fuzz_mutate_crash failures [consistent failure]
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "cmd/go" && test == "TestScript/test_fuzz_mutate_crash"
```

Issue created automatically to collect these failures.

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

    === RUN   TestScript/test_fuzz_mutate_crash
    === PAUSE TestScript/test_fuzz_mutate_crash
    === CONT  TestScript/test_fuzz_mutate_crash
        script_test.go:139: 2024-11-18T20:59:01Z
        script_test.go:141: $WORK=/home/swarming/.swarming/w/ir/x/t/cmd-go-test-1534623394/tmpdir4130087195/test_fuzz_mutate_crash1035018309
        script_test.go:163: 
            PATH=/home/swarming/.swarming/w/ir/x/t/cmd-go-test-1534623394/tmpdir4130087195/testbin:/home/swarming/.swarming/w/ir/x/w/goroot/bin:/home/swarming/.swarming/w/ir/x/w/goroot/bin:/home/swarming/.swarming/w/ir/x/w/goroot/bin:/home/swarming/.swarming/w/ir/cache/tools/bin:/home/swarming/.swarming/w/ir/bbagent_utility_packages:/home/swarming/.swarming/w/ir/bbagent_utility_packages/bin:/home/swarming/.swarming/w/ir/cipd_bin_packages:/home/swarming/.swarming/w/ir/cipd_bin_packages/bin:/home/swarming/.swarming/w/ir/cipd_bin_packages/cpython3:/home/swarming/.swarming/w/ir/cipd_bin_packages/cpython3/bin:/home/swarming/.swarming/w/ir/cache/cipd_client:/home/swarming/.swarming/w/ir/cache/cipd_client/bin:/home/swarming/.swarming/cipd_cache/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
            HOME=/no-home
            CCACHE_DISABLE=1
            GOARCH=amd64
    ...
            --- FAIL: FuzzWithBug (0.58s)
                --- FAIL: FuzzWithBug (0.00s)
                    testing.go:1665: panic: this input caused a crash!
                        goroutine 38 [running]:
                        runtime/debug.Stack()
                        	/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/debug/stack.go:26 +0x9b
                        testing.tRunner.func1()
                        	/home/swarming/.swarming/w/ir/x/w/goroot/src/testing/testing.go:1665 +0x1c8
                        panic({0x60eb00?, 0x695d10?})
                        	/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/panic.go:787 +0x132
    ...
            # Running the fuzzer should find a crashing input quickly for fuzzing two types. (2.023s)
            > ! go test -run=FuzzWithTwoTypes -fuzz=FuzzWithTwoTypes -fuzztime=100x -fuzzminimizetime=1000x
            [stdout]
            warning: starting with empty corpus
            fuzz: elapsed: 0s, execs: 0 (0/sec), new interesting: 0 (total: 0)
            fuzz: elapsed: 0s, execs: 111 (494/sec), new interesting: 1 (total: 1)
            PASS
            ok  	m	0.292s
        script_test.go:163: FAIL: testdata/script/test_fuzz_mutate_crash.txt:67: go test -run=FuzzWithTwoTypes -fuzz=FuzzWithTwoTypes -fuzztime=100x -fuzzminimizetime=1000x: unexpected success
    --- FAIL: TestScript/test_fuzz_mutate_crash (130.46s)


— [watchflakes](https://go.dev/wiki/Watchflakes)