sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: torch.export.export() fails with dynamic shapes when more than one shape is dynamic
Labels: module: dynamic shapes,oncall: export

### 🐛 Describe the bug

Here, the example below works if I only pass batch as the dynamic shape.  
With two shapes being dynamic, it fails:

Specializations unexpectedly required (batch, audio_signal__2)! For more information, run with TORCH_LOGS="+dynamic".                                                                                                           
  - batch = L['args'][0][0].size()[0] must be specialized to 4 because the guards generated for it are too complex.                      
  - audio_signal__2 = L['args'][0][0].size()[2] must be specialized to 256 because the guards generated for it are too complex.     
    
To install NeMo toolkit, run the following: 
pip install --extra-index-url https://pypi.ngc.nvidia.com nemo_toolkit[all]

```
import torch
from nemo.core.classes import typecheck
from nemo.utils.export_utils import wrap_forward_method
from nemo.collections.asr.models import EncDecCTCModelBPE

model = EncDecCTCModelBPE.from_pretrained(model_name="stt_en_conformer_ctc_small")

model = model.eval()
wrap_forward_method(model)
model._prepare_for_export()

typecheck.set_typecheck_enabled(enabled=False)

# This has to have min=2                                                                                                                 
batch = torch.export.Dim("batch", min=2, max=64)
dynamic_shapes={'input': { 0: batch,
                           2: torch.export.Dim("audio_signal__2")
                          },
                'length': {0: batch}
                }
input_example = model.input_module.input_example(max_batch=4)

ex_model = torch.export.export(
    model, tuple(input_example),
    dynamic_shapes=dynamic_shapes,
    strict=False
)


### Versions

Pytorch nightly 05/13

cc @ezyang @avikchaudhuri @gmagogsfm @zhxchen17 @tugsbayasgalan @angelayi @suo @ydwu4
Repository: ui
Issue: [bug]:  Wrong selector for select component placeholder
Labels: bug

### Describe the bug

Just found out that tailwind selector `placeholder:...` on trigger (Select component) won't have any effect. In my case`data-[placeholder]` will solve the issue

### Affected component/components

Select

### How to reproduce

change the style of the trigger placeholder in the select component, and see if there is a change

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
WSL
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: vscode
Issue: Support multiple `SemanticTokensProvider` per document selector
Labels: feature-request,semantic-tokens

Currently there is very basic support for multiple semantic tokens provider for the same language. The first provider that computed some tokens is used. (See #135580). This feature was also requested in #135599 but didn't look like anything got pushed to fix it...

However, in reality, tokens from multiple semantic token providers need to be taken into account. For example Java annotations in the case of Spring can have JPQL, HQL or native SQL queries depending on annotation parameters and JARs on the classpath. Seems that best approach for such use case in Semantic Tokens. However, since JDT LS also has `SemanticTokensProvider` any Spring specific `SemanticTokenProvider` would conflict with the JDT LS provider.

Looking at https://github.com/microsoft/vscode/blob/main/src/vs/editor/common/services/semanticTokensProviderStyling.ts#L142 i have a feeling that the restriction of effectively having one token provider giving tokens can be lifted if switched to `SemanticTokens[]`

(cc: @martinlippert)
Repository: pytorch
Issue: Inconsistent gradients in reverse mode and forward mode AD when using `MultiheadAttention`
Labels: needs reproduction,module: autograd,module: nn,triaged

### 🐛 Describe the bug

When I use forward and reverse AD(automatic differentiation), the calculated gradients are not consistent. I'm wondering what's goning on.
```
from helper_torch import (
    RevInv,
    FwdInv,
)
from classes.torch_library import TorchLibrary
import torch


torch.random.manual_seed(44298)
def get_fn():
    embed_dim = 512
    num_heads = 16
    dropout = True
    arg_class = torch.nn.MultiheadAttention(embed_dim, num_heads, dropout=dropout, device='cpu', )
    def fn(input_0, input_1, input_2):
        fn_res = arg_class(input_0, input_1, input_2)
        return fn_res
    return fn
fn = get_fn()
input_0_tensor = torch.empty([1, 1, 512], dtype=torch.float32)
input_0_tensor.uniform_(0, 7)
input_1_tensor = torch.empty([1, 1, 512], dtype=torch.float32)
input_1_tensor.uniform_(-2, 1)
input_2_tensor = torch.empty([1, 1, 512], dtype=torch.float32)
input_2_tensor.uniform_(-1, 7)


inputs = (input_0_tensor,input_1_tensor,input_2_tensor)

rev_status, rev_value, rev_grad, rev_err = RevInv(fn, inputs)
fwd_status, fwd_value, fwd_grad, fwd_err = FwdInv(fn, inputs)
print(TorchLibrary.is_equal(rev_grad, fwd_grad))

total_difference = 0
for grad1, grad2 in zip(rev_grad, fwd_grad):
    if grad1 is not None and grad2 is not None:
        if grad1.shape == grad2.shape:
            difference = torch.norm(grad1 - grad2)
            total_difference += difference.item()
        else:
            print(grad1.shape, grad2.shape)
print("total_difference: ", total_difference)
# False
# torch.Size([512, 512]) torch.Size([512, 1])
# torch.Size([512, 1]) torch.Size([512, 512])
# total_difference:  0.0
```


### Versions

PyTorch: 2.2.0
Ubuntu: 20.04
Python: 3.10.12

cc @ezyang @albanD @gqchen @pearu @nikitaved @soulitzer @Varal7 @xmfan @mruberry @jbschlosser @walterddr @mikaylagawarecki @Lezcano @bhosmer @cpuhrsch @erichan1 @drisspg
Repository: material-ui
Issue: iOS Safari Change Tabs Swipe Gesture Affects `Modal` Component
Labels: component: drawer,browser: Safari,customization: css

### Steps to reproduce

Minimal example code:
```js
export default function App() {
  return (
    <SwipeableDrawer
      SlideProps={{
        sx: {
          height: "61.8%",
        },
      }}
      anchor="bottom"
      onOpen={() => {}}
      open
    >
      asdf
    </SwipeableDrawer>
  );
}
```

### Your environment

iOS Version: 16.6.1
Model Name: iPhone 12 Pro Max

**Search keywords**: Style CSS JS Bleed
Repository: flutter
Issue: Build the engine for macOS without the iphoneos SDK
Labels: engine,platform-mac,P3,team-engine,triaged-engine

### Steps to reproduce

1. Follow the wiki to build the engine and specify `--mac --mac-cpu arm64 --target-os mac`

### Expected results

Flutter's engine should *only* build and require stuff for macOS.

### Actual results

Flutter's engine calls xcode to find the `iphoneos` SDK.

### Other details

This is heavily needed to package the Flutter Engine in Nix on Darwin. Without it, more work would have to be put in to get iOS stuff implemented which with the limited maintainers, that is near impossible. It is much easier if the engine gets this fixed upstream.
Repository: pytorch
Issue: Triton + fresh_inductor_cache overwrites root logger level
Labels: triaged,oncall: pt2,module: inductor,upstream triton

### 🐛 Describe the bug

```
import logging
import triton
from torch._inductor.utils import fresh_inductor_cache

with fresh_inductor_cache():
    logger = logging.getLogger()
    before = logger.getEffectiveLevel()
    triton.testing.get_dram_gbps()  # overwrites
    after = logger.getEffectiveLevel()
    assert before == after, f"{before} vs {after}"
```

fresh_inductor_cache will force triton to rebuild drivers, during which triton setup will overwrite root logger level

### Versions

main

cc @ezyang @msaroufim @bdhirsh @anijain2305 @chauhang @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @peterbell10 @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire
Repository: ollama
Issue: LLAVA1.6 performance huge drop after export/import using ModelFile
Labels: bug

### What is the issue?

Using ModelFile to change the temperature of LLAVA 1.6 or importing LLAVA from a GGUF file significantly reduces performance. This issue likely arises because the import operation treats the LLAVA 1.6 model as LLAVA 1.5 or earlier, ignoring the image-splitting into four parts. Please address this bug.

### OS

Linux

### GPU

Nvidia

### CPU

AMD

### Ollama version

Any version
Repository: svelte
Issue: Critial: static analyze some.svelte.ts 
Labels: documentation

### Describe the bug

This code throw Error when file named with .ts extention:

```ts
class ReactiveRecord {
	store = $state(null);

}

export const create = () => {
	return new ReactiveRecord();
}
```
CompileError: `$state(...)` can only be used as a variable declaration initializer or a class field

If the file is named .js, everything is working correctly.

### Reproduction

I've been researching the internal files and this is what I found:

_svelte\src\compiler\phases\2-analyze:_

```js
function validate_call_expression(node, scope, path) {
//...
	if (
		rune === '$state' ||
		rune === '$state.frozen' ||
		rune === '$derived' ||
		rune === '$derived.by'
	) {
		if (parent.type === 'VariableDeclarator') return;
		if (parent.type === 'PropertyDefinition' && !parent.static && !parent.computed) return;
		console.log("parent", parent);
		e.state_invalid_placement(node, rune);
	}
//...
}
```

### Logs

```
"parent": Node {
  type: 'AssignmentExpression',
  operator: '=',
  left: Node {
    type: 'MemberExpression',
    object: Node {
      type: 'ThisExpression',
    },
    property: Node {
      type: 'Identifier',
      name: 'store'
    },
    computed: false,
    optional: false
  },
  right: Node {
    type: 'CallExpression',
    callee: Node {
      name: '$state'
    },
    arguments: [ [Node] ],
    optional: false
  }
}
```

### System Info

```shell
Node: 20.11.1
svelte: 5.0.0-next.132
ts: 5.4.5
tsconfig: auto, included in create@svelte without custom editions

import { vitePreprocess } from "@sveltejs/vite-plugin-svelte";
Calling the Error for use with and without this preprocessor
```


### Severity

annoyance
Repository: storybook
Issue: error SB_PREVIEW_API_0010  due to indentation during Chromatic Extract process
Labels: bug,has workaround,story index,sev:S3

### Describe the bug

We hit error:

```
Error: Error: page.evaluate: SB_PREVIEW_API_0010 (MissingStoryFromCsfFileError): 
Couldn't find story matching id 'library-2-0-animatedtypingwrapper--default' after importing a CSF file.
```

The Storybook was published correctly, but the Chromatic verification step was failing.
Verification could not handle subdirectories properly:

```
[
{
directory: getFrontendPath('images'),
files: '**/*.stories.@(mdx|tsx|ts|jsx|js)',
titlePrefix: 'Icons',
},
{
directory: getFrontendPath('styles'),
files: '**/*.stories.@(mdx|tsx|ts|jsx|js)',
titlePrefix: 'Design tokens',
},
{
directory: getFrontendPath('components/lib/new'),
files: '**/*.stories.@(mdx|tsx|ts|jsx|js)',
titlePrefix: 'Library 2.0',
},
{
directory: getFrontendPath('components/lib'),
files: '**/*.stories.@(mdx|tsx|ts|jsx|js)',
titlePrefix: 'Library',
},
],

```

It places all stories in components/lib under Library EXCEPT all under components/lib/new. 
This works in Storybook only.

Replacing it with 

```
[
{
directory: getFrontendPath('images'),
files: '**/*.stories.@(mdx|tsx|ts|jsx|js)',
titlePrefix: 'Icons',
},
{
directory: getFrontendPath('styles'),
files: '**/*.stories.@(mdx|tsx|ts|jsx|js)',
titlePrefix: 'Design tokens',
},
{
directory: getFrontendPath('components/lib/new'),
files: '**/*.stories.@(mdx|tsx|ts|jsx|js)',
titlePrefix: 'Library 2.0',
},
{
directory: getFrontendPath('components/lib'),
files: '!(new)/*.stories.@(mdx|tsx|ts|jsx|js)',
titlePrefix: 'Library',
},
],
```

Note the "!(new)" in the components/lib section solves this and I can now finally deploy the storybook and verify it. 
Without the fix Chromatic adds the story to both the top folder and the nested folder, which is probably what causes the issue. 

Without fix (confuses chromatic):

```
Library
- FirstComponent
- subdir/
- SecondComponent

Library 2.0
- SecondComponent
```

With fix (publish works):

```
Library
- FirstComponent

Library 2.0
- SecondComponent
```

### To Reproduce
[chromatic-issue.zip](https://github.com/storybookjs/storybook/files/15304965/chromatic-issue.zip)


### System

N/A


### Additional context

Refer to internal task: [AP-4626](https://linear.app/chromaui/issue/AP-4626/customer-hits-error-sb-preview-api-0010-due-to-indentation)
Repository: godot
Issue: Unexpected change of color for editable children in Scene Tree dock in 3.6-beta5
Labels: discussion,topic:editor

### Tested versions

v3.6.beta5.official [2a347ab86]

### System information

w10 64

### Issue description

Previously the node names always appeared obscured, now it looks like this.
I don't see this change reflected in the list of changes, I guess it's a bug.

![Captura5](https://github.com/godotengine/godot/assets/19652075/8d730243-196f-422d-a12c-d94d31a6cfbb)


### Steps to reproduce

...

### Minimal reproduction project (MRP)

...
Repository: tensorflow
Issue: Aborted (core dumped) in `tf.raw_ops.FusedPadConv2D`
Labels: stat:awaiting tensorflower,type:bug,comp:ops,TF 2.16

### Issue type

Bug

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

Yes

### Source

source

### TensorFlow version

tf 2.16.1

### Custom code

Yes

### OS platform and distribution

Ubuntu 20.04

### Mobile device

_No response_

### Python version

_No response_

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

When `input` dimension is less than 4， it will cause abort.

### Standalone code to reproduce the issue

```shell
import tensorflow as tf

mode = "REFLECT"
strides = [1, 1, 1, 1]
padding = "VALID"
input = tf.constant(1.5e+300, shape=[], dtype=tf.float64)
paddings = tf.constant(65534, shape=[4,2], dtype=tf.int32)
filter = tf.constant([], shape=[1,1,0,1,0], dtype=tf.float64)
tf.raw_ops.FusedPadConv2D(input=input, paddings=paddings, filter=filter, mode=mode, strides=strides, padding=padding)
```


### Relevant log output

```shell
2024-05-14 08:19:37.953832: F tensorflow/core/framework/tensor_shape.cc:357] Check failed: d < dims() (1 vs. 0)
Aborted (core dumped)
```
Repository: tensorflow
Issue: Aborted (core dumped) in `QuantizedInstanceNorm`
Labels: stat:awaiting tensorflower,type:bug,comp:ops,TF 2.16

### Issue type

Bug

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

Yes

### Source

source

### TensorFlow version

tf 2.16.1

### Custom code

Yes

### OS platform and distribution

Ubuntu 20.04

### Mobile device

_No response_

### Python version

_No response_

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

Abort is triggered when the input x does not meet the condition of dimension 4.

### Standalone code to reproduce the issue

```shell
import tensorflow as tf

output_range_given = False
given_y_min = 0
given_y_max = 0
variance_epsilon = 1e-05
min_separation = 0.001
x = tf.constant([], shape=[0,0,0,1,1,0,0,0,11,9], dtype=tf.quint8)
x_min = tf.constant(-3.5e+35, shape=[], dtype=tf.float32)
x_max = tf.constant(0, shape=[], dtype=tf.float32)
tf.raw_ops.QuantizedInstanceNorm(x=x, x_min=x_min, x_max=x_max, output_range_given=output_range_given, given_y_min=given_y_min, given_y_max=given_y_max, variance_epsilon=variance_epsilon, min_separation=min_separation)
```


### Relevant log output

```shell
2024-05-14 08:25:37.034690: F tensorflow/core/framework/tensor_shape.cc:45] Check failed: NDIMS == dims() (4 vs. 10)Asking for tensor of 4 dimensions from a tensor of 10 dimensions
Aborted (core dumped)
```
Repository: rust
Issue: Reporting a reason of error with an irrelevant constraint in this example
Labels: A-diagnostics,T-compiler

### Code

```Rust
trait Binder<Args>{
   fn invoke(&self,args:Args);
}

impl<T,U,F> Binder<(T,U)> for F 
where F:Fn(T,U,& dyn Binder<(T,U)>)
{
  fn invoke(&self,args:(T,U)) {
     let (t,u) = args;
     self(t,u,self)
  }
}
fn main(){
   let f = |a,b,c|{};
   f.invoke((1,2));
}
```


### Current output

```Shell
--> src/main.rs:15:4
   |
14 |     let f = |a,b,c|{};
   |             ------- doesn't satisfy `<_ as FnOnce<(_, _, &dyn Binder<(_, _)>)>>::Output = ()` or `_: Binder<(_, _)>`
15 |     f.invoke((1,2));
   |       ^^^^^^
   |
note: trait bound `<{closure@src/main.rs:14:10: 14:17} as FnOnce<(_, _, &dyn Binder<(_, _)>)>>::Output = ()` was not satisfied
  --> src/main.rs:6:9
   |
5  | impl<T,U,F> Binder<(T,U)> for F 
   |             -------------     -
6  | where F:Fn(T,U,& dyn Binder<(T,U)>)
   |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^ unsatisfied trait bound introduced here
   = help: items from traits can only be used if the trait is implemented and in scope
note: `Binder` defines an item `invoke`, perhaps you need to implement it
  --> src/main.rs:1:1
   |
1  | trait Binder<Args>{
   | ^^^^^^^^^^^^^^^^^^
```


### Desired output

```Shell
This example should be successfully inferred from the context
```


### Rationale and extra context

_No response_

### Other cases

_No response_

### Rust Version

```Shell
rustc 1.78.0 (9b00956e5 2024-04-29)
binary: rustc
commit-hash: 9b00956e56009bab2aa15d7bff10916599e3d6d6
commit-date: 2024-04-29
host: x86_64-apple-darwin
release: 1.78.0
LLVM version: 18.1.2
```


### Anything else?

If manually annotate the parameter types, the example can be compiled
```rust
fn main(){
   	let f = |a,b,c:& dyn Binder<(i32,i32)>|{};
	f.invoke((1,2));
}
````
Repository: flutter
Issue: `ITMS-91065: Missing signature` when using plugins on the "privacy-impacting" list in add-to-app
Labels: platform-ios,P2,customer: castaway,team-ios,triaged-ios

### Use case

I uploaded my app using: url_launcher to testflight, however Apple rejected it with following reason:

ITMS-91065: Missing signature - Your app includes “Frameworks/url_launcher_ios.framework/url_launcher_ios”, which includes url_launcher_ios, an SDK that was identified in the documentation as a privacy-impacting third-party SDK. If a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a signature file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a signature. For details about verifying the code signature for a third-party SDK, visit: https://developer.apple.com/documentation/xcode/verifying-the-origin-of-your-xcframeworks.

### Proposal

Please help to resolve this issue?

Updated: Version ` url_launcher: ^6.2.6` and url_launcher_ios in pubspec.lock is: 6.3.0:
`  url_launcher_ios:
    dependency: transitive
    description:
      name: url_launcher_ios
      sha256: "7068716403343f6ba4969b4173cbf3b84fc768042124bc2c011e5d782b24fe89"
      url: "https://pub.dev"
    source: hosted
    version: "6.3.0"`
Repository: ui
Issue: [Accessibility]: Use <input list=""> or <select multiple > instead of combo-box to ensure accessibility across all devices
Labels: bug

### Describe the bug

I'm using [SonarQube Linter ](https://www.sonarsource.com/products/sonarlint/) that helps me to lint my code. It raises this accessiblity issue in the [Combobox component](https://ui.shadcn.com/docs/components/combobox.

![image](https://github.com/shadcn-ui/ui/assets/20143684/f1160e06-72cd-4ffc-990c-9266844cceff)


### Affected component/components

Combobox

### How to reproduce

![image](https://github.com/shadcn-ui/ui/assets/20143684/97f39c67-6f87-4683-9703-ab73a981f9f0)


### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
VS code.
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: vscode
Issue: Context menus make webview on the side steal focus
Labels: bug,webview

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
```
Version: 1.90.0-insider
Commit: bbc4ba1eff648ee542972589216f211b7a6a08f2
Date: 2024-05-14T05:47:50.971Z
Electron: 29.3.1
ElectronBuildId: 9464424
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Linux x64 6.8.8-300.fc40.x86_64
```
This bug has also been confirmed to occur on 1.88 and 1.89, but not 1.87.

Steps to Reproduce:

1. Open an untitled document and a webview panel next to it (for example, a markdown document and its markdown preview)
2. Right click in the untitled document, in the side bar or click an entry with a menu in the title bar
3. Observe that the webview panel becomes focused and the title bar entries jump over to the webview panel

![focus_bug](https://github.com/microsoft/vscode/assets/10852073/449018c4-8425-4d5b-bb91-0cd0b9fcaa98)

Context:

In the VS Code extension for the Lean 4 programming language and theorem prover, we use a webview to provide additional information about the Lean document that the user is currently working on. We also use a title bar menu entry for all of our commands. The webview stealing the focus from the text document creates several very annoying issues while working on Lean documents:
- Right clicking an identifier in the Lean document and selecting "Go to Definition", "Find References" or "Show Call Hierarchy" will open documents in the tab group of the webview, not that of the editor, covering the webview and displaying the contents of the opened file in a panel that is typically smaller than the editor panel and probably too small to read code
- Right clicking to paste something in the search sidebar view and then clicking a search result entry will also shift the focus and open the document in the wrong pane
- When clicking the title bar menu entry, the entry suddenly shifts away underneath the cursor to the webview panel, which is very disorientating

Original report at leanprover/vscode-lean4#438.

Potentially related issue: #210108