sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: rust-lldb pretty-printing not working for Rc<str>
Labels: A-debuginfo,C-bug,WG-debugging


I tried this code:

```rust
pub struct Testing {
    pub name: std::rc::Rc<str>,
    pub other_name: String,
}

fn main() {
    let my_name = "Bill";
    let foo = Testing { name: my_name.into(), other_name: my_name.into() };
    let disp = format!("{}", foo.name);
}
```

I expected to see this happen: Pretty printing of the Testing::name `Rc<str>` value in rust-lldb.

Instead, this happened: Just the first char of the `Rc<str>` was printed.

```text
(lldb) b src/main.rs:81
Breakpoint 1: 2 locations.
(lldb) run
Process 30797 launched: '/Users/billti/src/rsenum/target/debug/rsenum' (arm64)
Process 30797 stopped
* thread #1, name = 'main', queue = 'com.apple.main-thread', stop reason = breakpoint 1.1
    frame #0: 0x00000001000033d0 rsenum`rsenum::main::h7d2f7ff2357a65c7 at main.rs:81:16
   78  	fn main() {
   79  	    let my_name = "Bill";
   80  	    let foo = Testing { name: my_name.into(), other_name: my_name.into() };
-> 81  	    let disp = format!("{}", foo.name);
   82  	    
   83  	    
   84  	    
Target 0: (rsenum) stopped.
(lldb) var
(&str) my_name = "Bill" {
  data_ptr = 0x000000010003932c "Bill"
  length = 4
}
(rsenum::Testing) foo = {
  name = strong=1, weak=0 {
    value = 'B'
  }
  other_name = "Bill" {
    vec = size=4 {
      [0] = 'B'
      [1] = 'i'
      [2] = 'l'
      [3] = 'l'
    }
  }
}
(lldb) version
lldb-1403.0.17.67
Apple Swift version 5.8.1 (swiftlang-5.8.0.124.5 clang-1403.0.22.11.100)
```

I tested with stable and nightly with the same results (rustc 1.73.0-nightly (04abc370b 2023-07-28))
Repository: next.js
Issue: Next headers cookies has is not defined after the set cookies in app router
Labels: bug,Navigation

### 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 22.5.0: Thu Jun  8 22:22:20 PDT 2023; root:xnu-8796.121.3~7/RELEASE_ARM64_T6000
    Binaries:
      Node: 18.16.1
      npm: 9.5.1
      Yarn: N/A
      pnpm: N/A
    Relevant Packages:
      next: 13.4.13-canary.6
      eslint-config-next: 13.4.12
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.6
    Next.js Config:
      output: standalone
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

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

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/VitaliyR/nextjs-13-cookies-has-issue/blob/main/app/page.tsx

### To Reproduce

Open the provided link and see it in action.

Reproduction scenario:
App Routes, Server Components.

Cookies here - `import { cookies } from 'next/navigation'`

1. In your server component use `cookies().has` method - on original request works fine
2. Alter your cookie value (e.g. call `cookies().set` or `cookies().delete`)
3. Crashes with error that `not a function` because `has` is undefined in the result of `cookies()` call

### Describe the Bug

It seems that in server components after cookies has been altered - result of `cookies()` object is different compared to the result from the original call.

So basically, you have a component which console logs `typeof cookies().has` and a button which alters cookies in server action (set or delete).

On original call (no action, just landing on the page) the console output will be predictable - `function`. So, `cookies().has` is defined.

After user clicks on the button which runs server action and alters the cookies - crash happens, and console output is `undefined` - meaning that there are no `has` property in `cookies()` result object.

`cookies().get` is present in both cases - original land and cookies update.

### Expected Behavior

`cookies().has` should be always defined as a function and works as expected

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: PowerToys
Issue: Always pinned to the top border bug
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.70.0

### Installation method

GitHub, Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

Always on Top

### Steps to reproduce

# 在使用始终置顶置顶WSL的应用时边框有点问题

### ✔️ Expected Behavior

# 边框靠近在应用边框上

### ❌ Actual Behavior

# 边框离应用很远

### Other Software

_No response_
Repository: flutter
Issue: The Flutter test runner should expose the current test's file path
Labels: a: tests,framework,c: proposal,P2,team-framework,triaged-framework

The golden test system accesses the file system to read and write golden files, as well as visual output from failed diffs.

To read and write these files, the golden test system needs an awareness of where the current test lives, so that the golden files can be saved in a directory that's relative to the current test.

The ability to find, read, and write files within the test directory structure is not unique to Flutter's golden test subsystem. This is a general capability that tests might want for any reason. Tests might want to load JSON configuration files, relative to the test. Tests might want to write measurements to files, relative to the test. Any use-case to read or write to a file, relative to the test, needs to know where the test lives.

There's a StackOverflow post about this: https://stackoverflow.com/questions/74704732/get-path-to-current-executing-unit-test-in-flutter

If that StackOverflow post is still correct, the only way for a test to find its own directory is to access a property of a magic global object called `goldenFileComparator`. This expectation is a problem for multiple reasons:

- If I'm doing something that has nothing to do with goldens, this is confusing at best, and is very difficult to find because I have no basis up on which to search for some kind of "golden" tool.
- As a typical developer, we don't know who sets it, and therefore we don't know who might change it, or why. We blindly assume the runtime type, which could easily change in the future. It's inappropriate to establish a generic dependency on an object that could stop providing that information at any time.

There should be a way, both in Flutter widget tests, and plain Dart tests, to query, or otherwise locate the file system path to the currently executing test.

I'll also add, though it's not critical to the point of this ticket, that an API for general traversal across the test directory might be useful. The reason for finding the current test file is so that the test can then move into, or create, other nearby directories. The fundamental problem space is that of directory navigation through the test directory, beginning from the location of the current test. It might be nice if Flutter and Dart generally made that traversal quick and easy.
Repository: go
Issue: proposal: testing: verbose output should print package path before printing test output
Labels: Proposal

This makes it clear which package is being tested as the test output is printed.

For example, at the end of

```
=== RUN   TestFoo
--- PASS: TestFoo (0.00s)
PASS
ok  	example.com/foo	0.138s
=== RUN   TestBar
```

which package are we in? We don't know from the output. For large projects, where there are too many packages to memorize, especially their lexicographic order, this is valuable when you spot output you immediately want to investigate, but it takes a long time for the full package testing to finish, at which point the actual package path is printed out.

So, it would instead be something like

```
=== RUN   example.com/foo
=== RUN   TestFoo
--- PASS: TestFoo (0.00s)
--- PASS: example.com/foo	0.138s
=== RUN   example.com/bar
=== RUN   TestBar
```
Repository: create-react-app
Issue: deprecated notice on tar package
Labels: needs triage,issue: bug report

### Describe the bug
Performed:
```
npx create-react-app Tsunami18v2
```

Received:
```
npm WARN deprecated tar@2.2.2: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap.
```

### Did you try recovering your dependencies?
Yea with sudo. npm package is not an issue.
```
    npm install -g npm@latest
    npm install
```
### Which terms did you search for in User Guide?

<!--
  There are a few common documented problems, such as watcher not detecting changes, or build failing.
  They are described in the Troubleshooting section of the User Guide:

  https://facebook.github.io/create-react-app/docs/troubleshooting

  Please scan these few sections for common problems.
  Additionally, you can search the User Guide itself for something you're having issues with:

  https://facebook.github.io/create-react-app/

  If you didn't find the solution, please share which words you searched for.
  This helps us improve documentation for future readers who might encounter the same problem.
-->

(Write your answer here if relevant.)

### Environment

<!--
  To help identify if a problem is specific to a platform, browser, or module version, information about your environment is required.
  This enables the maintainers quickly reproduce the issue and give feedback.

  Run the following command in your React app's folder in terminal.
  Note: The result is copied to your clipboard directly.

  `npx create-react-app --info`

  Paste the output of the command in the section below.
-->

(paste the output of the command here.)

### Steps to reproduce

<!--
  How would you describe your issue to someone who doesn’t know you or your project?
  Try to write a sequence of steps that anybody can repeat to see the issue.
-->

(Write your steps here:)

1. Open terminal
2. npx create-react-app <name>
3. cd <name>; npm start

### Expected behavior

No warnings.

### Actual behavior

A wild warning appeared.

### Reproducible demo

Same as steps above.
Repository: next.js
Issue: App dir opengraph-image.tsx throws an error when used with custom pageExtensions
Labels: bug

### 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.0.0: Fri Jun 30 17:48:23 PDT 2023; root:xnu-10002.0.168.505.3~1/RELEASE_ARM64_T8103
    Binaries:
      Node: 20.4.0
      npm: 9.7.2
      Yarn: 1.22.19
      pnpm: N/A
    Relevant Packages:
      next: 13.4.13-canary.6
      eslint-config-next: 13.4.12
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.6
    Next.js Config:
      output: N/A
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

App Router

### Link to the code that reproduces this issue or a replay of the bug

https://codesandbox.io/p/sandbox/interesting-buck-tpf24f

### To Reproduce

1. Setup custom `pageExtensions` in `next.config.js`
2. Create sample `layout.[custom-ext].tsx` and `page.[custom-ext].tsx`
3. Create a `opengraph-image.[custom-ext].tsx` (and copy the example code provided in the next.js docs [https://nextjs.org/docs/app/api-reference/file-conventions/metadata/opengraph-image](https://nextjs.org/docs/app/api-reference/file-conventions/metadata/opengraph-image))
4. Run `next dev`

### Describe the Bug

The code fails to compile and throws an error

```bash
next-app-loader?name=app%2Fpage&page=%2Fpage&appPaths=%2Fpage&pagePath=private-next-app-dir%2Fpage.customExt.tsx&appDir=%2Fworkspace%2Fapp&pageExtensions=customExt.tsx&pageExtensions=customExt.ts&rootDir=%2Fworkspace&isDev=true&tsconfigPath=tsconfig.json&basePath=&assetPrefix=&nextConfigOutput=&preferredRegion=&middlewareConfig=e30%3D!:12
Error: Image import "next-metadata-image-loader?type=openGraph&segment=&basePath=&pageExtensions=customExt.tsx&pageExtensions=customExt.ts!/workspace/app/opengraph-image.customExt.tsx?__next_metadata__" is not a valid image file. The image may be corrupted or an unsupported format.
```

### Expected Behavior

The code should compile without errors

### Which browser are you using? (if relevant)

Safari, Chrome, Edge

### How are you deploying your application? (if relevant)

_No response_
Repository: vscode
Issue: [Bug] Unable to replace non-English regex match
Labels: editor-find,under-discussion

<!-- ⚠️⚠️ 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. -->

**VSCode Version**: 1.80.2
**Commit**: 2ccd690cbff1569e4a83d7c43d45101f817401dc
**Date**: 2023-07-27T20:41:52.615Z
**Electron**: 22.3.14
**ElectronBuildId**: 22695494
**Chromium**: 108.0.5359.215
**Node.js**: 16.17.1
**V8**: 10.8.168.25-electron.0
**OS**: Linux x64 6.4.6-arch1-1

Steps to Reproduce:

1. Put this in a JSON file:

  ```json
  {
    "song": [
      [
        "സ്തോത്രം പാടി വാഴ്ത്തിടുന്നു ഞാൻ",
        "പുത്രനെ തന്ന ദേവാ",
        "പാത്രനല്ലേനെങ്കിലും സു-",
        "പാത്രമാക്കി തീർത്തതാൽ"
      ],
      [
        "മന്നവനേശുതാനുന്നത ബലിയായ്",
        "തീർന്നതിനെ നിനപ്പാൻ - മന്നിൽ",
        "തന്നൊരു നിയമം ഇന്നിഹ നാമനു-",
        "വർത്തിക്കുന്നാദരവായ്"
      ],
      [
        "ഒടുവിലൊരിക്കൽ നിന്നരി-",
        "കിലണയും ഞാൻ",
        "അവിടെയും പാടും",
        "നിന്നതിശയ സ്നേഹത്തെ"
      ],
      [
        "കർത്താവാം കുഞ്ഞാട്ടിൻ കല്യാണനാളതിൽ",
        "കാന്തയായ് തൻമുമ്പിലെ-",
        "ന്നെയും നിർത്തുവാൻ",
        "ഘോരമാം പാടുകൾ ക്രൂരരാം യൂദരാൽ",
        "കാരണമില്ലാതെ സഹിച്ച സ്നേഹമേ"
      ]
    ]
  }
  ```

2. Use `editor-find` to search for `([^e\W])-"` and replace with `$1 -"`.

---

> Note: `([^e\p{L}])-"` does not match the same thing even though `$1` works with it.

---

**Screenshot**

![image](https://github.com/microsoft/vscode/assets/38415384/1bb0e9d5-8126-4fd9-a7bb-1cac99a88402)
Repository: pytorch
Issue: Runtime Error: Empty tensor
Labels: needs reproduction,triaged,module: mps

### 🐛 Describe the bug

M1 Max 64 GB RAM running Stable Diffusion in Automatic1111 with SDXL 1.0 model:

RuntimeError: [srcBuf length] > 0 INTERNAL ASSERT FAILED at "/Users/runner/work/pytorch/pytorch/pytorch/aten/src/ATen/native/mps/OperationUtils.mm":277, please report a bug to PyTorch. Placeholder tensor is empty!

### Versions

Collecting environment information...
PyTorch version: N/A
Is debug build: N/A
CUDA used to build PyTorch: N/A
ROCM used to build PyTorch: N/A

OS: macOS 14.0 (arm64)
GCC version: Could not collect
Clang version: 15.0.0 (clang-1500.0.34.3)
CMake version: version 3.27.1
Libc version: N/A

Python version: 3.9.6 (default, Jul  7 2023, 20:26:47)  [Clang 15.0.0 (clang-1500.0.34.3)] (64-bit runtime)
Python platform: macOS-14.0-arm64-arm-64bit
Is CUDA available: N/A
CUDA runtime version: Could not collect
CUDA_MODULE_LOADING set to: N/A
GPU models and configuration: Could not collect
Nvidia driver version: Could not collect
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: N/A

CPU:
Apple M1 Max

Versions of relevant libraries:
[pip3] No relevant packages
[conda] Could not collect


cc @kulinseth @albanD @malfet @DenisVieriu97 @razarmehr @abhudev
Repository: next.js
Issue: Blur placeholder of `next/image` is still visible after the image is loaded
Labels: Image (next/image),linear: next

### 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 22.5.0: Thu Jun  8 22:22:20 PDT 2023; root:xnu-8796.121.3~7/RELEASE_ARM64_T6000
    Binaries:
      Node: 18.6.0
      npm: 8.13.2
      Yarn: 1.22.18
      pnpm: 8.6.7
    Relevant Packages:
      next: 13.4.13-canary.6
      eslint-config-next: 13.4.9
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.6
    Next.js Config:
      output: N/A
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

Image optimization (next/image, next/legacy/image)

### Link to the code that reproduces this issue or a replay of the bug

https://codesandbox.io/p/sandbox/pensive-mccarthy-yfz9lg

### To Reproduce

- Use `next/image` to load an image that has a transparent background.
- Set a `placeholder="blur"` on such image.
- Check your app: the image blur won't be removed immediately after the image has been loaded. This makes the blurry image visible underneath the loaded image (since it has a transparent background). 

### Describe the Bug

The image/style generated by setting `placeholder="blur"` on a `next/image` can still be seen (for some time) after the image has been loaded.  

Example from the attached Codesandbox:
<img width="908" alt="ScreenShot 2023-07-29 at 11 12 30@2x" src="https://github.com/vercel/next.js/assets/9536354/92a7ff0f-60f8-4727-a954-0f9f1055743b">

You can see other people reporting and discussing this bug at https://github.com/vercel/next.js/issues/42140#issuecomment-1342533513 .

For reference, here's how a Gatsby image with blur setup looks like out-of-the box:


https://github.com/vercel/next.js/assets/9536354/3484be15-066e-4ad0-9eef-4fd7c0c238a0




### Expected Behavior

The placeholder image/style should immediately disappear when the image is loaded. Or, the generated image placeholder should respect the transparency pixels of the used image. 

### Which browser are you using? (if relevant)

`Chromium Engine Version 115.0.5790.114`, `Safari Version 16.5.2 (18615.2.9.11.10)`

### How are you deploying your application? (if relevant)

_No response_

<sub>[NEXT-1679](https://linear.app/vercel/issue/NEXT-1679/blur-placeholder-of-nextimage-is-still-visible-after-the-image-is)</sub>
Repository: godot
Issue: nested resources are not saved in the editor
Labels: bug,topic:editor

### Godot version

3.5 stable

### System information

fedora 38 silverblue

### Issue description

I use this code to make reasonable editor experience for setting up enemy waves. The problem is after adding some waves and enemySpawns, the enemyspawns dont get saved in the resource. It appears they do in the editor, but after loading the game theyre not there, or after reloading the project. 

```
extends Resource
tool

export(bool) var force_save := false setget force_save
func force_save(value):
	ResourceSaver.save(resource_path,self)
	force_save = false
	
export(Array, Resource) var set := [] setget set_set
var wave_idx := 0

func set_set(value):
	for s in value.size():
		if not value[s] is EnemyWave:
			value[s] = EnemyWave.new()
	set = value

func get_next() -> Array:
	# udrzuj index a vrat dalsi vlnu nepratel
	# return set[wave_idx++].spawn() if wave_idx < set.size() else null
	return set[wave_idx].spawn() if wave_idx < set.size() else null
	wave_idx = (wave_idx+1) % set.size()
	# return set[wave_idx++].spawn() if wave_idx < set.size() else null

class EnemyWave:
	extends Resource
	
	export(Array, Resource) var wave := [] setget set_wave

	func set_wave(value):

		if not Engine.editor_hint: return
		for s in value.size():
			if not value[s] is EnemySpawn:
				value[s] = EnemySpawn.new()
		wave = value

	func spawn() -> Array:
		var spawned := []
		print("AFUK",wave)
		for espawn in wave:
			print("BFUK")
			spawned.append_array(espawn.spawn())
		return spawned
	#  instancuj a vrat pole spawnutych nepratel

	class EnemySpawn:
		extends Resource
		enum EType { CUBE , SPHERE , BIG_A, BIG_B }
		# export var enemy : PackedScene
		export(EType) var enemy : int = 0
		export var count : int = 1
		var enemyfabs := [
			preload("res://A.tscn"),
			preload("res://B.tscn"),
		]

		func spawn() -> Array:
			var spawned := []
			print("DFUK")
			for i in count:
				var made = enemyfabs[enemy].instance()
				spawned.append(made)

			return spawned

```



### Steps to reproduce

open enemyset.tres resource in inspector and add few enemyspawns by resizing the enemywave array to larger by zero, you can even edit some values etc.

ctrl + s
 
reload project

the defined enemyspawns are gone

ill probably figure a workaround or force it to save somehow in the setter but feels like this should work

### Minimal reproduction project

[spawntest.zip](https://github.com/godotengine/godot/files/12206794/spawntest.zip)
Repository: godot
Issue: Unwanted warping when the cursor leaves the window boundaries after `warp_mouse()` was called with `MOUSE_MODE_HIDDEN` on Linux Wayland
Labels: bug,platform:linuxbsd,topic:gui

### Godot version

v4.1.1.stable.official [bd6af8e0e]

### System information

Fedora Linux 38 (Workstation Edition), GNOME 44.3 Wayland

### Issue description

If `warp_mouse()` is called when the mouse mode is set to `MOUSE_MODE_HIDDEN` on Linux Wayland, it causes unwanted warping to the previous warp position after the cursor leaves the window boundaries.

This does not occur on Xorg.

I have attached a reproduction project with all the steps to reproduce the bug.

[Screencast from 2023-07-29 14-12-16.webm](https://github.com/godotengine/godot/assets/36744029/3868835e-5ba3-4f55-a30a-9616c204c7c7)


### Steps to reproduce

1) Run the reproduction project on Linux Wayland with **Godot 4.1.1.stable**

2) Click and hold anywhere
	•  Mouse mode will be set to `Input.MOUSE_MODE_CAPTURED`
	•  `clicking_position` variable will be set.

3) Release the mouse button
	•  Mouse mode will be set to `Input.MOUSE_MODE_HIDDEN`
	•  `warp_mouse(clicking_position)` will be called

4) Try moving the cursor outside of the window boundaries
	•  Notice how once the cursor moves outside the boundaries it warps to `clicking_position` one more time.

### Minimal reproduction project

[Warp Mouse Bug.zip](https://github.com/godotengine/godot/files/12206832/Warp.Mouse.Bug.zip)