sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: Request: clarity about what version "PowerShell" Means
Labels: Product-Settings,Needs-Triage,Product-CommandNotFound

### Description of the new feature / enhancement

With the new CmdNotFound tool, I am confused about what PowerShell I have installed. When I open my PowerShell app, I can choose between a few versions. Including "PowerShell" and "Developer PowerShell for VS 2022". The page in PT Settings, however, says I don't have either of the required components (PowerShell 7.4+ and WinGet Client) installed. Am I missing something? And what is the exact version (or source) when I click on <kbd>Install</kbd> ?

### Scenario when this would be used?

?

### Supporting information

powershell.exe = 10.0.22621.2506, but I also have
%SystemRoot%\System32\WindowsPowerShell\v1.0\powershell.exe
Windows Terminal = 1.18.3181.0
![image](https://github.com/microsoft/PowerToys/assets/65828559/126ea95c-ee86-4565-8497-5ba89eef9dec)
Repository: terminal
Issue: Problem switching in and out of UTF-8 mode
Labels: Product-Conhost,Help Wanted,Area-VT,Issue-Bug

### Windows Terminal version

1.18.3181.0

### Windows build number

10.0.22621.0

### Other Software

_No response_

### Steps to reproduce

Output the character sequence twice using a tool of your choice:
`Esc % G E2 A3 BF Esc % @`

### Expected Behavior

Each time, the unicode character 28FF ⣿ (Braille Pattern Dots-12345678) will be printed.

### Actual Behavior

The correct character is printed the first time, the second time (and any subsequent times) prints "â£¿".

From my reading of the code, this is because Esc % @ (Select Default Character Set) correctly disengages UTF-8 by calling DesignateCodingSystem in ActionCsiDispatch.  However, its companion seuqnece Esc % G (Select UTF-8 Character Set) is not handled and thus the sequence is never again rendered in Unicode.
Repository: stable-diffusion-webui
Issue: [Feature Request]: Simple Lora XYZ test
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 ?

Suggestion to implement XYZ tester which works with LoRa models, such as `ABC:0.0-1.0 (+0.1)`

At this moment each time I have to write `ABC:0.0, ABC:0.1, ABC:0.2`, and so on.

### Proposed workflow

1. Include the LoRa model "**ABC**" in the prompt
2. Choose the XYZ tester and enter the LoRa model title as "**ABC**" in the input
3. We aim to test various model _weight_ combinations, so we include the "**:**" symbol and specify the starting and ending numbers as "**0.0-1.0**"
4. We need to review combinations that change every "0.1" weight until the weight reaches a maximum of "1.0". In this case we write number in brackets, like: **(+0.1)**
5. Final XYZ input looks like this: **ABC:0.0-1.0 (+0.1)**

### Additional information

Increasing the weight means we will need to generate it 10 times.
**New method** and input `ABC:0.0-1.0 (+0.1)` replaces **Prompt S/R** function/input:
`ABC:0.0,ABC:0.1,ABC:0.2,ABC:0.3,ABC:0.4,ABC:0.5,ABC:0.6,ABC:0.7,ABC:0.8,ABC:0.9,ABC:1.0`

*This suggestion only for _model weight_
Repository: next.js
Issue: Infinite Network Requests and Website Freeze with Two Intercepting Routes: /(.)[id1]/[id2] and /[id1]/(.)[id2]
Labels: bug,Parallel & Intercepting Routes

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/quirky-wave-j8wtlv

### To Reproduce

1. Run `next dev` and go to `http://localhost:3000`
2. Click the link `to /1/2`
3. The website will stuck and you can see tons of network requests in your browser developer tools.
4. If you click the link `to /1` then click `to /1/2`, you will see a 404 page.

### Current vs. Expected behavior

Expected behavior: I should see `id2-intercept-(.)[id1]/[id2]` on my screen, which is provided by `/app/@modal/(.)[id1]/[id2]/page.tsx`

Current behavior: The website gets stuck.

### Verify canary release

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

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Sun Aug  6 20:05:33 UTC 2023
Binaries:
  Node: 20.9.0
  npm: 9.8.1
  Yarn: 1.22.19
  pnpm: 8.10.2
Relevant Packages:
  next: 14.0.5-canary.40
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.1.3
Next.js Config:
  output: N/A
```


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

App Router, Routing (next/router, next/navigation, next/link)

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

next dev (local), next build (local), next start (local), Vercel (Deployed)

### Additional context

When I remove the directory `/app/[id1]/@modal`, the issue will disappear. However, this will prevent me from using  intercepting routes within `/[id1]`.

I also noticed next.js compiled both routes (`/(.)[id1]/[id2]` and `/[id1]/(.)[id2]`) when I click the link to `/1/2`.
```
 ○ Compiling / ...
 ✓ Compiled / in 1492ms (450 modules)
 ○ Compiling /(.)[id1]/[id2] ...
 ✓ Compiled /(.)[id1]/[id2] in 827ms (454 modules)
 ✓ Compiled /[id1]/(.)[id2] in 396ms (457 modules)
```
Repository: go
Issue: go/printer: incorrect *Config.Format results with +build comments and the SourcePos mode
Labels: NeedsInvestigation

<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

8db131082d08e497fd8e9383d0ff7715e1bef478 (tip, as of time of writing)

### What did you do?

Here is an example reproducer: https://go.dev/play/p/sphL42iaX_a

I think it's a pretty obscure issue which requires a few things:

1. the SourcePos mode enabled
2. one or more `// +build` constraints, and no `//go:build` comments
3. a change in the AST before the first `//+build` comment which offsets position such that the printer has to emit a `//line` directive

As far as I can tell, here's what's going wrong:

* the call to `printer.*Config.Fprint` will fully print the given node (a File) and then call [fixGoBuildLines](https://github.com/golang/go/blob/ead47b0ab39c5819aee207cda536531a8e44ddc7/src/go/printer/gobuild.go#L13) to consolidate build directives and translate "plus builds" to the current `//go:build` format
* when printing comments, build constraints are [special-cased](https://github.com/golang/go/blob/ead47b0ab39c5819aee207cda536531a8e44ddc7/src/go/printer/printer.go#L642): the current position of the writer is recorded to `p.plusBuild`, then the comment is written with `p.writeString`
* writeString checks if `SourcePos` is enabled and, if necessary, emits a line directive before writing its arg string to the output buffer

After printing, fixGoBuildLines turns `//+build` comments into `//go:build` by iterating the positions in `p.plusBuild` and parsing the constraints at each:
```
for _, pos := range p.plusBuild {
	y, err := constraint.Parse(p.commentTextAt(pos))
	if err != nil {
		x = nil
		break
	}
    ...
```

Because of SourcePos, the offsets recorded to `p.plusBuild` can incorrectly point to a `//line` comment, rather than a valid build constraint, so parsing fails, the loop exits, and subsequent plusBuild lines are ignored and the inserted block will be incomplete/incorrect. 

### What did you expect to see?

* `//+build` constraints should have been preserved and/or translated to `//go:build`
* I'm not sure if there's any value in a line directive on the build constraint comment -- perhaps that can be omitted.

### What did you see instead?

In the reproducer, one of the build constraints is omitted and a seemingly unnecessary line directive is printed ts the top of the file.
Repository: PowerToys
Issue: Batch renaming files using item enumeration when the new name already exists causes unexpected behavior
Labels: Issue-Bug,Product-PowerRename,Needs-Triage

### Microsoft PowerToys version

0.76.1

### Installation method

GitHub

### Running as admin

Yes

### Area(s) with issue?

PowerRename

### Steps to reproduce

Having a folder with the following files and selecting all of them:
* bill-01-23.pdf
* bill-02-23.pdf
* bill-03-23.pdf
* ... 
* bill-11-23.pdf

And running a PowerRename to shift all files to start from bill-02-23.pdf (as an example, to make space for the actual bill-01-23.pdf file) using the following configuration:

* Search for: `bill-(.*?)-23`
* Use regular expressions: true
* Match all occurrences: false
* Case sensitive: false
* Replace with: `bill-${start=2,padding=2}-23`
* Apply to: Filename only
* No text formatting

### ✔️ Expected Behavior

Having a folder with all the files renamed as:
* bill-02-23.pdf
* bill-03-23.pdf
* bill-04-23.pdf
* ... 
* bill-12-23.pdf

### ❌ Actual Behavior

The result will be instead:
* bill-02-23 (2).pdf
* bill-03-23 (2).pdf
* ... 
* bill-12-23 (2).pdf

Which is the expected Windows Explorer behavior, but I would assume a tool that does that externally would probably want to avoid that 😛 

### Other Software

This is on Explorer on Windows 11, if it helps
Repository: node
Issue: flaky: test-inspector-scriptparsed-context 
Labels: s390,flaky-test

### Test

test-inspector-scriptparsed-context 

### Platform

Linux s390x

### Console output

```console
Error Message
fail (1)
Stacktrace
---
duration_ms: 15564.382
exitcode: 1
severity: fail
...
```


### Build links

- https://ci.nodejs.org/job/node-test-commit-linuxone/nodes=rhel8-s390x/41718/testReport/junit/(root)/parallel/test_inspector_scriptparsed_context/

### Additional information

_No response_
Repository: pytorch
Issue: keep-going UX is not good
Labels: triaged,module: devx

Anecdotally, I've applied keep-going and it doesn't seem to work. I think this may be because it's really unclear what window of time we actually need to apply keep-going for in order for the CI to pick it up:
- I apply keep-going after the CI test job shows up. Sure, I expect this wouldn't work, but it would be nice if the test job's keep-going check happened when the first test failed (instead of at the beginning of the job)
- I apply keep-going after the CI test job shows up, but resubmits of the PR end up ignoring keep-going. This is what feels like is happening, but I'm not completely sure.

Overall, needing to wait for a round-trip (or more!) for CI to tell me if keep-going is working is a bad UX. We should try to improve this.

Some suggestions:
- If the PR's body has "[keep-going]" in it, then we keep going! This way there is no confusion: I can apply this before actually submitting the PR.

cc @ZainRizvi @kit1980 @huydhn @clee2000 @pytorch/pytorch-dev-infra
Repository: flutter
Issue: Expose focus control for PlatformViews / connect flutter focus to the platform view level
Labels: c: new feature,framework,a: platform-views,c: proposal,f: focus,P2,team-ios,triaged-ios

### Use case

I have a webview for which I would like to programmatically give focus (in a way that focuses within the webview such that a window focus event is fired). I would like my webview to be focused on initial load and to be able to give it focus programmatically in certain cases, like when another overlaying widget closes, and it seems the only way to do this currently is via user gestures (i.e. a user clicking on the webview).

It seems like [platform views have been updated to participate in the flutter focus tree](https://github.com/flutter/flutter/issues/34187) (though there is [a bug with this for android](https://github.com/flutter/flutter/issues/130652)), however, I'm not aware of any way to set focus or otherwise interact with the view's focus node. There is a [`clearFocus()`](https://api.flutter.dev/flutter/services/PlatformViewController/clearFocus.html) method on the `PlatformViewController`, which will clear focus and trigger a window blur event, but no way to do the opposite. A text widget, as an example of a simple focusable widget, has an [`autofocus`](https://api.flutter.dev/flutter/material/TextField/autofocus.html) property and [exposes its focus node](https://api.flutter.dev/flutter/material/TextField/focusNode.html) such that you can request focus for it whenever.

If I were to wrap my webview widget in a focus node and control focus at that level, it would not propagate down to the webview and trigger a window focus event, as there is no connection there. 

I have an alternative solution that works but doesn't seem to address the core issue within flutter -- I use [flutter_inappwebview](https://inappwebview.dev/) which has a [`clearFocus()`](https://pub.dev/documentation/flutter_inappwebview/latest/flutter_inappwebview/InAppWebViewController/clearFocus.html) method for clearing focus from the webview, and I can implement a `requestFocus()` method in a fork of that package which does the opposite (using [`requestFocus()`](https://developer.android.com/reference/android/view/View#requestFocus()) for android webview implementation and [`becomeFirstResponder()`](https://developer.apple.com/documentation/uikit/uiresponder/1621113-becomefirstresponder) for ios webview implementation).

### Proposal

Exposing focus functionality on platform views would allow for controlling their focus, like what we can do with other focusable widgets. This also needs to acquire focus on the platform side (i.e. triggering a window focus event within the webview, like how [`clearFocus()`](https://api.flutter.dev/flutter/services/PlatformViewController/clearFocus.html) triggers a window blur event), which should be managed alongside flutter focus logic.
Repository: godot
Issue: Don't work translations with keys on russian or chinese on android
Labels: bug,platform:android,topic:porting

### Tested versions

Godot v4.2.1.stable

### System information

NixOS 24.05 (Uakari) - X11 - Vulkan (Mobile) - dedicated NVIDIA GeForce GTX 1050 Ti (nvidia; 545.29.06) - Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz (8 Threads)

### Issue description

When you use russian language in translation keys, translation stop working on android export (on linux and in editor all fine)
(Issue only appear with scv translations)

### Steps to reproduce

Create some translation with key in russian, export to android (or export MRP to android).

### Minimal reproduction project (MRP)

translation csv
![image](https://github.com/godotengine/godot/assets/36816595/cc49429c-4f47-4679-ac36-d6d1e1c6c529)
MRP scene
![image](https://github.com/godotengine/godot/assets/36816595/b12ca5ce-2a0a-4513-852c-3ffeddd66afa)
MRP run on editor
![image](https://github.com/godotengine/godot/assets/36816595/dc6162df-a424-4865-a7b5-5070ef6200f6)
MRP run on android
![image](https://github.com/godotengine/godot/assets/36816595/120c96cb-0355-48b3-8408-826603f76e7b)


[L10nIssue.zip](https://github.com/godotengine/godot/files/13846613/L10nIssue.zip)
Repository: rust
Issue: Tracking Issue for tcp_deferaccept
Labels: T-libs-api,C-tracking-issue

Feature gate: `#![feature(tcp_deferaccept)]`

This is a tracking issue for the tcp_deferaccept feature.

It allows for the current socket to delay the acceptance of a connection until data is available to be read

### Public API

It expands the existing Linux's `TcpStreamExt` trait with

```rust
pub trait TcpStreamExt: Sealed{
  fn deferaccept(&self) -> io::Result<u32>;
  fn set_deferaccept(&self, accept: u32) -> io::Result<()>;
}
```

This feature directly translates to the underlying native Linux `TCP_DEFER_ACCEPT` tcp(7) option.
Repository: godot
Issue: Gdscript - should generate an error when adding (append) an element of a different type that does not match a typed array - No type validation errors will be generated, and the array will not have the element added
Labels: enhancement,discussion,topic:gdscript,confirmed

### Tested versions

Godot 4.2.1 without .net 

### System information

Macbook Apple M2 Pro - MacOs  Sonoma 14.2.1

### Issue description

Create a typed array and add an element of different type to it.
No type validation errors will be generated, and the array will not have the element added

### Steps to reproduce

**Resume**: call this simple Gdscript function **attached** and see what happens when trying append an value that doesn't match with array type

**Steps**:
1- call attached script function **test_typed_array_data01()** inside Godot 4.2.1 without .net on any node, inside func _ready(), just call it.
2- See lines where _.append()_ is called passing an _arg of type String_ and _not one that combine/match with type of array_
3- See stacktrace errors and when it happens
4- Comment lines like print 02 in the editor, save
5- reexecute steps 1,2,3


**Expected result:**
* Both of these should result in a parse error for attempting to append an element that breaks the array type.
And if not a parse error for sure a runtime error, but it should occur in .append() line and not in line like this:
_print(str(array1[0]))_ or _print(str(array2[0]))_

When i call an line like _print(str(array1[0]))_ this array has zero size **where i expect that had an value...**

**Evidences**:
1)
![image](https://github.com/godotengine/godot/assets/5435476/df3212ff-5077-46f5-aab3-308d53a20c34)


2)
![image](https://github.com/godotengine/godot/assets/5435476/997c07d0-0b62-4dda-854a-868edeb20a56)



### Minimal reproduction project (MRP)

Just call this GDscript function:

func test_typed_array_data01():
	
	var array1: Array[PackedVector2Array]
	var array2: Array[PackedInt32Array]
	
	print("Yes, array1 is appending an String!")
	array1.append("sad string")
	
	print(array1)
	
	print("Theres nothing to print")
	print(str(array1[0]))
	
	print("Yes, array2 is appending an String!")
	
	array2.append("evil string")
	
	print(array2)
	print("Theres nothing to print")
	print(str(array2[0]))
Repository: next.js
Issue: Streaming blocks navigation on both server and client side
Labels: bug,Navigation

### Link to the code that reproduces this issue

https://github.com/blenky36/suspense-broken-demo

### To Reproduce

1. Start the application with `npm run dev` or use [deployed version](https://suspense-broken-demo.vercel.app/) 
2. Click the buttons to see described behaviour

### Current vs. Expected behavior

1. `<Suspense />` boundaries are not being respected during server side navigation using `redirect` from `next/navigation`. Despite the async components being wrapped in `<Suspense />`, the page waits for all promises to resolve before navigating to the new page. 

It should navigate immediately and then display the fallback UI configured in `<Suspense />`

2. Parallel route `loading.tsx` files are not registered correctly when there are multiple parallel routes: 
- If there is no `loading.tsx` in the directory containing child parallel routes, then navigation is blocked until the first parallel route resolves.
- If there is a `loading.tsx` in the directory containing child parallel routes, then navigation is not blocked but the parent `loading.tsx` only covers the first parallel route.
- In both of the above case, the second parallel route behaves as expected displaying its own `loading.tsx` until resolving.

A parent `loading.tsx` should apply to all child parallel routes, and each parallel route should have its `loading.tsx` registered correctly.


### 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.10.0
  npm: 10.2.3
  Yarn: 1.22.21
  pnpm: N/A
Relevant Packages:
  next: 14.0.5-canary.40
  eslint-config-next: 14.0.4
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


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

App Router, Routing (next/router, next/navigation, next/link)

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

next dev (local), Vercel (Deployed)

### Additional context

Behaviour is consistent across both local development and deployed to Vercel.
Repository: next.js
Issue: Error encountered when using getStaticProps with notFound return
Labels: bug,Pages Router

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/next-demo-j5xg3c?file=%2Fpackage.json%3A9%2C20

### To Reproduce

1. Open sandbox and visit route /events or /tools

2. it will show error popup

<img width="1651" alt="image" src="https://github.com/vercel/next.js/assets/128681361/3a05dfaf-7bca-4017-a198-521f4b851e8c">

### Current vs. Expected behavior

## According to the docs - 
### https://nextjs.org/docs/pages/api-reference/functions/get-static-props#notfound

### Issue Description:
In the context of the getStaticProps function, the utilization of the notFound boolean return value to display a 404 page for a successfully generated page results in an error, contrary to the expected behavior outlined in the documentation.

### Current Behavior:
When attempting to employ the notFound property to showcase a 404 page for a specific route as demonstrated in the documentation, an error is encountered instead of rendering the expected 404 page.

### Expected Outcome:
The expected behavior is  to correctly render the 404 page when using the notFound property.

### Additional Observations:
Upon having a dedicated 404 page available in pages dir, it displays that page without encountering any issues.

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Sun Aug  6 20:05:33 UTC 2023
Binaries:
  Node: 20.9.0
  npm: 9.8.1
  Yarn: 1.22.19
  pnpm: 8.10.2
Relevant Packages:
  next: 14.0.4
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.1.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Data fetching (gS(S)P, getInitialProps)

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context


The problem was tested across various releases, with the issue first appearing in 13.4.13-canary.0. Reverting to version 13.4.12 resolves the problem.
Repository: PowerToys
Issue: [Run] COMException (0xD0000701)
Labels: Issue-Bug,Product-PowerToys Run,Severity-High,Needs-Triage

### Microsoft PowerToys version

0.76.2.0

### Installation method

PowerToys auto-update

### Running as admin

None

### Area(s) with issue?

PowerToys Run

### Steps to reproduce

Unknown, sorry. Returned from Sleep, and found the 'PowerToys Run ran into an issue' screen on my desktop, requesting that I post this bug

### ✔️ Expected Behavior

No error? 😄 

### ❌ Actual Behavior

Dialog box 'Something went wrong' on my desktop after a resume from sleep

```
Version: 0.76.2.0
OS Version: Microsoft Windows NT 10.0.22621.0
IntPtr Length: 8
x64: True
Date: 05/01/2024 23:16:39
Exception:
System.Runtime.InteropServices.COMException (0xD0000701): 0xD0000701
   at Standard.NativeMethods.DwmExtendFrameIntoClientArea(IntPtr hwnd, MARGINS& pMarInset)
   at System.Windows.Shell.WindowChromeWorker._ExtendGlassFrame()
   at System.Windows.Shell.WindowChromeWorker._UpdateFrameState(Boolean force)
   at System.Windows.Shell.WindowChromeWorker._HandleDwmCompositionChanged(WM uMsg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at System.Windows.Shell.WindowChromeWorker._WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at System.Windows.Interop.HwndSource.PublicHooksFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
```

### Other Software

_No response_