sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: Environment Variables: Request ability to copy profiles
Labels: Idea-Enhancement,Needs-Triage,Product-Environment Variables

### Description of the new feature / enhancement

This utility is terrific! Big thank you for coming up with it!
I use an application (Bentley Systems MicroStation) where many application behaviours can be set at system or user level.
It would be very helpful to be able to copy a profile to create a variation of that profile rather than having to create from scratch each time.


### Scenario when this would be used?

I work in a support/consultancy role for Bentley Systems, similar to that of administrators in our customer base.
Being able to quickly and easily change variables is very helpful in this context. 

### Supporting information

_No response_
Repository: PowerToys
Issue: Environment Variables: Request ability to load multiple profiles
Labels: Idea-Enhancement,Needs-Triage,Product-Environment Variables

### Description of the new feature / enhancement

I use an application (Bentley Systems MicroStation) where many application behaviours can be set at system or user level.
In several cases it would be very helpful if multiple profiles could be loaded at once as I am currently creating a number of similar profiles with varying content to set various combinations of settings.
For instance there are variables that I would typically set active most of the time, and others where particular features may be on or off alongside the typical selection.
It's a great utility, this would significantly enhance it in my context and that of our superuser customers.

### Scenario when this would be used?

I work in a support/consultancy role for Bentley Systems, similar to that of administrators in our customer base.
Being able to quickly and easily change variables is very helpful in this context.

### Supporting information

_No response_
Repository: vscode
Issue: Git - Files are not added to nearest .gitignore
Labels: bug,git

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.86.1
- OS Version: macOS Sonoma

Steps to Reproduce:

1. Create a git repo in directory d
2. Create a .gitignore file in d
3. Create a subdirectory d/s
4. Create a .gitignore file in d/s
5. Create a dummy.txt file in d/s
6. Open d or d/s in Code
7. From the source control view add dummy.txt to .gitignore

It's added to d/.gitignore and not to d/s/.gitignore.

I think this is not an intuitive behaviour (specially when the project is d/s so d/s/.gitignore is at the top of the project) and should be changed or made configurable.
Repository: flutter
Issue: Take screenshot of iOS 17 device in CI
Labels: platform-ios,tool,P2,team-ios,triaged-ios

Currently, iOS 17 screenshot functionality does not work. However, a potential solution that we could use for CI is to use XCUIApplication to take a screenshot of the device. It's not a great solution, but could potentially be used as a workaround if we really needed.
Repository: go
Issue: cmd/go: duplicate lines in coverage file after update to 1.22
Labels: NeedsInvestigation,GoCommand

### Go version

go version go1.22.0 windows/amd64

### Output of `go env` in your module/workspace:

```shell
GO111MODULE=on
GOARCH=amd64
GOBIN=
GOCACHE=C:\Users\astoffels\AppData\Local\go-build
GOENV=C:\Users\astoffels\AppData\Roaming\go\env
GOEXE=.exe
GOEXPERIMENT=
GOFLAGS=
GOHOSTARCH=amd64
GOHOSTOS=windows
GOINSECURE=
GOMODCACHE=C:\Source\golang\pkg\mod
GONOPROXY=
GONOSUMDB=
GOOS=windows
GOPATH=C:\Source\golang
GOPRIVATE=
GOPROXY=https://proxy.golang.org,direct
GOROOT=C:/Program Files/Go
GOSUMDB=sum.golang.org
GOTMPDIR=
GOTOOLCHAIN=auto
GOTOOLDIR=C:\Program Files\Go\pkg\tool\windows_amd64
GOVCS=
GOVERSION=go1.22.0
GCCGO=gccgo
GOAMD64=v1
AR=ar
CC=gcc
CXX=g++
CGO_ENABLED=0
GOMOD=C:\Source\golang\src\coverageRepro\go.mod
GOWORK=
CGO_CFLAGS=-O2 -g
CGO_CPPFLAGS=
CGO_CXXFLAGS=-O2 -g
CGO_FFLAGS=-O2 -g
CGO_LDFLAGS=-O2 -g
PKG_CONFIG=pkg-config
GOGCCFLAGS=-m64 -fno-caret-diagnostics -Qunused-arguments -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=C:\Users\ASTOFF~1\AppData\Local\Temp\go-build2371241097=/tmp/go-build -gno-record-gcc-switches
```


### What did you do?

Clone https://github.com/alainstoffels/coverageRepro
Run inside the root of the repo: `go test -cover -coverpkg=./... -coverprofile=coverage.out ./...`

### What did you see happen?

coverage.out now contains 2 lines for `coverageRepro/bar/bar.go`. One where it indicates that it's not covered, and another where it indicates that it is covered:
```
mode: set
coverageRepro/bar/bar.go:3.12,5.2 1 0
coverageRepro/bar/bar.go:3.12,5.2 1 1
coverageRepro/foo/foo.go:5.12,7.2 1 1
```

`foo.Foo()` calls `bar.Bar()`, so `foo.TestFoo()` should cover `bar.Bar()`.

### What did you expect to see?

I would expect it to output a single line for `coverageRepro/bar/bar.go`, indicating it as covered, like it did before the 1.22 update:
```
mode: set
coverageRepro/bar/bar.go:3.12,5.2 1 1
coverageRepro/foo/foo.go:5.12,7.2 1 1
```
Repository: stable-diffusion-webui
Issue: [Feature Request]: X/Y/Z plotting prompt S/R use file input
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 ?

I try to do an X/Y/Z plotting with S/R and want to use prompts stored in a text file.

After training a LoRA I want to check different LoRA strengths (X direction) and number of trained epochs (Y direction) to figure out which is best. So I want to use the Z direction for the image prompts which are a list of many tags each (comma separated as it is usual for beeing a prompt :) ) - but I can't do that as the S/R syntax is interfering with the prompt syntax. And the many tags woudn't make it readable anyway 

### Proposed workflow

1. Add an additional "prompt S/R" to the existing one, the new one would be "prompt S/R from text file" 
2. Have a text file where each line is like one of the current S/R tokens that are separated by a comma

=> So the first line of the text file is searched in the prompt and for each iteration the following line is used as replacement

So the new stuff to implement is very simple: duplicate the "prompt S/R" with a new name, have a file selector and then do the split for the S/R list not by a comma but by the new line character.


### Additional information

_No response_
Repository: next.js
Issue: Client side navigation with PPR enabled causes a flash of unstyled content (FOUC)
Labels: bug,Navigation

### Link to the code that reproduces this issue

https://github.com/florian-lp/next-client-ppr-bug

### To Reproduce

1. Build the app ("npm build")
2. Run in production ("npm start")
3. Visit the /other page "http://localhost:3000/other" (Do this by opening a new browser tab, as subsequent navigations in the same tab will make use of the browser cache)
4. Navigate to the home page by clicking the link, you will observe a FOUC.
5. Navigating back to the /other page will **not** show a FOUC.

Example:

https://github.com/vercel/next.js/assets/82889954/d00866b4-f1a3-4f65-b3e8-43e6359b2c4b

### Current vs. Expected behavior

Observed:
On first client-side navigation to a partially pre-rendered page, the css for that page is not loaded. This causes a flash of unstyled content.

Expected:
Navigating to the partially pre-rendered page should not cause a flash of unstyled content, matching the behaviour of server-side navigation, or subsequent client-side navigations.behavior

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Home
Binaries:
  Node: 20.9.0
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.1.1-canary.45
  eslint-config-next: 14.1.1-canary.45
  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, Routing (next/router, next/navigation, next/link)

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

next start (local)

### Additional context

This behavior has been present since release 14.0.5-canary.20, which introduced client-side navigation for PPR.

This behavior is only present with experimental.ppr enabled and only in production builds since pages are always server-rendered in development mode.
Repository: vscode
Issue: saving the .code-workspace resets the currently selected launch config from that file
Labels: bug,debug

Type: <b>Bug</b>

I use launch configs both in the launch.json file and the .code-workspace file. If a launch configuration from the .code-workspace file is selected (Run and Debug menu), if I edit something in the workspace file then save it, the Run and Debug target resets to one from the launch.json targets.

VS Code version: Code 1.83.1 (Universal) (f1b07bd25dfad64b0167beb15359ae573aecd2cc, 2023-10-10T23:46:55.789Z)
OS version: Darwin arm64 22.6.0

<details>
<summary>A/B Experiments</summary>

```
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscorecescf:30445987
vscod805:30301674
binariesv615:30325510
vsaa593:30376534
py29gd2263:30899288
vscaac:30438847
c4g48928:30535728
azure-dev_surveyone:30548225
0bi6i642:30933247
pythongtdpath:30769146
welcomedialog:30910333
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
pythontbext0:30879054
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
dsvsc019acf:30933242
7j2b6412:30949929

```

</details>

<!-- generated by issue reporter -->
Repository: electron
Issue: [Feature Request]: Expose physical size of displays
Labels: enhancement :sparkles:

### 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 feature request that matches the one I want to file, without success.

### Problem Description

I need the physical size of each connected display, e.g., 14 inches, in the main process.

### Proposed Solution

If possible, add the information to the existing `display` object as optional entry: https://www.electronjs.org/docs/latest/api/structures/display

### Alternatives Considered

The physical size of a display can be queried on [macOS](https://stackoverflow.com/questions/12589198/how-to-read-the-physical-screen-size-of-osx) via `CGDisplayScreenSize` and via `GetDeviceCaps(hdc, HORZSIZE)` and `GetDeviceCaps(hdc, VERTSIZE)` on [Windows](https://learn.microsoft.com/en-en/windows/win32/api/wingdi/nf-wingdi-getdevicecaps). One could create a native module to do so, however merging the information from the native module with the existing display information from Electron is cumbersome.

### Additional Information

_No response_
Repository: neovim
Issue: Netrw (file explorer) does not work on network location on Windows
Labels: bug,platform:windows,netrw

### Problem

I have tried to work with neovim on a network location, and use Netwr to browse around in the current working directory (CWD), however, when I use it it show utter emptyness.

This bug seems to correlate with breaking down of the LazyVim config. Basically, when I launch Neovim with LazyVim, and use the find file or find text option to open a file, even though in the menus, proper things are displayed, when I open the files with them neovim opens a completely empty file. If I write something into said file, and write it, then Neovim replicates the the folder structure of the server in which the chosen file lies into the CWD. and puts next to the chosen file.
So for example I have a file bar.py at location Microsoft.PowerShell.Core\FileSystem::\\\\server\\...\\foo\\bar.py and I choose Microsoft.PowerShell.Core\FileSystem::\\\\server\\...\\foo\\ as CWD for my LazyVim session. Then choosing to edit bar.py will result in the opening of a completely empty file. Then if I save it, it will just put in the CWD the following folder structure server\...\foo\bar.py next to bar.py .
In addition the nvim-tree plugin also fails to work the same way as the Netwr do.

I highly suspect that the breakdown of the LazyVim config emerges from this bug of the Netwr. In addition, I suspect that this bug emerges from its broken support of UNC paths.

### Steps to reproduce

nvim --clean .

### Expected behavior

Instead of the standard functionality of Netwr works in the current working directory, we get nothing it is used on a network location.

### Neovim version (nvim -v)

0.9.5

### Vim (not Nvim) behaves the same?

9.0

### Operating system/version

Windows 10 Pro, Version 22H2 (OS Build 19045.3930)

### Terminal name/version

wezterm 20230712-072601-f4abf8fd

### $TERM environment variable

not defined

### Installation

Scoop
Repository: flutter
Issue: Create windows arm64 release archive 
Labels: P2,team-release,triaged-release

Windows arm64 artifacts are already being produced and we need to start creating a win arm64 bundle. The following are the required steps: 

- [ ] https://github.com/flutter/flutter/issues/143230
- [ ] Update prepare_package script create the windows arm64 archive and add it to the metadata file.
- [ ] Create a package_builder build to test the configurations running on a windows arm64 machine.
- [ ] Update website to include the new archive

There are no blocker for main/master branch but there are two blockers for release candidate branches:

* Dart to start producing win arm64 artifacts for branches different than main.
* Availability of win arm64 machines in dart-internal.

@CaseyHillers can you please help triage and reassign?
Repository: ollama
Issue: LLaVA 1.6 Models Unable to Process Specific Image Size and Resolution Locally
Labels: bug

### Environment
- **Version**: Ollama v0.1.23
- **LLaVA Models Tested**: 13b-1.6 and 34b-1.6
- **Local Machine Specs**:
  - GPU: RTX3080ti 12GB
  - CPU: AMD 5800x
  - Memory: 32GB running on 3600mhz

### Issue Description
I have encountered an issue where the local versions of the LLaVA 1.6 models (13b and 34b) are unable to process a 1070x150 png image. The error message returned is:

`The image you've provided is too small and blurry for me to read the text and provide an accurate answer. Could you please try to provide a larger, clearer image or type out the question so I can assist you?`

However, when testing the same image on the public hosted LLaVA 1.6 instance (https://llava.hliu.cc/), the image is processed without any issues.

### Steps to Reproduce
1. Run either `ollama run llava:13b` or `ollama run llava:34b` locally with the mentioned system specifications.
2. Provide the model with the 1070x150 png image.
3. Observe the error message indicating the image is too small and blurry.

### Expected Behavior
The local models should process the image similar to the public hosted version, without returning an error about the image size and clarity.

### Additional Context
This issue seems to be specific to the local setup with the mentioned specifications. It's unclear if this is a limitation of the local environment or a discrepancy between the local and hosted versions of the model.

### Potential Causes
- Different handling of image inputs between local and hosted versions.
- Local resource limitations, although the specifications should be more than sufficient.
- Possible bug in the local implementation of image preprocessing.

### Attachments
- Error message screenshot (if applicable)
----
<img width="759" alt="image" src="https://github.com/ollama/ollama/assets/1207520/bf461f23-4a05-4fc8-9c39-36c23a098cd0">

- The 1070x150 png image (for testing and reproducibility)
----
![A-1](https://github.com/ollama/ollama/assets/1207520/41a5f112-580c-4e58-beb6-e2d807bd95e0)
Repository: flutter
Issue: Add windows arm64 bots to dart-internal
Labels: team-infra,P3,triaged-infra

### Type of Request

feature request

### Infrastructure Environment

LUCI

### What is happening?

This supports publishing release artifacts for windows arm64. These artifacts are already being produced at HEAD, so we should re-use the existing machine specs for dart-internal.

Parent issue at https://github.com/flutter/flutter/issues/143221

### Steps to reproduce

Step 1:
Step 2:
..
Step n:


### Expected results

I expect to see X when Y is finished.
Repository: godot
Issue: Opening Explorer with Win-E flashes Godot
Labels: bug,platform:windows,topic:porting,needs testing

### Tested versions

4.2.1

### System information

Window 11 RTX 2070 

### Issue description

Godot flashes in the background everytime I open Windows Explorer using Win+E 

This was an issue with Blender too, but they have fixed it. Here is the actual Blender bug report (that I opened) with more details from the Blender developers which might help, given they provided details about how to go about fixing it.

Bear in mind that **this seems to be Windows 11 issue**. You probably won't be able to replicate in previous versions/

https://projects.blender.org/blender/blender/issues/116618

### Steps to reproduce

Pres Win+E to open an explorer window while Godot in the foreground or in the background.

### Minimal reproduction project (MRP)

No project is required, it can be replicated with an empty scene as well.
Repository: opencv
Issue: Opencv.js --threads how to compleatly release memory when refreshing page?
Labels: bug,category: javascript (js)

### System Information

Opencv.js ver 4.5.5

build parameters:
`python ./opencv/platforms/js/build_js.py build_wasm --build_wasm --threads`

### Detailed description

An error occurs when refreshing a page due to insufficient RAM and only on devices with 3 Gb RAM (Android and iOS, for ex., iPhone 10, Honor 10 Lite, RedMi 7 Note). Doesnt occurs on devices with large amounts of RAM.
The error only occurs with the multi-threaded version of opencv (build with --threads flag) and does not occurs with the single-threaded version.

I tried release memory like this, but it didn't help
```
window.onbeforeunload = function()
{
	if (cv.PThread !== undefined)
	{
		cv.PThread.terminateAllThreads();
		cv.__emscripten_thread_free_data();
	}
}
```
It seems that the memory is not release or it does not happen immediately.

How can I release memory and unload opencv completely when the page is refreshed?

P.S.
I had exactly the same error with Tensorflow.js. It was successfully resolved after memory was released on the `window.onbeforeunload` event

### Steps to reproduce

1. Build opencv.js with --threads flag
2. Load it in script and make maximum use of RAM on your device
3. Refresh page

[OpenCV.zip](https://github.com/opencv/opencv/files/14224708/OpenCV.zip)


### 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
- [ ] 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: flutter
Issue: ☂️ Support Privacy Manifest and Required APIs in iOS and macOS
Labels: P1,a: plugins,team-ios,triaged-ios

Umbrella issue to track the work to support privacy manifests (xcprivacy) across the engine, packages, 3p packages, tooling, etc.

From https://github.com/flutter/flutter/issues/131494:
Introduced in Xcode 15, Apple is now flagging specific APIs as needed a “Required Reason” to use. All usages of “Required Reason” APIs MUST be outlined in a Privacy manifest. A Privacy manifest is a document outlining how your app/SDK collects and uses a user’s data.

This is also time sensitive (https://developer.apple.com/news/?id=z6fu1dcu). 
> Starting in fall 2023, when you upload a new app or app update to App Store Connect that uses an API (including from third-party SDKs) that requires a reason, you’ll receive a notice if you haven’t provided an approved reason in your app’s privacy manifest. And starting in spring 2024, in order to upload your new app or app update to App Store Connect, you’ll be required to include an approved reason in the app’s privacy manifest which accurately reflects how your app uses the API.
 
https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api
https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_data_use_in_privacy_manifests
https://developer.apple.com/videos/play/wwdc2023/10060/

- [x] Engine Flutter.xcframework https://github.com/flutter/flutter/issues/131494
- [x] Flutter-maintained packages https://github.com/flutter/flutter/issues/131495 and https://github.com/flutter/packages/pull/5846
- [x] https://github.com/flutter/flutter/issues/140934
- [x] Tooling and templates for new/existing Flutter plugins https://github.com/flutter/flutter/issues/140013
- [ ] Policy and documentation https://github.com/flutter/flutter/issues/131940
- [x] https://github.com/flutter/website/issues/10864
- [ ] https://github.com/flutter/flutter/issues/140966
- [ ] https://github.com/flutter/flutter/issues/147186
- [ ] https://github.com/flutter/flutter/issues/147140
- [x] https://github.com/flutter/flutter/issues/143381
Repository: go
Issue: proposal: cmd/gofmt: A change of spacing within for...range <int> loops
Labels: Proposal

### Proposal Details

I know this is dangerously close to bike-shedding but I thought it worth the suggestion, even if it ends up being closed.

Here's a quite tortured example that's derived from something slightly less tortured.

```go
package main

func main() {
	xs := []int{0, 1, 2}
	n := 1
	ys := make([]int, 0, len(xs)-(n-1))
	for range len(xs)-(n-1) {
		ys = append(ys, len(xs)-(n-1))
	}
}
```

When passed through gofmt, this becomes

```go
package main

func main() {
	xs := []int{0, 1, 2}
	n := 1
	ys := make([]int, 0, len(xs)-(n-1))
	for range len(xs) - (n - 1) {
		ys = append(ys, len(xs)-(n-1))
	}
}
```

which, to my eye, seems worse. The terms after the range keyword form a tight conceptual cluster, but the text is spread.

I didn't see any discussion on https://github.com/golang/go/issues/61405 about associated gofmt rules, so this may be an unintended outcome.

I propose that the spacing be as with function calls. I'm happy to have a stab at an implementation.