sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: material-ui
Issue: [joy-ui][Theme] Components use radius 'sm' irrespective of their own size. 
Labels: on hold,package: joy-ui,customization: theme

### Steps to reproduce

Link to live example: https://stackblitz.com/edit/github-9jgg4d?file=src%2Findex.tsx

Steps:
1. Inspect each of the size variants of the components button and input. 
2. Notice all components have a radius of 0px irrespective of their own size. This is the value of the `'sm'` prop in the theme's radius object. `var(--joy-radius-sm)`


### Current behavior

Components like button, input, etc. all use theme radius 'sm' irrespective of their own size ('sm', 'md', 'lg').

### Expected behavior

Components like button, input, etc. should (I think) use the theme's size radius appropriate for their own size. E.g `<Button size='lg'>` would use theme radius 'lg' as its radius.

At least, that's my assumption of how theme radius works 🙈 

### Context

Use the JoyUI theme object to theme my app.
Specifically here, to set the radius property for each size variant once (in the theme radius object) and have it apply to all components without the need to provide radius style override for components individually.

![Theme Radius](https://github.com/mui/material-ui/assets/17382173/456582c4-fb20-43c6-816b-a7754133da7c)


### Your environment

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
System:
    OS: macOS 14.3
  Binaries:
    Node: 20.9.0 - ~/.nvm/versions/node/v20.9.0/bin/node
    npm: 10.1.0 - ~/.nvm/versions/node/v20.9.0/bin/npm
    pnpm: Not Found
  Browsers:
    Chrome: 123.0.6312.106
    Edge: Not Found
    Safari: 17.3
  npmPackages:
    @emotion/react: ^11.11.3 => 11.11.4 
    @emotion/styled: ^11.11.0 => 11.11.5 
    @mui/base:  5.0.0-beta.40 
    @mui/core-downloads-tracker:  5.15.14 
    @mui/icons-material: ^5.15.14 => 5.15.14 
    @mui/joy: ^5.0.0-beta.32 => 5.0.0-beta.32 
    @mui/material: ^5.15.14 => 5.15.14 
    @mui/private-theming:  5.15.14 
    @mui/styled-engine:  5.15.14 
    @mui/system:  5.15.14 
    @mui/types:  7.2.14 
    @mui/utils:  5.15.14 
    @mui/x-date-pickers: ^6.19.0 => 6.19.8 
    @types/react: ^18.2.74 => 18.2.74 
    react: ^18.2.0 => 18.2.0 
    react-dom: ^18.2.0 => 18.2.0 
    typescript:  5.4.3 
```
</details>


**Search keywords**: joy-ui radius theme
Repository: rust
Issue: Tracking issue for RFC 3621: `derive(CoercePointee)`
Labels: T-lang,C-tracking-issue,S-tracking-impl-incomplete,B-experimental,F-derive_coerce_pointee

This is a tracking issue for `#[derive(CoercePointee)]`.

The feature gate for the issue is `#![feature(derive_coerce_pointee)]`.

It was formerly known as:
- `#[derive(UnsizeInner)]`
- `#[derive(SmartPtr)]`
- `#[feature(derive_smart_pointer)]`

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

### Steps

- [ ] Implement the language experiment.
  - https://github.com/rust-lang/rust/pull/125575
  - https://github.com/rust-lang/rust/pull/125048
  - https://github.com/rust-lang/rust/pull/123472
- [x] Accept an RFC.
  - https://github.com/rust-lang/rfcs/pull/3621
- [ ] Decide on a final name.
  - https://github.com/rust-lang/rust/issues/129104
- [ ] 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

### Unresolved Questions

- [ ] is the derive name good? Should it be more general than "smart pointer"? (Do not discuss on this issue, open a zulip thread or separate GitHub issue)
  - https://github.com/rust-lang/rust/issues/129104

### Related

- https://github.com/rust-lang/rfcs/pull/3621
- https://github.com/rust-lang/rust/pull/125575
- https://github.com/rust-lang/rust/pull/125048
- https://github.com/rust-lang/rust/pull/123472
- https://github.com/rust-lang/rust/pull/127283
Repository: flutter
Issue: [RFW] Add support to use [null] in switch syntax.  
Labels: c: new feature,package,c: proposal,team-ecosystem,P2,p: rfw,triaged-ecosystem

### Use case

Use `null` keyword with [switch]

We'd like to render a list of `dogs` which optionally can have `description` data. Remote widgets:
```
widget dogs { selected = 0 } = Column(children: [
  ...for item in data.items:
    dog(
      name: item.name,
      breed: item.breed,
      description: item.description,
    )
]);

dog = Container(
  child: Column(
    children: [
      Text(text: args.name),
      Text(text: args.breed),
      switch args.description {
        null: SizedBox(),
        default: Text(text: args.description),
      }
    ]
  ),
);
```

Data Model:
```
{
  "items": [
    {
      "name": // ...
      "breed": // ...
      "description": //...
    },
    {
      "name": // ...
      "breed": // ...
    }
  ]
}
```
Right now this won't compile.
### Proposal

Propose to allow null values with [switch] syntax.
Repository: pytorch
Issue: DISABLED test_dtensor_op_db_nn_functional_multi_head_attention_forward_cpu_float32 (__main__.TestDTensorOpsCPU)
Labels: oncall: distributed,triaged,module: flaky-tests,skipped

Platforms: linux

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

Over the past 3 hours, it has been determined flaky in 2 workflow(s) with 4 failures and 2 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_dtensor_op_db_nn_functional_multi_head_attention_forward_cpu_float32`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.


Test file path: `distributed/_tensor/test_dtensor_ops.py`

cc @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @H-Huang @kwen2501 @awgu @penguinwu @fegin @XilunWu @wanchaol @fduwjj @wz337 @tianyu-l @wconstab @yf225 @chauhang @clee2000
Repository: pytorch
Issue: DISABLED test_shufflenet_v2 (__main__.TORCH_NN_MODULE)
Labels: module: onnx,triaged,module: flaky-tests,skipped

Platforms: linux

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

Over the past 3 hours, it has been determined flaky in 3 workflow(s) with 3 failures and 3 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_shufflenet_v2`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.


Test file path: `onnx/test_fx_to_onnx_with_onnxruntime/TestFxToOnnxWithOnnxRuntime_op_level_debug_True_dynamic_shapes_False_model_type_TorchModelType.py` or `onnx/test_fx_to_onnx_with_onnxruntime`

cc @clee2000
Repository: deno
Issue: `deno add` - support `http:` and `https:` specifiers
Labels: good first issue,feat

Currently `deno add` only works with `jsr:` and `npm:` specifiers.

We should add an ability to do `deno add https://deno.land/x/foo/bar.ts`.

To do this, we should leverage existing `infer_name_from_url()` helper, that is already used in `deno install` and `deno compile`
https://github.com/denoland/deno/blob/d3d3582b1f1b71b18d8d89cdf8e14f112b8f40a7/cli/tools/installer.rs#L131-L185
Repository: storybook
Issue: [Bug]: Same repository failed with error if run locally but fine if run on stackblitz
Labels: bug,needs triage

### Describe the bug

I had this error when configuring storybook 8 with nextjs 14 and mui v5, and the same error occured, so I created a mini reproduction. Interestingly, though the mini reproduction are the same repo but failed to run with error when run locally but fine when run on stackblitz.

Here is the error when run locally:
```
TypeError
Cannot read properties of undefined (reading 'style')
Call Stack
 ./src/app/themes.ts
  main.iframe.bundle.js:323:180
 options.factory
  runtime~main.iframe.bundle.js:655:31
 __webpack_require__
  runtime~main.iframe.bundle.js:28:33
 fn
  runtime~main.iframe.bundle.js:313:21
 ./.storybook/preview.ts
  main.iframe.bundle.js:36:73
 options.factory
  runtime~main.iframe.bundle.js:655:31
 __webpack_require__
  runtime~main.iframe.bundle.js:28:33
 fn
  runtime~main.iframe.bundle.js:313:21
 PreviewWeb.getProjectAnnotations
  main.iframe.bundle.js:446:2081
 PreviewWeb.getProjectAnnotationsOrRenderError
  runtime.js:118:6367
```

### To Reproduce

you can run this repository locally [here](https://github.com/AnthonyZhang220/storybook_mini_reproduction)
here is the link when run on stackblitz: [link](https://stackblitz.com/~/github.com/AnthonyZhang220/storybook_mini_reproduction)

### System

```bash
local machine system:
Storybook Environment Info:

  System:
    OS: Windows 11 10.0.22631
    CPU: (12) x64 AMD Ryzen 5 7600 6-Core Processor
  Binaries:
    Node: 18.17.1 - C:\Program Files\nodejs\node.EXE
    npm: 9.6.7 - C:\Program Files\nodejs\npm.CMD <----- active
  Browsers:
    Edge: Chromium (123.0.2420.65)
  npmPackages:
    @storybook/addon-essentials: ^8.0.5 => 8.0.5
    @storybook/addon-interactions: ^8.0.5 => 8.0.5
    @storybook/addon-links: ^8.0.5 => 8.0.5
    @storybook/addon-onboarding: ^8.0.5 => 8.0.5
    @storybook/addon-themes: ^8.0.5 => 8.0.5
    @storybook/blocks: ^8.0.5 => 8.0.5
    @storybook/nextjs: ^8.0.5 => 8.0.5
    @storybook/react: ^8.0.5 => 8.0.5
    @storybook/test: ^8.0.5 => 8.0.5
    eslint-plugin-storybook: ^0.8.0 => 0.8.0
    storybook: ^8.0.5 => 8.0.5

stackblitz remote machine system
Storybook Environment Info:

  System:
    OS: Linux 5.0 undefined
    CPU: (6) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.18.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm <----- active
    pnpm: 8.15.3 - /usr/local/bin/pnpm
  npmPackages:
    @storybook/addon-essentials: ^8.0.5 => 8.0.5 
    @storybook/addon-interactions: ^8.0.5 => 8.0.5 
    @storybook/addon-links: ^8.0.5 => 8.0.5 
    @storybook/addon-onboarding: ^8.0.5 => 8.0.5 
    @storybook/addon-themes: ^8.0.5 => 8.0.5 
    @storybook/blocks: ^8.0.5 => 8.0.5 
    @storybook/nextjs: ^8.0.5 => 8.0.5 
    @storybook/react: ^8.0.5 => 8.0.5 
    @storybook/test: ^8.0.5 => 8.0.5 
    eslint-plugin-storybook: ^0.8.0 => 0.8.0 
    storybook: ^8.0.5 => 8.0.5
```


### Additional context

_No response_
Repository: PowerToys
Issue: Key Remaping falls asleep
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.79

### Installation method

PowerToys auto-update, Chocolatey

### Running as admin

Yes

### Area(s) with issue?

General

### Steps to reproduce

I have as a shortcut remaping the Win+Shift+S (snipping tool) remapped to  Ctrl+PrintScreeen (ShareX). PowerToys is set to start at startup always run as administrator.

### ✔️ Expected Behavior

To take a ShareX screenshot

### ❌ Actual Behavior

Opens the snipping tool (even thought it is not installed to my computer)

### Other Software

_No response_
Repository: flutter
Issue: Deprecate router parameters in favor of routerConfig
Labels: framework,f: routes,c: proposal,P2,team-framework,triaged-framework

It's still common to see code that uses `routeInformationProvider`, `routeInformationParser`, and `routerDelegate`. We should deprecate these and recommend `routerConfig` instead. See https://github.com/flutter/games/pull/42 for an example.

cc: @chunhtai @hangyujin
Repository: deno
Issue: Using `deno add` then importing dep in jupyter notebook does not take new deno.json into account
Labels: bug,lsp,deno jupyter

1. Open a jupyter notebook with a deno.json.
2. Run `deno add @std/collections`
3. Import `@std/collections`.
4. Cache it.
5. Run the cell in the notebook. The following error will occur.

```
Stack trace:
TypeError: Relative import path "@std/collections" not prefixed with / or ./ or ../ and not in import map from "file:///.../$deno$repl.ts"
    at async <anonymous>:2:19
```

For some reason I had to restart vscode completely for this change to take effect and restarting the deno language server had no effect.

Version: Deno 1.42.1+86bc7a4
Repository: TypeScript
Issue: Array prototype extensions fail circularly with `...args: T[]`, but not `args: T[]`
Labels: Possible Improvement

### 🔎 Search Terms

Typescript array prototype extension spread rest variadic parameter circular failure TS2310 version 5.4.3

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about circular compilation failures

I've added two playground links; the first works, the second fails. The *only* difference between the snippets is receiving an array `T[]` as a spread argument vs a single argument.

### ⏯ Playground Link

Working: https://www.typescriptlang.org/play?#code/PTAEBUAsEsGdQO4HsBOBrWAuAUAYyQHawAuoBApggLLnGRIAm8AvKAN7ahegCGDDAHnAA+ABR04mCAG0AugBpQANx4AbAK7ksM2QEop4dqAmwAdAAd1sSKNN2VGrboDcoFLXUoCytZtjSABllXAF9sEOdsYgBPc3JQADlKAEEUFB5omjpGFmNY8iQAMzJKLPomSOgCYnIUQp5ceNT06KFhUHIADxqCJkSUtIyynPYI7GwAeQAjACtyXGJTBnJCqvIABRQkOJQY0WaMiy3iJBi4xQByPgYLxTYOgnUAW1qeKdVyKXrVWHJFBBQ0GIbw+UmIKE0igcmikFGotHKZmuoBCLnG+CIpCe0WaUhIgIIAHM5KBWHJItjmqZrqJpKArlNcLd6ctCsyLoSYBdQHpInhCLAkB9TKokITRPdKWkUS4gA

Failing: https://www.typescriptlang.org/play?#code/PTAEBUAsEsGdQGYENoBtYC4BQBjA9gHawAuoBApgO4Cy5xkeAJvALygDeWo3oSjjAHnAA+ABT04GCAG0AugBpQAOhUA3JKgCu5TDNkBKKeA6gJsJQAdNsSKJVL1WnfoDcoAE51N7gqEfbYaQAGWTcAXywwlyxiAE8LclAAOSoAQXd3JFjaeiZWU3jyPAQyKhyGZmjoAmJyd2QcRPTM2KFhUHIAD1qCZmS0jKzyvI4orCwAeQAjACtyHGIlRnIEavIABXc8BPc40Wasyy3iPDiExQByPkYLxXYOgk0AWzqkKdRyKWR0ckVKd2gxDeHykxHc2kU-k+pRodAq5muoDCrnG+CIpCesWaUhIAIIAHM5KA2HJopjmkprqIrlMcLdQBdlgh6Rd8TALijcIRYHgPkpUHh8aJ7uSMkjXEA

### 💻 Code

Failing:
```ts
const newMethods = {
    add<T>(this: T[], ...values: T[]): T { this.push(...values); return values[0]; }
};
type NewArrayMethods = typeof newMethods;
interface Array<T> extends NewArrayMethods {};

Object.defineProperty(Array.prototype, 'add', { enumerable: false, writable: true, value: newMethods.add });

const myArr: string[] = [];
myArr.add('abc', 'def', 'ghi');

console.log({ myArr });
```

Working (only difference is `...values: T[]` is now `values: T[]` - without `...`):
```ts
const newMethods = {
    add<T>(this: T[], values: T[]): T { this.push(...values); return values[0]; }
};
type NewArrayMethods = typeof newMethods;
interface Array<T> extends NewArrayMethods {};

Object.defineProperty(Array.prototype, 'add', { enumerable: false, writable: true, value: newMethods.add });

const myArr: string[] = [];
myArr.add([ 'abc', 'def', 'ghi' ]);

console.log({ myArr });
```


### 🙁 Actual behavior

Example using `...values: T[]` fails to compile!

### 🙂 Expected behavior

Both examples should compile successfully.

### Additional information about the issue

_No response_
Repository: go
Issue: cmd/compile: static allocation should work with constant propagation and inlining
Labels: Performance,NeedsInvestigation,compiler/runtime

### Go version

go1.22.0

### Output of `go env` in your module/workspace:

```shell
GOOS=linux
GOARCH=amd64
```


### What did you do?

[Run the following benchmark](https://go.dev/play/p/tikT265hRog):
```go
package main

import "testing"

type Option interface{ isOption() }

type maxWindowSize uint64

func (maxWindowSize) isOption() {}

func MaxWindowSize(n uint64) Option { return maxWindowSize(n) }

var opt Option

func BenchmarkFunc(b *testing.B) {
	b.ReportAllocs()
	for i := 0; i < b.N; i++ {
		opt = MaxWindowSize(1024)
	}
}

func BenchmarkDirect(b *testing.B) {
	b.ReportAllocs()
	for i := 0; i < b.N; i++ {
		opt = maxWindowSize(1024)
	}
}
```

### What did you see happen?

I see:
```
BenchmarkFunc-24      	109294134	        11.11 ns/op	       8 B/op	       1 allocs/op
BenchmarkDirect-24    	1000000000	         0.4708 ns/op	       0 B/op	       0 allocs/op
```

### What did you expect to see?

I expect to see:
```
BenchmarkFunc-24      	1000000000	         0.4708 ns/op	       0 B/op	       0 allocs/op
BenchmarkDirect-24    	1000000000	         0.4708 ns/op	       0 B/op	       0 allocs/op
```
The `MaxWindowSize` function is inlineable, so I would expect it to be identical to declaring a `maxWindowSize` literal directly.

This seems to be an odd interaction between static allocations, constant propagation, and inlining. I'm not sure if the title properly reflects what's going on.
Repository: vscode
Issue: Image attachments in markdown are not uniquely named
Labels: feature-request,notebook-markdown

### Applies To

- [X] Notebooks (.ipynb files)
- [ ] Interactive Window and\/or Cell Scripts (.py files with \#%% markers)

### What happened?

Pasting an image into a markdown cell in a notebook in VS Code yields something like this:

```
![image.png](attachment:image.png)
```

Pasting an image in JupyterLab yields a unique name for each image:

```
![image.png](attachment:4300d43e-b0fc-41d3-aaf2-5332b457888b.png)
```

Having a unique name for each image is helpful when extracting them from the notebook, and possibly also helpful for https://github.com/microsoft/vscode/issues/209455?

Ideally the alttext would be left out when copying in the image as well, since this is displayed by some systems like quarto, but it is meaningless to display "image.png" as a caption. It would be better if it was empty: `![](attachment:4300d43e-b0fc-41d3-aaf2-5332b457888b.png)`

### VS Code Version

Version: 1.88.0-insider

### Jupyter Extension Version

2024.2.0

### Jupyter logs

_No response_

### Coding Language and Runtime Version

_No response_

### Language Extension Version (if applicable)

_No response_

### Anaconda Version (if applicable)

_No response_

### Running Jupyter locally or remotely?

Local
Repository: ant-design
Issue: [✨Feature Request] Responsive option for `Descriptions`'s `size` prop
Labels: 💡 Feature Request,Inactive

### What problem does this feature solve?

`default` / `middle`'s horizontal padding is too large for small screens, but `small`'s padding is just to small for large screens.
Due to the fact only `labelStyles` / `contentStyles` are provided, it's pretty hard to overwrite with media queries (no `classNames` option available).
The best way is to provide option in the responsive way.

### What does the proposed API look like?

```ts
type Size = 'middle' | 'small' | 'default';
export interface DescriptionsProps {
  size?: Size | Partial<Record<Breakpoint, Size>>
}
```

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: go
Issue: proposal: slices: add Trim, TrimRight, and TrimLeft
Labels: Proposal

### Proposal Details

I propose the addition of:
```go
// Trim returns a slice with all leading and trailing elements of s contained in v removed.
func Trim[S ~[]E, E comparable](s S, v ...E) S

// TrimLeft returns a slice with all leading elements of s contained in v removed.
func TrimLeft[S ~[]E, E comparable](s S, v ...E) S

// TrimRight returns a slice with all trailing elements of s contained in v removed.
func TrimRight[S ~[]E, E comparable](s S, v ...E) S

// TrimFunc returns a slice with all leading and trailing elements of s that satisfy f removed.
func TrimFunc[S ~[]E, E any](s S, f func(E) bool) bool

// TrimLeftFunc returns a slice with all leading elements of s that satisfy f removed.
func TrimLeftFunc[S ~[]E, E any](s S, f func(E) bool) bool

// TrimRightFunc returns a slice with all trailing elements of s that satisfy f removed.
func TrimRightFunc[S ~[]E, E any](s S, f func(E) bool) bool
```

These functions match similar functions found in the "bytes" and "strings" packages:
* `Trim`
* `TrimLeft`
* `TrimRight`
* `TrimFunc`
* `TrimLeftFunc`
* `TrimRightFunc`