sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: Arm32 EABI exception handling
Labels: A-runtime,O-Arm,O-netbsd,T-libs

I am opening this issue to track work regarding improving Arm 32-bit EABI exception-handling. There are a few fixmes that were never addressed and some things that I found a bit unclear. These are currently mostly *questions*, and it is possible this issue may be resolved fully by merely *answering the questions* (and hopefully committing an answer somewhere).

- [ ] How bad is reusing r12, anyways?
- [ ] What's up with NetBSD?

## Arm, GCC, exceptions, and r12

We find this comment in our source:

https://github.com/rust-lang/rust/blob/6106b05b27988f4b946d7af219a6db95fb4477a1/library/std/src/sys/personality/gcc.rs#L126-L136

It's unclear what benefits this has, to me, and if our codegen backend could even exploit them, theoretically, if we did this. Mere correctness? Perhaps mere correctness is worth it, it might just be a fairly simple def.

## NetBSD

According to this [lovingly detailed commit message](https://github.com/rust-lang/rust/pull/50864/commits/32f9b53ed8fe445ea11c7138e827190791058e05), NetBSD on 32-bit Arm using the EABI does not use the Arm EABI exception handling routines.

However, perhaps because it was not seen as relevant, it was not documented what it does use as its approach for unwinding. This is unfortunate, as we have recently seen Arm bugs on NetBSD that appear to be caused by assuming NetBSD on Arm must operate exactly like it does on x86, and discovering we are wrong, because of bugs or other reasons.

@he32 Do all NetBSD architectures use the same unwinding? Do we even unwind correctly on the not-so-x86 NetBSD architectures? Apparently not if this is to be believed? https://github.com/rust-lang/rust/issues/96914
Repository: godot
Issue: Using arrow keys to navigate dropdown menus focus random option when using multi window mode
Labels: bug,platform:linuxbsd,topic:porting,needs testing,topic:input,topic:gui

### Tested versions

Godot v4.3.beta3
Godot v4.2.2.stable

### System information

Godot v4.3.beta3 - Fedora Linux 40 (KDE Plasma) - Wayland - Vulkan (Forward+) - (software emulation on CPU) llvmpipe (LLVM 18.1.6, 256 bits)

### Issue description

Using arrow keys to navigate a dropdown menu (what is the correct name?) in the editor rapidly jumps through selection and then focus seemingly a random option. 
To be more clear: Only happens for first click after opening

Only clicked one time on arrow down key

[Screencast_20240724_220400.webm](https://github.com/user-attachments/assets/086d2143-6a8a-4ccd-9631-1675abe89035)

Same for Scene, Project Debug.. dropdowns too. Maybe more frequently on them or more visible.

Tested on both Fedora and Windows 10, with same result.

Good luck with your selection! :)





### Steps to reproduce

Click on a button that opens a dropdown menu (like Scene or Project) and then press down or up key on your keyboard

### Minimal reproduction project (MRP)

N/A
Repository: PowerToys
Issue: Microsoft Edge does not pick up FancyZones
Labels: Issue-Bug,FancyZones-Dragging&UI,Product-FancyZones,Needs-Triage

### Microsoft PowerToys version

0.82.1

### Installation method

GitHub

### Running as admin

No

### Area(s) with issue?

FancyZones

### Steps to reproduce

1. Open a Microsoft Edge browser instance
2. Try to drag it to a zone

### ✔️ Expected Behavior

Edge should snap to the zone like other browsers (Chrome, etc.). This works on my personal computer.

### ❌ Actual Behavior

When "Hold Shift key to activate zones while dragging a window" is checked, the zones do not even appear when I hold Shift and drag the Edge window. 

When "Hold Shift key to activate zones while dragging a window" is not checked, Edge is able to recognize that zones are there, but it does not snap to them.

### Other Software

Microsoft Edge version: Version 126.0.2592.113 (Official build) (64-bit)
Repository: deno
Issue: deno.jsonc silently ignored if deno.json is present
Labels: perf,lsp

Version: Deno 1.45.3

If both `deno.json` and `deno.jsonc` are present, there is no warning at that the latter is not processed. We should consider warning that `deno.jsonc` was present but not processed. 

While running through documentation examples, I inadvertently ended up with both files (I created deno.jsonc and deployctl created deno.json) and spent several minutes figuring out why my import map (defined in the redundant deno.jsonc file) wasn't working.
Repository: flutter
Issue: Make Xcode Cloud build number match Flutter build number
Labels: c: new feature,platform-ios,tool,t: xcode,c: proposal,P3,team-ios,triaged-ios

### Use case

Is there any way at all that Flutter build numbers could be kept in sync with Xcode Cloud build numbers, for Flutter iOS builds?

When building a Flutter app via Xcode Cloud, Xcode Cloud will apply its own build number:

https://developer.apple.com/documentation/xcode/setting-the-next-build-number-for-xcode-cloud-builds

This number increases by 1 each time you build, which may be as frequently as once per push, if you set up a GitHub hook for that.

You can manually change the current build number in Xcode Cloud settings. However, even if you set up the Flutter build number to auto-increment each time you push a change, so that hopefully the Xcode Cloud build number matches the Flutter build number, the Xcode Cloud build number can get out of sync with the Flutter build number for a number of reasons (e.g. if you push changes once, then wait insufficient time before pushing changes a second time, because the second set of changes will cancel the build from the first set of changes).

I can't find a way online to programmatically update the Xcode Cloud build number -- it looks like you have to make that change through the web interface. (But I would love to be wrong about this.) However, in Xcode's config files at least, you can use `${CI_BUILD_NUMBER}` to get the Xcode Cloud build number. I assume this doesn't work for local builds. 

However, maybe it would be possible for "reverse integration" -- where `${CI_BUILD_NUMBER}` is copied into `pubspec.yaml` if it is available? But then that would have to be pushed back into the git repo for the project, from the CI server, so that's not at all ideal.

### Proposal

Please provide some way to keep Flutter build numbers in sync with Xcode Cloud build numbers.

Ideally this would be by pushing the current Flutter build number to Xcode Cloud at the start of each build, if a programmatic way can be found to change the Xcode Cloud settings.
Repository: godot
Issue: Stop debugging (F8) shortcut activates even if modifiers are pressed while game window is focused
Labels: bug,topic:editor

### Tested versions

- Reproducible in: v3.5.3.stable.official [6c814135b]
- Not reproducible in: v4.2.2.stable.official [15073afe3]

### System information

Manjaro stable - amd64 - X11 - KDE Plasma 6.0.5

### Issue description

I have the `editor/stop` (Stop debugging) keyboard shortcut set to <kbd>F8</kbd>, as by default.

While the window of the game being debugged is in focus, pressing key combinations with modifiers, such as <kbd>Alt</kbd>+<kbd>Meta</kbd>+<kbd>F8</kbd>, or <kbd>Alt</kbd>+<kbd>F8</kbd>, also stops debugging and terminates the running game, in addition to just <kbd>F8</kbd>. This is of course undesirable, since I use global keybinds like <kbd>Alt</kbd>+<kbd>Meta</kbd>+<kbd>F8</kbd> in other software to perform unrelated actions.

While window focus is on the editor window instead, the problem doesn't occur - only <kbd>F8</kbd> by itself stops debugging and terminates the game.

According to the source code I've been able to find [1], the input event should be matched exactly against the shortcut, so I'm guessing the editor is getting the input event without modifiers in some way.

[1] https://github.com/godotengine/godot/blob/470ef4d63e4a962950647da24d114b3889eefb1f/core/os/input_event.h#L316

### Steps to reproduce

1. Create empty runnable project
2. Run (<kbd>F5</kbd>)
3. With the running app window in focus, press <kbd>Alt</kbd>+<kbd>F8</kbd>, <kbd>Ctrl</kbd>+<kbd>F8</kbd>, <kbd>Alt</kbd>+<kbd>Meta</kbd>+<kbd>F8</kbd>, etc.

### Minimal reproduction project (MRP)

N/A
Repository: flutter
Issue: flutter doctor shows ERRORS and then says "no issues found"
Labels: platform-ios,t: xcode,P2,team-ios,triaged-ios

### Steps to reproduce

We ran `flutter doctor` and we saw a surprising thing that took us "out of flow". In this case, the use have an iPhone for development.

### Expected results

We discussed some options. We think one idea would be to:

* add context for _what sub-function or sub-tool_ is spitting out the output that we're copying and displaying.

In this case, we think the ERRORS are from some underlying apple toolchain tools.

So, we could imagine the output of `flutter doctor` becomes something like:

```
[check] Connected devices (3 available)
Output from <name of tool>, which should be considered _informational_ and may not impact the results of `flutter doctor`:
ERROR: Browsing....
ERROR: Browsing...
```

There are probably better ways to do it, but the primary suggestion here is to qualify/contextualize _where_ the following text is coming from, and if the developer should consider it "from flutter" or "from some underlying tool".

In this way, when flutter doctor says "no issues found", it'll make more sense. And, the developer can see "oh, it's <this tool> that is saying the ERROR, I get it now"

### Actual results


Here's what we saw:

![Screenshot 2024-07-24 at 3 15 58 PM](https://github.com/user-attachments/assets/88d96d80-e524-4112-9eec-a7cd305bcfe7)

We also saw a "No issues found" at the end of the flutter doctor output. This was surprising because, as we can see in the screenshot above, "there were errors" so why "no issues found"? might be a question a user might have.

### Code sample

<details open><summary>Code sample</summary>

```dart
[Paste your code here]
```

</details>


### Screenshots or Video

<details open>
<summary>Screenshots / Video demonstration</summary>

[Upload media here]

</details>


### Logs

_No response_

### Flutter Doctor output

n/a (see above)
Repository: angular
Issue: Add an option to disallow concrete root providers to be used in TestBed
Labels: area: testing

### Which @angular/* package(s) are relevant/related to the feature request?

core

### Description

Currently, `TestBed` will happily use any `providedIn: 'root'` dependencies, in addition to dependencies provided by the component under test, or in non-standalone applications, module providers. This makes it extremely easy to introduce concrete dependencies to the test environment and thus break unit test isolation.

### Proposed solution

Add an option to `TestBed.configureTestingModule` that removes root, component, and module providers from consideration. This will force developers to provide mocks (or at least consciously choose concrete implementations) for all dependencies of a component.

Dependencies internal to the framework, such as those used by `effect` will need to be excluded from this restriction as framework functionality does not need to be mocked.

### Alternatives considered

Another approach would be to add a validation method that no concrete user services have been injected, similar to `HttpTestingController.verfiy`. I feel that putting it upfront rather than a testing assertion is more readable and harder to make a mistake with, but if the implementation of such a method is easier then it is a valid solution to the problem.
Repository: flutter
Issue: Switching between channels could be streamlined and result in less downloaded artifacts
Labels: P3,team-tool,triaged-tool

### Use case

We want to encourage folks to try beta channel.

### Proposal

 If it's easy to do, we want to find ways to streamline and simplify.

Today, developers need to do two steps:

```
flutter channel beta
flutter upgrade
```

Both of those options require the user to download artifacts. Seems like there might be duplicative downloading?

One idea here is to add a `flutter channel --upgrade` which does two things:

* runs upgrade when channel switching is done
* smartly downloads artifacts _once_
Repository: deno
Issue: suggestion: support `options` argument in `Deno.errors.*` constructors
Labels: public API,suggestion

Namely, [`option`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/Error#options) would allow code to define an error's [`cause`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/cause) property, and provide added context to an error.
Repository: react-native
Issue: No hot reloading when change font scale
Labels: Issue: Author Provided Repro,Type: New Architecture

### Description

In old arch, we can change font scale in realtime with `command option +/-`.
In new arch, it has to be refreshed manually with pressing R to get new font scale applied.

### Steps to reproduce

1. `gh repo clone yzhe554/new-arch-font-scale`
2. `cd new-arch-font-scale`
3. `npm i`
4. `npm run ios`
5. change font scale with `option command +/-`

### React Native Version

0.74.3

### Affected Platforms

Runtime - iOS

### Areas

Fabric - The New Renderer

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

```text
System:
  OS: macOS 14.5
  CPU: (10) arm64 Apple M1 Max
  Memory: 107.00 MB / 32.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 18.18.0
    path: ~/.nvm/versions/node/v18.18.0/bin/node
  Yarn:
    version: 1.22.18
    path: /usr/local/bin/yarn
  npm:
    version: 9.8.1
    path: ~/.nvm/versions/node/v18.18.0/bin/npm
  Watchman:
    version: 2024.05.06.00
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.15.2
    path: /opt/homebrew/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.5
      - iOS 17.5
      - macOS 14.5
      - tvOS 17.5
      - visionOS 1.2
      - watchOS 10.5
  Android SDK: Not Found
IDEs:
  Android Studio: 2023.2 AI-232.10300.40.2321.11567975
  Xcode:
    version: 15.4/15F31d
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.9
    path: /usr/bin/javac
  Ruby:
    version: 2.7.6
    path: /Users/yuzheng/.rbenv/shims/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: Not found
  newArchEnabled: Not found
iOS:
  hermesEnabled: true
  newArchEnabled: true
```


### Stacktrace or Logs

```text
N/A
```


### Reproducer

https://github.com/yzhe554/new-arch-font-scale

### Screenshots and Videos

In Old Arch

https://github.com/user-attachments/assets/b1e2d7a7-1070-4d3d-ac2c-a7e75952ef03

In New Arch

https://github.com/user-attachments/assets/e7ef203c-c355-4674-80de-e508c046e61f
Repository: flutter
Issue: Build Android `gen_snapshot` as arm64 binary to run natively on Apple Silicon
Labels: platform-android,engine,platform-mac,P2,team-ios,triaged-ios

On an arm64 Apple Silicon Mac, the published `gen_snapshot` binaries are `x86_64` and therefore run with Rosetta translation.
```
android-arm-profile/darwin-x64/gen_snapshot
android-arm-release/darwin-x64/gen_snapshot
android-arm64-profile/darwin-x64/gen_snapshot
android-arm64-release/darwin-x64/gen_snapshot
android-x64-profile/darwin-x64/gen_snapshot
android-x64-release/darwin-x64/gen_snapshot
```
Compile Android `gen_snapshot` binaries as arm64, and publish in the arm64 Flutter install (`artifacts.zip`), as well as the macOS desktop artifacts that get `curl`ed when upgrading on an arm64 Mac.

macOS issue was https://github.com/flutter/flutter/issues/101138
iOS issue was https://github.com/flutter/flutter/issues/152280
Repository: rust
Issue: rustc should allow moving a value and its borrowed data into a `move` closure.
Labels: T-lang,C-feature-request,T-types

Given the following code ([playground](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=32467de2aca9359367f7e8cdc8a8ec61)):

```rust
struct Borrows<'a>(&'a String);

impl<'a> Borrows<'a> {
    fn do_something(&self) {
        println!("data contents: {}", self.0);
    }
}

fn main() {
    let data = String::from("hi-ho kermit thee frog heer");
    let borrower = Borrows(&data);
    
    let _ = move || {
        println!("data size: {}", data.len());
        borrower.do_something();
    };
}
```

The following error is produced on stable (1.79.0) and nightly (1.81.0-nightly):

```
error[E0505]: cannot move out of `data` because it is borrowed
  --> src/main.rs:13:13
   |
10 |     let data = String::from("hi-ho kermit thee frog heer");
   |         ---- binding `data` declared here
11 |     let borrower = Borrows(&data);
   |                            ----- borrow of `data` occurs here
12 |     
13 |     let _ = move || {
   |             ^^^^^^^ move out of `data` occurs here
14 |         println!("data size: {}", data.len());
   |                                   ---- move occurs due to use in closure
15 |         borrower.do_something();
   |         -------- borrow later captured here by closure
   |
help: consider cloning the value if the performance cost is acceptable
   |
11 -     let borrower = Borrows(&data);
11 +     let borrower = Borrows(data.clone());
   |
```

This would normally make sense, except for the fact that both `borrower` **and** `data` are moved into the closure, and the `println!` statement inside the closure does not consume `data`.

So in theory, rustc could allow this code. It seems like it would be similar to other ways in which rustc pushes around lexical scopes in order to allow more code to be valid.

## Alternatives

Alternatively, rustc could suggest that the `move` is not necessary:

```
help: consider capturing by reference instead of by value
   |
13 -     let _ = move || {
13 +     let _ = || {
   |
```

Or it could suggest rebinding as a reference to be moved into the closure:

```
help: consider capturing `data` by reference instead of by value
   |
   +     let data = &data;
13 |     let _ = move || {
   |
```

@rustbot label +T-compiler
Repository: godot
Issue: DisplayServer.mouse_get_position() is really slow on X11
Labels: bug,platform:linuxbsd,topic:porting,confirmed,performance

### Tested versions

- Reproducible in: v4.2.2.stable.official [15073afe3]

### System information

Godot v4.2.2.stable - Manjaro Linux #1 SMP PREEMPT_DYNAMIC Mon Jul 15 21:39:34 UTC 2024 - X11 - GLES3 (Compatibility) - NVIDIA GeForce GTX 1070 Ti (nvidia; 550.100) - Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz (8 Threads)

### Issue description

`DisplayServer.mouse_get_position()` takes around 0.08ms to run on my X11 system.

This is an issue because many functions call it directly or indirectly, like `CanvasItem.get_global_mouse_position`/`get_local_mouse_position` and `Viewport.get_mouse_position()`. A game that calls these functions multiple times per frame could end up having serious performance problems for some users, and it wouldn't be caught easily if the game was developed in a different platform.

It seems that other DisplayServer implementations call `Input::get_singleton()->get_mouse_position()`, which returns a cached value. But on X11, it runs [all this](https://github.com/godotengine/godot/blob/2f2d1a7e68d315e5f26cde30532a51087536c9f6/platform/linuxbsd/x11/display_server_x11.cpp#L489) instead.


### Steps to reproduce

Run something like the following code:
```gdscript
	var start := Time.get_ticks_msec()
	for i in 3_000:
		DisplayServer.mouse_get_position()
	var end := Time.get_ticks_msec()
	print((end - start) / 3_000.0)
```

### Minimal reproduction project (MRP)

-
Repository: terminal
Issue: PATHEXT not working as expected
Labels: Product-Cmd.exe,Issue-Bug,Needs-Tag-Fix,zInbox-Bug

### Windows Terminal version

1.20.11781.0

### Windows build number

10.0.22631.3880

### Other Software

_No response_

### Steps to reproduce

Using cmd.exe
Create a shortcut to "C:\Program Files\7-Zip\7z.exe" in C:\Shims\7z.exe.lnk
Add C:\Shims to PATH - set PATH=%PATH%;C:\Shims
Add .exe.lnk to PATHEXT - set PATHEXT=%PATHEXT%;.exe.lnk
execute "7z"

### Expected Behavior

7z should execute.
This works on Windows 10 but doesn't work on Windows 11.
Also "where 7z" works correctly on both Windows 10 and Windows 11.

### Actual Behavior

'7z' is not recognized as an internal or external command,
operable program or batch file.
Repository: tensorflow
Issue: Does TensorFlow2.13.0 support RISC-V
Labels: stat:awaiting tensorflower,type:support,TF 2.13

### Issue type

Support

### Have you reproduced the bug with TensorFlow Nightly?

No

### Source

source

### TensorFlow version

2.13.0

### Custom code

Yes

### OS platform and distribution

Linux openeuler-riscv-4-2 6.6.0

### Mobile device

_No response_

### Python version

3.11.6

### Bazel version

5.3.0

### GCC/compiler version

12.3.1

### CUDA/cuDNN version

no

### GPU model and memory

no

### Current behavior?

I recently tried to build TensorFlow2.13.0 with bazel5.3.0 on RISC-V, but I encountered the following error during the build process：
```
ERROR: /home/tf2130/.cache/bazel/_bazel_tf2130/4d8a15755e0d938e330a7b941554a2cb/external/mkl_dnn_v1/BUILD.bazel:146:11: Compiling src/cpu/x64/rnn/brgemm_cell_common_bwd.cpp failed: (Exit 1): gcc failed: error executing command /usr/lib64/ccache/gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer -g0 -O2 '-D_FORTIFY_SOURCE=1' -DNDEBUG -ffunction-sections ... (remaining 67 arguments skipped)
external/mkl_dnn_v1/src/cpu/x64/rnn/brgemm_cell_common_bwd.cpp: In member function 'void dnnl::impl::cpu::x64::brgemm_diff_src_layer_iter_t<weights_t, scratch_t, gemm_acc_t>::execute() const':
external/mkl_dnn_v1/src/cpu/x64/rnn/brgemm_cell_common_bwd.cpp:102:37: error: 'const struct dnnl::impl::cpu::rnn_utils::diff_src_brgemm_conf_t' has no member named 'isa'
  102 |             && rnn_.diff_src_brgemm.isa == x64::avx512_core_bf16_amx_bf16) {
      |                                     ^~~
Target //tensorflow/tools/pip_package:build_pip_package failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 69717.150s, Critical Path: 1675.59s
INFO: 9452 processes: 1564 internal, 7888 local.
FAILED: Build did NOT complete successfully
```

### Standalone code to reproduce the issue

```shell
git clone https://github.com/tensorflow/tensorflow.git
cd tensorflow
git checkout tags/v2.13.0
bazel build //tensorflow/tools/pip_package:build_pip_package --local_ram_resoues=1024 --jobs=6
```


### Relevant log output

_No response_