sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: rename symbol preview not working
Labels: bug,rename

Type: <b>Bug</b>

Create simple program:

```python
text = "Hello, World!"
text = text.replace("World", "Python")
print(text)
```

Mark "text" and press F2
I get the following:
`Enter to rename, undefined to Preview`
So I don't have the option to preview.

Many thanks for your help!

VS Code version: Code 1.88.1 (e170252f762678dec6ca2cc69aba1570769a5d39, 2024-04-10T17:41:02.734Z)
OS version: Windows_NT x64 10.0.19045
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz (8 x 1800)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled|
|Load (avg)|undefined|
|Memory (System)|23.85GB (11.86GB free)|
|Process Argv|--crash-reporter-id 7fd7dfd0-5d75-4f7d-aebb-a48231238ebc|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (21)</summary>

Extension|Author (truncated)|Version
---|---|---
Bookmarks|ale|13.5.0
vscode-sqlite|ale|0.14.1
copilot-inline-toggle|Bub|0.1.0
githistory|don|0.6.20
vscode-firefox-debug|fir|2.9.10
code-runner|for|0.12.2
outline-map|Ger|1.4.0
copilot|Git|1.180.0
copilot-chat|Git|0.14.1
wrapSelection|kon|0.10.0
rainbow-csv|mec|3.11.0
black-formatter|ms-|2024.2.0
debugpy|ms-|2024.5.11001012
python|ms-|2024.4.1
vscode-pylance|ms-|2024.4.1
jupyter|ms-|2024.3.1
jupyter-keymap|ms-|1.1.2
vscode-jupyter-cell-tags|ms-|0.1.9
back-n-forth|nic|3.1.1
LiveServer|rit|5.7.9
markdown-preview-enhanced|shd|0.8.13


</details><details>
<summary>A/B Experiments</summary>

```
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscoreces:30445986
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
h48ei257:31000450
pythontbext0:30879054
accentitlementsc:30995553
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
d34g3935:30971562
fegfb526:30981948
bg6jg535:30979843
ccp1r6:30993540
dsvsc020:30976470
pythonait:31006305
gee8j676:31009558
dsvsc021:30996838
945dj816:31013170
pythoncenvpt:31022790

```

</details>

<!-- generated by issue reporter -->
Repository: godot
Issue: TabBar sometimes shows hover state when editing
Labels: bug,topic:gui

### Tested versions

4.2.2.stable & master[4a0160241fd0c1e874e297f6b08676cf0761e5e8]

### System information

Arch Linux

### Issue description

![Peek 2024-04-20 22-40](https://github.com/godotengine/godot/assets/372476/3fe7b895-2d57-4012-aaa1-d6852ec09a42)

### Steps to reproduce

1. Add a `TabBar` node in the scene and add some tabs.
2. Turn on "Clip Tabs" to make it easier to reproduce.
3. Quickly resize the node to its minimum width.

### Minimal reproduction project (MRP)

N/A
Repository: opencv
Issue: Inconsistent and unexpected behavior of cv.multiply() function with color images across OpenCV versions (4.5 to 4.8 vs. 4.9)
Labels: bug,category: python bindings

### System Information

OpenCV python version: 4.5.3 and 4.8.1 and 4.9.0 
Operating System / Platform: Ubuntu 20.04 and windows 10
Python version: 3.9

### Detailed description

The cv.multiply() function exhibits inconsistent and unexpected behavior when processing color images in OpenCV versions 4.5 to 4.8 compared to version 4.9. Specifically:

  1.  When using an integer as the multiplier, versions 4.5 to 4.8 only the blue channel is correctly multiplied by 2.0, while the green and red channels' pixel values become zero.
   2.  When using a one-dimensional NumPy array (np.array([2.0])) as the multiplier, versions 4.5 to 4.8 correctly multiply all channels (BGR) of the image by the given value. However, in OpenCV 4.9, only the blue channel is correctly multiplied, while the green and red channels' pixel values are set to zero.
   
These anomalies deviate from users' reasonable expectations for the cv.multiply() function, potentially leading to incorrect results or difficult-to-debug issues in applications.

### Steps to reproduce

# Sample Code
```
import cv2 as cv
import numpy as np

# Create a color image
gray_img = np.zeros((400, 400, 3), dtype=np.uint8)
gray_img[:, :, 0] = 50  # B
gray_img[:, :, 1] = 50  # G
gray_img[:, :, 2] = 50  # R

# Use an integer as the multiplier
tmp_img_int = cv.multiply(gray_img, 2)

# Use a one-dimensional NumPy array as the multiplier
tmp_img_array = cv.multiply(gray_img, np.array([2.0]))

# Output results
print(tmp_img_int[:2, :2])
print(tmp_img_array[:2, :2])
```

# Expected Result

1 For both integer and one-dimensional NumPy array multipliers, the cv.multiply() function should correctly multiply all channels (BGR) of the color image by the specified value, regardless of the OpenCV version.


# Actual Result
OpenCV versions 4.5 to 4.8:

```
[[[100   0   0]
  [100   0   0]]

 [[100   0   0]
  [100   0   0]]]
[[[100 100 100]
  [100 100 100]]

 [[100 100 100]
  [100 100 100]]]
```

OpenCV version 4.9:

```
[[[100 100 100]
  [100 100 100]]

 [[100 100 100]
  [100 100 100]]]
[[[100   0   0]
  [100   0   0]]

 [[100   0   0]
  [100   0   0]]]
```

# Reproduction Steps
1. Copy the sample code into a Python environment.
2. Run the code using OpenCV versions 4.5 to 4.8 and then version 4.9.
5. Observe and compare the output results.

### 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
- [ ] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: godot
Issue: Scenes can be saved outside project directory when using native file dialog
Labels: bug,platform:linuxbsd,topic:editor

### Tested versions

master[4a0160241fd0c1e874e297f6b08676cf0761e5e8]

### System information

Arch Linux

### Issue description

For example, I can "Save Branch as Scene" into somewhere outside the project directory. Trying to access this sub-scene fails.

https://github.com/godotengine/godot/assets/372476/249b5df4-f856-4262-bb23-1431d1fe540e

Exporting the resulting project won't fail though. The exported project tries to load that path on user's machine :P


### Steps to reproduce

1. Turn on interface/editor/use_native_file_dialogs in editor settings.
2. Right click on a node and "Save Branch as Scene".
3. Select somewhere outside the project directory.

### Minimal reproduction project (MRP)

N/A
Repository: rust
Issue: std::fs::symlink_metadata + set_permissions makes unintuitive behavior
Labels: A-lints,T-compiler,A-docs,T-libs

### Location

`std::fs::symlink_metadata` or `std::fs::set_permissions`

### Summary

```rust
fn main() -> std::io::Result<()> {
  use std::os::unix::fs::PermissionsExt;

  let path = std::path::PathBuf::from("bar");   // `bar` is a symlink
  let meta = std::fs::symlink_metadata(&path)?;
  let mut permissions = meta.permissions();
  println!("current mode: {:o}", permissions.mode());
  permissions.set_mode(0o707);
  println!("new mode: {:o}", permissions.mode());

  std::fs::set_permissions(&path, permissions)?;  // applied permission to original file

  let meta = std::fs::symlink_metadata(&path)?;
  let mut permissions = meta.permissions();
  println!("reloaded mode: {:o}", permissions.mode());
  Ok(())
}
```

```shell
current mode: 120755
new mode: 707
reloaded mode: 120755
```

Since I could obtain metadata for either original file or symlink, I expected there must be a way to apply permissions to symlink. But `symlink_metadata` revealed not to have a pair of `set_permissions`. 

By the design if it is intended or lack of API, it could be documented somewhere like `symlink_metadata` or `set_permissions`.

On the other hand, metadata is obtainable from either file or symlink. Then I expected `set_permission` to be placed on metadata object if metadata includes symlink information. 
e.g. `metadata.set_permissions(path, permissions)`
Repository: flutter
Issue: [flutter_lints] Consider including `discarded_futures` and `unawaited_futures`
Labels: c: new feature,package,c: proposal,team-ecosystem,P2,p: flutter_lints,triaged-ecosystem

### Use case

I did not understand correctly how to you async and Futur the right way because these two linter rules are not activated by default
```
  - discarded_futures
  - unawaited_futures
```

### Proposal

I think they should be activated by default or at least mentioned in https://dart.dev/codelabs/async-await
that would have avoided a lot of pain in my learning...
Repository: deno
Issue: issue with permission prompt and vite create 
Labels: bug,permissions

Version: deno 1.42.4+c0f40ed

` deno run  --allow-env --allow-read npm:create-vite@latest test`

choose vanilla typescript, then deno ask for write permission for mkdirsync:
- Actual: when I input something (like `y` or `n`) it gets ignored the first time, and I have to reineput it again
- Expected: when input something it gets accepted immediately like usual 
[Screencast from 2024-04-20 18-22-44.webm](https://github.com/denoland/deno/assets/22427111/810e2cbe-9d32-421b-bc59-aebfada92c72)

I opened this issue even if its minor, because its reproducible, I noticed this for a while now
Repository: storybook
Issue: [Documentation]: Svelte - Better documentation for decorators/render function
Labels: help wanted,documentation,svelte

### Describe the problem

It's not very clear how to use decorators/the render function in Svelte correctly.

For example, the return value of a decorator function is a Story Result - but it's not quite clear how to use that in Svelte. In React, it's just some JSX, but in Svelte it's an object with 4 undocumented properties - `Component` and `props` (self-explaining), but also `on` and `decorator` (no idea what they do).
It is mentioned that you can choose what component to render and with what props:

```ts
return {
    Component: SomeComponent,
    props: { prop1: 1, prop2: 2 }
}
```

But nothing more than that. The section about custom render functions linked in a couple of pages is [missing](https://storybook.js.org/docs/api/csf) (choose Svelte and click on "Custom render function" in the table of contents on the right). I tried returning some component in the `decorator` property, which I realised exists because of TypeScript autocomplete, but it doesn't seem to do anything:

```ts
return {
    Component: SomeComponent,
    props: { prop1: 1, prop2: 2 },
    decorator: MyWrapper,
}
```

I would expect this to render this:

```html
<MyWrapper>
    <SomeComponent {...props} />
</MyWrapper>
```

But the wrapper component is never actually instantiated. It also seems like you can actually use React hooks in decorators, even when using Svelte. By doing some more digging, this seems to work:

```ts
// preview.ts
import type { Preview } from "@storybook/svelte"
import { global } from "@storybook/global"
import { useEffect } from "@storybook/preview-api"

const preview: Preview = {
    decorators: [
        (Story) => {
            useEffect(() => {
                console.log("In effect", global.document.getElementById("storybook-root"))
            }, [])
            return Story()
        }
    ]
}
```

But this isn't really documented anywhere, The only time this is mentioned is in the "Writing addons" sections. But even there, `global` is not documented. Both are extremely useful for decorators.

Finally, in [this PR](https://github.com/storybookjs/storybook/pull/13785) it is stated you can set Svelte contexts, which is not stated anywhere in the docs. This is incredibly useful, as the only decorator example given in the docs is `() => MarginDecorator`, and it doesn't explain how one would set the margin size, for example, based on global arguments. This is actually possible to do (as described in the PR above) like so:

```js
import { setContext } from 'svelte'

const decorator = () => {
    setContext('marginDecoratorSize', 12)
    return MarginDecorator
}
```

The `MarginDecorator` component can then do `getContext('marginDecoratorSize')`.

### Additional context

_No response_
Repository: godot
Issue: Unsafe cast when loading WAV files
Labels: bug,topic:audio,topic:import

### Tested versions

4.2.1
4.3.dev5

### System information

Windows 10 x64

### Issue description

[There is](https://github.com/godotengine/godot/blob/master/editor/import/resource_importer_wav.cpp#L200)(link) unsafe cast from `uint32_t` to `int` 
```
frames = chunksize;
```

If you try to load WAV file with size more then INT_MAX (2147483647) you'll get `frames < 0`, and after [some lines of code](https://github.com/godotengine/godot/blob/master/editor/import/resource_importer_wav.cpp#L213)
you will get a not clear message 
> ERROR: Condition "p_size < 0" is true. Returning: ERR_INVALID_PARAMETER
   at: CowData<float>::resize (core/templates/cowdata.h:314)

Or, if workstation have small amout of RAM (8Gb)  - Godot also crash


As a partial solution you can add check like this after [this line](https://github.com/godotengine/godot/blob/master/editor/import/resource_importer_wav.cpp#L150) 
```
if (chunksize > INT_MAX) {
		ERR_FAIL_V_MSG(ERR_INVALID_DATA, "File too big.");
}
```
but it not well IMO. May be better to constraint file size with understandable message for Godot user.
WAV file can be 4Gb as `chunksize` is unsigned 32bit int [wiki ](https://en.wikipedia.org/wiki/WAV#:~:text=The%20WAV%20format%20is%20limited,record%20the%20file%20size%20header.), but in Godot data also stored in `Vector<float>`, and it require big amount of memory and mine 32Gb not enougth(I try to rebuild Godot changing `frames` type to `uint32_t` and got exception with `stosb` assembler instruction )


### Steps to reproduce

Try to import big WAV file, more then 2147483647 bytes

### Minimal reproduction project (MRP)

N/A
Repository: flutter
Issue: [Proposal] Reduce warnings in flutter.groovy file 
Labels: platform-android,tool,t: gradle,c: proposal,P2,team-android,triaged-android

### Use case

right now **(using flutter 3.19.6)** when opening the _android module_ in android studio the `flutter.groovy` file located inside `...\flutter\packages\flutter_tools\gradle\src\main\groovy\flutter.groovy` needs some refactoring and cleaning because it has more then 70 warnings right now (some libraries are deprecated,some unused methods ...): 
i couldn't upload the code cz github has a limit in the body length so it's [here](https://github.com/AbdeMohlbi/flutter_groovy_pr/blob/main/flutter_old.groovy)

### Proposal

the updated version can be found [here](https://github.com/AbdeMohlbi/flutter_groovy_pr/blob/main/flutter_new.groovy)
note that i haven't change or delete any function or messed any kind of logic just cleaned a bit and did as same as [here](https://github.com/flutter/flutter/issues/146036) to get rid of buildDir deprecation(there is now 31 warnings )
Repository: bitcoin
Issue: `keypoolrefill` doesn't fill keypool to specified parameter
Labels: Wallet

### Is there an existing issue for this?

- [X] I have searched the existing issues

### Current behaviour

According to the help manual the parameter is `newsize` and `keypoolrefill` fills the keypool to `newsize`. This was the behavior up to at least v21 of bitcoind. In v24 of bitcoind these semantics have changed. Related to https://github.com/bitcoin-s/bitcoin-s/pull/5496

```
$ bitcoin-cli -regtest getwalletinfo
{
  "walletname": "",
  "walletversion": 169900,
  "format": "sqlite",
  "balance": 50.00000000,
  "unconfirmed_balance": 0.00000000,
  "immature_balance": 3675.00000000,
  "txcount": 101,
  "keypoolsize": 4000,
  "keypoolsize_hd_internal": 4000,
  "paytxfee": 0.00000000,
  "private_keys_enabled": true,                                                                                                                                                                             
  "avoid_reuse": false,        
  "scanning": false,
  "descriptors": true,
  "external_signer": false
}
```

So I have a keypool of size `4,000`

```
$ bitcoin-cli -regtest keypoolrefill 4001
```

Somehow I end up with a keypool size of 16,004?

```
$ bitcoin-cli -regtest getwalletinfo
{
  "walletname": "",
  "walletversion": 169900,
  "format": "sqlite",
  "balance": 50.00000000,
  "unconfirmed_balance": 0.00000000,
  "immature_balance": 3675.00000000,
  "txcount": 101,
  "keypoolsize": 16004,
  "keypoolsize_hd_internal": 16004,
  "paytxfee": 0.00000000,
  "private_keys_enabled": true,
  "avoid_reuse": false,
  "scanning": false,
  "descriptors": true,
  "external_signer": false
}
```

### Expected behaviour

I would expect `keypoolrefill` to fill up the keypool to the given parameter.

### Steps to reproduce

Run commands given in the issue

### Relevant log output

_No response_

### How did you obtain Bitcoin Core

Pre-built binaries

### What version of Bitcoin Core are you using?

Bitcoin Core version v24.2.0

### Operating system and version

Darwin 23.4.0 Darwin Kernel Version 23.4.0: Fri Mar 15 00:12:41 PDT 2024; root:xnu-10063.101.17~1/RELEASE_ARM64_T8103 arm64

### Machine specifications

_No response_
Repository: ollama
Issue: My internet is too slow to download the model
Labels: feature request,networking

### What is the issue?

I keep getting the same error

>  ollama run llama3
> pulling manifest
> pulling 00e1317cbf74...   1% ▕                                                                                                            ▏  28 MB/4.7 GB   61 KB/s  20h58m
> Error: max retries exceeded: Get "https://dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com/ollama/docker/registry/v2/blobs/sha256/00/00e1317cbf74d901080d7100f57580ba8dd8de57203072dc6f668324ba545f29/data?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=66040c77ac1b787c3af820529859349a%!F(MISSING)20240420%!F(MISSING)auto%!F(MISSING)s3%!F(MISSING)aws4_request&X-Amz-Date=20240420T204533Z&X-Amz-Expires=1200&X-Amz-SignedHeaders=host&X-Amz-Signature=8e4efa642799d32a9e502990baa74226f9f0f740b2cdb7ed0bd6b6741e0106df": net/http: TLS handshake timeout

Is there a way to download llama3 externally and then use it with ollama?

Many thanks

### OS

Windows

### GPU

Nvidia

### CPU

Intel

### Ollama version

0.1.32
Repository: node
Issue: WASI stdio (stdin, stdout) API not very useful
Labels: feature request,wasi,stale,never-stale

### What is the problem this feature will solve?

Currently the WASI API only lets you give file descriptors for stdin, stdout and stderr. That's not very useful. In most cases I want to interact with these streams which doesn't seem possible - at least not without a ton of platform specific work - with just file descriptors.

### What is the feature you are proposing to solve the problem?

You should be able to pass `ReadableStream` and `WritableStream` instead. You can do this when spawning subprocesses.

### What alternatives have you considered?

Slightly ludicrously, spawning a new child process that just starts the WASI module and does nothing else seems to be the most reasonable workaround currently, though I haven't tried it.
Repository: flutter
Issue: Missing part of map while moving on Android
Labels: platform-android,p: maps,package,has reproducible steps,P2,team-android,triaged-android,found in release: 3.19,found in release: 3.22

### What package does this bug report belong to?

google_maps_flutter

### What target platforms are you seeing this bug on?

Android

### Have you already upgraded your packages?

Yes

### Steps to reproduce

1. Using google maps widget
2. Moving map and zooming in and out

### Expected results

Smooth map camera without white boxes appearing. On iOS working properly and smoothly. 

### Actual results

White boxes appear as in video. Sometimes you can see outlines of buildings even though they are disabled. 

### Code sample

<details open><summary>Code sample</summary>

```dart
 GoogleMap(
            style: MapStyle.style,//json string from assets/map_style.json
            padding: EdgeInsets.only(
              top: MediaQuery.of(context).viewPadding.top +
                  180,
              bottom: 15,
            ),
            onMapCreated: c.onMapCreated,
            initialCameraPosition: 
                CameraPosition(
                  target: c.center,
                  zoom: 16.5,
                ),
            myLocationButtonEnabled: true,
            myLocationEnabled: true,
            markers: c.markers.values.toSet(),
            buildingsEnabled: false,
            compassEnabled: true,
          )
```

</details>


### Screenshots or Videos

<details open>
<summary>Screenshots / Video demonstration</summary>

[record.webm](https://github.com/flutter/flutter/assets/76404640/530da26e-ed5c-43dd-b2db-6f5a004b1369)

</details>

### Flutter Doctor output

<details open><summary>Doctor output</summary>

```console
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.19.5, on Arch Linux 6.8.4-arch1-1, locale C.UTF-8)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.3)
[✓] IntelliJ IDEA Community Edition (version 2024.1)
[✓] Connected device (2 available)
[✓] Network resources

• No issues found!

```

</details>
Repository: godot
Issue: Changes to CollisionShape2D debug color project setting are not applied due to the previous default color being considered as custom
Labels: bug,topic:editor,topic:physics,topic:2d

### Tested versions

- Reproducible in: 4.3.dev b091162a9

### System information

Godot v4.3.dev (4a0160241) - Fedora Linux 39 (KDE Plasma) - X11 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4090 (nvidia; 550.67) - 13th Gen Intel(R) Core(TM) i9-13900K (32 Threads)

### Issue description

Changes to CollisionShape2D debug color project setting are not applied due to the previous default color being considered as custom:

![image](https://github.com/godotengine/godot/assets/180032/92bb2a2a-bd20-43a2-b7bf-8cb1f247015d)

https://github.com/godotengine/godot/assets/180032/8208ad7a-e514-4271-9f89-69f448f64b34

To resolve this, I suggest using the RayCast3D custom debug color behavior instead:

![image](https://github.com/godotengine/godot/assets/180032/9fb92a67-c4ee-4814-a1ff-fd2a30721bcd)

An opaque black color is considered as being "no override". In practice, you'll almost never want a debug shape to be opaque black – and if you really want to, you can use `#010101` or `#000001` anyway.

### Steps to reproduce

- Create a CollisionShape2D with a CircleShape2D.
- Change debug shape color in the project settings.
- Select another node and select the CollisionShape2D again to force the inspector to update.
- Notice how the default debug colors becomes considered as a custom debug color in the CollisionShape2D inspector, which means 2 things:
  - The new default color isn't automatically applied; you have to click the reset icon instead.
  - The old debug color is written to the scene file as it's a non-default value.

### Minimal reproduction project (MRP)

N/A