sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: DISABLED test_device_mode_ops_sparse_sampled_addmm_cpu_float64 (__main__.TestDeviceUtilsCPU)
Labels: module: sparse,triaged,module: flaky-tests,skipped,module: unknown

Platforms: asan, linux

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

Over the past 3 hours, it has been determined flaky in 25 workflow(s) with 75 failures and 25 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_device_mode_ops_sparse_sampled_addmm_cpu_float64`
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_utils.py", line 1164, in test_device_mode_ops
    for sample in samples:
  File "/opt/conda/envs/py_3.11/lib/python3.11/site-packages/torch/testing/_internal/common_utils.py", line 388, in __next__
    input_idx, input_val = next(self.child_iter)
                           ^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/py_3.11/lib/python3.11/site-packages/torch/utils/_contextlib.py", line 36, in generator_context
    response = gen.send(None)
               ^^^^^^^^^^^^^^
  File "/opt/conda/envs/py_3.11/lib/python3.11/site-packages/torch/testing/_internal/common_methods_invocations.py", line 1214, in sample_inputs_sparse_sampled_addmm
    .to_sparse_csr()
     ^^^^^^^^^^^^^^^
RuntimeError: Please register PrivateUse1HooksInterface by `RegisterPrivateUse1HooksInterface` first.

To execute this test, run the following from the base repo dir:
    python test/test_utils.py -k TestDeviceUtilsCPU.test_device_mode_ops_sparse_sampled_addmm_cpu_float64

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

</details>


Test file path: `test_utils.py`

cc @alexsamardzic @nikitaved @pearu @cpuhrsch @amjames @bhosmer @jcaip @clee2000
Repository: pytorch
Issue: Profiler getProfilerConfig interface can not support Ascend npu platform
Labels: OSS contribution wanted,oncall: profiler

### 🚀 The feature, motivation and pitch

On Ascend NPU platform，the [torch_npu plugin](https://gitee.com/ascend/pytorch) supports some platform specific features. For profiler,  torch_npu plugin has a [NpuProfilerConfig](https://gitee.com/ascend/pytorch/blob/master/torch_npu/csrc/profiler/npu_profiler.h) which is similar to ProfilerConfig.  But the getProfilerConfig interface of namespace torch::profiler::impl is incompatible for NpuProfilerConfig. The return value type is restricted to ProfilerConfig, converting from NpuProfilerConfig to ProfilerConfig will result in an error.
Pytorch
![torch](https://github.com/user-attachments/assets/069b8504-6dfd-4edc-a9c3-0e65e52beb93)
![torch_profilier_config](https://github.com/user-attachments/assets/c164dd6f-6389-45da-99c0-517c6271b854)
torch_npu
![torch_npu_config](https://github.com/user-attachments/assets/7869d33b-ea3b-46db-b4e0-e0a8e6ea5208)

### Alternatives

The getProfilerConfig interface returns a pointer to base class, BaseProfilierConfig for example. Then ProfilerConfig of pytorch and NpuProfilerConfig of torch_npu inherit from base class. This will enable compatibility with profiler configuration differences across different platforms


### Additional context

_No response_

cc @robieta @chaekit @aaronenyeshi @guotuofeng @guyang3532 @dzhulgakov @davidberard98 @briancoutinho @sraikund16 @sanrise
Repository: create-react-app
Issue: Allow user to config publicPath of webpack and set its default value to auto
Labels: issue: proposal,needs triage

### Is your proposal related to a problem?

<!--
  Provide a clear and concise description of what the problem is.
  For example, "I'm always frustrated when..."
-->

It's popular to use CDN when deploy a web app to production, while in test stage the static assets are served with a file server or s3. In most case this can be done by building app multiple time with different `PUBLIC_URL`. 

But there are some case that will need to change `publicPath` in the runtime. 
One case is serving built vendor frontend assets without source code.
The typical case make me want this feature is streamlit and its compoments. Their frontend code is built with `create-react-app` and release the built assets in the installation packages, which make it hard to rebuild it with another  `PUBLIC_URL`. 

There are several issues related to this proposal.

* https://github.com/facebook/create-react-app/issues/3834
* https://github.com/facebook/create-react-app/issues/13467
* https://stackoverflow.com/questions/59034660/how-to-change-the-publicpath-in-create-react-app

### Describe the solution you'd like

<!--
  Provide a clear and concise description of what you want to happen.
-->

Currently, the webpack `publicPath` field is decided by `PUBLIC_URL`  and it's hard to modify the webpack configuration.
In order to make it easier to apply CDN in the mentioned case, 
I think `create-react-app` should provide another option (maybe `WEBPACK_PUBLIC_PATH`) to allow user to config `publicPath` independently, and its default value should be 'auto' instead of the value of `PUBLIC_URL`.

With this all it need to do to apply CDN for built frontend is to replace the `href` in all `<link>` and '<script>` tags in the `index.html`.
Repository: PowerToys
Issue: Add color space converter to PowerToys Run
Labels: Idea-Enhancement,Product-PowerToys Run,Run-Plugin

### Description of the new feature / enhancement

This feature should convert one color space into others. For example, if I paste a HEX color Code into the PowerToys Run toolbar, I get a list of the same color in RGB, HSL, CMYK, HCL, etc. 

### Scenario when this would be used?

This would be useful for a fast conversion into other color spaces without the need to open the browser and search for a website that does the same thing. I guess a lot of developers turning designs into code would benefit from this feature.

### Supporting information

_No response_
Repository: PowerToys
Issue: Preview for xlsm files
Labels: Idea-Enhancement,Needs-Triage,Product-Peek

### Description of the new feature / enhancement

ctrl space to get a preview on a XLSM FILE

### Scenario when this would be used?

i work mostly with xlsm file and preview pane by windows does not allow preview of xlsm file

### Supporting information

_No response_
Repository: ui
Issue: [bug]:  Form component with Zod resolver Types of parameters value and value are incompatible.
Labels: bug

### Describe the bug

I having the Type error on the <Form {...form} and FormField <FormField control={form.control}. The only way to get rid of the error is by add <Form {...form as any}. 

```
const formSchema = z.object({
  isFree: z.boolean().default(false),
});

const form = useForm<z.infer<typeof formSchema>>({
    resolver: zodResolver(formSchema),
    defaultValues: {
      isFree: Boolean(initialData.isFree),
    },
  });


 <Form {...form}>

```

Current versions: 

  "@hookform/resolvers": "^3.9.0",
 "zod": "^3.23.8",
"react-hook-form": "^7.52.2",



### Affected component/components

Form

### How to reproduce

No steps, the lint will flag this in IDE right away

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Webstorm
Mac
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: vscode
Issue: Vimium or Vim easymotion like keyboard navigation for the whole UI
Labels: feature-request,accessibility

<!-- ⚠️⚠️ 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. -->

[Vimium](https://chromewebstore.google.com/detail/vimium/dbepggeogbaibhgnhhndojpepiihcmeb?hl=en)
[Hunt-and-peck](https://github.com/zsims/hunt-and-peck)
[win-vind](https://github.com/pit-ray/win-vind)
As a developer I really don't want to  use my mouse. In order to do so these are some of programs I in daily. It's like vim [easymotion](https://github.com/easymotion/vim-easymotion) but for the whole UI. But there are several problems while using them with vscode.

- Linux support.
- Menu bar automatically closes.
- All buttons are not accessible

I'm requesting this feature in the hope that vscode will be fully usable without a mouse. Automation of the vscode UI will be easy.

![image](https://github.com/user-attachments/assets/0eab6be8-8795-4a06-9522-19ba335443f3)
 **I've searched market place and alternative software for linux but haven't found any.**
Repository: material-ui
Issue: [material-ui][Autocomplete] Improve editing experience of Autocomplete using the "multiple" option
Labels: package: material-ui,component: autocomplete,enhancement

### Summary

When an Autocomplete with multiple possible values already has a few options selected, it could end up with very limited space while typing to add a new option. It would be cool if the text input part could be rendered on a new line when overflow starts and/or when there's very limited space to type a query/value.

### Examples

In the example you can see only 4 characters of input are visible.
<img width="767" alt="Screenshot 2024-08-06 at 10 22 23" src="https://github.com/user-attachments/assets/3cccbd44-3bd4-4d45-8160-990a7b770927">


### Motivation

This is useful when writing complex values that prefer context of already written text.

P.S. My company has 10 pro licenses.

**Search keywords**: Autocomplete, multiple
Repository: godot
Issue: godot suddenly close
Labels: bug,topic:editor,needs testing,crash,topic:animation

### Tested versions

4.1 stable and 4.2.2 stable

### System information

windows 11 - i5-12400f - rtx2060 - 16gb ram.

### Issue description

the issue is that whenever i start working on animationplayer node, and start the animation to test it, after a few second it suddenly close godot, and that happen 90% of the time, sometimes it just stop at random time and not from the animationplayer node, and all that happen when i'm working on my pc, but in my laptop that is weaker than my pc maybe 10x, everything works perfectly and never crash or close godot, and the version doesn't change anything, it doesn't even give a crash message, it just close.

### Steps to reproduce

.

### Minimal reproduction project (MRP)

.
Repository: vscode
Issue: Notebooks check object leaks smoketest failure
Labels: bug,smoke-test-failure,notebook

```
 1) VSCode Smoke Tests (Web)
       Notebooks
         check object leaks:
     Error: Timeout: get element '.notebook-editor .monaco-list-row.focused' after 20 seconds.
      at Code.poll (/Users/runner/work/1/s/test/automation/out/code.js:204:23)
      at async Code.waitForElement (/Users/runner/work/1/s/test/automation/out/code.js:163:16)
      at async Notebook.openNotebook (/Users/runner/work/1/s/test/automation/out/notebook.js:18:9)
      at async /Users/runner/work/1/s/test/smoke/out/areas/notebook/notebook.test.js:35:17
      at async Profiler.checkObjectLeaks (/Users/runner/work/1/s/test/automation/out/profiler.js:17:9)
      at async Context.<anonymous> (out/areas/notebook/notebook.test.js:34:13)

````

https://monacotools.visualstudio.com/Monaco/_build/results?buildId=286726&view=results
Repository: material-ui
Issue: [docs-infra] Test the link check script
Labels: test,core,ready to take,scope: docs-infra

              The cleanest way I can think of would be to extract the script logic into packages-internal/scripts, test it there and leave just the CLI in the scripts directory.

_Originally posted by @michaldudak in https://github.com/mui/material-ui/issues/43144#issuecomment-2270663097_
            
            
For context, the script which takes care of verifying each internal link point to an existing page, and an existing anchor was doing nothing (except eating some CPU time)

It would be nice to have a test that ensures it fails 

The idea would be to have two markdown files, one with broken links, one with ok links, and run test that ensure the script is failing on the correct one and passing the other one.

This should avoid the issue we got with the script silently failing because it detected no link

**Search keywords**:
Repository: deno
Issue: Bug: `Buffer` fails to encode ascii string to base64
Labels: bug,node compat

It seems like a special crafted string can causes an error to be thrown when creating a Node Buffer and encode with `base64`.

## Steps to reproduce

Run this file:

```ts
import { Buffer } from "node:buffer";
Buffer.from("base64-encoded-bytes-from-browser", "base64");
```

Output (Deno 1.45.5):

```sh
error: Uncaught (in promise) InvalidCharacterError: Failed to decode base64
Buffer.from("base64-encoded-bytes-from", "base64");
       ^
    at base64Write (ext:deno_node/internal_binding/_utils.ts:30:12)
    at Buffer.base64Write_ [as base64Write] (ext:deno_node/internal/buffer.mjs:726:10)
    at Object.write (ext:deno_node/internal/buffer.mjs:2177:46)
    at fromStringFast (ext:deno_node/internal/buffer.mjs:255:22)
    at fromString (ext:deno_node/internal/buffer.mjs:276:10)
    at _from (ext:deno_node/internal/buffer.mjs:160:12)
    at Function.from (ext:deno_node/internal/buffer.mjs:198:10)
    at file:///Users/marvinh/dev/test/deno-buffer/foo.mjs:2:8
```

Output (Deno git 86e219c50):
```sh
error: Uncaught (in promise) InvalidCharacterError: Failed to decode base64
Buffer.from("base64-encoded-bytes-from-browser", "base64");
       ^
    at forgivingBase64Decode (ext:deno_web/00_infra.js:257:10)
    at base64ToBytes (ext:deno_node/internal_binding/_utils.ts:26:12)
    at Uint8Array.base64Write (ext:deno_node/internal/buffer.mjs:672:21)
    at Object.write (ext:deno_node/internal/buffer.mjs:2123:46)
    at Uint8Array.write (ext:deno_node/internal/buffer.mjs:794:14)
    at fromString (ext:deno_node/internal/buffer.mjs:216:22)
    at _from (ext:deno_node/internal/buffer.mjs:124:12)
    at Function.from (ext:deno_node/internal/buffer.mjs:162:10)
    at file:///Users/marvinh/dev/test/deno-buffer/foo.mjs:2:8
```

Version: Deno 1.45.5
Repository: transformers
Issue: Zero-shot finetuning examples
Labels: Feature request,Vision

### Feature request

@amyeroberts @qubvel @NielsRogge 

Does HF team intersted in adding zero-shot finetuning example like https://github.com/SangbumChoi/transformers/tree/grounding_examples/examples/pytorch/zero-shot?

If the team merge these two following open PR then
https://github.com/huggingface/transformers/pull/31828
https://github.com/huggingface/transformers/pull/31964

we can finetune the groundingdino and write something like this.
https://blog.roboflow.com/how-to-fine-tune-paligemma/

I will left some model that you can run 
Model : https://huggingface.co/danelcsb/grounding-dino-tiny-finetuned-cppe-5-10k-steps-no-trainer/tree/main

### Motivation

People can use zero-shot model to finetune there own projects.

### Your contribution

I have made the branch already and ready to generate PR. Need some more modification.
Before
<img width="1002" alt="Screenshot 2024-08-06 at 6 08 57 PM" src="https://github.com/user-attachments/assets/92bbe009-91df-4be5-b786-eb998fe4c508">
After
<img width="793" alt="Screenshot 2024-08-06 at 6 09 05 PM" src="https://github.com/user-attachments/assets/dec37ec9-f0fb-4ef4-93a9-a5575196e472">
Repository: react
Issue: [DevTools Bug] Cannot add node "1" because a node with that id is already in the Store.
Labels: Type: Bug,Status: Unconfirmed,Component: Developer Tools

### Website or app

local repo

### Repro steps

just loaded the local  react app

### How often does this bug happen?

Every time

### DevTools package (automated)

react-devtools-extensions

### DevTools version (automated)

5.3.1-ccb20cb88b

### Error message (automated)

Cannot add node "1" because a node with that id is already in the Store.

### Error call stack (automated)

```text
at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1172435
    at v.emit (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1141877)
    at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1143565
    at bridgeListener (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1551564)
```


### Error component stack (automated)

_No response_

### GitHub query string (automated)

```text
https://api.github.com/search/issues?q=Cannot add node  because a node with that id is already in the Store. in:title is:issue is:open is:public label:"Component: Developer Tools" repo:facebook/react
```
Repository: pytorch
Issue: Why is kvcache transfer slow using peer-to-peer communication (two GPUs on one machine).
Labels: oncall: distributed,triaged,module: nccl

Why use point-to-point communication (two GPU on a single machine)? Sending kvcache after each layer of model inference takes a long time, 2000 tokens take 0.5 seconds.

Could anyone provide some suggestions to help me optimize my NCCL code for transmitting KV cache to improve performance? 

I put the kvcache tensor split information in a list（send_metas）, and send and receive it in a loop at a certain stage。

The process of sending：

```
>   for send_meta in send_metas:
>           sendgpu_id = send_meta['sendgpu_id']
>           recvgpu_id = send_meta[recvgpu_id]
>           layer_id = send_meta[layer_id]
>           block_id = send_meta[block_id]
>           tensor_tmp = send_meta[layer_id][kv, block_id, :]
>           if(rank==sendgpu_id):
>                  dist.send(tensor=tensor_tmp, dst=recvgpu_id)
```


The process of recv：
```

> for recv_meta in recv_metas:
>         sendgpu_id = recv_meta['sendgpu_id']
>         recvgpu_id = recv_meta[recvgpu_id]
>         layer_id = recv_meta[layer_id]
>         block_id = recv_meta[block_id]
>         tensor_tmp = send_meta[layer_id][kv, block_id, :]
>         if(reak==recvgpu_id):
>                 dist.recv(tensor=tensor_tmp, dst=sendgpu_id)
```

cc @XilunWu @H-Huang @awgu @kwen2501 @wanchaol @fegin @fduwjj @wz337 @wconstab @d4l3k @c-p-i-o
Repository: rust
Issue: Can CFI be made compatible with type erasure schemes?
Labels: T-compiler,A-sanitizers,C-discussion,PG-exploit-mitigations,T-opsem

There is a kind of common type erasure scheme used in Rust that goes something like this:
```rust
/// Invariant: there exists some type `T` such that `data` is actually a `&'a T` and `op`
/// is actually a `fn(&T)`.
struct ErasedTypeAndOp<'a> {
  data: *const (),
  op: fn(*const ()),
  _phantom: PhantomData<&'a ()>,
}

impl<'a> ErasedTypeAndOp<'a> {
  pub fn new<T>(data: &'a T, op: fn(&'a T)) {
    Self {
      data: data as *const T,
      op: unsafe { std::mem::transmute(op) },
      _phantom: PhantomData,
    }
  }

  pub fn call_op(&self) {
    (self.op)(self.data)
  }
}
```
This is used, in particular, in the standard library for type-erased `fmt` arguments.

Unfortunately, CFI is not happy with this since the function pointer `op` was transmuted, and is not invoked at its original type. Our documented [ABI compatibility rules](https://doc.rust-lang.org/stable/std/primitive.fn.html#abi-compatibility) are fine with this (and Miri also won't complain), but CFI is actually more restrictive than those rules and (at least in some configurations) rejects this call since caller and callee do not agree on the type of the argument.

This is not good: ideally we could just tell people they can turn on CFI in any Rust program and expect it to work. In other words, ideally CFI would only reject programs that we consider buggy (in an official Rust lang/opsem sense), since they have either UB or [erroneous behavior](https://github.com/rust-lang/unsafe-code-guidelines/issues/512).

I am not sure what is the best way to fix this. I also know very little about what CFI can and cannot do (and I understand there's actually a bunch of CFI implementations that differ in their capabilities). My completely naive first idea would be to say that we have a new magic primitive type `Erased` and then declare `ErasedTypeAndOp` as follows:
```rust
struct ErasedTypeAndOp<'a> {
  data: *const Erased,
  op: fn(*const Erased),
  _phantom: PhantomData<&'a ()>,
}
```
Then we say that if caller and callee use different pointer types for their arguments, that is erroneous behavior unless one of them uses the special `Erased` pointee type, in which case the call is permitted. (Or maybe only the call site is allowed to use `Erased` like that?)

Is that something CFI can do -- basically have pointee type checking "turned off" if the call site uses `*const Erased`? If yes, would this be an acceptable trade-off between still rejecting accidental type mismatches (and catching as many attacks as possible) while accepting legitimate type erasure patterns?

Cc @rust-lang/opsem @maurer @rcvalle
Repository: flutter
Issue: [pigeon] linux generator only supports 123 total custom types
Labels: platform-linux,package,team-ecosystem,p: pigeon,P1,triaged-ecosystem

https://github.com/flutter/packages/pull/6840 adds support for unlimited custom types to all generators besides via the overflow class. This functionality needs to be extended to the gobject generator as well.
Repository: go
Issue: x/website: module tutorial "add a test" should apply "keep going" principle"
Labels: Documentation,NeedsFix,website

### Go version

n/a

### Output of `go env` in your module/workspace:

```shell
n/a
```


### What did you do?

I visisted https://go.dev/doc/tutorial/add-a-test and I read how to create a test for Go code.

### What did you see happen?

I saw it advise test construction using `(*testing.T).Fatalf` per the excerpts below:

```go
func TestHelloName(t *testing.T) {
    name := "Gladys"
    want := regexp.MustCompile(`\b`+name+`\b`)
    msg, err := Hello("Gladys")
    if !want.MatchString(msg) || err != nil {
        t.Fatalf(`Hello("Gladys") = %q, %v, want match for %#q, nil`, msg, err, want)
    }
}

func TestHelloEmpty(t *testing.T) {
    msg, err := Hello("")
    if msg != "" || err == nil {
        t.Fatalf(`Hello("") = %q, %v, want "", error`, msg, err)
    }
}
```

### What did you expect to see?

Given the design guidance with tests to "[keep going](https://go.dev/wiki/TestComments#keep-going)", I would expect these tests to be written as below using `(*testing.T).Errorf`:

```go
func TestHelloName(t *testing.T) {
    name := "Gladys"
    want := regexp.MustCompile(`\b`+name+`\b`)
    msg, err := Hello("Gladys")
    if !want.MatchString(msg) || err != nil {
        t.Errorf(`Hello("Gladys") = %q, %v, want match for %#q, nil`, msg, err, want)
    }
}

func TestHelloEmpty(t *testing.T) {
    msg, err := Hello("")
    if msg != "" || err == nil {
        t.Errorf(`Hello("") = %q, %v, want "", error`, msg, err)
    }
}
```

It seems like it would be useful to have the training material aligned with community development expectations.