sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: react-native
Issue: TextInput keyboard getting dismissed automatically
Labels: Issue: Author Provided Repro,Component: TextInput,API: Keyboard,Type: New Architecture

### Description

When a TextInput is wrapped with a View, and the View is given conditional styles based on the focus state of the TextInput, the keyboard gets dismissed as soon as it is tapped to gain focus. So, as soon as onFocus is called, onBlur is triggered automatically. Note that this is not happening for all style keys, but I have encountered it only for "elevation" and "shadowColor" properties till now.

The issue is only happening when new architecture is enabled on both android and ios.

### Steps to reproduce

Here is a minimum reproducible example for the issue: [https://github.com/1880akshay/RN_NewArch_TextInput](https://github.com/1880akshay/RN_NewArch_TextInput)


### React Native Version

0.74.3

### Affected Platforms

Runtime - Android, Runtime - iOS

### Areas

Fabric - The New Renderer

### Output of `npx react-native info`

```text
System:
  OS: macOS 13.6.7
  CPU: (10) arm64 Apple M1 Max
  Memory: 204.98 MB / 64.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 18.19.0
    path: ~/.nvm/versions/node/v18.19.0/bin/node
  Yarn:
    version: 1.22.21
    path: ~/.nvm/versions/node/v18.19.0/bin/yarn
  npm:
    version: 10.2.3
    path: ~/.nvm/versions/node/v18.19.0/bin/npm
  Watchman:
    version: 2024.07.15.00
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.15.2
    path: /opt/homebrew/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.2
      - iOS 17.2
      - macOS 14.2
      - tvOS 17.2
      - visionOS 1.0
      - watchOS 10.2
  Android SDK: Not Found
IDEs:
  Android Studio: 2022.3 AI-223.8836.35.2231.10406996
  Xcode:
    version: 15.2/15C500b
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.10
    path: /usr/bin/javac
  Ruby:
    version: 3.3.0
    path: /opt/homebrew/opt/ruby/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.74.3
    wanted: 0.74.3
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: true
iOS:
  hermesEnabled: Not found
  newArchEnabled: true
```


### Stacktrace or Logs

```text
-
```


### Reproducer

https://github.com/1880akshay/RN_NewArch_TextInput

### Screenshots and Videos


https://github.com/user-attachments/assets/7a70be20-4d74-4da1-9b07-aae8472f0a60
Repository: storybook
Issue: [Bug]: Story with a prop that kaes an array that holds JSX freezes storybook.
Labels: bug,needs triage

### Describe the bug

The issue was documented already here:
https://github.com/storybookjs/storybook/issues/17720

if you add a component to your story with a prop that takes an array of objects, and pass in jsx it breaks the story especially in docs.



See here:

https://stackblitz.com/edit/github-buuamr?file=public%2Ftest.stories.ts,src%2Fstories%2FProblem.stories.tsx&preset=node


If you change the icon inside the stuff prop to regular text it works and shows up as a story. Otherwise it hangs.


### Reproduction link

https://stackblitz.com/edit/github-buuamr?file=public%2Ftest.stories.ts,src%2Fstories%2FProblem.stories.tsx&preset=node

### Reproduction steps

Visit the Test "Problem" Story.
See that ti does not work if the prop takes in JSX

### System

```bash
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.20.3 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm <----- active
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    @storybook/addon-essentials: ^8.3.0-alpha.2 => 8.3.0-alpha.2 
    @storybook/addon-interactions: ^8.3.0-alpha.2 => 8.3.0-alpha.2 
    @storybook/addon-links: ^8.3.0-alpha.2 => 8.3.0-alpha.2 
    @storybook/addon-onboarding: ^8.3.0-alpha.2 => 8.3.0-alpha.2 
    @storybook/blocks: ^8.3.0-alpha.2 => 8.3.0-alpha.2 
    @storybook/nextjs: ^8.3.0-alpha.2 => 8.3.0-alpha.2 
    @storybook/react: ^8.3.0-alpha.2 => 8.3.0-alpha.2 
    @storybook/test: ^8.3.0-alpha.2 => 8.3.0-alpha.2 
    storybook: ^8.3.0-alpha.2 => 8.3.0-alpha.2
```


### Additional context

_No response_
Repository: go
Issue: x/crypto/x509roots/fallback: tag versions to reduce version churn from x/crypto commits
Labels: NeedsInvestigation,FeatureRequest

### Go version

n/a

### Output of `go env` in your module/workspace:

```shell
n/a
```


### What did you do?

If we do `go get golang.org/x/crypto/x509roots/fallback@latest`, since that submodule is not itself versioned, it instead uses the commit hash as the version.

The problem is that whenever we run this command in order to update our go.mod file, it is picking the version derived from the latest commit of x/crypto itself, instead of the latest commit that actually changed x/crypto/x509roots/fallback.

This is confirmed by https://pkg.go.dev/golang.org/x/crypto/x509roots/fallback?tab=versions

At present, that lists the latest version as v0.0.0-20240726163919-3375612bf41a, even though that commit had nothing to do with x/crypto/x509roots/fallback. https://github.com/golang/crypto/commit/3375612bf41a8cdb0cdfdc21e6ca2c7ae0f764b5

### What did you see happen?

I expect the latest version of a submodule that is not tagged to be reported as the last commit that modified it (including deleting files).

Barring that, I expect x/crypto/x509roots/fallback to have tagged releases to avoid this problem.

### What did you expect to see?

It changes constantly even though there really isn't a change, which is confusing and interferes with our ability to properly maintain our dependencies.
Repository: godot
Issue: HTTPClient does not resolve internationalized domain names
Labels: bug,needs testing,topic:network

### Tested versions

v4.2.2.stable.mono.official [15073afe3]

### System information

Godot v4.2.2.stable.mono - Windows 10.0.19045 - GLES3 (Compatibility) - NVIDIA GeForce GTX 1060 3GB (NVIDIA; 32.0.15.5585) - AMD Ryzen 5 5600X 6-Core Processor (12 Threads)

### Issue description

I'm currently building a home-automation app and noticed the following:

the follow URL is not treated properly with HTTPClient:
`something.lüfter`

it should make a DNS request to:
`something.xn--lfter-kva`

but tries to request `something.lüfter`, which is not a legal dns area name

### Steps to reproduce

well.. you need an internal DNS Server with a .lüfter (xn--lfter-kva) domain, then make a simple get request, youll end up with a HTTPClient.STATUS_CANT_RESOLVE error instead

### Minimal reproduction project (MRP)

"N/A"
Repository: flutter
Issue: [go_router] `onPopPage` is deprecated
Labels: package,team-ecosystem,P2,c: tech-debt,p: go_router,triaged-ecosystem,p: deprecated api

This deprecation showed up in the routine sweep of flutter/packages; ideally it should be fixed as soon the necessary APIs to do so are on `stable`, to minimize future client disruption.

```
   info • lib/src/builder.dart:434:11 • 'onPopPage' is deprecated and shouldn't be used. Use onDidRemovePage instead. This feature was
          deprecated after v3.16.0-17.0.pre. Try replacing the use of the deprecated member with the replacement. •
          deprecated_member_use
   info • test/custom_transition_page_test.dart:55:15 • 'onPopPage' is deprecated and shouldn't be used. Use onDidRemovePage instead. This
          feature was deprecated after v3.16.0-17.0.pre. Try replacing the use of the deprecated member with the replacement. •
          deprecated_member_use
   info • test/custom_transition_page_test.dart:104:15 • 'onPopPage' is deprecated and shouldn't be used. Use onDidRemovePage instead. This
          feature was deprecated after v3.16.0-17.0.pre. Try replacing the use of the deprecated member with the replacement. •
          deprecated_member_use
   info • test/go_router_state_test.dart:209:17 • 'onPopPage' is deprecated and shouldn't be used. Use onDidRemovePage instead. This feature was
          deprecated after v3.16.0-17.0.pre. Try replacing the use of the deprecated member with the replacement. •
          deprecated_member_use
```

Reference: https://docs.flutter.dev/release/breaking-changes/navigator-and-page-api
It looks like this will be in the next stable release after 3.22?
Repository: react-native
Issue: Keyboard accessibility issues on Android (TextInput but also beyond)
Labels: Issue: Author Provided Repro,Component: TextInput,Platform: Android,API: Keyboard

### Description

Can not operate TextInput with external keyboards and it seems that TextInputs  "block" focus for other elements if those are between two TextInputs.

We can not really use TextInputs for applications that need to be accessible (app is failing WCAG and EN 301 549 accessibility standards).

This issue is also reopening https://github.com/facebook/react-native/issues/31820 (that was closed because it was stale)...

### Steps to reproduce

1. Connect a physical keyboard to Android device (I've used both PC with direct connection to Android and external Bluetooth keyboard that works with other apps).

2. Open Expo snack (https://snack.expo.dev/aAQHfOdiVoSZF6jo6TzWN) or basically run this code:


```
<Button
  onPress={() => onPressLearnMore("First")}
  title="First focus"
  color="#841584"
/>
      <TextInput
        style={styles.input}
        onChangeText={onChangeText}
        value={text}
      />

      <Button
  onPress={() => onPressLearnMore("between")}
  title="Focus in between"
  color="#2196F3"
/>
      <TextInput
        style={styles.input}
        onChangeText={onChangeNumber}
        value={number}
        placeholder="1234"
        keyboardType="numeric"
      />

            <Button
  onPress={() => onPressLearnMore("Last")}
  title="Last focus"
  color="#000"
/>
```
3. try to focus in either of TextInput's or try to focus and activate the button in between them....


### React Native Version

0.74.3

### Affected Platforms

Runtime - Android

### Output of `npx react-native info`

```text
N/A
```


### Stacktrace or Logs

```text
Nothing reported...
```


### Reproducer

https://snack.expo.dev/aAQHfOdiVoSZF6jo6TzWN

### Screenshots and Videos

https://www.youtube.com/watch?v=EZmllQhzzMU
Repository: kubernetes
Issue: Special-case whitespace-only values in webhook conversion client construction
Labels: sig/api-machinery,priority/important-longterm,triage/accepted

https://github.com/kubernetes/kubernetes/pull/124061#issuecomment-2142880235

Comment from liggitt:

> I think I'd suggest the following:

> 1. For CRDs that do not have an Established=True condition (on CRD creation or pre-serving updates)
a. In validation, allow arbitrary caBundle values like today
b. In staging/src/k8s.io/apiextensions-apiserver/pkg/controller/establish/establishing_controller.go, gate setting Established=True on the caBundle value being valid (if specified). This means until caBundle is populated with a valid value in a new CRD, the CRD will not be served and will not show up in discovery.

> 2. For CRDs that do have an Established=True condition (which means they are being served)
a. In validation, add ratcheting validation (this PR) so valid caBundle values have to stay valid
b. When constructing the webhook conversion client in webhookClientConfigForCRD, consider special-casing whitespace-only values to treat them as an empty value and fall back to system trust roots. This will still likely fail when attempting to contact the conversion webhook, but reads/writes that don't require conversion could still succeed, so if there were no persisted objects or only requests to the version matching the storage version and all existing persisted objects were in that version, clients like the namespace controller could be unblocked.

https://github.com/kubernetes/kubernetes/pull/124061 addresses 1a, 1b, 2a.

2b is still pending
Repository: pytorch
Issue: Result of MPS memory operation can be corrupted if memory pressure is high
Labels: high priority,module: memory usage,triaged,module: correctness (silent),module: mps

### 🐛 Describe the bug

Have not come up with the minimal reproducer yet, but if one tries to use torchchat to run int4-quantized model, weights can get corrupted during quantization while running the following code:
```python
  int_data = quantize_affine(w, block_size, scales, zeros, output_dtype, quant_min, quant_max, zero_point_domain = ZeroPointDomain.FLOAT)
  int_data = (int_data[::, ::2] << 4 | int_data[::, 1::2]).to(torch.uint8)
```

But the same code works fine if smaller model (say stories110M are quantized), which suggests that it happens when memory allocated to store temporary tensors are reused (but needs more invsestigation

### Versions

2.4/nightly

cc @ezyang @gchanan @zou3519 @kadeng @msaroufim @kulinseth @albanD @DenisVieriu97 @jhavukainen
Repository: godot
Issue: CharacterBody2D without velocity get sticky collision
Labels: bug,topic:physics,needs testing,topic:2d

### Tested versions

Reproducible:
v4.3.rc1.official [e343dbbcc]
v4.2.2.stable
v4.2.1.stable
v4.1.1.stable
v4.1.stable
v4.0.stable
v4.0.beta.10


### System information

Godot v4.3.rc1 - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 2070 SUPER (NVIDIA; 31.0.15.5186) - Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (8 Threads)

### Issue description

`CharcterBody2D` with velocity of (0, 0) sticks to other `CharacterBody2D` which collided with it.
`CollisionShape2D.shape` doesn't matter.
`motion_mode` doesn't matter.
`platform_on_leave` doesn't matter.
Static CharacterBody2D receives slide_collisions without moving and receives them while stuck to other body.
Requires minimal code to test. For MRP I used AnimationPlayer for `dir` manipulation.

```gdscript
extends CharacterBody2D

@export var speed_max:float = 60.0
@export var dir:Vector2

func _physics_process(delta: float) -> void:
	velocity = velocity.move_toward(speed_max * dir, delta * 200.0)
	move_and_slide()
```

https://github.com/user-attachments/assets/f58e10ae-863a-4ddf-ae01-f62fcc6fd329



### Steps to reproduce

- CharacterBody2D without velocity calling move_and_slide()
- Second CharacterBody2D running into it and walking away

### Minimal reproduction project (MRP)

[sticky_collision.zip](https://github.com/user-attachments/files/16418895/sticky_collision.zip)
Repository: rust
Issue: Repr is incorrectly documented for structs with hidden field
Labels: T-rustdoc,A-attributes,C-bug,A-repr

```rust
#[repr(transparent)]
pub struct Public {
    pub field: i32,
}

#[repr(transparent)]
pub struct Private {
    field: i32,
}

#[repr(transparent)]
pub struct Hidden {
    #[doc(hidden)]
    pub field: i32,
}
```

<img width="467" alt="Screenshot 2024-07-29 at 1 46 31 PM" src="https://github.com/user-attachments/assets/752d6269-3c9a-4f7e-ba8f-86ca8dadb674">

<img width="467" alt="Screenshot 2024-07-29 at 1 46 15 PM" src="https://github.com/user-attachments/assets/b8ddcbca-ac40-4aaf-9c5e-c3335d3ec896">

<img width="467" alt="Screenshot 2024-07-29 at 1 46 22 PM" src="https://github.com/user-attachments/assets/bf31aebd-a6a4-4e7e-bb64-b75be9c17acd">

Previous discussions of `repr` documentation:

- https://github.com/rust-lang/rust/issues/90435
- https://github.com/rust-lang/rust/pull/115439

I believe the intent was that `repr(transparent)` should only appear in rendered documentation if the field's type is a public API that the documentation reader gets to rely on.

This is the case for `repro::Public`, and not the case for `repro::Private`.

I believe `repro::Hidden` should be treated more like `repro::Private` for the purpose of documenting repr.

In the standard library, this currently impacts `core::pin::Pin`. https://doc.rust-lang.org/1.80.0/core/pin/struct.Pin.html
Repository: rust
Issue: rustc uses a constantly increasing amount of memory up to OS crash or OOM kill
Labels: I-crash,C-bug,T-types,fixed-by-next-solver

Clone the [bug branch of webgraph-rs](https://github.com/vigna/webgraph-rs/tree/bug) and run a check:
```
git clone git@github.com:vigna/webgraph-rs
cd webgraph-rs
git checkout bug
cargo c
```

On MacOs 14.5 (M1), nixos 23.11, and Fedora 38 the compilation process stops at this message:
```
    Building [=======================> ] 207/209: webgraph
```

At this point, `rustc` uses a constantly increasing amount of memory. The result is an OS crash in MacOS, and OOM-kill on Linux.

The problem appears both in stable and nightly.

`rustc --version --verbose`:
```
rustc 1.82.0-nightly (2cbbe8b8b 2024-07-28)
binary: rustc
commit-hash: 2cbbe8b8bb2be672b14cf741a2f0ec24a49f3f0b
commit-date: 2024-07-28
host: aarch64-apple-darwin
release: 1.82.0-nightly
LLVM version: 18.1.7

rustc 1.80.0 (051478957 2024-07-21)
binary: rustc
commit-hash: 051478957371ee0084a7c0913941d2a8c4757bb9
commit-date: 2024-07-21
host: aarch64-apple-darwin
release: 1.80.0
LLVM version: 18.1.7
```

The same setup works without problems on Arch Linux.

UPDATE: the first post claimed mistakenly that the check was working on Fedora 38.
Repository: TypeScript
Issue: Paste with imports should not add imports when pasting into a string
Labels: Bug,Help Wanted,Fix Available

### 🔎 Search Terms

- Paste with imports

### 🕗 Version & Regression Information

5.6.0-dev.20240729

### ⏯ Playground Link

_No response_

### 💻 Code

For a project


```ts
// abc.ts
export const abc =123;

console.log(abc);
```

Copy and paste `abc` into a file:

```ts
const str = "|"
```

Where `|` is the cursor position 


### 🙁 Actual behavior

An import is added:

```ts
import { abc } from "./abc";

const a = 'abc'
```

### 🙂 Expected behavior

No import added

### Additional information about the issue

_No response_
Repository: godot
Issue: Clicking outside popup in single window mode will pass the event
Labels: bug,topic:input,topic:gui

### Tested versions

4.3 rc1 and earlier

### System information

Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1060 (NVIDIA; 31.0.15.4633) - Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 Threads)

### Issue description

When you run editor in single window mode and click outside a popup to close it, the popup is closed, but the event is passed further.
In multi window mode closing the popup by clicking outside will block the event from propagating further.

This inconsistency caused #93718

### Steps to reproduce

1. Open editor in any window mode
2. Open a popup menu
3. Click a node in 2D editor while the popup is open
4. Repeat the steps with other window mode and compare results

### Minimal reproduction project (MRP)

N/A
Repository: rust
Issue: Suggest `ptr::null` when using `ptr::addr_of!(0)` or `&raw const 0`
Labels: A-diagnostics,T-compiler

### Code

```Rust
fn main() {
    let null = std::ptr::addr_of!(0);
}
```


### Current output

```Shell
error[E0745]: cannot take address of a temporary
 --> src/main.rs:2:35
  |
2 |     let null = std::ptr::addr_of!(0);
  |                                   ^ temporary value

For more information about this error, try `rustc --explain E0745`.
```


### Desired output

```Shell
error[E0745]: cannot take address of a temporary
 --> src/main.rs:2:35
  |
2 |     let null = std::ptr::addr_of!(0);
  |                                   ^ temporary value
note: if you wanted to create a null pointer, use `core::ptr::null` instead
  |
2 |     let null = core::ptr::null();
  |                ~~~~~~~~~~~~~~~~~
For more information about this error, try `rustc --explain E0745`.
```


### Rationale and extra context

The same applies for `let null = std::ptr::addr_of_mut!(0);`, `let null = &raw const 0;` and `let null = &raw mut 0;`.
In all these cases, the intention was likely to create a null pointer instead of a pointer to 0.
Especially with `&raw` syntax, this seems like a plausible mistake.

### Other cases

_No response_

### Rust Version

```Shell
rustc 1.80.0 (051478957 2024-07-21)
binary: rustc
commit-hash: 051478957371ee0084a7c0913941d2a8c4757bb9
commit-date: 2024-07-21
host: x86_64-unknown-linux-gnu
release: 1.80.0
LLVM version: 18.1.7
```


### Anything else?

_No response_
Repository: flutter
Issue: Cupertino Context Menu accessibility issue, doesn't seem to respect User's setting in Settings>Accessibility>Touch>Haptic
Labels: framework,f: cupertino,has reproducible steps,P2,team-design,triaged-design,found in release: 3.22,found in release: 3.24

### Steps to reproduce

Go to Settings>Accessibility>Touch>Haptic on a phone

Change to fast

Then try to tell if that setting was respected in the tap duration in a context menu

### Expected results

The tap duration in context menu should respect the user's setting in Settings>Accessibility>Touch>Haptic

### Actual results

No apparent change to tap/touch duration when interacting with Context Menu

### Code sample

TODO

### Screenshots or Video

https://x.com/mahersafadii/status/1818048784577806560

### Logs

_No response_

### Flutter Doctor output

n/a
Repository: flutter
Issue: CupertinoContextMenu: haptic(vibration) playing almost in the middle of the animation not at the end when it pops
Labels: framework,f: cupertino,P2,team-design,triaged-design
Repository: flutter
Issue: Existence of two independent iOS-style Switch implementations
Labels: framework,f: cupertino,c: proposal,P2,c: tech-debt,team-design,triaged-design

### Use case

There are two independent iOS-style switch implementations: Switch.adaptive and CupertinoSwitch, creating an extra burden of support.

### Proposal

One of them should be used in lieu of the other. `Switch.adaptive` does support material theming, unlike `CupertinoSwitch`. However, it feels intuitive to delegate to `CupertinoSwitch`, especially with their APIs being almost identical. With a proper adaptive theming solution, using `CupertinoSwitch` seems like a no-brainer.

References: 
* #130425 which introduced a parallel `Switch.adaptive`
* https://github.com/flutter/flutter/pull/149465 which brought `CupertinoSwitch` up to date with `Switch.adaptive`

Related to: [#149275](https://github.com/flutter/flutter/issues/149275)
Repository: flutter
Issue: cupertino context menu: the menu options don’t look like the native ones in dark mode
Labels: waiting for customer response,framework,a: fidelity,f: cupertino,has reproducible steps,P2,team-design,triaged-design,found in release: 3.22,found in release: 3.24
Repository: flutter
Issue: CupertinoCheckbox should have an inset dropshadow
Labels: framework,f: cupertino,c: proposal,P2,team-design,triaged-design

### Use case

A macOS-style checkbox has an inner dropshadow, most pronounced at the top edge:
<img width="390" alt="Screenshot 2024-07-29 at 3 41 57 PM" src="https://github.com/user-attachments/assets/53bc256e-c823-4c0b-a9a1-28927b0c2b6f">


### Proposal

`CupertinoCheckbox` should also have this dropshadow to look closer to native macOS checkboxes.
Repository: flutter
Issue: CupertinoContextMenu: they lack blur and transparency
Labels: framework,a: fidelity,f: cupertino,P2,team-design,triaged-design
Repository: flutter
Issue: WidgetState should add a value for AppLifecycleState.inactive
Labels: framework,c: proposal,P2,team-framework,triaged-framework

### Use case

On macOS, widgets change their look when an app is no longer in the foreground but has visible windows:

![ScreenRecording2024-07-29at3 55 25PM-ezgif com-video-to-gif-converter](https://github.com/user-attachments/assets/f861b50b-9416-4ba5-8462-9e32cd67f06d)


### Proposal

Adding this value to the WidgetState enum would allow widget properties to be configured in this state.