sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: Making Mamba first-class citizen in PyTorch
Labels: triaged,needs research,oncall: pt2,module: higher order operators,module: pt2-dispatcher

### 🚀 The feature, motivation and pitch

[Mamba](https://arxiv.org/pdf/2312.00752.pdf) is a new SSM (State Space Model) which is developed to address Transformers’ computational inefficiency on long sequences. It has attracted more attention recently due to faster inference and linear scaling in sequence length. We are exploring how to support Mamba as first-class citizens in PyTorch. 

To better understand the gaps and coordinate these ongoing effects, we created the following doc to trace the requested features and issues. Feel free to comment if you have any feedback!
https://docs.google.com/document/d/1rNNByFrOjOQOBM6ZZqnOqc-LGMRmdnQifKfbY_KalnM/edit?usp=sharing 

cc @ezyang @msaroufim @bdhirsh @anijain2305 @zou3519 @Chillee @ydwu4 @peterbell10 @lezcano @aakhundov @chauhang
Repository: tauri
Issue: [bug] tauri 2.0beta package android problem
Labels: type: bug,status: needs triage

### Describe the bug
use create-tauri-app create a project,After packaging the Android APK for tauri 2.0 beta, the package was large (45M)

### Reproduction

_No response_

### Expected behavior

_No response_

### Full `tauri info` output

```text
[✔] Environment
    - OS: Mac OS 13.5.2 X64
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.76.0 (07dca489a 2024-02-04)
    ✔ cargo: 1.76.0 (c84b36747 2024-01-18)
    ✔ rustup: 1.26.0 (5af9b9484 2023-04-05)
    ✔ Rust toolchain: stable-x86_64-apple-darwin (default)
    - node: 18.10.0
    - yarn: 1.22.11
    - npm: 8.19.2

[-] Packages
    - tauri [RUST]: 2.0.0-beta.2
    - tauri-build [RUST]: 2.0.0-beta.1
    - wry [RUST]: 0.35.2
    - tao [RUST]: 0.25.0
    - cargo-tauri [RUST]: 1.0.3
    - @tauri-apps/api [NPM]: 2.0.0-beta.0
    - @tauri-apps/cli [NPM]: 2.0.0-beta.1

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist
    - devUrl: http://localhost:1420/
    - framework: Vue.js
    - bundler: Vite
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: tauri
Issue: [feat] Allow uncompressed resources embedded to the executable binary.
Labels: type: feature request

### Describe the problem

When use large size file, in production tauri app will compress it into its binary target. Using it will lead some time cost to uncompressed the data.

### Describe the solution you'd like

Add an option in config, let user decide to enable/disable resource compression in production.

### Alternatives considered

_No response_

### Additional context

_No response_
Repository: ollama
Issue: [Documentation request] API - <GenerateResponse> and other endpoints - options
Labels: documentation,api

Most of the parameter descriptions can be found [here](https://github.com/ollama/ollama/blob/main/docs/modelfile.md#format). However, it would be nice to have short one-liners on what each of the options do, and maybe their performance implications.
For example, I would hazard a guess that setting
```bash
curl http://localhost:11434/api/generate -d '{
    ...,
    "options": {
        ...,
        "numa": true,
        ...,
    }
}'
```
would utilise the numa library and therefore lead to some performance increase, but I cannot find any documentation to confirm this. I think that even one-liners giving some form of context for each available option would be extremely useful.
Repository: godot
Issue: Warnings in console when I exit to project manager
Labels: bug,topic:rendering

### Tested versions

v4.3.dev3.official [36e943b6b]

### System information

w10 64

### Issue description

I get some prompts in the console when I exit to the project manager but my project is all apparently fine.
I don't know if this is a bug?

![Captura5](https://github.com/godotengine/godot/assets/19652075/cc26aabc-6b2a-4480-af6a-caff5cf86b0c)


### Steps to reproduce

Import and open the project
Exit to project manager
See the console

### Minimal reproduction project (MRP)

[Test.zip](https://github.com/godotengine/godot/files/14328581/Test.zip)
Repository: flutter
Issue: [RFW] Add fontPackage argument for ArgumentDecoders.iconData
Labels: c: new feature,package,team-ecosystem,P3,p: rfw,triaged-ecosystem

### What package does this bug report belong to?

rfw

### What target platforms are you seeing this bug on?

Windows

### Have you already upgraded your packages?

Yes

### Dependency versions

<details><summary>ArgumentDecoders.iconData need fontPackage argument </summary>

"The [fontPackage] argument must be non-null when using a font family that is included in a package. This is used when selecting the font." (c) class IconData

</details>


### Steps to reproduce

1. add fontPackage in argument_decoders.dart

### Expected results

can by use a font family that is included in a package
```
fontFamily: 'Material Design Icons',
fontPackage: 'material_design_icons_flutter',
```

### Actual results

icons from package not displayed

### Code sample

<details open><summary>argument_decoders.dart </summary>

```dart
static IconData? iconData(DataSource source, List<Object> key) {
    final int? icon = source.v<int>([...key, 'icon']);
    if (icon == null) {
      return null;
    }
    return IconData(
      icon,
      fontFamily: source.v<String>([...key, 'fontFamily']),
      fontPackage: source.v<String>([...key, 'fontPackage']),
      matchTextDirection: source.v<bool>([...key, 'matchTextDirection']) ?? false,
    );
  }
```

</details>


### Screenshots or Videos

<details open>
<summary>Screenshots / Video demonstration</summary>

[Upload media here]

</details>


### Logs

<details open><summary>Logs</summary>

```console
[Paste your logs here]
```

</details>


### Flutter Doctor output

<details open><summary>Doctor output</summary>

```console
...No issues found!
```

</details>
Repository: godot
Issue: Minimizing triggered by gui_input blocks subsequent interactions
Labels: needs testing,topic:gui

### Tested versions

Reproducible in v4.2.1.stable.mono.official [b09f793f5]

### System information

Godot v4.2.1.stable.mono - Windows 10.0.22621 - GLES3 (Compatibility) - NVIDIA GeForce RTX 3080 (NVIDIA; 31.0.15.5123) - AMD Ryzen 7 3700X 8-Core Processor (16 Threads)

### Issue description

I'm trying to recreate the default OS window functionality in my custom interface by using a borderless window and recreating the top bar.
While working on this feature, I have tried to use a ColorRect to represent the minimize (orange), maximize (green) & close button (red).
In testing, the minimize function does close (although without the OS window closing animation), but upon trying to re-open the window, it acts as if the minimize ColorRect node's interactable area takes up the entire screen. Thus, preventing any other interactions other than minimizing the window again.
```gdscript
DisplayServer.window_set_mode(DisplayServer.WINDOW_MODE_MINIMIZED)
```

This bug does not happen when the function is called on a regular button press. It only seems to occur when trying to call it from a gui_input InputEventMouseButton click.
It has also occurred when using this function:
```gdscript
get_window().mode = Window.MODE_MINIMIZED
```

### Steps to reproduce

Below is the exact function I use. Connect this function to a ColorRect node's gui_input signal.
You can also use the MRP I've provided with my custom window interface.

```gdscript
func _minimize_window(event:InputEvent)->void:
	if(event is InputEventMouseButton && event.button_index == MOUSE_BUTTON_LEFT && event.pressed):
		DisplayServer.window_set_mode(DisplayServer.WINDOW_MODE_MINIMIZED)
```

### Minimal reproduction project (MRP)

I've kept a few functions just to maintain window functionality like resizing, etc.
But it's a stripped-down project with only the custom window I am trying to create.
I've included a regular button called "minimize" to show that a pressed signal works correctly, but a gui_input on the ColorRect works incorrectly.

[borderless_minimize_test.zip](https://github.com/godotengine/godot/files/14329087/borderless_minimize_test.zip)
Repository: transformers
Issue: Request to add FLMR
Labels: New model

### Model description

## Basic Information

This issue requests adding Fine-grained Late-interaction Multi-modal Retriever (FLMR).
The model leverages late interaction (as originally proposed by Stanford [ColBERT](https://github.com/stanford-futuredata/ColBERT)) to compute token-level similarity between every query token and document token, which enables more accurate retrieval relative to DPR-like systems.
 The model was proposed in [here](https://openreview.net/forum?id=IWWWulAX7g) (NeurIPS 2023) and [here](https://arxiv.org/abs/2402.08327) (a follow-up version that was pre-trained on more than ten million of multi-modal retrieval data). 


## Resources
- Project page [here](https://preflmr.github.io/)
- Official codebase [here](https://github.com/linweizhedragon/retrieval-augmented-visual-question-answering)
- The pre-trained checkpoints are [here](https://huggingface.co/models?search=PreFLMR).

## Why adding this model
1. This work has gained attention from researchers across the world. We received many requests during NeurIPS 2023 to provide an easy implementation of this model.
2. The work has been recognized by the authors of ColBERT [twitter post](https://twitter.com/lateinteraction/status/1757652639503007893)
3. There exists no implementation for late-interaction retrieval models in hf-transformers, which have been extensively researched in these years.
4. There are many requests in the original codebase [an example issue](https://github.com/LinWeizheDragon/Retrieval-Augmented-Visual-Question-Answering/issues/24)
5. As original authors, we have finished 99% of the model, including an example for indexing and searching.   Limited work is required to have it on huggingface-transformers!  #29062 




### Open source status

- [x] The model implementation is available
- [X] The model weights are available

### Provide useful links for the implementation

The PR is already here:
#29062
Repository: vscode
Issue: Suggest Widget Details: Empty Message
Labels: suggest,under-discussion

<!-- ⚠️⚠️ 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. -->
![Views](https://komarev.com/ghpvc/?username=r-microsoft-vscode-issues-205533&label=Views:)

Show a message when the details are empty, such as

_No details_

This will be useful because it is unclear if details are enabled when suggestions don't have details.

For example, if you have a suggestion that provides details, and details are disabled, it doesn't show.

This can be confused with the suggestion not actually providing any details.
Repository: kubernetes
Issue: Scheduler: Sort scheduling failure msgs to better analysis the reason why this node cannot afford pod
Labels: sig/scheduling,kind/feature,triage/accepted

### What would you like to be added?

Currently，the scheduling failure msgs from filter stage are as follows, where they are simply sorted by `sort.Strings()`.
```
0/8 nodes are available: 1 {out-of-tree-plugin-2 reason-2}, 2 Insufficient cpu, 2 {out-of-tree-plugin-1 reason-1}, 2 node(s) didn't match pod topology spread constraints, 3 Insufficient memory.
```

I want to sort the failure messages in the order of plugins in the filter stage of the profile.

Example: 
```
      - schedulerName: test-scheduler
        plugins:
          ...
          filter:
            enabled:
            - name: out-of-tree-plugin-1
            - name: out-of-tree-plugin-2
         ...
```

Then, the expected failure msgs are as follows:
```
0/8 nodes are available: 2 Insufficient cpu, 3 Insufficient memory, 2 node(s) didn't match pod topology spread constraints, 2 {out-of-tree-plugin-1 reason-1}, 1 {out-of-tree-plugin-2 reason-2}.
```


### Why is this needed?

After sorting the scheduling failure msgs according to the method proposed above, it is more convenient for us to investigate `the reason why a node cannot afford the pod accurately` without increasing the output information. 

Because we can determine the specific reason why the node cannot afford the pod one by one in the order of error messages, and we don't know which error message to start checking from before.

Example:

if nodeA can not pass the both `out-of-tree-plugin-2` and `NodeResourcesFit` plugins,  with the previous msgs:
```
0/8 nodes are available: 1 {out-of-tree-plugin-2 reason-2}, 2 Insufficient cpu, 2 {out-of-tree-plugin-1 reason-1}, 2 node(s) didn't match pod topology spread constraints, 3 Insufficient memory.
```
if we check the reason `{out-of-tree-plugin-2 reason-2}` before `Insufficient cpu` for nodeA (Due to we do not known which reason to check firstly), then we may mistakenly believe that the scheduling failure was caused by `reason-2`, rather than `Insufficient cpu`. While it actually caused by `Insufficient cpu` in this scheduling cycle.

After we using following proposed failure msgs:
```
0/8 nodes are available: 2 Insufficient cpu, 3 Insufficient memory, 2 node(s) didn't match pod topology spread constraints, 2 {out-of-tree-plugin-1 reason-1}, 1 {out-of-tree-plugin-2 reason-2}.
```
we can check failure reason  in the order mentioned above, and get the correct failure reason `Insufficient cpu` for nodeA in this scheduling cycle.

Besides, when we have this proposed order of error messages, we can also quickly identify the `failure reasonA` for the node, as it can avoid many unnecessary checks for the reason sorted after `failure reasonA`.
Repository: TypeScript
Issue: [ID-Prep] Type of variable is widened in declaration with !strictNullChecks
Labels: Help Wanted,Possible Improvement,Domain: Isolated Declarations

_The [[ID-prep]](https://github.com/microsoft/TypeScript/issues?q=is%3Aissue+%5BID-prep%5D+in%3Atitle+) set of issues aligns Declaration Emit with the forthcoming [Isolated Declarations](https://github.com/microsoft/TypeScript/issues/47947) feature._

### 🔎 Search Terms

const declaration widen

### 🕗 Version & Regression Information

- This is the behavior in every version I tried

### ⏯ Playground Link

[Playground Link](https://www.typescriptlang.org/play?&code/MYewdgzgLgBAHgZhgXhgWQIZQBYDoBOGYAJiALYAUAlDAPwwBEGARsAzAFyPECmAZgwDcMGAHpRjFmxgAfbvwYBYAFBA=#code/CYUwxgNghgTiAEAzArgOzAFwJYHtVIGYAeAFQD4AKKALnhIBp4AjWkgSlYG4BYAKDDwBnDPAAeBeAF5CFAERQmYWY1mhEstp3jwA9DvjzFs+AB8Da2UA)

### 💻 Code

```ts
declare function f3<T>(a: T, b: T): T;
const x3 = f3("abc", "def");  // "abc" | "def"
```


### 🙁 Actual behavior

`x3` is emitted as `declare const x3: string;` in declaration files but it's actually `"abc" | "def"` in source


### 🙂 Expected behavior

`x3` is emitted as `declare const x3: "abc" | "def"`


### Additional information about the issue

_No response_
Repository: TypeScript
Issue: [ID-Prep] Explicit type annotation of const replaced with initializer in declaration emit
Labels: Help Wanted,Possible Improvement,Domain: Isolated Declarations

_The [[ID-prep]](https://github.com/microsoft/TypeScript/issues?q=is%3Aissue+%5BID-prep%5D+in%3Atitle+) set of issues aligns Declaration Emit with the forthcoming [Isolated Declarations](https://github.com/microsoft/TypeScript/issues/47947) feature._

### 🔎 Search Terms

declarations type annotation const not preserved

### 🕗 Version & Regression Information

- This is the behavior in every version I tried


### ⏯ Playground Link

[Playground Link](https://www.typescriptlang.org/play?&code/MYewdgzgLgBAHgZhgXhgWQIZQBYDoBOGYAJiALYAUAlDAPwwBEGARsAzAFyPECmAZgwDcMGAHpRjFmxgAfbvwYBYAFBA=#code/KYOwrgtgBAolDeUBEBnA9hYUBuBDANmMElALxQCMUAvgNwCwAUAMZogoAuUwAXFBwE8ADsDQAzWAG1UGLHkLEAumSkzMOAkSSLaQA)

### 💻 Code

```ts
enum E { "some value" = 1 };
const e: typeof E["some value"] = E["some value"];
```


### 🙁 Actual behavior

`e` is emitted in declarations as `declare const e = E["some value"];`


### 🙂 Expected behavior

`e` should have in declarations the type that was manually declared


### Additional information about the issue

_No response_
Repository: ant-design
Issue: support for menu's subMenu "rtl" positioning
Labels: Inactive,improvement

### What problem does this feature solve?

"rtl" languages menus.
i am writing in an "rtl" language and my subMenu is always stuck to the left side of the menu item, which is not suitable for "rtl" menus.

### What does the proposed API look like?

i don't have a possible solution.

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: godot
Issue: Syntax Highlighting for custom type hints fails after linebreaks in parameter list
Labels: bug,topic:gdscript,topic:editor

### Tested versions

4.2.1

### System information

Windows 10, Godot 4.2.1, Gles3 compatibility

### Issue description

When adding typehints to function declarations the highlighting stops working if linebreaks are added:

![grafik](https://github.com/godotengine/godot/assets/11277588/c4808fbe-3cc4-46c0-a11e-81776f115a2f)
![grafik](https://github.com/godotengine/godot/assets/11277588/5901c06e-d519-48f4-8faf-97ce0f2605b5)


### Steps to reproduce

Write a function with type hints for some custom types. Add linebreaks in the parameter list

### Minimal reproduction project (MRP)

-
Repository: godot
Issue: Could not extend preloaded script (Identifier "MyClass" is not a preloaded script or class)
Labels: bug,discussion,topic:gdscript

### Tested versions

- Reproducible in: v4.3.dev3.official [36e943b6b], v4.2.1.stable.official [b09f793f5]

### System information

Godot v4.3.dev3 - Windows 11 - Vulkan (Forward+) - integrated Intel(R) Iris(R) Xe Graphics () - 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz (8 Threads)

### Issue description

I have two scripts:
```gdscript
#ClassA.gd
extends Node
```
```gdscript
#ClassB.gd
extends Node
```
I don't use class_name. Instead, I preload these classes into constants via autoload
```gdscript
#custom_classes.gd
extends Node

const Ok = preload("res://ClassA.gd")
const NotOk: GDScript = preload("res://ClassB.gd")

func _ready() -> void:
	print(Ok) # GDScript
	print(NotOk) # also GDScript
```
Then i extend one of these classes in a new file
```gdscript
#ClassC.gd
#extends CustomClasses.Ok
extends CustomClasses.NotOk
```
When using type hint (const NotOk: GDScript) I get an error: _Identifier "NotOk" is not a preloaded script or class_
![изображение](https://github.com/godotengine/godot/assets/77234360/aae44dc6-709c-407d-a71e-1be5e4005a6a)

P.S.: also constants don't show up in autocomplete tooltip

### Steps to reproduce

1. create first script, don't use class_name keyword
2. create second script and make it autoload
3. inside the autoload: preload the first nameless class/script and assign it to const with a type hint
4. try extending the preloaded class in another script
5. get an error

### Minimal reproduction project (MRP)

[MRP.zip](https://github.com/godotengine/godot/files/14331882/MRP.zip)
Repository: ant-design
Issue: Card Loading state for Extra & Actions 
Labels: Inactive,improvement

### Reproduction link

no needed
### Steps to reproduce

Basically if I apply a loading state to a card which has a **extra and action props** I want to see the loading also on that elements.


### What is expected?

Loading on all components

### What is actually happening?

Loading only on native card elements

| Environment | Info |
| --- | --- |
| antd | 5.13.3 |
| React | 18 |
| System | mac |
| Browser | chrome |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->

![Screenshot 2024-02-19 alle 15 28 28](https://github.com/ant-design/ant-design/assets/40239902/9a54ae26-c13a-4d52-b282-9e2aae5b5423)
Repository: next.js
Issue: Params prop are passed to searchParams prop while using the Edge runtime
Labels: bug

### Link to the code that reproduces this issue

https://github.com/x-priyam/nextjs-edge-params-bug

### To Reproduce

1. Create a dynamic route: `/[slug]`

1. Enable the edge runtime on the page:

   ```JSX
   export const runtime = "edge";
   ```

1. Add `params` and `searchParams` props to the default exported component:

   ```JSX
   export default function Page({
    params,
    searchParams
   }:{
    params: {
      slug: string
    },
    searchParams: {}
   }) {
     // Code
   }
   ```

1. Add a way to see the content of `searchParams` (and params too optionally)

   ```JSX
   return(
     <pre>
       {JSON.stringify(searchParams, null, "\t")}
     </pre>
   )
   ```

    _Feel free to use any method you prefer here, `console.log()`, etc._

1. Run/build the project and navigate to the appropriate page: `/anyRandomString`

### Current vs. Expected behavior

## Current:
You'll see that `searchParams` has all entries present in `params`

   ```JSON
   "searchParams": {
     "slug": "someRandomString"
   }
   ```

## Expected:
`searchParams` should be an empty object

   ```JSON
   "searchParams": {}
   ```

## tl;dr
`params` are prop used for dynamic routing, their values are going into `searchParams`. Can lead to unexpected behaviors.

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Home Single Language
Binaries:
  Node: 21.6.1
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.1.1-canary.61 // Latest available version is detected (14.1.1-canary.61).
  eslint-config-next: 14.1.0
  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)

App Router

### 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: next.js
Issue: react-refresh-runtime.development.js:645 Uncaught ReferenceError: exports is not defined
Labels: bug

### Link to the code that reproduces this issue

https://github.com/xkeshav/reaction

### To Reproduce


> npm run dev

no issue on page but  in console it gives issue 

giving this issue which takes to this file


> react-refresh-runtime.development.js:645 Uncaught ReferenceError: exports is not defined
line # 645 exports._getMountedRootCount = _getMountedRootCount


earliet it was having issue then runn `npm install next@canary` then it resolved but again this issue came 


![image](https://github.com/vercel/next.js/assets/415219/0582aebf-d3f4-472f-9af0-3dd3fe324b39)


### Current vs. Expected behavior

it should now give any issue in console.

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Pro
Binaries:
  Node: 18.17.1
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.1.0
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: N/A
Next.js Config:
  output: N/A
```


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

Not sure

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

next dev (local)

### Additional context


below info appears when run next info while i already run nthe command.
```sh
warn  - Latest canary version not detected, detected: "14.1.0", newest: "14.1.1-canary.61".
        Please try the latest canary version (`npm install next@canary`) to confirm the issue still exists before creating a new issue.
        Read more - https://nextjs.org/docs/messages/opening-an-issue
```