sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: react
Issue: [Compiler Bug]: eslint plugin rule only applied to first instance inside a file
Labels: Type: Bug,Status: Unconfirmed,Component: Optimizing Compiler

### What kind of issue is this?

- [ ] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [X] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhHCA7MAXABAMwglwF5cAKASlID4LqS7gBfAHQ3YQA8AHCGPABME+AIZQANnnxQMcbAEtMuALIBPAII8eVXMHa5c6LNKIBhURIkAjUXADWpXACUEd7ADooYBBau2HckIIKkoDI0wcXFsYPxs7RzJXdy8fOID7IKJQ9nCYBGxYDFwAHkEFADcaAAkEK2IAdX4JQRKAenKqgG52NgwQZiA

### Repro steps

For the rule 'Expected the first argument to be an inline function expression', it is only applied to the first violation even if there is more than one violation. (Example in playground link.) Moreover, on my setup if I eslint-disable the first violation and then eslint-enable after, then subsequent violations still aren't shown. I couldn't get eslint-disable to work in the playground though.

### How often does this bug happen?

Every time

### What version of React are you using?

18.3.1

### What version of React Compiler are you using?

n/a eslint-plugin issue
Repository: ui
Issue:  I have two sidebar how to trigger each of them
Labels: area: request

I have two sidebar how to trigger each of them 
I have right sidebar and left sidebar how to have close button for each one speartly ???
Repository: flutter
Issue: [dash forum?] Adoping new features for readability
Labels: team,P3,team-framework,triaged-framework,d: docs/

### Extension types

- https://github.com/flutter/flutter/pull/158466

<br>

(plus a couple of other topics, [see below](https://github.com/flutter/flutter/issues/158954#issuecomment-2484307494)!)
Repository: flutter
Issue: CPU sampling broken for Dart CLI applications with VM developer options enabled.
Labels: tool,dependency: dart,d: devtools,P2,team-tool,dependency:dart-triaged

Repro.

1. Run the flutter tool from source

```
cd packages/flutter_tools
dart --pause-isolates-on-start  --observe lib/executable.dart doctor
```

Connect and open devtools 

```
jonahwilliams-macbookpro3:flutter_tools jonahwilliams$ dart --pause-isolates-on-start --pause-isolates-on-exit  --observe lib/executable.dart doctor
The Dart VM service is listening on http://127.0.0.1:8181/fyaRaipVUnQ=/
The Dart DevTools debugger and profiler is available at: http://127.0.0.1:8181/fyaRaipVUnQ=/devtools/?uri=ws://127.0.0.1:8181/fyaRaipVUnQ=/ws
vm-service: isolate(4954098837581171) 'main' has no debugger attached and is paused at start.  Connect to the Dart VM service at http://127.0.0.1:8181/fyaRaipVUnQ=/ to debug.
^C
```

Resume Isolate and click "start recording".  let this run for a second or so and then click stop.

![image](https://github.com/user-attachments/assets/cab64d58-7adf-484c-84dc-044e65b1013f)


Problems:

1. even with `--pause-isolates-on-exit ` the dart isolate immediately exits, which causes devtools to stop working. I hacked around this by adding an await 

```diff
diff --git a/packages/flutter_tools/lib/runner.dart b/packages/flutter_tools/lib/runner.dart
index f1a46f9a9a..268ee416e0 100644
--- a/packages/flutter_tools/lib/runner.dart
+++ b/packages/flutter_tools/lib/runner.dart
@@ -3,6 +3,7 @@
 // found in the LICENSE file.
 
 import 'dart:async';
+import 'dart:developer' as dev;
 
 import 'package:args/command_runner.dart';
 import 'package:intl/intl.dart' as intl;
@@ -130,6 +131,8 @@ Future<int> run(
 
         await runner.run(args);
 
+        await Future.delayed(Duration(hours: 16));
+
         // Triggering [runZoned]'s error callback does not necessarily mean that
         // we stopped executing the body. See https://github.com/dart-lang/sdk/issues/42150.
         if (firstError == null) {
```

2. The CPU profile will never load, even though the isolate is not paused. If I open the browser console, i see what looks like parsing errors

![image](https://github.com/user-attachments/assets/e82f283d-c535-4709-824c-341bd07f59f0)

I am running this on the beta channel, meaning the next stable.

```
[!] Flutter (Channel [user-branch], 3.27.0-1.0.pre.4, on macOS 14.7.1 23H222 darwin-arm64, locale en)
    ! Flutter version 3.27.0-1.0.pre.4 on channel [user-branch] at /Users/jonahwilliams/flutter
      Currently on an unknown channel. Run `flutter channel` to switch to an official channel.
      If that doesn't fix the issue, reinstall Flutter by following instructions at https://flutter.dev/setup.
```
Repository: terminal
Issue: GPT-4o
Labels: Issue-Feature,Product-Terminal,Needs-Tag-Fix,Area-Chat

### Description of the new feature

I would appreciate the option to switch the ChatGPT model to 4o, as I have better results with it when programming and communicating in non-English languages.

### Proposed technical implementation details

_No response_
Repository: godot
Issue: The lighting is breaking
Labels: bug,topic:rendering,regression,topic:3d

### Tested versions

4.4 dev4

### System information

Godot v4.4.dev4 - Windows 10.0.19045 - Multi-window, 1 monitor - Vulkan (Forward+) - dedicated Radeon RX 560 Series (Advanced Micro Devices, Inc.; 31.0.14001.45012) - Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz (4 threads)

### Issue description

I noticed a few issues when migrating my project from 4.3 stable to 4.4 dev4.

1. Lighting in 4.4 dev4 does not look as intended:

 4.3 (Good):
![1](https://github.com/user-attachments/assets/efd8f4e2-b298-4ce6-bc31-d80da43afec8)

4.4 dev4 (Badly):
![3](https://github.com/user-attachments/assets/a2b9313b-aa53-4a1f-b214-d1af27a62960)

2. I also noticed another problem when I cleared the project cache to reduce its size, after deleting the .godot folder and all .import files, the lighting looked like this on 4.3 and 4.4:
![2](https://github.com/user-attachments/assets/f0b5e33b-c4ab-41d5-984a-da3f501a8be3)





### Steps to reproduce

1. Open MRP on 4.3 to check lighting
2. Now open it on 4.4 (Lighting is broken)
3. Delete project cache and open project again (Another lighting breakage)

### Minimal reproduction project (MRP)

[prj.zip](https://github.com/user-attachments/files/17759024/prj.zip) - 14.1 mb
Repository: pytorch
Issue: KeyError in default_cache_dir() when user account doesn't exist
Labels: triaged,oncall: pt2,module: inductor

### 🐛 Describe the bug

The `torch._inductor` package creates a cache directory. If the `TORCHINDUCTOR_CACHE_DIR` env variable is not set, it defaults to `/tmp/torchinductor_{username}`, where `username` is determined from the python standard library `getpass.getuser()` function.

This function raises a `KeyError` if the user account does not exist. This is a common situation in production deployments where containers are often forced to run as an ordinary user for security reasons, but the user account isn't created in the container with `useradd` or similar.

It would be helpful to fall back to `/tmp/torchinductor` or whatever if getting the user name fails. The username part doesn't seem especially necessary, since I don't imagine that "multiple users on a shared machine" is the most common usage context.

Setting `TORCHINDUCTOR_CACHE_DIR` does work around the problem.

### Error logs

``` 
File "/usr/local/lib/python3.12/dist-packages/torch/_inductor/runtime/runtime_utils.py", line 137, in cache_dir
    sanitized_username = re.sub(r'[\\/:*?"<>|]', "_", getpass.getuser())
                                                      ^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/getpass.py", line 169, in getuser
    return pwd.getpwuid(os.getuid())[0]
           ^^^^^^^^^^^^^^^^^^^^^^^^^
torch._dynamo.exc.BackendCompilerFailed: backend='inductor' raised:
KeyError: 'getpwuid(): uid not found: 1001'
```

### Versions

Unable to run in production config, but the problematic code is present in `main` currently:
https://github.com/pytorch/pytorch/blob/e90888a93d9ebda9978b2828640a9372388dd74a/torch/_inductor/runtime/cache_dir_utils.py#L18-L23

cc @ezyang @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire @aakhundov
Repository: storybook
Issue: [Bug]: bare import path resolution doesn't work under Yarn PNPM linker
Labels: bug,help wanted,core,pnpm,yarn

### Describe the bug

SB attempts to strip all leading `node_modules/` components off of the path of an import to get Vite to bundle correctly:
https://github.com/storybookjs/storybook/blob/33e439766251689d3b30be4f532d44294a023c16/code/core/src/common/utils/strip-abs-node-modules-path.ts#L9-L17

This doesn't work correctly under the Yarn [PNPM linker](https://yarnpkg.com/features/linkers#nodelinker-pnpm), which constructs a `node_modules` tree via symlinks into a `node_modules/.store` directory. So, all packages are stored under `/node_modules/.store/<packagename>-virtual-<hash>/package/`, and `require.resolve` will return absolute paths into here. Thus, `stripAbsNodeModulesPath` is called since `node_modules` is in the path, and ti will return a path like `.store/...`, which is not a valid import path. Vite then throws errors about these paths:
```
3:37:05 PM [vite] Pre-transform error: Failed to resolve import ".store/@storybook-react-virtual-d2ec5c3452/package/dist/entry-preview.mjs" from "/virtual:/@storybook/builder-vite/vite-app.js". Does the file exist?
3:37:05 PM [vite] Internal server error: Failed to resolve import ".store/@storybook-react-virtual-d2ec5c3452/package/dist/entry-preview.mjs" from "/virtual:/@storybook/builder-vite/vite-app.js". Does the file exist?
  Plugin: vite:import-analysis
  File: /virtual:/@storybook/builder-vite/vite-app.js:7:81
  5  |      
  6  |    const getProjectAnnotations = async (hmrPreviewAnnotationModules = []) => {
  7  |      const configs = await Promise.all([hmrPreviewAnnotationModules[0] ?? import('.store/@storybook-react-virtual-d2ec5c3452/package/dist/entry-preview.mjs'),
     |                                                                                  ^
  8  |  hmrPreviewAnnotationModules[1] ?? import('.store/@storybook-react-virtual-d2ec5c3452/package/dist/entry-preview-docs.mjs'),
```

### Reproduction link

https://github.com/ethanwu10/sb-yarn-pnpm-vite-repro

### Reproduction steps

1. Clone repro
2. Run `yarn storybook`
3. Observe errors from Vite + storybook iframe does not load

### System

```bash
System:
    OS: macOS 14.7
    CPU: (10) arm64 Apple M2 Pro
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 23.1.0 - /private/var/folders/44/y4hzbjt52nv8ddgrvy_p85g00000gn/T/xfs-d59be415/node
    Yarn: 4.5.1 - /private/var/folders/44/y4hzbjt52nv8ddgrvy_p85g00000gn/T/xfs-d59be415/yarn <----- active
    npm: 10.9.0 - /opt/homebrew/bin/npm
  Browsers:
    Safari: 18.0
  npmPackages:
    @storybook/addon-essentials: ^8.4.4 => 8.4.4 
    @storybook/addon-interactions: ^8.4.4 => 8.4.4 
    @storybook/addon-onboarding: ^8.4.4 => 8.4.4 
    @storybook/blocks: ^8.4.4 => 8.4.4 
    @storybook/react: ^8.4.4 => 8.4.4 
    @storybook/react-vite: ^8.4.4 => 8.4.4 
    @storybook/test: ^8.4.4 => 8.4.4 
    eslint-plugin-storybook: ^0.11.0 => 0.11.0 
    storybook: ^8.4.4 => 8.4.4
```

### Additional context

_No response_
Repository: PowerToys
Issue: Bug: Inconsistent Window Focus Switching with Win + PageUp/Down in FancyZones
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.86.0

### Installation method

Microsoft Store

### Running as admin

No

### Area(s) with issue?

FancyZones

### Steps to reproduce

1. Create 1 layout with 2 or more zones.
2. Open two or more windows in the same zone.
3. Minimize one of the windows.
4. Click on the window that remains visible in the zone.
5. Use the shortcuts **Win + PageUp** and **Win + PageDown** to see the focus bug.

If this is not enough to reproduce the issue, try:
1. Open Discord in one of the zones.
2. Minimize or close Discord.
3. Use the shortcuts **Win + PageUp** and **Win + PageDown**.

### ✔️ Expected Behavior

- Pressing **Win + PageUp** and **Win + PageDown** should cycle through the windows in each zone smoothly.
- Windows should gain focus and be brought to the front as they are selected.

### ❌ Actual Behavior

- Inconsistent behavior between zones:
    - Sometimes, windows lose focus and are not brought to the front.
    - This issue occurs randomly in any of the zones.
    - Repeating the command multiple times sometimes brings the window to the front, but not consistently.
Repository: react-native
Issue: [0.76] `KeyboardAvoidingView` animation issues since 0.76+ upgrade
Labels: Issue: Author Provided Repro,Impact: Regression,Component: KeyboardAvoidingView,API: Keyboard,Newer Patch Available,Needs: Attention

### Description

I've updated my project from 0.75.2 to 0.76.1 this morning, and I noticed that the `KeyboardAvoidingView`, which was previously animating properly, is no longer animating. It now jumps and doesn't follow the keyboard animation.

Not sure why in my project it doesn't work, but while creating the reproduction repo, I noticed the animation behaviour has changed and doesn't look native smooth anymore. 

### Steps to reproduce

Any new project with KeyboardAvoidingView

### React Native Version

0.76.1

### Affected Platforms

Runtime - iOS

### Output of `npx react-native info`

```text
System:
  OS: macOS 15.2
  CPU: (10) arm64 Apple M1 Pro
  Memory: 157.52 MB / 16.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 22.11.0
    path: ~/.nvm/versions/node/v22.11.0/bin/node
  Yarn:
    version: 1.22.17
    path: ~/.npm-global/bin/yarn
  npm:
    version: 10.9.0
    path: ~/.nvm/versions/node/v22.11.0/bin/npm
  Watchman:
    version: 2024.01.22.00
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.15.2
    path: /Users/Alexis/.rbenv/shims/pod
```


### Stacktrace or Logs

```text
No crash
```


### Reproducer

https://github.com/alexmngn/reproducer-react-native-keyboard-avoiding

### Screenshots and Videos

### On my project

**Before update, 0.75.2**

https://github.com/user-attachments/assets/5089cd4d-fb2f-4bde-9a9b-a7790b989c23

**After update, 0.76.1**

https://github.com/user-attachments/assets/60bc6d95-c444-4492-887b-cdb7d4e562d1


### On the reproducer repo

**Before update, 0.75.2**

https://github.com/user-attachments/assets/83df6cab-b4c4-4698-a458-291ab37f982c

**After update, 0.76.1**

https://github.com/user-attachments/assets/8fa6d39c-88af-4527-b41c-d7ae2bc8e7a2
Repository: go
Issue: cmd/compile: TestScript/script_test_basics failures
Labels: help wanted,OS-NetBSD,NeedsInvestigation,arch-arm64,compiler/runtime

```
#!watchflakes
default <- pkg == "cmd/compile" && test == "TestScript/script_test_basics"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8731270051656900545)):

    === RUN   TestScript/script_test_basics
    === PAUSE TestScript/script_test_basics
    === CONT  TestScript/script_test_basics
        run.go:223: 2024-11-14T20:19:02Z
        run.go:225: $WORK=/home/swarming/.swarming/w/ir/x/t/TestScriptscript_test_basics3024012314/001
        run.go:232: 
            BOTO_CONFIG=/home/swarming/.swarming/w/ir/x/a/gsutil-bbagent/.boto
            CIPD_ARCHITECTURE=arm64
            CIPD_CACHE_DIR=/home/swarming/.swarming/w/ir/cache/cipd_cache
            CIPD_PROTOCOL=v2
    ...
            WORK=/home/swarming/.swarming/w/ir/x/t/TestScriptscript_test_basics3024012314/001
            TMPDIR=/home/swarming/.swarming/w/ir/x/t/TestScriptscript_test_basics3024012314/001/tmp
            
            # Test of the linker's script test harness. (21.847s)
            > go build
            > [!cgo] skip
            [condition not met]
            > cc -c testdata/mumble.c
        run.go:232: FAIL: testdata/script/script_test_basics.txt:6: cc -c testdata/mumble.c: exec: WaitDelay expired before I/O complete
    --- FAIL: TestScript/script_test_basics (21.87s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: net: TestUDPServer/0 failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "net" && test == "TestUDPServer/0"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8731256705775492193)):

    === RUN   TestUDPServer/0
        server_test.go:258: udp :0<-127.0.0.1
        server_test.go:315: client: read udp 127.0.0.1:51784: i/o timeout
        server_test.go:322: server: read udp [::]:62172: i/o timeout
    --- FAIL: TestUDPServer/0 (3600.00s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: ui
Issue: [bug]: npx shdnc@latest url stuck at "Installing dependencies"
Labels: bug

### Describe the bug

When I run npx shdnc@latest url, the process gets stuck at the "Installing dependencies" step and does not proceed

### Affected component/components

Cannot install any component using the cli

### How to reproduce

Run npx shadcn@latest add "https://v0.dev/chat/b/b_wslkIiIMLhs?token=eyJhbGciOiJkaXIiLCJlbmMiOiJBMjU2R0NNIn0..pt0lLMnobX0YxVIb._Fh59fncD8EAU8BlmQgAaC25DK0KqCgq4R86zw28bkXG-Hrg83lQmkIynis.I42dFW87PMfK4Fq5j_Ht5g"

Observe that the process stalls at "Installing dependencies."

### Codesandbox/StackBlitz link

_No response_

### Logs

```bash
Checking registry.
Installing dependencies
```


### System Info

```bash
Ubuntu 24.04
node v22.11.0
bun 1.1.34
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: ui
Issue: [bug]: Dropdown Menu using wrong icons
Labels: bug

### Describe the bug

It looks like the new york style was recently updated to use lucide icons, but DropDownMenu is trying to use radix icons when installed with cli.

I changed
`import { CheckIcon, ChevronRightIcon, DotFilledIcon } from "@radix-ui/react-icons"`
to 
`import { CheckIcon, ChevronRightIcon, CircleIcon } from "lucide-react"`
and changed the single usage of `DotFilledIcon` to `CircleIcon`.

### Affected component/components

Dropdown Menu

### How to reproduce

**EDIT: This repro is incorrect, see next issue comment**

- init shadcn using new york style
- `npx shadcn@latest add dropdown-menu`

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Windows 11
Powershell 7
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: rust
Issue: Add a run-make test that checks our `core::ffi::c_*` types against Clang
Labels: A-testsuite,E-hard,A-FFI,E-needs-test,T-libs,E-needs-design

It would be good to have a test that our C interop types are always compatible with C (`c_char`, `c_long`, `c_longlong` all vary to some extent). This will more or less be what @taiki-e did at https://github.com/rust-lang/rust/issues/129945, just rolled into a run-make test rather than a shell script.

The test will basically need to do the following:

1. Loop through each target string in the output of `rustc --print target-list`
2. Map the rust target to a LLVM target if they aren't the same
3. Loop through a list of each `c_*` type available in `core::ffi`
4. Query `clang -E -dM -x c /dev/null -target LLVM_TARGET` to get a list of builtin definitions. Of note will be something like the following (comments added by me)
    
    ```c
    #define __CHAR_BIT__ 8 // c_char
    #define __CHAR_UNSIGNED__ 1 // char signedness
    
    #define __SIZEOF_DOUBLE__ 8 // c_double
    #define __SIZEOF_FLOAT__ 4 // c_float
    #define __SIZEOF_INT__ 4 // c_int
    #define __SIZEOF_LONG_DOUBLE__ 16 // c_longdouble
    #define __SIZEOF_LONG_LONG__ 8 // c_longlong
    #define __SIZEOF_LONG__ 4 // c_long
    #define __SIZEOF_POINTER__ 4 // *const c_void
    #define __SIZEOF_PTRDIFF_T__ 4 // c_ptrdiff_t
    #define __SIZEOF_SHORT__ 2 // c_short
    #define __SIZEOF_SIZE_T__ 4 // c_size_t
    
    #define __BOOL_WIDTH__ 8 // bool
    #define __INTPTR_WIDTH__ 32 // isize
    #define __INT_WIDTH__ 32 // c_int
    #define __LLONG_WIDTH__ 64 // c_longlong
    #define __LONG_WIDTH__ 32 // c_long
    #define __POINTER_WIDTH__ 32 // *const c_void
    #define __PTRDIFF_WIDTH__ 32 // c_ptrdiff_t
    #define __SHRT_WIDTH__ 16 // c_short
    #define __SIZE_WIDTH__ 32 // c_size_t
    #define __UINTPTR_WIDTH__ 32 // usize
    ```
5. Use the above to construct a simple Rust program that can verify the sizes and (when applicable) signedness line up at compile time. Probably do an assignment that will catch mismatched types plus a const assert for anything that doesn't have literals.

    ```rust
    // input to check `c_short`
    const C_SHORT: u{c_sizeof_short} = 0;
    const RUST_SHORT: core::ffi::c_short = C_SHORT;

   ```rust
    // input to check pointer width
    const _: () = assert!(size_of::<*const core::ffi::c_void>() * 8 == {c_pointer_width});
    ```
6. Run `rustc -Z no-codegen` and check success/failure against a list of xfail targets.

`run_make_support` has [`clang`](https://doc.rust-lang.org/nightly/nightly-rustc/run_make_support/external_deps/clang/index.html) available, example usage: https://github.com/rust-lang/rust/blob/e84902d35a4d3039c794e139eb12fba3624c5ff1/tests/run-make/cross-lang-lto-clang/rmake.rs. There is probably some way we could check this on MSVC targets too.

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"ricci009"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: PowerToys
Issue: Always On Top does not work for some applications
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.85.1

### Installation method

GitHub

### Running as admin

Yes

### Area(s) with issue?

Always on Top

### Steps to reproduce

Always On Top feature does not work for some applications

1. MobaXTerm
2. VMWare Workstation
3. Netcam Studio X

Is it because of the MDI window implementation? Any workaround btw? This drives me nuts cos its nearly perfect

### ✔️ Expected Behavior

Support for these apps described above

### ❌ Actual Behavior

-

### Other Software

1. MobaXTerm
2. VMWare Workstation
3. Netcam Studio X
Repository: godot
Issue: Engine supports multiple translation objects per locale but `TranslationServer.get_translation_object` is only capable of fetching one
Labels: discussion,topic:gui

### Tested versions

Reproducible in 4.3.stable

### System information

Godot v4.3.stable - Windows 10.0.22631 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1660 SUPER (NVIDIA; 32.0.15.6603) - Intel(R) Core(TM) i7-10700F CPU @ 2.90GHz (16 Threads)

### Issue description

The engine supports adding multiple translation objects per locale, but `TranslationServer.get_translation_object` is only capable of fetching one of them. For example, from the project settings, you can add one file for Spanish UI translations, and another one for Spanish dialog translations. Both of these translation resources will work, and provide translations properly in the game. However, if you call `TranslationServer.get_translation_object("es")`, you will only get back one of them. The other will not be accessible at all.

If the intended usage is that you should only have one translation object per locale, then the project settings UI should reflect and enforce this. If it is intended that multiple are allowed, then the API for `TranslationServer` should support fetching *all* translation objects for a locale, or at least fetch the entire list of translation objects.

### Steps to reproduce

See above.

### Minimal reproduction project (MRP)

N/A. See above.