sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: transformers
Issue: More rich documentation on pipelines
Labels: Feature request

### Feature request

For instance, in the case of pipelines, there are merely some community examples such as automatic-speech-recognition. There is no indication of who constitutes it or how the Voice Activity Detection (VAD) is involved. As a result, users are perplexed.

### Motivation

More detailed descriptions on pipline details.

### Your contribution

currently not
Repository: rust
Issue: Split `run-make` into two test suites: fast-path that don't need to build cargo/rustdoc and a slow-path that requires these tools
Labels: A-testsuite,E-hard,C-enhancement,T-bootstrap,A-compiletest,A-run-make,A-test-infra

Building stage 1 cargo and rustdoc takes quite a bit of time and is annoying if your run-make test doesn't even need cargo/rustdoc. Building stage 1 cargo for tests that do need cargo is actually necessary because beta cargo (the usual bootstrap cargo) might not have changes that are present in nightly cargo.
Repository: rust
Issue: compiletest: inconsistent and inconvenient ways to request verbose test output
Labels: A-testsuite,E-hard,T-bootstrap,C-bug,A-compiletest,A-test-infra,E-needs-investigation

compiletest has some strange `--nocapture` (which is a libtest thing) support for `ui` tests but inconsistently for other test suites. `crashes` test suite uses an env var `COMPILETEST_VERBOSE_CRASHES=1` to unhide the crashes test failure output. `run-make` test suite has multiple layer of hiding going on.

There's also the bootstrap verbose/verbose tests -> compiletest handling.
Repository: vscode
Issue: Disable inline completions when composing via an IME (Input Method Editor)
Labels: editor-input-IME,inline-completions

<!-- ⚠️⚠️ 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. -->
I would like inline completions to be disabled when composing characters via an IME. The completions given at those moments are not super useful as the characters typed in are intermediate and would just be replaced after selection. It would greatly reduce distractions while using GitHub Copilot or extensions alike, especially for users who usually code in multiple languages using IMEs.

Here is an example of me receiving unhelpful inline completions while composing Chinese characters via an IME:
![Image](https://github.com/user-attachments/assets/9dfb3a15-f257-4dd4-a129-4d303b2062d0)

As far as I know, the input event is not exposed to extension developers, so it would be hard for them to know when to stop providing completion results. Feel like here is the right place to ask.
Repository: tensorflow
Issue: ValueError: as_list() is not defined on an unknown TensorShape.
Labels: type:support,TF 2.18

### Issue type

Support

### Have you reproduced the bug with TensorFlow Nightly?

No

### Source

source

### TensorFlow version

2.18.0

### Custom code

Yes

### OS platform and distribution

Ubuntu 20.04.6 LTS

### Mobile device

_No response_

### Python version

3.11

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

The created dataset's <class 'tensorflow.python.data.ops.prefetch_op._PrefetchDataset'> shape is unknown.
which when used for model.evaluate results in error:

```
self.model.evaluate(self.data_loader.get_valid_loader(batch_size), verbose=1)
  File "/home/perfuser/shailesh/9_dec/lib/python3.11/site-packages/keras/src/utils/traceback_utils.py", line 122, in error_handler
    raise e.with_traceback(filtered_tb) from None
  File "/home/perfuser/shailesh/9_dec/lib/python3.11/site-packages/keras/src/utils/traceback_utils.py", line 122, in error_handler
    raise e.with_traceback(filtered_tb) from None
    ^^^^^^^^^^^^^^^
ValueError: as_list() is not defined on an unknown TensorShape.
```
Apologies for sharing partial code.
My question is: how can I set the shape of  tensorflow.python.data.ops.prefetch_op._PrefetchDataset dataset, or what is the solution to resolve the issue "as_list() is not defined on an unknown TensorShape"?

The same dataset with an unknown shape worked with TensorFlow 2.13.

### Standalone code to reproduce the issue

```shell
ds_val = ds_val.map(lambda x: tf.py_function(self.read_nifti_file,
                                                     [x, False], [tf.float32, tf.float32]),
                            num_parallel_calls=tf.data.experimental.AUTOTUNE)
self.model.evaluate(self.data_loader.get_valid_loader(batch_size), verbose=1)
```
```


### Relevant log output

```shell
ds_val 3 <_PrefetchDataset element_spec=(TensorSpec(shape=<unknown>, dtype=tf.float32, name=None), TensorSpec(shape=<unknown>, dtype=tf.float32, name=None))>

type(ds_val) <class 'tensorflow.python.data.ops.prefetch_op._PrefetchDataset'>
type(ds) <class 'tuple'>
shape(ds) (2, 64, 64, 64, 1)
type(ds) <class 'tuple'>
shape(ds) (2, 64, 64, 64, 1)
type(ds) <class 'tuple'>
shape(ds) (2, 64, 64, 64, 1)
type(ds) <class 'tuple'>
shape(ds) (2, 64, 64, 64, 1)
type(ds) <class 'tuple'>
shape(ds) (2, 64, 64, 64, 1)
type(ds) <class 'tuple'>
shape(ds) (2, 64, 64, 64, 1)
type(ds) <class 'tuple'>
shape(ds) (2, 64, 64, 64, 1)
type(ds) <class 'tuple'>
shape(ds) (2, 64, 64, 64, 1)
type(ds) <class 'tuple'>
shape(ds) (2, 64, 64, 64, 1)
```
Repository: ant-design
Issue: Spin组件fullscreen模式下wrapperClassName属性不生效
Labels: Inactive

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/p/sandbox/antd-reproduction-template-forked-7z7zfx?file=%2Findex.tsx)

### Steps to reproduce

Spin组件添加fullscreen和wrapperClassName属性

### What is expected?

wrapperClassName属性生效，spin外层元素有自定义类名

### What is actually happening?

wrapperClassName属性未生效

| Environment | Info |
| --- | --- |
| antd | 5.22.3 |
| React | 18.0.0 |
| System | macos14.5 |
| Browser | chrome |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: deno
Issue: Allow expanding the types displayed on hover
Labels: feat,lsp

When hovering over a complex type, it's usually hard to read. It would be cool to be able to expand the types manually in order to see the final computed type.

This would upstream the changes in https://github.com/microsoft/vscode/issues/94679#issuecomment-2529656036 and therefore requires TS 5.7.
Repository: ant-design
Issue: 手机端H5使用Select 组件，设置allowClear之后，由于手机端没有hover事件，需要点击才能看到清除图标。此场景有合适的方案吗，比如选择框有值的时候，就展示清除图标。
Labels: Inactive,📱Mobile Device

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io)

### Steps to reproduce

手机端H5使用

### What is expected?

手机端H5使用Select 组件，设置allowClear之后，由于手机端没有hover事件，需要点击才能看到清除图标。此场景有合适的方案吗，比如选择框有值的时候，就展示清除图标。

### What is actually happening?

手机端H5使用Select 组件，设置allowClear之后，由于手机端没有hover事件，需要点击才能看到清除图标。

| Environment | Info |
| --- | --- |
| antd | 5.20.0 |
| React | ^18.2.0 |
| System | window |
| Browser | google |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: transformers
Issue: Adding Mamba2ForTokenClassification to Mamba2
Labels: Feature request

### Feature request

I’ve noticed that many newly added models do not include a `ForTokenClassification` implementation. Is this due to fundamental challenges in implementation (though I don’t perceive any major obstacles—perhaps I’ve overlooked something), or is it simply a matter of development priorities and time constraints?

### Motivation

I am currently testing a prototype based on the Mamba series models, which requires token classification outputs.

### Your contribution

If it’s merely a time issue preventing the implementation of `ForTokenClassification` in `transformers`, I’d be more than willing to contribute by adding this feature for Mamba/Mamba2. If time allows, I’d also be happy to extend the support to other models.

From my understanding, replicating the approach used in `LlamaForTokenClassification` should suffice to implement token classification model for most models. Any advice or guidance would be highly appreciated!
Repository: rust
Issue: Tracking issue for release notes of #93235: Tracking Issue for `const_nonnull_new`
Labels: T-libs-api,relnotes,A-const-eval,relnotes-tracking-issue


This issue tracks the release notes text for #93235.

### 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
# Const Stabilized APIs
- [`NonNull::new`](https://doc.rust-lang.org/stable/std/ptr/struct.NonNull.html#method.new)
````

> [!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 @lilasta -- origin issue/PR authors and assignees for starting to draft text
Repository: pytorch
Issue: DISABLED test_override_cpu_sum (__main__.TestPythonRegistration)
Labels: triaged,module: flaky-tests,skipped,module: python dispatcher

Platforms: asan, linux, mac, macos, rocm, win, windows, slow





This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/flakytest?name=test_override_cpu_sum&suite=TestPythonRegistration&limit=100) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/34161750972).

Over the past 3 hours, it has been determined flaky in 36 workflow(s) with 72 failures and 36 successes.

**Debugging instructions (after clicking on the recent samples link):**
DO NOT ASSUME THINGS ARE OKAY IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
3. Grep for `test_override_cpu_sum`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.



<details><summary>Sample error message</summary>

```
Traceback (most recent call last):
  File "/var/lib/jenkins/workspace/test/test_python_dispatch.py", line 330, in test_override_cpu_sum
    self.assertEqual(torch.sum(x), x)
  File "/opt/conda/envs/py_3.11/lib/python3.11/site-packages/torch/testing/_internal/common_utils.py", line 4016, in assertEqual
    raise error_metas.pop()[0].to_error(
AssertionError: The values for attribute 'shape' do not match: torch.Size([]) != torch.Size([2]).

To execute this test, run the following from the base repo dir:
    python test/test_python_dispatch.py TestPythonRegistration.test_override_cpu_sum

This message can be suppressed by setting PYTORCH_PRINT_REPRO_ON_FAILURE=0
```

</details>


Test file path: `test_python_dispatch.py`

ConnectionTimeoutError: Connect timeout for 5000ms, GET https://raw.githubusercontent.com/pytorch/pytorch/main/test/test_python_dispatch.py -2 (connected: false, keepalive socket: false, socketHandledRequests: 1, socketHandledResponses: 0)
headers: {}

cc @clee2000 @wdvr
Repository: react
Issue: Bug: `select` menu won't update highlight when options change
Labels: Status: Unconfirmed

If a `<select>`'s options changes (e.g. if options are loaded asynchronously) while the menu is open, the `<select>` won't re-examine its options to update its highlight position (`selectedIndex`). 

In the Codesandbox example below, I have a select menu that will have its options swapped out 1 second after it receives focus. This is to simulate the fetch call that I'm doing in my real app.

React version: 19.0.0

## Steps To Reproduce

**Browser:** Either use Google Chrome or Microsoft Edge, it's not reproducible in Firefox.

Browser versions:

- Google Chrome – Version 131.0.6778.109 (Official Build) (64-bit)
- Microsoft Edge – Version 131.0.2903.86 (Official build) (64-bit)


1. Open [this Codesandbox](https://codesandbox.io/p/sandbox/select-menu-with-dynamic-options-forked-nvt488?workspaceId=ws_DVJY22si5M9kiWeZb4Ybth)
2. Click on the select menu
3. Watch as the complete options list replaces the old one

1 ![image](https://github.com/user-attachments/assets/69a7ca1a-2c01-42b2-ae4e-9f08be431a2b) 2 ![image](https://github.com/user-attachments/assets/dba3eb0e-4043-4ba7-96a7-64f6ff583529) 3 ![image](https://github.com/user-attachments/assets/25b9f490-ddf4-4698-bc91-beb16fddfcc5)

## The current behavior

When the new options replaces the old ones, the highlight position stays on the first element. Only after closing and re-opening the menu, the highlight goes to the option with `value="italy"`

## The expected behavior

I want the select menu to highlight the `value="italy"`  option after options are replaced
Repository: vscode
Issue: Statusbar has strange theme defaults
Labels: bug,ux,workbench-status

In default dark, you get a nice hover feedback:

![Image](https://github.com/user-attachments/assets/c1ebf921-97a2-4047-8acc-4716a3eca4cf)

Even for prominent items:

![Image](https://github.com/user-attachments/assets/b9e91ae7-fcde-4496-8ef9-900437363400)

In default light theme, there is no hover feedback at all?

![Image](https://github.com/user-attachments/assets/42ea5c11-cf00-4698-aa1f-e03d1ba4f95a)

In high contrast themes, should we be using background color at all for prominent or other indicators?

![Image](https://github.com/user-attachments/assets/8af9b3d4-55f2-42d4-8c9b-a6861b40d5c9)

Because we do not in dark high contrast.
Repository: rust
Issue: Investigate using `crosstool-ng` instead of CentOS baseline
Labels: C-enhancement,T-infra,A-CI,E-needs-investigation

In some `dist` builders (mainly the x64 one), we use an old Linux distro (e.g. CentOS 7) to have a low glibc baseline. However, it seems like using `crosstool-ng`, and essentially "cross-compiling" from platform A to platform A could also work, and perhaps result in a simpler CI configuration (https://github.com/rust-lang/rust/pull/133902).
Repository: bitcoin
Issue: Use clang in VS build?
Labels: Brainstorming,Windows,Build system

MSVC has many issues, for example:

* non-optimized codegen: https://github.com/bitcoin/bitcoin/pull/29852#issuecomment-2049803970
* compile failure: https://github.com/bitcoin/bitcoin/issues/31303
* legal, but brittle stdlib: https://github.com/bitcoin/bitcoin/pull/31391#issuecomment-2510762011
* unspecified issue: https://github.com/bitcoin/bitcoin/pull/31061#issuecomment-2531244463

Thus, it could make sense to evaluate whether to switch the build docs to clang (possibly with libc++), see https://learn.microsoft.com/en-us/cpp/build/clang-support-msbuild
Repository: rust
Issue: STATUS_ACCESS_VIOLATION happens frequently with rust 1.83 under windows x64 environment
Labels: S-needs-repro

<!--
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.
-->

I tried this code:

```rust
<code>
fn main() {
    println!("hihi");
}
```

I expected to see this happen:
*Just a normal "hihi" string* printed out on my console


Instead, this happened: *explanation*
```
PS C:\Users\maple\Desktop\etc\dev\temp> cargo run
   Compiling temp v0.1.0 (C:\Users\maple\Desktop\etc\dev\temp)
error: could not compile `temp` (bin "temp")

Caused by:
  process didn't exit successfully: `C:\Users\maple\.rustup\toolchains\1.83-x86_64-pc-windows-msvc\bin\rustc.exe --crate-name temp --edition=2021 src/main.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --diagnostic-width=142 --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debuginfo=2 --check-cfg cfg(docsrs) --check-cfg "cfg(feature, values())" -C metadata=d54b924dfe4288ad --out-dir C:\Users\maple\Desktop\etc\dev\temp\target\debug\deps -C incremental=C:\Users\maple\Desktop\etc\dev\temp\target\debug\incremental -L dependency=C:\Users\maple\Desktop\etc\dev\temp\target\debug\deps` (exit code: 0xc0000005, STATUS_ACCESS_VIOLATION)
```

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
<version>
PS C:\Users\maple\Desktop\etc\dev\temp> rustc --version --verbose
rustc 1.83.0 (90b35a623 2024-11-26)
binary: rustc
commit-hash: 90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf
commit-date: 2024-11-26
host: x86_64-pc-windows-msvc
release: 1.83.0
LLVM version: 19.1.1
```

<!--
Include a backtrace in the code block by setting `RUST_BACKTRACE=1` in your
environment. E.g. `RUST_BACKTRACE=1 cargo build`.
-->
<details><summary>Backtrace</summary>
<p>

</p>
</details>

Hi, I used rust 1.81 before and upgraded to 1.83 today. When I write any codes and execute through 'cargo run' command, error happens frequently and randomly. I tried this on wsl, but it was fine.

I guess there might be some bug with recently rust compiler (version 1.83) under windows / x86_64 environment
Repository: rust
Issue: Type inference fails where LUB coercion succeeds
Labels: A-inference,C-bug,A-coercions,T-types

This is probably a known effect, but I'd like to get confirmation that this is intended behavior or a known bug. It sure caught me by surprise.

I tried this code:

```rust
let a1: _ = [b"a", b"a" as &[u8]];
let b1: _ = [b"a" as &[u8], b"a"];

let a2: [_; 2] = [b"a", b"a" as &[u8]];
let b2: [_; 2] = [b"a" as &[u8], b"a"];

let a3: [&[u8]; 2] = [b"a", b"a" as &[u8]];
let b3: [&[u8]; 2] = [b"a" as &[u8], b"a"];

fn unify<T>(_x: T, _y: T) {}
unify(b"a", b"a" as &[u8]); // a4
unify(b"a" as &[u8], b"a"); // b4

if true { b"a" } else { b"a" as &[u8] }; // a5
if true { b"a" as &[u8] } else { b"a" }; // b5
```

I expected to see this happen: Each pair of lines is symmetrical, so intuitively, either they should both compile or both fail typeck.

Instead, this happened:

- `a1` and `b1` both compile
- `a2` *fails to compile*, `b2` compiles
- `a3` and `b2` both compile
- `a4` *fails to compile*, `b4` compiles
- `a5` and `b5` both compile

The reason is that in cases 1, 3, 5, LUB coercion is used, and in cases 2 and 4, a more generic type inference mechanism is used (I think). I can kind of see why `a4` needs to fail compilation, but `a2` failing is extremely counterintuitive.


### Meta

`rustc --version --verbose`:
```
rustc 1.84.0-nightly (1e4f10ba6 2024-10-29)
binary: rustc
commit-hash: 1e4f10ba6476e48a42a79b9f846a2d9366525b9e
commit-date: 2024-10-29
host: x86_64-unknown-linux-gnu
release: 1.84.0-nightly
LLVM version: 19.1.1
```
Repository: deno
Issue: Panic when passing a windows style file path in `patch` field of `deno.json`
Labels: cli,config,panic

The patch field looks like this: `patch: [ "D:\\a\\fresh\\fresh\\" ]`

```
============================================================
Deno has panicked. This is a bug in Deno. Please report this
at https://github.com/denoland/deno/issues/new.
If you can reliably reproduce this panic, include the
reproduction steps and re-run with the RUST_BACKTRACE=1 env
var set and include the backtrace in your report.
Platform: windows x86_64
Version: 2.1.3
Args: ["C:\\hostedtoolcache\\windows\\deno\\2.1.3\\x64\\deno.exe", "run", "-A", "main.ts"]
thread 'main' panicked at C:\Users\runneradmin\.cargo\registry\src\index.crates.io-6f17d22bba15001f\deno_config-0.39.3\src\workspace\discovery.rs:953:56:
called `Result::unwrap()` on an `Err` value: UrlToFilePathError(Url { scheme: "d", cannot_be_a_base: true, username: "", password: None, host: None, port: None, path: "\\a\\fresh\\fresh\\/", query: None, fragment: None })
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
```
Repository: three.js
Issue: Select if a directional light should contribute to the lighting color contribution, or to a shadow map only ( real time shadowing ) 
Labels: Enhancement

### Description

A while ago I did hack my way on a custom threejs of the webGLRenderer to render both baked and real time lighting, 
And I found out really useful to determine / selecting if a light should contribute of the color lighting output, or **cast shadow only** and only contributes to the shadow mapping

**Example for a scene, let say you have two directional lights :**

1 used for baking shadows globally and for lighting color contribution

1 used for real time shadowing, but this one should not contribute to the color lighting as it would add up a second contribution, and on top affecting perfs since one light is only needed for the lighting color contribution



### Solution

Maybe adding an boolean property to toggle off the color contribution ? 



### Additional context

_No response_
Repository: TypeScript
Issue: The identifiers field of Sourcefile is not correct
Labels: Needs More Info

### 🔍 Search Terms

The following programming practices:
1.  open or create an arkts project and create a new HSP module (shared library)
2.  Create a new test.ets file under library->pages, and enter the code:export function cc (param:string) {}
export function name(params: string) {
}
export  const  sss = ''
3. Create a new test2.ets file. Enter the code:
export function name(param:string) {

}
4. Modify the index.ets file code under the library module as:
export {name} from "./src/main/ets/pages/test2"
export { add } from './src/main/ets/utils/Calc'
5. Execute undo（ctrl+z）
6. Right click generate... Declarations in the test.ets file, select all the items to be exported, and click OK，The code of the index.ets file under the check module is as follows. Name is not a unique name
export {name} from "./src/main/ets/pages/test2"
export { add } from './src/main/ets/utils/Calc'

export { cc, name, sss } from "./src/main/ets/pages/test"

### ✅ 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

The identifier value can be updated in real time according to the text, so that the naming of the exported function in the index.ets file can ensure uniqueness

### 📃 Motivating Example

Expected results：
export {name} from "./src/main/ets/pages/test2"
export { add } from './src/main/ets/utils/Calc'

export { cc, name as name_1, sss } from "./src/main/ets/pages/test"

### 💻 Use Cases

1. What do you want to use this for?
2. What shortcomings exist with current approaches?
3. What workarounds are you using in the meantime?