sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: transformers
Issue: Mamba Models - Missing MambaForSequenceClassification
Labels: Feature request

### Feature request

Many prominent transformers (e.g. BERT) under the transformers library have specific implementations for SequenceClassification. I believe implementing these could potentially save a huge amount of time in the community.

### Motivation

I have been using the transformers library for tasks in biology or healthcare that required elegant refactoring of the current transformers library which has made me quite familiar with the internal infrastructure used to connect everything. Recently, I came upon the Mamba model and it seems these sub-models are missing.

### Your contribution

I am currently implementing MambaforSequenceClassification using the standard transformers library design patterns and will make a PR. You could assign this issue to me!
Repository: godot
Issue: Fog is weird in double precision
Labels: bug,topic:rendering,needs testing,topic:3d

### Tested versions

- Reproducible https://github.com/V-Sekai/godot/commit/1d265a7208febe4c0dba90066e02a91cc532c1cd (doubles)
- Not reproducible: https://github.com/godotengine/godot/releases/tag/4.2.2-stable (single)

### Untested versions but suspicious

https://github.com/godotengine/godot/releases/tag/4.2.2-stable (double)

### System information

Windows 11, Nvidia 3090, Vulkan forward+

### Issue description

https://youtu.be/cNQ9ksd5cAw

Fog seems to be not working correctly. Seems to be split into layers instead of being even.

### Steps to reproduce

Turning on fog causes this to happen on https://github.com/V-Sekai/godot-crappy-contraptions/commit/0fff44fa1bf2e70c2ce295a4bbfdc27cd07dbf1b

### Minimal reproduction project (MRP)

[godot-crappy-contraptions-main.zip](https://github.com/godotengine/godot/files/15078404/godot-crappy-contraptions-main.zip)
Repository: godot
Issue: Custom shortcuts Shift+Alt+I for ui_text_caret_line_end not working
Labels: bug,topic:input

### Tested versions

Reproducible in Godot 4.2.1 and master-4a0160241fd0c1e874e297f6b08676cf0761e5e8.

### System information

Windows 10 - Godot v4.2.1 Vulkan 1.3.277 - Forward+

### Issue description

I was learning Godot for game develop and try to add a custom shortcuts Shift+Alt+I to move cursor to line end. After I add the shortcuts in editor settings, I just found it is not working.
![image](https://github.com/godotengine/godot/assets/33823695/f0dd78bf-14c9-4ed8-8039-aaee1c463da1)

I also tried to build the latest Godot source code (HEAD at commit 4a0160241fd0c1e874e297f6b08676cf0761e5e8) and it's still not working.

Then I just dig into the Godot source code, and found (maybe not correct) that the shift key is unset when checking the caret_line_end action.
![image](https://github.com/godotengine/godot/assets/33823695/0d1bd0ea-94bb-49a0-b3a2-8002ba799d3f)

Is this the bug? Or there is just another way to solve this?

### Steps to reproduce

Open or create any project.
Open editor settings and add shortcuts Shift+Alt+I for ui_text_caret_line_end.
Open any script and put the caret in the middle of a sentence.
Press Shift+Alt+I, expect caret moved to line end, but found nothing happended

### Minimal reproduction project (MRP)

[foo.zip](https://github.com/godotengine/godot/files/15078359/foo.zip)
Just an empty project with a script attached to root node is enough.
Repository: next.js
Issue: cancel headers() caching
Labels: bug,Pages Router,Parallel & Intercepting Routes

### Link to the code that reproduces this issue

https://github.com/MrOxMasTer/shopco/commit/9da44da590d9317cda07f6949a9982dd004952c7

### To Reproduce

1. go to the auth page, using the person icon
2. to open a burger menu
3. to close the burger menu by clicking on the cross.
4. go to the home page by clicking on the logo
5. To try and open a menu burger
6. close menu 
7. Realize that when you close, you've gone to the page you were on before (on the authentication page)

### Current vs. Expected behavior

Every time the menu is opened, the data from headers() should be updated and with some processing put a new link (href) in the close button.

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro
  Available memory (MB): 16320
  Available CPU cores: 6
Binaries:
  Node: 20.12.2
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.2.1 // There is a newer version (14.2.2) available, upgrade recommended! 
  eslint-config-next: 14.1.3
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.4.5
Next.js Config:
  output: standalone
```


### Which area(s) are affected? (Select all that apply)

Parallel & Intercepting Routes

### Which stage(s) are affected? (Select all that apply)

next dev (local), Other (Deployed)

### Additional context

I've tried all the different functions from noStore() to setting the page dynamic='force-dynamic', but no way to get an updated header
Repository: godot
Issue: Polygon2D (with multiple parts) fails to mask with Clip Children when Inverted on
Labels: bug,topic:2d

### Tested versions

Reproducible in: 4.3-dev5, 4.2.1-stable, 4.1.3-stable

### System information

Godot v4.2.2.rc3 - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 2070 SUPER (NVIDIA; 31.0.15.5152) - Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (8 Threads)

### Issue description

When using a Polygon2D of multiple parts (using the Polygons array to define them via their point indices), it will correctly mask its children when Clip Children is set to Clip Only. However if you Invert the polygon, the masking fails to give the expected 'opposite' result. It doesn't matter if the boxes are created clockwise or anticlockwise.

I hope this is a legal and valid method of doing this.. I'm using this video as a guide... https://www.youtube.com/watch?v=NvJuW7ruuN0

![PolygonInvertedClippingBugA_annotated](https://github.com/godotengine/godot/assets/167312641/bb2fe758-24f0-4004-9072-35bf3d2062b4)

![PolygonInvertedClippingBugB_annotated](https://github.com/godotengine/godot/assets/167312641/d232cba3-6d88-45ac-8e5f-15ac743cd3be)

![PolygonInvertedClippingBugC_annotated](https://github.com/godotengine/godot/assets/167312641/8f3d7481-7c05-4afb-87e7-286d1323cece)


### Steps to reproduce


We need to make a Polygon2D whose points define two separate boxes and use the Polygons array to define them via their indexes 0-3 for one and 4-7 for the other.

1. In a new scene, add a Polygon2D and create a box with 4 points.
2. In the inspector for the polygon, manually add 4 more points with Add Element for a total of 8. Drag these new points to form a second box to the side (see picture).
3. In the Inspector, under the Data/Polygons section, increase the array Size to 2.
4. For each array, change the type from null to PackedInt32Array.
5. Under the first PackedIn32Array, add 4 elements and insert values 0 to 3
6. Under the second PackedIn32Array, add 4 elements and insert values 4 to 7
8. Drag the gogot icon.svg into the viewport and overlap the edges of both boxes of the polygon.
9. Make the icon a child of the Polygon2D and set the polygon's Clip Children to Clip Only.
10. This shows the masking working correctly.
11. If you now set the polygon's Invert flag to ON, it fails. It does not give the expected result of clipping out the opposite parts of the sprite.


### Minimal reproduction project (MRP)

[PolygonInvertedClippingBug.zip](https://github.com/godotengine/godot/files/15078891/PolygonInvertedClippingBug.zip)
Repository: ui
Issue: [bug]: Type error: Property 'char' does not exist on type 'SlotProps | undefined'.
Labels: bug

### Describe the bug

After installation of the input-otp component I am getting a build error in Next.js - using TypeScript.

The error occurs here: `const { char, hasFakeCaret, isActive } = inputOTPContext.slots[index];`


Property 'char' does not exist on type 'SlotProps | undefined'.ts(2339)
Property 'hasFakeCaret' does not exist on type 'SlotProps | undefined'.ts(2339)
Property 'isActive' does not exist on type 'SlotProps | undefined'.ts(2339)

### Affected component/components

Input OTP

### How to reproduce

Install input-otp.

Setup eslint:
eslintrc.cjs:

```
/** @type {import("eslint").Linter.Config} */
const config = {
  parser: "@typescript-eslint/parser",
  parserOptions: {
    project: true,
  },
  plugins: ["@typescript-eslint"],
  extends: [
    "next/core-web-vitals",
    "plugin:@typescript-eslint/recommended-type-checked",
    "plugin:@typescript-eslint/stylistic-type-checked",
  ],
  rules: {
    // These opinionated rules are enabled in stylistic-type-checked above.
    // Feel free to reconfigure them to your own preference.
    "@typescript-eslint/array-type": "off",
    "@typescript-eslint/consistent-type-definitions": "off",

    "@typescript-eslint/consistent-type-imports": [
      "warn",
      {
        prefer: "type-imports",
        fixStyle: "inline-type-imports",
      },
    ],
    "@typescript-eslint/no-unused-vars": ["warn", { argsIgnorePattern: "^_" }],
    "@typescript-eslint/require-await": "off",
    "@typescript-eslint/no-misused-promises": [
      "error",
      {
        checksVoidReturn: { attributes: false },
      },
    ],
  },
};

module.exports = config;
```

### Codesandbox/StackBlitz link

_No response_

### Logs

```bash
./src/components/core/ui/input-otp.tsx:39:11
Type error: Property 'char' does not exist on type 'SlotProps | undefined'.

  37 |   const inputOTPContext = React.useContext(OTPInputContext);
  38 |
> 39 |   const { char, hasFakeCaret, isActive } = inputOTPContext.slots[index];
     |           ^
  40 |
  41 |   return (
  42 |     <div
 ELIFECYCLE  Command failed with exit code 1.
```


### System Info

```bash
package.json

"next": "^14.1.4",
"@types/eslint": "^8.56.2",
"@typescript-eslint/eslint-plugin": "^7.0.2",
"@typescript-eslint/parser": "^7.0.2",
"eslint": "^8.56.0",
"eslint-config-next": "^14.1.0",
"typescript": "^5.4.3",
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: vscode
Issue: potential listener LEAK detected, having 185 listeners already.
Labels: bug,notebook-toc-outline

Testing #210961

* todays insiders `347777655976bbc8460f833449592dd0a9a8f340`
* having a really large ipynb notebook
* :bug: seeing the leak warning below

```
event.ts:875 [72h] potential listener LEAK detected, having 185 listeners already. MOST frequent listener (8):
check @ event.ts:875
q @ event.ts:1056
M @ menuService.ts:395
q @ event.ts:1064
m @ notebookOutline.ts:217
renderElement @ notebookOutline.ts:182
renderElement @ abstractTree.ts:418
renderElement @ listWidget.ts:1249
Z @ listView.ts:940
(anonymous) @ listView.ts:876
transact @ rowCache.ts:80
Y @ listView.ts:867
ib @ listView.ts:1107
y @ event.ts:1156
z @ event.ts:1167
fire @ event.ts:1191
(anonymous) @ scrollableElement.ts:216
y @ event.ts:1156
fire @ event.ts:1187
n @ scrollable.ts:393
setScrollPositionNow @ scrollable.ts:303
R @ scrollableElement.ts:470
$ @ scrollableElement.ts:382
event.ts:876 Error
    at c.create (event.ts:889:25)
    at l.q [as onDidChange] (event.ts:1055:34)
    at Object.M [as onWillAddFirstListener] (menuService.ts:395:34)
    at f.q [as onDidChange] (event.ts:1064:20)
    at O.m (notebookOutline.ts:217:44)
    at O.renderElement (notebookOutline.ts:182:9)
    at A.renderElement (abstractTree.ts:418:17)
    at Y.renderElement (listWidget.ts:1249:13)
    at m.Z (listView.ts:940:13)
    at listView.ts:876:11
    at E.transact (rowCache.ts:80:4)
    at m.Y (listView.ts:867:14)
    at m.ib (listView.ts:1107:9)
    at n.y (event.ts:1156:13)
    at n.z (event.ts:1167:9)
    at n.fire (event.ts:1191:9)
    at d.value (scrollableElement.ts:216:19)
    at n.y (event.ts:1156:13)
    at n.fire (event.ts:1187:9)
    at I.n (scrollable.ts:393:18)
    at I.setScrollPositionNow (scrollable.ts:303:8)
    at n.setScrollPosition (scrollableElement.ts:619:21)
    at m.setScrollTop (listView.ts:1030:26)
    at X.reveal (listWidget.ts:1909:14)
    at ie.reveal (abstractTree.ts:2989:14)
    at d.H [as value] (outlinePane.ts:332:11)
    at n.y (event.ts:1156:13)
    at n.z (event.ts:1167:9)
    at n.fire (event.ts:1191:9)
    at d.value (notebookOutline.ts:375:24)
    at n.y (event.ts:1156:13)
    at n.z (event.ts:1167:9)
    at n.fire (event.ts:1191:9)
    at u.r (notebookOutlineProvider.ts:298:22)
    at notebookOutlineProvider.ts:57:79
    at async.ts:364:13
check @ event.ts:876
q @ event.ts:1056
M @ menuService.ts:395
q @ event.ts:1064
m @ notebookOutline.ts:217
renderElement @ notebookOutline.ts:182
renderElement @ abstractTree.ts:418
renderElement @ listWidget.ts:1249
Z @ listView.ts:940
(anonymous) @ listView.ts:876
transact @ rowCache.ts:80
Y @ listView.ts:867
ib @ listView.ts:1107
y @ event.ts:1156
z @ event.ts:1167
fire @ event.ts:1191
(anonymous) @ scrollableElement.ts:216
y @ event.ts:1156
fire @ event.ts:1187
n @ scrollable.ts:393
setScrollPositionNow @ scrollable.ts:303
R @ scrollableElement.ts:470
$ @ scrollableElement.ts:382
```
Repository: excalidraw
Issue: Stabilize `Snapshot` diffing
Labels: performance ⚡️,refactor,store

As of now, our `Snapshot` diffing algo is limited by a shallow compare on the level of object properties, meaning it goes just two levels deep. It's due to the instability of reference values inside `appState` and `elements`, as sometimes they mutate or result in new instances even though they didn't change - thus we cannot perform quick reference checks.

For now, it's sufficient for our purposes, but it is not super flexible, not super fast, does not allow deeper nesting and likely our needs will eventually outgrow it rather sooner than later. Therefore we should stabilise updating reference values inside `appState` & `elements`, so that we can always perform quick reference checks and go possibly infinitely deep.

At the same time, we should reconsider using an array as part of reference values, as if we would like to depend on a meaningful order, we would have to maintain a fractional index-like solution on every such value, once applying the incremental change more granularly (without overriding whole array, as we currently do i.e. with `linearElement.points`,  `element.groupIds`). 

```[tasklist]
### Tasks
- [ ] Enforce immutable handling of reference values to create new instances on change (not individual elements per se - we can keep mutating, but we need to be immutable on their properties).
- [ ] Ensure we don't create a new instance when there is no change (i.e. `selectedElementIds`).
- [ ] Update the diffing algo to support deep diffing based on the quick reference checks.
- [ ] Identify observed arrays (such as `element.groupIds`) which depend on the correct order and consider rewriting them into key-value records, so that they don't depend on the order (or introduce fractional-like index within).
- [ ] Consider post processing most of the reference values as part of delta calculation, so that when applying changes, we could be more granular and apply just changes (as we do with `boundElements`), not overriding whole object/array.
- [ ] Consider adding a decorator for reference values which should be post-processed, as for some it does not have to make sense (i.e. `linearElement.points`).
```
Repository: deno
Issue: deno check w/ byonm shows resolver error for micromatch npm package
Labels: bug,node compat

```ts
// main.ts
import * as foo from "npm:micromatch@4.0.5";

console.log(foo);
```

```json
{
  "unstable": ["byonm"]
}
```

```json
{
  "dependencies": {
    "micromatch": "^4.0.5"
  }
}
```

1. `npm install`
2. `deno run main.ts` -- ok
3. `deno run --check main.ts` -- fail

```
% deno run --check main.ts
error: Failed resolving types. Failed resolving package subpath for 'npm:micromatch@4.0.5' in '/Users/david/dev/scratch/node_modules/micromatch'.
    at file:///Users/david/dev/scratch/main.ts:1:22
```

```
% deno info main.ts
local: /Users/david/dev/scratch/main.ts
emit: /Users/david/Library/Caches/deno/gen/file/Users/david/dev/scratch/main.ts.js
type: TypeScript
dependencies: 1 unique
size: 63B

file:///Users/david/dev/scratch/main.ts (63B)
├── file:///Users/david/dev/scratch/node_modules/micromatch/index.js (unknown)
└── Failed resolving package subpath for 'npm:micromatch@4.0.5' in '/Users/david/dev/scratch/node_modules/micromatch'. (resolve error)
scratch % deno run --check main.ts
error: Failed resolving types. Failed resolving package subpath for 'npm:micromatch@4.0.5' in '/Users/david/dev/scratch/node_modules/micromatch'.
    at file:///Users/david/dev/scratch/main.ts:1:22
```
Repository: vscode
Issue: Large notebook trigger very many leak warnings 
Labels: bug,notebook-toc-outline

Testing #210961

[slow.ipynb.txt](https://github.com/microsoft/vscode/files/15079389/slow.ipynb.txt)

* open dev tools console
* open the notebook from above
* 😱 notice leak warnings from various places

This is critical: `REFUSES to accept new listeners because it exceeded its threshold by far` because it means a listener will never be used, meaning a feature is likely not working. 

This seems to be a widespread misconception and it seems each cell listens by itself. So, more cells,  more listener, leak warning and refusal to accept more listeners. Generally, listener should be used sparingly, e.g instead of each cell being a listener there should be one per notebook which dispatches onto cell.
Repository: rustdesk
Issue: MultiMonitor setup on Ubuntu doesn't retain the chosen monitor configuration after screen locking due to inactivity
Labels: bug

### Bug Description

When you have 2 RustDesk windows open on a multi-monitor setup, and Ubuntu locks the screen due to inactivity, upon responding, both RustDesk windows appear on the first monitor.

Example:
RustDesk1 -> Monitor1
RustDesk2 -> Monitor2

After Lock on and restore: 
Expected behavior:
RustDesk1 -> Monitor1
RustDesk2 -> Monitor2

Actual behavior:
RustDesk1 -> Monitor1
RustDesk2 -> Monitor1

### How to Reproduce

Open 2 rust desk pointing to 2 monitors and lock on ubuntu.

### Expected Behavior

MultiMonitor  retain the chosen monitor configuration after screen locking due to inactivity

### Operating system(s) on local side and remote side

ubuntu 22.04

### RustDesk Version(s) on local side and remote side

1.2.4 (2024-03-14)

### Screenshots



### Additional Context

_No response_
Repository: vscode
Issue: Sticky scroll flashing non stop
Labels: bug,notebook-sticky-scroll

Testing #210961


* open [slow.ipynb.txt](https://github.com/microsoft/vscode/files/15079576/slow.ipynb.txt)
* scroll "# Header 1111111111111111111111989898" into view
* scroll so that it gets very close the sticky scroll headers
* :bug: things start flashing


https://github.com/microsoft/vscode/assets/1794099/a8b80af6-4665-4779-883c-8f69affd601a
Repository: excalidraw
Issue: Simplify conflict resolution when applying increments
Labels: refactor,store

When applying increments, we need to resolve conflicts, in case our increment modifies a bi-directional relation, which was in the meantime deleted by another client.

For now, we are resolving conflicts between bound elements, especially arrow <=> bindable elements and text <=> container. For details check the history test cases inside #7348. The simplified logic is as follows:

1. don't allow bindings pointing to deleted elements from non-deleted elements, as they could result in rendering issues
2. leave the binding on the deleted elements, so that we can restore the bi-directional bindings when restoring deleted elements through the history
3. after applying increments, always re-check if bindings are bi-directional and if they are not, try to fix them (either rebind if possible - element did not get bound to something else, or unbind from both sides)
4. when 3. results in some updates, apply such updates to the increment so that they don't get lost

```[tasklist]
- [ ] Simplify resolution of text <=> container bindings by extracting `text` from the `boundElements` into a separate property (i.e. `boundTextId`)
- [ ] Replace `boundElements` array with an object, as it does not depend on the order.
- [ ] Consider maintaining conflict-free unidirectional format in the data structure, while i.e. maintaining an in-memory index of bi-directional bindings. Might simplify conflict resolution, but could lead to the inability to restore bindings in certain situations.
- [ ] Consider having a semantic runtime validation of bindings nothing non-deleted points to deleted, non-deleted to non-deleted is always bidirectional, deleted to non-deleted is always unidirectional, etc.)
```
Repository: vscode
Issue: Notebook sticky scroll does not show correct element based viewport
Labels: bug,notebook-sticky-scroll

Testing #210961

Open the attached file. Rename to `.ipynb`
Navigate to the middle of the file (for example where Header 10 is mentioned).
Notice how the sticky scroll outline shows the wrong element. It is not based on keyboard focus, or what is at the screen. It seems like it is a couple of cells off in the computation.


![Image](https://github.com/microsoft/vscode/assets/1926584/a0ebfca4-1a4c-46c1-bee3-d30defe9b68b)

Header 10 is off screen. It is one page above.

![Image](https://github.com/microsoft/vscode/assets/1926584/c44f5e8c-1a56-4156-8516-21b24113f70f)


[test.json](https://github.com/microsoft/vscode/files/15079770/test.json)
Repository: vscode
Issue: Issue Reporter: similar issues UI looks half-baked
Labels: feature-request,issue-reporter

Testing #210874

I realize this is probably unrelated to the TPI, but I noted that this list that opens up feels like it's missing some design love. Maybe some CSS inspiration from "Used references" in the chat UI could be a starting point. Or something from the settings UI.

At minimum a border around the list might make it feel less like it's floating in space on it's own 🌌

![CleanShot 2024-04-23 at 09 57 40@2x](https://github.com/microsoft/vscode/assets/25163139/5ddcf622-5637-4c58-bbd9-5c9fbb04c6b3)
Repository: rust
Issue: Spurious “constant provided when a type was expected” upon syntax error in a generic parameter list
Labels: A-diagnostics,A-parser,T-compiler,D-confusing,D-verbose

### Code

```Rust
struct Foo;
struct Bar;

impl From<Option<Foo> x> for Bar {
}
```


### Current output

```Shell
error: expected one of `,` or `>`, found `x`
 --> src/lib.rs:4:23
  |
4 | impl From<Option<Foo> x> for Bar {
  |                       ^ expected one of `,` or `>`
  |
help: expressions must be enclosed in braces to be used as const generic arguments
  |
4 | impl From<{ Option<Foo> x }> for Bar {
  |           +               +

error[E0747]: constant provided when a type was expected
 --> src/lib.rs:4:11
  |
4 | impl From<Option<Foo> x> for Bar {
  |           ^^^^^^^^^^^^^
```


### Desired output

The “error[E0747]: constant provided when a type was expected” should be omitted.


### Rationale and extra context

The secondary error is a distraction from the syntax error, because it is unlikely that the user in fact meant to write a const expression.

As an implementation strategy: perhaps E0747 should not be shown if the const-ness of the argument is a result of syntax error recovery, or perhaps if there were any syntax errors at all since there are lots of ways to typo a generic type.

Or there could be a heuristic like "if the candidate expression has got paired `<` and `>`, then it probably isn't an expression at all".

### Other cases

This seems to only occur if the generic parameter text is parseable as an expression.

### Rust Version

```Shell
rustc 1.77.2 (25ef9e3d8 2024-04-09)
binary: rustc
commit-hash: 25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04
commit-date: 2024-04-09
host: x86_64-apple-darwin
release: 1.77.2
LLVM version: 17.0.6
```


### Anything else?

_No response_