sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: react-native
Issue: Accessibility roles 'radio' & 'checkbox' not announced by screenreader on ios since 0.73.0
Labels: Platform: iOS,Issue: Author Provided Repro

### Description

since version `v0.73.0` the roles for `radio` & `checkbox` are not announced by Screen readers on ios
this was working in `v0.72.10` but stopped working in `v0.73.0`



### Steps to reproduce

1. install the app with `yarn ios`
2. navigate with a screenreader or Accessibility inspector to the text `Welcome to React Native` and go down from there
3. listen to the output - it does not announce roles for `radio` & `checkbox` - `button` is still announced fine

### React Native Version

0.73.5

### Affected Platforms

Runtime - iOS

### Output of `npx react-native info`

```text
System:
  OS: macOS 13.6.1
  CPU: (10) arm64 Apple M1 Max
  Memory: 1.12 GB / 32.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 20.10.0
    path: ~/.nvm/versions/node/v20.10.0/bin/node
  Yarn:
    version: 1.22.21
    path: ~/.nvm/versions/node/v20.10.0/bin/yarn
  npm:
    version: 10.2.3
    path: ~/.nvm/versions/node/v20.10.0/bin/npm
  Watchman:
    version: 2023.11.06.00
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods: Not Found
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.10811636
  Xcode:
    version: 15.2/15C500b
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 11.0.15
    path: /Users/lutz.kwauka/.sdkman/candidates/java/current/bin/javac
  Ruby:
    version: 2.6.10
    path: /Users/lutz.kwauka/.rbenv/shims/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.73.5
    wanted: 0.73.5
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: true
  newArchEnabled: false
```


### Stacktrace or Logs

```text
no crash happened
```


### Reproducer

https://github.com/lutzk/accessibility-reproducer/

### Screenshots and Videos

`v0.72.10` working:
https://github.com/facebook/react-native/assets/793755/cec0dd90-6b7b-40d1-9fb5-9cd1d00e3f97

`v0.73.5` not working:
https://github.com/facebook/react-native/assets/793755/c86794d2-f4fa-43df-835e-93315a63aa46
Repository: deno
Issue: deno publish not using jsr.json when deno.json exists
Labels: bug,good first issue,publish,jsr

Version: deno 1.41.1 (release, x86_64-pc-windows-msvc)

### Problem:
When I have a _deno.json_ file in the base folder **deno publish** doesnt seem to respect or even try to read options from _jsr.json_.

Error message looks like this.
```
PS E:\code\PROJECTNAME> deno publish --dry-run
error: file:///E:/code/PROJECTNAME/deno.json is missing 'name' field
```
if I rename or delete deno.json it correctly reads jsr.json when publishing.
```
PS E:\code\PROJECTNAME> deno publish --dry-run
Checking for slow types in the public API...
Simulating publish of <PACKAGE>@0.5.3 with files:
..
... FILE LIST REMOVED
```
### Expected behaviour:
**deno publish** should check for the relevant options in _jsr.json_ when the options is not included in _deno.json_. Or maybe even primary looking for the publish options in jsr.json.
Repository: go
Issue: x/pkgsite: inconsistency major version between pseudo version and base version
Labels: Unfortunate,modules,pkgsite

### What is the URL of the page with the issue?

https://pkg.go.dev/github.com/ricoberger/script_exporter@v1.3.1-0.20240210123610-ebeaf9415eb1

### What did you do?

https://github.com/ricoberger/script_exporter has released an valid version "v2.18.0" (commit id: ebeaf9415eb1) (just an example no offence)

However script_exporter's mod has no major suffix with "/v2", but [github.com/ricoberger/script_exporter@v1.3.1-0.20240210123610-ebeaf9415eb1](https://pkg.go.dev/github.com/ricoberger/script_exporter@v1.3.1-0.20240210123610-ebeaf9415eb1) is an valid "pseudo version" according to ["mod spec"](https://go.dev/ref/mod#pseudo-versions) 

My concern is clearly v2 incompatible with v1, but import "v1.3.1-0.20240210123610-ebeaf9415eb1" that will breaks [minimal version selection](https://go.dev/ref/mod#glos-minimal-version-selection) since both version (`v1.3.0` and `v1.3.1-0.20240210123610-ebeaf9415eb1`) has same major version.

### What did you see happen?

https://pkg.go.dev/github.com/ricoberger/script_exporter@v1.3.1-0.20240210123610-ebeaf9415eb1 is valid version

### What did you expect to see?

No valid version if pseudo version related commit is after different major semver tag.
Repository: opencv
Issue: cv2.pyrDown breaks the symmetry and shifts the data to the bottomright corner
Labels: bug,category: imgproc

### System Information

OpenCV python version: 4.8.0.74
Operating System / Platform: MacOS M1 Silicon
Python version: 3.9.4

### Detailed description

The function `cv2.pyrDown` shifts the data due to the rejection of even rows and columns instead of doing proper bilinear interpotation, or at least averaging over 2x2 window. This can be reproduced by downscaling a simple symmetrical 4x4 image.


### Steps to reproduce

```python
import cv2
import numpy as np

img = np.zeros((4,4))
img[1:3,1:3] = 1
print (f'{img=}')

cv2_2x2 = cv2.pyrDown(img)
print (f'{cv2_2x2=}')
```

Result:

```
img=array([[0., 0., 0., 0.],
       [0., 1., 1., 0.],
       [0., 1., 1., 0.],
       [0., 0., 0., 0.]])
cv2_2x2=array([[0.390625  , 0.4296875 ],
       [0.4296875 , 0.47265625]])
```

Expected result: the output should be symmetrical.

Example from kornia:

```
import kornia 
import numpy as np
img=array([[0., 0., 0., 0.],
       [0., 1., 1., 0.],
       [0., 1., 1., 0.],
       [0., 0., 0., 0.]])
kornia_2x2 = kornia.geometry.pyrdown(kornia.image_to_tensor(img, False))
print (f'{kornia_2x2=}')
```

output:
```
kornia_2x2=tensor([[[[0.4307, 0.4307],
          [0.4307, 0.4307]]]], dtype=torch.float64)
```

### 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
- [X] I updated to the latest OpenCV version and the issue is still there
- [X] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: go
Issue: cmd/asm,cmd/compile: add support for control flow integrity
Labels: NeedsInvestigation,compiler/runtime

Modern CPUs provide support for branch tracking control flow integrity (BTCFI) in the form of Intel's Indirect Branch Tracking (IBT) and AARCH64's Branch Tracking Identification (BTI). BTCFI helps to mitigate flow control based exploits, such as those achieved via Jump Oriented Programming (JOP). 

Some operating systems (for example, OpenBSD 7.4 onwards) are starting to enforce IBT and BTI on hardware where it is available (Intel Tigerlake onwards, Apple's M2, etc). Go binaries need to be marked with `PT_OPENBSD_NOBTCFI` in order to allow them to execute. Other operating systems have varying levels of support (Linux enables IBT in the kernel, but not userland AIUI - https://lwn.net/Articles/889475/).

Go should ideally support BTCFI - in the IBT/BTI case it is effectively a matter of providing a "landing pad" instruction (`endbr64` on `amd64` and `bti c` on `arm64`), at function entry points and any other locations where control flow is expected to land. On machines that do not support these instructions (or have BTCFI enabled/enforced in userland), they are effectively a no-ops. This does potentially impact code where it is intentional to jump into a function at some offset - for example, duff devices (`DUFFCOPY`, `DUFFZERO`) and jump tables. This would also need landing pads at each potential entry point, or revisiting/disabling.
Repository: react-native
Issue: Animated - start animation callback is called immediately
Labels: Issue: Author Provided Repro,API: Animated,Newer Patch Available

### Description

When i call the "start()" method of Animated.timing the callback inside it is called immediately and not when the animation finish.

This is the code:
```typescript
Animated.timing(positionY, {
    toValue: 100,
    duration: 500,
    useNativeDriver: false,
}).start(() => {
   hideMessage()
})
```

### Steps to reproduce

I tried to reproduce the error on Expo online but on that playground the code works as expected. I also uploaded the video of the issue

### React Native Version

0.73.5

### Affected Platforms

Runtime - Android, Runtime - iOS

### Output of `npx react-native info`

```text
System:
  OS: macOS 14.3.1
  CPU: (12) x64 Apple M3 Pro
  Memory: 98.03 MB / 18.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 18.19.0
    path: /usr/local/opt/node@18/bin/node
  Yarn:
    version: 1.22.21
    path: /usr/local/bin/yarn
  npm:
    version: 10.2.3
    path: /usr/local/opt/node@18/bin/npm
  Watchman: Not Found
Managers:
  CocoaPods:
    version: 1.14.3
    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: 2023.1 AI-231.9392.1.2311.11330709
  Xcode:
    version: 15.2/15C500b
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.9
    path: /usr/bin/javac
  Ruby:
    version: 2.6.10
    path: /usr/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.73.4
    wanted: 0.73.4
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: true
  newArchEnabled: false
```


### Stacktrace or Logs

```text
My bug is not a crash.
```


### Reproducer

https://snack.expo.dev/9vyz9rIza-lsKdo3usD2v

### Screenshots and Videos

https://github.com/facebook/react-native/assets/15747776/3c4fa16c-9b8d-4697-8d56-0879c57597b2
Repository: vscode
Issue: terminate tasks gracefully and not forcefully on closing VSCode or when using the "kill" (trashcan) button
Labels: feature-request,tasks

<!-- ⚠️⚠️ 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.87.0 (and all versions before I can remember)
- OS Version: Ubuntu 22.04.4

Steps to Reproduce:

I am not able to create a real minimal example, but will show my exact usecase here and try to explain it.

1. create a task with the command `bench start` from frappe bench (https://github.com/frappe/bench) and run it
    * this starts 3 redis servers, a node server, a yarn watcher and some other stuff
3. use the "kill" button for the task or close VSCode
4. `bench start` got terminated, but all the processes it itself spawned are still running
5. reopening VSCode and starting the task again will error out, because the still running redis servers are blocking some necessary ports
    * even if it would work, we would still have multiple resource hogging processes lingering in the background

Pressing CTRL-C instead in the tasks terminal gracefully shuts it down and `bench start` is able to do its proper teardown of all the spawned processes. I am not invested at all in `bench` so can't answer specific questions to it, but I know that it is using `honcho` and a Procfile to managing all these processes.

So I guess all I am asking for is a way for tasks to not be forcefully killed, but do the same as CTRL-C in the console would do to it.

This seems to describe that the same functionality already exists for `launch.json`: https://github.com/microsoft/vscode-js-debug/issues/630#issuecomment-732414805
Repository: terminal
Issue: Canary release notes should go to the commit on Github
Labels: Area-UserInterface,Product-Terminal,Issue-Task

<!-- Briefly describe which document needs to be corrected and why. -->
In help/about I click release notes.  I don't get the canary release notes.  I should either get them or there should be somewhere I can get the release notes.  I look in git and can't find a branch for the commits for a canary version
Repository: rust
Issue: format args should suggest using the formatter for const values when it makes sense
Labels: A-diagnostics,T-compiler,A-suggestion-diagnostics

### Code

```Rust
const fn msg() -> &'static str {
    "this is a panic"
}

const fn panic_please() -> ! {
    let e = msg();
    panic!("{e}")
}

fn main() {
    panic_please()
}
```


### Current output

```Shell
Errors
Exited with status 101
Standard Error
   Compiling playground v0.0.1 (/playground)
error[E0015]: cannot call non-const formatting macro in constant functions
 --> src/main.rs:7:13
  |
7 |     panic!("{e}")
  |             ^^^
  |
  = note: calls in constant functions are limited to constant functions, tuple structs and tuple variants
  = note: this error originates in the macro `$crate::const_format_args` which comes from the expansion of the macro `panic` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0015]: cannot call non-const fn `Arguments::<'_>::new_v1` in constant functions
 --> src/main.rs:7:5
  |
7 |     panic!("{e}")
  |     ^^^^^^^^^^^^^
  |
  = note: calls in constant functions are limited to constant functions, tuple structs and tuple variants
  = note: this error originates in the macro `$crate::const_format_args` which comes from the expansion of the macro `panic` (in Nightly builds, run with -Z macro-backtrace for more info)

For more information about this error, try `rustc --explain E0015`.
error: could not compile `playground` (bin "playground") due to 2 previous errors
Standard Output
```


### Desired output

```Shell
Something along the lines of

Errors
Exited with status 101
Standard Error
   Compiling playground v0.0.1 (/playground)
error[E0015]: cannot call non-const formatting macro in constant functions
 --> src/main.rs:7:13
  |
7 |     panic!("{e}")
  |             ^^^
  |
  = note: calls in constant functions are limited to constant functions, tuple structs and tuple variants
  = note: consider using `panic!("{}", e)` which calls Arguments::new_const

etc...
```


### Rationale and extra context

When not familiar with Arguments and the formatting internals it can be a bit weird to see the panic which morally has a const input fail to compile, especially since clippy heavily encourages users to use the panic!("{e}") syntactic form, while panic!("{}", e) will work just fine in this case

### Other cases

```Rust
All formatting macros likely "suffer" from this
```


### Rust Version

```Shell
rustc 1.78.0-nightly (2bf78d12d 2024-02-18)
binary: rustc
commit-hash: 2bf78d12d33ae02d10010309a0d85dd04e7cff72
commit-date: 2024-02-18
host: x86_64-unknown-linux-gnu
release: 1.78.0-nightly
LLVM version: 18.1.0
```


### Anything else?

Maybe update the formatting macro to automatically call the new_const function if it's able to do so instead of changing the diagnostics, and if it can't then change the diagnostics message (I don't know the exact formatting for those messages but I think you get the idea)

Cheers
Repository: create-react-app
Issue: Snyk Package Analysis - Incomplete List of Disallowed Inputs Vulnerability
Labels: needs triage,issue: bug report

Introduced through: react-scripts@5.0.1
Fixed in: @babel/traverse@7.23.2, @8.0.0-alpha.4

Please upgrade internal package @babel/traverse (v7.20.13 to v7.23.2) of react-scripts


![Screenshot 2024-03-01 at 5 54 44 PM](https://github.com/facebook/create-react-app/assets/14250261/508df959-8fb3-4bd5-8473-c6ff2d6bf723)
Repository: create-react-app
Issue: Snyk Package Analysis - Sandbox Bypass Copy link to issue Vulnerability
Labels: needs triage,issue: bug report

Introduced through: react-scripts@5.0.1
Fixed in: webpack@5.76.0

Please upgrade internal package webpack (v5.75.0 to v5.76.0) of react-scripts

![Screenshot 2024-03-01 at 6 03 38 PM](https://github.com/facebook/create-react-app/assets/14250261/f95d823e-a026-4d2a-811b-ef52b9eb5eae)
Repository: create-react-app
Issue: Snyk Package Analysis - Regular Expression Denial of Service (ReDoS) Vulnerability
Labels: needs triage,issue: bug report

Introduced through: react-scripts@5.0.1
Fixed In: nth-check@2.0.1

Please upgrade internal package nth-check (v1.0.2 to v2.0.1) of react-scripts


![Screenshot 2024-03-01 at 6 07 21 PM](https://github.com/facebook/create-react-app/assets/14250261/7fe203e1-98ac-4785-a11d-818a7bc221e2)
Repository: create-react-app
Issue: Snyk Package Analysis - Regular Expression Denial of Service (ReDoS) Vulnerability
Labels: needs triage,issue: bug report

Introduced through: react-scripts@5.0.1
Fixed In: semver@5.7.2, @6.3.1, @7.5.2

Please upgrade internal package xmsemverl2js (v7.3.8 & v6.3.0 to v7.5.2) of react-scripts

![Screenshot 2024-03-01 at 6 09 39 PM](https://github.com/facebook/create-react-app/assets/14250261/a9c3ef8b-aa8c-447b-b590-790c8f09c890)
Repository: create-react-app
Issue: Snyk Package Analysis - Improper Input Validation Vulnerability
Labels: needs triage,issue: bug report

Introduced through: react-scripts@5.0.1
Fixed In: follow-redirects@1.15.4

Please upgrade internal package follow-redirects (v1.15.2 to v1.15.4) of react-scripts


![Screenshot 2024-03-01 at 6 20 31 PM](https://github.com/facebook/create-react-app/assets/14250261/7bfe798e-a45b-434e-bab0-c74be90da7f4)
Repository: create-react-app
Issue: Snyk Package Analysis - Prototype Pollution Vulnerability
Labels: needs triage,issue: bug report

Introduced through: react-scripts@5.0.1
Fixed In: tough-cookie@4.1.3

Please upgrade internal package tough-cookie (v4.1.2 to v4.1.3) of react-scripts

![Screenshot 2024-03-01 at 6 25 28 PM](https://github.com/facebook/create-react-app/assets/14250261/ba3d54a2-e040-437e-91f7-62b5a726c01c)
Repository: create-react-app
Issue: Snyk Package Analysis - Missing Release of Resource after Effective Lifetime Vulnerability
Labels: needs triage,issue: bug report

Introduced through: react-scripts@5.0.1
Fixed In: No fix available

Please fix this issue which was introduced in react-scripts@5.0.1

![Screenshot 2024-03-01 at 6 27 44 PM](https://github.com/facebook/create-react-app/assets/14250261/1a48f0e1-cd07-4079-a318-30ec3480e34e)
Repository: vscode
Issue: Git - Support diff textconv on unstaged changes
Labels: feature-request,git

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
Please reopen feature request  #168472.

This Feature tangents only sysadmin who uses ansible and vscode. I am not sure how small the Union is, but I think small enough not reach enough people to get enough likes.

I try to promote it anyway.
Repository: pytorch
Issue: AttributeError: module 'mpmath' has no attribute 'rational'
Labels: high priority,module: binaries,oncall: releng,triaged

### 🐛 Describe the bug

```
tests/tools/_perturbation_space/test_discriminator_classifier.py:48: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
pertpy/tools/_perturbation_space/_discriminator_classifier.py:154: in train
    self.trainer.fit(
/opt/hostedtoolcache/Python/3.11.8/x64/lib/python3.11/site-packages/pytorch_lightning/trainer/trainer.py:537: in fit
    model = _maybe_unwrap_optimized(model)
/opt/hostedtoolcache/Python/3.11.8/x64/lib/python3.11/site-packages/pytorch_lightning/utilities/compile.py:125: in _maybe_unwrap_optimized
    from torch._dynamo import OptimizedModule
/opt/hostedtoolcache/Python/3.11.8/x64/lib/python3.11/site-packages/torch/_dynamo/__init__.py:2: in <module>
    from . import allowed_functions, convert_frame, eval_frame, resume_execution
/opt/hostedtoolcache/Python/3.11.8/x64/lib/python3.11/site-packages/torch/_dynamo/allowed_functions.py:30: in <module>
    from .utils import hashable, is_safe_constant, NP_SUPPORTED_MODULES
/opt/hostedtoolcache/Python/3.11.8/x64/lib/python3.11/site-packages/torch/_dynamo/utils.py:89: in <module>
    import torch.fx.experimental.symbolic_shapes
/opt/hostedtoolcache/Python/3.11.8/x64/lib/python3.11/site-packages/torch/fx/experimental/symbolic_shapes.py:38: in <module>
    from torch.utils._sympy.functions import FloorDiv, Mod, IsNonOverlappingAndDenseIndicator
/opt/hostedtoolcache/Python/3.11.8/x64/lib/python3.11/site-packages/torch/utils/_sympy/functions.py:1: in <module>
    import sympy
/opt/hostedtoolcache/Python/3.11.8/x64/lib/python3.11/site-packages/sympy/__init__.py:30: in <module>
    from sympy.core.cache import lazy_function
/opt/hostedtoolcache/Python/3.11.8/x64/lib/python3.11/site-packages/sympy/core/__init__.py:9: in <module>
    from .expr import Expr, AtomicExpr, UnevaluatedExpr
/opt/hostedtoolcache/Python/3.11.8/x64/lib/python3.11/site-packages/sympy/core/expr.py:4159: in <module>
    from .mul import Mul
/opt/hostedtoolcache/Python/3.11.8/x64/lib/python3.11/site-packages/sympy/core/mul.py:2193: in <module>
    from .numbers import Rational
```

This leads to

`AttributeError: module 'mpmath' has no attribute 'rational'`

### Versions

My CI installs the pre-releases. 

cc @ezyang @gchanan @zou3519 @kadeng @seemethere @malfet @osalpekar @atalman