sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: PopupMenu with prefer_native_menu=true locks focus on last focused node on MacOS
Labels: bug,platform:macos,topic:gui

### Tested versions

v4.3.stable.mono.official [77dcf97d8]

### System information

Godot v4.3.stable.mono - macOS 15.1.1 - Vulkan (Forward+) - dedicated AMD Radeon Pro 5500M - Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz (16 Threads)

### Issue description

When setting up a custom context menu when pressing the right click on top of a button with a PopUpMenu with prefer_native_menu set to true after the PopUp is displayed and hidden, by selecting a PopUpMenu item or not, the focus becomes permanently linked to the last control that the mouse was on top of.

The issue does not happen when prefer_native_menu=false, I tested on Windows and a friend tested on linux and the issue does not happen, appears to be exclusive to macOS.

### Steps to reproduce

- Create an empty project
- Add some button
- Add a PopUpMenu with prefer_native_menu set to true
- Add a script with an override to the _gui_input method
- On the same method when right click event received clear the PopUpMenu, add an item and call the popup method
- Run the project
- Right click on the button, dismiss the popup or select an item and try to press another button present in the scene


Also here is a video better explaining the issue.
https://github.com/user-attachments/assets/e2e43e56-2df9-49a8-9e52-0ab2b9f3f637




### Minimal reproduction project (MRP)

[bug-popup-menu.zip](https://github.com/user-attachments/files/18278468/bug-popup-menu.zip)
Repository: godot
Issue: Cannot compile godot project after moving godot scripts to new assembly
Labels: enhancement,discussion,topic:dotnet

### Tested versions

Reproducible in All versions. Especially 4.3 and 4.2

### System information

All

### Issue description

Godot does is not compiling application if godot scripts are moved into a second assembly.

How do we organize code for a larger project or make multi-project shared code if all scripts are forced to be in the top-level assembly?

### Steps to reproduce

Take a multi-assembly godot project.

Then move scripts to another assembly.

### Minimal reproduction project (MRP)

N/A
Repository: terminal
Issue: Allow Fixing of Row/Col number, resize window only changes font size.
Labels: Issue-Feature,Help Wanted,Area-UserInterface,Product-Terminal,Needs-Tag-Fix

### Description of the new feature

Allow setting the number of rows and columns to fixed numbers. 
If the user then adjusts the size of the window, font size is adjusted instead of adding more rows or columns.


### Proposed technical implementation details

_No response_
Repository: rust
Issue: Tracking Issue for `-Z link-directives`
Labels: A-linkage,T-compiler,C-tracking-issue,A-CLI

This is a tracking issue for the unstable rustc flag `-Z link-directives` where

> `-Zlink-directives=no` will ignored `#[link]` directives while compiling a crate, so nothing is emitted into the crate's metadata.  The assumption is that the build system already knows about the crate's native dependencies and can provide them at link time without these directives.
>
> *PR description of https://github.com/rust-lang/rust/pull/107675#issue-1571163041*

### About tracking issues

Tracking issues are used to record the overall progress of implementation. They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions. A tracking issue is however *not* meant for large scale discussion, questions, or bug reports about a feature. Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

### Steps

- [x] ~~Open an MCP and have it accepted.~~ At the time of impl, there was no such requirement.
- [x] Implementation
    - https://github.com/rust-lang/rust/pull/107675
- [ ] Adjust documentation ([see instructions on rustc-dev-guide][doc-guide])
- [ ] Stabilization PR ([see instructions on rustc-dev-guide][stabilization-guide])

[stabilization-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#stabilization-pr
[doc-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#documentation-prs

### Unresolved Questions

- Missing unstable flag documentation?
- What does this unstable rustc flag `-Z link-directives` do, exactly?
- How does it relate to the stable `#[link]` attribute?
- What does this mean for the [`#[link]` attribute][link-attr] (which is a stable attribute)?
- How does this unstable flag relate to `-Z link-native-libraries`?

### Implementation history

- Initial implementation PR: https://github.com/rust-lang/rust/pull/107675

### Related links

- https://github.com/rust-lang/rust/issues/70093
- https://github.com/rust-lang/rust/pull/70095
- https://github.com/rust-lang/rust/issues/134948

[link-attr]: https://doc.rust-lang.org/reference/items/external-blocks.html#the-link-attribute
Repository: rust
Issue: Tracking Issue for `-Z link-native-libraries`
Labels: A-linkage,T-compiler,C-tracking-issue,A-CLI

This is a tracking issue for the unstable rustc flag `-Z link-native-libraries`.

### About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however *not* meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
Discussion comments will get marked as off-topic or deleted.
Repeated discussions on the tracking issue may lead to the tracking issue getting locked.

### Steps

- [x] ~~Open an MCP and have it accepted.~~ At the time of impl, there was no such requirement.
- [x] Implementation
    - https://github.com/rust-lang/rust/pull/70095
- [ ] Adjust documentation ([see instructions on rustc-dev-guide][doc-guide])
    - https://github.com/rust-lang/rust/pull/116213
- [ ] Stabilization PR ([see instructions on rustc-dev-guide][stabilization-guide])

[stabilization-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#stabilization-pr
[doc-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#documentation-prs

### Unresolved Questions

- What does this unstable rustc flag `-Z link-native-libraries` do, exactly?
- How does it relate to the stable `#[link]` attribute?
- What does this mean for the [`#[link]` attribute][link-attr] (which is a stable attribute)?
- How does this unstable flag relate to `-Z link-directives`?
    > > Seems fine to me. Perhaps we should proactively remove the other Zlink-native-libraries flag as a "failed experiment"?
    >
    > I think we still need -Zlink-native-libraries to deal with prebuilt rlibs - ie, the sysroot libraries.
    > https://github.com/rust-lang/rust/pull/107675#issuecomment-1489041015

### Implementation history

- https://github.com/rust-lang/rust/pull/70095
- https://github.com/rust-lang/rust/pull/116213

### Related links

- https://github.com/rust-lang/rust/issues/70093
- https://github.com/rust-lang/rust/pull/70095
- https://github.com/rust-lang/rust/issues/134947

[link-attr]: https://doc.rust-lang.org/reference/items/external-blocks.html#the-link-attribute
Repository: PowerToys
Issue: OLED Protection feature.
Labels: Needs-Triage

### Description of the new feature / enhancement

#000000 overlay with opacity setting on top of each window until you hover on them or focus on them. Press a hotkey to show without overlay for set number of seconds or hold hotkey instead. Same thing goes for the taskbar so no need to set it to auto-hide.

An addon to FancyZones or a completely new feature.

### Scenario when this would be used?

OLED monitors are becoming more and more common and naturally the number of people buying them goes up, but they do still currently have issues with burn-in if you don't take care of them, especially for people with productivity workloads.



Much better than having to minimize them every time. This will definitely reduce burn-in to a significant degree.

### Supporting information

https://www.rtings.com/tv/tests/longevity-burn-in-test-updates-and-results

Thank you!
Repository: neovim
Issue: Already-typed prefix is deleted when invoking omnifunc with completeopt set to menuone,longest
Labels: bug,lsp,completion

### Problem

When using `completeopt=menuone,longest`, triggering omnifunc with `<C-X C-O>` will delete the already-typed prefix if there are multiple matches. It should not delete any characters at all.

If I edit a Python file and try to type `staticmethod` by typing `sta` then pressing `<C-X C-O>`, `sta` is deleted and the completion popup is shown for prefix `sta`. If I type more characters before I invoke omnifunc, it will complete properly instead of deleting. It seems to be inconsistent how many characters are needed.

If I disable `longest` and just set `completeopt` to `menuone`, omnifunc in the Python file no longer causes the already-typed prefix to be deleted (but I lose the functionality of `longest`).

I bisected and found commit 025c87441502cf570bad7b71f40bc6fe88989297 does not exhibit this bug, but it looks like there has been a lot of change to the LSP code since then so there may be versions in between that don't exhibit it either.

### Steps to reproduce

My `minimal.lua`, from the template, and run with `nvim --clean -u minimal.lua`:

```
for name, url in pairs {
  'https://github.com/neovim/nvim-lspconfig/',
} do
  local install_path = vim.fn.fnamemodify('nvim_issue/' .. name, ':p')
  if vim.fn.isdirectory(install_path) == 0 then
    vim.fn.system { 'git', 'clone', '--depth=1', url, install_path }
  end
  vim.opt.runtimepath:append(install_path)
end

vim.o.completeopt = "longest,menuone"

local on_attach = function(client, bufnr)
    vim.bo.omnifunc = "v:lua.vim.lsp.omnifunc"
end

local nvim_lsp = require('lspconfig')

nvim_lsp.pyright.setup({ on_attach = on_attach })
```

I have built neovim from source using a vanilla `make install` to a custom prefix:

```
git clone --bare --recurse-submodules https://github.com/neovim/neovim /path/to/dir
cd /path/to/dir
make CMAKE_BUILD_TYPE=Release CMAKE_INSTALL_PREFIX="/path/to/install" install
```

### Expected behavior

If I edit a Python file and try to type `staticmethod` by typing `sta` then pressing `<C-X C-O>`, `sta` should be preserved and the completion popup should be shown for prefix `sta`.

### Nvim version (nvim -v)

commit e9c077d197a80a2ecd858821b18d0be3e3eb6d0b

### Vim (not Nvim) behaves the same?

Can't reproduce, LSP related.

### Operating system/version

Debian Trixie

### Terminal name/version

foot 1.18.1

### $TERM environment variable

xterm-256color

### Installation

Build from repo
Repository: next.js
Issue: Turbopack error when using roboto flex font
Labels: Font (next/font),Turbopack

### Link to the code that reproduces this issue

https://github.com/Arctomachine/next-font-roboto-flex-bug

### To Reproduce

Start dev server and open page in browser

### Current vs. Expected behavior

Current: gives error 500 when following is present. Error happens when constant is assigned. Other fonts from roboto family work
```js
import { Roboto_Flex } from 'next/font/google'

const robotoFlex = Roboto_Flex({
  subsets: ['latin'],
})
```

Expected: works with this font

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Pro
  Available memory (MB): 32720
  Available CPU cores: 12
Binaries:
  Node: 20.17.0
  npm: 10.8.2
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 15.1.1-canary.23 // Latest available version is detected (15.1.1-canary.23).
  eslint-config-next: N/A
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Font (next/font), Turbopack

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

_No response_
Repository: flutter
Issue: SelectionArea should expose a selectionHeightStyle option
Labels: c: new feature,framework,c: proposal,P3,f: selection,team-framework,triaged-framework

### Use case

For a `SelectionArea` with nested `Text` that defines a sufficiently large `height` value, the selected region contains gaps that do not account for the height, as seen in the example below:

```dart
Text(
  "Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.",
  style: TextStyle(height: 1.5),
),
```

<img width="537" alt="selection_area" src="https://github.com/user-attachments/assets/ee7a4ec1-a9fe-43d3-a25d-8d650fbf5fad" />

### Proposal

The reason for this is that `SelectionArea` does not expose a `selectionHeightStyle` property that allows a user to set `BoxHeightStyle` to an alternate value than the default.

This is provided for `SelectableText` and works as expected, but there is not analogous option in `SelectionArea`.

```dart
SelectableText(
  "Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.",
  style: TextStyle(height: 1.5),
  selectionHeightStyle: ui.BoxHeightStyle.includeLineSpacingTop,
),
```

<img width="538" alt="selectable_text" src="https://github.com/user-attachments/assets/fc902516-f3ae-4e83-8ccf-b7a8d0a137d7" />

------

It would be nice to be able to set this in `SelectionArea` once instead of needing to use `SelectableText`. Further, it is more preferable to to use `SelectionArea` in a web app (to be able to drag the entire page) and `SelectableText` may not even be an option.

### Flutter Version

```
Flutter 3.27.1 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 17025dd882 (2 weeks ago) • 2024-12-17 03:23:09 +0900
Engine • revision cb4b5fff73
Tools • Dart 3.6.0 • DevTools 2.40.2
```

### Related Issues:

There are two somewhat related issues/comments:

- https://github.com/flutter/flutter/issues/104429
- https://github.com/flutter/flutter/issues/137817#issuecomment-2010414947
Repository: ui
Issue: [bug]: After the mobile sidebar is opened and the page is redirected, the style="pointer-events: none;" in the body affects the click events on the redirected page.
Labels: bug

### Describe the bug

On the mobile page, after opening the sidebar, a link was redirected. After the redirect, the style="pointer-events: none;" in the body was not reset, affecting the page's click events.

### Affected component/components

Sidebar

### How to reproduce

1. `NavUser.tsx`

```tsx
  <SidebarMenu>
      <DropdownMenuGroup>
              <DropdownMenuItem onClick={() => router.push('/')}>
                <Undo2 />
               Return to Home Page
              </DropdownMenuItem>
            </DropdownMenuGroup>
  </SidebarMenu>
```

then in body 

`<body style='pointer-events:none;'></body>`



### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
macos
chrome
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: TypeScript
Issue: Incorrect Formatting on `if (a) try {} finally {}`
Labels: Bug,Help Wanted,Domain: Formatter

### 🔎 Search Terms

format, formatter, finally

### 🕗 Version & Regression Information

- This is the behavior in every version I tried (it didn't change between TS3.3 and TS5.8).

### ⏯ Playground Link

[Playground Link](https://www.typescriptlang.org/play/?ts=5.7.2#code/JYMwBAFALgTgrgUwJRlgTzAbwFBj2AegLADozsBfMEYAOwEMAbRjHfQ4sky7IA)

### 💻 Code

```ts
if (true) try {
    // ...
} finally {
    // ...
}
```

Click "Format Document" from the context menu or via keyboard shortcut (opt+shift+f).

### 🙁 Actual behavior

The format result is
```ts
if (true) try {
    // ...
} finally {
        // ...
    }
```

### 🙂 Expected behavior

Do not add indentation to the finally block.

### Additional information about the issue

Note that `if (a) try {} catch {}` works fine. Maybe there're something related. [Playground Link](https://www.typescriptlang.org/play/?ts=5.7.2#code/JYMwBAFALgTgrgUwJRlgTzAbwFBj2AegLADozsBfMAYwEMpqALLXfI08qkYAO1oBt+GHPlGFiZEqzwVsQA)

Related #3817
Repository: electron
Issue: [Bug]: tray not showing up over fullscreen window when clicked on tray icon from a secondary display
Labels: platform/macOS,bug :beetle:,33-x-y

> ### Electron Version
> 33.2.1
> 
> ### What operating system(s) are you using?
> macOS
> 
> ### Operating System Version
> macOS Sonoma 15.1.1
> 
> ### What arch are you using?
> arm64 (including Apple Silicon)
> 
> ### Last Known Working Electron version
> No response
> 
> ### Update
> The tray now shows up when clicked on the tray icon of the secondary display, though not visible on fullscreen apps.
> 
> Shows on empty workspace
> ![Image](https://github.com/user-attachments/assets/37852f4c-2443-4dbe-9daf-2555219927de)
> 
> Shows over non-fullscreen window
> ![Image](https://github.com/user-attachments/assets/9ffcb47a-eaae-401b-a4be-22c809ce98a1)
> 
> Not visible over the same app in fullscreen mode
> ![Image](https://github.com/user-attachments/assets/507937f6-49f6-4047-bca6-156c4f341da1)
>  

 _Originally posted by @Hackerbee in [#43489](https://github.com/electron/electron/issues/43489#issuecomment-2566137038)_
Repository: godot
Issue: Moving mesh files with embedded textures doesn't clear files created in the original location
Labels: bug,topic:import

### Tested versions

- Reproducible in 4.3 stable

### System information

Godot v4.3.stable - Fedora Linux 41 (Workstation Edition) - Wayland - Vulkan (Forward+) - integrated Intel(R) UHD Graphics (TGL GT1) - 11th Gen Intel(R) Core(TM) i5-11400H @ 2.70GHz (12 Threads)

### Issue description

When a mesh containing embedded textures is imported Godot automatically creates files for textures in that mesh. However, when that mesh is then moved to another directory, the automatically created textures will stay around (with new ones being created in the new directory).
That makes it quite easy to pollute your project with spurious files.

### Steps to reproduce

In editor, drag and drop `anvil.glb` from the `source_dir` to the `target_dir`.

The original texture will remain in `source_dir`.

### Minimal reproduction project (MRP)

[repro.zip](https://github.com/user-attachments/files/18279587/repro.zip)
Repository: transformers
Issue: "Is it possible for Hugging Face to implement a chat model for quick information retrieval similar to vLLM?"
Labels: Feature request

### Feature request

![screenshot-20241231-155528](https://github.com/user-attachments/assets/889e19bf-7d74-4486-ad98-0210203df42f)


### Motivation

Quick and convenient information retrieval.

### Your contribution

I don't have relevant code for this feature request.
Repository: react
Issue: [React 19] Bug: optimisticState is updated with both new state and optimisticValue in useOptimistic
Labels: React 19

Using the react Example given for useOptimistic hook in docs, an update in state passed to the hook should directly reset the optimisticState in one render.

Instead
1. It calls the updaterFn first, updates the optimisticState using new state and optimisticValue during one render cycle
resets optimisticState with new State in another render cycle.
2. As a result, both the new state and optimisticValue is rendered. Tried this in 20x slowdown

https://github.com/user-attachments/assets/6abfdd9a-c2ea-4776-8df4-48ce2e3eb41d


**React version**: 19

**Steps To Reproduce**

1. Throttle CPU to 20x slowdown
2. Type some input in text box and press submit
3. See that the optimistic state is displayed and then it is pushed down for an instant along with the new state
4. Check console logs

<img width="1728" alt="Screen Shot 2024-12-31 at 1 42 21 PM" src="https://github.com/user-attachments/assets/10c655e8-154c-4813-9f68-eb78e4e1e57e" />

**Link to code example:**

https://codesandbox.io/p/sandbox/react-dev-forked-gmlxnr?file=%2Fsrc%2FApp.js&workspaceId=ws_QiCvK4c476hege6EDsXfpC

**The current behavior**

When new state is passed to useOptimistic,

1. It updates optimisticState by calling updaterFn with new state and optimisticValue
2. Component is rendered using this optimisticState (incorrect one)
3. Another update to optimisticState is done by resetting it to the new state
4. Component is rendered using this new optimisticState (correct one)


**The expected behavior**

When new state is passed to useOptimistic, it should directly reset the optimisticState without calling the updater Fn
Repository: flutter
Issue: Line indentation and paragraph spacing
Labels: framework,a: typography,c: proposal,P3,team-engine,triaged-engine

### Use case

I would like to render poetic text where a soft-wrap results in greater indentation than the first line. For example, the word "inheritance" in the image below is more indented. Additionally, different lines have different indentation styles:

<img width="333" alt="Screenshot 2024-12-31 at 16 34 38" src="https://github.com/user-attachments/assets/30a3bfd9-301b-4934-a03f-d2f6471ca051" />

It would be possible to achieve an initial indent with a `WidgetSpan` wrapping a `SizedBox`. However, I know of no way to accomplish the soft-wrap indentation in Flutter besides measuring and laying out every word myself. 

Another need is to be able to adjust the spacing between paragraphs. Using different Text widgets results in not being able to select text across widgets. Note in the following example, the paragraph spacing is less that it would be if you simply used two newline characters to separate the paragraphs:

<img width="363" alt="Screenshot 2024-12-31 at 16 55 48" src="https://github.com/user-attachments/assets/7a01173c-147d-4ac6-b38f-a1c13d66a2bb" />

Related issues: #12255, #128218

### Proposal

I would like a solution similar to what is available in Android or iOS development.

In Android, indentation is possible with [`LeadingMarginSpan`](https://developer.android.com/reference/android/text/style/LeadingMarginSpan) as shown in the following image ([source](https://stackoverflow.com/a/42058964/3681880)):

![image](https://github.com/user-attachments/assets/5f1aaa62-7b53-4a9d-8cfb-473ec502e442)

In iOS, both indentation and paragraph spacing are possible with [`NSMutableParagraphStyle`](https://developer.apple.com/documentation/uikit/nsmutableparagraphstyle). 

An API similar to the iOS solution would be great.