sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: Rust should warn for unused "pure" objects
Labels: A-diagnostics,T-compiler

### Code

```Rust
use std::path::PathBuf;

fn main() {
    let mut buf = PathBuf::new();
    buf.push("/something");
}
```


### Current output

```Shell
Compiling playground v0.0.1 (/playground)
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.64s
     Running `target/debug/playground`
```


### Desired output

```Shell
Warning: buf is written to but never read.
```


### Rationale and extra context

Here `push` is a side effect free operation, it only modifies memory belonging to the object. With some sort of attribute or other annotation it should be possible to tell rustc about this, allowing more warnings about unused objects to be produced. The standard library should use such attributes where appropriate (various methods on `String`, `str`, `PathBuf`, etc).

Do note that for generic types such as `Vec<T>` this might be tricky, as `T` would also have to be side effect free (e.g. warning about `Vec<i32>::push` is good, `Vec<MutexGuard>::push` is probably not), I'm not sure about the best way to handle that, or if it should just be punted to the future.

### Other cases

_No response_

### Rust Version

```Shell
❯ rustc --version --verbose
rustc 1.79.0 (129f3b996 2024-06-10)
binary: rustc
commit-hash: 129f3b9964af4d4a709d1383930ade12dfe7c081
commit-date: 2024-06-10
host: x86_64-unknown-linux-gnu
release: 1.79.0
LLVM version: 18.1.7
```


### Anything else?

Having a warning for this would have saved me time in the profiler (yes, in a hot loop left over (otherwise refactored) pathbuf construction was actually causing a noticable slowdown in my program).
Repository: flutter
Issue: SpellCheckConfiguration for TextField doesn't work with AppLocalizations on iOS
Labels: a: text input,platform-ios,framework,a: internationalization,has reproducible steps,P2,team-ios,triaged-ios,found in release: 3.22,found in release: 3.24

### Steps to reproduce

1. Add Internationalizing to the app by flutter_localizations and intl (https://docs.flutter.dev/ui/accessibility-and-internationalization/internationalization)
2. Add spellCheckConfiguration parameter to the TextField
3. Try to write wrong words 

### Expected results

Spell check works with AppLocalization on Android and iOS

### Actual results

Spell check doesn't work with AppLocalization on iOS (there is no problem on Android)

### Code sample

<details open><summary>Code sample</summary>

https://github.com/tatraef/spell_bug.git

</details>


### Screenshots or Video

<details open>
<summary>Screenshots / Video demonstration</summary>

<img width="747" alt="Screenshot 2024-07-13 at 17 35 44" src="https://github.com/user-attachments/assets/282023dc-819c-4c49-b324-9f5063986874">
<img width="746" alt="Screenshot 2024-07-13 at 17 36 34" src="https://github.com/user-attachments/assets/12ed4b3d-f145-4cb0-bb6c-e36b74fd37e0">

</details>


### Logs

_No response_

### Flutter Doctor output

<details open><summary>Doctor output</summary>

```console
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.22.2, on macOS 14.5 23F79 darwin-arm64, locale en-RU)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 15.4)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.3)
[✓] VS Code (version 1.81.1)
[✓] Connected device (5 available)
[✓] Network resources
```

</details>
Repository: next.js
Issue: Suspense not working in a nested route 
Labels: bug,Partial Prerendering (PPR)

### Link to the code that reproduces this issue

https://github.com/HermesThemes/ArtDungeon

### To Reproduce

1-npm run dev
2- navigate to /post/[id]


### Current vs. Expected behavior

after step 2 you can see that is show the data directly and if i added a sleep function of 5 second it will wait all that time and not showing a suspense fallback
I expect to the the suspense fallback just like in other route (note: suspense is not working only on a nested route, folder inside folder)

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Wed, 17 Apr 2024 15:20:28 +0000
  Available memory (MB): 7845
  Available CPU cores: 4
Binaries:
  Node: 21.7.3
  npm: 10.5.2
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.2.4
  eslint-config-next: 14.2.3
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.4.5
Next.js Config:
  output: N/A
```


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

Not sure, Partial Prerendering (PPR)

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

next dev (local)

### Additional context

This bug seems to happen only in a nested route, as the same component or page will work very well in the main route, I tested the same component (Post) in in a dynamic route and it's not working but works on the main page.js 

https://github.com/user-attachments/assets/6690a23b-f932-4596-80a3-0a02c07bc511
Repository: stable-diffusion-webui
Issue: [Feature Request]: Enter key to submit the prompt - 2
Labels: enhancement

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What would your feature do ?

Pressing "Enter" key would submit the prompt, just like most messaging apps do
Just Enter key, not Ctrl+Enter (yes I am aware)

### Proposed workflow

1. Go to .... prompt
2. Press .... Enter key
3. ... Generation starts


### Additional information

Same request was already asked but was closed by someone because there's this "Ctrl+Enter"
But it's not same, and simple Enter key would speed things a lot
Any way to add this feature? Would be fantastic
Thanks!
Repository: vscode
Issue: Give options for outliner
Labels: info-needed,editor-sticky-scroll

We need 
- collapse (and option to show just class, functions)
- open all in tree
- search context
- indicate item line code next to item (before name or after eg. #no #100 Function)
- discrete separators from class functions and vars
- icons to hide some items, or option to include fact that item is hidden in code (collapsed by arrow - but also can be nice collapsed in code from outline)
- the indicated name on documents is by buble above name, should be some other type like just focus row
- for some reason class separator and continuation looks ugly
![vsc sep](https://github.com/user-attachments/assets/ccd72750-9494-455f-a5b0-612eead43eec)

VS Code version: Code 1.89.1 (dc96b837cf6bb4af9cd736aa3af08cf8279f7685, 2024-05-07T05:13:33.891Z)
OS version: Windows_NT x64 10.0.22631
Modes:



<!-- generated by issue reporter -->
Repository: ollama
Issue: Add model metadata which indicated model purpose to /api/tags endpoint.
Labels: feature request,api

It would be nice if part of the **/api/tags** response detals would include metadata such as:

`type: embedding | general | code | math | vision | audio` etc...
`languages: [en-US, ...]`

This could help with model sorting and selection.
If metadata is not available maybe add an option to mark it with metadata by the user.
Repository: tauri
Issue: [bug] Using "message": true dialog causes App to not open (in dev or release build)
Labels: type: bug,priority: 2 medium,platform: Windows,status: needs triage

### Describe the bug

 Im trying to use the "message" dialog in my tauri app, yet everytime I set "message": true in tauri.conf.json, the app fails to even open, even though there are no errors. I tried building both dev/build with verbose and no errors show up. As soon as I set "message": false and build again,  it starts working fine (of course the message dialog does not appear). This is on Windows 10

tauri.conf.json setting:
```
"dialog": {
        "all": false,
        "open": true,
        "message": true
      },
```
      
 Logs from the build...
```
0 verbose cli C:\Program Files\nodejs\node.exe C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js
1 info using npm@10.7.0
2 info using node@v20.15.0
3 silly config:load:file:C:\Program Files\nodejs\node_modules\npm\npmrc
4 silly config:load:file:xxxxxx\.npmrc
5 silly config:load:file:C:\Users\xxxx\.npmrc
6 silly config:load:file:C:\Users\xxxx\AppData\Roaming\npm\etc\npmrc
7 verbose title npm run dev
8 verbose argv "run" "dev"
9 verbose logfile logs-max:10 dir:C:\Users\xxxxx\AppData\Local\npm-cache\_logs\2024-07-13T20_54_16_468Z-
10 verbose logfile C:\Users\xxxxx\AppData\Local\npm-cache\_logs\2024-07-13T20_54_16_468Z-debug-0.log
11 silly logfile start cleaning logs, removing 1 files
12 silly logfile done cleaning log files
13 verbose exit 4294967295
14 verbose code 4294967295
```


### Reproduction

_No response_

### Expected behavior

The message dialog should work fine

### Full `tauri info` output

```text
✔] Environment
    - OS: Windows 10.0.19045 X64
    ✔ WebView2: 126.0.2592.102
    ✔ MSVC:
        - Visual Studio Build Tools 2019
        - Visual Studio Build Tools 2022
    ✔ rustc: 1.79.0 (129f3b996 2024-06-10)
    ✔ cargo: 1.79.0 (ffa9cf99a 2024-06-03)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (default)
    - node: 20.15.0
    - npm: 10.7.0

[-] Packages
    - tauri [RUST]: 1.7.1
    - tauri-build [RUST]: 1.5.3
    - wry [RUST]: 0.24.10
    - tao [RUST]: 0.16.9
    - @tauri-apps/api [NPM]: 1.6.0
    - @tauri-apps/cli [NPM]: 1.6.0

[-] App
    - build-type: build
    - CSP: unset
    - distDir: ../dist
    - devPath: http://localhost:1420/
    - framework: Vue.js
    - bundler: Vite
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: PowerToys
Issue: Add a Contents submenu to the context menu for folders
Labels: Idea-New PowerToy,Needs-Triage

### Description of the new feature / enhancement

Instead of opening a folder in Windows Explorer to look at files and sub-folders, it may be easier if we have the "Contents" submenu added to the context menu for folders. This makes it easier to view or click any file or sub-folder.

### Scenario when this would be used?

Right clicking a folder will show the "Contents" submenu. If we right-click a folder and point to "Contents," a submenu will open and we can see files and sub-folders.

### Supporting information

The "Contents" submenu can either be shown as default or only when we hold SHIFT and right-click the folder. The "Contents" submenu won't be shown when right-clicking a file.
Repository: godot
Issue: Fix ViewportTexture's "has_alpha()" returning false when the SubViewport it's from, has "transparent_bg" turned on.
Labels: discussion,topic:rendering,documentation,topic:gui

### Tested versions

v4.2.2.stable.official [15073afe3]

### System information

Godot v4.2.2.stable - Windows 10.0.22631 - Vulkan (Forward+)

### Issue description

The **ViewportTexture** from a **SubViewport** with `transparent_bg` on, when calling `has_alpha()` on it, will always return _false_, despite `transparent_bg` being turned on.

Using `ViewportTexture.get_image()` is too resource-intensive for some use cases like mine, where I just have to differentiate pixels from one another in any way, from a texture created by a shader (To let the GPU handle the lag-inducing math that would normally occur on the CPU).

**Texture2D**'s `_is_pixel_opaque()` function is virtual, hence inaccessible.

I expect a **ViewportTexture**, when `transparent_bg` is on, to be able to have an alpha channel. This actually seems to be the case, as when calling `ViewportTexture.get_image().get_pixel(x: int, y: int).a` on a transparent pixel, it returns a value of 0 for the alpha, and for an opaque pixel, returns 1 for  the alpha. As a contradiction, `ViewportTexture.has_alpha()` returns _false_.

Using a **Sprite2D**'s `is_pixel_opaque(pos: Vector2)`, likewise, works if has_alpha() is _true_. And this is not the case for the **ViewportTexture** that gets returned.

Anything fast that can be called hundreds of times in GDScript that would allow fetching a pixel's data in a given **Texture2D**, in order to differentiate pixels from one another, would do for similar use cases, as this would mean one could let the GPU handle lots of maths that would otherwise be very laggy on the CPU.

### Steps to reproduce

1. Add a **SubViewport** and turn on `transparent_bg`
2. Add a **TextureRect** / **Sprite2D** as a child of it
3. Make the texture have transparent bits (I used a shader to do this in the example project, but same thing occurs with a png)
4. Use `get_texture()` on the **SubViewport**
5. On this **ViewportTexture**, call `has_alpha()`, which will be _false_
6. On this **ViewportTexture**, call `get_image().get_pixel(x:int, y:int)` on a pixel that is transparent. It will have an alpha value of 0, and the opaque bits will have an alpha value of 1, therefore contradicting step 5.

This, if the **ViewportTexture** is assigned to a **Sprite2D**'s texture, makes the **Sprite2D**'s `is_pixel_opaque(pos: Vector2)` unusable, as it will only return _true_.

### Minimal reproduction project (MRP)

[TextureViewport Alpha Issue.zip](https://github.com/user-attachments/files/16203699/TextureViewport.Alpha.Issue.zip)
Repository: next.js
Issue: OpenTelemetry Tracing is poluted with some extra spans from middlewares
Labels: bug,Middleware,Internationalization (i18n)

### Link to the code that reproduces this issue

https://github.com/pksorensen/nextjs-repro-otel

### To Reproduce

1. configure som otel endpoint and replace .env
2. Start npm run dev
3. monitor traces

### Current vs. Expected behavior

It is emiting this wierd trace with `next.bubble | true`  which seems related to old bug https://github.com/vercel/next.js/issues/55752 where i dont fully get what is going on at 
![image](https://github.com/user-attachments/assets/ec52968f-2016-454a-9edf-2530f8a1e702)

 
![image](https://github.com/user-attachments/assets/3f43079e-d90a-4578-9cbd-d500028c32ce)

The expected trace is there also
![image](https://github.com/user-attachments/assets/851e26ef-31e6-4bcb-a176-c54af5542e38)
which has all the childs,
![image](https://github.com/user-attachments/assets/61a3f05e-20d7-450c-bad9-90ca3f256511)

so either that first one /da/ should be a child of /[locale] or not there at all ?

I think its related to also that middleware does not run with the same traceid that the request is doing. 

I added 
```
function withTraceParent(res: NextResponse) {
    const spanContext = trace.getActiveSpan()?.spanContext();
    if (spanContext)
        res.cookies.set("traceparent", `00-${spanContext.traceId}-${spanContext.spanId}-0${spanContext.traceFlags}`);
    return res;
};
```

to the middleware and can inspect that the traceparent set in cookie from within the middleware is totally different from those in the above request (either of the two base requests)


### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Enterprise N
  Available memory (MB): 32687
  Available CPU cores: 16
Binaries:
  Node: 20.9.0
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 15.0.0-canary.65 // Latest available version is detected (15.0.0-canary.65).
  eslint-config-next: N/A
  react: 19.0.0-rc-6f23540c7d-20240528
  react-dom: 19.0.0-rc-6f23540c7d-20240528
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


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

Internationalization (i18n), Middleware

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

next dev (local), next start (local), Other (Deployed)

### Additional context

_No response_
Repository: rust
Issue: Encountering the type length limit ICEs Miri
Labels: I-ICE,T-compiler,C-bug,A-const-eval,T-types

The following program ICEs Miri when invoked with `-Zenforce-type-length-limit`:
```rust
#![type_length_limit = "8"]
fn main() {}
```
Miri reports:
```
Miri caused an ICE during evaluation. Here's the interpreter backtrace at the time of the panic:
note: the place in the program where the ICE was triggered
   --> /home/ben/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/rt.rs:140:5
    |
140 |     panic::catch_unwind(move || unsafe { init(argc, argv, sigpipe) }).map_err(rt_abort)?;
    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |
    = note: BACKTRACE:
    = note: inside `std::rt::lang_start_internal` at /home/ben/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/rt.rs:140:5: 140:70
    = note: inside `std::rt::lang_start::<()>` at /home/ben/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/rt.rs:158:17: 163:6

error: internal compiler error: src/tools/miri/src/diagnostics.rs:324:17: This error should be impossible in Miri: encountered overly generic constant

thread 'rustc' panicked at src/tools/miri/src/diagnostics.rs:324:17:
<backtrace to Miri's error reporting code, not relevant>
```

I'm filing this here because I'm pretty sure the problem is that the core interpreter logic does not handle the new failure path out of `Instance::try_resolve` correctly.

```
rustc 1.81.0-nightly (c6727fc9b 2024-07-12)
binary: rustc
commit-hash: c6727fc9b5c64cefa7263486497ee95e529bd0f8
commit-date: 2024-07-12
host: x86_64-unknown-linux-gnu
release: 1.81.0-nightly
LLVM version: 18.1.7
```
Repository: godot
Issue: UV2 Does Not Update When Light Bake Setting Changed
Labels: bug,topic:editor,topic:import,topic:3d

### Tested versions

4.3 Beta 3

### System information

Windows 11, Nvidia RTX4070ti, AMD Ryzen7700x

### Issue description

If a mesh has a custom UV2, switchin from Static to Static Lightmaps (and vice versa) for Light Baking and hitting Reimport does not update the lightmap until the scene is reloaded. The completed bake will act like the setting was never changed.
If the only mesh in the scene has no UV2, switching from Static to Static Lightmaps causes Godot to warn the user that no UV2 is available for lightmapping. The scene must be reloaded to rectify.

### Steps to reproduce

- Open MRP
- Change the Light Bake setting
- Bake the lightmap, no change
- Close and reload the scene
- UV2 will be updated, bake must be redone

### Minimal reproduction project (MRP)

[customlightmapbugv2.zip](https://github.com/user-attachments/files/16208961/customlightmapbugv2.zip)
Repository: terminal
Issue: new windows will only attach to previously used window if terminal is already running
Labels: Issue-Bug,Product-Terminal,Priority-3,Area-Windowing

### Windows Terminal version

1.20.11781.0

### Windows build number

10.0.19045.3930

### Other Software

_No response_

### Steps to reproduce

Settings:

- When Terminal starts: Open windows from a previous session
- New instance behaviour: Attach to the most recently used window

### Expected Behavior

Open previously used window and attach to it as new tab.

### Actual Behavior

Opens new window and the previous one.
Repository: go
Issue: proxy.golang.org: allow Tor
Labels: NeedsInvestigation,proxy.golang.org

```reading
https://proxy.golang.org/google.golang.org/api/@v/v0.162.0.zip: 403 Forbidden
```
Please allow access from Tor exit nodes
Repository: godot
Issue: BBCode is inconsistent when used in  inspector tooltips with @export variables.
Labels: discussion,topic:editor,documentation,topic:gui

### Tested versions

v4.3.beta2.official [b75f0485b]

### System information

Linux Kubuntu 23.04 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8

### Issue description

Adding tooltips to @export variables does not support many bbcodes. 

![image](https://github.com/user-attachments/assets/5a5b7335-9f4b-4147-a8e9-c92ae8981726)


### Steps to reproduce

Create an empty 2D scene. E.g. `Control`
Add an external script to it. E.g. `control.gd
`
Add the following to script and save:
```gdscript
extends Control

## [p]Hello[/p]Notice no paragraph.
## [bgcolor=RED]Should be background red.[/bgcolor][br][i][color=green]THIS IS ITALIC AND GREEN.[/color][/i]
## [br]Click for more info url works [url=https://yahoo.com]https://yahoo.com[/url]
## [p][right]This is a paragraph but did not break[/right]
## [br][font_size=30]Should be 10[/font] font
## [br]Strangely enough the [ br ] acts as [br] paragraph, although not documented.
@export var maximum_speed:int=100
```

Now hover over the exported variable `maximum_speed`, in the inspector. You will see that only some of the bbcodes work. For example` [p], [bgcolor], [right] `are ignored and shown as text. As a matter of fact I have discovered an undocumented `[br] `break in lieu of `[p] `paragraph code.


### Minimal reproduction project (MRP)

Test project [Archive.zip](https://github.com/user-attachments/files/16214893/Archive.zip)
Repository: next.js
Issue: middleware: Return or Link to the home page, the index.json of the updated data is redirected
Labels: examples

### 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 20.6.0: Wed Jun 23 00:26:27 PDT 2021; root:xnu-7195.141.2~5/RELEASE_ARM64_T8101
  Available memory (MB): 16384
  Available CPU cores: 8
Binaries:
  Node: 18.20.0
  npm: 10.5.0
  Yarn: 1.22.15
  pnpm: N/A
Relevant Packages:
  next: 14.2.5 // Latest available version is detected (14.2.5).
  eslint-config-next: 14.2.5
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.5.3
Next.js Config:
  output: N/A
```


### Which example does this report relate to?

no

### What browser are you using? (if relevant)

chrome 126.0.6478.127

### How are you deploying your application? (if relevant)

next dev

### Describe the Bug

I am using the PageRouter  & basePath

Unable to get the correct props parameters either by linking to the home page via the Link TAB or returning to the home page via the browser's back button, the index.json request to update the home page was redirected

This problem comes up when I use middleware， The problem went away when I removed middleware


I  have tried all except the home page without this problem

### Expected Behavior

Return or link to the home page to update the home page data

### To Reproduce

<img width="782" alt="image" src="https://github.com/user-attachments/assets/ce2c72d2-7f2a-430a-915c-4f2f3f077aa7">
Repository: godot
Issue: @export script variables do not display tooltips when they are in built in script of node.
Labels: bug,topic:editor

### Tested versions

v4.3.beta2.official [b75f0485b]

### System information

Linux Kubuntu 23.04 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8

### Issue description

@export variable tooltips will not display if the script they are in is internal to a node.
![image](https://github.com/user-attachments/assets/a43fbf17-4ada-4a76-b6b1-ba3e252b02b4)


### Steps to reproduce

Create a new 2D scene e.g. Control
Create a built-in/internal script for Control.

Add the following code and save:


```gdscript
extends Control

## Here should be a tooltip
@export var maximum_speed:int=100
```

After save click in the inspetor variable and hover over `maximum_speed`. Notice no tooltip shows up.

### Minimal reproduction project (MRP)

n/a