sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: properly not working
Labels: info-needed,triage-needed


Type: <b>Bug</b>

work space is not working in this visual studio code


VS Code version: Code 1.96.4 (cd4ee3b1c348a13bafd8f9ad8060705f6d4b9cba, 2025-01-16T00:16:19.038Z)
OS version: Windows_NT x64 6.2.9200
Modes:

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

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i5-7300U CPU @ 2.60GHz (4 x 2712)|
|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>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|undefined|
|Memory (System)|7.88GB (1.42GB free)|
|Process Argv|--crash-reporter-id 678aba3c-fe94-4076-af47-bbf5e066d80f|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (29)</summary>

Extension|Author (truncated)|Version
---|---|---
python-debug-address-prompt|ale|1.0.1
prettier-vscode|esb|11.0.0
c-cpp-runner|fra|9.4.9
codespaces|Git|1.17.3
cpptask|kay|0.0.1
csdevkit|ms-|1.15.34
csharp|ms-|2.61.28
vscode-dotnet-runtime|ms-|2.2.5
debugpy|ms-|2024.14.0
python|ms-|2024.22.2
vscode-pylance|ms-|2024.12.1
jupyter|ms-|2024.11.0
jupyter-keymap|ms-|1.1.2
jupyter-renderers|ms-|1.0.21
vscode-jupyter-cell-tags|ms-|0.1.9
vscode-jupyter-slideshow|ms-|0.1.6
cmake-tools|ms-|1.19.52
cpptools|ms-|1.22.11
cpptools-extension-pack|ms-|1.3.0
powershell|ms-|2024.4.0
remote-explorer|ms-|0.4.3
remote-server|ms-|1.5.2
java|red|1.38.0
LiveServer|rit|5.7.9
cmake|twx|0.0.17
vscode-lldb|vad|1.11.1
vscode-gradle|vsc|3.16.2024111106
vscode-java-debug|vsc|0.58.1
vscode-java-test|vsc|0.43.0

(1 theme extensions excluded)

</details><details>
<summary>A/B Experiments</summary>

```
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
2i9eh265:30646982
962ge761:30959799
pythonnoceb:30805159
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
dvdeprecation:31068756
dwnewjupytercf:31046870
newcmakeconfigv2:31071590
nativerepl1:31139838
pythonrstrctxt:31112756
nativeloc2:31192216
cf971741:31144450
iacca1:31171482
notype1cf:31157160
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530
cf1a2727:31215809
6074i472:31201624
dwoutputs:31217127

```

</details>

<!-- generated by issue reporter -->
Repository: rust
Issue: Missing re-export of `FromCoroutine` in `core::iter` for `from_coroutine`
Labels: C-bug,T-libs

The `FromCoroutine` type returned by the unstable function `core::iter::from_coroutine` was not publicly re-exported in the `core::iter` module.
Repository: svelte
Issue: Cannot set properties of null (setting 'currentTime'), when transition
Labels: transition/animation

### Describe the bug

When playing audio HTML element with binded currentTime value becomes hidden with transition, the Svelte still tries to set the value of the now missing property (while animated), which results in an error Cannot set properties of null.

### Reproduction

Full example: [REPL](https://svelte.dev/playground/6b0bf9775fe64b0097f0fe18d5eee5ad?version=5.19.0)

Press play and then hide the player



### Logs

```shell

```

### System Info

```shell
Chrome 131
```

### Severity

annoyance
Repository: transformers
Issue: Defining LLM Dataset types in Trainers or during Training Workflow
Labels: Feature request

### Feature request

Hi, 
Just wondering if its possible to define a way to define the dataset input labels mapping argument in the transformers.Trainer or something similar? 

I understand that the input data labels are dependent on the type of training loss function used and problem for example, the type of defining attention mask ids for Mask learner vs Causal learners etc. Would also be extremely helpful if I can have suggestions on how I can check what dataset column labels the trainer/model will read? -- besides the `help(model.forward)` as this really just shows the model's inputs as it is into the learner. 

Any suggestions would be greatly appreciated! thanks!

### Motivation

This problem is giving me clinical depression 

### Your contribution

If there's any suggestions in solving this case, I would love to contribute
Repository: rust
Issue: Tracking issue for release notes of #133925: disallow `repr()` on invalid items
Labels: T-lang,relnotes,needs-triage,relnotes-tracking-issue


This issue tracks the release notes text for #133925.

### 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
# Category (e.g. Language, Compiler, Libraries, Compatibility notes, ...)
- [disallow `repr()` on invalid items](https://github.com/rust-lang/rust/pull/133925)
````

> [!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 @folkertdev, @compiler-errors -- origin issue/PR authors and assignees for starting to draft text
Repository: rust
Issue: Tracking issue for release notes of #133889: Consider fields to be inhabited if they are unstable
Labels: T-lang,relnotes,needs-triage,relnotes-tracking-issue


This issue tracks the release notes text for #133889.

### 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
# Category (e.g. Language, Compiler, Libraries, Compatibility notes, ...)
- [Consider fields to be inhabited if they are unstable](https://github.com/rust-lang/rust/pull/133889)
````

> [!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 @compiler-errors, @Nadrieril -- origin issue/PR authors and assignees for starting to draft text
Repository: angular
Issue: Add link to Language Service page from the Installation page
Labels: help wanted,good first issue,area: docs

### Describe the problem that you experienced

It would be helpful to have a blurb somewhere on the Installation page of the documentation with a recommendation to setup the Language Service extension and a link to that page of the documentation. For new Angular developers, this is the first place they will come to learn how to setup a new project and get going. The Language Service page is way further down in the documentation and a new developer could potentially spend a very long time without this critical editor extension until they finally stumble upon that page. This should be highlighted at the very start of their journey. 

### Enter the URL of the topic with the problem

https://angular.dev/installation

### Describe what you were looking for in the documentation

_No response_

### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

_No response_

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```

### Provide any additional information here in as much as detail as you can

```true

```
Repository: ui
Issue: [bug]: Github Button Link Hierarchy
Labels: bug

### Describe the bug

In the main website, when trying to press github button to go to the github, only the icon is clickable, the button iself isn't.

### Affected component/components

Button

### How to reproduce

1. Go to https://ui.shadcn.com
2. Try to click on Github link, not the icon.
![Image](https://github.com/user-attachments/assets/bb5fe3bf-2bf7-4245-bfc5-ea1e86da5986)

### Codesandbox/StackBlitz link

_No response_

### Logs

```bash

```

### System Info

```bash
-
```

### Before submitting

- [x] I've made research efforts and searched the documentation
- [x] I've searched for existing issues
Repository: rust
Issue: Tracking issue for release notes of #133951: Make the wasm_c_abi future compat warning a hard error
Labels: T-lang,relnotes,O-wasm,A-ABI,needs-triage,relnotes-tracking-issue


This issue tracks the release notes text for #133951.

### 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
# Category (e.g. Language, Compiler, Libraries, Compatibility notes, ...)
- [Make the wasm_c_abi future compat warning a hard error](https://github.com/rust-lang/rust/pull/133951)
````

> [!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 @bjorn3, @workingjubilee -- origin issue/PR authors and assignees for starting to draft text
Repository: rust
Issue: Tracking issue for release notes of #134276: fully de-stabilize all custom inner attributes
Labels: T-lang,relnotes,needs-triage,relnotes-tracking-issue


This issue tracks the release notes text for #134276.

### 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
- [stop accepting `#![test]` and `#![rustfmt::skip]` in more places than intended](https://github.com/rust-lang/rust/pull/134276)
````

> [!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 @RalfJung, @SparrowLii -- origin issue/PR authors and assignees for starting to draft text
Repository: rust
Issue: Tracking issue for release notes of #125087: Optimize `Seek::stream_len` impl for `File`
Labels: O-windows,relnotes,T-libs,O-unix,needs-triage,O-wasi,O-hermit,O-solid,relnotes-tracking-issue


This issue tracks the release notes text for #125087.

### 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
# Category (e.g. Language, Compiler, Libraries, Compatibility notes, ...)
- [Optimize `Seek::stream_len` impl for `File`](https://github.com/rust-lang/rust/pull/125087)
````

> [!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 @tbu-, @ChrisDenton -- origin issue/PR authors and assignees for starting to draft text
Repository: vscode
Issue: Allow scm.diffDecorationsGutterWidth to take values between 1 and 9, not just 1 and 5
Labels: feature-request,ux,scm

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
`scm.diffDecorationsGutterWidth` currently takes values between 1 and 5. 
I would like it to take values between 1 and 9 (I like my gutters **fat**).
Repository: rust
Issue: Tracking Issue for raw-dylib on ELF
Labels: T-compiler,C-tracking-issue

This is a tracking issue for raw-dylib on ELF (no RFC, extending [RFC 2627](https://rust-lang.github.io/rfcs/2627-raw-dylib-kind.html))
The feature gate for the issue is `#![feature(raw_dylib_elf)]`.

`raw-dylib` on ELF links against a generated stub shared object, allowing linking against libraries that are not present on the host system, for example for cross-compilation scenarios.

### About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however *not* meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
Discussion comments will get marked as off-topic or deleted.
Repeated discussions on the tracking issue may lead to the tracking issue getting locked.

### Steps
<!--
Include each step required to complete the feature. Typically this is a PR
implementing a feature, followed by a PR that stabilises the feature. However
for larger features an implementation could be broken up into multiple PRs.
-->

- [x] Initial implementation (#135695)
- [ ] Wider Testing
- [ ] Adjust documentation ([see instructions on rustc-dev-guide][doc-guide])
- [ ] Stabilization PR ([see instructions on rustc-dev-guide][stabilization-guide])

[stabilization-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#stabilization-pr
[doc-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#documentation-prs
[nightly-style-procedure]: https://github.com/rust-lang/style-team/blob/main/nightly-style-procedure.md 
[Style Guide]: https://github.com/rust-lang/rust/tree/master/src/doc/style-guide

### Unresolved Questions
<!--
Include any open questions that need to be answered before the feature can be
stabilised.
-->

- [ ] How to deal with symbol versioning?


### Implementation history

<!--
Include a list of all the PRs that were involved in implementing the feature.
-->

- Initial implementation: #135695
Repository: pytorch
Issue: The latest PyTorch XPU wheel 2.7.0.dev20250117+xpu does not work on Windows
Labels: module: binaries,module: windows,triaged,module: xpu

Steps:
```
# This installs 2.7.0.dev20250117+xpu
pip install torch --index-url https://download.pytorch.org/whl/nightly/xpu
python -c 'import torch;print(torch.__version__)'
```

Result:
```
OSError: [WinError 126] The specified module could not be found. Error loading "C:\.venv\lib\site-packages\torch\lib\shm.dll" or one of its dependencies.
```

The last known wheel that worked is `2.7.0.dev20250110+xpu`:

```
# This installs 2.7.0.dev20250110+xpu
pip install torch --index-url https://download.pytorch.org/whl/nightly/xpu
python -c 'import torch;print(torch.__version__)'
```

Result:
```
2.7.0.dev20250110+xpu
```

cc @seemethere @malfet @osalpekar @atalman @peterjc123 @mszhanyi @skyline75489 @nbcsm @iremyux @Blackhex @gujinghui @EikanWang @fengyuan14 @guangyey
Repository: rust
Issue: Type inference issues with well specified trait function call
Labels: A-diagnostics,T-compiler,A-inference,A-suggestion-diagnostics

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

While debugging a recent build failure in diesel I noticed that type inference fails in situation where the type is fully specified. I've build the following minimal example for this:

```rust
#[derive(Debug)]
struct Error;

trait FromSql<ST, DB>: Sized {
    fn from_sql(bytes: &[u8]) -> Result<Self, Error>;
}

struct UuidST;
struct Integer;
struct Pg;

#[derive(Debug, PartialEq)]
struct Uuid;

struct OtherType;

// remove this rather unrelated impl to fix the compilation
impl PartialEq<OtherType> for Uuid {
    fn eq(&self, other: &OtherType) -> bool {
        false
    }
}


impl FromSql<UuidST, Pg> for Uuid {
    fn from_sql(bytes: &[u8]) -> Result<Self, Error> {
        todo!()
    }
}

impl FromSql<Integer, Pg> for i32 {
    fn from_sql(bytes: &[u8]) -> Result<Self, Error> {
        todo!()
    }
}

fn main() {
    let input = &[];
    
    let out = FromSql::<UuidST, Pg>::from_sql(input).unwrap();

    assert_eq!(Uuid, out);
}

```

This fails to compile with the following error:

```
error[[E0790]](https://doc.rust-lang.org/nightly/error_codes/E0790.html): cannot call associated function on trait without specifying the corresponding `impl` type
  --> src/main.rs:43:15
   |
7  |     fn from_sql(bytes: &[u8]) -> Result<Self, Error>;
   |     ------------------------------------------------- `FromSql::from_sql` defined here
...
43 |     let out = FromSql::<UuidST, Pg>::from_sql(input).unwrap();
   |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ cannot call associated function of trait
   |
help: use a fully-qualified path to one of the available implementations
   |
43 -     let out = FromSql::<UuidST, Pg>::from_sql(input).unwrap();
43 +     let out = <Uuid as FromSql<UuidST, Pg>>::from_sql(input).unwrap();
   |
43 -     let out = FromSql::<UuidST, Pg>::from_sql(input).unwrap();
43 +     let out = <i32 as FromSql<UuidST, Pg>>::from_sql(input).unwrap();
   |
```

This seems to be caused by the additional `PartialEq` implementation that breaks inferring the type of the `out` variable. For me it looks strange that rustc cannot infer that there is only a single possible impl that fulfills the given constraints, so it should be possible to infer the correct type here.

(Also even if that's desired behavior the suggestion is definitively off, as the second variant (that with `i32 as FromSql<UuidST, Pg>` would result in a compilation error.

Playground: https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=1a20f58b8678382f922f0006217bbf60

Related:  https://github.com/uuid-rs/uuid/issues/787


`rustc --version --verbose`:
```
Build using the Nightly version: 1.86.0-nightly

(2025-01-17 6067b36314ab5eb2eb47)
```
Repository: next.js
Issue: dynamic route, dynamicIO, mdx, notFound => NEXT_HTTP_ERROR_FALLBACK;404
Labels: TypeScript,Turbopack,Markdown (MDX),dynamicIO

### Link to the code that reproduces this issue

https://github.com/volfadar/next-bug

### To Reproduce

1. bun install
2. bun dev
3. go to "http://localhost:3000/lecture/marketing/intro"

### Current vs. Expected behavior

Simply, it should not throw an error `NEXT_HTTP_ERROR_FALLBACK;404` because I already have a `not-found.tsx`.

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Home Single Language
  Available memory (MB): 16087
  Available CPU cores: 8
Binaries:
  Node: 20.11.1
  npm: 10.2.4
  Yarn: 1.22.22
  pnpm: 9.0.2
Relevant Packages:
  next: 15.2.0-canary.15 // Latest available version is detected (15.2.0-canary.15).
  eslint-config-next: N/A
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.7.3
Next.js Config:
  output: N/A
```

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

dynamicIO, Turbopack, TypeScript, Markdown (MDX)

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

next dev (local)

### Additional context

_No response_
Repository: transformers
Issue: Issue: Error with _eos_token_tensor when using Generator with GenerationMixin
Labels: bug

### System Info

e-readability-summarization/src/inference$ python run_2.py 
Traceback (most recent call last):
  File "/home/surenoobster/Documents/project/src/inference/run_2.py", line 87, in <module>
    output = generator.generate(
             ^^^^^^^^^^^^^^^^^^^
  File "/home/surenoobster/anaconda3/lib/python3.12/site-packages/torch/utils/_contextlib.py", line 116, in decorate_context
    return func(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/home/surenoobster/Documents/project/src/inference/generation_2.py", line 572, in generate
    stopping_criteria = self.model._get_stopping_criteria(
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/surenoobster/anaconda3/lib/python3.12/site-packages/transformers/generation/utils.py", line 1126, in _get_stopping_criteria
    if generation_config._eos_token_tensor is not None:
       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'GenerationConfig' object has no attribute '_eos_token_tensor'

### Who can help?

_No response_

### Information

- [ ] The official example scripts
- [x] My own modified scripts

### Tasks

- [ ] An officially supported task in the `examples` folder (such as GLUE/SQuAD, ...)
- [ ] My own task or dataset (give details below)

### Reproduction

I'm not able to get it , getting problem with device

### Expected behavior

The Generator should initialize the required token tensors correctly to ensure compatibility with GenerationMixin and avoid errors.