sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: cursor_set_custom_image not changing cursor setting to same (but updated) texture
Labels: discussion,topic:rendering,topic:porting,confirmed,documentation

### Godot version

v4.2.rc1.official [ad72de508]

### System information

Godot v4.2.rc1 - Windows 10.0.19042 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 2070 (NVIDIA; 31.0.15.2756) - Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz (8 Threads)

### Issue description

If you pass the same texture into `DisplayServer.cursor_set_custom_image`, the cursor graphic won't update, even if the texture has been

### Steps to reproduce

set cursor to a texture using `cursor_set_custom_image` on one tick, next tick update image & texture, use same resource for `cursor_set_custom_image` call. Cursor will not change. `cursor_texture.emit_changed()` does nothing.

Bogus fix:
```gdscript
DisplayServer.cursor_set_custom_image(null)
DisplayServer.cursor_set_custom_image(cursor_texture)
```
Will "work", but will flicker to the system cursor at random, largely during motion but also when idle (Happens less frequently at lower cursor pic resolutions, but still happens).

### Minimal reproduction project

[customcursor.zip](https://github.com/godotengine/godot/files/13408283/customcursor.zip)
Repository: pytorch
Issue: [JIT] - torch.script - 'Optional[Tensor]' object has no attribute or method 'size'
Labels: oncall: jit

### 🐛 Describe the bug

Could not manage to solve nor to understand the appearance of this error: `'Optional[Tensor]' object has no attribute or method 'size'` 

```
from transformers import AutoTokenizer, AutoModelForSeq2SeqLM, AutoModel
device = torch.device("cuda" if torch.cuda.is_available() else "cpu")

model = AutoModel.from_pretrained("dbmdz/bert-base-german-europeana-cased", torchscript=True).to(device)
model.eval()

scripted_model = torch.jit.script(model)
```

```
'Optional[Tensor]' object has no attribute or method 'size'.:
  File "[...]/python3.11/site-packages/transformers/models/bert/modeling_bert.py", line 213
            input_shape = input_ids.size()
        else:
            input_shape = inputs_embeds.size()[:-1]
                          ~~~~~~~~~~~~~~~~~~ <--- HERE
    
        seq_length = input_shape[1]
```

### Versions

PyTorch version: 2.0.1+cu117
Is debug build: False
CUDA used to build PyTorch: 11.7
ROCM used to build PyTorch: N/A

OS: Ubuntu 20.04.4 LTS (x86_64)
GCC version: (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
Clang version: Could not collect
CMake version: version 3.27.1
Libc version: glibc-2.31

Python version: 3.11.4 (main, Jul  5 2023, 13:45:01) [GCC 11.2.0] (64-bit runtime)
Python platform: Linux-5.15.0-27-generic-x86_64-with-glibc2.31
Is CUDA available: True
CUDA runtime version: 11.0.221
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration: 
GPU 0: NVIDIA A100-SXM4-40GB
[...]
Versions of relevant libraries:
[pip3] numpy==1.25.2
[pip3] torch==2.0.1
[pip3] torch-model-archiver==0.8.1
[pip3] torchserve==0.8.1
[pip3] triton==2.0.0

cc @EikanWang @jgong5 @wenzhe-nrv @sanchitintel
Repository: opencv
Issue: Cannot load the paddleocr v3 model after converted to onnx
Labels: bug,confirmed,category: dnn (onnx)

### System Information

OpenCV version: 4.8.0
operation System : windows11
compiler : visual c++ 2019

### Detailed description



Error messages

```
[ERROR:0@0.021] global onnx_importer.cpp:1064 cv::dnn::dnn4_v20230620::ONNXImporter::handleNode DNN/ONNX: ERROR during processing node with 2 inputs and 1 outputs: [MatMul]:(onnx_node!p2o.MatMul.2) from domain='ai.onnx'
OpenCV: terminate handler is called! The last OpenCV error is:
OpenCV(4.8.0) Error: Unspecified error (> Node [MatMul@ai.onnx]:(onnx_node!p2o.MatMul.2) parse error: OpenCV(4.8.0) C:\GHA-OCV-1\_work\ci-gha-workflow\ci-gha-workflow\opencv\modules\dnn\src\layers\fully_connected_layer.cpp:156: error: (-2:Unspecified error) in function 'bool __cdecl cv::dnn::FullyConnectedLayerImpl::getMemoryShapes(const class std::vector<class std::vector<int,class std::allocator<int> >,class std::allocator<class std::vector<int,class std::allocator<int> > > > &,const int,class std::vector<class std::vector<int,class std::allocator<int> >,class std::allocator<class std::vector<int,class std::allocator<int> > > > &,class std::vector<class std::vector<int,class std::allocator<int> >,class std::allocator<class std::vector<int,class std::allocator<int> > > > &) const'
> >  (expected: 'inputsTmp[0][i] == inputsTmp[1][i]'), where
> >     'inputsTmp[0][i]' is 1
> > must be equal to
> >     'inputsTmp[1][i]' is 0
> ) in cv::dnn::dnn4_v20230620::ONNXImporter::handleNode, file C:\GHA-OCV-1\_work\ci-gha-workflow\ci-gha-workflow\opencv\modules\dnn\src\onnx\onnx_importer.cpp, line 1083
```



### Steps to reproduce

Steps to reproduce:

1. Install paddle2onnx and downlaod official paddleocrv3
2. Convert the model by following cmd

```
paddle2onnx --model_dir ./ch/ch_PP-OCRv3_rec_infer ^
--model_filename inference.pdmodel ^
--params_filename inference.pdiparams ^
--save_file ./ch/rec_onnx/model.onnx ^
--opset_version 11 ^
--input_shape_dict="{'x':[-1,3,-1,-1]}" ^
--enable_onnx_checker True
```

3. Run onnxsimplify

```
import onnx
from onnxsim import simplify

model = onnx.load(input_model_name)

# convert model
model_simp, check = simplify(model)
assert check, "Simplified ONNX model could not be validated"

onnx.save(model_simp, "{}_simple.onnx".format(output_model_name))
```

4. load the model by opencv

`cv::dnn::readNet("ch_PP-OCRv3_rec_simple.onnx");`

[Model after onnx simplify](https://drive.google.com/file/d/1NkVeaM5-8btimxBYX-MrcLf5FlmW0czD/view?usp=drive_link)
[Model before onnx simplify](https://drive.google.com/file/d/1r6pIX8e2e_7ebU6bf2l_nf9h4wq6Mc0n/view?usp=drive_link)


### Issue submission checklist

- [X] I report the issue, it's not a question
- [X] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [X] I updated to the latest OpenCV version and the issue is still there
- [X] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: vscode
Issue: Multi Diff Editor Revealing lines doesn't auto reveal after a threshold
Labels: bug,multi-diff-editor

When pulling the bottom border of the top divider of a code block up, hidden lines appear which is nice. However, the amount of lines that can appear is limited to how high up the code block is in the editor. To reveal more lines I have to pull it up again and again... I think it should start auto revealing when pulling the border up with the mouse over the tab bar.

![Recording 2023-11-20 at 12 03 59](https://github.com/microsoft/vscode/assets/44439583/d3fff5e9-5093-422a-8751-554f979fec36)
Repository: electron
Issue: [Bug]: Gap between window decoration and content under GNOME wayland with fractional scaling
Labels: platform/linux,bug :beetle:,25-x-y

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a bug report that matches the one I want to file, without success.

### Electron Version

25.9.4

### What operating system are you using?

Other Linux

### Operating System Version

Manjaro

### What arch are you using?

x64

### Last Known Working Electron version

24.8.8

### Expected Behavior

I'm expecting Electron 25 to be able to display window decorations on GNOME with fractional scaling enabled as well as it used to do in Electron 24.

### Actual Behavior

A 1px gap appears between the window decorations and the window frame.

![image](https://github.com/electron/electron/assets/442722/3ff273c8-c0c5-4fcc-b5e8-3ed681405729)


### Testcase Gist URL

_No response_

### Additional Information

Affects vscode, discord, eletron 25.

Does not affect Caprine, Electron 24, Electron 22.
Repository: godot
Issue: EditorInterface.get_inspector() signal "property_edited" not firing in some circumstances
Labels: bug,topic:editor

### Godot version

v4.2.rc1.official [ad72de508]

### System information

Godot v4.2.rc1 - Ubuntu 22.04.3 LTS 22.04 - X11 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 2060 (nvidia; 535.129.03) - Intel(R) Core(TM) i5-9400F CPU @ 2.90GHz (6 Threads)

### Issue description

This screenshot shows the Inspector on a GradientTexture2D. The 'widget' at the top, I don't know the name, allows one to change the properties "fill_from" and "fill_to"; however, the signal "property_edited" is not being called from that widget.

![image](https://github.com/godotengine/godot/assets/392218/88cf290d-ab3e-4702-baab-3829be3ab7ae)

I have a sample project and some info below.

### Steps to reproduce

See link below for my repo.

. Make sure main scene is open. etc.
. Double-click "res://new_gradient_texture_2d.tres" to see it in the Inspector.
. Move the "fill from" and "fill to" widget handles in the tool at the very top.
. Notice that there is no printout from _inspector_prop_edited
. Now open the Fill subsection and change the settings there; now  _inspector_prop_edited happens.

 **Conclusion**: the inspect.property_edited is somehow ignoring the top widget.

```Python
func _ready() -> void:
	var inspect = EditorInterface.get_inspector()
	if inspect.is_connected(&"property_edited",_inspector_prop_edited):
		inspect.property_edited.disconnect(_inspector_prop_edited)
	inspect.property_edited.connect(_inspector_prop_edited)
	print(inspect.get_signal_connection_list(&"property_edited"))

func _inspector_prop_edited(p:String):
	print("_inspector_prop_edited:", p)
```

Not sure if this is a bug or not. There was no other similar issue.
HTH.

### Minimal reproduction project

Reproduction project here: https://gitlab.com/dbat/prop-edited-issue
Repository: tauri
Issue: [bug] Input Method does not work properly
Labels: type: bug,platform: Linux,status: needs triage

### Describe the bug

I am using tauri 1.5.2 on Linux, Debian 12, KDE/Wayland.
The Chinese input method in fcitx5 looks quite strange, is there any problem with GTK and Wayland?
![wayland](https://github.com/tauri-apps/tauri/assets/46845934/8c1f149a-01f6-4bb5-9f91-2f1abdab3459)

I tried to switch to X11, but the problem still exists.

### Reproduction

_No response_

### Expected behavior

The input method should follow the textarea, look at this in Firefox.
![input](https://github.com/tauri-apps/tauri/assets/46845934/a0412103-f338-43c2-9a7e-869add9061e4)


### Platform and versions

```text
[✔] Environment
    - OS: Debian 12 X64
    ✔ webkit2gtk-4.0: 2.42.2
    ✔ rsvg2: 2.54.7
    ✔ rustc: 1.74.0 (79e9716c9 2023-11-13)
    ✔ cargo: 1.74.0 (ecb9851af 2023-10-18)
    ✔ rustup: 1.26.0 (5af9b9484 2023-04-05)
    ✔ Rust toolchain: stable-x86_64-unknown-linux-gnu (default)
    - node: 18.18.0
    - yarn: 1.22.21
    - npm: 9.8.1

[-] Packages
    - tauri [RUST]: 1.5.2
    - tauri-build [RUST]: 1.5.0
    - wry [RUST]: 0.24.4
    - tao [RUST]: 0.16.5
    - @tauri-apps/api [NPM]: 1.5.1
    - @tauri-apps/cli [NPM]: 1.5.6

[-] App
    - build-type: bundle
    - CSP: default-src 'self'; img-src 'self' asset: https://asset.localhost
    - distDir: ../dist
    - devPath: http://localhost:1420/
    - framework: Vue.js
    - bundler: Vite
```


### Stack trace

_No response_

### Additional context
![session](https://github.com/tauri-apps/tauri/assets/46845934/9921d36c-92e3-400f-8a99-20fb3b650a60)

_No response_
Repository: PowerToys
Issue: Peek - Trigger on hover w/ timer
Labels: Idea-Enhancement,Product-Peek

### Description of the new feature / enhancement

This feature is an improvement over the current peek feature which requires a keyboard shortcut to activate, however I believe it would be more efficient if the peek feature was activated on the hover of the cursor on a specific file. Now, I know that this would be too cluttered, so I was thinking to add a delay of about 2 seconds of hovering before the peek enables. 

### Scenario when this would be used?

The scenario where this would be helpful is for browsing through files that have no previews such as word documents. 

### Supporting information

_No response_
Repository: transformers
Issue: Getting equivalent results between Transformer's resize and tf.image.resize
Labels: Feature request

### Feature request

For the SigLIP model (#26522), I'd like to get equivalent results between tf.image.resize and the resize method available in Transformers.

Here's what I tried:

``` 
from PIL import Image
import requests

import tensorflow as tf
import numpy as np

def resize(image, size, method="bilinear", antialias=False):
    """Resizes image to a given size."""
    # Note: use TF-2 version of tf.image.resize as the version in TF-1 is
    # buggy: https://github.com/tensorflow/tensorflow/issues/6720.
    # In particular it was not equivariant with rotation and lead to the network
    # to learn a shortcut in self-supervised rotation task, if rotation was
    # applied after resize.
    dtype = image.dtype
    tf_dtype = tf.type_spec_from_value(image).dtype
    image = tf.image.resize(image, size, method=method, antialias=antialias)
    return tf.cast(tf.clip_by_value(image, tf_dtype.min, tf_dtype.max), dtype)

# load image
url = 'https://cdn.openai.com/multimodal-neurons/assets/apple/apple-ipod.jpg'
image = Image.open(requests.get(url, stream=True).raw)

# get original pixel values
original_pixel_values = resize(np.array(image), size=(224,224))

# get our pixel values
from transformers.image_transforms import resize

pixel_values = resize(np.array(image), size=(224,224), resample=Image.Resampling.BILINEAR)

# verify results
np.testing.assert_array_equal(original_pixel_values, pixel_values)
```
This currently fails with:
```
AssertionError: 
Arrays are not equal

Mismatched elements: 87370 / 150528 (58%)
Max absolute difference: 255
Max relative difference: 255.
 x: array([[[127, 101,  59],
        [136, 112,  72],
        [129, 109,  72],...
 y: array([[[131, 105,  63],
        [138, 114,  74],
        [126, 108,  70],...
```

### Motivation

Would be great to have equivalent results such that logits match with the original implementation.

### Your contribution

I provide a notebook [here](https://colab.research.google.com/drive/1nP8f07qd3jWBRgCnE29cagseRtqVMADa?usp=sharing) for testing.
Repository: flutter
Issue: [flutter_markdown] Support RTL
Labels: c: new feature,package,team-ecosystem,P3,p: flutter_markdown,triaged-ecosystem

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Use case

RTL is not supported in `flutter_markdown`.

### Proposal

Github site supports this Feature:

![Screenshot from 2023-11-20 17-53-38](https://github.com/flutter/flutter/assets/20955005/c17a09e0-062d-44a8-b333-4d914f853b3a)

But `flutter_markdown` is not support:

![Screenshot from 2023-11-20 18-04-42](https://github.com/flutter/flutter/assets/20955005/01c17d33-83b7-4217-8b84-4ab641704000)


Example code:
```markdown
# Title
This is atest
## Title 2
This is a test

https://github.com

این تست است این تست است

این تست است این تست است
# Title
This is atest
```

I suggest adding this feature.
Repository: vscode
Issue: Support strict matching in Problems filtering
Labels: feature-request,error-list

Type: <b>Bug</b>

This bug report describes a problem regarding the PROBLEMS view (workbench.actions.view.problems)

Prerequisites:
1. clangd is installed and active
2. open a C++ file which causes 'clangd' and 'clang-tidy' warnings
3. write 'clangd' into the problems filter line edit
Result: 
1. clangd and clang-tidy warnings are displayed
2. the following characters are highlighted
   clangd: whole word
   clang-tidy: 'clang' and the 'd' in 'tidy'

If you set the filter to 'clang-tidy', the view only shows clang-tidy warnings.

The overall behavior of the filtering is quite strange and it should be explained to users how the matching works. 

VS Code version: Code 1.84.2 (1a5daa3a0231a0fbba4f14db7ec463cf99d7768e, 2023-11-09T10:50:47.800Z)
OS version: Linux x64 5.14.21-150500.55.36-default
Modes:

<details><summary>Extensions (15)</summary>

Extension|Author (truncated)|Version
---|---|---
Bookmarks|ale|13.4.2
githistory|don|0.6.20
gitlens|eam|14.5.0
font-switcher|eva|4.1.0
simple-new-file|fay|1.1.2
output-colorizer|IBM|0.1.2
vscode-clangd|llv|0.1.24
git-graph|mhu|1.30.0
autopep8|ms-|2023.8.0
pylint|ms-|2023.10.1
python|ms-|2023.20.0
vscode-pylance|ms-|2023.11.10
cpptools|ms-|1.18.5
vscode-yaml|red|1.14.0
sort-lines|Tyr|1.11.0

(1 theme extensions excluded)

</details>
<!-- generated by issue reporter -->
Repository: next.js
Issue: Dynamic Component is rendered statically when loading.tsx is present beside the layout
Labels: bug,Pages Router

### Link to the code that reproduces this issue

https://github.com/imbhargav5/nextjs-loading-error-reproduction

### To Reproduce

1. Clone the repository
2. Build it with `yarn build`

### Current vs. Expected behavior

I put a fake wait promise within a dynamic layout. (See `/src/app/dynamic/layout.tsx`). And I put a loading.tsx file to stream render the response. 
```tsx
import { ReactNode } from "react";

export const dynamic = 'force-dynamic';
export const revalidate = 0;

const fakeWait = (ms: number) => {
    console.log('This should never run statically');
    return new Promise(resolve => setTimeout(resolve, ms))
};

export default async function Layout({children}: {
    children: ReactNode
}){
    // This should only be run dynamically as this layout is dynamic
    await fakeWait(1000);
    return <>{children}</>
}
```

### Current behaviour 
When this project is built, this is the odd behaviour. 
With loading.tsx present beside the layout.tsx with force-dynamic behaviour present, this fakeWait function is being called during the build step.
Without loading.tsx present, it doesn't get called.


### Expected behaviour
Irrespective of loading.tsx being present or not, fakeWait function should never be called as this layout is not static and it should not be built statically.

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.1.0: Mon Oct  9 21:27:24 PDT 2023; root:xnu-10002.41.9~6/RELEASE_ARM64_T6000
Binaries:
  Node: 20.4.0
  npm: 9.7.2
  Yarn: 1.22.18
  pnpm: N/A
Relevant Packages:
  next: 14.0.4-canary.5
  eslint-config-next: 14.0.3
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.2.2
Next.js Config:
  output: N/A
```


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

App Router, Data fetching (gS(S)P, getInitialProps)

### Additional context

![Xnapper-2023-11-20-20 16 22](https://github.com/vercel/next.js/assets/2936644/800669bf-1e3f-4724-95a1-3d0a396ecfd0)
![Xnapper-2023-11-20-20 17 41](https://github.com/vercel/next.js/assets/2936644/f7c7f51d-2375-491b-b7cf-9979d80f38e6)
Repository: react-native
Issue: Text Component ellipsis is not displayed correctly in Android (the three dots are cut-off) 
Labels: Issue: Author Provided Repro,Platform: Android,Resolution: Fixed

### Description

I have identified a recurring issue in the current version of React Native (RN) that appears to be a continuation of a previously reported bug ([GitHub issue #36350](https://github.com/facebook/react-native/issues/36350)). The problem persists when using numberOfLines={1} on a Text component within a fixed-width parent component. Specifically, the ellipsis is being cut off, resulting in only a partial display of the dots or text, as illustrated in the attached screenshot

**Expected Behavior:**

The ellipsis should be fully visible, regardless of the fixed width of the parent component.

**Actual Behavior:**

The ellipsis is cut off, displaying only a portion of the dots or text.

### React Native Version

0.72.7

### Output of `npx react-native info`

System:
  OS: macOS 14.0
  CPU: (12) arm64 Apple M2 Max
  Memory: 259.44 MB / 32.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 16.20.2
    path: ~/.nvm/versions/node/v16.20.2/bin/node
  Yarn:
    version: 1.22.19
    path: ~/.nvm/versions/node/v16.20.2/bin/yarn
  npm:
    version: 8.19.4
    path: ~/.nvm/versions/node/v16.20.2/bin/npm
  Watchman:
    version: 2023.09.18.00
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.13.0
    path: /Users/user/.rbenv/shims/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.0
      - iOS 17.0
      - macOS 14.0
      - tvOS 17.0
      - watchOS 10.0
  Android SDK: Not Found
IDEs:
  Android Studio: 2022.3 AI-223.8836.35.2231.11005911
  Xcode:
    version: 15.0.1/15A507
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 11.0.20.1
    path: /usr/bin/javac
  Ruby:
    version: 3.0.1
    path: /Users/vladislavcusnir/.rbenv/shims/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.72.7
    wanted: 0.72.7
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: true
  newArchEnabled: false

### Steps to reproduce

1. Open the provided Snack link: [Snack Link](https://snack.expo.dev/Ux79Y-bc1)
2. Review the code in the Snack editor.
3. Switch to Android
4. Run the Snack and observe the ellipsis cut-off issue with numberOfLines={1} on the Text component within a fixed-width parent.

### Snack, screenshot, or link to a repository
[Snack Link](https://snack.expo.dev/Ux79Y-bc1)
<img width="819" alt="android-bug-ellipsis" src="https://github.com/facebook/react-native/assets/46562769/15f4ee8d-0ec7-463e-b8dd-5e8661c0413a">