sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: MPS clamp_min on older MacOS
Labels: triaged,module: correctness (silent),module: mps

### 🐛 Describe the bug

When using the MPS device on an Apple M2 Pro, I see the following behavior:

```
import torch

t = torch.tensor([1,2,3]).to("mps")
t.clamp_min(1.0)
```
Output: `tensor([0., 0., 0.], device='mps:0')`

If the correct type is used for the clamp value:
```
t.clamp_min(1)
```
Output: `tensor([1, 2, 3], device='mps:0')`

Also note, the same behavior is seen for the `clamp` method:
```
t.clamp(min=1.)
```
Output: `tensor([0., 0., 0.], device='mps:0')`
with the following message:
```
miniconda3/envs/test2/lib/python3.12/site-packages/torch/_tensor_str.py:138: UserWarning: MPS: nonzero op is supported natively starting from macOS 13.0. Falling back on CPU. This may have performance implications. (Triggered internally at /Users/runner/work/pytorch/pytorch/pytorch/aten/src/ATen/native/mps/operations/Indexing.mm:335.)
  nonzero_finite_vals = torch.masked_select(
```

This seems to only occur on the MPS device, whereas CPU (on same machine) and cuda (different environment) produced the correct output.

### Versions

Collecting environment information...
PyTorch version: 2.4.0
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: macOS 13.6.7 (arm64)
GCC version: Could not collect
Clang version: 15.0.0 (clang-1500.1.0.2.5)
CMake version: version 3.27.6
Libc version: N/A

Python version: 3.12.4 | packaged by Anaconda, Inc. | (main, Jun 18 2024, 10:07:17) [Clang 14.0.6 ] (64-bit runtime)
Python platform: macOS-13.6.7-arm64-arm-64bit
Is CUDA available: False
CUDA runtime version: No CUDA
CUDA_MODULE_LOADING set to: N/A
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

CPU:
Apple M2 Pro

Versions of relevant libraries:
[pip3] numpy==1.26.4
[pip3] torch==2.4.0
[conda] numpy                     1.26.4                   pypi_0    pypi
[conda] torch                     2.4.0                    pypi_0    pypi

cc @ezyang @gchanan @zou3519 @kadeng @msaroufim @kulinseth @albanD @malfet @DenisVieriu97 @jhavukainen
Repository: material-ui
Issue: Joy UI: Disabled Link IconButton appearance appears to still be enabled
Labels: on hold,component: icon button,package: joy-ui

### Steps to reproduce

Link to live example: https://codesandbox.io/s/peaceful-estrela-dr8zfz

Steps:
1. Create a Joy UI IconButton
2. Set its component prop to either `"a"` or `Link` from `react-router-dom`
3. Set its `disabled` prop to `true`
4. The button is still clickable and visually appears to be enabled because it is


### Current behavior

The button appears to still be enabled even though it shouldn't be.

### Expected behavior

The button should be disabled (no pointer-events, less contrast with the background, etc...)

### Context

I am simply trying to have a link button be disabled.

My guess: in the DOM, the disabled prop cannot be applied to the `a` element, which messes up the styles since the selector is literally:

```css
.css-randomId-JoyIconButton-root:disabled {
  // rules
}
```

### Your environment

Tested on Chrome version 127.0.6533.89 (Official Build) (arm64)

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  System:
    OS: macOS 14.6
  Binaries:
    Node: 22.4.1 - /opt/homebrew/bin/node
    npm: 10.8.2 - /opt/homebrew/bin/npm
    pnpm: Not Found
  Browsers:
    Chrome: 127.0.6533.100
    Edge: Not Found
    Safari: 17.6
  npmPackages:
    @emotion/react: ^11.11.4 => 11.13.0 
    @emotion/styled: ^11.11.5 => 11.13.0 
    @mui/base:  5.0.0-beta.42 
    @mui/core-downloads-tracker:  6.0.0-dev.240424162023-9968b4889d 
    @mui/joy: ^5.0.0-beta.48 => 5.0.0-dev.240424162023-9968b4889d 
    @mui/private-theming:  6.0.0-dev.20240529-082515-213b5e33ab 
    @mui/styled-engine:  6.0.0-dev.20240529-082515-213b5e33ab 
    @mui/system:  6.0.0-dev.240424162023-9968b4889d 
    @mui/types:  7.2.15 
    @mui/utils:  6.0.0-dev.20240529-082515-213b5e33ab 
    @types/react: ^18.3.3 => 18.3.3 
    react: ^18.3.1 => 18.3.1 
    react-dom: ^18.3.1 => 18.3.1 
    typescript: ^5.5.4 => 5.5.4
```
</details>


**Search keywords**: IconButton, disabled, Link, react-router-dom, enabled
Repository: rust
Issue: regression: overflow evaluating the requirement
Labels: E-needs-test,P-medium,T-compiler,regression-from-stable-to-stable

- https://crater-reports.s3.amazonaws.com/beta-1.81-2/beta-2024-07-26/gh/DanielGilchrist.poke_search_cli/log.txt
- https://crater-reports.s3.amazonaws.com/beta-1.81-2/beta-2024-07-26/reg/triangulate-0.2.0/log.txt
- https://crater-reports.s3.amazonaws.com/beta-1.81-2/beta-2024-07-26/reg/similari-0.26.2/log.txt


```
[INFO] [stdout] error[E0275]: overflow evaluating the requirement `NaturePokeathlonStatAffect: Unpin`
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider increasing the recursion limit by adding a `#![recursion_limit = "256"]` attribute to your crate (`poke_search`)
[INFO] [stdout] note: required because it appears within the type `PhantomData<NaturePokeathlonStatAffect>`
[INFO] [stdout]     --> /rustc/08328a323ecd80b443a8fcc72c6b1071f48e233f/library/core/src/marker.rs:740:12
```
Repository: rust
Issue: regression: assertion `left == right` failed for floats
Labels: T-compiler,regression-from-stable-to-stable

- https://crater-reports.s3.amazonaws.com/beta-1.81-2/beta-2024-07-26/gh/TheLastBytebender.rust-workshop/log.txt
- https://crater-reports.s3.amazonaws.com/beta-1.81-2/beta-2024-07-26/gh/YogirajT.rustnet/log.txt
- https://crater-reports.s3.amazonaws.com/beta-1.81-2/beta-2024-07-26/reg/lightbird-0.1.10/log.txt

```
[INFO] [stdout] thread 'tests::test_get_ordebook_skew_by_range_orderbook' panicked at tests/test_orderbook.rs:645:9:
[INFO] [stdout] assertion `left == right` failed
[INFO] [stdout]   left: 0.8855105548523078
[INFO] [stdout]  right: 0.885510554852308
```
Repository: flutter
Issue: Web: Move decodeImageFromPixels off heap / drastically reduce memory usage
Labels: c: new feature,engine,platform-web,c: proposal,e: web_canvaskit,P2,e: web_skwasm,team-web,triaged-web

### Use case

CanvasKit heap space is limited to 2GB, which continues to cause problems when apps use a lot of images, resulting in the flutter web process crashing due to reaching the limit. Currently, decodeImageFromPixels places image data on the CanvasKit heap, which makes the problem very easy to run into.

### Proposal

Update decodeImageFromPixels to use ImageData / createImageFromTextureSource to bind the texture to image data that is outside the canvaskit heap.

Sample here shows the difference in memory usage:

https://github.com/jezell/mem_test/blob/main/lib/main.dart

Off heap via createImageFromTextureSource (proposed) 128 MB (zero impact since it starts at 128 MB): 
<img width="1228" alt="Screenshot 2024-08-09 at 10 40 31 AM" src="https://github.com/user-attachments/assets/e8d19948-b89a-4241-84d6-cd541378f079">

On heap (current) 645 MB:
<img width="1235" alt="Screenshot 2024-08-09 at 10 42 08 AM" src="https://github.com/user-attachments/assets/7f7e577d-8d7d-4ca3-84a9-c530189b27d5">
Repository: godot
Issue: Timer emits timeout sooner than it should when initialized together with the scene
Labels: discussion,topic:core,needs testing

### Tested versions

Reproducible in: v4.2.stable.official.46dc27791, v4.2.1.stable.official.b09f793f5, v4.2.2.stable.official.15073afe3

### System information

Godot v4.2.1.stable - Windows 10.0.19045 - Vulkan (Mobile) - dedicated AMD Radeon RX 6650 XT (Advanced Micro Devices, Inc.; 31.0.22011.4008) - 13th Gen Intel(R) Core(TM) i5-13400F (16 Threads)

### Issue description

If a timer is initialized together with the scene it emits timeout for the first time sooner than it should.
For example, when I run the project with the script below (Steps to reproduce) I get

```
1723225685.736
1723225686.681
1723225687.681
1723225688.680
1723225689.681
1723225690.681
```
In this case the first timeout signal was emitted 55 milliseconds sooner than expected, and after that the consecutive times remain stable with errors of at most one or two milliseconds.

I have tested with different hardware/wait_times and have gotten discrepancies ranging from 40 up to 72 milliseconds in the first timeout.

### Steps to reproduce

Create a Timer node with autostart = true (or started in _ready, doesn't matter) with the following script:
```
extends Timer

func _ready():
	timeout.connect(_on_timeout)
	print(Time.get_unix_time_from_system())

func _on_timeout():
	print(Time.get_unix_time_from_system())
```

### Minimal reproduction project (MRP)

[test_bug_timer.zip](https://github.com/user-attachments/files/16565193/test_bug_timer.zip)
Repository: TypeScript
Issue: Type name in @throws not rendered as a link
Labels: Help Wanted,Domain: JSDoc,Possible Improvement

According to the JSDoc documentation you can put a type name after a `@throws`. Something like `@throws {Error}`. I would expect the type name to be rendered as a link, but it is rendered as `{Error}`

<img width="597" alt="image" src="https://github.com/user-attachments/assets/35b207aa-f4e8-484d-91bc-3dd8b7a986b8">
Repository: PowerToys
Issue: PowerToys Run windows position changes based on number of results
Labels: Issue-Bug,Product-PowerToys Run,Needs-Triage,Status-Reproducible

### Microsoft PowerToys version

0.83.0

### Installation method

PowerToys auto-update

### Running as admin

None

### Area(s) with issue?

PowerToys Run

### Steps to reproduce

* Disable `clear previous query on launch` setting.
![image](https://github.com/user-attachments/assets/cd223136-fb3d-4249-a148-034876fa01f3)
* open PowerToys Run 
![Screenshot 2024-08-10 000500](https://github.com/user-attachments/assets/d7e4acef-d4f7-41a9-8780-66df3efb6b64)
* Type words in input box until result listed becomes fewer. 
![Screenshot 2024-08-10 000515](https://github.com/user-attachments/assets/7bdb3d05-9ea6-4b2b-ad52-dc73b1bc156e)
* Now close the PowerToys Run.
* Reopen it. 
![Screenshot 2024-08-10 000532](https://github.com/user-attachments/assets/68ae0919-8991-4536-841e-018024ce084a)
* Now the position of the PowerToys Run would have changed based on the number of results.


### ✔️ Expected Behavior

The position of PowerToys Run not changes based on number of results of previous query.

### ❌ Actual Behavior

Position of PowerToys Run changing based on number of results of previous query.

### Other Software

_No response_
Repository: kubernetes
Issue: Add debug_redact to fields in message AuthConfig (image streaming CRI API)
Labels: priority/backlog,sig/auth,area/code-organization,triage/accepted

It is a good practice to annotate sensitive fields in proto definitions with the `debug_redact`. I tried, but it seems this is blocked by https://github.com/kubernetes/kubernetes/issues/96564. At least I didn't find an easy way to bring the debug_redact as an import.

If anybody have a suggestions on how to do it or have time to investigate - it will be great.

/sig api-machinery
/area code-organization
/priority backlog
Repository: TypeScript
Issue: Add organize imports presets
Labels: Suggestion,Committed

### Acknowledgement

- [x] I acknowledge that issues using this template may be closed without further explanation at the maintainer's discretion.

### Comment

From https://github.com/microsoft/vscode/pull/209293

Looks like we added support for the fine grained settings but no support for the presets proposed in https://github.com/microsoft/vscode/pull/209293, such as `dprint` or `eslint`
Repository: deno
Issue:  npm:@temporalio/client doesn't work properly in Deno
Labels: bug,node compat,node:http

Version: Deno 1.44.2

I'm trying to use the @temporalio/client  [typescript SDK](https://docs.temporal.io/develop/typescript) with Deno to start my Workflows from my project. With the NPM layer compability i can start my workflows and connect to my [Temporal Server](https://temporal.io/).

But after some time or when i disconnect from my server, I'm getting some `node:http2` and `grpc` errors:

```shell
Warning: Not implemented: Http2Session.socket
Warning: Not implemented: Http2Session.socket

error: Uncaught TypeError: Cannot read properties of undefined (reading 'message')
    at new ERR_HTTP2_STREAM_CANCEL (ext:deno_node/internal/errors.ts:1704:51)
    at closeSession (node:http2:225:20)
    at ClientHttp2Session.destroy (node:http2:173:5)
    at file:///mnt/projects/xxxxxxxxxxxxxx/node_modules/.deno/@grpc+grpc-js@1.11.1/node_modules/@grpc/grpc-js/build/src/transport.js:255:26
    at eventLoopTick (ext:core/01_core.js:203:13)
Watcher Process failed. Restarting on file change...
```

Simple script to test:

Connect wrapper:
```ts
import { Connection, Client } from 'npm:@temporalio/client';

export default async function ({
  buildId = '1.0',
  workflowId,
  workflowTypeOrFunc
}: any) {
  try {
  // Connect to the default Server location
  const connection = await Connection.connect({
    address: Deno.env.get('TEMPORAL_SERVER_ADDRESS'),
  });

  const client = new Client({
    connection,
  });

    await client.taskQueue.updateBuildIdCompatibility('taskQueue', {
      operation: 'addNewIdInNewDefaultSet',
      buildId,
    });

    const handle = await client.workflow.start(workflowTypeOrFunc, {
      taskQueue: 'TEMPORAL_QUEUE',
      args: [],
      workflowId: workflowId,
      searchAttributes: {
        Product: ['Store Evt Driver']
      }
    });

    console.log(`Started workflow ${handle.workflowId}`);

  } catch (err: any) {
    console.error('Error starting workflow:', err);
  }
}

```

Running:

```ts
await temporalClient({ workflowId: crypto.randomUUID(), workflowTypeOrFunc: 'wfFunctionName' });
```
Repository: pytorch
Issue: [dynamo] Improve support for subclasses of popular builtin types like dict, list, set
Labels: triaged,enhancement,oncall: pt2,module: dynamo

### 🐛 Describe the bug

Dynamo specializes if the type of the object is builtin types. If we have a subclass of these buiiltin-types (even very simple one), we map it to UserDefinedObject. This is correct because one can do arbitrary stuff with the subclass.

When we call methods of the subclassed object, which map to the builtin object methods, we have to specialize. This is done here - https://github.com/pytorch/pytorch/blob/78cf8df4a019e919e8eac5f5d048d8842d4fc692/torch/_dynamo/variables/user_defined.py#L630-L708

I think we can do little better here and also extend the support. 

1) We should think which methods are common e.g. `list.__len__`, `list. __setitem__`. We should think what are the other common buitin types like `set`.
2) Similar to `__setattr__`, we will have to add support for `__setitem__` and track side effect. For example, there is no reason for the following program to not work w/o graph breaks. 

```
    def test_dict_subclass_construction(self):
        class MyDict(dict):
            pass

        my_dict = MyDict({"a" : 2})
        def fn(x):
            my_dict["b"] = 4
            return my_dict["a"] * my_dict["b"] * x

        opt_fn = torch.compile(fn, backend="eager", fullgraph=True)        

        x = torch.randn(4)
        self.assertEqual(fn(x), opt_fn(x))
```
I think this will greatly reduce graph breaks arising from users subclassing dicts.

We could probably do a little refactor and add comments so that its easy to extend.

This would pave a path to support construction of subclasses objects inside the compiled function boundary. Currently, we only support `object.__new__`/`__init__` and user defined `__new__`/`__init__`. By supporting common methods as above, we could support constructions of subclassed object like `dict.__new__`/`dict.__init__` mostly using polyfill.

### Error logs

_No response_

### Minified repro

_No response_

### Versions

NA

cc @ezyang @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @amjames
Repository: pytorch
Issue: MultiProcContinuousTest doesn't work with pytest/buck
Labels: oncall: distributed,triaged

any situation where the testing infrastructure discovers and runs a MultiProcContinuousTest itself will fail, because the first thing it will do is call `setupClass` which will assert that cls.rank>0.

The apparent design for `MultiProcContinuousTest` is that users run it by explicitly calling `.run_rank(rank, worldsize)` which will (1) set cls.rank, clsworldsize (2) call run_tests() which triggers setupClass() and passes the assertion

But why do we need .run_rank instead of just letting setupClass read RANK/WORLD_SIZE envs directly and let the tests be launched the usual way?   The goal of `MPCT` is to start the process and init the process group once, then reuse them for many tests, which means we don't want to do process creation in `setup()` which is once per test.  Could we move the process spawning logic inside `setupClass`, taking inspiration from the way MultiProcessTestCases spawns processes inside 'setup()'?  

Flagging as this led to the revert of this PR https://github.com/pytorch/pytorch/pull/130488 based on buck tests failing, due to rank being unset.

cc @XilunWu @H-Huang @awgu @kwen2501 @wanchaol @fegin @fduwjj @wz337 @d4l3k @c-p-i-o @mori360
Repository: flutter
Issue: [flutter_markdown] inline code blocks break selectable text
Labels: package,team-ecosystem,has reproducible steps,P2,p: flutter_markdown,triaged-ecosystem,found in release: 3.24

`flutter_markdown 0.7.3+1`

```dart
          MarkdownBody(
            data:
                'We also support `userId`, `sessionId`, `timestamp` (ISO-8601). All other keys are stored as custom properties.',
            selectable: true
          ),
```


<img width="738" alt="Screenshot 2024-08-09 at 4 01 26 PM" src="https://github.com/user-attachments/assets/a47710e1-b445-4764-9e2c-bfd084ede6d0">

expected: inline code blocks are also part of the selection

related: https://x.com/luke_pighetti/status/1821999839564956033
Repository: next.js
Issue: Scroll restoration does not work with pages router.
Labels: bug,Navigation

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/nextjs-scrollposition-rjrd6s?file=%2Fapp%2Fpage4%2Fpage.tsx%3A134%2C1

### To Reproduce

Codesandbox: https://rjrd6s-3000.csb.app/

### Pages Router
routes `/` and `/page2` are using the pages router. If you scroll down and then use the link on the page to go from `/` to `/page2` and then use the back button to return to `/` you will see your scroll position is NOT restored.

### App Router
routes `/page3` and `/page4` are using the app router. If you scroll down and then use the link on the page to go from `/page3` to `/page4` and then use the back button to return to `/page3` you will see your scroll position IS restored.


### Current vs. Expected behavior

both routers should restore scroll position.

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Sun Aug  6 20:05:33 UTC 2023
  Available memory (MB): 4102
  Available CPU cores: 2
Binaries:
  Node: 20.11.1
  npm: 10.2.4
  Yarn: 1.22.19
  pnpm: 8.15.4
Relevant Packages:
  next: 14.2.5 // Latest available version is detected (14.2.5).
  eslint-config-next: 14.2.1
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


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

Navigation

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

next dev (local), next build (local), next start (local), Vercel (Deployed), Other (Deployed)

### Additional context

_No response_
Repository: PowerToys
Issue: Account Managing because I want to keep my configs sync when I need in others computers
Labels: Idea-New PowerToy,Needs-Triage

### Description of the new feature / enhancement

Account Managing because I want to keep my configs sync when I need in others computers

### Scenario when this would be used?

Account Managing because I want to keep my configs sync when I need in others computers

### Supporting information

_No response_
Repository: godot
Issue: BBCode parsing breaks on strings with spaces in option values
Labels: bug,topic:gui

### Tested versions

Reproducible in 4.0.2-stable, 4.1.2-stable, 4.2-stable, 33fe10c065d194b2a440a883ecdc6a71fd3fbd5f

4.0 and 4.1 don't strip of quotation marks but still split on spaces, so multi word strings are not possible.

### System information

Godot v4.3.rc (33fe10c06) - EndeavourOS #1 SMP PREEMPT_DYNAMIC Tue, 06 Aug 2024 07:21:19 +0000 - Wayland - Vulkan (Forward+) - integrated AMD Radeon Graphics (RADV RENOIR) - AMD Ryzen 5 5500U with Radeon Graphics (12 Threads)

### Issue description

The BBCode parser splits options of tags at spaces. Some options allow arbitrary strings which should allow spaces, but this breaks. E.g. `[font name="font folder/font.ttf"][/font]` or `[img tooltip="Some tooltip"][/img]`.

### Steps to reproduce

* Create a RichTextLabel
* enable BBCode
* Enter '[font name="font folder/font.ttf"][/font]`
* An error will appear saying 

> Resource file not found: res://"font (expected type: Font)

### Minimal reproduction project (MRP)

[mrp.zip](https://github.com/user-attachments/files/16566772/mrp.zip)
Repository: ollama
Issue: Docs: tfs_z description incorrect
Labels: bug

### What is the issue?

In the Modelfile docs (https://github.com/ollama/ollama/blob/main/docs/modelfile.md#parameter) tfs_z is defined as:
```
Tail free sampling is used to reduce the impact of less probable tokens from the output. A 
higher value (e.g., 2.0) will reduce the impact more, while a value of 1.0 disables this
 setting. (default: 1)


```

So that says the range will be 1 to something higher. But this part of the llama.cpp docs suggests that it’s a range of 0 to 1. 

https://github.com/ggerganov/llama.cpp/blob/master/examples/main/README.md#tail-free-sampling-tfs

### OS

macOS

### GPU

Apple

### CPU

Apple

### Ollama version

_No response_
Repository: react
Issue: Bug: Inconsistent styles between client-side and server-side routing
Labels: Status: Unconfirmed

React version: 18.2.0

This may be verging into undefined behavior, but there seems to be a slight discrepancy when it comes to applying ill-formed CSS styles to a React element. For instance, say we had the following JSX:
```tsx
<div style={{ backgroundColor: "orange; font-size: 40px;", color: "blue" }}>Hello World</div>
```

When the JSX is server rendered, it produces mostly the "expected" HTML:
```html
<div style="background-color:orange; font-size: 40px;;color:blue">Hello World</div>
```

However, when the JSX is rendered from client-side routing, it strips the ill-formed style from the HTML and reports a warning in the console:
```html
<div style="color: blue;">Hello World</div>
```
```
Warning: Style property values shouldn't contain a semicolon. Try "backgroundColor: orange; font-size: 40px" instead.
    at div
```

While ultimately the problem is with the style definition, it seems like React should be more consistent with how it handles bad styles. I would expect either that the styles are present in both types of routing, or stripped and warned about in both types of routing.

## Steps To Reproduce
The steps below are in a Next.js project, but I have been able to reproduce this in Remix as well.

1. Press on "Go to Test".
2. Observe that the button text is blue, but the rest of the styles are the defaults.
3. Click the button to refresh the page.
4. Observe that the button now has an orange background and larger font size.

Link to code example: https://codesandbox.io/p/devbox/styles-bug-3kxt2g

| Client-side routing | Server-side routing |
| - | - |
| <img width="403" alt="image" src="https://github.com/user-attachments/assets/500fe2a7-1aef-445f-97a7-73add6921096"> | <img width="403" alt="image" src="https://github.com/user-attachments/assets/ca8dfee1-ed18-46c8-962c-50ca68657339"> |