sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: [iOS] Permission dialog when pasting text from universal clipboard may be closed before user has had time to allow pasting
Labels: a: text input,platform-ios,a: fidelity,has reproducible steps,P2,found in release: 3.7,found in release: 3.8,team-ios,triaged-ios

## Steps to Reproduce

1. flutter create handoff_clipboard
2. prepare a macbook and any iOS deivce
3. make sure Apple's 'Handoff' feature is enabled on the devices above.
4. add a `TextField()` at somewhere of the `lib/main.dart`
5. run flutter on the ios device
6. `cmd+c` some text on the screen of macOS
7. tap TextField widget on the screen of iOS
8. tap "Paste"
9. There flash an alert and then disappear, leave a Error in console (Xcode/vscode): ```[Pasteboard] ...requesting item failed with error: Error Domain=PBErrorDomain Code=13 "Operation not authorized." UserInfo={NSLocalizedDescription=Operation not authorized.}```
10. tap paste again, the alert will stay on the screen, looks good.

some codes in starter project, if useful

```dart
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text(widget.title),
      ),
      body: Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          // 🚧 add this line
          crossAxisAlignment: CrossAxisAlignment.stretch,
          children: <Widget>[
            const Text(
              'You have pushed the button this many times:',
            ),
            Text(
              '$_counter',
              style: Theme.of(context).textTheme.headlineMedium,
            ),
            // 🚧 add this line
            TextField(),
          ],
        ),
      ),
      floatingActionButton: FloatingActionButton(
        onPressed: _incrementCounter,
        tooltip: 'Increment',
        child: const Icon(Icons.add),
      ),
    );
  }
```

flutter doctor

```
➜  ~ flutter doctor          
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.7.5, on macOS 13.2.1 22D68 darwin-arm64, locale en-CN)
[!] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/macos#android-setup for more details.
[✓] Xcode - develop for iOS and macOS (Xcode 14.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.1)
[✓] VS Code (version 1.75.1)
[✓] Proxy Configuration
[✓] Connected device (3 available)
[✓] HTTP Host Availability
```
Repository: godot
Issue: Data gets overriden on editor reload - closing and reopening
Labels: bug,discussion,topic:editor

### Godot version

4.0 beta rc5,rc4,rc3 ...

### System information

Windows 10 Forward+

### Issue description

When I close editor and open it again resources get overridden.
One material get changed to 1 other material that is constantly selected.
so it is like 1 material is constantly changed to 1 other material (I created 1 material and then another 3 and first got set into fourth created on meshes not affecting the second and third where it was setted)
(Using XR tools) when setting Viewport2Din3D scene it also gets overridden

example.
I set this
![obraz](https://user-images.githubusercontent.com/51274570/221349060-003ef6ff-de4e-4d6e-bb99-5e37d14835bf.png)
to scene called storage_ui_content.tscn
but it gets back to being settings scene after editor reopening


Also I searched is this bug described in other issue but I could not find it.

### Steps to reproduce

Create multiple materials (I not sure how many 10, 15 mayby more)
Create double the amount of meshes - could be cubes
Set materials created before to cubes
Reopen editor
You should see some meshes having changed/not saved material you selected

### Minimal reproduction project

N/A
Repository: godot
Issue: CylinderShape3D is buggy, works worse than CapsuleShape3D
Labels: bug,topic:physics,topic:3d

### Godot version

Both v4.0.rc2.official [d2699dc7a] and v4.0.rc5.official [6296b4600], IIRC early 4.0 versions are affected too

### System information

Linux Mint 20.3, Intel Core i7

### Issue description

When using CylinderShape3D as a shape for a car tires, the car behaves strange - it looks like it "stumbles" on a smooth terrain. If you replace this shape with a CapsuleShape3D the problem dissapears.

There's similar #57048, but I think its a) too broad and b) does not describe this specific behavior (horizontal cylinders on a smooth terrain).

### Steps to reproduce

Basically you need a smooth but not flat terrain and a something car-alike with cylinder collision shapes as a tires. See two minimal reproduction projects below.

For the projects: WSAD to move, mose to look.

### Minimal reproduction project

Here's two projects: the only difference between them is wheel shape (capsule vs cylinder)

---

Buggy cylindrical shape: [gd_cyl_bug-cylindrical.zip](https://github.com/godotengine/godot/files/10830760/gd_cyl_bug-cylindrical.zip).

[cylinder.webm](https://user-images.githubusercontent.com/17745136/221350753-a0885949-72c2-4b68-9f8d-606d55e0a7da.webm)

---

Fine capsule shape: [gd_cyl_bug-capsule.zip](https://github.com/godotengine/godot/files/10830759/gd_cyl_bug-capsule.zip).

[capsule.webm](https://user-images.githubusercontent.com/17745136/221350714-c31a5d4b-898d-4a82-bb88-e3a1714fcb52.webm)
Repository: stable-diffusion-webui
Issue: [Feature Request]: Saving Images with parent txt file for tagging
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 ?

It would be nice to have every saved image be parent with a txt file that contains all tags.
The image names could be shortened and the txt file would allow the perfect import for imageboard/organizer like hydrusnetwork.

Example Files:
image001.png
image001.txt
image002.png
image002.txt

Example content of txt:
Tag1
Tag2
Tag3

The tags results from the prompt that created the image.

### Proposed workflow

Same as current version. Just with an additional checkmarker like "create tag txt file".
Currently mostly the Prompts go into the filename that is restricted by os in lengh. Moving this to a parent file would enhance the organisation om said images. Specialy the longer promps.


### Additional information

_No response_
Repository: terminal
Issue: F16 Is not usable in Terminal
Labels: Help Wanted,Area-Input,Issue-Bug,Area-TerminalControl,Product-Terminal,Priority-3

### Windows Terminal version

1.16.10261.0

### Windows build number

10.0.19044.2604

### Other Software

Happens running cmd or pwsh 7.3.2 within the tab.

### Steps to reproduce

Have a keyboard with additional function keys.
Run an app that reports key presses.
In terminal F13, F14, & F15 work. But F16 does not: no input is seen. Also cannot map to a WT action.

The test application works with F16 (including with modifiers) under conhost.exe. Also seen (and mappable) in Visual Studio 2022 (didn't check earlier versions).

### Expected Behavior

See keyboard input when F16 is pressed. Can map to actions, and when pressed that action is triggered.

### Actual Behavior

F16 does nothing in Windows Terminal and applications running within Windows Terminal.
Repository: PowerToys
Issue: 能不能提供快捷键查询这类的功能？
Labels: Needs-Triage

### Description of the new feature / enhancement

本软件与window11的默认输入的切换冲突，导致powertoys的alt+space起不来

### Scenario when this would be used?

alt+space

### Supporting information

_No response_
Repository: next.js
Issue: Inline Script example raises error
Labels: examples

### Verify canary release

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

### Provide environment information

    Operating System:
      Platform: darwin
      Arch: x64
      Version: Darwin Kernel Version 21.1.0: Wed Oct 13 17:33:23 PDT 2021; root:xnu-8019.41.5~1/RELEASE_X86_64
    Binaries:
      Node: 16.13.0
      npm: 8.1.0
      Yarn: 1.22.17
      pnpm: N/A
    Relevant packages:
      next: 13.2.1
      eslint-config-next: 13.2.1
      react: 18.2.0
      react-dom: 18.2.0


### Which example does this report relate to?

https://beta.nextjs.org/docs/optimizing/scripts#inline-scripts

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

_No response_

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

_No response_

### Describe the Bug

https://beta.nextjs.org/docs/optimizing/scripts#inline-scripts

On a fresh install of NextJS, the inline script example raises an exception.

Here is the inline script added to the root layout:

```
import Script from 'next/script';
import './globals.css'

export const metadata = {
  title: 'Create Next App',
  description: 'Generated by create next app',
}

export default function RootLayout({
  children,
}: {
  children: React.ReactNode
}) {
  return (
    <html lang="en">
      <Script id="analytics">
        {`document.getElementById('banner').classList.remove('hidden')`}
      </Script>
      <body>{children}</body>
    </html>
  )
}

```

The error raised is:

```
Unhandled Runtime Error
Error: Unsupported Server Component type: {...}
```

### Expected Behavior

Runs script

### To Reproduce

Create new app, paste example code into layout.tsx
Repository: TypeScript
Issue: 【bug】ThisType is invalid when using param on generic object
Labels: Bug,Help Wanted

# Bug Report

<!--
  Please fill in each section completely. Thank you!
-->

### 🔎 Search Terms
ThisType Object Generic
<!--
  What search terms did you use when trying to find an existing bug report?
  List them here so people in the future can find this one more easily.
-->

### 🕗 Version & Regression Information

<!-- When did you start seeing this bug occur?

"Bugs" that have existed in TS for a long time are very likely to be FAQs; refer to
  https://github.com/Microsoft/TypeScript/wiki/FAQ#common-bugs-that-arent-bugs

If possible, please try testing the nightly version of TS to see if it's already been fixed.
For npm: `typescript@next`
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly

Note: The TypeScript Playground can be used to try older versions of TypeScript.

Please keep and fill in the line that best applies:
-->
I was unable to test this on prior versions because I was not using this feature previously

### ⏯ Playground Link

<!--
  A link to a TypeScript Playground "Share" link which shows this behavior

  The TypeScript Workbench can be used for more complex setups, try
  https://www.typescriptlang.org/dev/bug-workbench/

  As a last resort, you can link to a repo, but these will be slower for us to investigate.
-->
[Playground link with relevant code](https://www.typescriptlang.org/play?#code/C4TwDgpgBAkgMgSwGYWAgttAvFA3gKCigHsA7AZQAsBDAJwgBUMIAbBUiALigAoBKKFgB8UAM7Ba7AOb4AvvnxIArqQDGaMlFX1qwCAHkARgCsI6gDwARIT2InulqADJYiFGkzOoDSglENwCCshAQIiVTJRYhYIADoAdzpSWxM+OQUAegyoeOJaAGtpfG0IXQMTM2AeMKg0YBjuAHIAEwh0YkaAGkISChp6Jkw2Dn48HqJ6YCVaUihGxp75WTT8LKhSYmAcvMLSGRKyo1N1ap66hrnW9q6esio6RmZhiFGaidRp2eBfUVjziEWcj4QA)

### 💻 Code

<!-- Please post the relevant code sample here as well-->
```ts
type ILifetime = {
  onShareTimeline: () => string
}

function createObject<D>(obj: D & ILifetime & ThisType<D>) {
  console.warn(obj)
}

// working
createObject({
  title: 'demo',
  onShareTimeline() {
    return ''
  }
})

// not working
createObject({
  title: 'demo',
  onShareTimeline() {
    return this.title
  }
})
```

### 🙁 Actual behavior

<!-- What happened, and why it was wrong -->
The generic type is broken
### 🙂 Expected behavior

<!-- What you expected to happen instead, and why -->
The generic type should contain the object properties as those are finally included into the result
Repository: rust
Issue: `Add` confusion when casting an integer to a float with trait functions
Labels: A-trait-system,T-compiler,C-bug

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

The following code seems to trick the compiler into thinking that `f64` does not implement `Add<Self>`:

```rust
use std::fmt::Debug;
use std::ops::Add;

/// A scalar number.
pub trait Scalar
where
    Self: Debug
        + Sized
        + Add<Self, Output = Self> // If this bound is moved last, the error goes away
        + for<'a> Add<&'a Self, Output = <Self as Add<Self>>::Output>, 
{
}

/// A floating point number constructed from a scalar number
pub trait FloatFrom<Src>: Float
where
    Src: Scalar,
{
    /// Converts the value into a floating point number.
    fn from_scalar(value: Src) -> Self;
}

/// A floating point number.
pub trait Float: Scalar {}

impl Scalar for i32 {}
impl Scalar for f64 {}
impl Float for f64 {}
impl FloatFrom<i32> for f64 {
    fn from_scalar(value: i32) -> Self {
        value as f64
    }
}

fn add_one_f64<S>(x: S)
where
    f64: FloatFrom<S>,
    S: Scalar,
{
    let float = f64::from_scalar(x);
    let one = 1.0_f64;
    assert_eq!(float + &one, 2.0);
    assert_eq!(float + one, 2.0); // <-- error[E0308]: mismatched types, expected `&f64`, found floating-point number
}

fn main() {
    let a = 1;
    add_one_f64(a)
}
```

I expected the code would compile without errors. Instead, the compiler complained about mismatched types. 

The error goes away if the `Scalar` trait is rewritten as:
```rust
pub trait Scalar
where
    Self: Debug
        + Sized
        // + Add<Self, Output = Self>
        // + for<'a> Add<&'a Self, Output = <Self as Add<Self>>::Output>,
        + for<'a> Add<&'a Self, Output = <Self as Add<Self>>::Output>
        + Add<Self, Output = Self>,
{
}
```

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.67.1 (d5a82bbd2 2023-02-07)
binary: rustc
commit-hash: d5a82bbd26e1ad8b7401f6a718a9c57c96905483
commit-date: 2023-02-07
host: x86_64-unknown-linux-gnu
release: 1.67.1
LLVM version: 15.0.6
```

<!--
Include a backtrace in the code block by setting `RUST_BACKTRACE=1` in your
environment. E.g. `RUST_BACKTRACE=1 cargo build`.
-->
<details><summary>Backtrace</summary>
<p>

```
 Compiling scrap v0.1.0 (/home/me/scrap)
error[E0308]: mismatched types
  --> src/main.rs:41:24
   |
41 |     assert_eq!(float + one, 2.0); // <-- error[E0308]: mismatched types, expected `&f64`, found floating-point number
   |                        ^^^
   |                        |
   |                        expected `&f64`, found `f64`
   |                        help: consider borrowing here: `&one`

For more information about this error, try `rustc --explain E0308`.
error: could not compile `scrap` due to previous error
```

</p>
</details>
Repository: rust
Issue: Unable to notice trait bound in trait type when implementing trait on generic
Labels: A-trait-system,T-compiler,C-bug,T-types

Ran this code on playground:

```rust
trait Tr {
    type X: Copy;
}

enum EnA<V: Tr> {
    A(V::X),
    B(V)
}

struct Str {
    x: &'static str
}

impl Tr for Str {
    type X = &'static str;
}

impl<V: Tr> From<V::X> for EnA<V> {
    fn from(value: V::X)->EnA<V> {
        EnA::A(value)
    }
}
```

Expected to see no error since `EnA` does not derive `Copy` but `Tr::X` requires deriving `Copy`.

Instead, this happened:
```
   Compiling playground v0.0.1 (/playground)
error[E0119]: conflicting implementations of trait `From<EnA<_>>` for type `EnA<_>`
  --> src/lib.rs:18:1
   |
18 | impl<V: Tr> From<V::X> for EnA<V>{
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: conflicting implementation in crate `core`:
           - impl<T> From<T> for T;

For more information about this error, try `rustc --explain E0119`.
error: could not compile `playground` due to previous error
```

Looks like the compiler fails to realize that `EnA` can never be used as `Tr::X` and claims it conflicts with the blanket derivation. In fact, if I do:
```rs
trait IntoEnA<V: Tr> {}

impl<V: Tr> IntoEnA<V> for V::X {}

impl<V: Tr> IntoEnA<V> for EnA<V>{}
```
Similar issue arise:
```
   Compiling playground v0.0.1 (/playground)
error[E0119]: conflicting implementations of trait `IntoEnA<_>` for type `EnA<_>`
  --> src/lib.rs:22:1
   |
20 | impl<V: Tr> IntoEnA<V> for V::X {}
   | ------------------------------- first implementation here
21 |
22 | impl<V: Tr> IntoEnA<V> for EnA<V>{}
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ conflicting implementation for `EnA<_>`

For more information about this error, try `rustc --explain E0119`.
error: could not compile `playground` due to previous error
```
Repository: godot
Issue: Tileset terrain's center bit doesn't update when the terrains change position inside a terrain set
Labels: bug,topic:2d

### Godot version

v4.0.rc5.official [6296b4600]

### System information

Manjaro Linux

### Issue description

When moving the terrains inside a terrain set the center of each tile won't update and will keep the old value.

https://user-images.githubusercontent.com/483531/221360038-5f314c93-817e-4fcb-8d0c-d72f00929e31.mp4



### Steps to reproduce

See attached video.

### Minimal reproduction project

N/A
Repository: deno
Issue: Error loading package.json: Not a directory
Labels: bug,node compat

```ts
import "npm:@sdkgen/node-runtime";
```

This fails on Deno 1.31.1 with:

```
error: Uncaught Error: Error loading package.json at /mnt/node_modules/.deno/@sdkgen+node-runtime@2.2.0/node_modules/decimal.js/decimal.js/package.json. Not a directory (os error 20)
    at resolveExports (internal:deno_node_loading/02_require.js:318:14)
    at Function.Module._findPath (internal:deno_node_loading/02_require.js:357:31)
    at Function.Module._resolveFilename (internal:deno_node_loading/02_require.js:618:27)
    at Function.Module._load (internal:deno_node_loading/02_require.js:467:27)
    at Module.require (internal:deno_node_loading/02_require.js:678:19)
    at require (internal:deno_node_loading/02_require.js:818:16)
    at Object.<anonymous> (file:///mnt/node_modules/.deno/@sdkgen+node-runtime@2.2.0/node_modules/@sdkgen/node-runtime/dist/src/encode-decode.js:40:22)
    at Object.<anonymous> (file:///mnt/node_modules/.deno/@sdkgen+node-runtime@2.2.0/node_modules/@sdkgen/node-runtime/dist/src/encode-decode.js:374:4)
    at Module._compile (internal:deno_node_loading/02_require.js:745:34)
    at Object.Module._extensions..js (internal:deno_node_loading/02_require.js:778:10)
```

The same import works on Deno 1.30.3, so this is a regression.

Importing `decimal.js` directly works, but not indirectly. Both modules are commonjs.
Repository: rust
Issue: Alleged type visibility leakage
Labels: A-visibility,C-bug

Working on a type with a builder, I found it surprising that a documentation link to the builder type was broken.

I set up the following repo as a test case: https://github.com/fengalin/test_builder_visibility.

In `my_lib`, `rustdoc` reports:

```text
warning: public documentation for `builder` links to private item `MyTypeBuilder`
 --> my_lib/src/my_type.rs:7:26
  |
7 |     /// Instantiates a [`MyTypeBuilder`].
  |                          ^^^^^^^^^^^^^ this item is private
  |
  = note: this link will resolve properly if you pass `--document-private-items`
  = note: `#[warn(rustdoc::private_intra_doc_links)]` on by default
```

`MyTypeBuilder` is declared as a `pub struct`, however it is not re-exported as `pub` by `my_lib`.

`rustc` disagrees with `rustdoc` and allows the external [`main`](https://github.com/fengalin/test_builder_visibility/blob/main/src/main.rs) to use a function declared on a `MyTypeBuilder` instance, obtained by calling `MyType::builder()`.

@GuillaumeGomez requested that I report the issue here.

### Meta

Issue observed using:

`rustc --version --verbose`:
```
rustc 1.67.0 (fc594f156 2023-01-24)
binary: rustc
commit-hash: fc594f15669680fa70d255faec3ca3fb507c3405
commit-date: 2023-01-24
host: x86_64-unknown-linux-gnu
release: 1.67.0
LLVM version: 15.0.6
```

&

`cargo +nightly --version --verbose`:
```
cargo 1.69.0-nightly (9d5b32f50 2023-02-22)
release: 1.69.0-nightly
commit-hash: 9d5b32f503fc099c4064298465add14d4bce11e6
commit-date: 2023-02-22
host: x86_64-unknown-linux-gnu
libgit2: 1.5.0 (sys:0.16.0 vendored)
libcurl: 7.86.0-DEV (sys:0.4.59+curl-7.86.0 vendored ssl:OpenSSL/1.1.1q)
os: Fedora 37.0.0 [64-bit]
```
Repository: godot
Issue: Vulkan mobile: any visual change breaks cull/visual layers. Light visual/cull layers do not work at all.
Labels: bug,topic:rendering,topic:3d

### Godot version

4.0 RC4

### System information

Ubuntu 22.04

### Issue description

When setting visual cull layers, any change to the objects like  changing material or even moving it around seems to "reset" or disable cull layers in the frame it takes effect. This means that playing any animation makes cull layers not to work at all  because it disables layer culling every frame.
Also, seems like visual layers do not work for lights at all. Maybe is a consequence of the same issue.


https://user-images.githubusercontent.com/8985409/221366993-78fa508c-916f-430a-84e8-7d2d59fe2260.mp4




### Steps to reproduce

Add a decal and set its visual layer to 1. Add a decal and set its cull layer to 2. The decal is still visible. Move the decal or set its cull layer again. Now the decal is not visible (its cull layer works). Make a visual change to the scene like moving the mesh instance. Cull layers stop working.

### Minimal reproduction project

[mobile_decal_cull_layer_bug.zip](https://github.com/godotengine/godot/files/10831626/mobile_decal_cull_layer_bug.zip)