sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: react-native
Issue: multiline TextInput does not render value properly with newline characters
Labels: Issue: Author Provided Repro,Component: TextInput

### Description

Unstyled `TextInput` in a `SafeAreaView` has some strange behaviour when it's `value` prop contains new line characters.
The text seems to clip under the first line break and does not appear before tapping the text input box.

Some considerations:
- Does not happen for long text that breaks "naturally" (no line breaks)
- I can't reproduce this using a normal view and not a safe area view
  - Wrapping the text input in a view does not fix the issue as long as there exists a parent SafeAreaView 
- I can't reproduce this in the iOS simulator using Expo Snack (SDK 49.0.0)
- `alignSelf: "flex-start"` seems to fix the issue

### Steps to reproduce

1. clone the reproducer repo
2. install and initialize:
```shell
yarn install
cd ios
pod install
```
3. run according to docs:
```shell
yarn start
yarn run ios
```

4. Observe the text clipping after two lines. Tap the text to make the rest of it appear. Reload to make it appear again.


### React Native Version

0.73.1

### Affected Platforms

Runtime - iOS, Build - MacOS

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

```text
System:
  OS: macOS 14.1.1
  CPU: (10) arm64 Apple M1 Pro
  Memory: 3.85 GB / 32.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 18.18.2
    path: ~/.nvm/versions/node/v18.18.2/bin/node
  Yarn:
    version: 1.22.19
    path: ~/.nvm/versions/node/v18.18.2/bin/yarn
  npm:
    version: 9.8.1
    path: ~/.nvm/versions/node/v18.18.2/bin/npm
  Watchman:
    version: 2023.10.09.00
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.13.0
    path: /opt/homebrew/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.0
      - iOS 17.0
      - macOS 14.0
      - tvOS 17.0
      - watchOS 10.0
  Android SDK: Not Found
IDEs:
  Android Studio: Not Found
  Xcode:
    version: 15.0.1/15A507
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 11.0.12
    path: /usr/bin/javac
  Ruby:
    version: 2.6.10
    path: /usr/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react: Not Found
  react-native: Not Found
  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 relevant stacktrace
```


### Reproducer

https://github.com/HaakonSvane/TextInputBug

### Screenshots and Videos

https://github.com/facebook/react-native/assets/36899138/d0caa3ff-425c-4ee5-bf41-49e4e550736b

(I added red background color to the safe area view to better visualize the element size before and after text appears. There seems to be no apparent change)
Repository: PowerToys
Issue: Latest version unable to launch - Application error in event log - faulting module microsoft.ui.xaml.dll
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.76.2

### Installation method

GitHub, PowerToys auto-update, Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

General, Settings

### Steps to reproduce

Right click icon in tray click on settings - application crash logged in event viewer
Report bug attached
[PowerToysReport_2024-01-04-15-16-21.zip](https://github.com/microsoft/PowerToys/files/13832025/PowerToysReport_2024-01-04-15-16-21.zip)


### ✔️ Expected Behavior

Settings to open

### ❌ Actual Behavior

Application crashed after briefly displaying window border

### Other Software

_No response_
Repository: godot
Issue: VisibleOnScreenNotifier2D will use its position(but not only use its Rect.Position ) to check visible
Labels: bug,topic:rendering,topic:2d

### Tested versions

4.2.stable.mono

### System information

Godot v4.2.stable.mono - Windows 10.0.23606 - Vulkan (Mobile) - dedicated NVIDIA GeForce RTX 3080 Laptop GPU (NVIDIA; 31.0.15.3734) - AMD Ryzen 9 5900HX with Radeon Graphics (16 Threads)

### Issue description

VisibleOnScreenNotifier2D will use its position(but not only use its Rect.Position ) to check visible.(It probably happen in the SceenEntered signal)

When its node's Position is different from its Rect.Position, it will check visible use the node's Position and its Rect.Position, this is something wired.

When I set its Rect.Position same as the node's Position, the node works correcttly, as its Rect not visible, the ScreenExited signal will be emited, its Rect visible, the ScreenEntered signal will be emited.

But when its node's Position is different from its Rect.Position, the Rect not visible, the ScreenExited signal will be emited correcttly, 
but the ScreenEntered signal will also be emited when its node's Position is on screen and the Rect not on screen.

### Steps to reproduce

---

### Minimal reproduction project (MRP)

---
Repository: ollama
Issue: Simpler UI / CLI for predicting model performance on user's device?
Labels: feature request

Hi, I was wondering if the current Ollama system grabs any system information regarding CPU and RAM capacities. Especially since a majority of users are on Mac, there's a finite # of hardware specs for Ollama to recognize. Then, Ollama can automatically recommend which models will run best on the user's Mac. 

I think this would be easier for first-time users, and promote Ollama's accessibility for non-technicals (average MacOS users). 

If this doesn't exist, I would be more than happy to make a branch with my suggestion. If the underlying CLI/code to recognize device GPU/CPU limitations already exists, I'd love to take a stab at incorporating it into the UI. I'd appreciate any direction for which part of the codebase to observe.
Repository: godot
Issue: SoftBody3D prevents scene from loading if Physics set to Run on Separate Thread
Labels: bug,topic:physics,crash,topic:3d

### Tested versions

v4.2.1.stable.official [b09f793f5]

### System information

Godot v4.2.1.stable - Ubuntu 22.04.3 LTS 22.04 - X11 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3080 Ti (nvidia; 535.129.03) - AMD Ryzen Threadripper 2950X 16-Core Processor (32 Threads)

### Issue description

As title suggests, having softbody3d with separate physics thread causes godot to crash. The MRP crashes quickly, however in the project I originally discovered this, the run would stall forcing me to `kill` the proc. Console output from MRP captured below:

```
christopwner@desktop:/opt/godot$  
Godot Engine v4.2.1.stable.official.b09f793f5 - https://godotengine.org
Vulkan API 1.3.242 - Forward+ - Using Vulkan Device #0: NVIDIA - NVIDIA GeForce RTX 3080 Ti
 
ERROR: Caller thread can't call this function in this node (/root). Use call_deferred() or call_thread_group() instead.
   at: propagate_notification (scene/main/node.cpp:2236)

================================================================
handle_crash: Program crashed with signal 11
Engine version: Godot Engine v4.2.1.stable.official (b09f793f564a6c95dc76acc654b390e68441bd01)
Dumping the backtrace. Please include this when reporting the bug to the project developer.
[1] /lib/x86_64-linux-gnu/libc.so.6(+0x42520) [0x7f70db909520] (??:0)
[2] /opt/godot/Godot_v4.2.1-stable_linux.x86_64() [0x26113b7] (??:0)
[3] /opt/godot/Godot_v4.2.1-stable_linux.x86_64() [0x2fd0741] (??:0)
[4] /opt/godot/Godot_v4.2.1-stable_linux.x86_64() [0x34af01b] (??:0)
[5] /opt/godot/Godot_v4.2.1-stable_linux.x86_64() [0x373cb85] (??:0)
[6] /opt/godot/Godot_v4.2.1-stable_linux.x86_64() [0x42b87a3] (??:0)
[7] /lib/x86_64-linux-gnu/libc.so.6(+0x94ac3) [0x7f70db95bac3] (??:0)
[8] /lib/x86_64-linux-gnu/libc.so.6(+0x126660) [0x7f70db9ed660] (??:0)
-- END OF BACKTRACE --
================================================================
```

### Steps to reproduce

* create 3d scene
* add softbody3d node
* create boxmesh in mesh slot for softbody3d
* in project settings, click advanced settings, then turn on physics/3d -> run on separate thread
* run scene

### Minimal reproduction project (MRP)

[softbody3d-separate-thread.zip](https://github.com/godotengine/godot/files/13832569/softbody3d-separate-thread.zip)
Repository: vscode
Issue: Minimap view state
Labels: bug,editor-minimap


Type: <b>Bug</b>

Greetings,
when you right-click on the minimap view within a source code file (e.g. a .cpp file) and then click on the mimap entry in its context menu, the minimap disappears correctly. But if you then decide to open the View/Appearance menu, you'll notice that the minimap item remains selected.

VS Code version: Code 1.85.1 (0ee08df0cf4527e40edc9aa28f4b5bd38bbff2b2, 2023-12-13T09:49:37.021Z)
OS version: Windows_NT x64 10.0.19045
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i5-3337U CPU @ 1.80GHz (4 x 1796)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: disabled_off<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: unavailable_off<br>raw_draw: disabled_off_ok<br>video_decode: enabled<br>video_encode: unavailable_off<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled|
|Load (avg)|undefined|
|Memory (System)|11.89GB (4.78GB free)|
|Process Argv|--crash-reporter-id 898939e8-9b23-499a-a5cb-c5ce01e5d2b3|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (10)</summary>

Extension|Author (truncated)|Version
---|---|---
Bookmarks|ale|13.4.2
todo-tree|Gru|0.0.226
cpptools|ms-|1.19.1
cpptools-extension-pack|ms-|1.3.0
powershell|ms-|2023.8.0
mq4|ner|1.0.4
mql-extension-pack|nic|0.0.4
mql-over-cpp|nic|0.0.3
mql-snippets|nic|0.1.2
material-icon-theme|PKi|4.32.0

(1 theme extensions excluded)

</details><details>
<summary>A/B Experiments</summary>

```
vsliv368cf:30146710
vsreu685:30147344
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242:30382549
vsjup518:30340749
vshan820:30294714
vscoreces:30445986
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
py29gd2263:30899288
vsclangdc:30486549
c4g48928:30535728
dsvsc012cf:30540253
azure-dev_surveyonecf:30548226
89544117:30613380
pythongtdpath:30769146
i26e3531:30792625
welcomedialogc:30910334
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
dsvsc013:30795093
dsvsc014:30804076
dsvsc015:30845448
pythontestfixt:30902429
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
h48ei257:30885898
pythontbext0:30879054
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
aa_t_chat:30882232
dsvsc019:30917259
cp7184t3:30927821

```

</details>

<!-- generated by issue reporter -->
Repository: flutter
Issue: Make SnackBar floating by default
Labels: c: new feature,f: material design,c: proposal,P3,team-design,triaged-design

### Use case

In Material 3 the `SnackBar` is floating by default. But I'm Flutter it's not, Although material 3 is now preset.

### Proposal

Make the behavior of SnackBar in Flutter floating by default.
Repository: PowerToys
Issue: Doing an alternate Desktop the RIGHT way.
Labels: Needs-Triage

### Description of the new feature / enhancement

I tried to add a second desktop to my Windows 11 computer the other day and found out that it would only contain the applications that were active at the time I created the desktop.  It would be nice to be able to cut and paste the data files and folders that I needed on the new desktop as well. There doesn't seem to be a way to do that currently. Honestly, it seems like the easiest way would just be to select the files, folders, and shortcuts on my original desktop and paste them into a new desktop.  This would be a lot simpler than doing it the way Microsoft has implemented this feature.

### Scenario when this would be used?

My current desktop has a huge number of files, folders and shortcuts. I find that I am slowly filling up my desktop with these items. It would be nice to have desktops that are oriented towards specific projects or applications. I believe this was Microsoft's intention when they created this feature.

### Supporting information

I have seen many people that, over time, fill up their desktops with too many files and folders. Being able to cut and paste files and folders from an old desktop into a new one is something that everyone could understand and use.
Repository: tensorflow
Issue: Need MPMD supporting for GPU to use pipeline parallelism training large scale model
Labels: stat:awaiting tensorflower,type:feature,comp:dist-strat,TF 2.15

### Issue type

Feature Request

### Have you reproduced the bug with TensorFlow Nightly?

Yes

### Source

binary

### TensorFlow version

tf 2.15

### Custom code

No

### OS platform and distribution

_No response_

### Mobile device

_No response_

### Python version

_No response_

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

Nowadays pipeline parallelism has been implemented in PyTorch for a long time. It's very useful for training a CTR model with Embedding pipeline or training a large language model between two machine.

### Standalone code to reproduce the issue

```shell
Maybe a easy send/recv construction like tpu with xla?
```


### Relevant log output

_No response_
Repository: next.js
Issue: Error thrown in middleware causes `res.statusCode` to be incorrectly set to 404
Labels: bug,Runtime

### Link to the code that reproduces this issue

https://github.com/joekur/next-bug-middleware-error-404

### To Reproduce

1. Run `npm run dev`
2. Access `localhost:3000`
3. Expectedly, you will see an error thrown from the middleware
4. See the stdout logs reported from the custom server - the response status (`res.statusCode`) will show `404`, even though the response as seen by the client/browser is `500`

Example: `Request completed: 404 Internal Server Error - GET /`
![Screenshot 2024-01-04 at 11 46 38 AM](https://github.com/vercel/next.js/assets/1043396/2b9fe99b-2357-4f7e-ac10-4e071c01b92f)


### Current vs. Expected behavior

If an error is thrown from middleware, this results in a 500 error page returned in the response, as expected.

However, when you look at `res.statusCode` within a custom server, after running `await handle()` ([example code](https://github.com/joekur/next-bug-middleware-error-404/blob/4ed3b84f11f0b99407c17d5270da4ce37b4e4c1b/server.ts#L15-L17)), it is set to `404`, whereas I would expect `500`, to match what was returned in the actual response. `res.statusMessage` is still `Internal Server Error` as expected, although this of course does not match with a `404`.

This results in inaccurate logging and APM (datadog) when used with a custom server.

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.1.0: Mon Oct  9 21:28:45 PDT 2023; root:xnu-10002.41.9~6/RELEASE_ARM64_T6020
Binaries:
  Node: 20.4.0
  npm: 9.7.2
  Yarn: 1.22.19
  pnpm: 8.6.5
Relevant Packages:
  next: 14.0.5-canary.38
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.1.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Middleware / Edge (API routes, runtime)

### Which stage(s) are affected? (Select all that apply)

next dev (local), next start (local), Other (Deployed)

### Additional context

Note: this can be reproduced locally (`next dev` and `next build`/`next start`). In production, I have verified this happens for middleware run in a Node environment - I'm not sure what happens on Vercel/edge.
Repository: electron
Issue: [Bug]: BrowserWindow.getPosition() returns [0, 0] on Wayland
Labels: platform/linux,bug :beetle:,component/BrowserWindow,wayland,28-x-y

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a bug report that matches the one I want to file, without success.

### Electron Version

28.1.1

### What operating system are you using?

Other Linux

### Operating System Version

Arch Linux with Sway WM (Wayland)

### What arch are you using?

x64

### Last Known Working Electron version

_No response_

### Expected Behavior

The `BrowserWindow.getPosition()` should return the window position on any oS.

### Actual Behavior

When starting the application with Wayland support (i.e. `--ozone-platform-hint=auto --enable-features="WaylandWindowDecorations"`), the position returned is always `[0, 0]`.

Bug reproduced both with Electron 28.1.1 and with 29.0.0-alpha.6.

### Testcase Gist URL

https://gist.github.com/threema-danilo/066f28235a408323a460966da82c7f3b

### Additional Information

Load and start the Electron Fiddle and look at the console. The position is printed every second.

If you start the fiddle without any parameters (defaulting to X), the position is correct.

![screenshot-20240104-180424](https://github.com/electron/electron/assets/78751145/4bc6e09b-65cf-42cd-b5f3-6b9f93a16257)

If you start the fiddle with Wayland support (Settings > Execution, see screenshot below), the position is always [0, 0].

![screenshot-20240104-180311](https://github.com/electron/electron/assets/78751145/724c191f-94b0-432a-b118-af905df923bc)

![screenshot-20240104-180356](https://github.com/electron/electron/assets/78751145/14c7ede3-198d-408a-906b-b615d3a5e3da)
Repository: go
Issue: x/crypto/ssh/test: tests fail on macOS 14
Labels: OS-Darwin,NeedsInvestigation

```
=== RUN   TestAgentForward
    exec.go:88: test timed out while running command: /usr/sbin/sshd -f /Users/swarming/.swarming/w/ir/x/t/sshtest3423651030/sshd_config -i -e
panic: test timed out after 10m0s
running tests:
	TestAgentForward (10m0s)
[...]
```

See https://ci.chromium.org/ui/p/golang/builders/ci/x_crypto-gotip-darwin-amd64-longtest/b8759816251100556177/test-results for full details.

It doesn't seem to reproduce for me locally:

```
$ go test -v ./ssh/test -run=^TestAgentForward$ 
=== RUN   TestAgentForward
--- PASS: TestAgentForward (0.79s)
PASS
ok  	golang.org/x/crypto/ssh/test	1.355s
```

Nor on the old dashboard, though it's hard to be sure whether this test is running or being skipped there.

This failure is blocking the automated monthly tagging workflow, so adding Soon label. If this ends up taking a while to figure out and fix, we might want to temporarily skip the test since it's happening since the builder was added in LUCI, to unblock the rest of the tagging.

CC @drakkan, @golang/security, @prattmic.
Repository: TypeScript
Issue: Avoid using just color to distinguish markers in type compatibility chart (WCAG 1.4.1)
Labels: Website

### Acknowledgement

- [X] I acknowledge that issues using this template may be closed without further explanation at the maintainer's discretion.

### Comment

In the handbook section [`any`, `unknown`, `object`, `void`, `undefined`, `null`, and `never` assignability](https://www.typescriptlang.org/docs/handbook/type-compatibility.html#any-unknown-object-void-undefined-null-and-never-assignability), the chart uses **just** color to differentiate checkmarks:

1. A blue `✓` (class `blue-tick`) for a combination that's assignable regardless of `strictNullChecks`
2. A green `✓` (class `black-tick` [sic]) for a combination that's only assignable when `strictNullChecks` is off
3. A lighter blue `✓` (via inline style) for the intersection of `any` and `unknown`

It's really subtle and hard to see even with "normal" color vision, let alone for people with color blindness. (People who are red-green color blind -- the most common kind -- *"...tend to confuse purple, blue, green, orange, and red...."* [source](https://www.typescriptlang.org/docs/handbook/type-compatibility.html#any-unknown-object-void-undefined-null-and-never-assignability).) See also [WCAG Success Criterion 1.4.1](https://www.w3.org/WAI/WCAG21/Understanding/use-of-color.html): *"Color is not used as the only visual means of conveying information..."*

For (2) above, I suggest using a different marker entirely, perhaps one of: `*` `†` `‡` `○`. Or alternatively, perhaps a combination like `✓?` or `✓‡`. (The text above explaining about the special checkmarks would also need to be changed to match.)

For (3) above, the text doesn't call out why that intersection is different from others, so I suggest the inline style could just be removed. If the distinction is important, though, it could be another marker.
Repository: vscode
Issue: Cannot read properties of undefined (reading 'element')
Labels: error-telemetry

```javascript
TypeError: Cannot read properties of undefined (reading 'element')
at b.element in src/vs/base/browser/ui/list/listView.ts:780:28
at <anonymous> in src/vs/base/browser/ui/list/listWidget.ts:244:98
at Array.map (<anonymous>)
at b.splice in src/vs/base/browser/ui/list/listWidget.ts:244:50
at <anonymous> in src/vs/base/browser/ui/list/splice.ts:17:35
at Array.forEach (<anonymous>)
at t.splice in src/vs/base/browser/ui/list/splice.ts:17:20
at <anonymous> in src/vs/base/browser/ui/list/listWidget.ts:1550:57
at fn in src/vs/base/common/event.ts:1576:13
at X.splice in src/vs/base/browser/ui/list/listWidget.ts:1550:22
at X.splice in src/vs/base/browser/ui/tree/abstractTree.ts:1901:9
at Object.splice in src/vs/base/browser/ui/tree/compressedObjectTreeModel.ts:390:9
at g.s in src/vs/base/browser/ui/tree/indexTreeModel.ts:306:14
at g.splice in src/vs/base/browser/ui/tree/indexTreeModel.ts:157:9
at D.l in src/vs/base/browser/ui/tree/objectTreeModel.ts:122:14
at D.setChildren in src/vs/base/browser/ui/tree/objectTreeModel.ts:71:8
at h.i in src/vs/base/browser/ui/tree/compressedObjectTreeModel.ts:238:14
at h.setChildren in src/vs/base/browser/ui/tree/compressedObjectTreeModel.ts:156:9
at d.setChildren in src/vs/base/browser/ui/tree/compressedObjectTreeModel.ts:467:14
at k.setChildren in src/vs/base/browser/ui/tree/objectTree.ts:208:14
at ce.I in src/vs/base/browser/ui/tree/asyncDataTree.ts:1024:13
at ce.I in src/vs/base/browser/ui/tree/asyncDataTree.ts:1311:9
at ce.B in src/vs/base/browser/ui/tree/asyncDataTree.ts:789:8
at async ce.z in src/vs/base/browser/ui/tree/asyncDataTree.ts:549:3
at async ce.setInput in src/vs/base/browser/ui/tree/asyncDataTree.ts:522:3
```
[Go to Errors Site](https://errors.code.visualstudio.com/card?ch=0ee08df0cf4527e40edc9aa28f4b5bd38bbff2b2&bH=429bc535-9255-7055-5874-51b265942fea)
Repository: PowerToys
Issue: Can powertoys be run programatically, e.g. from CMD?
Labels: Idea-Enhancement

### Description of the new feature / enhancement

Is it possible to run a powertoy programatically rather than using the keyboard shortcuts, e.g. by running `"%LOCALAPPDATA%\PowerToys\PowerToys.ColorPickerUI.exe"` to launch the Color Picker, or something like `"%LOCALAPPDATA%\PowerToys\WinUI3Apps\PowerToys.FileLocksmithUI.exe" "C:\ExampleTargetFile.dll"` to run the Locksmith utility on some target file?

If it's not currently possible, could this functionality be added?

### Scenario when this would be used?

Automation scenarios, better integration into other utilities, more poweruser flexibility in general (e.g. users could create a desktop shortcut to launch a utility, run a utility as a scheduled task, integrate a utility into an AutoHotKey script without having to worry about sending keypresses, etc.)